11_BSS12 New Features

8/12/2019 11_BSS12 New Features

http://slidepdf.com/reader/full/11bss12-new-features 1/74

Confidential © Nokia Siemens Networks 1 (74)

DN0745995

BSS12

New FeaturesVersion 4.4.0




DN0745995

The information in this document is subject to change without notice and describes only the productdefined in the introduction of this documentation. This document is not an official customer documentand 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 ofthe 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 NokiaSiemens Networks. The documentation has been prepared to be used by professional and properlytrained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networkswelcomes customer comments as part of the process of continuous development and improvement ofthe documentation.

The information or statements given in this documentation concerning the suitability, capacity orperformance of the mentioned hardware or software products are given “as is” and all liability arising inconnection with such hardware or software products shall be defined conclusively and finally in aseparate agreement between Nokia Siemens Networks and the customer.

IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATIONOR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, that mightarise 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 ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, ARE MADE IN RELATION TOTHE ACCURACY, RELIABILITY OR CONTENTS OF THIS DOCUMENT. NOKIA SIEMENSNETWORKS RESERVES THE RIGHT TO REVISE THIS DOCUMENT OR WITHDRAW IT AT ANYTIME WITHOUT PRIOR NOTICE.

This document and the product it describes are considered protected by copyrights and other intellectualproperty rights according to the applicable laws.

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

Other product names mentioned in this document may be trademarks of their respective owners, andthey are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.




DN0745995

BSS12 New Features - Table of Contents:

1 Introduction ........................... .............................. ............................. .............................. ................ 4 2 BASE STATION CONTROLLER ........................... ............................. .............................. ............. 8

2.1 Supported BSC/TCSM Product Variants.............................. .............................. ..................... 8 2.2 CPU Memory Requirements for the Basic S12 SW Release ........................... ....................... 8 2.3 PCU Requirements for the Basic S12 SW Release ............................. .............................. ..... 9 2.4 O&M Link (Q3 interface between BSC and NetAct) capacity........................... ....................... 9 2.5 BSC3i 1000 / 2000 .......................... ............................. .............................. ........................... 10 2.6 TCSM3i........................... .............................. ............................. .............................. .............. 12 2.7 SIGTRAN over A Interface ............................. .............................. ............................. ............ 14

3 BASE STATIONs ............................. .............................. ............................. .............................. ... 16 3.1 FlexiEDGE TRX HW Activation License............................... ............................. .................... 16 3.2 FlexiEDGE MHA Support .......................... .............................. ............................. ................. 17 3.3 Nokia UltraSite EDGE BTS Mini........................... .............................. ............................. ...... 17 3.4 Nokia Pico GSM/EDGE BTS ........................... ............................. .............................. ........... 18 3.5 LMUB alarm in BSC: Position not locked (8272).............. ............................. ........................ 19

4 PACKET SWITCHED DATA............................ .............................. ............................. ................. 20 4.1 Dual Transfer Mode DTM .......................... .............................. ............................. ................. 20 4.2 High Multislot Classes .......................... .............................. ............................. ...................... 25 4.3 Extended Dynamic Allocation........... ............................. .............................. .......................... 28

5 RADIO NETWORK PERFORMANCE ............................. .............................. ............................. . 31 5.1 Support for Single Antenna Interference Cancellation ......................... .............................. ... 31 5.2 Space Time Interference Rejection Combining (STIRC)............................ ........................... 33 5.3 Multipoint A interface ............................ ............................. .............................. ...................... 35 5.4 DL DTX Audio Quality .......................... .............................. ............................. ...................... 38 5.5 Maximum MS TX Power During E911 location .......................... ............................. .............. 39 5.6 Increased Dynamic SDCCH capacity.............................. ............................. ......................... 40 5.7 Load based AMR Packing .......................... .............................. ............................. ................ 41 5.8 Single MA list for EGSM and PGSM .......................... ............................. .............................. 42 5.9 DFCA RRM Power Reduction .............................. ............................. .............................. ...... 44 5.10 Radio Link Timeout parameter for AMR HR ........................... ............................. .............. 46 5.11 Intelligent Selective Paging...... .............................. ............................. .............................. . 47

6 OPERABILITY........................................... .............................. ............................. ........................ 49 6.1 File Based Plan Provisioning................. ............................. .............................. ..................... 49 6.2 File Based Configuration Upload....... ............................. .............................. ......................... 52 6.3 CS Statistics Enhancements ........................... ............................. .............................. ........... 53

6.4 MEFICO (Monitoring Tool for BSC)........................... .............................. ............................. . 53 6.5 Missing NSEI Alarm......................... ............................. .............................. ........................... 54 6.6 24 TRX per BCF for Flexi EDGE BTS ............................. ............................. ......................... 55 6.7 New Counters for Handover Measurement .......................... .............................. ................... 56 6.8 Statistics for SIGTRAN .............................. .............................. ............................. ................. 58 6.9 Flexi EDGE Dual TRX Manual Power Down ............................. .............................. .............. 60 6.10 Multipoint A Load Balancing ............................. ............................. .............................. ...... 61 6.11 FOXMEA support for macros and print all counters .......................... ............................. ... 63

7 VALUE ADDED SERVICES....................................... .............................. ............................. ....... 64 7.1 BSC integrated SMLC capacity ............................ ............................. .............................. ...... 64

8 Transmission & Transport........................... ............................. .............................. ...................... 66 8.1 FlexiEDGE Abis TRS Grooming........ ............................. .............................. ......................... 66

8.2 FlexiEDGE TRS Loop Protection ......................... .............................. ............................. ...... 67 8.3 FlexiEDGE Additional 2 E1, T1 IF .............................. ............................. .............................. 69




DN0745995

9 MULTIRADIO INTERWORKING.......................................... .............................. .......................... 70 9.1 TD-SCDMA interworking, idle mode..................... .............................. ............................. ...... 70 9.2 TD-SCDMA incoming HO support............................. .............................. ............................. . 70




DN0745995

1 INTRODUCTION

This document describes the new functionality provided by the BSS system releaseBSS12.

Nokia BSS12 software consists of Operating Software (OSW) and ApplicationSoftware (ASW). Operating Software means software that includes the basicfunctionalities and enhancements. Application Software means the software thatconsists of value-adding functionalities.

BSS12 Operator Value

BSC & TCSM Solution: BSS12 release is introducing new High Capacity BSC3i 2000and TCSM3i GSM/EDGE BSS products. Increased capacity is an enabler for cuttingcosts. BSC3i 1000/2000 is compact in size with one cabinet 1000 TRXs and with twocabinets 2000 TRXs. Built in SDH/SONET connectivity is now available for easycommissioning to support fast roll-outs. TCSM3i has very high capacity with over 11000 traffic channels in one cabinet. SDH/SONET connectivity is also available with thecombined BSC3i/TCSM3i installation.

BTS Solution: BSS12 supports new innovative Nokia Flexi EDGE BTS. Nokia FlexiEDGE BTS is a part of all purpose modular site optimized Flexi BTS platform. In FlexiBTS platform microcells, macrocells and multi mode solutions can be supported withthe same 19" Flexi modules. Nokia Flexi BTS platform minimizes the cost of network

deployment and operation; makes possible of re-using existing network assets andensures future technology evolution.

Radio Network Performance : In BSS12 release the Performance area is introducingnew features to mitigate the impact of interference in radio networks. This increasesthe spectral efficiency in terms of Erlangs per MHz and improves voice qualityexperienced by users. In addition BSS12 gives possibity to connect one BSC toseveral MSC servers and thus improves scalability and availability.

Operability: In BSS12 the configuration management between BSC and NetAct ischanged. Configuration changes between NetAct and BSC are done plan basis, whichgives end user performance gain in these mass parameter change operations. There

is also new CS statistics brought in to BSC.

Packet Switched Data: BSS12 Data area is introducing new functionalities that bringDual Transfer to expand data services continuity network wide, thus giving increasedend user experience by bringing better usability. In addition, Packet Switched Dataarea brings increase to bitrates and data throughput values that benefits the usage ofnew mobile services and applications.

End User Services: BSS12 release contains performance improvements to Locationservices. The performance and calculation capacity of BSC integrated SMLC (servingmobile location centre) is increased. No additional network elements needed.




DN0745995

The BSS12 system features will be available in the following network elementreleases: BSC S12, UltraSite CX5.0, MetroSite CXM5.0 and FlexiEDGE EP1.0.

The compatibilities for individual NE releases are as follows:

o BSS12 consists of the releases: BSC S12, UltraSite and MetroSite CX(M)5.0,FlexiEDGE EP1.0

o BSS12 is supported by following NE releases: NetAct OSS4.1 CD Set 1, MSCM12 & M13, SGSN SG5 & SG6

S12 BSC is compatible with OSS4.0 CD Set 3 only in the S11.5 level functionalities

and performances. To utilise S12 level functionalities and performances, OSS4.1 CDSet 1 or later is mandatory requirement.

This document also includes the hardware requirements and the planned systemcompatibility information of the features. The different BTS generations (Nokia 2ndgeneration, Talk-Family, PrimeSite, MetroSite, UltraSite, FlexiEDGE and InSite BaseStations) are mentioned so that any exceptations are highlighted. If no exceptions arementioned, the feature applies to all four BTS generations.

The introduction of new BSC S12 software release will terminate the usability of BSCE,TCSME, BSC2E and BSC2A products. BSC SW release S11.5 will be the lastcompatible software level for these old BSC and TCSM product models. Please see

more details in BSC Technical Note 796 publication date on 10th of May 2004.The standardisation baseline of BSS12 release is 3GPP Release 5.




BSS12 Compatibility Matrix

OSS4 OSS4.1Release S11 S11.5 S12 B13.1 DF7.0 I3.0 CX4.0 CX4.1 CX5.0 CXM4.0 CXM4.1 CXM5.0 EP1.0 LMU4.4 LMU-B 1.0 CDset3 CDset1 NML3.1S12CXM5.0CX5.0EP1.0OSS4.1

Release M12 M13 SG4 SG5 SG5.1 SG6 U2 U3A U3B U3C RN2.0 RN2.1 RN2.2 RN3S12CXM5.0CX5.0

EP1.0OSS4.1

The meaning of the colors in the compatibility matrix:

Compatibi li ty not applicableCompatibi li ty not support edSecondary compatibil it yPrimary compatibi li ty

For further BSS12 Information, see S12 Compatibility Report in Nokia BSC ReleaseDocumentation

BSS12 does not include a software release for 2 nd generation or Talk Family base stations.The basic BSC S12 software release is compatible with 2 nd generation B13 and Talk FamilyDF7 base station software release. Specific BSS12 feature support for 2 nd generation andTalk Family base stations can be found in the relevant feature specific dependency table.

DN0745995




DN0745995

Notations Used in Dependency Tables

The table below is used to relate the described BSS features to required system components:SUPPORTED IN:

GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC SGSN

NetActPlanner

Nokia 2 nd

Gen.Nokia

Talk-familyNokia

PrimeSiteNokia

MetroSiteNokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

HW/FW DEPENDENCY: BSS SOFTWARE:BSCMMI

BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW

Operating/ Application

In the table we use the following notations:SUPPORTED IN:

GSM800

This feature is supported in the GSM EDGE 800MHz system (Y= yes, N= no). Nokia

MetroSiteThis feature is supported by Nokia MetroSite (Y=yes, N= no). (Y) in parentheses indicates thatthe BTS is not actually applicable with thisfeature.

GSM900

This feature is supported in the GSM EDGE 900MHz system (Y= yes, N= no).

NokiaInSite

This feature is supported by Nokia InSite (Y=yes, N= no). (Y) in parentheses indicates thatthe BTS is not actually applicable with thisfeature.

GSM1800


NokiaUltraSite

This feature is supported by Nokia UltraSite (Y=yes, N= no). (Y) in parentheses indicates thatthe BTS is not actually applicable with thisfeature.

GSM1900


NokiaFlexiEDGE

This feature is supported by Nokia FlexiEDGE(Y= yes, N= no). (Y) in parentheses indicatesthat the BTS is not actually applicable with this

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

Nokia MSC release/feature nbr., N= no, - = notapplicable).

BSC MMI This feature has parameters that are managedwith the BSC MMI (Y= yes, - = not applicable).

NokiaNetAct

This feature is supported in the Nokia NetAct (Y=yes, xxx = Nokia NetAct release/feature nbr., - =not applicable).

BTS MMI This feature has parameters that are managedwith the BTS MMI (Y= yes, - = not applicable).

BSC This feature is supported by the BSC (Y= yes, N=no). (Y) in parentheses indicates that the BSC isnot actually applicable with this feature.

MS The feature sets special requirements to mobilestations (Y = yes, see the note; - = norequirements).

