225754744 NSN RG10 New Features and Features Under Development

1

RG10(BSS) NF & FUD

New Features and Features Under Development

Ver 2.15.0

Confidential

2

The information in this document is subject to change without notice and describes only the product defined in

the introduction of this documentation. This document is not an official customer document and Nokia Siemens

Networks does not take responsibility for any errors or omissions in this document. This document is intended

for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the

document is submitted. No part of this documentation may be used, reproduced, modified or transmitted in any

form or means without the prior written permission of Nokia Siemens Networks. The documentation has been

prepared to be used by professional and properly trained personnel, and the customer assumes full

responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of

continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity or performance of

the mentioned hardware or software products are given as is and all liability arising in connection with such

hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia

Siemens Networks and the customer.

IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR

ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR

CONSEQUENTIAL OR ANY LOSSES SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE,

BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, that might arise from the use of this

document or the information in it.

THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY APPLICABLE

MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE AND NON-INFRINGEMENT, ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR

CONTENTS OF THIS DOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT TO REVISE

THIS DOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE.

This document and the product it describes are considered protected by copyrights and other intellectual

property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia

Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are

mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2010. All rights reserved.

3

Index

1 Summary of changes ................................................................................................ 5

2 Introduction ............................................................................................................. 11

3 BSC & TCSM Products ........................................................................................... 16

3.1 BSC hardware requirements ......................................................................................... 16

3.2 TCSM hardware requirements ...................................................................................... 18

3.3 PCU hardware requirements ......................................................................................... 18

3.4 BSC HW requirements for new ASW products...................................................... 18

3.5 Integrated IP card for BSC and TCSM ....................................................................... 19

3.6 Asymmetrical PCU HW Configuration ....................................................................... 21

3.7 Flexi BSC ............................................................................................................................... 24

3.8 L3 Connectivity for Flexi BSC ....................................................................................... 27

3.9 SDH/SONET Equipment Protection ............................................................................ 29

3.10 SW Support of BS2xx@FlexiBSC Family ............................................................. 31

3.11 SW Support of Horizon@FlexiBSC Family .......................................................... 32

3.12 Flexi Multiradio HW Activation ................................................................................. 33

4 Radio Network Performance .................................................................................. 35

4.1 Wideband AMR (WB-AMR) ............................................................................................. 35

4.2 Wideband AMR support for TCSM3i .......................................................................... 39

4.3 AMR HO Signaling Optimizations ............................................................................... 41

4.4 Tandem Free Operation (TFO) for AMR .................................................................... 42

4.5 A5/3 ciphering ...................................................................................................................... 45

4.6 SDCCH and PS Data Channels on DFCA TRX ....................................................... 47

4.7 AMR Unpacking Optimization ....................................................................................... 49

4.8 105km Extended Cell ........................................................................................................ 51

4.9 105km Extended Cell for GPRS/EDGE ...................................................................... 54

4.10 Enhanced Satellite Abis Support up to 420ms .................................................. 55

4.11 Paging Coordination ..................................................................................................... 56

4.12 Extended CCCH .............................................................................................................. 58

4.13 Extended BCCH .............................................................................................................. 60

4.14 Priority Based Voice Quality...................................................................................... 61

4

4.15 Merged P- & E-GSM900 ................................................................................................ 62

4.16 Higher Average Power per TRX in Flexi Multiradio ......................................... 64

4.17 Instant QoS Signaling ................................................................................................... 66

4.18 Disable Internal Handover .......................................................................................... 68

4.19 RF Sharing GSM - WCDMA ........................................................................................ 69

5 Interworking............................................................................................................. 71

5.1 Load Reporting via Iur-G ................................................................................................. 71

5.2 ISHO acceleration via Iur-G ............................................................................................ 73

5.3 LTE System Information w/ MML support ............................................................... 74

6 Packet Switched Data ............................................................................................. 77

6.1 Downlink Dual Carrier ...................................................................................................... 77

6.2 PCU2 Acceleration ............................................................................................................. 80

6.3 Smart Resource Adaptation (SRA) ............................................................................. 82

7 Operability ............................................................................................................... 85

7.1 Energy saving mode for BCCH TRX........................................................................... 85

7.2 2G TRX Automatic Power Down .................................................................................. 87

7.3 Secure remote MMI ............................................................................................................ 89

7.4 OSI over TCP/IP ................................................................................................................... 91

7.5 Automated RNW O&M log collection ......................................................................... 93

7.6 Support of FlexiEdge PWE Counters ......................................................................... 95

7.7 Flexi BSC support of all BTSplus ENVA alarms ................................................... 98

7.8 Adjustable UL RLT Increase Step ............................................................................. 100

7.9 BSC L3 Data Collector .................................................................................................... 101

8 Transmission and Transport ................................................................................ 102

8.1 FlexiEDGE Ethernet switching ................................................................................... 102

9 Value Adding Services .......................................................................................... 103

9.1 Support for Real Time Road Traffic Information ................................................. 103

9.2 Support for Commercial Mobile Alert System (CMAS) .................................... 108

9.3 Blocking of DTMF in Downlink ................................................................................... 110

5

1 Summary of changes

DATE ISSUE EDITED SUMMARY OF MAIN CHANGES

FCD (Feature Candidate Description)

18.05.2007 1.0.0 Reijo

Lyytinen

RG10(BSS) Program internal version

04.06.2007 1.1.0 Reijo

Lyytinen

Approved version

27.08.2007 1.2.0 Reijo

Lyytinen

The following features removed

- BSS21184, 8k Abis for AMR/FR

- BSS21109, Early UL TBF establishment

- BSS20519, Proactive extended UL TBF

polling

- Separate RLT for AMR DL and UL in

Optimizations

10.12.2007 1.3.0 Frode

Paulsen


- Fast Ack/Nack Reporting

- Packet Switched Handover (PSHO)

- Support for MS Receiver Diversity

16.12.2007 1.4.0 Frode

Paulsen

The following features added

- AMR unpacking optimization

- Automated RNW O&M log Collection

- Asymmetrical PCU HW Configuration

02.01.2008 1.5.0 Frode

Paulsen

The name of BSS20984 has been changed to

- Flexi EDGE DTRX Automatic Power Down


- Proactive DL TBF Establishment

For Asymmetrical PCU HW Configuration:

Functional Description-Text improved.

6

For WB-AMR:


For WB-AMR support by TCSM3i:


For AMR TFO:


Dependency Tables have been updated for the

following features:

- AMR HO Signaling Optimisations

- AMR Unpacking Optimisations

- Downlink Dual Carrier

- Secure Remote MMI

- OSU over TCP/IP

FUD (Features Under Development)

14.03.2008 2.0.0 Frode

Paulsen

The following features removed from the document

- PCU Restart Handling

- Robust EDGE Retransmission

- Improved Extended UL TBF

Chapter 2: Compatibility with other NEs has been

updated.

07.04.2008 2.1.0 Frode

Paulsen

The 2G 2G part of the Load Aware ISHO

admission has been separated from the original

feature and turned into its own feature BSS30650

Load Aware Inter-BSC HO Admission.

03.06.2008 2.1.0 Frode

Paulsen

The SGSN dependency for the DL DC feature has

been removed.

10.07.2008 2.2.0 Frode

Paulsen

The PCU-2 Dependency to the BSS20097

Automated RNW O&M log collection has been

removed.

17.07.2008 2.3.0 Frode

Paulsen

Removed from RG10(BSS):

BSS21141 Load aware ISHO admission

BSS30650 Load aware inter-BSC HO admission

7

17.07.2008 2.3.0 Frode

Paulsen

Added to RG10(BSS):

BSS21333 Support for Real Time Road Traffic Inform.

17.07.2008 2.3.0 Frode

Paulsen

Preliminary Compatibility Tables have been

introduced into chapter 1. Introduction

17.07.2008 2.3.0 Frode

Paulsen

The classification of ASW and Basic Feature has

been removed

16.09.2008 2.3.0 Frode

Paulsen

Added to RG10(BSS):

BSS21149 Flexi BSC.

30.09.2008 2.4.0 Frode

Paulsen

Added to RG10(BSS):

BSS21317 Full support of Append BTS

