09_rg20 (bss) rg20 (bss) on top features under development

Confidential Nokia Siemens Networks

1 (105)

RG20(BSS) Release and RG20(BSS) on top

Features Under Development Version 2.7.1

Confidential


2 (105)

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is not an official customer document and Nokia Siemens Networks does not take responsibility for any errors or omissions in this document. This document is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted. No part of this documentation may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, that might arise from the use of this document or the information in it. THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THIS DOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT TO REVISE THIS DOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE. This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2010. All rights reserved.


3 (105)

1 Summary of Changes.....................................................................................6

2 Introduction...................................................................................................14

2.1 RG20(BSS) Operator Value..........................................................................15

2.2 RG20(BSS) on top Operator Value..............................................................16

2.3 RG20(BSS) / RG20(BSS) on top Compatibility Information and Matrix ...17

2.4 Hardware Dependency Summary - RG20(BSS) & on top Features ..........22

3 Hardware Product Solutions for the RG20(BSS) Release.........................25

3.1 BSC Hardware Requirements......................................................................25

3.2 Transcoder Hardware Requirements ..........................................................26

3.3 PCU Hardware Requirements......................................................................26

3.4 BSC Hardware Requirements for new Software Features ........................27

3.5 Flexi BSC Capacity Evolution......................................................................29

3.6 TCSM3i Capacity Evolution .........................................................................30

4 Hardware Product Solutions for RG20(BSS) on top..................................31

4.1 BSC Hardware Requirements......................................................................31

4.2 Transcoder Hardware Requirements ..........................................................32

4.3 PCU Hardware Requirements......................................................................32

4.4 BSC Hardware Requirements for new Software Features ........................32

4.5 Multicontroller BSC / Transcoder................................................................33


4 (105)

5 Software Product Solutions - Features Under Development....................39

5.1 Radio Network Performance........................................................................39 5.1.1 Energy optimised TCH Allocation .......................................................................... 39 5.1.2 OSC Half Rate with SAIC MS ................................................................................ 41 5.1.3 Circuit Switched Dynamic Abis Pool ...................................................................... 46 5.1.4 Merged P- & E-GSM900 ........................................................................................ 48 5.1.5 OSC Full Rate with SAIC MS................................................................................. 50 5.1.6 8k TRAU for OSC AMR FR.................................................................................... 52 5.1.7 Random Fill Bits..................................................................................................... 53 5.1.8 DFCA support for OSC .......................................................................................... 54 5.2 Packet Switched Data...................................................................................56 5.2.1 DL DC Territory Procedures .................................................................................. 56 5.2.2 TRX Specific Link Adaptation for DLDC ................................................................ 57 5.2.3 Inter-BSC NACC .................................................................................................... 58 5.2.4 Inter System NACC................................................................................................ 60 5.2.5 Inter System NACC for LTE................................................................................... 61 5.3 Transmission & Transport ...........................................................................63 5.3.1 A over IP ................................................................................................................ 63 5.3.2 Abis Delay Measurement (TDM, PWE3)................................................................ 66 5.3.3 Packet Abis over IP/Ethernet ................................................................................. 67 5.3.4 Packet Abis over TDM ........................................................................................... 68 5.3.5 Packet Abis over Satellite ...................................................................................... 69 5.3.6 Packet Abis Security .............................................................................................. 69 5.3.7 Packet TRS for UltraSite / BTSplus ....................................................................... 70 5.3.8 Packet Abis Congestion Reaction.......................................................................... 71 5.3.9 Local Switching for Packet Abis............................................................................. 72 5.3.10 Packet Abis Sync. ToP IEEE1588v2 ..................................................................... 73 5.3.11 Packet Abis Synchronous Ethernet ....................................................................... 74 5.3.12 Packet Abis Delay Measurement........................................................................... 75 5.3.13 FlexiPacket Radio Connectivity ............................................................................. 76 5.3.14 Packet Abis IP/TDM Aggregation .......................................................................... 78 5.3.15 BS2xx@Flexi BSC Enhanced Satellite Support .................................................... 79 5.3.16 Packet Abis Network Media conversion................................................................. 80


5 (105)

5.4 Operability.....................................................................................................81 5.4.1 PCU Restart Handling............................................................................................ 81 5.4.2 Automatic EDAP Reallocation in PCU ................................................................... 81 5.4.3 Energy saving mode for BCCH TRX...................................................................... 83 5.4.4 Fast BSS Restart ................................................................................................... 84 5.4.5 Flexi BTS Autoconnection...................................................................................... 86 5.4.6 Flexible Frame Offset Management....................................................................... 87 5.4.7 Segment name modification via FBPP .................................................................. 88 5.4.8 User configurable FHO time limit for FBPP............................................................ 89 5.4.9 Extended Cell function for Multiradio BTS ............................................................. 90 5.4.10 Precise Rx Level Measurement ............................................................................. 91 5.4.11 Precise Timing Advance Measurement ................................................................. 91 5.4.12 Precise Power Level Measurement ....................................................................... 92 5.4.13 Adjacent Cell Rx Level Measurement.................................................................... 93 5.4.14 Air Path Loss Measurement................................................................................... 94 5.5 Multiradio Interworking ................................................................................95 5.5.1 LTE System Information ........................................................................................ 95 5.5.2 RF Sharing GSM - LTE.......................................................................................... 97 5.5.3 IMSI-based Handover ............................................................................................ 98 5.5.4 GSM - WCDMA Interworking ................................................................................. 98 5.6 Site Solutions................................................................................................99 5.6.1 Cositing with BS2xx ............................................................................................... 99 5.6.2 Integrated IP card for BSC and TCSM................................................................. 101 5.6.3 BS2xx Loop Protection with Flexi BSC ................................................................ 102 5.6.4 Flexi Multiradio 10 BTS........................................................................................ 103 5.7 Location Services.......................................................................................104 5.7.1 Geo-Redundant SMLC over Multi-Homed Lb Interface ....................................... 104


6 (105)

1 Summary of Changes

DATE ISSUE EDITED SUMMARY OF MAIN CHANGES 09.05.2008 1.0.0 Paul J.

Dawson Initial version.

09.06.2008 1.0.1 Paul J. Dawson

General updates and corrections.

Feature BSS21238, Merged P- & E-GSM900 included.

07.07.2008 1.0.2 Paul J. Dawson

Format update.

General updates and corrections for feature descriptions.

29.10.2008 1.1.0 Paul J. Dawson

Document title and corresponding feature description updates included.

New Features (and descriptions) included:

BSS21454, Packet Abis over IP/Ethernet BSS21440 , Packet Abis over TDM

(MLPPP)

BSS21438 , Packet Abis over Satellite BSS21444 , Packet Abis Security BSS21443 , Packet TRS for UltraSite /

BTSplus

BSS21445, Packet Abis Congestion reaction

Updates for Feature:

BSS21288, GSM/EDGE - LTE Interworking

11.11.2008 1.1.1 Paul J. Dawson

Compatibility information for features BSS21443 and BSS21445 corrected.


7 (105)

18.12.2008 1.2.0 Paul J. Dawson

New Features (plus descriptions) included into the RG20 Release:

BSS20083, Inter-BSC NACC BSS21045 , Inter System NACC BSS21355 , Inter System NACC for LTE

Features removed from the RG20 Release:

BSS21345, QoS Streaming BSS20708, Packet Switched Handover

and document aligned correspondingly.

13.03.2009 1.3.0 Paul J. Dawson

General updates. Compatibility information for features BSS21309, BSS21343, BSS21392 updated.

Features (plus descriptions) included into the RG20 Release:

BSS21232, Automatic EDAP Reallocation in PCU

BSS21327, Local Switching for Packet Abis

Features removed from the RG20 (BSS) Release:

BSS21335, Precise Paging BSS21361, Dynamic PCU2 Pooling

and document aligned correspondingly.


8 (105)

30.06.2009 2.0.0 Paul J. Dawson

Document Title updated. BSS21440 Feature Title updated.

Features (plus descriptions) included into the RG20 (BSS) Release:

BSS21439, Packet Abis Sync. ToP IEEE1588v2

BSS30450, Packet Abis Synchronous Ethernet

BSS21353, LTE System Information (replaces BSS21288)

Features removed from the RG20 (BSS) Release:

BSS21288, GSM/EDGE - LTE Interworking (replaced with BSS21353)

Chapter 2 extended and Compatibility Information included.

Chapter 3 extended and Hardware Dependency Information included.

General updates for the RG20 (BSS) features.

24.09.2009 2.1.0 Paul J. Dawson

Compatibility information for feature BSS21309 updated.

AoIP Feature ID information updated.

Description for features BSS20083, BSS21045 and BSS21443 updated.

Feature (plus description) included into the RG20 Release:

BSS30395, Packet Abis Delay Measurement


9 (105)

30.11.2009 2.2.0 Paul J. Dawson

Compatibility Information for all features and Section 2.2 Compatibility Matrix updated.

New Summary Tables 1 and 2 included.

Feature Title updated for BSS21316 and BSS21309.

Features (plus description) included into the RG20 Release:

RG301397, Cositing with BS2xx BSS21503, FlexiPacket Radio Connectivity