SGSN This feature is supported by the SGSN (Y= yes,N= no). (Y) in parentheses indicates that theSGSN is not actually applicable with this feature. HW/FW DEPENDENCY:

NetAct

Planner

This feature is supported in NetAct Planner, (Y=yes, xxx = NetAct Planner Version nbr., - = notapplicable).

BSC

HW/FW

This feature requires additional or alternativeBSCS hardware or firmware (Y= additional, A=alternative, or - = not applicable).

Nokia 2ndGen.

This feature is supported by the 2nd gen. BTS (Y=yes, N= no). (Y) in parentheses indicates that theBTS is not actually applicable with this feature.

BTSHW/FW

This feature requires additional or alternativeBTS hardware or firmware (Y= additional, A=alternative, or - = not applicable).

NokiaTalk-family

This feature is supported by Nokia Talk-family ofbase stations (Y= yes, N= no). (Y) in parenthesesindicates that the BTS is not actually applicablewith this feature.

TC HW/FW This feature requires additional or alternativetranscoder hardware or firmware (Y= additional,

A= alternative, or - = not applicable).

NokiaPrimeSite

This feature is supported by Nokia PrimeSite (Y=yes, N= no). (Y) in parentheses indicates that theBTS is not actually applicable with this feature.

SGSNHW/FW

This feature requires additional or alternativeSGSN hardware or firmware (Y= additional, A=alternative, or - = not applicable).


BSS SOFTWARE:

Indicates whether this feature is an Operating or Application SW feature (Operating = Standard, Application = Optional).




DN0745995

2 BASE STATION CONTROLLER

2.1 Supported BSC/TCSM Product Variants

In S12 release the supported Nokia BSC product variants are BSC3i, BSC2i and BSCiproducts. Similarly supported Nokia Transcoder Submultiplexer product variants areTCSM3i and TCSM2. Old BSCE, BSC2 and TSCME products are not supported any morewith S12 software release.

For further information of old BSC/TCSM products please see also the following TechnicalNotes:

• BSC TN 531: Availability of Nokia BSCE and TCSME Equipment,

• BSC HW TN 87: Availability of Nokia BSC2E and BSC2A Equipment

• BSC SW TN 796: SW Support for Nokia BSCE, TCSME, BSC2E and BSC2AProducts.

Extensions for BSC2i as well as the upgrades from BSCE/BSC2 to BSCi/BSC2i are notanymore available for the ordering. The last orders were handled on 30.03.2006 and lastdeliveries were sent on 30.07.2006.

2.2 CPU Memory Requirements for the Basic S12 SW Release

In S12 release MCMU and OMU computer units in BSC need at least 512 Mbytes memory.

Similarly in BCSUs the minimum memory amount is 512 Mbytes. Memory configurations inBSC CPU units needs to be extended up to minimum required level in BSCi, BSC2i andBSC3i. These minimum HW requirements are confirmed in a BSC HW Technical Note 154.

Memory extension can be installed flexibly to BSCs before S12 SW releaseimplementation. Memory configuration in CP6LX and CP6MX processor units used inBSCi/2i can be extended using MS256M memory modules. Memory configuration inCP710-A processor units used in BSC3i can be extended with MR256M memory modules.

Required memory amount per computer unit will be the following:

Computer

unit

S11.5

Memory amount,Mbytes

S12

Memory amount,MbytesOMU 256 512

MCMU 256 512BCSU 128 512

Table 3: Memory Requirements.



2.3 PCU Requirements for the Basic S12 SW Release

In S12 release all existing PCU HW variants are still supported with basic S12 SW.

Second generation PCU for BSC3i, includes two logical PCUsPCU2 - D

Second generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU2 - U Nokia SecondGenerationPacket ControlUnit - PCU2

First generation PCU for BSC3i, includes two logical PCUsPCU - B

First generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU - T

First generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU - S

First generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU Nokia FirstGenerationPacket ControlUnit - PCU1

ExplanationPCU variant nameGeneral name

Packet Control Unit, a general term for all Nokia GSM/EDGE PCU v ersions PCU

Second generation PCU for BSC3i, includes two logical PCUsPCU2 - D

Second generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU2 - U Nokia SecondGenerationPacket ControlUnit - PCU2

First generation PCU for BSC3i, includes two logical PCUsPCU - B

First generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU - T

First generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU - S

First generation PCU for BSCE, BSC2E/A, BSCi and BSC2iPCU Nokia FirstGenerationPacket ControlUnit - PCU1

ExplanationGeneral name

Packet Control Unit, a general term for all Nokia GSM/EDGE PCU versions PCU

Table 4: PCU requirements.

New application SW products Dual Transfer Mode (DTM), Extended Dynamic Allocation(EDA) and High Multislot Classes (HMC) require second generation PCU2 HW.

2.4 O&M Link (Q3 interface between BSC and NetAct) capacity

In most cases the current 128 kbit/s O&M link capacity requirement is not any morefeasible. As BSC releases have introduced more features and an increased amount ofobjects and measurements, more link capacity will be needed. Additionally BSC3i with1000/2000 TRXs sets higher requirements to O&M link capacity. IP connection is the mostpowerful alternative and also digital X.25 connection is seen feasible when using multiple64 kbit/s timeslots whereas analog X.25 connection has limited capacity. Therefore analogX.25 connection is not anymore available with BSC3i 1000/2000 configuration.

Tentative O&M bandwidth requirements for BSC S12:

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

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

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

Please note that figures presented here are still calculated estimates that have not beentested in live usage, so some changes may still be possible. Please also note thatdeviations to the figures might exist due to the implications caused by amount of managedobjects under BSC, activated features, customer specific data collection settings, workprocesses etc.


DN0745995



2.5 BSC3i 1000 / 2000

Feature ID: BSS20118

Description: BSC3i 1000/2000 is a further development in bringing higher capacity toNokia GSM/EDGE BSCs. Nokia BSC3i with 660TRXs was introduced in S10.5 release in2002. Now Nokia is introducing the next steps in BSC3i capacity evolution path byincreasing the TRX capacity of the BSC up to 1000 (in one cabinet) / 2000 TRXs (in twocabinets) in S12 release.

Figure 1: BSC3i 2000 with Optional Cabling Cabinet.

Providing three times the circuit switched capacity and four times the PS capacity of itspredecessor, the BSC3i 2000 has the capacity to meet even the most demandingrequirements. Based on the latest Intel processors, the Nokia BSC3i 2000 challenges anyother BSC on the market for CS capacity and outperforms any other for PS handlingcapacity. In fact, the PS traffic handling capacity is so large that there is no practical limit,avoiding the need for operators to buy new BSCs as business grows.

The vastly increased capacity means the network needs correspondingly less equipment,cutting OPEX typically by 50%. Compact size reduces site space costs while easy to

connect interfaces also speeds installation, cutting IMPEX. Furthermore new integratedSTM-1/OC-3 interfaces units are developed for BSC3i 1000/2000 configurations to ensureflexibility and ease of installation for external transmission connectivity.


DN0745995




DN0745995

The modular structure of the Nokia BSC3i 1000/2000 means flexibility in extending capacityin predefined modules of 200 TRXs and with the help of Operating SW licence keys. Allexisting BSC3i 660 configurations can optionally be upgraded to latest BSC3i 1000/2000

configuration. Upgrades are available at the same time with new deliveries of BSC3i1000/2000.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC SGS

N

NetActPlanner

Nokia 2ndGen.

NokiaTalk-family

NokiaPrimeSite MetroSite

Nokia NokiaInSite

NokiaUltraSite

NokiaFlexi

EDGEY Y Y Y - OSS4.1

CD set 11)

S121)

- - (Y) (Y) (Y) (Y) (Y) (Y) (Y)

HW/FW DEPENDENCY: BSS SOFTWARE:BSCSMMI

BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW

OPERATING/ APPLICATION

Y - - Y - - - Operating

NOTE: 1) Analogue X.25 O&M link from BSC3i 1000/2000 to NetAct not supported, LAN (Ethernet) connection recommended.



2.6 TCSM3i


Description: New Nokia TCSM3i high capacity transcoder submultiplexer is introduced inS12 release. New implementation shall provide up to twelve times more transcodingchannel capacity compared to earlier TCSM2, while maintaining the same compact size. Itcan also be easily expanded to meet future capacity needs. This capacity has beenarranged to provide 11,520 channels for ETSI, and 9,120 channels for ANSI and has beenachieved using the latest DSP (Digital Signal Processor) technology.

Enhancements have been done also on pool management side to minimise configurationwork over time. Known as all-in-one circuit pool, the new method allows one pool to supportall the different codecs saving the time and cost of having to reconfigure for differentcodecs as the traffic pattern changes with time.

As with the new BSC3i 2000, the higher capacity TCSM3i cuts OPEX because lessequipment is needed. Its compact size also reduces site space costs, while its easy toconnect interfaces speed up installation, cutting IMPEX.

Twelve times more capacity with fewer transcoder cabinets gives operators a greatopportunity to cut O&M costs to the bare minimum. Cost savings can be made across theoperation, in technical staff, spare part kits, energy consumption and site rentals.

Figure 2: TCSM3i.

Optical (STM-1/OC-3) interfaces can be introduced towards A Interface with an alternativeTCSM3i configuration option called "Nokia TCSM3i for combined BSC3i/TCSM3iinstallation". In this configuration BSC3i 1000/2000 and TCSM3i are installed together andmaintenance of optical connections is done by BSC. Optical connectivity is achieved byordering a basic set of hardware and additional STM-1/OC-3 Exchange Terminals.


DN0745995



2.7 SIGTRAN over A Interface


Description: SIGTRAN is a standardised way to carry SS7 signaling over an IP backbone.Originally SIGTRAN was designed for PSTN signaling transport for trunking purposes, butcan be used on any interface where SS7 signalling is used. Same IP backbone can beused for all kind of traffic (management, user and control planes). IP based transmissionprovides cost savings compared to TDM infrastructure. It also allows flexible capacityallocation which is not tied to a fixed bandwidth like 64 kbit/s or 2Mbit/s. SIGTRAN can beconfigured with state-of-the-art relisience functionality like SCTP multihoming together withheartbeat mechanism. Usage of redundant routes and duplicated backbone elementsprovide the basis for resilience for QoS-aware IP network. Signalling is assigned to highpriority class for IP routers and enough transmission capacity must be ensured for this highpriority class in IP backbone. Paraller usage with old SS7 transport network provides extra

resilience for transfer period . Application SW - Sales Item BSC.1470.

IPbackbone

NE NE

NE NESS7 links

A-interface change when

Benefits for the Operator:

CAPEX savings with easy scalability of the signaling network capacity. IP basedtransmission provides cost savings compared to TDM infrastructure. It also allows flexiblecapacity allocation which is not tied to a fixed bandwidth

Simplifies signalling network planning and configuration:

• SIGTRAN is decoupled from the physical transmission medium


DN0745995




DN0745995

• Same signaling transport used throughout the network corethus making planning procedures more uniform

IP connectivity:• Cost savings due to common IP backbone

• Same IP backbone for all kind of traffic

• Cost savings in IP based transmission compared to TDM infrastructure

Flexible capacity allocation:

• Signaling link capacity not tied to a fixed bandwidth (64 kbit/s or 2Mbit/s)

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC SGS

N

NetActPlanner

Nokia 2ndGen.

NokiaTalk-family

NokiaPrimeSite MetroSite

Nokia NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y M13 - S12ED1.1

1)

- - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCSHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - Y 2) - - - Application

NOTE: 1) SIGTRAN in combination with Multipoint A Interface is supported with the release BSS12 ED1.1.2) In BSCi and BSC2i IP cabling and CPLAN panels as well as site LAN switches and/or routers are mandatory HW

requirements.




DN0745995

3 BASE STATIONS

3.1 FlexiEDGE TRX HW Activation License


Description: The new Flexi EDGE BTS is a modular GSM/EDGE base station based onthe new Nokia Flexi BTS platform

• Flexi EDGE BTS is scalable from 1TRX to 24 TRX in a volume of a traditionalmacro BTS cabinet (12 TRX supported in S12)

• Ethernet based signaling between modules instead of backplanes

• Same weather-proof modules for all site types

• Indoors and outdoors, macro- and microcellular

• Can be installed on walls, poles or floors without cabinets or in 19”racks andcabinets

• Industry leading radio performance:

o Output power 47 dBm, sensitivity –115.5 dBm

o 2-way diversity, interference rejection combining

o All possible dual band configurations supported: GSM 800/1800, GSM

800/1900, GSM 900/1800

Application SW - Sales Item BSC00144 (usage of Flexi EDGE BTS).


• Lower radio network CAPEX & OPEX

• Easier site acquisition and space utilization