commissioning.

30.09.2008 2.5.0 Frode

Paulsen

Text modified/improved:

BSS21149 Flexi BSC.

30.09.2008 2.6.0 Frode

Paulsen

New Feature introduced:

BSS21323 L3 Connectivity for Flexi BSC.

30.09.2008 2.6.0 Frode

Paulsen

Text updated for:

3. BSC & TCSM Products (changed from tentative to

actual).

18.01.2009 2.7.0 Frode

Paulsen

The Release name changed from BSS14 to

RG10(BSS)

18.01.2009 2.7.0 Frode

Paulsen

New Feature introduced:

BSS21234 Support of FlexiEdge PWE Counters.

18.01.2009 2.7.0 Frode

Paulsen

Feature changed from Public to Internal :

BSS21317 6.6 Full support of Append BTS commissioning.

Note: The functionality is still supported, but not

handled/described as sales feature.

18.01.2009 2.7.0 Frode

Paulsen

Correction :

BTS dependency in the dependency table has been

removed for the feature BSS20916 AMR HO

Signaling Optimizations".

27.02.2009 2.8.0 Frode

Paulsen

Feature added to the FUD:

BSS21108 SDH/SONET Equipment Protection.

8

27.02.2009 2.8.0 Ismo

Honkala

mmi

Correction :

BSC HW requirements have been updated

27.02.2009 2.9.0 Frode

Paulsen

Correction :

The Compatibility Matrixes in the Introduction

chapter have been updated.

27.04.2009 2.9.0 Frode

Paulsen

Added to the WB AMR description:

Note that the WB AMR Capacity License is required

to enable more than 100 simultaneous calls per BSC.

27.05.2009 2.9.0 Frode

Paulsen

Features added to the FUD:

BSS21198 PCU2 Acceleration

BSS21270 105km Extended Cell for CS

BSS21277 105km Extended Cell for GPRS/EDGE

.

17.08.2009 2.9.1 Frode

Paulsen

Correction::

Compatibility Matrix corrected: Red color for OSS4.2

CD Set 1 with CX7 and EP3.

.

09.09.2009 2.9.2 Frode

Paulsen

Correction::

The PCU2 dependency for Asymmetrical PCU

Configuration on page 11 has been removed.

.

15.12.2009 2.10.2 Frode

Paulsen

New Features added :

Network Evolution

BSS21538 Extended CCCH

BSS21497 Enhanced Satellite Abis Support to 420ms

Voice and Data

BSS20738 Paging Coordination

Interworking

BSS21527 Load Reporting via Iur-G

Site Solutions

BSS21469 SW Support of BS2xx@FlexiBSC Family

(the introduction ch. has been adapted accordingly)

9

15.12.2009 2.10.2 Frode

Paulsen

Dependency Tables have been updated :

- BTSplus has been introduced as BTS type

- BTS 2nd Gen. has been removed

05.04.2010 2.11.0 Frode

Paulsen

Correction:

Support of Extended CCCH for MetroSite BTS has

been corrected from MP3.0 to MP2.0 in the

dependency table

15.04.2010 2.11.0 Frode

Paulsen

Feature added.

The Feature Extended BCCH has been added

18.04.2010 2.11.0 Frode

Paulsen

Features added.

BSS21403 Flexi Multiradio HW Activation

BSS101456 Priority based Voice Quality

BSS21528 Iur-g interface phase 2

BSS21529 LTE System Info. w/ MML support

BSS101422 Support for CMAS

BSS101443 Blocking of DTMF in Downlink

BSS21238 Merged P-&E-GSM900

15.07.2010 2.12.1 Frode

Paulsen

Dependency Tables have been updated :

- Flexi MultiRadio has been introduced as BTS type

- Talk Family BTS has been removed

15.10.2010 2.12.2 Frode

Paulsen

Flexi BSC Family as requirement for Flexi

MultiRadio has been removed. (Was never the case!)

15.11.2010 2.12.2 Frode

Paulsen

The Flexi Multiradio version to support eCCCH and

eBCCH has been corrected to EX3.1 MP1.0.

15.02.2011 2.13.0 Frode

Paulsen

The feature Smart Resource Adaptation (SRA) has

been introduced.

10

11.05.2010 2.14.0 Frode

Paulsen

Features added.

RG602081 SW Support of Horizon@FlexiBSC Family

RG301555 Higher Average Power pr TRX in FlexiMR

BSS402071 Instant QoS Signaling

RG301631 Disable Internal Handover

RG301677 Flexi BSC support of all BTSplus alarms

RG301743 Adjustable UL RLT Increase Step

20.05.2011 2.14.1 Frode

Paulsen

PCU2 has been noted to be a pre-requisite for

BSS21161: SDCCH and PS data channels on DFCA

TRX.

11.10.2010 2.15.0 Frode

Paulsen

Features added.

RG301793 BSC L3 Data Collector

BSS21403 RF Sharing GSM - WCDMA

2 Introduction

This document describes the feature candidates for the Base Station Subsystem (BSS)

system release RG10(BSS).

Nokia Siemens Networks RG10(BSS) brings advantages for all operators by enabling

amongst others

Significantly improved voice quality by Wideband AMR

Enhanced CS service security by new A5/3 Ciphering algorithm

Doubled bit rates with EDGE evolution

OPEX savings with low cost transport and BTS energy saving solutions

OPEX savings with optimised BSC HW solutions

The standardisation baseline of RG10(BSS) release is 3GPP Release 7 September.

The compatibilities for individual NE releases are as follows:

RG10(BSS) consists of the releases: BSC S14, MetroSite CXM7, UltraSite CX7,

FlexiEDGE EP3, BTSplus BRG1 and Flexi Multiradio EX3.1.

Note:The latter would only be supported from the EP5.1 package of RG10(BSS).

RG10(BSS) is supported by the following NE releases: NetAct OSS5.1 CD set 2, MSC

M14.4, MGW U4.2 and SGSN SG7 CD2

The basic BSC S14 software release will be compatible with Talk Family DF7 BTS software

release, but the new RG10(BSS) features with BTS SW impact will not be supported by the

Talk Family BTS.

From the S14 MP3.0 also the BTSplus (BTS types from the former BR systems) will be

supported. This feature is called BSS21469 SW Support of BS2xx@FlexiBSC Family.

BSC SW release S13 will be the last compatible software level for the former Nokia InSite

BTS SW, so no support of RG10(BSS) is foreseen.

12

RG10(BSS) Compatibility Matrix

BSC BTSplus

Flexi

MultiR UltraSite MetroSite Flexi EDGE LMU

Release S12 S13 S14 BRx BRG1 EX3,1 CX5 CX6 CX7 CxM5 CxM6 CxM7 EP1 EP2 EP3 4.3 4.4 B1.0

S14

CXM7

CX7

EP3

OSS4.1 CD Set 2

OSS4.2

OSS4.2 CD Set 1

OSS5.1 CD Set 1

OSS5.1 CD Set 2

Release LMU4.3 LMU4.4

LMU-B

1.0

S14

CXM7

CX7

EP3

MSC MGW (with MSC-S) SGSN RNC

Release M12 M13 M14.3 M14.4 U2 U3A U3B U3C U4.1 SG5.1 SG6 SG7 RN2.2 RN3 RN4

S14

w/o

WB

AMR

Legend:

Compatibility not applicable

Compatibility not supported

13

Secondary compatibility

Primary compatibility

Notations used in dependency tables:

The table is used to relate the described BSS features to required system

components:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE

NetAct SGSN MSC RAN MS

Release - - - - - - - - - - - - -

14

In the table we use the following notations:

SUPPORTED IN:

MSC This feature is supported in the Nokia MSC (xxx =

Nokia Siemens Networks MSC release/feature

no) N = No, - = no dependency, X = support

required but release not defined.

Nokia

Siemens

Networks

MetroSite

This feature is supported by Nokia Siemens

Networks MetroSite BTS (xxx = Nokia Siemens

Networks release/feature no) N = No, - = no

dependency, X = support required but release

not defined.

Nokia

Siemens

Networks

NetAct

This feature is supported in the Nokia Siemens

Networks NetAct (xxx = Nokia Siemens Networks

release/feature no) N = No, - = no dependency, X