05.03.2010 2.3.0 Paul J. Dawson

Section 2, Introduction, has been updated.

Section 3, Hardware Product Solutions, has been updated and Table 7 included.

Compatibility Information for the features BSS21341, BSS30380, BSS21454 and BSS21440 updated.

Description for feature BSS21353 has been updated, accounting for feature support in RG10 (BSS) EP Release (Note: There is no change from the earlier defined RG20 capability).

Description and Compatibility Information for features BSS21309 and RG301397 updated.

Features (plus description) included into the RG20 Release:

BSS30385, Circuit Switched Dynamic Abis Pool

BSS21498, Geo-Redundant SMLC over Multi-Homed Lb Interface

Support extended to the BTSplus Base Station type for the RG10 (BSS) features:

BSS20958 , Energy saving mode for BCCH TRX

BSS21157, Integrated IP card for BSC and TCSM

Tables 1 and 2 updated, correspondingly.


10 (105)

14.05.2010 2.4.0 Paul J. Dawson

General update to all relevant sections accounting for the RG25 (BSS) Release.

Section 4, RG25 (BSS) Hardware information, has been added.

Logistics and Compatibility Information for the feature BSS21309 updated.

Compatibility Information for the feature BSS30385 updated.

Summary updated for feature BSS30380.

Features (plus description) included into the RG25 (BSS) Release:

BSS21534, OSC Full Rate with SAIC MS BSS21325, 8k TRAU for OSC AMR FR BSS21520, RF Sharing GSM - LTE BSS21539, Packet Abis IP/TDM

Aggregation

RG601668, BS2xx Loop Protection with Flexi BSC

Support extended to the BTSplus Base Station type for the features:

BSS12158, IMSI-based Handover BSS10101, GSM - WCDMA Interworking


29.06.2010 2.5.0 Paul J. Dawson

Minor text corrections.

Compatibility Matrix (Section 2.3) extended with full details for RG25 (BSS).

Feature Title updated for BSS21392.

Description for features BSS21353 and BSS21355 have been updated.

BSS21327, Local Switching for Packet Abis re-allocated to RG25 (BSS). Compatibility Information updated.

BSS21299, High Symbol Rate in DL (REDHOT-B) and BSS21298, High Symbol Rate in UL (HUGE-B) re-allocated to RG30 (BSS).



11 (105)

28.09.2010 2.6.0 Paul J. Dawson


Section 2.3, RG20 (BSS) Compatibility Information and Matrix with NetAct updated to OSS5.2 MP1.


BSS101583, Precise Rx Level Measurement

BSS101584, Precise Timing Advance Measurement

BSS101585, Precise Power Level Measurement

BSS101586, Adjacent Cell Rx Level Measurement

Feature (plus description) included into the RG20 (BSS) MP1.0 Release:

BSS21388, Random Fill Bits



12 (105)

30.11.2010 2.7.0 Paul J. Dawson


General update to all relevant sections accounting for the Multicontroller BSC/ Transcoder.

Section 2.3, Compatibility Information and Matrix updated.

Description and Compatibility Information for feature BSS21539 updated.

Compatibility Information for features BSS21309, BSS21534, BSS21341/BSS30380, BSS21454 and BSS21440 updated.

Operational Aspects section introduced for feature BSS21355.


BSS21530, Multicontroller BSC BSS21530, Multicontroller Transcoder BSS21391, DFCA support for OSC RG301587, BS2xx@Flexi BSC Enhanced

Satellite Support

BSS101414, Packet Abis Network Media conversion

BSS101621, Flexi Multiradio 10 BTS BSS101570, Segment name modification

via FBPP

BSS101469, User configurable FHO time limit for FBPP

BSS101482, Extended cell function for Multiradio BTS

BSS101574, Air Path Loss Measurement



13 (105)

10.12.2010 2.7.1 Paul J. Dawson


Document Title updated.

RG20(BSS) on top naming introduced, replacing RG25(BSS).

Sections 3.1 and 4.1, BCSU memory requirement updated.

Compatibility Information for features BSS21454 and BSS21440 updated.

Table 3 corrected.

2 Introduction

This document describes the Features Under Development for the Base Station Subsystem (BSS) release RG20(BSS) and RG20(BSS) on top.

The Nokia Siemens Networks release RG20(BSS) provides advantages for all operators, through supporting:

Voice Capacity / Spectral Efficiency Enhancements - maximising the utilisation of the existing infrastructure and providing CAPEX / OPEX efficient capacity upgrade solutions through the unique OSC (Orthogonal Sub Channel) capability.

CAPEX / OPEX Efficient Enhanced Transport solutions - achieved through employing the Packet Abis and AoIP Solutions.

Extended BTS Energy Saving solutions - beyond those already realised in the RG10(BSS) Release.

Enhanced GSM/EDGE-LTE Interworking - Providing coverage continuity and an improved end user experience. Maximising the use of existing GSM/EDGE resources and employing support for NACC (Network Assisted Cell Change).

EDGE Evolution - Building upon the existing RG10(BSS) Downlink Dual Carrier solution.

RG20(BSS) on top builds upon the capabilities provided by RG20(BSS), enhancing the value through extending the OSC function to include OSC Full Rate and thus improving network Quality. Packet Abis IP/TDM Aggregation saves CAPEX/OPEX costs through enabling an even greater transmission efficiency for Packet Abis over TDM configurations. Local Switching for Packet Abis further reduces the Abis bandwidth requirement and CAPEX/OPEX savings are also reflected in the GSM-LTE Interworking extension. In addition, the new features introduced for the BTSplus Base Station type provide an even greater level of function across the network (for Operators with this configuration scenario).

Furthermore, RG20(BSS) on top introduces the new Multicontroller BSC / Transcoder and Flexi Multiradio 10 BTS solutions.


15 (105)

2.1 RG20(BSS) Operator Value BSC & TCSM Solution: The BSC / Transcoder solution for the RG20(BSS) Release provides enhancements to the product capacity as well as the optional new interface modules to support the Packet Abis and A over IP feature capabilities.

BTS Solution: With RG20(BSS), the Flexi BTS Autoconection feature enables faster and more efficient rollouts and also OPEX savings in normal operation. Furthermore, the Flexi EDGE BTS provides the necessary interfacing for the Orthogonal Sub Channel (OSC) and Packet Abis capabilities.

Radio Network Performance: The Orthogonal Sub Channel (OSC) feature provides enhancements to a number of key network aspects, addressing capacity, spectral efficiency and coverage. In addition, it is a key OPEX saving enabler. Yet further spectral efficiencies may be realised through the Merged P- and E-GSM900 capability.

Transmission Solutions: The Packet Abis and A over IP features introduced with RG20(BSS) enable IP Networking for both the Abis- and A-Interfaces. They realise capacity (via an integrated Abis Optimization) and CAPEX/OPEX savings; increase flexibility and enable a simpler network operation / maintenance. Beyond this, FlexiPacket Radio Connectivity extends the unique Nokia Siemens Networks Zero Footprint Flexi-based solution.

Operability: The Fast BSS Restart feature enables a significant reduction in BSS downtime and consequently acts to increase network availability and of course revenue. The Automatic EDAP Reallocation in PCU and PCU Restart Handling features reduce OPEX and increase PCU availability, also acting to boost revenue.

Packet Switched Data: NACC reduces the service outage during cell changes, enhancing the performance for services that require higher throughput or shorter delays. The Dual Carrier in Downlink feature enhancements enable throughput performance increases and improve the efficiency of the PCU allocation.

Multi-radio Interworking: NACC support for WCDMA and LTE reduce the service outage for multi-RAT interworking. Furthermore, NACC with LTE may be used (where RIM is supported) as an extension for the CS Fallback Voice Call Continuity solution. Basic LTE interworking with GSM/EDGE provides continuity of coverage in the network.

Energy Savings: Amongst the other key advantages indicated above, the Orthogonal Sub Channel (OSC) feature enables energy (OPEX) savings through reducing the number of TRXs and combining losses. In addition, the feature Energy optimised TCH Allocation further enhances the possible OPEX savings.


16 (105)

2.2 RG20(BSS) on top Operator Value BSC & TCSM Solution: RG20(BSS) on top introduces the Multicontroller BSC / Transcoder application on top of the new scalable multipurpose Multiradio Controller Platform. It realises a revolutionary, highly scalable and high capacity solution, providing a future-proof BSC / Transcoder implementation for all IP-based networks. Support for up to 4,400 TRX and up to 26,400 Erlangs is provided. The Multicontroller BSC / Transcoder application on top of the Multiradio Controller Platform extends the existing Nokia Siemens Networks Single RAN solution.

BTS Solution: RG20(BSS) on top extends support for the RG20(BSS) / RG20(BSS) on top feature set to the Multiradio BTS. Furthermore, support for the BTSplus is further enhanced with the Loop Protection feature (amongst others), which increases network redundancy and availability, ensuring revenue flow. Importantly, support for OSC Full Rate and Half Rate is now also provided for the UltraSite BTS, extending the advantages provided by OSC utilisation to a potentially wider network area. The Extended Cell solutions are also introduced for the Flexi Multiradio BTS. Additionally, support for the the new Flexi Multiradio 10 BTS solution is provided.