• Effective co-existence of GSM/EDGE and other radio technologies

Operational Aspects: The usage of Flexi EDGE BTS is controlled with a capacity licence.The licence sets a limit for unlocked Flexi EDGE BTS TRX count. If the Flexi EDGE BTSTRX licence doesn’t exist or feature state is OFF then Flexi EDGE BTS specific optionsare not shown to the user in MML commands

Nokia Flexi EDGE BTS 1st SW release EP1.0 will secure the functionality on the level ofNokia UltraSite EDGE BTS in operating features. EP1.0 provides the same BCF capacity,number of sectors and number of TRX per site as Nokia UltraSite EDGE BTS supports

EP1.0 will not include features for “extreme” coverage building in sparsely populated areas.



3.2 FlexiEDGE MHA Support


Description: Integrated functionality in Flexi EDGE BTS to offer power feed for Nokia or3rd party mast head amplifier

Application SW - Sales Item 2003478.

3.3 Nokia UltraSite EDGE BTS Mini


Summary: New 4 TRX UltraSite BTS variant for building cost effective rural coverage.Supports all UltraSite SW CX5.0 features

Market leading RF performance:

• highest TX output power (46 dBm)

• best RX sensitivity (- 115 dBm)

• widest coverage area

Lowest power consumption per coverage areaSuitable for mast top installation:

• small size and low weight

Significant savings:

• no feeder cable losses

• no feeder cable material and installation costs

• no mast head amplifiers

Operating SW.

Benefits for the Operator: Cost Effective Rural Coverage.


DN0745995



3.4 Nokia Pico GSM/EDGE BTS


Description: New 1 TRX Pico BTS for building cost effective indoor coverage. For detailedfeature description, please contact NSN Product Marketing.

On-site Indoor Coverage:

• Indoor optimised power output (+20 dBm) with xDSL backhaul

• Plug and Play deployment for end-customer

Connected to Nokia BSC:

• Appears as 1 TRX Nokia MetroSite BTS

• Fault Management by existing NetAct over Nokia Abis

• Allows WLAN type network solutions with complete system testing by Nokia

World-wide Sales & Maintenance by Nokia:

• Sold through Nokia sales and logistics channel

• Complete system testing at Nokia

• Release delivery mechanism to customer following the same process as all other

BTS’s

Operating SW.

Operational Aspects: Pico BTS Rel 1 ED1 supports S11.5 and S12. Pico BTS Rel 2supports AMR and EDGE. For further information, please contact NSN Product Marketing

Benefits for the Operator: Cost Effective Indoor Coverage.


DN0745995




DN0745995

3.5 LMUB alarm in BSC: Position not locked (8272)


Summary: An alarm notification is sent when the Location Measurement Unit (LMU) is notin a “locked” state and cancelled once a “locked” state has been achieved.

Operating SW.

Description: The Location Measurement Unit (LMUB) may need over 24 hours to reachthe GPS “self survey” (where the unit is searching for the satellite view and configuringitself accordingly) state. Further, it could take an additional day to several days until theGPS unit achieves the OK (or “Locked”) state.

Note that the LMUB must reach the “Locked” state before it can be operational. Currently,a notification that the “Locked” state has been achieved is not provided. With this feature,an alarm notification is sent when the LMUB is not in a “Locked” state and it will becancelled when the “Locked” state has been achieved.

Benefits for the Operator: The solution reduces the OPEX costs for the Operator since aremote polling of the LMU units by LMUB Manager or local access at site is no longernecessary.

SUPPORTED IN :

GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y - OSS4.2CD Set 1

S12ED3.

1

- - N Y N Y N Y Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - - - - - Operating



4 PACKET SWITCHED DATA

4.1 Dual Transfer Mode DTM

Feature ID: BSS20088 for 2G; BSS30100 for 2G/3G

Summary: Dual transfer mode provides simultaneous Circuit Switched (CS) voice andPacket Switched (PS) data service in a coordinated manner. In dual transfer mode, themobile station is simultaneously in dedicated mode and in packet transfer mode so that thetimeslots allocated in each direction are consecutive and within the same frequency. TheCS part consists of a single slot connection, while the PS part can consist of a multislotconnection

Application SW - Sales Items: BSC00055 - Dual Transfer Mode DTM (2G) & BSC00096 -Dual Transfer Mode DTM (2G/3G).

21

3

IMSIMS

IP Backbone

PacketCoreDTM User 3

BSC/PCU

MSC/HLR

BTS

DTM User 1

BTSBSC/PCU

non-DTM MS

Mail server

DTM User 2

CS voice callPS data stream

Figure 3: Dual Transfer Mode (DTM) Concept.

Description:DTM State Transitions

The mobile is in DTM mode when it has simultaneous CS speech and PS dataconnections.

Change to DTM mode can be made only through CS dedicated mode. If there is an activePS radio connection ongoing, it is released before moving to DTM mode. PCU re-establishes the PS radio connection again as soon as the CS channel has been activated.Similarly if CS call is released in DTM mode the MS will release also the PS connectionand PCU will re-establish the PS radio connection again as soon as the CS channelrelease procedure has been finalised. In case of PS release during DTM connection, theMS goes back to the dedicated mode. The possible RR state transitions related to the DTMmode are shown in the figure below.


DN0745995



Dual Transfer Mode

Packet Transfer Mode

RR Idle Mode/Packet Idle Mode

PS Release

CS Release

DTMAssignment

CS SpeechConnection

PS DataConnection

CS Speech+PS Data

Connection

DedicatedMode

DedicatedMode

Figure 4: State Transitions for DTM.

Supported DTM Multislot Classes

The BSC supports DTM multislot classes 5, 9, and 11. The BSC supports dynamicallocation (DA) and extended dynamic allocation (EDA) modes for uplink temporary blockflows (TBFs) that operate in dual transfer mode. In EDA mode, it is possible to allocate twoPS timeslots in the uplink direction for a DTMmultislot class 11 MS. In DA mode, it ispossible to allocate only one PS timeslotin the uplink direction in dual transfer mode. Table1 illustrates how PS and CS resources can be allocated for multislot classes 5, 9,and 11.The PS and CS resources must be in consecutive timeslots.

Downlink radio slots: 0 1 2 3 4 5 6 7

Uplink radio slots: 0 1 2 3 4 5 6 7

DTM Class 5,9,11 PS CS

2+2=4 PS CS

DTM Class 5,9,11 CS PS

2+2=4 CS PS

DTM Class 9,11 PS PS CS

3+2=5 PS CS

DTM Class 9,11 PS CS PS

3+2=5 CS PS

DTM Class 11 PS CS

2+3=5 EDA PS CS PS

Table 1: Possible DTM Multislot Allocations for DTM Classes 5, 9 and 11.


DN0745995



DTM Radio Resource Management

DTM supports all full rate speech codecs: FR, EFR and AMR/FR. The speech codecselection for DTM is similar to the one used for plain CS connection. DTM half ratespeech is not supported.

DTM/PS channels can be multiplexed similar to normal GPRS/EDGE.

0 1 2 3 4 5 6 7

PSPS CS

Timeslots allocatedfor PS user

Timeslots allocatedfor DTM user

Figure 5: Example of DTM and GPRS/EDGE Multiplexing.

Due to packet channel multiplexing possibility the radio resources are used most efficientlyby putting DTM to GPRS/EDGE territory. PCU performs admission control when the MS isentering DTM mode. Radio resource territory handling takes into account the CS resourceallocation into the GPRS/EDGE territory.

DTM Handover Control

3GPP standard defines that inter cell handovers shall be done by CS handover procedure.That means that NCCR and NACC procedures are not used for DTM connections. Current

CS handover criteria are used to trigger DTM handover. DTM capable cells can bepreferred for DTM capable MSs with new operator parameter. PCU can trigger inter cellhandover to CS RRM (CS performs the actual handover execution). Reasons for PCUinitiated handovers are:

• If admission control cannot accept new PS connection to DTM

• If Quality Control triggers cell change due to PS data transfer quality degradation

PCU can perform radio channel reallocation (intra cell handover) for DTM connection. PCUcan trigger reallocation for DTM connection:

•

In GPRS/EDGE territory downgrade• If Quality Control triggers reallocation due to PS data transfer quality degradation

When MS changes from dedicated mode to DTM, intra cell HO is performed from CSterritory to GPRS/EDGE territory.

GPRS Transparent Transport Protocol

GPRS mobility management and session management signaling (e.g. PDP contextactivation) can be sent on main DCCH, i.e. signaling channel when MS is on dedicatedmode. This is done by new new GPRS Transparent Transport Protocol (GTTP) layer. Inradio interface new GPRS INFORMATION message is introduced to deliver theinformation.


DN0745995




DN0745995

Using GTTP signaling, no separate radio connection (TBF) is needed. This provides fastsignaling link for GMM/SM messages.

DTM Paging Coordination

When MS has a speech call (MS is in dedicated mode), PS paging is done via CSconnection using PACKET NOTIFICATION message.

CS paging coordination means that CS Paging Request is sent to the MS on PACCH whenthe MS has PS data transmission (MS is in packet transfer mode). This is supported inNMO I (Gs interface required).

IMSI Co-ordination

The BSC must know the international mobile subscriber identity (IMSI) of an MS to be ableto provide dual transfer mode for DTM-capable MSs. The IMSI is needed for co-ordinationand identification purposes. Without the IMSI, the BSC cannot co-ordinate the CS and PSresources.

The MSC delivers the IMSI of the MS to CS connection control during a CS callestablishment. If the IMSI is not available, DTM resources cannot be allocated. Therefore,the MSC must be configured to send the IMSI information to CS connection control.

DTM and Quality of Service

Basic prinsible in introducing new applications or functionality is that these should notdecrease the performance of the existing applications. The less radio channels areavailable for packet switched usage, the more important it is to perform priorization amongthe applications. Priority based QoS enables service differentiation among the applications,and as well increase the size of PS territory.

The DTM traffic handling capacity depends on the CS and PS traffic handling capacity ofthe system. Therefore, DTM must be taken into account in PS territory planning.

Note:• The CS channel of a DTM call is allocated from the PS territory.

• The DTM CS connection uses a full rate (FR) traffic channel.

• A DTM CS radio timeslot (RTSL) in the PS territory cannot be used for data traffic.

Therefore, DTM call allocations can cause fragmentation to the PS timeslots. This happenswhen there are several simultaneous ongoing DTM calls and the DTM specific channelallocation algorithm needs to allocate resources from the middle of the PS territory.

When the PS territory is fragmented, the PCU's capability to give multislot allocations forother data connections decreases. Therefore, if DTM users are expected to contributeconsiderably to the PS traffic load and the quality of experience (QoE) of the existing data




DN0745995

users cannot be decreased, it may be necessary to evaluate and possibly increase the sizeof the PS territory.

Benefits for the Operator: Dual Transfer Mode (DTM) enables the operator to expandservice continuity network wide (GSM/EDGE and WCDMA). Increased end userexperience by bringing better usability, meaning that the data services continue whilehaving a speech call. The services benefiting from DTM are e.g. mobile e-mail, MMS andbrowsing during voice calls.

.

SUPPORTED IN :

GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y M11 OSS4.1CD2

S12ED2.

1

Y - N (Y) N (Y) N (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - Y 1) Y 2) - - - ApplicationNOTE:

1) DTM capable MS2) PCU2



4.2 High Multislot Classes


Summary: High Multislot Classes (HMC) increases EDGE peak throughput value from236.8 kbit/s to 296 kbit/s. Also the combined downlink and uplink transmission throughputincreases.

Higher throughput is beneficial for typical applications like file transfer or email as well asfor multimedia applications like e.g. video streaming.

Application SW - Sales Item BSC00061.

Description:

Introduction to GSM TDMA Frame

GSM/EDGE radio interface is divided into 200 kHz wide channels and timeslots. Timeslotsdivide a channel into eight recurring transmission/reception slots. Eight consecutivetimeslots constitute a TDMA frame.

An uplink TDMA frame is three timeslots behind of the corresponding downlink TDMAframe. This makes it possible that an MS does not need lossy duplex filter, because TX andRX operations are not simultaneous. During each TDMA frame, MS switches between DL(reception) and UL (transmission) frequencies. In a multislot connection MS can useseveral timeslots for reception or transmission during one TDMA frame. MS performs also

neighbour cell measurements during each TDMA frame between receive and transmitprocedures.

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

Downlink - MS receiving

Uplink - MS transmitting

1

322 4 55

During a connection MS

1. Receives downlink radio block on assigned timeslot

2. Changes its radio frequency to uplink frequency

3. Transmits uplink radio block on assigned timeslot

4. Makes neighbour cell measurements on neighbour cell frequencies