= support required but release not defined.

Nokia

Siemens

Networks

InSite


Networks InSite BTS (xxx = Nokia Siemens



not defined

BSC This feature is supported by the BSC (xxx = Nokia

Siemens Networks release/feature no) N = No, - =

no dependency, X = support required but release

not defined...

Nokia

Siemens

Networks

UltraSite


Networks UltraSite BTS (xxx = Nokia Siemens



not defined

SGSN This feature is supported by the SGSN (xxx =

Nokia Siemens Networks release/feature no) N =

No, - = no dependency, X = support required but

release not defined.

Nokia

Siemens

Networks

FlexiEDGE


Networks FlexiEDGE BTS (xxx = Nokia Siemens



not defined

Nokia

Siemens

Networks

2nd

Gen.

This feature is supported by the 2nd gen BTS.

(xxx = Nokia Siemens Networks release/feature

no) N = No, - = no dependency, X = support

required but release not defined.

MS The feature sets special requirements to mobile

stations (xxx = 3GPP release), - = no


not defined.

Nokia

Siemens

Networks

Talk-

family


Networks Talk-family BTS (xxx = Nokia Siemens


dependency, X = support required but release not

defined.

HW/FW DEPENDENCY:

Nokia

Siemens

Networks

PrimeSite


Networks PrimeSite BTS (xxx = Nokia Siemens


dependency, X = support required but release not

BSC

HW/FW

This feature requires additional or alternative

BSC hardware or firmware

15

defined.

DX200

Platform

This feature is supported by DX200 Platform (xxx

= Nokia Siemens Networks release/feature no) N

= No, - = no dependency, X = support required but

release not defined.

BTS

HW/FW


BTS hardware or firmware

TC HW/FW This feature requires additional or alternative

Transcoder hardware or firmware

SGSN

HW/FW


SGSN hardware or firmware

Operating/

Application

BSS SOFTWARE:

Indicates whether this feature is an Operating or

Application SW feature

16

3 BSC & TCSM Products

The S14 level HW requirements were confirmed at E2 (P5) milestone and have also

been communicated with the BSC HW Technical Note 174.

3.1 BSC hardware requirements

On top of Flexi BSC and BSC3i also BSCi and BSC2i will support the S14 SW

release. Some functionality like Integrated IP card will be available only for Flexi

BSC and BSC3i 1000/2000 (and additionally for TCSM3i).

The S14 release sets a mandatory HW requirements for the minimum memory

capacity of CPU units in computer units of M98 mechanics BSCs This means there is

a need to extend the memory configuration of BSC3i from S13 level:

BSC3i 660 and 1000/2000: 512 MB in BCSU, 1 GB in MCMU and OMU.

BSCi and BSC2i: 512 MB in OMU, MCMU and BCSU.

Flexi BSC has 1 GB in all units as standard.

Minimum Hard Disk size remains same as in S13.

The typical minimum O&M link capacity requirements remain the same as in S13:

BSCi, BSC2i, BSC3i 660: minimum 256 kbit/s, recommended 512 kbit/s

BSC3i 1000: minimum 512 kbit/s, recommended 1024 kbit/s

BSC3i 2000: minimum 1024 kbit/s, recommended 2048 kbit/s

Please note that deviations to the figures might exist due to the implications such as

number of managed objects under BSC, activated features, customer-specific data

collection settings or work processes.

LAN-based O&M connection is currently recommended to all product configurations

and most powerful link option method. Alternatively also digital X.25 connection is

still feasible when multiple 64 kbit/s timeslots are used. However, LAN interfaces are

mandatory with higher than 1024 kbit/s data speeds. As with earlier S13 SW release

analog X.25 connection with limited link capacity is no longer available with BSC3i

1000/2000 configuration + with Flexi BSC only LAN based connection is supported.

Please note also that in BSCi and BSC2i O&M LAN interface requires IP cabling and

CPLAN panels as well as external LAN switches and/or routers.

17

Note: For information on required EPROM upgrades with RG10(BSS) please refer to

the RA Maintenance Status Update issued 16.11.2010 by Jan Jensen with the title:

GSM/EDGE reminder of new EPROM ordering procedure (RG10/S14 upgrades)

18

3.2 TCSM hardware requirements

On top of TCSM3i also TCSM2 will support the S14 SW release. New transcoding

related Application SW (like Wideband AMR) will be supported only by TCSM3i.

3.3 PCU hardware requirements

All existing PCU units (PCU1, PCU2) can still be used with the basic S14 SW

release. Please note, that all new packet data related application SW (listed below)

will require PCU2.

3.4 BSC HW requirements for new ASW products

As with previous SW releases certain application software products set additional

requirements for BSC hardware. HW requirements for new S14 Application SW

(ASW) Products are listed in the following table:

PCU2 plug-in unit is mandatory HW

requirement for:

Downlink Dual Carrier

Table 1 BSC HW requirements for S14 Application SW products

19

3.5 Integrated IP card for BSC and TCSM

Feature ID: BSS21157

Summary: This feature integrates the IP/Ethernet interfaces into BSC3i 1000/2000 Abis

and Ater- and TCSM3i A- and Ater-interfaces. An ETIP1 plug-in unit, based on Circuit

Emulation Service over Packet-Switched Networks (CESoPSN) technology, is equipped

in place of an E1/T1 or STM-1/OC-3 unit to provide the IP connectivity. This solution

enables flexible integrated product configuration options between these transmission

technologies.

Benefits for the Operator: Transport in GERAN networks is today based mainly on

E1/T1 PCM lines. Several backhaul transport technologies are in use besides the native

E1/T1, like microwave radios, SDH rings/point-to-point connections, ATM etc.

IP based transmission is widely seen as a cost efficient alternative to reduce operability

costs, allows easy expansions and is predicted to be even more efficient in future. IP

networks are or will be readily available in many markets.

IP/Ethernet based transmission is especially suitable as common transport for 2G/3G

sites.

Lower OPEX and IMPEX can be achieved because there is no need for external

transmission units and no need to use BSCs interfaces to connect to this equipment.

Fast implementation is assured as cabling, power supply etc. issues can be discarded.

Integrated solution offers additionally higher reliability, lower power consumption and

integrated O&M via NetAct.

BSC & TCSM HW Requirements: TCSM3i or BSC3i 1000/2000 or Flexi BSC

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE


Release RG10(BSS) S14 B13 - - - - - - - - - -

21

3.6 Asymmetrical PCU HW Configuration


Summary: Asymmetrical PCU HW configuration allows operator to add and activate

PCU HW in granularity of one and according to traffic needs.

Benefits for the Operator:

Optimized and more space and cost efficient PCU HW configuration

Functional Description:

Asymmetrical PCU HW configuration allows the operator to add and activate PCU HW in

granularity of one and according traffic needs.

PCU HW is installed into the BSC in granularity of one (+ required amount of PCU HW

into the spare BCSU). BCSUs are equipped with PCU HW units according to traffic

needs, i.e. PCU HW units are added to BCSUs one by one until the full PCU HW unit

amount is reached in the BSC.

Asymmetrical PCU HW configuration introduces a definition of the primary spare BCSU.

With Asymmetrical PCU HW configuration the primary spare BCSU is configured to have

enough PCU HW units to take over any of the active BCSUs. The system will keep the

primary spare BCSU as the spare BCSU by performing related BCSU switchovers as

soon as the BCSU statuses allow this. A related alarm is raised if the primary spare

BCSU unit is not in SP-EX state.

22

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE


Release RG10(BSS) S14 - - - - - - - - - - -

24

3.7 Flexi BSC


Summary: The Flexi BSC name refers to the full support of the Flexi EDGE BTS and its

future evolution and also to full the flexibility in the Flexi BSC's capacity and connectivity

dimensioning. Flexi BSC is engineered to provide remarkable capacity and low power

consumption in one single cabinet design.


Every aspect of this product contributes to high operational efficiency. This BSC offers a

new level of capacity efficiency to the marketplace by being the only BSC to support

3000 TRXs in one cabinet and to provide the highest traffic handling capacity with 18000

Erlang. Additionally it offers a fully integrated solution to provide IP/Ethernet for all

interfaces, which will further strengthen the potential of the Flexi BSC the full flexibility

in configuring different transmission media will enable the operator to select the most

cost efficient alternative.


The new Flexi BSC configuration will support very high TRX configurations up to 3000

TRXs in very compact one single cabinet solution. The cabinet configuration will be

flexible from 500TRX to 3000 TRXs in 6 capacity steps. Together with the Circuit

Switched traffic support configuration it will support Packet Switched traffic amounts up

to 30 720 Abis links (16kbit/s). The Flexi BSC is based on the DX200 distributed

processor platform, which efficiently evolves with the commercial Intel processing power

and distributed architecture to new requirements this applies to the capacity as well as

to the functional evolution. All earlier delivered BSC3i configurations can be upgraded to

this latest specification.

25

Figure:

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTS

InSite

BTS

Flexi

EDGE


Release RG10(BSS) S14 - - - - - - OSS5.1

CD

SET 2

- - - -

27

3.8 L3 Connectivity for Flexi BSC


Summary: From S11.5 onwards, the BSC IP Connectivity solution /D/ requires L2/STP

interoperability between ESBs and Multilayer Site Switches. This could reduce the

reliability of the IP connectivity and also cause additional complexity in configuring the

connections. This feature removes the L2/STP interoperability requirement. Then BSC IP

Connectivity can be integrated to operator backbone without special IP requirements.


L3 Connectivity gives a more stable and easy-to-configure network compared to using

L2 connectivity.


The L3 Connectivity feature makes BSC IP integration easier for the operator IP

backbone and simplifies ESB configuration. L3 Connectivity is activated by configuring IP

address/route. Thus, the problematic L2 spanning tree configuration step is not needed

for enabling BSC IP Site Connectivity (in the Multilayer Site Switch).

L3 Connectivity means that multilayer functionality from Multilayer Site Switch is

transferred to L3 ESB such as MSTP root, virtual gateway and routing. Then, the

Multilayer Site Switches are operating as Site Routers from BSC point of view.

In the previous (S13) L2 solution, one or several BSC and Multilayer Site Switches

constitute one spanning area, e.g. called to MSTP region.

In the L3 solution, each BSC site has its own MSTP region. Thus Multilayer Site

Switches and BSCs are not controlled by the same spanning tree. Spanning tree is not

needed to be enabled in Multilayer Site Switch due to BSC.

28

Figure:

MSTP Region

MSTP Region

MSTP Region

MSTP Region

MSTP Region

IP backbone

BSC

L3 ESBs

L3

L3

L3

L3

L3

L2

L2L2

L2

L2

L2

L2

L2BSC

L2 ESBs

L2 and L3 sites

BSC application and Ethernet interface point of view, there is no need to do configuration

changes (IP addressing and routing).

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



CD

SET 2

- - - -

29

3.9 SDH/SONET Equipment Protection


Summary:

A highly reliable and redundant transport connection between the network elements is of

major importance for any operator and his business. This becomes even more important

with STM-1/OC-3 interfaces because of the high capacity of one optical fibre

SDH Equipment Protection is standardized solution and compatible with other suppliers

equipment in a multivendor environment.


In spite of an eventual drop out of one transmission interface unit the connection

between the network elements will sustain, thus preventing a break down in the mobile

network traffic and corresponding revenues and subscriber satisfaction.


Equipment protection is in addition to the 2N line redundancy (MSP 1+1 optical)

supported with the BSC3i configuration. Equipment protection fulfills the resiliency

options for various operator needs. It brings full 2N equipment redundancy for optical

interface units (ETS2).

BSC & TCSM HW Requirements: The Flexi BSC Family or TCSM3i for combined

BSC3i/TCSM3i installation.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE


30


CD

SET 2

- - - -

31

3.10 SW Support of BS2xx@FlexiBSC Family


Summary:

So far the BTS types BTSplus or the BS24x, BS4x, BS288 and BS82 II have only been

compatible with the BSC types BSC72/BSC120/eBSC. With this feature these BTS types

can also be used together with, and controlled by, the FlexiBSC family.


The introduction of the new FlexiBSC can be deployed in areas where the BTS types

BS24x, BS4x, BS288 and BS82 II are being used. Moreover, these BTS types can be

combined with the BTS types FlexiEDGE, Metro Site, Ultra Site, etc. in a common BSC

area controlled by one OSS system via NetAct.


The BS2xx SW, Abis interface and BTS/BSC functional split have been adapted to the

FlexiBSC. Moreover, where relevant the FlexiBSC functionality has been extended to

also support the legacy BS2xx functionality.

BSC & TCSM HW Requirements: The Flexi BSC Family and TCSM3i (or a MGW) are

required.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Talk

Family

BTSplus BTS

Flexi

EDGE


Release RG10(BSS) S14

MP3.0

And

PCU2

- - - - BRG1

9-40

- OSS5.1

CD

SET 2

- - - -

32

3.11 SW Support of Horizon@FlexiBSC Family

Feature ID: RG602081

Summary:

So far the BTS Horizon I and Horizon II could only be connected with the Motorola BSC

types BSC2/BSC6. With this feature these BTS types can also be used together with,

and controlled by, the NSN Flex iBSC family.


he Motorola Horizon I and Horizon II BTS hardware may be reused when introducing the

NSN FlexiBSC and the NSN BSS system. Moreover, these BTS types can be combined

with the BTS types FlexiEDGE, Metro Site, Ultra Site, etc. in a common BSC area

controlled by one OSS system via NetAct.


The Horizon BTS SW, Abis interface and BTS/BSC functional split have been adapted to

the NSN FlexiBSC. Horizon BTS will be an integral part of the NSN BTS portfolio and will

be managed by the BSC as any other NSN BTS.

BSC & TCSM HW Requirements: The Flexi BSC Family and TCSM3i (or a MGW) are

required.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Horizon

I and II

BTSplus BTS

Flexi

EDGE



EP9.1

And

PCU2

- - - HR 1.0 - - OSS5.2

CD

SET 2

- - - -

33

3.12 Flexi Multiradio HW Activation


Summary:

The BSS system will hereby also support this new Flexi Multiradio BTS type that is also

capable to run (beyond 2G/GSM) 3G and LTE radio standards.


The same HW can be (re)used for different radio network technologies like GSM, UMTS

and LTE thus saving OPEX and CAPEX.


This BTS can work standalone in either one technology or in sharing mode, sharing

GERAN with LTE, GERAN with 3G, or 3G with LTE. The shared modules inside the BTS

are Radio Modules (RM). The system modules (for GERAN ESMB system module and

for 3G & LTE FTM system module) are not shared and thus the M-plane functionalities

are not impacted.

The Flexi Multiradio wil support all the BSS features except:

Combined O&M and Telecom signaling

Extended Cell - Long Reach TSL (FlexiEDGE BTS)

105km Extended Cell (FlexiEDGE BTS)

Extended Cell for GPRS/EDGE

105km Extended Cell for GPRS/EDGE

Double Power TRX for Flexi EDGE BTS

DFCA related features

LMU Sync

SRC(IDD+2UD and IDD+4UD)

BSC & TCSM HW Requirements: All the BSC variants support the Flexi Multiradio BTS.

34

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP5.1

- - - EX3.1 - - OSS5.2

CD

SET 2

- - - -

35

4 Radio Network Performance

4.1 Wideband AMR (WB-AMR)


Summary: Wideband Adaptive multi rate (WB AMR) brings voice communication to new

era with a new speech codec family. Audible improvements include warmer and clearer

tone due to extended bandwidth towards both lower and higher frequencies.

Wide Band Adaptive Multi-Rate (WB-AMR) uses a twice as high sampling rate compared

to current voice services in mobile and fixed line telephony. Together with higher

sampling frequency the transcoding algorithms are improved as well in WB-AMR.

Furthermore audio capabilities of current handsets e.g. with integrated MP3 players are

well ahead of AMR quality, thus motivating to improve voice service capabilities as well.

WB-AMR codec set supported by BSS consists of 12.65, 8.85 and 6.60 kbps codec

rates, which are currently the same as in WCDMA RAN.


Increased revenue expected by longer and more frequent voice calls.

Improved end user experience: WB-AMR provides significant speech quality

enhancements compared to AMR, fixed line telephony or xDSL VoIP. Even music

applications are possible through enhanced audio bandwidth. With clear audible

enhancements, MS to MS conversations will become more transparent and callers will

feel like being closer to each other. Furthermore the transmission of the finer nuances of

the human voice will make communicating more complete.

As soon as the end-user has once experienced this quality, he will most likely not be

willing to change back to non-WB-AMR anymore if a choice is being offered. With WB-

AMR mobile voice calls will be used more frequently and continue longer. WB-AMR will

boost wire-line to mobile substitution and provide advantages towards the competition

from emerging voice technologies e.g. VoIP over xDSL.

For dual mode operators WB-AMR provides also service continuity between WCDMA

36

and GSM and enhances the probability to establish a WB-AMR call. Thus WB-AMR will

support the "2G network to complement 3G" strategy of the operator.


The Wide Band Adaptive Multi-Rate codec (AMR-WB) was developed by 3GPP

including 5 codec rates ranging from 6.6 to 23.85 kbps and including rate adaptation

mechanisms as in AMR.

Audio sampling rate of 16000 samples per second, linked with WB specific algorithms

enhances audio frequency band to 50 Hz - 7000Hz for WB-AMR, which is significant

increase compared to 300 Hz - 3400Hz frequency band for existing voice services e.g. in

G.711 or AMR. This new sampling rate restricts the use of WB codec to MS to MS calls.

According to listening tests further quality gains from higher WB codec modes than 12.65

are seen small, thus set of three codecs i.e. 6.6, 8.85 and 12.65 carried with GSM

modulated channel are to be supported by RG10(BSS).

Like in AMR, the codec mode can be chosen based on the radio conditions, yielding to

optimal audio performance through rate adaptation. The codec mode can be changed

every 40 ms in GSM. The codec also includes a source controlled rate adaptation

mechanism, which allows it to encode speech at a lower average rate by taking speech

inactivity into account.

WB-AMR requires end to end TFO (Tandem Free Operation) support, because down

sampling in transcoding would invalidate WB properties of sound. If TFO is not possible

transcoding to G.711 is used, and the G.711 restricts the audio frequency range to 300 -

3400 Hz. Indeed e.g. in inter PLMN WB-AMR calls it needs to be ensured that the

transport chain is transparent to carry TFO.

WB-AMR transcoding functions will be available in the NSN Media Gateway (MGW) with

Ater-support. Alternatively feature BSS21218 offers WB-AMR support for TCSM3i.

Figure: WB AMR makes voice warmer and makes the speaker appear closer

37

BTS HW: Edge MetroSite TRX is needed for this feature. UltraSite Edge Baseband unit

(BB2E or BB2F) is needed for this feature

MSS:

For this WB AMR feature (BSS20960): NSN Rel-4 Core. i.e. MSC Server with MGW.

For Rel 99 core networks please use the BSS21218 Wideband AMR support for TCSM3i

MS: WB-AMR capable MS required

Important logistical NOTE: This feature item (BSS20960) is valid for up to 100

simultaneous calls in total on one BSC and is being sold per TRX supporting it. The

additional item BSS21312 "Wideband AMR Capacity License" is required for additional

capacity in steps of 100 simultaneous calls per BSC up to max 16 steps per BSC. After

this limit the additional steps are FOC.

Dependency Table:

G.711

300-

3400

Hz

WB

AMR

50-

7000

Hz

Nuances

Presence

Warmth

38

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP3.2

EP5.1

- CX7.0 CXM7.0

EX3.1

BRG1

9-40

EP3.0 OSS5.1

CD

SET 2

- U4.2

M14.4

- Rel5

*) Quality based NB WB is not supported.

39

4.2 Wideband AMR support for TCSM3i


Summary: This feature adds Wideband AMR (WB-AMR) support for TCSM3i.

Benefits for the Operator: This feature provides the same general benefits as the

BSS20960 WB-AMR feature with the NSN MGW, and may additionally be used together

with other vendors standard compliant core networks with either Rel99 (e.g. NSN

CS5.0) or Rel4 architectures, as long as they support WB-AMR.

Additionally it protects investments to the new TCSM3i far into the future.

Functional Description: This feature provides WB-AMR by transcoder TCSM3i

connected to the GSM/EDGE core network via the standardized A-interface.

Figure:

BSC & TCSM HW: TCSM3i



40

MS: WB-AMR capable MS required

Important logistical NOTE: To allow faster rollout, this feature item (BSS21218) is

valid for up to 100 simultaneous calls in total on one BSC and is being sold per TRX

supporting it. The additional item BSS21312 "Wideband AMR Capacity License" is

required for additional capacity in steps of 100 simultaneous calls per BSC up to max 16

steps per BSC. After this limit the additional steps are FOC.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP3.2

EP5.1

- CX7.0 CXM7.0

EX3.1

BRG1

9-40

EP3.0 OSS5.1

CD

SET 2

- U4.2

M14.4

- Rel5

41

4.3 AMR HO Signaling Optimizations


Summary: This feature optimizes HO signaling for AMR in order to reduce the call drop

rate for intracell handovers. The number of intracell handovers may increase with the

utilization of HR.

Benefits for the Operator: CAPEX savings by reducing call drop rate for intracell

handovers.

Functional Description: FACCH channel used for signaling is less robust for poor radio

conditions than the most robust AMR codecs (i.e. AFS4.75) thereby limiting the coverage

and capacity gains that can be achieved with AMR. One way of increasing signaling

performance is to reduce the size of signaling messages in such a way that one L3

message fits e.g. into one L2 frame.

Possible redundant information, e.g. unnecessary frequency information elements, is

removed in intra-cell handovers. The speed to perform intra cell handovers or AMR

packing/unpacking is improved.

MS: AMR capable MS required

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE


Release RG10(BSS) S14 - - - - - - - - - - -

42

4.4 Tandem Free Operation (TFO) for AMR


Summary: This feature enhances the BSS support of TFO to also include AMR in

addition to the existing FR and EFR support. It applies to both the TCSM3i and the NSN

(ex-Nokia) Ater-in-MGW solution. Tandem Free Operation (TFO) is intended to avoid the

traditional double speech encoding/decoding (G.711 AMR) in MS to MS (2G) or MS

to UE (2G/3G), and thereby improving the voice quality and potentially reducing the

transport capacity need inside the core network.

Benefits for the Operator: CAPEX and OPEX savings by lowering bandwidth and costs

for core network links towards BSC

Operator can protect core network investments through common (Rel4) core network for

WCDMA and BSS. Operators can obtain substantial savings in Rel4 core network

transmission capacity e.g. 4 times more voice calls can be provided, if TrFO/TFO

Interworking is used between the core nodes.

Functional Description: TFO for AMR-FR and AMR-HR will be supported for calls that

are within the same network or to another GSM / UMTS network that supports TFO

version 6.3. With either AMR-FR or AMR-HR at the local end the TFO can be used with

a GSM AMR-FR, GSM AMR-HR or UMTS-AMR2 (narrowband AMR) call at the remote

end.

43

To ensure TFO compatible operation with best voice quality in all these cases the 3GPP

recommended AMR narrow band configuration is used, with fixed modes of 12.2, 7.4,

5.9, 4.75 kbit/s for AMR-FR and fixed modes of 7.4, 5.9, 4.75 kbit/s for AMR-HR.

Note: AMR-FR AMR-HR call in TFO keeps the AMR-FR radio channel, so that the

TFO is available while keeping the optimum radio channel setup at both ends of the call.

In this case the AMR-FR side is constrained to only use the 3 lower codec rates, which

matches the AMR-HR codec set.

If WB-AMR is also used in the network then the Immediate Codec Type optimization will

ensure that AMR-WB call with TFO is used if both ends of the call support the AMR-WB

operation.

The existing TFO for the GSM FR, EFR and HR codecs is still supported, as TFO

version 0.0 operation, so that if both ends of the call use the same (FR, EFR or HR)

codec then TFO is used. This TFO operation is a separate feature from the AMR TFO

operation and can be active in a network at the same time as AMR TFO operation, but

there is no TFO operation if one end (local or remote) of a call is using AMR and the

other end (remote or local) is using FR, EFR or HR codec.

44

TFO vs. TrFO:

Tandem Free Operation (TFO): call configuration where a transcoder device is physically

present in the signal path, but the transcoding functions are bypassed. TFO uses in-band

signaling for control. In-band TFO provides no direct saving of transmission costs, but

e.g. proprietary G.711 removal schemes may be used.

Transcoder Free Operation (TrFO): call configuration where no transcoder device is

physically present and hence no control or conversion or other functions associated with

it are activated. TrFO is currently specified only for WCDMA and not for GSM Radio and

is thus not applicable to RG10(BSS). TrFO uses out-of-band signaling for control. TrFO

provides direct transmission savings in core network.



MS: AMR capable MS required

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP5.1

- CX7.0 CXM7.0

EX3.1

BRG1

9-40

EP3.0 OSS5.1

CD

SET 2

- SR3.1

U4.2

M14.3

- X

45

4.5 A5/3 ciphering


Summary: A5/3 is a new, more secure; 3GPP standardized ciphering method and is

based on the same core algorithm as used in WCDMA. Ciphering is performed by the

BTS. BSC selects the ciphering algorithm based on the information received from the

MSC and the information about allowed and supported algorithms in the BSS and MS.

Benefits for the Operator: A5/3 gives the possibility to use more secure ciphering

method over radio interface.

Functional Description: A new, more secure ciphering method has been standardized

and is advised to take in use to replace the A5/1 algorithm. A5/3 is based on Kasumi F8

which is also used in WCDMA RAN.

Ciphering is performed by the BTS burst by burst. The BSC selects the ciphering

algorithm based on the information received from the MSC and the information about

allowed (and supported) algorithms in the BSS.

In the BTS, the A5/3 algorithm will be supported only by the EDGE BB of the TRX,

because in EDGE BB has enough DSP capacity for this feature. Therefore, the BSC

must check if the TRX is A5/3 capable before selecting the ciphering algorithm. BSC will

use the BB Unit Type parameter, which was added to the Abis O&M interface in S13.

Note: Current standardization sets a restriction for changing ciphering algorithm during

DTM reallocation. DTM Assignment Command message does not include Cipher Mode

Setting IE before 3GPP Rel-7 and that's why ciphering algorithm could not be changed

for Rel-6 MSs during reallocations between EDGE TRXs supporting A5/3 and GPRS

TRXs supporting A5/1. For Rel-6 MSs ciphering mode shall be changed with assignment

procedure, which means leaving the DTM mode for a while. A Rel-7 MS will indicate its

support for ciphering mode change during DTM assignment procedure.

BTS HW: Edge MetroSite TRX is needed for this feature

UltraSite Edge Baseband unit (BB2E or BB2F) is needed for this

46

Operational Aspects: In BTS SW the support for A5/3 is included in the same SW

package with A5/1.

MS: A5/3 capable MS required. For DTM Rel 7 MS is required with support for ciphering

mode change during DTM assignment.

Dependency Table:

BSS BSCS DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP5.1

- CX7.0 CXM7.0

EX3.1

BRG1

9-40

EP3.0 OSS5.1

CD

SET 2

- U4.1

M14.3

- X

47

4.6 SDCCH and PS Data Channels on DFCA TRX


Summary: The gains from the feature Dynamic Frequency and Channel Allocation

(DFCA) introduced in BSS11.5 can be fully exploited by also supporting the SDCCH and

GPRS/EDGE channels in the DFCA layer. No separate planning for additional non-

DFCA TRX is then required which saves frequency bands significantly.

Benefits for the Operator: CAPEX savings by improved data and radio network

performance; i.e. more capacity when DFCA gains to its full potential. SDCCH

capacity is no more limited to regular TRXs.

OPEX savings can be achieved due to no need for separate planning for additional non-

DFCA TRX.

Functional Description: The current DFCA feature can handle only Circuit Switched

(CS) traffic and thus Packet Switched (PS) layer and CS layer must be separated

(different TRXs). As PS traffic is increasing it often requires more than one TRX (BCCH)

which consumes frequencies from dynamic DFCA layer and decreases spectral

efficiency, and causes some extra needs for planning/management as well.

With this extension to the DFCA feature it will be possible to assign SDCCH and PS

traffic also to DFCA TRXs. Then it would be only BCCH TRX that remains out of DFCA's

reach. PS territory would upgrade and downgrade freely over TRXs without DFCA

related restrictions. Similarly, both static and dynamic SDCCH channels would be

possible in DFCA layer.

BTS HW: MetroSite EDGE TRX is needed for this feature.

UltraSite EDGE Baseband unit (BB2E or BB2F) is needed for this feature.

BSC HW Prerequisite: PCU2 is needed.

SW Prerequisite: DFCA feature (BSS11052) is needed.

Dependency Table:

48

BSS BSCS DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP5.1

- CX7.0 CXM7.0

EX3.1

MP2.0

N EP3.0 OSS5.1

CD

SET 2

- - - -

49

4.7 AMR Unpacking Optimization


Summary:

This feature provides new AMR quality and handover parameters to avoid useless

unpacking in intracell FR/HR handovers.


CAPEX savings and improved network quality by reducing drop call rate.


Optimal functionality of unpacking is very important for AMR. To further optimize

unpacking two new parameters are introduced in HO algorithm.

1. Lower RX level thresholds for quality based intra cell handovers

If RX level is below this threshold then AMR unpacking, packing and interference

handovers (the new type) are not allowed.

In case of rapid field strength drop, quality also typically drops. This easily triggers AMR

unpacking handovers. If the field drop is high enough quality goes such bad that the

mobile cannot possibly decode the handover assignment, thus the mobile cannot

perform HO. Normally radio link timeout timer controls the time how long the mobile can

be unreachable before the TCH is deactivated and the call is seen as a drop. This can

be e.g. 16 seconds. But when a handover is started is used a fixed 6 seconds timer to

control handover success. If the MS does not answered during this time either

successful or not successful handover, the BSC deactivates the target channel and also

the source channel. This is a drop. So without an intracell handover start the MS have

about 10 seconds more time to get out off bad coverage.

2. Lower quality threshold to prevent interference and AMR intracell handovers

If the quality is on that level or worse then intracell quality based HOs are not started.

Basically this is the same thing than the level limit but based on quality. When the MS

moves around a corner it can happen that it's own RX level is not changing but the

interferer gets rapidly a lot stronger. This can cause that the MS quality drops to e.g. 7th

level. In the 7th level can easily happen that the MS fails SACCH decoding and hence

cannot identify any handover assignment request. Consequences of this are then the

50

same as when a handovers is started in rapid field drop case.

The same filtering windows sizes are used for level and quality.

MSC: 3GPP Rel5 TS 48.008 compliancy required for information transfer from BSS/RAN

to RAN/BSS.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



CD

SET 2

- X - -

51

4.8 105km Extended Cell


Summary:

This feature enhances the Extended Cell function through extending the cell radius from

the existing maximum of 70 km to up to 105 km. It is supported by the BTS Base Station

and is for CS Services only.

BSS21270 105km Extended Cell for GPRS/EDGE complements this feature and

provides a similar capability for PS Services.


This feature allows operators to serve larger coverage areas from the BTS (such as

coastal or very sparsely populated regions).

Current Implementation:

With the existing BSS13 feature, support for Extended Cells up to a maximum radius of

70 km is provided.

For this implementation, an Extended Cell is served by two types of TRX (N-TRX and

E-TRX):

N-TRXs serve the Normal coverage area

E-TRXs serve the Extended coverage area

The N-TRXs provide coverage up to a maximum distance of 35 km from the BTS. The

position (and thus overlap) of the 35 km wide extended coverage area (served by the E-

TRXs) may be adjusted as required. Consequently, the outer limit of the extended

coverage area is between 35 km and 70 km from the BTS.

For an E-TRX, the timing of the receiver is delayed in relation to the transmitter so that

the TRX can serve the area beyond the normal cell range of 35 km. The receiver delay is

configured at the BTS according to the required cell radius extension. The maximum

delay introduced corresponds to a time of approximately 40% of a single timeslot. Note,

however, that from the transmission perspective there is no timing (or other) difference

between an N-TRX and E-TRX. The MS listens to the BCCH, which is provided by one

52

of the N-TRX in the cell, regardless of whether the MS is moving in the normal or

extended coverage area of an Extended Cell.


Feature BSS21277 builds upon the principles employed for the up to 70 km extended

cell ranges and provides support for reaches up to 105 km from the BTS. This is

achieved through delaying TRX reception (in relation to TRX transmission) of up to

approximately 80% of a single timeslot. Here, in addition to the N-TRX and E-TRX, the

Superextended TRX (or S-TRXs) is employed.

In an Extended Cell, the BTS observes and uses the Timing Advance (TA) parameter to

report the distance an MS has moved into a coverage area to the BSC.

The timeslots of an S-TRX are configured in the same way as those of an E-TRX. The

(up to) 80% reception delay introduced means that the S-TRX RACH (E-RACH) overlaps

only with timeslots 0 and 1 of the N-TRX on the same frequency and therefore the

existing N-TRX configuration does not need to be changed:

The E-RACH occupies TSL 0 of one S-TRX per extended cell. The timeslot

accommodating the E-RACH is tuned to the same frequency as the timeslot

accommodating the BCCH/RACH in order that it can receive access bursts

transmitted by an MS in the super extended coverage area. The Downlink direction of

the E-RACH timeslot is unused - The BCCH (of the N-TRX) serves all three coverage

areas.

It is preferable that TSL 1 of the E-RACH S-TRX is configured as SDCCH. For

the case of a TRX failure, the SDCCH would also be swapped across to the new TRX.

TSL 1 of the BCCH N-TRX is unused, since its reception overlaps with that of

the E-RACH timeslot on the same frequency.

The remaining six timeslots of the E-RACH S-TRX can be used for user traffic.

Only the BCCH BTS of an Extended Cell may accommodate E-TRX(s) and S-TRX(s).

As indicated above, in order to achieve continuous Extended Cell coverage and smooth

MS movement between coverage areas, all three TRXs (N-TRX; E-TRX and S-TRX)

must be configured into a Super Extended Cell. It is also very important that adjacent

areas of the Extended Cell overlap. This ensures:

That excessive switching between adjacent areas of an Extended Cell is alleviated

The MS can move between coverage areas without service interruption

53

Within a Super Extended Cell, it is possible to configure S-TRXs without E-TRXs,

however, there would then be a discontinuity between the normal and super extended

coverage areas since intra-cell handovers between the normal and super extended area

are not possible.

Triggering of intra-cell handovers between the different cell areas is based on the Timing

Advance (TA) reported by the BTS and the MAX/MIN parameters. An intra-cell handover

between the normal and super extended area is not possible since these two areas do

not overlap with one another.

External handovers (from 2G or from 3G) are performed either to the super extended

area or to the actual cell area where the mobile is located - if the Long Reach TSL

(FlexiEDGE BTS) feature is activated.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



MP3.0

EP5.1

- N N

EX4.1

N EP3.0

MP2.0

OSS5.1

CD

SET 2

- - - -

54

4.9 105km Extended Cell for GPRS/EDGE


Summary:

This feature enhances the Extended Cell function through extending the cell radius from

the existing maximum of 70 km to up to 105 km. It is supported by the Flexi EDGE BTS

Base Station and is for PS Services only.

BSS21277 105km Extended Cell (FlexiEDGE BTS) complements this feature and

provides a similar capability for CS Services.


This feature allows operators to serve larger coverage areas from the BTS (such as

coastal or very sparsely populated regions).


The PS timeslot (EGTCH) configuration rules for S-TRXs are the same as those for E-

TRXs. (E)GPRS channels (EGTCH) are manually configured for S-TRXs and constitute

a fixed EGTCH territory, which cannot be utilized for CS traffic. Also, the constituent

timeslots cannot be dynamically moved between the CS and PS territories.

During radio resource allocation, the PCU allocates resources to an MS to either an S-

TRX; E-TRX or N-TRX depending upon the MS location - the PCU has either already

stored the coverage area information of the MS or determines it through the access burst

received from the MS.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE

NetAct

SG

SN

MS

C

RA

N

MS


MP3.0

EP5.1

- N N

EX4.1

N EP3.0

MP2.0

OSS5.1

CD SET 2

- - - -

55

4.10 Enhanced Satellite Abis Support up to 420ms


Summary:

So far satellite services have caused ca. 300ms one-way delay to transmission paths

(used mainly in Abis). Due to the (transport) network technological evolution (Dynamic

BW allocation", "Optimized TDM via packets" and "Local Switching") the satellite

environment has changed and we might face delays up to 400ms.


Support of Satellite Abis links can be guaranteed, even with the extended delays caused

by the new transport network technologies.


Comprehensive tests have been carried out to verify that our BSS system can tolerate

up to 420ms delays on the Abis interfaces.

.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



MP3.0

- - - - N - - - - - -

56

4.11 Paging Coordination


Summary:

BSC performs Paging Coordination between PS and CS internally without DTM and Gs

interface (i.e. in NMO II). BSC forwards all CS paging messages to the PCUs; the PCU

which finds the MS (IMSI) in packet transfer state initiates the paging procedure to the

cells belonging to the paging area.


The subscribers will be pageable for CS calls also when connected in PS mode without

deploying NMO I and DTM support E2E and therefore without implementing Gs

interface.

The Paging Coordination implementation brings improved paging success rate

(reduction of lost pagings). Therefore it consequently offers to the operators the

possibility to achieve higher ARPU, less help desk calls, and reduced churn rate.

In comparison with the other alternative solution (Full DTM and Gs support) Paging

Coordination introduces CAPEX and OPEX savings.


Currently, in NMO II mode, the GPRS core network and the BSC do not provide CS

Paging coordination. Both the CS and PS paging requests are sent to the MS on CCCH

paging channel (PCH). This means that, if a DTM-capable MS is in packet transfer

mode, it does not necessarily monitor the PCH channel and, therefore, does not respond

to the CS paging.

Only in NMO I it is the core network that provides Paging Coordination so that CS paging

requests to GPRS-attached MSs are sent to the PCU via the SGSN. This requires Gs

interface between MSC and SGSN. The PCU then provides CS paging on the PACCH

channel if the MS is in packet transfer mode. If the MS is in packet idle mode, it is paged

for a CS call on the PCH channel.


57

With the Paging Coordination the MSC sends a CS paging request to the BSC which

then broadcasts the paging request further to the PCUs. When a PCU receives a CS

paging, the PCU examines whether it has a TBF for the given IMSI. If the PCU does not

have a TBF for that IMSI, then the PCU just ignores the CS paging request message.

Otherwise, it sends a PACKET PAGING REQUEST message to the MS on the PACCH

channel, if the MS is in packet transfer mode, and initiates a paging procedure on those

cells that belong to the given paging area (MCC + MNC + LAC + CI). The CS paging

request message contains the IMSI of the mobile.

If the MS is in packet idle mode and if there is a PCCCH in the cell, then the MS is CS

paged on PPCH. In other cases, the MS is paged on PCH.

BSC HW Prerequisite: PCU2 or PCU2E

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE

SGSN MSC RAN MS


EP3.2

- - - - - - - - - -

58

4.12 Extended CCCH


Summary:

This feature adds more radio time slots for the CCCH use e.g. in larger BTS

configurations or heavily loaded cells. Especially, increased use of PS services

introduces plenty of CCCH load per user.


This feature improves paging success rate and makes call establishments shorter,

especially in congested cells. Also network optimisation becomes leaner since other

dimensioning tasks e.g. LA/RA downsizing can be avoided.


Up to now only single CCCH channel could be supported.


Extended CCCH feature increases CCCH channel capacity in the cell up to four CCCH

timeslots in total. Extended CCCH channel allocated in time slots 2, 4 or 6 contains one

BCCH block and 9 CCCH blocks presented in figure 4.12.1.

Figure 4.12.1. TDMA frame mapping for FCCH + SCH + BCCH + CCCH/9

MS: The handset must be capable of allocating up to 4 TS for CCCH.

BSC HW Prerequisite: PCU2 is required if the extended CCCH channel is used with

GPRS/EDGE in the same segment.

59

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP3.2

EP5.1

- CX7.0

MP3.0

CXM7.0

MP3.0

EX3.1

MP1.0

BRG1

9-40

EP3.0

MP3.0

OSS

5.2

CD

set 1

- - - X

60

4.13 Extended BCCH


Summary:

TD-SCDMA GSM IW leads to long SI messages which have to be split up into several

messages. Thus the UE needs more time to read them; and that means more time for

HO and Update. To reduce the time to read such long SI messages on the GSM side

this feature brings more space for SI by increasing BCCH subchannels from one to two.


Extended BCCH feature reduces time of handovers and update by reducing amount of

individual SI 2 quater messages.


Up to now only one BCCH subchannel was available.


With the Extended CCCH feature operator can define new BCCH channel to the time

slot 0. This new BCCH channel type contains of BCCH block, extended BCCH block and

8 not combined CCCH blocks. Following picture presents TDMA frame mapping for the

new CCCH channel. Only SI2quater system info messages are sent on 2nd BCCH

subchannel. SI2quater sending is moved from normal to extended BCCH subchannel..

Figure 4.13.1. TDMA frame mapping for FCCH + SCH + BCCH/2 + CCCH/11

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE

NetAct

SG

SN

MS

C

RA

N

MS


EP5.1

- CX7.0

MP3.0

CXM7.0

MP3.0

EX3.1

MP1.0

BRG1

9-40

EP3.0

MP3.0

OSS 5.2

CD set 2

- - - -

61

4.14 Priority Based Voice Quality


Summary:

HR or AMR HR can be allocated for lower tariff users.


Operator may provide voice quality per subscription e.g. for providing flat rate voice tariff

while quality for normal tariff is not compromised.


Up to know the conditional allocation of HR was based on load situation or service type

only. With this feature also the priority of the subscriber will be considered.


BSC allocates, independently of network load, HR or AMR HR for users indicating pre-

emption vulnearibility (PVI=Y).

Unpacking of AMR HR to AMR FR can either be prevented, allowed normally or allowed

when packing load threshold is not yet exceeded. This can be controlled with UTPFIL

parameter.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP5.1

- CX7.0

MP3.0

CXM7.0

MP3.0

EX3.1 BRG1

9-40

EP3.0

MP3.0

N - - - -

62

4.15 Merged P- & E-GSM900


Summary:

A number of P-GSM / E-GSM feature enhancements have already been provided in

earlier software releases. This feature complements these through combining the P-

GSM and E-GSM frequency bands into one and removing the specific handling

previously required for P-GSM only handsets.


This new feature introduces an improved spectral efficiency through the merging of the

P-GSM and E-GSM Bands. Furthermore, the general operability of the network is

improved and simplified.


Originally, PGSM900 and EGSM900 resources were managed separately and

configured as separate cells within the BSC, with handover support between them. Over

later software releases (BSS11.5, BSS12 and BSS13) a number of enhancements were

realised in order to increase the integration of the two frequency bands.

In former releases, PGSM900 and EGSM900 frequencies can be used within a single

BTS object and support for PGSM-only handsets has been maintained. However, in

cases where the BCCH carrier of a PGSM900-EGSM900 BTS is on the PGSM900

frequency band there are currently operational aspects that must be considered, which

would be unnecessary if all GSM900 handsets in the network also supported the

EGSM900 band.

These operational aspects are:

It is possible to combine PGSM900 and EGSM900 frequencies only in the BCCH

BTS and with such a BCCH BTS it is not possible to employ GSM900 frequencies in

any other BTS object of the segment

It is not possible to use RF Hopping and (E)GPRS on the same TRX

Baseband Hopping cannot be employed

It is not possible to use super reuse TRXs

DFCA Hopping cannot be employed

Static SDCCH resources must be configured for the PGSM900 TRXs

63

The BSC limits the dynamic reconfiguration of SDCCHs to be within the PGSM900

TRXs

The BSC limits the actions of FACCH setup to be within the PGSM900 TRXs

The feature High Speed Circuit Switched Data is not supported

It would no longer be necessary to consider these if it can be assumed that all GSM900

handsets in the network support EGSM900. This is the basis for this feature, Merged

PGSM900 and EGSM900, which complements the existing PGSM900-EGSM900 feature

enhancements, combining the two frequency bands into one and removing the specific

handling previously required for PGSM-only handsets. The feature then eliminates the

above operational aspects.

Note that generically for GSM systems, the maximum number of available GSM900

frequencies in a PGSM900-EGSM900 segment is 16 (17 if ARFCN 0 is included).

This feature represents the final step in a series of enhancements that have been

introduced.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP5.1

- CX7.0

MP2.0

CXM7.0

MP2.0

EX3.1 BRG1

9-40

EP3.0

MP2.0

tbd - - - -

64

4.16 Higher Average Power per TRX in Flexi Multiradio


Summary:

This feature increases the GSM coverage while retaining capacity in Flexi Multiradio

BTS.


With this new feature we will increase the MCPA capacity to 4TRXs with average 20W

per TRX (also upto 6/6/6@15W per TRX as compared to 4/4/4). This would mean:

- Higher capacity within retained coverage without adding the new hardware

- Coverage enhancement: More distant and weak CS and PS connections served.

- Opex and Capex savings to the operator

- Reduced power consumption.


This is the first step towards Dynamic Power Sharing, which enables unused power from

different TRXs to be used dynamically between other TRXs of the same cell. While

BCCH power is permanently allocated, the remaining MCPA power is dynamically

allocated for TCH carriers. In case there is a temporary demand for high TX power on all

TCH carriers, TX power compression is done in the BTS. When there is an increase in

the number of defined carriers, maximum operation per carrier is not reduced and

therefore, the cell coverage remains unchanged.

65

Figure 4.16 Impact on cell range due to dynamic power sharing

With this feature, a sector can have large coverage and/or capacity. In rural or in distant

adjacent sectors, this can cover the silent spots and weigh the traffic differently across

adjacent sectors resulting with HO/mobility parameters re-planning, to provide a fully

optimized network area.

The feature is supported for RF Modules and can be activated from the SCF. Dynamic

power sharing is supported for the following configurations:

Table 4.16 : Configurations supporting Dynamic Power Sharing.

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP5.1

- N N EX3.1

MP1

N N OSS5.2

CD

SET 2

- - - -

66

4.17 Instant QoS Signaling


Summary:

BSS provides quick QoS downgrade mechanism e.g. for specific instant messaging

protocol according to service type signalling from SGSN.


Enhanced capacity utilization when Smart Phones are being used.


Ineffieciency on radio resources

Instant Messaging services have become popular. E.g. QQ may have over half a billion

subscriptions in China. IM Protocols are not optimized for cellular use. For example

regular precedence updates for all the friends in list may cause high load even without

end user activity. Messages are typically short (around 100B), and with pair of message

poll and response is found a typical behavior. Indeed a friend may be polled every 100s,

thus multiple friends may directly multiply polling rate.

BSS reserves always maximum number of timeslots and that may cause TBF blocking.

Functionalities:

Detection of instant messaging service in GGSN based on server addresses and

ports numbers.

Signalling of service information to SGSN in GTP U plane

Signalling to BSS in BSSGP e.g. in new information element

Reducion of scheduling priority in PCU

Reduction of timeslot allocation in PCU

Functionality is built on top of priority based scheduling, where lowest priority is

used for QQ LLC PDUs.

Maximum number of allocated time slots is set to 1 according to new IE

Coexistense with Smart Phone Capacity

67

If this feature is activated with Smart Phone capacity feature, reduced timeslot allocation

of is used when either packet is short or qq service

Dependency Table:

BSS BSC DX200

Platform

BTS

Ultra

Site

BTS

Metro

Site

BTS

Flexi

MultiR

BTSplus BTS

Flexi

EDGE



EP9.1

- - - - - - - - - - -

68

4.18 Disable Internal Handover


Summary:

The configuration s

Date post:	07-Oct-2015
Category:	Documents
Upload:	sourabh-ohri
View:	93 times
Download:	5 times

225754744 NSN RG10 New Features and Features Under Development

Documents