Radio Network Performance: With RG20(BSS) on top, the OSC Solution is extended to include OSC Full Rate, enhancing Quality within the network. It enables the same capacity as AMR Half Rate, but achieves this with a higher MOS quality. With the 8k TRAU feature, the Operator is able to introduce OSC Full Rate into the network without having to modify the existing legacy Abis transmission solution. Through combining OSC with DFCA (Dynamic Frequency and Channel Allocation), the OSC channel specific requirements may now be accounted for during optimisation of the radio channel, training sequence and user pair selections.

Transmission Solutions: Packet Abis IP/TDM Aggregation builds upon the RG20(BSS) Packet Abis solution, realising further capacity savings via statistical multiplexing gains. Local Switching for Packet Abis continues this approach and provides mechanisms to yet further reduce the Abis bandwidth requirement.

Multi-radio Interworking: GSM-LTE Concurrent Mode operation deepens the support for LTE, realising CAPEX savings through hardware sharing and reducing OPEX costs via the modular solution. Critically, flexibility is also increased, enabling a faster, more flexible and simpler migration to LTE.


17 (105)

2.3 RG20(BSS) / RG20(BSS) on top Compatibility Information and Matrix Where applicable and in general, the RG20(BSS) and RG20(BSS) on top software features are managed via Licence Key. A summary table is included below:

Feature ID Feature Licence Key BSS21309 OSC Half Rate with SAIC MS Y

BSS30385 Circuit Switched Dynamic Abis Pool Y

BSS21222 Energy optimised TCH Allocation Y

BSS21238 Merged P- & E-GSM900 Y

BSS21343 DL DC Territory Procedures N*

BSS21392 TRX Specific Link Adaptation for DLDC N*

BSS20083 Inter-BSC NACC Y

BSS21045 Inter System NACC Y

BSS21355 Inter System NACC for LTE Y

BSS21353 LTE System Information Y

BSS21368 Flexi BSC Capacity Evolution N

BSS21371 TCSM3i Capacity Evolution N

RG301397 Cositing with BS2xx N

BSS21341 A over IP, Transcoder in BSS Y

BSS30380 A over IP, Transcoder in MGW Y

BSS21454 Packet Abis over IP/Ethernet Y

BSS21440 Packet Abis over TDM Y

BSS21438 Packet Abis over Satellite Y

BSS21444 Packet Abis Security Y

BSS21443 Packet TRS for UltraSite / BTSplus Y

BSS21445 Packet Abis Congestion reaction N*

BSS21327# Local Switching for Packet Abis Y

BSS21439 Packet Abis Sync. ToP IEEE1588v2 Y

BSS30450 Packet Abis Synchronous Ethernet Y

BSS21271 Abis Delay Measurement (TDM, PWE3) Y

BSS30395 Packet Abis Delay Measurement Y

BSS21503 FlexiPacket Radio Connectivity N

BSS21316 Flexi BTS Autoconnection Y

BSS20045 PCU Restart Handling N

BSS21232 Automatic EDAP Reallocation in PCU N

BSS21362 Fast BSS Restart N

BSS21498 Geo-Redundant SMLC over Multi-Homed Lb Interface

N*


18 (105)

Feature ID Feature Licence Key BSS101583 Precise Rx Level Measurement Y

BSS101584 Precise Timing Advance Measurement Y

BSS101585 Precise Power Level Measurement Y

BSS101586 Adjacent Cell Rx Level Measurement Y

BSS21388 Random Fill Bits N*

BSS21534# OSC Full Rate with SAIC MS Y

BSS21325# 8k TRAU for OSC AMR FR Y

BSS21520# RF Sharing GSM - LTE Y

BSS21539# Packet Abis IP/TDM Aggregation Y

RG601668# BS2xx Loop Protection with Flexi BSC N

BSS21530# Multicontroller BSC N

BSS21530# Multicontroller Transcoder N

BSS21391# DFCA support for OSC N*

RG301587# BS2xx@Flexi BSC Enhanced Satellite Support

N

BSS101414# Packet Abis Network Media conversion N

BSS101621# Flexi Multiradio 10 BTS Y

BSS101570# Segment name modification via FBPP N

BSS101469# User configurable FHO time limit for FBPP

N

BSS101482# Extended cell function for Multiradio BTS

N*

BSS101574# Air Path Loss Measurement Y

* The dependant feature(s) is(are) Licence Key Managed. # The feature is supported from RG20(BSS) on top.

Table 1: Licence Key Managed Feature Summary for RG20(BSS) & RG20(BSS) on top.


19 (105)

The compatibility of the NE releases for RG20(BSS) and RG20(BSS) on top is as follows:

RG20(BSS) consists of the releases: BSC S15; MetroSite CXM8.0; UltraSite CX8.0; Flexi EDGE EX4.0 and BTSplus BRG2.

RG20(BSS) is supported by the following NE releases: NetAct OSS5.2 MP1; MSC M15 and SGSN SG8.

RG20(BSS) on top consists of the releases: BSC S15 EPx.0; MetroSite CXM8.1; UltraSite CX8.1; Flexi EDGE EX4.1; Flexi Multiradio EX4.1 and BTSplus BRG2.1.

Also within RG20(BSS) on top: mcBSC S15 2.x *; Flexi EDGE EX4.1 and Flexi Multiradio EX4.1

RG20(BSS) on top is supported by the following NE releases: NetAct OSS5.3 CD Set 2; MSC M14.6 and SGSN SG8.

* Supporting the RG20(BSS) Feature Set (with RF Sharing GSM - LTE on top), and where the Flexi EDGE & Flexi Multiradio BTSs are connected via Packet Abis over IP/Ethernet (all interfacing is IP based).

Concerning the BSC / Transcoder, the upgrade from RG20(BSS) to RG20(BSS) on top will be like an EP Release upgrade. Note that the respective BTSs also need to be upgraded in order that the new functionality provided in RG20(BSS) on top can be supported.

The BSCi / BSC2i / TCSM2 and Talk Family BTS systems are compatible (supported) by the RG20(BSS) Release. Also, the new RG20(BSS) features are not supported by the Transcoder TCSM2 and Talk Family BTSs.

The BSCi / BSC2i and TCSM2 and Talk Family BTS systems are compatible (supported) by RG20(BSS) on top. Also, the new RG20(BSS) on top features are not supported by the Transcoder TCSM2 and Talk Family BTSs.


20 (105)

The standardisation baseline of the RG20(BSS) release and RG20(BSS) on top is 3GPP Release 8, Meeting #41.


21 (105)

Notations used in the dependency tables:

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

BSS BSC DX200

Platform BTS Ultra Site

BTS Metro Site

BTS Talk

Family

BTS Flexi EDGE

BTS Flexi

Multiradio

BTS BTSplus

NetAct SGSN MSC RAN MS Licensing

Release - - - - - - - - - - - - - - - In the table we use the following notations: SUPPORTED IN: MSC This feature is supported in the MSC (xxx = MSC

release/feature no) N = No, - = no dependency, X = support required but release not defined.

DX200 Platform