5. Changes its radio frequency to downlink frequency

6. Multislot allocation and High Multislot Classes

Figure 6: Principle of GSM TDMA Frame.


DN0745995



3GPP release 4 or earlier MSs are limited to using a maximum sum of five uplink anddownlink timeslots within a TDMA frame, because such MSs are allowed to use anaggregate of at least three timeslots for frequency switching and neighbour cell

measurements.3GPP Release 5 (TS 45.002) introduces new MS multislot classes that can use up to amaximum sum of six timeslots per TDMA frame. This is achieved by reducing the timerequired to perform frequency switching and neighbour cell measurements.

21544

TrTtSumTxRx

21544

TrTtSumTxRx

11645

TrTtSumTxRx

11645

TrTtSumTxRx

Eg. MS multislot class 33

Eg. MS multislot class 12

Figure 7: High Multislot Classes Increase Number of Timeslots.

0 1 2 3 4 5 6 7

0 1 2 3 4 5 6 7

Tt Tr

Figure 8: High Multislot Classes Example Allocation.


DN0745995




DN0745995

Table 2 lists the new allocation configurations which are enabled by High Multislot Classesapplication software.

5+1, 4+262641

5+1, 4+2 , 3+363642

5+1, 4+2 , 3+3, 2+464643

5+1, 4+2 , 3+3, 2+465644

5+1, 4+2 , 3+3, 2+466645

5+161640

4+1, 3+2, 2+355539

4+1, 3+2, 2+354538

4+1, 3+2, 2+353537

4+1, 3+252536

4+151535

5+1, 4+2 , 3+3, 2+465534

5+1, 4+2 , 3+3, 2+464533

5+1, 4+2 , 3+363532

5+1, 4+262531

5+161530

SumTxRx

Downlink+uplinkconfigurations

MaximumNumber of slots

MSmultislot

class

5+1, 4+262641

5+1, 4+2 , 3+363642

5+1, 4+2 , 3+3, 2+464643

5+1, 4+2 , 3+3, 2+465644

5+1, 4+2 , 3+3, 2+466645

5+161640

4+1, 3+2, 2+355539

4+1, 3+2, 2+354538

4+1, 3+2, 2+353537

4+1, 3+252536

4+151535

5+1, 4+2 , 3+3, 2+465534

5+1, 4+2 , 3+3, 2+464533

5+1, 4+2 , 3+363532

5+1, 4+262531

5+161530

SumTxRx

Downlink+uplinkconfigurations

MaximumNumber of slots

MSmultislot

class

Table 2: New configurations introduces by High Multislot Classes (downlink+uplink).

Benefits for the Operator: CAPEX savings by increasing throughput and less TRXs areneeded. Higher ARPU by increased data service throughput and service usability. HighMultislot Classes will give increased data rates to mobiles in the existing services (like webbrowsing, emails) as well in new mobile services (video conferencing, See What I see etc).

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SSGSN

NetActPlanner

Nokia 2 nd

Gen.Nokia

Talk-familyNokia

PrimeSiteNokia


NokiaUltraSite

NokiaFlexi

EDGE Y Y Y Y - OSS4.1

CD set 1S12 - - (Y) (Y) (Y) (Y) N (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - Y1) Y2) - - - Application

NOTE: 1)3GPP Rel5 MS. 2) PCU2.



4.3 Extended Dynamic Allocation


Summary: Extended Dynamic Allocation (EDA) allows an MS to use more than twotimeslots in uplink. In BSS12 the maximum number of uplink timeslots per uplink TBF isfour, which permits the following maximum uplink bitrates:

• GPRS with CS-1/CS-2, up to 48 kbit/s

• GPRS with CS-3/CS-4, up to 80 kbit/s

• EDGE, up to 236 kbit/s


Description:

GPRS/EDGE Uplink Access Methods

A radio timeslot may be shared by several GPRS/EDGE MSs. PCU assigns Uplink StateFlag (USF) to MS on each radio channel that is allocated to MS. During scheduling PCUuses these USF values in downlink radio blocks to indicate which mobile station is allowedto transmit in the following uplink radio block.

USF scheduling can be applied in two modes: Dynamic Allocation (DA) and ExtendedDynamic Allocation (EDA).

Dynamic Allocation

When Dynamic Allocation mode is applied, a received Uplink State Flag gives the MSpermission to send during the next block period on the corresponding uplink timeslot.

When this method is applied, an MS needs to decode every downlink block on eachtimeslot included in its uplink allocation in order to detect USFs. This limits the maximum

number of uplink timeslots to two.

USF

0 1 2 3 4 5 6 7

USF USF

TT

0 1 2 3 4 5 6 7

T

USF

T

Figure 9: Dynamic Allocation.


DN0745995



Extended Dynamic Allocation

Extended Dynamic Allocation mode allows more timeslots to be allocated in uplink byremoving the need of detecting USFs separately for each allocated uplink timeslot. Areceived USF gives the MS permission to send during the next block period on thecorresponding uplink timeslot and on all other timeslots of the uplink TBF allocation thatfollow this timeslot.

USF

TT

0 1 2 3 4 5 6 7

T

USF

TT T T T

Figure 10: Extended Dynamic Allocation.

MS Power Reduction

MS may reduce its transmission power when it uses more than one timeslot in uplink. Theamount of power reduction a MS applies depends on the number of allocated uplinktimeslots and the MS’s multislot power profile. 3GPP Release 5 standard defines fourdifferent MS multislot profiles.

um er ouplink

timeslots

erm e nom nareduction of maximum

output power (dB)

um er ouplink

timeslots

Multislotprofile 0

Multislotprofile 1

Multislotprofile 2

Multislotprofile 3

1 0.0 1 0.0 0.0 0.0 0.02 3.0 2 3.0 1.0 0.0 0.03 4.8 3 4.8 2.8 0.8 0.04 6.0 4 6.0 4.0 2.0 0.0

3GPP release 4 3GPP release 5

Tables 3 & 4: MS Multislot Power Profiles.

The reduced MS transmission power is taken into account together with the expectedquality of the radio path when:

• Selecting the number of uplink timeslots, and

• Selecting the initial channel coding scheme for a new connection.

Assigning less channels to a MS means higher tranmission power on each uplink timeslot.This ensures that there is no effect on the GPRS/EDGE coverage, thus no need for anynetwork replanning. During the uplink data transmission, link adaptation takes MS powerreduction into account.


DN0745995




DN0745995

Determining Number of Uplink Timeslots

For the streaming traffic class connection only as many uplink timeslots are allocated it isnecessary to achieve the guaranteed bitrate.

For other traffic classes the number of uplink timeslots is determined by estimating whichallocation will give the best uplink throughput. The highest throughput is not alwaysreached by the highest number of allocated uplink timeslots. This is due to MS powerreduction and scheduling inflexibility. During radio connection the PCU adapts theallocation of downlink and uplink timeslots based on the monitored amount of downlink anduplink data traffic.

MS Extended Dynamic Allocation Capability

Extended Dynamic Allocation support is mandatory for MS Classes 22, 24, 25 and 27. Forother classes, MS indicates its Extended Dynamic Allocation capability in the MS Radio

Access Capability IE (RAC), which it sends to network during the connection creation.

Benefits for the Operator: Higher ARPU by increased data service uplink throughput andservice usability. The maximum number of uplink time slots and the achievable uplinkthroughput are doubled in comparison with earlier BSS releases. This is beneficial foruplink oriented applications and connections.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SSGSN

NetActPlanner

Nokia 2 nd

Gen.Nokia

Talk-familyNokia

PrimeSiteNokia


NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y - OSS4.1CD set 1

S12 - - (Y) (Y) (Y) (Y) N (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - Y1) Y2) - - - Application

NOTE: 1) Multislot capable MS 2) PCU2




DN0745995

5 RADIO NETWORK PERFORMANCE

5.1 Support for Single Antenna Interference Cancellation


Summary: Single Antenna Interference Cancellation (SAIC) is a downlink technique thatenables interference cancellation without using a second receiver antenna.

SAIC is primarly a mobile station feature, which functionality can be further enhanced byproper network support. The target is to get the best possible system capacity available inall conditions when SAIC capable mobiles and conventional receivers are present in thenetwork.

With the Nokia BSS SAIC feature, on the network side, the operator will be able to collectSAIC related statistics and adjust DFCA algorithm for SAIC mobiles. The SAIC capablemobile stations will indicate their capability towards the network which then will takeappropriate actions.

SAIC is a generic term for a receiver algorithm utilising one antenna in a MS.

DARP is a abbreviation for Downlink Advanced Receiver Performance. DARP is a 3GPPstandardized feature for 2G utilising SAIC and uplink signalling and Introduced in Rel-6 asrelease independent feature. DARP can be introduced to terminals supporting earlier 3GPPreleases.


Description:

SAIC and Network Support

Interference cancellation algorithms in terminals work independently. However, in order toenable operators to optimise and follow the behavior of SAIC terminals’ network signalingand statistics support is needed:

• BSS Class mark support to recognize SAIC terminals

•

Separate statistics for SAIC terminals in order to get insight into SAIC performanceThe BSS SAIC feature provides new counters for SAIC mobile stations in the followingmeasurements: MS Capability Indication, RX Quality Statistics,AMR RX Quality, PowerControl FER and Packet Control Unit measurement. With these new counters the operatormay validate the distribution and traffic of the SAIC mobile stations in relation to old legacymobiles. Also one new measurement (DFCA SAIC) is introduced. This new measurementis visible if DFCA feature is activated in addition to SAIC feature. In case the operatoractivates DFCA together with SAIC, further radio resource enhancements will be present inthe network.

PCU related functionality will be implemented only in PCU2.




CAPEX savings by better utilisation of the spectral efficiency. Improved end userexperience by providing better call quality. SAIC-enabled terminals will realise animmediate improvement in their call quality (better FER) at low SAIC terminal penetrationsrates, especially when DL Power Control is not in use. When DL Power Control is used DLtransmission power for SAIC terminals can be reduced and this way overall DL interferencein network is decreased and also the call quality of legacy terminals is improved. With SAICthe terminals perform in quality conditions that would not be good enough for legacyterminals, i.e. DL Power Control is not any more usable nor are the quality basedhandovers possible.

When the terminal penetration rates grow, SAIC starts to provide system capacity gain. Thespectral efficiency can be improved by increasing the frequency reuse (with DL PowerControl) in downlink interference limited network. In high terminal penetration rates, SAIC

provides both call quality to SAIC enabled terminals as well as large gain in overall systemcapacity. Simulated capacity gain with full SAIC penetration is 50-60 %.

Figure 11: Simulated SAIC Gains in Synchronized Networks*.

*Simulation based on 2.4 MHz bandwidth with 12 hopping frequencies. The

traffic consisted of 70 % speech (AMR 5.9) and 30 % GPRS (CS1/CS2).Multislot class 3+1 was used. Synchronized BSS (implication ofsynchronization as such not evaluated).

Operational Aspects: Some parts of SAIC feature have dependencies to other featuresand licences in the BSC. These are Dynamic Frequency and Channel Allocation (DFCA)and Adaptive Multirate Speech Codec (AMR) feature.

DFCA needs to be enabled for DFCA SAIC optimisations to work. When AMR is usedtogether with SAIC, AMR specific SAIC counters are updated in the AMR RX Qualitymeasurement.


DN0745995



SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SSGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexi

EDGE Y Y Y Y - OSS4.1

CD set 1S12 - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - Y 1) Y 2) - - - Application

NOTE: 1) SAIC/DARP capable MS (3GPP Rel6)2) PCU2 for PCU related measurement

5.2 Space Time Interference Rejection Combining (STIRC)


Summary: The STIRC is an enhancement for the basic IRC, which is implemented inNokia EDGE Ultra Site & Metro Site products. STIRC improves significantly theinterference (Co-channel & Adjacent channel) rejection capability of the UltraSite andMetroSite receivers.


Description: STIRC gives best gain when there is a single dominant interferer, so it workswell in typical urban conditions. For example, estimated link level interference rejectionperformance of EDGE 8PSK gives on average 4 – 10 dB gains compared to currentUltraSite/MetroSite products, under Typical Urban (TU) conditions with 2 way UL Diversity.

Achieved gains decrease when Dominant to rest Interference Ratio (DIR) decreases, e.g.DIR 10dB gives an estimated 2 dB average gain over basic IRC.

STIRC

Quality booster

STIRC

Quality booster

Figure 12: Better UL Performance Improve Overall Quality.

STIRC is a licensed capacity enhancement feature, administered by BSC on a perBTS_Object basis. In case EDGE TRX is not allowed to utilize STIRC, the current IRCalgortihm will be used instead. Uplink diversity is based on the idea of having independentRF paths between MS and BTS, formed by two or more horizontally spaced or orthogonallypolarized antennas at the BTS. These independent paths are processed and combined byBTS DSP SW. IRC and STIRC are proprietary UL Receiver Technologies to improve BTS

Air interface sensitivity. Earlier combining algorithm implemented in Nokia GSM BTS is aMaximum Ratio Combining (MRC). MRC combines the signal trying to maximise the signalto noise ratio. IRC identifies and rejects an interfering signal in diversity combination. It isideal in canceling a single, co channel or adjacent, interferer i.e. the gain is maximum whenDIR (Dominant to rest of the Interference Ratio) is high.


DN0745995




DN0745995

STIRC is implemented to BTS base band DSP SW in such a way, that it does not affect theBTS architecture or capacity of the BTS. All antenna configurations are supported, howeverbest performance is ensured with two or four way uplink diversity configurations with co- or

cross polarized antennas. Compatibility with Nokia Smart Radio Concept (SRC) isguaranteed. All forms of RF hopping: synthesizer, baseband and antenna hopping aresupported.

Benefits for the Operator: CAPEX savings and increased end user experinence byimproved network performance.

STIRC ensures better uplink quality particularly in high user density/interference limitedscenarios, better user data throughput, both improved traffic and control channelperformance as well as provides possibility to use less mobile Tx power for quality baseduplink power control. This latter issue leads to reduction in overall interference level inuplink and improves mobile battery life.

With STIRC the link balance with the deployment of SAIC mobiles can be re-established.Near-far performance can be improved against co-channel interferers for tight frequencyreuse (e.g. 1/1). STIRC partially compensates the wall penetration loss, i.e. supports betterthe indoor users, and is able to restore Link Balance for indoor SAIC users.

Interaction with Other Features: BSS synchronization helps in achieving full STIRC gain.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC


NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y - - S12 - - N N N CX5 N CX5 EP2


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - - Y 1) - - Application

NOTE: 1) EDGE TRX required



5.3 Multipoint A interface


Summary: With Multipoint A feature it is possible to connect the BSC to several MSCservers.


Description: Multipoint A Interface provides the following benefits:

• Network performance in terms of scalability is improved.

• Capacity upgrades by adding additional MSS/VLRs in the pool-area are smooth.

• Network load can be distributed amongst the serving entities, enables the BSCsto route information to different MSCs.

• Required signalling is reduced (MS roaming case, signalling towards HLR andbetween VLRs not needed in intra pool-area location updates, inter-MSSrelocations are reduced).

• The neighbouring pool areas can overlap, which allows to separate the trafficinto different 2G MS moving patterns, e.g. pool-areas where each covers aseparate residential area and all the same city centre.

• Fault protection is improved.

• Failure in one MSS/VLR does not stop the service in pool-area

• Flexibility to software upgrades/maintenance (MSS/VLR)

A re a 1

B S C

A re a 5

B S C

A re a 6

B S C

A re a 7

B S C

A re a 8

B S C

A re a 2

B S C

A re a 3

B S C

A re a 4

B S C

P o o l A re a 2P o o l

A re a 1

M S C 3M S C 2

M S C 1

M S C 6M S C 5

M S C 4

P o o l

A re a 3

M S C 8M S C 7

Figure 13: Pool-area Configuration Example.


DN0745995



All MSCs in the pool area have to support this feature so that Multipoint A interface featurecan also be used in BSC.

BSC 1

BSC 2

TC 1

TC 2

MSS 2

BSC 1

BSC 2

TC 1

TC 2

MSS 2

Ater A

MGW 1

MSS 1

MGW 1

MSS 1

MGW 2MGW 2

BSC 1

BSC 2

TC 1

TC 2

MSS 2

BSC 1

BSC 2

TC 1

TC 2

MSS 2

Ater A

MGW 1

MSS 1

MGW 1

MSS 1

MGW 1

MSS 1

MGW 1

MSS 1

MGW 2MGW 2MGW 2MGW 2

Figure 14: Multipoint A interface Architecture Example.

Selection of MSC

When MS attempts location update or attachments to the network, MSC will be selected byBSC serving the area where MS is currently located. Normally MSC selection is based onNRI (Network Resource Identifier). With Multipoint A BSC shall be able to perform MSCselection also when e.g.:

• Received NRI is unknown for BSC

• There is no NRI

• MSC identified by NRI is unreachable

In these cases load balancing between MSSs in the pool will be taken into account by BSC. After NRI assignment, future transactions between MS and MSC are done towards thesame MSC.

VLR

MSCSSP

BSC

MSS_1

VLR

MSCSSP

MSS_2

Location UpdateAttach Procedure(IMSI/IMEI)

NASNodeselectionfunction Location Update

Attach Procedure(IMSI/IMEI)

Pool area 1

Encode TMSIso that it containsNRI

TMSI(NRI)TMSI (NRI)

VLR

MSCSSP

BSC

MSS_1

VLR

MSCSSP

MSS_2

Location UpdateAttach Procedure(IMSI/IMEI)

NASNodeselectionfunction Location Update

Attach Procedure(IMSI/IMEI)

Pool area 1

Encode TMSIso that it containsNRI

TMSI(NRI)TMSI (NRI)

Figure 15: Pool-area Configuration Example.


DN0745995




DN0745995

MSC will be identified with NRI.

• Length of the NRI can be from 0 to 10 bits.

• NRI is part of the TMSI and it is located to bits 14 to 23 of TMSI.

NAS Node Selection function - Assigns specific network resources (of MSC) to serve anMS and route the traffic to the assigned network resource.

• BSC masks NRI out of the TMSI, which is indicated in each initial NAS signallingmessage.

• BSC routes the NAS message to the relevant MSC.

• If no MSC address is configured for the requested NRI or if no NRI can be derived(e.g. the MS indicated an identity which contains no NRI) then the BSC selects anavailable MSC according to CGR (Circuit Group) load of each MSC’s SPC(Signallling Point Code).

Benefits for the Operator: CAPEX savings by improving scalability and the faultprotection in Core network.

Multipoint A is a resilience solution for the operator by protecting the core network elements-in case of failures in the NSS the network can stay operational with reduced capacity.

Multipoint A increases the network performance in terms of scalability, distributes thenetwork load among several network elements and reduces the amount of signallingrequired by roaming mobile stations, because the pool area is larger than the service areaof one MSC/MSS.

Operational Aspects: The Reversed Hunting feature which allows the BSC allocate the Ainterface circuits is not supported together with Multipoint A interface feature in S12release. The ANSI and ETSI standards cannot be used in parallel when creatingconnections to MSCs for Multipoint A use.

All MSCs in the pool area have to support this feature so that Multipoint A interface feature

can also be used in BSCS. (Feature 1564 Nokia MSC Multipoint A)

Maximum 10 MSCs can be connected to one BSC.

Signalling Network parameters - All MSCs/MSSs must belong to the same signallingnetworks.




DN0745995

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

N Y Y Y Y Y 1) OSS4.1CD set 1

S12 Y 2) - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - - - - - Application

NOTE: 1) Multipoint A (Nokia M13) 2) Global CN-ID support in CS Paging (SG5.1)

5.4 DL DTX Audio Quality


Summary: Quality of musical ringback tone suffers when downlink DTX (DiscontinuousTransmission) feature is used. This feature improves the quality of ringback tone by activatingdownlink DTX to the calling subscriber only after the called subscriber has answered.

Operating SW - However, this must be ordered separately, using Sales Item BSC00134.

Description: When musical ringback tone is used, DTX (disable transmission) feature causesinterrupts in the continuous music. It was found that Nokia DL DTX (EFR & AMR) algorithm inTCSM is not optimised to work with the DL music. And often the active music sample issubstituted with SID (silence indicator). Phone is generating comfort noise as part of the DTXalgorithm, which is recognised as whooshing noise by the user.

Signalling in the BSC is changed so that downlink DTX at the TCSM is activated only after thecalled subscriber has actually answered.

During the call setup BSC will first disable DL-DTX even if MSC requests that (in the Assignment request).

When the called party has answered and MS sends Connect Ack message to the MSC, BSCwill detect this and activates DTX by sending Mode Modify message to the BTS.

No modifications are required in the TCSM or BTS.

Benefits for the Operator: When musical ringback tones (caller tunes) are used, this featureimproves the quality of the ringback tone in cases where downlink DTX is used.

Operational Aspects: This feature is activated with a licence (on/off licence). This featuregives benefit only when downlink DTX is used. DTX is activated with MML commands.




DN0745995

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexi


CD set 1S12 (Y) - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - - - - - OPERATING

5.5 Maximum MS TX Power During E911 location


Summary: This feature disables uplink power control for a period of locationing on the trafficchannel for any MS that is being positioned whenever during an emergency call using the U-TDOA technology.


Current Implementation : With the current implementation, uplink power control andhandovers are disabled only in the beginning of an emergency call for a configurable period oftime.

Description: For the GSM Lb case, the initial location is triggered by the MSC. When anemergency call is placed from an MS, the MSC sends a first Perform Location Request(PLRQ) to the BSC, which is then forwarded to the locationing system. This PLRQ has theresponse time set to low delay. The locationing system computes a UTDOA position andprovides the response back to the BSC, where it is sent back to the MSC.

The GMLC can also request for an updated position of this MS to the MSC, which will kick off asubsequent request – PLRQ – to the BSC which results in another request to the locationingsystem, where a second location calculation is initiated.

The issue with the Lb implementation is the latency within which the locationing systemreceives location requests (PLRQs). Due to this delay, the PLRQ occurs after the MS ispowered down to the level required to sustain the voice call due to power control beingenforced. This power down causes degraded accuracy of locations and significantly impactsthe 95 th percentile location accuracy.

With this feature, whenever receiving the Perform Location Request (PLRQ) from the MSC forthe purpose of positioning a MS on an emergency call or upon subsequent receipt of U-TDOAlocationing request from the locationing system, the BSC executes a command to power upthe MS. Power of the MS will be kept in the maximum until locationing has been performed.




DN0745995

Benefits for the Operator: This feature ensures that MS transmits with maximum powerduring locationing procedure of emergency calls. This gives better locationing accuracy.

Operational Aspects: This feature is controlled with BSC level licence and feature code. Thisfeature is used only with Lb-interface and for U-TDOA locationing requests.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC SGS

N

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexi

EDGEY Y Y Y - OSS4.2 S12

ED1.1- - - Y Y Y Y Y Y Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - - - - - Application

5.6 Increased Dynamic SDCCH capacity


Summary: With this feature BSC may allocate Dynamic SDCCH channels in UltraSite BTSs togive a total of up to 24 x SDCCH channels for a BCCH TRX, and up to 32 SDCCH channelsfor a non-BCCH TRX. In Common BCCH (Segment) operation the Dynamic SDCCH channelsare only allocated on TRXs in the BCCH frequency band.


Description: This feature is controlled by Licence Key LK in the BSC. There is no otheroperator control or setup.

Benefits for the Operator: The SDCCH signalling capacity in BCCH TRX is increased by50%, and in non-BCCH TRX by 100%. The increases SMS capacity in networks with veryheavy SMS loading, and increases voice call capacity in dual band networks where there islimited frequency allocation in the BCCH band.

Operational Aspects: 64 kbit/s signalling channels (TRXSIG) are needed for each TRX. OnlyUltraSite BTS is supported.




DN0745995

SUPPORTED IN:GSM

800

GSM

900

GSM

1800

GSM

1900 MSC

Nokia

NetAct BSC SGSN

RNC NetAct

Planner

Nokia

2nd Gen.

Nokia

Talk-family

Nokia

PrimeSite

Nokia

MetroSite

Nokia

InSite

Nokia

UltraSite

Nokia

FlexiEDGE

Y Y Y Y - OSS4.2 S12ED1.1

- - - N N N N N Y N


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW



5.7 Load based AMR Packing


Summary: BSS21154 introduces AMR specific parameters for load based channel ratecontrol.


Current Implementation: Before BSS21154, the load threshold parameters that control traffic

channel allocation in half rate mode were the same for both AMR and non-AMR calls.However, the robustness of AMR speech CODECs makes it possible for AMR calls to survivein poorer radio conditions longer than is possible for non-AMR calls. Consequently, half ratecan safely be used for AMR calls more frequently than for non-AMR calls.

Description: With feature BSS21154 it is possible to define parameters both on the BSC andon the segment level to control the use of half rate based on traffic load for AMR calls. Theparameter set is similar to the one that is already used for both AMR and non-AMR calls. WithBSC level parameters it is possible to define load thresholds that are applied in all cellsmanaged by the BSC. If the general values defined at the BSC level are not suitable for all

cells then it is possible to define cell specific values with segment level parameters.