This feature is supported by DX200 Platform (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined.

NetAct This feature is supported in the NetAct (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined.

BSC This feature is supported by the BSC (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined...

MS The feature sets special requirements to mobile stations (xxx = 3GPP release), - = no dependency, X = support required but release not defined.

SGSN This feature is supported by the SGSN (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined.

Talk-family

This feature is supported by Talk-family BTS (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined.

HW/FW DEPENDENCY:

UltraSite This feature is supported by UltraSite BTS (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined

BSC HW/FW

This feature requires additional or alternative BSC hardware or firmware

MetroSite This feature is supported by MetroSite BTS (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined.

BTS HW/FW

This feature requires additional or alternative BTS hardware or firmware

Flexi EDGE

This feature is supported by Flexi EDGE BTS (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined

TC HW/FW This feature requires additional or alternative Transcoder hardware or firmware

Flexi Multiradio

This feature is supported by Flexi Multiradio BTS (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined

SGSN HW/FW

This feature requires additional or alternative SGSN hardware or firmware

BTSplus This feature is supported by BTSplus BTS (xxx = release/feature no) N = No, - = no dependency, X = support required but release not defined

Licensing

BSS Licensing: Provides information on the method of Licence Control.


22 (105)

2.4 Hardware Dependency Summary - RG20(BSS) & on top Features A summary list of the BSS and MS Hardware Dependancies is included in the table below:

Feature ID Feature BSC TSCM BTS MS

BSS21309 OSC Half Rate with SAIC MS - - FE, FM, UltraSite # Rel.6

BSS30385 Circuit Switched Dynamic Abis Pool - - FE, FM, UltraSite # -

BSS21222 Energy optimised TCH Allocation - - - -

BSS21238 Merged P- & E-GSM900 - - - EGSM 900

BSS21343 DL DC Territory Procedures - - - Rel.7

BSS21392 TRX Specific Link Adaptation for DLDC - - - Rel.7

BSS20083 Inter-BSC NACC - - - Rel.5

BSS21045 Inter System NACC - - - Rel.5

BSS21355 Inter System NACC for LTE - - - Rel.8

BSS21353 LTE System Information - - - Rel.8

BSS21368 Flexi BSC Capacity Evolution Flexi BSC - - -

BSS21371 TCSM3i Capacity Evolution - TCSM3i - -

RG301397 Cositing with BS2xx - - FE, FM -

BSS21341 A over IP, Transcoder in BSS - TCSM3i - -

BSS30380 A over IP, Transcoder in MGW

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21454 Packet Abis over IP/Ethernet

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21440 Packet Abis over TDM

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21438 Packet Abis over Satellite

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21444 Packet Abis Security

BSC3i 1000/2000

or Flexi BSC

- FE, FM -


23 (105)


BSS21443 Packet TRS for UltraSite / BTSplus

BSC3i 1000/2000

or Flexi BSC *

- UltraSite, BTSplus -

BSS21445 Packet Abis Congestion reaction

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21327# Local Switching for Packet Abis

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21439 Packet Abis Sync. ToP IEEE1588v2

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS30450 Packet Abis Synchronous Ethernet

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21271 Abis Delay Measurement (TDM, PWE3)

BSC3i 1000/2000

or Flexi BSC *

- FE, FM -

BSS30395 Packet Abis Delay Measurement

BSC3i 1000/2000

or Flexi BSC

- FE, FM -

BSS21503 FlexiPacket Radio Connectivity - - FE, FM -

BSS21316 Flexi BTS Autoconnection - - FE, FM -

BSS20045 PCU Restart Handling - - - -

BSS21232 Automatic EDAP Reallocation in PCU - - - -

BSS21362 Fast BSS Restart - - - -

BSS21498 Geo-Redundant SMLC over Multi-Homed Lb Interface - - - -

BSS101583 Precise Rx Level Measurement - - - -

BSS101584 Precise Timing Advance Measurement - - - -

BSS101585 Precise Power Level Measurement - - - -

BSS101586 Adjacent Cell Rx Level Measurement - - - -

BSS21388 Random Fill Bits - - UltraSite, FE, FM -


24 (105)


BSS21534# OSC Full Rate with SAIC MS - - FE, FM, UltraSite Rel.6

BSS21325# 8k TRAU for OSC AMR FR - - FE, FM, UltraSite -

BSS21520# RF Sharing GSM - LTE - - FM -

BSS21539# Packet Abis IP/TDM Aggregation

BSC3i 1000/2000

or Flexi BSC

- FE -

RG601668# BS2xx Loop Protection with Flexi BSC - - BTSplus -

BSS21530# Multicontroller BSC mcBSC mcTranscoder FE, FM -

BSS21530# Multicontroller Transcoder mcBSC mcTranscoder FE, FM -

BSS21391# DFCA support for OSC - - FE, FM, UltraSite Rel.6

RG301587# BS2xx@Flexi BSC Enhanced Satellite Support - - BTSplus -

BSS101414# Packet Abis Network Media conversion

BSC3i 1000/2000, Flexi BSC,

or mcBSC

- FE, FM -

BSS101621# Flexi Multiradio 10 BTS - - - -

BSS101570# Segment name modification via FBPP - - - -

BSS101469# User configurable FHO time limit for FBPP - - - -

BSS101482# Extended cell function for Multiradio BTS - - FM -

BSS101574# Air Path Loss Measurement - - - - Key: FE - Flexi EDGE BTS FM - Flexi Multiradio BTS (Features supported from RG20(BSS) on top). * - For the integrated CESoPSN solution # - The feature is supported from RG20(BSS) on top.

Table 2: Hardware Dependency Summary for the RG20(BSS) and on top Features.


25 (105)

3 Hardware Product Solutions for the RG20(BSS) Release As indicated at an earlier stage, with the C3 of the RG20(BSS) Release, a confirmation of the product hardware related requirements can be provided and has been communicated through the BSC Hardware Technical Note - TS-BSC-HW-0178.

In addition, Technical Note TS-BSC-HW-0181 details the new Hardware Items that have been developed for the BSC and Transcoder Products and which are supported at the new S15 - RG20(BSS) - Software Release level.

The BSCi / BSC2i / TCSM2 and Talk Family BTS systems are compatible (supported) by the RG20(BSS) Release. Also, the new RG20(BSS) features are not supported by the Transcoder TCSM2 and Talk Family BTSs.

3.1 BSC Hardware Requirements Beyond the Flexi BSC and BSC3i, the BSCi and BSC2i support the RG20(BSS) software release. Some functions - such as the ETP / ETP-A module required for the Packet Abis and A over IP features - are available only for the Flexi BSC, BSC3i 1000/2000 and additionally for the TCSM3i.

The RG20(BSS) Release sets the same mandatory minimum hardware requirement as per the RG10(BSS) Release, described below:

Minimum CPU Memory Size:

Is generally as per the RG10(BSS) Release. However, certain software products set additional requirements for the BSC Hardware

Flexi BSC has 1 GB in all units as standard BSC3i 660: 512 MB in BCSU, 1 GB in MCMU and OMU BSC3i 1000/2000: 512 MB in BCSU (except in scenarios where the ETP

and Packet Abis is employed, where it is then 1GB), 1 GB in MCMU and OMU. In general, 1GB for all units is recommended

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

Minimum Hard Disk Size:

Is as per the BSS13 and RG10(BSS) Releases BSC3i: 9GB BSCi and BSC2i: 4GB


26 (105)

Typical Minimum O&M Link Capacity Requirement:

Is as per the BSS13 and RG10(BSS) Releases BSC3i 2000: minimum 1024 kbit/s, recommended 2048 kbit/s BSC3i 1000: minimum 512 kbit/s, recommended 1024 kbit/s BSCi, BSC2i, BSC3i 660: minimum 256 kbit/s, recommended 512 kbit/s

Please note that the figures presented above are calculated estimates that have not yet been confirmed in live usage and consequently changes may potentially arise.

Please also note that some deviation to these figures may exist arising from the number of managed objects under the BSC, the activated features, customer specific data collection settings, work processes, etc

A LAN-based O&M connection is currently recommended for all product configurations and is the most powerful link option method. Alternatively, a digital X.25 connection is still feasible when multiple 64kbit/s timeslots are employed. LAN interfaces are mandatory for data speeds higher than 1024 kbit/s. As for the earlier BSS13 software release, an analog X.25 connection with limited link capacity is no longer available with the BSC3i 1000/2000 configuration; and as for the earlier RG10(BSS) release, with the Flexi BSC only a LAN based connection is supported.

Please also note that in BSCi and BSC2i the O&M LAN interface requires IP cabling and CPLAN panels as well as external LAN switches and/or routers.

3.2 Transcoder Hardware Requirements Beyond the TCSM3i, the TCSM2 supports the base RG20(BSS) software release. Note that the new transcoder related capabilities are only supported by the TCSM3i.

3.3 PCU Hardware Requirements The PCU1 is supported by the RG20(BSS) release. The new packet data related software features listed below will require the PCU2.


27 (105)

3.4 BSC Hardware Requirements for new Software Features As for previous software releases, certain software products set additional requirements for the BSC hardware. An initial hardware requirement for the new RG20(BSS) software features is listed in the following table:

The PCU2 Plug-in unit is a mandatory hardware requirement for: DL DC Territory Procedures TRX Specific Link Adaptation for DLDC Inter-BSC NACC Inter System NACC Inter System NACC for LTE Packet Abis over IP/Ethernet * Packet Abis over TDM * Cositing with BS2xx

* Including any dependant features.

Table 3: Initial PCU2 Hardware requirements for RG20(BSS) software features.

Furthermore:

The ETP Plug-in unit (for Flexi BSC / BSC3i 1000/2000) is a mandatory hardware requirement for:

Packet Abis over IP/Ethernet Packet Abis over TDM Packet Abis over Satellite

Table 4: Initial BSC Hardware requirements for RG20(BSS) software features.

Also:

The ETP-A Plug-in unit (for Flexi BSC, BSC3i 1000/2000 and TCSM3i) is a mandatory hardware requirement for:

A over IP



28 (105)

Additionally:

A new version of the ETS2 (STM-1) module is required for:

Packet Abis over TDM


Finally:

An additional pair of LAN Switch (ESB24-D) Modules (i.e. 2x ESB24-D Modules) is a mandatory requirement for the BSC3i 1000/2000 or Flexi BSC in order to interconnect ETP and / or ETP-A Modules for:

Packet Abis over IP/Ethernet Packet Abis over TDM Packet Abis over Satellite A over IP


Hardware requirements for the software features introduced in earlier software releases should be reviewed separately.


29 (105)

3.5 Flexi BSC Capacity Evolution Feature ID: BSS21368 Summary: The Flexi BSC was introduced with the RG10(BSS) Release to complement the existing members of the Flexi BSC product family - The BSC3i 660 and the BSC3i 1000/2000. The Flexi BSC is designed to provide both a leading capacity and low power consumption in a single cabinet solution and is fully flexible in capacity and connectivity dimensioning. With the RG20(BSS) Release, this evolution is continued through the introduction of a new Intel CPU enabling the capacity to be further extended to support up to 4200 TRXs in one single cabinet. Benefits for the Operator: Every aspect of the Flexi BSC contributes to its high operational efficiency. The solution offers a unique level of capacity efficiency - being the only BSC in the marketplace to support up to 4200 TRXs in one cabinet, whilst providing the highest traffic handling capacity of 25000 Erlang. Additionally, it offers a new level of efficiency in transmission, through enabling the Packet Abis and A over IP functions through the new ETP / ETP-A modules - which can be also be used in the BSC3i 1000/2000 and TCSM3i. The Flexi BSC, through offering full flexibility in configuration for different transmission media will enable the operator to realise the most cost efficient solution for their requirements. Functional Description: The new Flexi BSC configuration supports very high TRX configurations with up to 4200 TRXs in an extremely compact, single cabinet solution. Along with support for Circuit Switched traffic, it supports Packet Switched services with up to 30 720 Abis links (16kbit/s). Scalability and flexibility are the key drivers allowing the tuning of the capacity and transmission connectivity to the specific levels required by the operator. The Flexi BSC is based on the DX200 distributed processor platform, which efficiently evolves with the available commercial Intel processing power; and the distributed architecture enables the solution to meet new and evolving requirements. All earlier BSCs of the Flexi BSC product family (BSC3i 660, BSC3i 1000/2000 and the Flexi BSC from RG10(BSS) ) may optionally be upgraded to provide this latest capability. Dependency Table:

BSS BSC DX200 Platform

BTS Ultra Site

BTS Metro Site

BTS Talk

Family

BTS Flexi EDGE

BTS Flexi Multiradio

BTS BTSplus


Release RG20 S15 - (Y) (Y) (Y) (Y) (Y) 1) (Y) - - - - - -

1) The feature is supported with RG20(BSS) on top.


30 (105)

3.6 TCSM3i Capacity Evolution Feature ID: BSS21371 Summary: The TCSM3i Transcoder was introduced with the BSS12 Release. The extremely high channel capacity of the TCSM3i is now yet further extended with a new configuration setup - supporting up to 14400 traffic channels in an ETSI environment and 11400 traffic channels in an ANSI environment for a stand-alone installation. The capacity of the combined BSC / Transcoder solution remains at the market leading 34000 channel level (introduced with the BSS13 Release), but the packing density has been further increased, so that this can now be realised with two cabinets instead of the current three. Enhancements to the BSC connectivity have also been realised, where up to 272 different BSCs can now be connected to a combined BSC / Transcoder solution and up to 30 for stand-alone configurations. A new transmission interfacing option will also be available for the A over IP function - enabled via the ETP-A interface module. Benefits for the Operator: The following benefits are realised:

CAPEX Savings, through combining the enhanced capacity of the TCSM3i with a flexible site installation

OPEX Savings, through reduced transmission, site and O&M costs In addition to the significant benefits of the TCSM3i for existing combined BSC / TCSM solutions, that is, native optical A-interfaces for fast installation and clear transmission and site cost savings, the major capacity increase enables a new flexibility in BSC / Transcoder site installations. Moreover, a greater number of BSCs can now be served by a single transcoding entity, simplifying the network design. Dependency Table:


BTS Ultra Site

BTS Metro Site

BTS Talk

Family

BTS Flexi EDGE


BTS BTSplus


Release RG20 S15 - (Y) (Y) (Y) (Y) (Y) 1) (Y) - - - - - -

1) The feature is supported with RG20(BSS) on top.


31 (105)

4 Hardware Product Solutions for RG20(BSS) on top A confirmation of the product hardware related requirements has been communicated through the BSC Hardware Technical Note - TS-BSC-HW-0183.

The BSCi / BSC2i / TCSM2 and Talk Family BTS systems are compatible (supported) by RG20(BSS) on top. Also, the new RG20(BSS) on top features are not supported by the Transcoder TCSM2 and Talk Family BTSs.

4.1 BSC Hardware Requirements Beyond the Flexi BSC and BSC3i, the BSCi and BSC2i support the RG20(BSS) on top software release. RG20(BSS) on top sets the same mandatory minimum hardware requirement as per the RG20(BSS) Release, described below:

Minimum CPU Memory Size:

Is generally as per the RG10(BSS) and RG20(BSS) Releases. However, certain software products set additional requirements for the BSC Hardware

Flexi BSC has 1 GB in all units as standard BSC3i 660: 512 MB in BCSU, 1 GB in MCMU and OMU BSC3i 1000/2000: 512 MB in BCSU (except in scenarios where the ETP

and Packet Abis is employed, where it is then 1GB), 1 GB in MCMU and OMU. In general, 1GB for all units is recommended

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

Minimum Hard Disk Size:

Is as per the BSS13, RG10(BSS) and RG20(BSS) Releases BSC3i: 9GB BSCi and BSC2i: 4GB


32 (105)

Typical Minimum O&M Link Capacity Requirement:

Is as per the BSS13, RG10(BSS) and RG20(BSS) Releases BSC3i 2000: minimum 1024 kbit/s, recommended 2048 kbit/s BSC3i 1000: minimum 512 kbit/s, recommended 1024 kbit/s BSCi, BSC2i, BSC3i 660: minimum 256 kbit/s, recommended 512 kbit/s

Please note that the figures presented above are calculated estimates that have not yet been confirmed in live usage and consequently changes may potentially arise.

Please also note that some deviation to these figures may exist arising from the number of managed objects under the BSC, the activated features, customer specific data collection settings, work processes, etc

A LAN-based O&M connection is currently recommended for all product configurations and is the most powerful link option method. Alternatively, a digital X.25 connection is still feasible when multiple 64kbit/s timeslots are employed. LAN interfaces are mandatory for data speeds higher than 1024 kbit/s. As for the earlier BSS13 software release, an analog X.25 connection with limited link capacity is no longer available with the BSC3i 1000/2000 configuration; and as for the earlier RG10(BSS) and RG20(BSS) releases, with the Flexi BSC only a LAN based connection is supported.

Please also note that in BSCi and BSC2i the O&M LAN interface requires IP cabling and CPLAN panels as well as external LAN switches and/or routers.

4.2 Transcoder Hardware Requirements Beyond the TCSM3i, the TCSM2 supports the base RG20(BSS) on top software. Note that the new transcoder related capabilities are only supported by the TCSM3i.

4.3 PCU Hardware Requirements The PCU1 is supported by RG20(BSS) on top.

4.4 BSC Hardware Requirements for new Software Features As for previous software releases, certain software products set additional requirements for the BSC hardware. For RG20(BSS) on top, there are currently no additional hardware requirements.

Hardware requirements for the software features introduced in earlier software releases should be reviewed separately.


33 (105)

4.5 Multicontroller BSC / Transcoder Feature ID: BSS21530

Summary: The Nokia Siemens Networks Multicontroller BSC / Transcoder application on top of the new scalable multipurpose Multiradio Controller Platform realises a revolutionary, highly scalable and high capacity solution. It provides a future-proof BSC / Transcoder implementation for all IP-based networks. Support for up to 4,400 TRX and up to 26,400 Erlangs is provided. The Multicontroller BSC / Transcoder application on top of the Multiradio Controller Platform extends the existing Nokia Siemens Networks Single RAN solution.

On top of the revolutionary implementation for new all IP-based BSC installations, the Multicontroller BSC can be used to introduce and extend the all IP-capacity of Flexi BSC and BSC3i 1000/2000 products in existing networks. With Multicontroller BSC extensions for Flexi BSC and BSC3i 1000/2000 products, future proof evolution towards new technologies can be gradually introduced to the existing installed base.

Benefits for the Operator: The Multicontroller BSC / Transcoder offer a wide range of benefits for the Operator, including new and unique saving opportunities.

With compact size and scalable capacity:

Installation and site space OPEX cost savings Reduced equipment needs Simpler logistics and transportation processes Fast installation and commissioning procedures Fewer spare parts and a reduced process complexity Easy capacity upgrades, through just adding modules

With a modular Multiradio Controller Platform design:

Meeting the specific GSM and WCDMA site requirements Re-use of the existing equipment investment A simple evolution path towards Multicontroller RNC configurations through

module reuse With an all IP-based solution:

Evolution capability for all IP-based networking Support for efficient and flexible IP transport design Transport efficiency through Packet Abis (over IP/Ethernet); A over IP; Gb over IP

and SIGTRAN (SS7 over IP)


34 (105)

Functional Description: The Multiradio Controller Platform is a new concept that enables operators to provide the needed capacity with an unrivalled footprint, scalability and evolution capability. The Multicontroller BSC and Multicontroller RNC applications on top of the common Multiradio Controller Platform increase the flexibility and versability for the Operator, to fully protect the original investment.

The Multiradio Controller Platform hardware is based on the latest component technology and research solutions enabling an unrivalled packing density. Furthermore, the extremely modular design and revolutionary processor architecture enables a capacity, connectivity and functionality which can be efficiently scaled to match the network needs in a fully flexible, fast and cost efficient manner.

The modular design of the Multiradio Controller Platform is extremely adaptive, supporting with the Multicontroller BSC application a flexible TRX and PS Data capacity as well as catering for a wide range of network topologies. The revolutionary concept meets network needs, from highly centralised - where a high capacity Multicontroller BSC is located at the switch site, to largely distributed - where the Multicontroller BSC is located close to remote and smaller BTS areas. Further, the combination of a highly flexible hardware design and distributed software solution ensures that capacity extensions and functionality upgrades are easy to optimise according the particular network requirements and services.

The extremely small footprint realised opens up new installation options, providing a unique opportunity in the industry for significant savings in real estate investment. In addition, OPEX cost efficiency just took a quantum leap forward in the area of spare parts management too, since both the number and types of plug-in units have been significantly reduced.

The modular design of the Multiradio Controller Platform enables an efficient and complete Multicontroller BSC - Multicontroller RNC installation, providing a re-use path between the BSC and RNC applications.

Multicontroller BSC All IP-based Multicontroller BSC configurations are realised with easily installable, standard-sized, compact Multiradio Controller modules. The modular and compact design allows flexible scalability in configuration and efficient utilisation of the available site space.

The smallest operational size of the Multicontroller BSC uses two modules, and the maximum supported configuration uses eight modules. TRX and PS Data capacity extensions are realised by simply adding additional modules, according to the particular traffic and connectivity requirements.


35 (105)

Figure: New Multicontroller BSC installation.

Additionally, the Flexi BSC, BSC3i 1000/2000 and Multicontroller BSC complement one other, offering a flexible and future-proof evolution path for Operators.

Multicontroller BSC modules may be used in a combined site installation with an

existing Flexi BSC or BSC3i 1000/2000 product, to introduce and extend the all IP-capacity, for a future-proof evolution path in existing networks.

In a combined site installation, the latest evolution options are introduced to the installed base through simply adding Multicontroller BSC modules into the existing Flexi BSC or BSC3i 1000/2000 implementation. The all IP-based interfaces supported by the Multicontroller BSC provide a smooth and future-proof evolution via Packet Abis over IP/Ethernet, AoIP and Gb/IP.

In addition to the extended all IP-based capacity provided by the Multicontroller BSC, Flexi BSC or BSC3i 1000/2000 continue to support traditional E1/STM-1 connections for the existing legacy radio network.

The combined Flexi BSC / BSC3i 1000/2000 - Multicontroller BSC installation creates a powerful combined single BSC configuration. It provides support for the existing installed legacy radio network and in addition provides the evolution path to support all IP-based networking solutions and as well looks even further into the future, with an evolution capability towards Multicontroller RNC configurations.


36 (105)

The smallest operational size of the Multicontroller BSC extension for Flexi BSC / BSC3i 1000/2000 is with two modules. The maximum supported extension configuration uses 6 modules. Within the Multicontroller BSC extension either TRX or PS Data capacity extensions are implemented by simply adding additional modules according to the particular traffic and connectivity requirements.

Figure: Combined Flexi BSC - Multicontroller BSC installation. Multicontroller Transcoder The Multicontroller BSC also includes a transcoder implementation for AoIP, Transcoder in the BSS applications as a functional part of the BSC via separate Multicontroller Transcoder modules. Transcoder resources may be physically located along with the Multicontroller BSC or in a separate site supporting several Multicontroller BSCs.

Therefore, the Multicontroller BSC may always be connected via the standardised A-Interface (3GPP Rel.8 based A over IP) to any vendors Core Network either through AoIP, Transcoder in the MGW or through AoIP, Transcoder in the BSS implementations.

The highly scaleable design is also evident with the Multicontroller Transcoder implementation - the needed transcoding capacity and Multicontroller BSC connectivity may be achieved through simply adding Multicontroller Transcoder modules starting from the minimum one module implementation. The additional modules easily enable channel capacity and Multicontroller BSC connectivity extensions according to the particular traffic and network topology needs.


37 (105)

The Multicontroller Transcoder provides:

Up to 5040 Channels within a single Multicontroller Transcoder module Connectivity for up to 30 Multicontroller BSCs per single Multicontroller

Transcoder module

A scalable solution through adding additional modules according to the traffic and Multicontroller BSC connectivity needs

Figure: AoIP, Transcoder in the BSS, using the Multicontroller Transcoder.

Operational Aspects: The Multicontroller BSC supports both the Flexi EDGE and Flexi Multiradio BTS types via a Packet Abis over IP/Ethernet connectivity. Indeed, the all IP-based Multicontroller BSC requires an IP/Ethernet implementation for all interfaces, including Packet Abis over IP/Ethernet, AoIP, SS7 over IP (SIGTRAN), Packet Ater/Ethernet, Gb/IP, O&M/IP, Lb/IP.

The software feature support for the Multicontroller BSC for new BSC installations is according to the RG20(BSS) Release feature baseline plus the RG20(BSS) on top RF Sharing GSM - LTE feature capability. The other RG20(BSS) on top software features are not supported by the Multicontroller BSC. Furthermore, all TDM transport related features and interfacing capabilities (including Packet Abis over TDM, E1/T1, SDH, PWE, Dynamic Abis, etc) are not applicable for the Multicontroller BSC.


38 (105)

Additionally, the software feature support for a combined Flexi BSC / BSC3i 1000/2000 - Multicontroller BSC installation is also according to the RG20(BSS) Release feature baseline plus the RG20(BSS) on top RF Sharing GSM - LTE feature capability. The other RG20(BSS) on top software features are not supported in a combined Flexi BSC / BSC3i 1000/2000 installation with the Multicontroller BSC.

Furthermore, all features relating to other specific products - such as other BSC products (Flexi BSC product family, BSC2i/i), TCSM2, TSCM3i, UltraSite BTSs, BTSplus, etc- are not applicable for the Multicontroller BSC in all installation scenarios. Also, features related to the Flexi BSC/BSC3i 1000/2000, legacy BTSs and transport interfaces (E1/T1, SDH, PWE, Dynamic Abis) are supported via the Flexi BSC, BSC3i 1000/2000 part in the combined installation with the Multicontroller BSC for the existing legacy radio network.

Dependency Table:

BSS BSC mcBSC Platform

BTS Ultra Site

BTS Metro Site

BTS Talk

Family

BTS Flexi EDGE


BTS BTSplus


Release RG20 on top

S15 2.x

Y 1) N N N Y 2) Y 2) N - - - - - -

1) Please refer to the Operational Aspects section for details of the supported feature scope. 2) The BSS21454, Packet Abis over IP/Ethernet software feature (and Licence Key) are required.