For both the BSC and the segment level there is a pair of load limits - the lower limit and theupper limit. These limits are compared with the amount of idle full rate traffic channels in a cell.Half rate allocation starts when the amount of idle FR TCHs falls below the lower limit. TCHsfor AMR calls are allocated in full rate again after the amount of idle FR TCHs returns to a levelabove the upper limit.

The load limits are also used to trigger the packing of ongoing AMR FR calls into AMR HRcalls.

On the BSC level, the parameters are AMR Lower Limit For FR Resources and AMR Upper

Limit For FR Resources . The segment specific BTS object parameters are AMR Lower LimitFor SEG FR Resources and AMR Upper Limit For SEG FR Resources .




DN0745995

Benefits for the Operator: With the new parameters provided by feature BSS21154, it is now

possible to control half rate use separately for AMR and non-AMR calls. Since AMR calls cansurvive in poorer radio conditions longer than non-AMR calls, it is now possible to have halfrate triggering for AMR calls occurring earlier than those for non-AMR calls.

Operational Aspects: The parameters for feature BSS21154 are optional and require notonly a licence for the Load Based AMR Packing feature, but also a licence for AMR HR use.

The parameters realised by feature BSS21154 control half rate use for AMR calls only.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - OSS4.2

CD1S12ED2.

1

- - - N Y Y Y N Y Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - Y - - - - Application 1)

Note: 1) The feature AMR Capacity (HR) is also required (ASW: BSC00004).

Note too that AMR capable MS are required.

5.8 Single MA list for EGSM and PGSM


Summary: The feature BSS21165 introduces the possibility to employ radio frequencyhopping (RF hopping) in a PGSM900-EGSM900 BTS irrespective of the cell’s BCCH carrierfrequency, whether PGSM900 or EGSM900. The most important aspect is that the BSC willallow RF hopping over the entire PGSM900-EGSM900 frequency range in a PGSM900-

EGSM900 BTS.


Current Implementation: Traditionally in the Nokia BSC, PGSM900 and EGSM900 areregarded as two separate frequency bands. Combining of PGSM900 and EGSM900 radioresources within a cell was originally enabled through the segment concept - where theresources of the two bands are realised as two separate BTS objects within a segment.

The features BSS20826 and BSS21010 allow the configuring of both PGSM900 and

EGSM900 in a single BTS object. Currently, the possibilities to utilise the resources of aPGSM900-EGSM900 BTS vary, depending on whether a segment’s BCCH is on PGSM900 orEGSM900. With a PGSM900 BCCH, frequency hopping is not possible; however, with an




DN0745995

EGSM900 BCCH, RF hopping is possible but the mobile allocation (MA) frequency list maycontain only either PGSM900 or EGSM900 frequencies.

Description: This feature introduces the possibility to employ RF hopping in a configurationwhere a BTS has both PGSM900 and EGSM900 TRXs and the BCCH carrier is on thePGSM900 frequency band. The most important aspect of this feature is that the operator maynow enable RF hopping over the entire PGSM900-EGSM900 frequency range throughincluding both PGSM900 and EGSM900 frequencies in a single mobile allocation frequencylist used in the BTS. The possibility to use a combined MA frequency list for RF hopping in aPGSM900-EGSM900 BTS is available irrespective of the BCCH carrier’s frequency band -whether PGSM900 or EGSM900.

Benefits for the Operator: This feature improves the potential spectral efficiency realised bythe BTS and importantly leads to improved KPIs.

Operational Aspects: Feature BSS21165 requires a valid licence.

When the hopping frequencies of both PGSM900 and EGSM900 are included in a cellallocation (CA) frequency list, the amount of frequencies on the list may become limited. Thisis a consequence of the radio interface messages of the GSM system and may thus limit theavailable frequencies that can be used in RF hopping.

When the BCCH TRX of a PGSM900-EGSM900 BTS is on the PGSM900 band, the BSCallows only EGSM900 frequencies in the non-BCCH TRXs of the BTS. However, this does notrestrict the frequency use in RF hopping: all the hopping TRXs in the BTS can perform RFhopping over the frequencies of the attached mobile allocation frequency list, which maycontain both PGSM900 and EGSM900 frequencies.

In a PGSM900-EGSM900 BTS with the BCCH on PGSM900, the BSC supports GPRS/EDGEin the PGSM900 BCCH TRX only. The operator must set the GTRX parameter of theEGSM900 TRXs to the value “N”. In addition, the operator should limit static SDCCHresources to the PGSM900 BCCH TRX. The BSC itself limits dynamic SDCCH allocation andFACCH setup actions in the PGSM900 BCCH TRX only.

Baseband hopping (BB hopping) is not possible in a PGSM900-EGSM900 BTS where theBCCH is on PGSM900. Other features that cannot be used in this configuration are DynamicFrequency and Channel Allocation (DFCA) and features that employ super reuse TRXs - thatis, Intelligent Underlay-Overlay (IUO), Enhanced Coverage by Frequency Hopping (ECFH) andHandover Support for Coverage Enhancement (HSCE). Further, the BSC does not support theuse of High Speed Circuit Switched Data in a BCCH BTS where there are both PGSM900 andEGSM900 resources in use and the BCCH carrier is on the PGSM900 frequency band.

In a segment environment, the BSC does not allow GSM900 frequencies in any other BTSobject of the segment when PGSM900 and EGSM900 frequencies are combined in the BCCHBTS and the BCCH carrier of the segment is on the PGSM900 frequency band.




DN0745995

In an extended range cell with both PGSM900 and EGSM900 TRXs in a BTS object under thecontrol of a PGSM900 BCCH, the E-RACH TRX must be tuned to a PGSM900 frequency inorder that the PGSM-only MSs have full coverage in the cell.

For the configuration of a PGSM900-EGSM900 BTS with the BCCH on EGSM900, the BSCsupports GPRS/EDGE in the band of the BCCH TRX only. Here, the operator must set theparameter GTRX of each PGSM900 TRX to the value “N”.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEN Y N N - OSS4.2

CD1S12ED2.

1

- - - N Y N Y N Y Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - Y - - - - Application

Note: MS EGSM900 support is required.

5.9 DFCA RRM Power Reduction


Summary: The DFCA Power Level calculation in RRMPRB is changed such that two newUTPFIL parameters (one for the UL and one for the DL) are implemented for limiting UL andDL power pre-reduction in RRMPRB.

Operating SW.

Current Implementation: During DFCA trials, it has been observed that in some cases for thecurrent implementation RRMPRB reduces the UL and/or DL power too much, which maycontribute to dropped calls.

Description: Two new UTPFIL parameters (one for the UL and one for the DL) areimplemented for limiting UL and DL power pre-reduction in RRMPRB. With those UTPFILparameters, the maximum power pre-reduction in RRMPRB is defined:

DFCA_MAX_PWR_RED_UL (range = 0 – 30, default value = 10)DFCA_MAX_PWR_RED_DL (range = 0 – 30, default value = 10)

RRMPRB compares the calculated UL/DL power pre-reduction value with the new UTPFILparameter DFCA_MAX_PWR_RED_UL/DL. If the calculated UL/DL power pre-reduction valueis greater than the value which is patched to DFCA_MAX_PWR_RED_UL/DL, the value of theUTPFIL parameter is used for the UL/DL power reduction instead of the calculated UL powerpre-reduction value.




DN0745995

If there are no values patched for DFCA_MAX_PWR_RED_UL and/orDFCA_MAX_PWR_RED_DL to the UTPFIL, or the patched values are not in the range (0-30),so RRMPRB set default values will be employed for those UTPFIL parameters.

Benefits for the Operator: This capability further enhances the performance of the DFCAfeature through reducing the potential number of dropped calls in some cases.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - - S12

ED2.1

- - - N N N Y N Y Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - - - - - Operating




DN0745995

5.10 Radio Link Timeout parameter for AMR HR


Summary: This feature enables the operator to set separate Radio Link Timeout (RLT)parameters for AMR FR and AMR HR.


Description: This feature enables the operator to set separate Radio Link Timeout (RLT)parameters for AMR FR and AMR HR. This then provides an increased flexibility for the

operator to adjust and tune the network according to the particular requirements and canultimately assist with reducing the Call Drop Rate.

Benefits for the Operator: The increased flexibility of parameter setting can assist theOperator in reducing the Call Drop Rate.

SUPPORTED IN:

GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - OSS4.1

CD Set 2S12ED3.

1

- - - N Y Y Y N Y Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - Y - - - - Application 1)

Note: AMR capable MS is required.1) The feature AMR Capacity (HR) is required (ASW BSC00004).




DN0745995

5.11 Intelligent Selective Paging


Summary: The CCCH capacity in the BSS may be enhanced through sending pagingmessages to an area smaller than the whole Location Area.


Current Implementation: The operator may need to reduce the used LA size in order to allowfor more paging capacity, with the tradeoff that the number of LA updates will increase.

Description: The MSC includes the LAC and Cell ID of the last recorded cell into the issuedpaging messages.

The BSC then forwards the paging message to the indicated cell and the neigbouring cells ofthe identified cell in the same LA (according to the defined neighbour cell list).

The CCCH load decrease is in proportion to the length of the neighbour list and also the size ofthe LA area, assuming that the paged handset is actually located in the reduced paged area

Benefits for the Operator: The paging capacity of the CCCH can typically be enhanced bybetween 40...70%.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y Y 1) - S12

ED4.

1

- - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - - - - - Application

1) Feature 1682. M13.6 TOP is required. Refer to the Activation Instruction for Feature 1682.




DN0745995




DN0745995

6 OPERABILITY

6.1 File Based Plan Provisioning


Summary: With File Based Plan Provisioning operating software the operator downloadsthe network plan by using FTP.

File Based Plan Provisioning improves the performance of the configuration changeprocedure. The performance improvement is needed due to increased network elementcapacity (eg. BSC3i 2000), increased amount of radio network objects and growing networksizes. File Based Plan Provisioning allows also the configuration of more BSCs and BTSsduring the same maintenance window period.

Operating SW.

Description:

File Based Plan Provisioning - Main Features

File Based Plan Provisioning makes NetAct Radio Access Configurator provisioning morescalable. It allows parallel operations like operations to several BSCs at the same time orthe possibility for BSC to activate several sites at the same time. Configuration changes are

transferred in one XML file to BSC using FTP or FTAM. BSC plan validation ensures errorfree activation.

File Based Plan Provisioning allows several methods for plan activation:

1. Minor service impact, slower activation

2. Medium service impact

3. High service impact, fastest activation

With fastest activation (3) the network downtime is minimised. Whereas with sloweractivation (1, 2) the network handling capability is kept better during activation. With options1 and 2 BSC tries to hand over speech connections from the activated cells to workingcells.

Automatic fallback storing in BSC is always applied.

File Based Plan Provisioning - User Workflow

Configuration change process must be divided into phases. Preparations can be done inadvance in the day shift. There is less work to be done in the activation phase, which isusually done during the nigth shift.



Actuals

Plan(s)

Upload Provision

2G 3G

Actuals

ConsistencyChecking

Plan(s)

Upload Provision

EventsIn caseof localRNWchanges

1.

2.

3.4.

5.

Figure 16: File Based Plan Provisioning, User Workflow.

User Workflow:

1. Plan generation

• Plan is imported or built in NetAct.

• Consistency checks can be executed in NetAct for the plan.

2. Download

• Selected plan is downloaded to BSCs.

• Logs are reviewed in NetAct

3. Validation

• Cross-checkings in BSCs to ensure that plan is correct for activation

• Logs are reviewed in NetAct

4. Activation

• Automatic storing of fallback configuration.

• Start activation for selected BSCs.

• Follow the activation progress in NetAct.

5. Possible activation of fallback configuration

• User can activate stored fallback configuration in case of an emergency situation.


DN0745995




DN0745995

File Based Plan Provisioning comparison to other methods:

Compared to MML macros

• The activation is faster.

• There is no need for several MML commands per site and no massive event loadtowards the NetAct.

• There is less work and no human error possibilities in the activation phase.

Compared to provisioning using Q3 interface (plan download and direct activation)

• The performance is better.

• Preparation work can be done beforehand in the daytime and there are less steps inthe activation phase.

Compared to background database

• The plan download and activation performance is better.

• Support for parameter and objects is more comprehensive.

• File Based Plan Provisioning supports object creation and deletion operations.

Benefits for the Operator: File Based Plan Provisioning decreases the time used fornetwork provisioning and thus decreases the operator operational costs. File Based PlanProvisioning makes the parameter change process similar to the one used in Nokia 3G.The increased amount of provisioned objects in S12 adds the need for this operatingsoftware.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia 2 nd

Gen.Nokia

Talk-familyNokia

PrimeSiteNokia


NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y - OSS4.1CD2; CD1323 2)