39 (105)

5 Software Product Solutions - Features Under Development

5.1 Radio Network Performance 5.1.1 Energy optimised TCH Allocation Feature ID: BSS21222 Summary: The RG10(BSS) Release feature set encompasses a significant capability for minimising power consumption and consequently reducing operator OPEX costs. With the RG20(BSS) Release, this new feature builds upon the RG10(BSS) capability, further reducing the BTS power consumption through adapting the voice call allocation procedure such that allocation to the BCCH TRX is also based upon the Downlink received signal level information. Benefits for the Operator: The RG10(BSS) Release provides a significant capability for minimising power consumption and consequently reducing OPEX costs for the operator. This new RG20(BSS) feature enhances this energy saving potential at the BTS, further decreasing the OPEX costs for the operator. It also acts to reduce the Downlink interference level, through the improved power level management realised. Functional Description: Currently, the allocation of radio timeslots (RTSL) in a cell is based upon the sequential availability of resources and also the value of the TRP (TRX Priority In TCH Allocation) parameter. Timeslots which are occupied by calls with a low Downlink Rx Level have a maximum radiated power at the BTS. Typically, there will be cases where calls demanding a high Downlink transmit power (where the measured Downlink Rx Level is low) are allocated to a non-BCCH TRX and calls with a low Downlink transmit power (where the measured Downlink Rx Level is high) are allocated to the BCCH TRX. Since the BCCH TRX is operating on maximum power an "excessive" transmit power is being used for calls with a high Downlink Rx Level (simply because they have been allocated to the BCCH TRX). Equally, calls with a lower Downlink Rx Level which are allocated to a non-BCCH TRX result in a higher total power consumption (if the BCCH TRX is occupied by calls with a higher Downlink Rx Level).

Figure: Current TCH Allocation Mechanism.

Distant MS allocated to the TCH TRX => due to low

received signal strength it

TCH TRX operates at full Near MS allocated to the BCCH TRX => PC not

BCCH TRX operates at full


40 (105)

Consequently, the BTS power consumption could thus be reduced if the circuit switched TCH allocation procedure to the BCCH TRX also takes the reported downlink received signal level information into account. The Energy optimised TCH Allocation feature provides a mechanism that optimises the selection of the BCCH and non-BCCH TRXs for TCH allocation within a BSC in terms of power consumption. This means that the total power consumption in the BTS can be reduced, consequently saving OPEX costs. Two new segment level parameters:

Lower DL RX lev for BCCH TRX preference (LDRB) Upper DL RX lev for BCCH TRX preference (UDRB)

Lower and Upper Downlink Rx Level thresholds, for BCCH TRX preference in TCH allocation will be introduced. With these parameters the operator is able to define a Downlink Rx Level window for BCCH TRX preference. If the measured Downlink Rx Level is within this window, the BSC will attempt to allocate the call to the BCCH TRX, otherwise it will be allocated to a non-BCCH TRX.

Figure: Energy optimised TCH Allocation Mechanism for TCH Allocation. Furthermore, this window based approach (where a Lower Rx Level threshold is used in addition to the Upper Rx Level threshold), accommodates networks which employ RF Hopping. In this case, calls with a very poor Downlink Rx Level (receive level close to the Downlink receiver sensitivity level) are allocated to a non-BCCH TRX in order to benefit from the hopping gain (the BCCH TRX is not used in hopping). This approach then maintains the existing call drop rate.