S12ED2.

1

- - (Y) (Y) N (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - Y 1) - - - Operating

1) Ethernet plug-in unit for FTP, or X.25 interface card (AS7) for FTAM2) NetAct Radio Access Configurator (RAC)




DN0745995

6.2 File Based Configuration Upload


Summary: NetAct RAC functionality is based on having correct and real time maintainedactual configuration. There are some operator and Nokia personnel tasks where the actualconfiguration maintenance needs to be done using data upload functionality from NEs(Network Element). With File Based Configuration Upload the configuration data istransferred to NetAct in bigger portions using files.

Operating SW.

Description: File Based Configuration Upload improves the performance of theconfiguration change procedure. The performance improvement is needed due to theincreased network element capacity (eg. BSC3i 2000), increased amount of radio networkobjects and growing network sizes. File Based Configuration Upload makes the upload in ashorter period, which allows for faster synchronization between NetAct and BSCdatabases.

File Based Configuration Upload - Main Features:

File Based Configuration Upload makes NetAct Radio Access Configurator more scalablefor uploading. It allows parallel operations like operations to several BSCs at the sametime. Configuration changes are uploaded in one file to NetAct using FTP or FTAM.

There are two methods for the upload

• Topology upload

• Whole RNW configuration upload

Benefits for the Operator: File Based Configuration Upload decreases the time used fornetwork configuration data upload from BSC to NetAct RAC and thus decreases theoperator’s operational costs. The increased amount of configured objects and parametersin S12 adds the need for this operating software.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC SGS

N

NetActPlanner

Nokia 2 nd

Gen.Nokia

Talk-familyNokia

PrimeSiteNokia


NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y - OSS4.1CD set 1

2)

S12 - - (Y) (Y) N (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - Y 1) - - - Operating

1) Ethernet plug-in unit for FTP, or x.25 interface card (AS7) for FTAM2) NetActRadio Access Configurator (RAC)




DN0745995

6.3 CS Statistics Enhancements


Description: CS statistics enhancements consist of improvements to BSC circuit switchedstatistics:

In order to provide the operator more accurate information for performance managementnew counters are added. The counters will improve network monitoring in a sense of moreaccurate key performance indicators. The new counters utilize the use of Nokia preferredkey performance indicators, KPIs, which will help to achieve agreed meters in customernetworks. New counters include:

• SDCCH attempts counters: Separate counters for mobile originated, mobileterminated calls and location updates.

• TCH usage counters: Take half rate better into account when calculating busyTCHs.

Operating SW.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y - OSS4.1

CD set 1

S12 - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - - - - - Operating

6.4 MEFICO (Monitoring Tool for BSC)


Summary: MEFICO is Temporary tool for converting measurement and observation datafiles into readable ASCII format.

Application Software - Sales Item 2003479.

Description: Converting measurement and observation data files into readable ASCIIformat by: Transferring measurement and observation data files to PC.

Converting measurement and observation data files with MEFICO.

This feature is to be used only in the test bed installations and not in any live environment.




DN0745995

Benefits for the Operator: OPEX savings by converting BSS data fast into readableformat in the network test environment, when connection to NetAct is missing or upgraded.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

- - - - - - S12 - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW



6.5 Missing NSEI Alarm


Summary: On some rare occasions, GPRS load situations may disturb MIPC messagedeallocation routines in PCU1 so that PCU1 runs out of MIPC messages. This disables allGPRS traffic through that PCU1 and yet no alarms are set or automatic recovery action taken.S12 ED “Missing NSEI alarm” (BSS21156) introduces two new alarms to tackle this problem.

Operating SW.

Current Implementation: On some rare occasions, GPRS load situations may disturb MIPCmessage deallocation routines in PCU1 so that PCU1 runs out of MIPC messages. Thisdisables all GPRS traffic through that PCU1 and yet no alarms are set or automatic recoveryaction taken.

Description: Two new alarms to tackle the problem: 3451 MIPC BLOCKS RUNNING OUT INPCU and 3452 ZERO FREE MIPC BLOCKS IN PCU.

PCU1 application uses two MIPC message spaces: Abis Pool and PCU Pool. When thenumber of free message decreases below 70 % of the maximum in either of these spaces, aone star alarm is set to indicate the operator that there are probably some problems in MIPCmessage deallocation routines. If the number of free messages decreases down to zero, athree star alarm is set and the operator can take manual recovery actions.

Benefits for the Operator: The operator is able to notice that there is a situation that maysoon lead to a situation in which no GPRS traffic is going through a PCU. The operator hastime to act according the situation. The operator gets information if the situation led to the

Missing NSEI problem and no traffic is going through the PCU. The operator is able to actaccordingly right away. There is information in the alarms that will help us enhance our SW totackle the problem automaticly in the future.




DN0745995

Operational Aspects: No optionality, no licensing, no depencencies on other features.Feature will be always active, no activation is needed.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC SGS

N

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - OSS4.2 S12ED

1.1.(Y) (Y) - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - - - - - Operating

6.6 24 TRX per BCF for Flexi EDGE BTS


Description: The potential number of TRXs under a single BCF is now increased for the FlexiEDGE BTS from 12 to 24. Note that the maximum number of TRXs under a BTS object is 12.

Operating SW.

Benefits for the Operator: CAPEX and OPEX savings may be realised through reducing thenumber of radio sites necessary.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC


NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexi


CD1S12ED2

.1

- - N N N N N N EP1.1


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y Y - - - - - Operating




DN0745995

6.7 New Counters for Handover Measurement


Summary: The feature BSS20999 provides several counter additions in ‘4 HandoverMeasurement’.

Operating SW.

Current Implementation: For the current implementation, internal handovers which arechanged to MSC controlled due to circuit pool switching or in order to avoid DL muting aremeasured as normal successful external handovers. This then leads to the situation wherethere are more internal handover attempts than successes, even if those handovers that were

started as internal and consequently changed to external were successful. This then meansthat the internal handover success or failure ratio KPIs (Key Performance Indicators) cannot becalculated correctly (the internal handover failure ratio appears to be higher than it really is).

Description: The following counters are now added to the ‘4 Handover Measurement’:

• Counters to count intra-cell, incoming inter-cell and outgoing inter-cell handovers that werechanged to MSC controlled and were successful:

004202 SUCCEEDED BSC I INTERNAL HO TO EXTERNAL

004203 SUCCEEDED BSC O INTERNAL HO TO EXTERNAL

004204 SUCCEEDED INTRA CELL TCH HO TO EXTERNAL

Furthermore, the following additional counters are also provided by the feature capability:

• Counters to count the real success of the packing and unpacking procedures in an intra-cell HO:

004205 HO SUCCEEDED AMR FR TO HR

004206 HO SUCCEEDED AMR HR TO FR

• Counters to count circuit pool switching effects in 3G to 2G handovers:

004207 UNSUCCESS MSC I HO FROM WCDMA RAN DUE POOL SWITCHING

004208 SUCCESS MSC I HO FROM WCDMA RAN CIRCUIT POOL SWITCH




DN0745995

Benefits for the Operator: With this feature, the operator is able to derive more accuratestatistics concerning handover performance by employing these new counters in KPIs.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - OSS4.2 S12

ED2.1

- - - N N Y Y Y Y Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


- - - - - - - Operating




DN0745995

6.8 Statistics for SIGTRAN


Summary: New 661 M3UA Association Set Measurement is introduced for measuringsignaling transport over IP (SIGTRAN).

Operating SW - However, this must be ordered separately, using Sales Item BSC00146.

Current Implementation: SIGTRAN is already supported by the BSC, however, currentlyperformance measurements to follow the functionality and performance of SIGTRAN are notsupported.

Description: With the measurement, it is possible to monitor performance of SIGTRAN oninterfaces of A, Lb as well as BSC-BSC.

The measurement collects information from the M3UA layer and M3UA SCTP layer traffic asshown below:

The M3UA Association Set Measurement collects information for each association. Themeasurement consists of the association set and the association counters. The associationcounters are further divided into M3UA and SCTP counters.

Association set counters:

• 661001 M3UA ASSOCIATION SET UNAVAILABLE TIME

• 661002 M3UA ASSOCIATION SET UNAVAILABLE

M3UA counters of association:

• 661003 M3UA CUMULATIVE UNAVAILABLE TIME

• 661004 M3UA UNAVAILABLE

• 661005 M3UA MESSAGES RECEIVED




DN0745995

• 661006 M3UA MESSAGES SENT

• 661007 M3UA OCTETS RECEIVED

• 661008 M3UA OCTETS SENT

SCTP counters of association:

• 661009 M3UA SCTP PACKETS RECEIVED

• 6610010 M3UA SCTP PACKETS SENT

• 6610011 M3UA SCTP OCTETS RECEIVED

• 6610012 M3UA SCTP OCTETS SENT

• 6610013 M3UA SCTP PACKETS RETRANSMITTED

• 6610014 M3UA SCTP DUPLICATED TRANSMISSION SEQUENCE NUMBERS

Benefits for the Operator: From the counters at the M3UA layer, the operator can follow thetraffic at M3UA associations. The M3UA layer counters tell e.g. what the payload of the M3UAand SCTP connection is.

From the counters at the SCTP layer, the operator can monitor the traffic at the SCTP layerused by the M3UA association. The SCTP layer counters provide more accurate informationon the real load required for sending M3UA traffic through SCTP. The SCTP packetsretransmitted and SCTP duplicated transmission sequence numbers received counters can beused to trace the quality of the IP network. For example, if the counters are increasing, thequality of IP network may be too poor.

The M3UA counters provide availability information for the M3UA connections and otheradditional information concerning the M3UA functionality.

S RUPPOGSM800

TED INGSM900

:GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - OSS4.2 S12

ED2.1

- - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)

HW/FW DEPENDENCY E:: BSS SOFTWARBSCMMI

BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - - - - - Operating 1)

Note: 1) The feature SIGTRAN over A Interface is required (ASW: BSC.1470).




DN0745995

6.9 Flexi EDGE Dual TRX Manual Power Down


Summary: This feature introduces a new MML command at the BSC to enable a powershutdown mechanism for Flexi EDGE BTS Dual TRX modules in order to achieve powersavings.


Description: This feature introduces a new MML instruction to the BSC, which commandsFlexi EDGE BTS Dual TRX modules to power down. The -48V supply to the complete DualTRX module is shut down.

The achieved Power Saving is estimated to be approximately 40 Watts per Dual TRX module.The feature may be employed for Flexi EDGE BTS configurations with 2-6 Dual TRXs (3-12carriers) per cell.

For example, the approximate power savings in the following configurations would be:

4+4+4 shutdown to 2+2+2 = 120 Watts.



12+12 shutdown to 2+2 = 400 Watts.

Benefits for the Operator: During night-time, when TRXs are not heavily utilised, theoperator is able to reduce the power consumption at BTSs through shutting down Flexi EDGEBTS Dual TRX modules. This results in OPEX savings for the operator, especially important inthese times of mounting energy costs and increased Customer environmental awareness.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - - S12

ED3.1

- - - N N N N N N EP1


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - - Dual TRXModule

- - Application




DN0745995

6.10 Multipoint A Load Balancing


Summary: The scope of the existing Multipoint A solution is now enhanced through providingan additional load balancing mechanism, providing the Operator with a greater flexibility ofsolution.


Current Implementation: Currently, the NAS Node Selection routing mechanism for theMultipoint A solution is based upon the loading of the available A-interface circuits. Here, theBSC calculates the average loading of all circuit groups towards the MSCs/MSSs. This is

derived through dividing the number of reserved circuits by the total number of circuitsconfigured on the A-interface. The higher capacity MSCs/MSSs offer a higher number ofavailable circuits and consequently are assigned more subscribers in comparison with lowercapacity MSCs/MSSs.

Description: The existing circuit group loading mechanism will continue to be supported forthose operators who prefer to employ this approach.

However, in networks where unequal VLR capacities are likely to arise, the VLR load within thepool area could become unbalanced unless it is possible to follow the load in the individualVLRs and utilise this to influence the load balancing mechanism in the BSC. In this case thecircuit utilisation rate based mechanism may not provide a sufficiently good solution.

Consequently, the scope of the existing solution is now extended with the new Multipoint ALoad Balancing feature, providing an additional mechanism. The new mechanism is based onthe MSC/MSS capacities (percentage of users directed to each Core Network element), plus anew “weighting factor” parameter which is defined per MSC/MSS at the BSC. A completelyseparate weighting factor value (parameter) is defined for each MSC/MSS. This weightingfactor is then used with a round robin selection. Under certain network conditions this solutionwill then deliver an improved performance. The Operator is able to adjust the weighting factormanually via O&M.