41 (105)

It is currently estimated that Energy optimised TCH Allocation will enable transmit power reductions of the order of 1.5 to 2.5dB, translating into an up to around 10% power consumption improvement over the existing mechanism. The gain is highest in lower to medium TRX loading levels (approximately up to 60% loading of TRXs). For increasing loads beyond this level the influence of the feature reduces and consequently the gains also reduce. Furthermore, the higher the number of non-BCCH TRXs in a cell, the greater is the saving in power consumption. Of course, the gain also depends upon the particular parameter settings. Operational Aspects: The Downlink Rx Level based TRX prioritisation is applied only during call setup and for intra-BSC handovers. For external handovers the Downlink Rx Level is not known by the target BSC and consequently the TRX selection is performed according to the existing TRP parameter setting. Furthermore, the feature is only applied to CS Calls. Should the feature BSS08037, Enhanced Coverage by Frequency Hopping, be in use in the network, it is recommended not to simultaneously employ both features within a cell. Dependency Table:


BTS Ultra Site

BTS Metro Site

BTS Talk

Family

BTS Flexi EDGE


BTS BTSplus


Release RG20 S15 - Y Y N Y Y 1) Y - - - - - Licence Key

Control

1) The feature is supported with RG20(BSS) on top. 5.1.2 OSC Half Rate with SAIC MS Feature ID: BSS21309 Summary: Orthogonal Sub Channel (OSC) introduces a doubling of the voice channel capacity, such that with the new RG20(BSS) feature, OSC Half Rate with SAIC MS, four users can now share the same radio Timeslot. Only SAIC and AMR support are required from the Handset. The increase in voice channel capacity is realised through the adoption of a quaternary modulation scheme in the Downlink and utilising spatially orthogonal sub-channels in the Uplink. These two solutions, combined with AMR, enable the possibility to serve two Handsets which support single antenna interference cancellation (SAIC), simultaneously in a single radio traffic channel. OSC not only introduces a step change in network capacity, it is achieved in a very energy efficient manner, reducing the total energy requirement at the BTS, saving further OPEX costs for the operator.


42 (105)

Benefits for the Operator: Normally, when an operator needs to increase capacity this is achieved through extending the BTS configuration (via increasing the TRX and combiner port count), increasing the combining loss and potentially impacting coverage. OSC can provide for this increased capacity without requiring new TRXs (or related hardware) and avoiding the network impact. Consequently, for the operator an increased capacity can be provided more easily and CAPEX/OPEX effectively. Through the capacity improvements realised by OSC, a reduced number of TRX is necessary in order to realise a specific capacity or spectral efficiency. Consequently, the energy consumption required per Erlang may be reduced by as much as 50% with OSC. Furthermore, OSC Half Rate with SAIC MS provides a profitable network growth path for operators, with minimised CAPEX and OPEX costs. The coverage area can be maintained in capacity extensions and the need to add new sites is avoided, thus, lowering or delaying considerably the operators expenditure. For new network deployments, the increased capacity per TRX achievable through OSC can be used to effectively reduce the required site density (and consequently CAPEX/OPEX costs) through the reduced combining losses now possible. Alternatively, since OSC Half Rate with SAIC MS increases the voice capacity potential, the feature can also be employed to release capacity for additional data traffic. Most importantly, contra to the 3GPP Rel.9 VAMOS (Voice services over Adaptive Multi-user Orthogonal Sub channels) capability, which of course requires the availability and sufficient penetration of Rel.9 Handsets, with the Nokia Siemens Networks OSC solution, the existing Handsets supporting AMR and SAIC are sufficient. This is available today and thus operators can derive the full gains from OSC immediately. Functional Description: Orthogonal Sub Channel (OSC) introduces a doubling of the voice channel capacity, such that with the new RG20(BSS) feature, OSC Half Rate with SAIC MS, four users can now share the same radio Timeslot. Only SAIC (the Handset must indicate its support for SAIC to the network) and AMR support are required from the Handset. The two OSC Sub-channels are identified as OSC-0 and OSC-1, in a TCH/H. The OSC Sub-channels are independent of one other, that is, they have an independent Radio Resource layer signalling. Separation between the simultaneous connections in a TCH is realised through the use of individual training sequences. Individual Training Sequences The separation of the two simultaneous users in Downlink and Uplink is enabled through employing different training sequences, whilst the other channel parameters can be the same as that for a normal GMSK modulated channel. This enables the use of normal SAIC handsets for OSC. The Sub-channel specific Training Sequence Codes (TSC) are organised as TSC pairs, which provide the lowest cross-correlation. Multiplexing in the Downlink In the Downlink, the BTS uses Quaternary Phase Shift Keying (QPSK) modulation which is composed from two orthogonal sub channels. These are received by the legacy SAIC Handsets as normal GMSK. Separate reception of one of the Sub-channels is achieved


43 (105)

as they are orthogonal and through the different training sequences employed for the Sub-channels. The figure below shows the mapping of Users A and B in the QPSK modulation constellation, where User A is mapped to the first bit and User B to the second bit:

Figure: Multiplexing in the Downlink. Multiplexing in the Uplink In the Uplink, Handsets employ standard GMSK transmission and simultaneous Sub-channels are differentiated via the training sequences and propagation path. Antenna Diversity (two antennas) is required for the BTS, in order to facilitate reception of the two simultaneous users - This is inherent, resulting from the degree of freedom rule, applied for MU-MIMO (Multi User - Multiple Input, Multiple Output) systems in general, which states that the number of simultaneous users can be the same as the number of receiving antennas. Please refer to the figure below. The radio propagation paths in the Uplink are generally uncorrelated due to the separate locations of the users.

User-A

User-B

Deciphering Decoding


V-MIMOReceiver Abis

V-MIMO

TRXUser-A

User-B



V-MIMOReceiver Abis

V-MIMO

TRX

Figure: Multiplexing in the Uplink. Channel Rate Adaptation OSC in the Downlink direction has an approximate 3 dB reduction in performance (in comparison with AMR HR), thus it may not be applicable for the most demanding radio conditions. Through employing AMR Full Rate and AMR Half Rate together with the new OSC Half Rate capability, the network capacity can be increased without compromising the voice quality (arising from the 3dB reduction). Typically, OSC Half Rate may be used in over 50% of connections. The allocation of different channel rates in relation to the carrier to interference (C/I) ratio is depicted in the figure below:

(0,0)

(0,1) (1,1)

(1,0)I

Q (User-A, User-B)

(0,0)

(0,1) (1,1)

(1,0)I

Q (User-A, User-B)


44 (105)

HRFR DHRHR DHR

DHRDHR

C/Ic.d.f.

~8 dB~10%

~12 dB~50%

HRFR DHRHR DHR

DHRDHR

HRFR DHRHR DHR

DHRDHR

C/Ic.d.f.

~8 dB~10%

~12 dB~50%

Figure: Channel Rate Adaption for AMR Full Rate, Half Rate and OSC Half Rate. The existing AMR channel rate adaptation solution, that is, packing / upacking is extended for OSC Half Rate by introducing new quality and Rx level thresholds. With OSC Half Rate with SAIC MS, the target channel for OSC packing is always a TCH/H where an AMR call is currently ongoing and which offers a sufficient signal level and quality. For an ongoing AMR HR connection, another appropriate AMR call (where the Uplink Rx levels of the connections may be adjusted sufficiently closely) is searched for. With the OSC multiplexing procedure, an AMR call is handed over to the target TCH. The original channel rate of the AMR connection to be handed over may be either Half Rate or Full Rate. Consequently, a direct multiplexing from AMR FR to OSC HR is possible. The target for the multiplexing handover is however a TCH/H. Unpacking (de-multiplexing) of an OSC HR channel, may either result from a deteriorating quality of an OSC HR connection or by the weakening of the Uplink Rx level balance between the OSC Sub-channels. In the former case, de-multiplexing is performed (by default) to a Full Rate TCH. However, with BSS21120, AMR Unpacking Optimisation, the de-multiplexing Handover may be to either a Half Rate TCH or a Full Rate TCH, depending upon the radio conditions. If the reason for de-multiplexing is the excessive Uplink Rx level difference between the multiplexed calls, the handover is primarily made to a Half Rate TCH. With BSS21483, Improved AMR Packing and Unpacking, the de-multiplexing Handover may also be triggered based upon the connection specific Rx level criteria introduced by the feature. Power Control with OSC In the Downlink, power control is naturally common for both Orthogonal Sub-channels, consequently, the highest Tx power required is that which is employed. In the Uplink, the received power at BTS is aligned by means of power control and an appropriate user pairing.


45 (105)

Double Stealing for FACCH The BTS steals voice blocks from both the OSC Sub-channels and sends GMSK instead of QPSK for FACCH signalling in order to boost the FACCH performance. If the FACCH occurs simultaneously in both OSC Sub-channels or a SID frame is sent in another then QPSK is employed. The feature, BSS20916, AMR HO Signalling Optimisation may be employed to enhance performance in terms of Call Drop Rate and MOS Statistics (since fewer FACCH blocks are then needed during a Handover procedure). Dynamic Allocation of Abis Resources from a Shared Pool It is important to consider, that employing OSC Half Rate will always require additional transport capacity, since two 8kbit/s Abis Timeslots are required to support the paired OSC Half Rate Calls (OSC-0 and OSC-1). That is, a maximum of four 8kbit/s Abis Timeslots are now required for a single Radio Timeslot. There are two practical solutions for this, to either employ:

1. A Packet Abis solution (BSS21454, Packet Abis over IP/Ethernet or BSS21440, Packet Abis over TDM)

2. BSS30385, Circuit Switched Dynamic Abis Pool (CSDAP)

Please refer to the appropriate sections of this document for further details. The Sub-channel OSC-0 uses the existing Abis transport resources and the legacy TSC of the TRX. BSC Capacity Aspects The voice channel handling capacity of the BSC remains unchanged with the introduction of the OSC Half Rate with SAIC MS feature. With Half Rate, when defining the maximum allowed channel configuration for a BSC (or rather, BCSU), the BSC calculates all HR capable Radio TSLs as two channels. With OSC Half Rate, when defining the maximum possible configuration for a BCSU, the BSC calculates an AMR HR capable Radio TSL where OSC Half Rate is enabled as three channels. This must be accounted for during the planning for deployment of OSC. Operational Aspects: A sufficient LAPD signalling link capacity is required in order to manage the increased radio measurements and signalling resulting from the increased number of calls per TRX with OSC. A minimum 32kbit/s LAPD signalling link is required when OSC is enabled in a TRX. The triggering of OSC Half Rate multiplexing is based upon the traffic loading in a BTS. The triggering load limit - Limit for Triggering OSC DHR Multiplexing - is a new parameter, based upon a similar definition for load as that for the traditional parameters with AMR Half Rate Packing. The load limit parameter also serves as a BTS specific control function for the feature, with which it is possible to turn the feature ON and OFF in a particular BTS. OSC Half Rate is not applied to Emergency Calls.


46 (105)

Important Logistics Note: This feature item (BSS21309) is valid for up to 100 simultaneous OSC HR Call Pairs in total for one BSC. The additional item BSS101419 OSC HR Capacity Licence is required for additional OSC capacity beyond this initial allocation and is required for each step of 100 simultaneous OSC HR Call Pairs per BSC. Dependency Table:


BTS Ultra Site

BTS Metro Site

BTS Talk

Family

BTS Flexi EDGE


BTS BTSplus


Release RG20 S15 1)

- Y 2) N N Y 3) Y 4) N 5) - - - - Y 6)

Licence Key

Control

1) The features (and licence keys for) BSS30060, AMR Capacity (HR); BSS01073, Rx Diversity and BSS11610, Discontinuous Transmission DL and UL (DTX) are required. The feature BSS20082, Support for Single Antenna Interference Cancellation is optional.

2) The feature is supported with RG20(BSS) on top. Also: I. Either EDGE or OSC is supported within one TRX Module - both cannot be supported within the

one Module.

II. If Baseband or Antenna Hopping is used, then all of the carriers within a BTS Object must be of type OSC or EDGE.

3) This feature is also supported by the EXxA Flexi EDGE BTS Dual TRX Module, but not with the full feature capability:

I. Either EDGE or OSC is supported within one Dual TRX Module - both cannot be supported within the one Dual TRX Module.

II. If Baseband or Antenna Hopping is used, then all of the carriers within a BTS Object must be of type OSC or EDGE.

The EXxB version of the Flexi EDGE BTS Dual TRX is required for full compatibility. 4) The feature is supported with RG20(BSS) on top. 5) Supported via RG301397, Cositing with BS2xx. 6) A 3GPP Rel.6 capable Handset is required - Handset must indicate its support for SAIC to the network.

5.1.3 Circuit Switched Dynamic Abis Pool Feature ID: BSS30385 Summary: Since two 8kbit/s Abis Timeslots are required to support the paired OSC Half Rate Calls (OSC-0 and OSC-1) with BSS21309, then practically either a Packet Abis solution or the Circuit Switched Dynamic Abis Pool (CSDAP) feature is required in order to support the additional Abis capacity that must be managed when employing OSC. Functional Description: For the standard Abis interface, a fixed 16kbit/s transmission capacity is allocated for each Radio Timeslot (TSL) from the available Abis ETPCM. When BSS21309, OSC Half Rate with SAIC MS is deployed, then additional Abis transmission capacity is necessary for each Radio TSL, since two (OSC) Half Rate Calls are now multiplexed on to one single Half Rate TCH. Although possible, it is generally not efficient to allocate double the fixed transmission capacity for each Radio TSL, since the extra transmission capacity is only necessary during higher load scenarios, when OSC Calls are activated within the cell. Alternatively, the new Circuit Switched Dynamic Abis Pool feature offers the possibility to create and manage common transmission pool(s) - shared capacity - for OSC Half Rate Calls within the BCF.


47 (105)

Figure: CSDAP Timeslot Allocation within the Abis. Circuit Switched Dynamic Abis Pool(s) (CSDAPs) are created per BCF (BTS Site) and shared by all TRXs within the BCF. Up to four CSDAPs are possible per BCF, with up to a maximum of 1000 CSDAPs supported per BSC. A CSDAP may be allocated to the same or indeed a different Abis ETPCM than that which is being used by the TRX, but it must be created using consecutive PCM Timeslots (as illustrated in the figure above). Thus, the size of a CSDAP ranges from 131 TSL for an E1 (respectively 124 for a T1), with a granularity of 1 PCM Timeslot. If required, the transmission resources for all TRXs of a BCF cabinet may be allocated to one single CSDAP. Note that since the OSC Half Rate CS Calls are independent, then no synchronisation is necessary between the TRAU Frames associated with the paired OSC-0 / OSC-1 Calls. Benefits for the Operator: The Operator avoids the need to configure additional fixed Abis transmission capacity when taking OSC Half Rate into use through the CSDAP feature, which then provides a CAPEX/OPEX efficient solution.


48 (105)

Dependency Table:


BTS Ultra Site

BTS Metro Site

BTS Talk

Family

BTS Flexi EDGE


BTS BTSplus


Release RG20 S15 - Y 1) N N Y Y 1) N 2) - - - - - Licence Key

Control

1) The feature is supported with RG20(BSS) on top. 2) Supported via RG301397, Cositing with BS2xx.

5.1.4 Merged P- & E-GSM900 Feature ID: BSS21238 Summary: A number of P-GSM / E-GSM feature enhancements have already been provided in earlier software releases. This feature complements these through combining the P-GSM and E-GSM frequency bands into one and removing the specific handling previously required for P-GSM only handsets. Benefits for the Operator: This new feature introduces an improved spectral efficiency through the merging of the P-GSM and E-GSM Bands. Furthermore, the general operability of the network is improved and simplified. Functional Description: Originally, PGSM900 and EGSM900 resources were managed separately and configured as separate cells within the BSC, with handover support between them. Over later software releases (BSS11.5, BSS12 and BSS13) a number of enhancements were realised in order to increase the integration of the two frequency bands. Up to the RG20(BSS) Release, PGSM900 and EGSM900 frequencies can be used within a single BTS object and support for PGSM-only handsets has been maintained. However, in cases where the BCCH carrier of a PGSM900-EGSM900 BTS is on the PGSM900 frequency band there are currently operational aspects that must be considered, which would be unnecessary if all GSM900 handsets in the network also supported the EGSM900 band.


49 (105)

These operational aspects are:

It is possible to combine PGSM900 and EGSM900 frequencies only in the BCCH BTS and with such a BCCH BTS it is not possible to employ GSM900 frequencies in any other BTS object of the segment

It is not possible to use RF Hopping and (E)GPRS on the same TRX Baseband Hopping cannot be employed It is not possible to use super reuse TRXs DFCA Hopping cannot be employed Static SDCCH resources must be configured for the PGSM900 TRXs The BSC limits the dynamic reconfiguration of SDCCHs to be within the

PGSM900 TRXs

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

The feature High Speed Circuit Switched Data is not supported It would no longer be necessary to consider these if it can be assumed that all GSM900 handsets in the network support EGSM900. This is the basis for this RG20(BSS) feature, Merged PGSM900 and EGSM900, which complements the existing PGSM900-EGSM900 feature enhancements, combining the two frequency bands into one and removing the specific handling previously required for PGSM-only handsets. The feature then eliminates the above operational aspects. Note that generically for GSM systems, the maximum number of available GSM900 frequencies in a PGSM900-EGSM900 segment is 16 (17 if ARFCN 0 is included). This RG20(BSS) feature represents the final

09_rg20 (bss) rg20 (bss) on top features under development

Documents