Benefits for the Operator: Operators who have deployed the Multipoint A networkingcapability may now derive additional advantages through the enhanced overall flexibility ofsolution provided.

CAPEX savings arising from the enhanced flexibility and capability provided by this featureextension.

The new extended solution is able to provide an improved End User experience under somenetwork conditions arising from the alternative load sharing mechanism realised with the newcapability provided.




DN0745995

Operational Aspects: The M14 (MSC) software release is required for support of the REL-6load re-distribution capability. In the first phase of this solution (a couple of Periodic LUperiods long) the VLR to be off-loaded should allocate TMSIs with null-NRI and non-broadcast

LAI via an O&M command (MSC/MSS function). This will trigger the terminal to make aLocation Update and consequently it will be re-directed to a new VLR.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y Y 1) OSS4.2

CD Set 1S12ED3.

1

Y 2) - (Y) (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - - - - - Application 3)

NOTES: 1) Multipoint A (Nokia M13).2) Global CN-ID support in CS Paging (SG5.1).3) Multipoint A Interface Application Software is required (SI: BSC00073, ID: BSS20092).




DN0745995

6.11 FOXMEA support for macros and print all counters


Summary: This feature enables a simpler counter enquiry and output information procedurevia the FOXMEA service terminal extension.

Operating SW.

Description: This feature enables the output of all counters of 50 "BSC Level Clear Code", 51"BSC Level Clear Code (PM)" and "57 BSC Level Cleare code (SERLEV)" measurements withthe FOXMEA service terminal extension.

It also supports the output of the counter data for these measurements using the commandprompt mode instead of the menu based user interface. The operator can use commandscripts with the HIT tool when outputting the data. The scripts can be used to automaticallycheck counter values and produce reports.

Additionally, FOXMEA detects the active BCSU and MCMU units and uses those as defaultwhen a counter data inquiry is initiated.

FOXMEA also supports a remote print out of the observations for the service terminal session.

Benefits for the Operator: The feature enables a more immediate and accurate pin pointingof problems within the network using the available counters.

In cases where BSS engineers either do not have access to NetAct or cannot wait until thestandard measurement report is produced, it is possible to use this faster access to thecounter data in order to more quickly address network problems directly from the BSC.

Operational Aspects: This feature enhances the function and usability of the FOXMEAservice terminal extension.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

RNC NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiED

GEY Y Y Y - - S12

ED4.1

- - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - - - - - Operating




DN0745995

7 VALUE ADDED SERVICES

7.1 BSC integrated SMLC capacity


Summary: The ‘BSC integrated SMLC capacity’ - feature is improvement toBSS10012: POSITION BASED SERVICES (PBS) IN BSC - feature. The BSCintegrated SMLC capacity feature improves BSC internal SMLC performance in manyways:

• Better performance in internal SMLC (Architectural improvements in internal SMLC)

• Increased calculation capacity

• Better internal SMLC management and software maintainability in future (removalof unnecessary LCS options and parameters)

• Calculation capacity limiting by BSC SMLC licencing


Description: Improved BSC internal SMLC supports following location methods:

- S9+ (Support for location calculation in GMLC)

- CITA (Cell ID + Timing Advance)

- C-GPS (Conventional Global Positioning System)

Benefits for the Operator: The BSC Integrated SMLC capacity feature improvescalculation capacity in Integrated SMLC.

CAPEX savings because using Location Services of BSS requires no additionalnetwork elements. Internal SMLC supports Cell ID + Timing Advance (CI+TA) andconventional GPS locationing methods. CI+TA is fast, lightweight, and does not needlocation support in the MS. C-GPS is more accurate than SMLC, but slower, andrequires global positioning system in the MS.

Operational Aspects: Existing FIFILE parameters S9_LOCATION_SYSTEM (0701)and PBS_USAGE (0654) are used with integrated SMLC as used in S11.5

Old S11.5 unnecessary LCS options and parameters are removed.

Capacity licence is required for BSC integrated SMLC position capacity forcommercial location services. The licence tells the limit of handled location requests




DN0745995

in integrated SMLC in one second. The sellable step of capacity licence is 5 locationrequests per second. The capacity is averaged over 10 second periods.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexiEDGE

Y Y Y Y - OSS4.1CD1

S12 - - (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y - - 1) - - - Application

NOTE: 1) CP6MX CPUs in both MCMUs (BSCi/BSC2i)



8 TRANSMISSION & TRANSPORT

8.1 FlexiEDGE Abis TRS Grooming


Summary: For more efficient use of Abis, grooming fractional used E1 / T1 Abisframe to save transmission capacity.


Current Implementation: Existing in Nokia UltraSite, Nokia MetroSite and NokiaMetroHub and always part of the solution, in Nokia FlexiEDGE trust based license.

Description: In Nokia FlexiEDGE the transport concept is based on cost efficientconfigurations where only functions which are used are charged, the Grooming Abisefficiency feature will be trust based in BSS12/ EP1.0 which means it is charged butno delivery of SW license is required.

Benefits for the Operator: The feature is only charged if used, improved Abis transmissionefficiency.


DN0745995




DN0745995

Operational Aspects: No SW license file in BSS12/EP1.0, trust based, BSC pool license in

BSS13/ EP2.0.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC

NokiaNetAct

BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexi

EDGEY Y Y Y - OSS4.

1 CD1S12 - - (Y) (Y) (Y) (Y) N (Y) Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW



8.2 FlexiEDGE TRS Loop Protection


Summary: For better availability and reliability of the transmission network. Protectsthe transmission by building loops. If one direction fails it switches over to thealternaive route without traffic break.

Application Software - Sales Item 2003471.

Current Implementation: Existing in Nokia UltraSite, Nokia MetroSite and NokiaMetroHub and always part of the solution, in Nokia FlexiEDGE trust based license asloop slave.

Description: In Nokia FlexiEDGE the transport concept is based on cost efficientconfigurations where only functions which are used are charged, the Loop Protectiontransmission availability feature will be trust based in BSS12/ EP1.0 which means it is

charged but no delivery of SW license is required. Loop protection requires groomingas well.

.



Benefits for the Operator: The feature is only charged if used, protected Abis transmissionavailability.

Operational Aspects: No SW license file in BSS12/EP1.0, trust based, BSC pool license inBSS13/ EP2.0.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MS

C

NokiaNetAct BSC

SGS

N

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSit

e

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexi


CD1S12 - - (Y) (Y) (Y) (Y) N (Y) Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW




DN0745995




DN0745995

8.3 FlexiEDGE Additional 2 E1, T1 IF


Summary: FlexiEDGE offers in total 8 E1 or T1 interfaces on the plug-in card (FIEA,FIPA) where two interfaces are activated. Additional E1 or T1 activation in blocks oftwo can be bought based on trust in BSS12/ EP1.0.


Current Implementation: Nokia UltraSite, Nokia MetroSite and Nokia MetroHuboffer plug-in cards with up to four E1/ T1 interfaces, for more capacity additional HWneeds to be added. Nokia FlexiEDGE offers HW ready up to eight E1/ T1 interfaceswhere two are included in HW price and additional interfaces are trust basedlicenses.

Description: In Nokia FlexiEDGE the transport concept is based on cost efficientconfigurations where only interfaces which are used are charged. Additionaltransmission interfaces are charged trust based in BSS12/ EP1.0 which means it ischarged but no delivery of SW license is required.

Benefits for Operators : Two E1/ T1 interfaces are always included to the HW price, up toeight interfaces are available without HW upgrade, charged on trust base in BSS12/EP1.0.

Operational Aspects: No SW license file in BSS12/EP1.0, trust based, BSC pool licensein BSS13/ EP2.0.

SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MS

C

NokiaNetAct BSC

SGSN

NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaFlexi

EDGE

Y Y Y Y - OSS4.1CD1 S12 - - - - - - - - Y


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW






DN0745995

9 MULTIRADIO INTERWORKING

9.1 TD-SCDMA interworking, idle mode


Description: Idle mode support means that BSC offers needed TD-SCDMA cellparameters for the mobile so that it can make CS and PS cell reselection from the GSMnetwork to the TD-SCDMA network.


SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC


NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaEpsilon

Y Y Y Y (Y) N 1) S12ED1.1

(Y) N (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y N Y N N N N Application

1) BSC S12 release supports TD-SCDMA neighbor maintenance operations only via MML. NetAct support for TD-SCDMA maintenanceoperations will be implemented in future BSC S-releases

9.2 TD-SCDMA incoming HO support

Feature ID : BSS30315

Description: Incoming handover from TDD system is supported when feature TD-SCDMAincoming HO support is active.


SUPPORTED IN:GSM800

GSM900

GSM1800

GSM1900 MSC


NetActPlanner

Nokia2nd Gen.

NokiaTalk-family

NokiaPrimeSite

NokiaMetroSite

NokiaInSite

NokiaUltraSite

NokiaEpsilon

Y Y Y Y (Y) N 1) S12ED1.1

(Y) N (Y) (Y) (Y) (Y) (Y) (Y) (Y)


BTSMMI MS

BSCHW/FW

BTSHW/FW

TCHW/FW

SGSNHW/FW


Y N Y N N N N Application

1) BSC S12 release supports TD-SCDMA neighbor maintenance operations only via MML. NetAct support for TD-SCDMA maintenanceoperations will be implemented in future BSC S-releases




DN0745995

Document Revision History

DATE ISSUE EDITED SUMMARY OF MAIN CHANGES30.12.2004 1.0 A. Kangas BSS12 Program internal version23.5.2005 2.0 A. Kangas BSS12 First customer version13.9.2005 2.1 A. Kangas Update: Compatibility matrix added, HW

requirements confirmed.29.9.2006 2.2.0 Reijo

LyytinenUpdate:

- Document format changed- Sales items added for ASW features- Ch 1: Compatibility matrix updated- Ch 2 updated- Ch 2.7: SIGTRAN added- Ch. 3.1: FlexiEDGE BTS added- Ch 3.2: UltraSite Mini BTS added- Ch 3.3: Pico BTS added- Ch 4.1: DTM description revised- Ch 4.3: EDA description revised- Ch 5.1: SAIC description revised- Ch 5.3: Multipoint A description revised

16.10.2006 2.3.0 ReijoLyytinen

Update:- Ch 1: Compatibility matrix updated

- Ch 2.7: Dependency table added forSigtran


Update:- Ch 7.1: Internal SMLC capacity added- Ch 5.2: STIRC description updated- Ch 2.7: Sigtran over A interface, feature

name changed- For all features: Operator benefits

updated


Update:- Ch 1: Compatibility matrix updated- Ch 1: Operator value added- Ch 4.1: DTM will be available in S12

ED- Ch 5.1 DL DTX Audio Quality added- Ch 7.1 dependency table added for

Internal SMLC capacity- Ch 8.1, 8.2 and 8.3 three FlexiEDGE

Transport features added




DN0745995


Document updated to New Features after S12E5 approval 25 May 2007- Ch 1: Compatibility matrix updated

- Ch 6.1 File Based Plan Provisioning deliveredin S12 ED2.1- Ch 6.1/6.2 PrimeSite BTS does not supportFile Based Plan Provisioning and File BasedConfiguration Upload- Ch 5.2 STIRC description updated- Document identifier added to document infooter- Ch 3.1 FlexiEDGE Sales Item revised- Ch 3.2 FlexiEDGE MHA added- Ch 6.4 MEFICO added


- Ch 6: ED1.1 features Missing NSEI alarmand Cell Barring Parameter for SSPmessag added

- Ch 5: ED1.1 features Disable PowerControl for E911 calls and IncreasedDynamic SDCCH Capacity added

09.11.2007 4.2.0 Paul J.Dawson

- Updates accounting for the BSS12 ED2.1Features:- Load based AMR Packing

- Single MA list for EGSM and PGSM- DFCA RRM Power Reduction- 24 TRX per BCF for Flexi EDGE BTS- New Counters for Handover

Measurement- Statistics for SIGTRAN

- Other minor changes and updates

20.12.2007 4.3.0 Paul J.Dawson

- Updates accounting for the BSS12 ED3.1Features:

- Radio Link Timeout parameter for AMRHR- Flexi EDGE DTRX Manual Power

Down- Multipoint A Load Balancing- LMUB alarm in BSC: Position not

locked (8272)- Other minor changes and updates



13.03.2008 4.3.1 Paul J.Dawson

- Document Title updated- Title and text for feature BSS21261

updated- Sales Item for feature BSS21217 updated- MSC & SGSN Compatability information

corrected28.04.2008 4.4.0 Paul J.

Dawson- Updates accounting for the BSS12 ED4.1

Features:- Intelligent Selective Paging- FOXMEA support for macros and print

all counters- Minor format changes

11_BSS12 New Features

Documents

Transcript of 11_BSS12 New Features