BSS_14_Feature_Candidates_(FCD)_Ver_1.5.0.pdf

8/14/2019 BSS_14_Feature_Candidates_(FCD)_Ver_1.5.0.pdf

http://slidepdf.com/reader/full/bss14featurecandidatesfcdver150pdf 1/34

BSS14 FCD

Feature Candidates

Ver 1.5.1

Confidential

Confidential © Nokia Siemens Networks 1 (34)




The information in this document is subject to change without notice and describes only the product defined inthe introduction of this documentation. This document is not an official customer document and Nokia SiemensNetworks does not take responsibility for any errors or omissions in this document. This document is intendedfor 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 anyform or means without the prior written permission of Nokia Siemens Networks. The documentation has beenprepared to be used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity or performance ofthe mentioned hardware or software products are given “as is” and all liability arising in connection with suchhardware or software products shall be defined conclusively and finally in a separate agreement between NokiaSiemens 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 ORCONSEQUENTIAL 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 thisdocument or the information in it.

THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY APPLICABLEMANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE AND NON-INFRINGEMENT, ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY ORCONTENTS OF THIS DOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT TO REVISETHIS DOCUMENT OR WITHDRAW IT AT ANY TIME 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, and they arementioned for identification purposes only.

Copyright © Nokia Siemens Networks 2007. All rights reserved.




1 Summary of changes................................................................................................. 4 2 Introduction ................................................................................................................ 6

3 BSC & TCSM Products .............................................................................................. 8

3.1 BSC hardware requirements ................................................................................ 8

3.2 TCSM hardware requirements ............................................................................. 8

3.3 PCU hardware requirements ................................................................................ 8

3.4 BSC HW requirements for new Application Software products .................. 8

3.5 Integrated IP card for BSC3i and TCSM3i ......................................................... 9

3.6 Asymmetrical PCU HW Configuration ............................................................. 10

4 Radio Network Performance................................................................................... 12

4.1 WB-AMR .................................................................................................................. 12

4.2 WB-AMR support by TCSM3i ............................................................................. 14

4.3 AMR HO Signaling Optimisations ..................................................................... 15

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

4.5 A5/3 ciphering ........................................................................................................ 18

4.6 SDCCH and PS Data on DFCA TRX .................................................................. 19

4.7 AMR Unpacking Optimisation............................................................................ 20

5 Packet Switched Data .............................................................................................. 22

5.1 Improved Extended UL TBF................................................................................ 22

5.2 Robust EDGE Retransmission........................................................................... 23

5.3 Downlink Dual Carrier .......................................................................................... 24

6 Operability ................................................................................................................ 26

6.1 Energy saving mode for BCCH TRXS .............................................................. 26

6.2 Flexi EDGE DTRX Automatic Power Down ..................................................... 27

6.3 Secure remote MMI ............................................................................................... 28

6.4 PCU Restart Handling .......................................................................................... 29

6.5 OSI over TCP/IP ..................................................................................................... 30

6.6 Automated RNW O&M log collection ............................................................... 32

7 Multiradio Interworking ........................................................................................... 33

7.1 Load Aware ISHO Admission ............................................................................. 33




1 Summary of changes

DATE ISSUE EDITED SUMMARY OF MAIN CHANGES

18.05.2007 1.0.0 ReijoLyytinen

BSS14 Program internal version


Approved version


The following features removed- BSS21184, 8k Abis for AMR/FR- BSS21109, Early UL TBF establishment- BSS20519, Proactive extended UL TBF

polling- Separate RLT for AMR DL and UL in

Optimisations

10.12.2007 1.3.0 FrodePaulsen

The following features removed- Fast Ack/Nack Reporting

- Packet Switched Handover (PSHO) - Support for MS Receiver Diversity


The following features added

- AMR unpacking optimization- Automated RNW O&M log Collection - Asymmetrical PCU HW Configuration


The name of BSS20984 has been changed to- Flexi EDGE DTRX Automatic Power Down


The following features removed

- Proactive DL TBF Establishment


The umbrella name/feature “TBF Accelerations” hasbeen removed, since “Improved delayed UL TBFrelease” is the only remaining part (ref cell above).


The umbrella name/feature “TBF Accelerations” hasbeen removed, since “Improved delayed UL TBFrelease” is the only remaining part (ref cell above).

02.01.2008 1.5.0 Frode

Paulsen

For “Asymmetrical PCU HW Configuration”:

“Functional Description”-Text improved.02.01.2008 1.5.0 Frode

PaulsenFor “WB-AMR”:“Functional Description”-Text improved.


For “WB-AMR support by TCSM3i”:“Functional Description”-Text improved.


For “AMR TFO”:“Functional Description”-Text improved.





Dependency Tables have been updated for thefollowing features:

• AMR HO Signaling Optimisations

• Robust EDGE Retransmission• Downlink Dual Carrier

• Secure Remote MMI

• PCU Restart Handling

• OSU over TCP/IP


“PCU restart handling” support has been extendedfrom PCU2 only to also include PCU1.



2 Introduction

This document describes the feature candidates for the Base Station Subsystem (BSS)system release BSS14.

Nokia BSS14 brings advantages for all operators by enabling

• Strong subsciber and voice traffic growth

• Data traffic growth

• OPEX savings with low cost transport and BTS energy saving solutions

• Optimised service quality with GSM/EDGE interworking solutions

• OPEX savings with optimised BSC HW solutions

Nokia BSS14 Software consists of Operating Software (OSW) and Application Software(ASW). Operating Software means software that includes the basic functionalities andenhancements. Application Software means software that consists of value-addingfunctionalities.

The compatibilities for individual NE releases are as follows:

BSS14 consists of the releases: BSC S14, MetroSite CXM7, UltraSite CX7, andFlexiEDGE EP3

BSS14 is supported by the following NE releases: NetAct OSS5.2, MSC M15, and SGSNSG8

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

BSC SW release S13 will tentatively be the last compatible software level for Nokia InSiteBTS SW. More details will be available in BSS14 E1 (P3) phase in BSS14 FUD and BSCTechnical Note.

Preliminary BSS14 Compatibility Matrix will be available in BSS14 E1 (P3) milestone.BSS14 Compatibility Matrix will be confirmed in BSS14 E2 (P5) milestone

The standardisation baseline of BSS14 release is 3GPP Release 7




Notations used in dependency tables

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

BSS BSC DX200Platform

BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE

NetAct SGSN MSC RAN MS

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

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

MSC This feature is supported in the Nokia MSC (xxx =Nokia MSC release/feature no) N = No, - = no

dependency, X = support required but release notdefined.

Nokia

MetroSite

This feature is supported by Nokia MetroSiteBTS (xxx = Nokia release/feature no) N = No, - =

no dependency, X = support required butrelease not defined.

NokiaNetAct

This feature is supported in the Nokia NetAct (xxx= Nokia release/feature no) N = No, - = nodependency, X = support required but release notdefined.

NokiaInSite

This feature is supported by Nokia InSite BTS(xxx = Nokia release/feature no) N = No, - = nodependency, X = support required but releasenot defined

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

NokiaUltraSite

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

SGSN This feature is supported by the SGSN (xxx =Nokia release/feature no) N = No, - = nodependency, X = support required but release notdefined.

NokiaFlexiEDGE

This feature is supported by Nokia FlexiEDGEBTS (xxx = Nokia release/feature no) N = No, - =no dependency, X = support required butrelease not defined

Nokia 2

nd

Gen.

This feature is supported by the 2nd gen BTS.(xxx = Nokia release/feature no) N = No, - = nodependency, X = support required but release notdefined.

MSThe feature sets special requirements to mobilestations (xxx = 3GPP release), - = nodependency, X = support required but releasenot defined.

NokiaTalk-family

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

HW/FW DEPENDENCY:

NokiaPrimeSite

This feature is supported by Nokia PrimeSite BTS(xxx = Nokia release/feature no) N = No, - = nodependency, X = support required but release notdefined.

BSCHW/FW

This feature requires additional or alternativeBSC hardware or firmware

DX200Platform

This feature is supported by DX200 Platform (xxx= Nokia release/feature no) N = No, - = nodependency, X = support required but release notdefined.

BTSHW/FW

This feature requires additional or alternativeBTS hardware or firmware

TC HW/FW This feature requires additional or alternativeTranscoder hardware or firmware

SGSNHW/FW

This feature requires additional or alternativeSGSN hardware or firmware

Operating/ Application

BSS SOFTWARE: Indicates whether this feature is an Operating or

Application SW feature




3 BSC & TCSM Products

At this phase of BSS14 project only a general tentative overview of product HWrelated requirements can be provided. More detailed tentative HW requirements willbe added to a new version of this document after the E1 (P3) milestone. The S14level HW requirements will be confirmed after E2 (P5) milestone and will becommunicated with BSS 14 FUD document and BSC HW Technical Note will also beissued.

3.1 BSC hardware requirements

On top of BSC3i also BSCi and BSC2i will, according to current estimates, supportthe S14 SW release. Some functionality – like Integrated IP card – will tentatively beavailable only for BSC3i 1000/2000.

3.2 TCSM hardware requirements

On top of TCSM3i also TCSM2 will, according to current estimates, support the S14SW release. New transcoding related Application SW will tentatively be supportedonly by TCSM3i.

3.3 PCU hardware requirements

All existing PCU units (PCU1, PCU2) could, according to current estimates, still beused with the basic S14 SW release. Please note, that all new packet data relatedapplication SW (listed below) will tentatively require PCU2.

3.4 BSC HW requirements for new Application Software products

As with previous SW releases certain application software products set additionalrequirements for BSC hardware. Tentative HW requirements for new S14 ApplicationSW (ASW) Products are listed in the following table:

PCU2 plug-in unit is tentativelymandatory HW requirement for:

• Improved delayed UL TBF release

• Robust EDGE Retransmission

• Downlink Dual Carrier

• PCU Restart handling

Table 1 Tentative BSC HW requirements for S14 Application SW products

The list above describes only specific tentative HW requirements of new ApplicationSW in S14. HW requirements for Application SW introduced in earlier SW releasesshould be reviewed separately.




3.5 Integrated IP card for BSC3i and TCSM3i

Feature ID: BSS21157

Summary: This feature integrates the IP/Ethernet interfaces into BSC3i 1000/2000 Abisand Ater- and TCSM3i A- and Ater-interfaces. An ETIP1 plug-in unit, based on CircuitEmulation Service over Packet-Switched Networks (CESoPSN) technology, is equippedin place of an E1/T1 or STM-1/OC-3 unit to provide the IP connectivity. This solutionenables flexible integrated product configuration options between these transmissiontechnologies.

Benefits for the Operator : Transport in GERAN networks is today based mainly onE1/T1 PCM lines. Several backhaul transport technologies are in use besides the nativeE1/T1, like microwave radios, SDH rings/point-to-point connections, ATM etc.

IP based transmission is widely seen as a cost efficient alternative to reduce operabilitycosts, allows easy expansions and is predicted to be even more efficient in future. IPnetworks are or will be readily available in many markets.

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

Lower OPEX and IMPEX can be achieved because there is no need for externaltransmission units and no need to use BSC’s interfaces to connect to this equipment.Fast implementation is assured as cabling, power supply etc. issues can be discarded.Integrated solution offers additionally higher reliability, lower power consumption andintegrated O&M via NetAct.

BSS SW: Application SW

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

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 B13 - - - - - - - - - - - -




3.6 Asymmetrical PCU HW Configuration


Summary: Asymmetrical PCU HW configuration allows operator to add and activatePCU HW in granularity of one and according to traffic needs.

Benefits for the Operator :Optimized and more space and cost efficient PCU HW configuration

Functional Description: Asymmetrical PCU HW configuration allows the operator to add and activate PCU HW ingranularity of one and according traffic needs.

PCU HW is installed into the BSC in granularity of one (+ required amount of PCU HWinto the spare BCSU). BCSUs are equipped with PCU HW units according to trafficneeds, i.e. PCU HW units are added to BCSUs one by one until the full PCU HW unitamount is reached in the BSC.

Asymmetrical PCU HW configuration introduces a definition of the primary spare BCSU.With Asymmetrical PCU HW configuration the primary spare BCSU is configured to haveenough PCU HW units to take over any of the active BCSUs. The system will keep theprimary spare BCSU as the spare BCSU by performing related BCSU switchovers assoon as the BCSU statuses allow this. A related alarm is raised if the primary spareBCSU unit is not in SP-EX state.




Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - - - - - - - - - - - - -




4 Radio Network Performance

4.1 WB-AMR


Summary: Wide Band Adaptive Multi-Rate (WB-AMR) uses a twice as high samplingrate compared to current voice services in mobile and fixed line telephony. Together withhigher sampling frequency the transcoding algorithms are improved as well in WB-AMR.Furthermore audio capabilities of handsets e.g. with integrated MP3 players are wellahead of AMR quality, thus motivating to improve voice transfer capabilities as well.WB-AMR enhances both low and high end of audio frequency band providing a clearlywarmer and more intimate sound.

WB-AMR codec set supported by BSS consists of 12.65, 8.85 and 6.60 kbps codecrates, which are currently the same as in WCDMA RAN.

Benefits for the Operator : Improved end user experience: WB-AMR providessignificant speech quality enhancements compared to AMR, fixed line telephony or xDSLVoIP. Even music applications are possible through enhanced audio bandwidth. Withclear audible enhancements, MS to MS conversations will become more transparent andcallers will feel like being closer to each other. Furthermore the transmission of the finernuances of the human voice will make communicating more complete.

As soon as the end-user has once experienced this quality, he will most likely not bewilling to change back to non-WB-AMR anymore if a choice is being offered. With WB-

AMR mobile voice calls will be used more frequently and continue longer. WB-AMR willboost wire-line to mobile substitution and provide advantages towards the competitionfrom emerging voice technologies e.g. VoIP over xDSL.

For dual mode operators WB-AMR provides also service continuity between WCDMAand GSM and enhances the probability to establish a WB-AMR call. Thus WB-AMR willsupport the "2G network to complement 3G" strategy of the operator.

Functional Description:

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

including 5 codec rates ranging from 6.6 to 23.85 kbps and including rate adaptationmechanisms as in AMR.

Audio sampling rate of 16000 samples per second, linked with WB specific algorithmsenhances audio frequency band to 50 Hz - 7000Hz for WB-AMR, which is significantincrease compared to 300 Hz - 3400Hz frequency band for existing voice services e.g. inG.711 or AMR. This new sampling rate restricts the use of WB codec to MS to MS calls.

According to listening tests further quality gains from higher WB codec modes than 12.65are seen small, thus set of three codecs i.e. 6.6, 8.85 and 12.65 carried with GSMmodulated channel are to be supported by BSS14.

Like in AMR, the codec mode can be chosen based on the radio conditions, yielding tooptimal audio performance through rate adaptation. The codec mode can be changed




every 40 ms in GSM. The codec also includes a source controlled rate adaptationmechanism, which allows it to encode speech at a lower average rate by taking speechinactivity into account.

WB-AMR requires end to end TFO (Tandem Free Operation) support, because downsampling in transcoding would invalidate WB properties of sound. If TFO is not possibletranscoding to G.711 is used, and the G.711 restricts the audio frequency range to 300 -3400 Hz. Indeed e.g. in inter PLMN WB-AMR calls it needs to be ensured that thetransport chain is transparent to carry TFO.

WB-AMR transcoding functions will be available in the NSN Media Gateway (MGW) with Ater-support.. Alternatively feature BSS21218 offers WB-AMR support for TCSM3i.

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

G.711

300-

3400

WB

AMR

50-

7000

Hz

Nuances

Presence

Warmth

BTS HW: Edge MetroSite TRX is needed for this feature. UltraSite Edge Baseband unit(BB2E or BB2F) is needed for this feature


MSS: NSN Rel-4 Core NW is needed i.e. MSC Server with MGW.

MS: WB-AMR capable MS required

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - CX7.0 CXM7.0 N N N N EP3.0 OSS5.2 - MSSSR3.1M14.1

- Rel5




4.2 WB-AMR support by TCSM3i

Feature ID: BSS21218Summary: This feature adds Wide Band Adaptive Multi-Rate (WB-AMR) support forTCSM3i.

Benefits for the Operator : This feature provides the same general benefits as theBSS20960 WB-AMR feature with the NSN MGW, and may additionally be used togetherwith other vendor’s standard compliant core networks with either Rel99 (e.g. NSNCS5.0) or Rel4 architectures, as long as they support WB-AMR.

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

Functional Description: This feature provides WB-AMR by transcoder TCSMS3iconnected to the GSM/EDGE core network via the standardized A-interface.

Figure:

BSC & TCSM HW: TCSM3i

BTS HW: Edge MetroSite TRX is needed for this feature. UltraSite Edge Baseband unit(BB2E or BB2F) is needed for this feature

BSS SW: Application SW. Prerequisite: BSS20960 WB-AMR.

MS: WB-AMR capable MS required




Dependency Table:


BTSUltra

Site

BTSMetro

Site

BTSTalk

Family

BTSPrime

Site

BTSInSite

2ndGen

BTS

BTSFlexi

EDGE


Release BSS14 S14 - CX7.0 CXM7.0 N N N N EP3.0 OSS5.2 - M14.1Or

CS5.0

- X

4.3 AMR HO Signaling Optimisations

Feature ID: BSS21219BSS21216

Summary: This feature optimizes HO signalling for AMR in order to reduce the call droprate for intracell handovers. The number of intracell handovers may increase with theutilisation of HR.

Benefits for the Operator : This feature provides lower call drop rate for intracellhandovers.

Functional Description: FACCH channel used for signaling is less robust for poor radioconditions than the most robust AMR codecs (i.e. AFS4.75) thereby limiting the coverageand capacity gains that can be achieved with AMR. One way of increasing signalingperformance is to reduce the size of signaling messages in such a way that one L3message fits e.g. into one L2 frame.

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

removed in intra-cell handovers. The speed to perform intra cell handovers or AMRpacking/unpacking is improved.


MS: AMR capable MS required

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - - - - - - - - - - - - -




4.4 Tandem Free Operation (TFO) for AMR


Summary: This feature enhances the BSS support of TFO to also include AMR inaddition to the existing FR and EFR support. It applies to both the TCSM3i and the NSN(ex-Nokia) Ater-in-MGW solution. Tandem Free Operation (TFO) is intended to avoid thetraditional double speech encoding/decoding (G.711 <->AMR) in MS to MS (2G) or MSto UE (2G/3G), and thereby improving the voice quality and potentially reducing thetransport capacity need inside the core network.

Benefits for the Operator : Capex savings by increasing usability of the existing corenetwork capacity: Operator can protect core network investments through common(Rel4) core network for WCDMA and BSS. Operators can obtain substantial savings inRel4 core network transmission capacity e.g. 4 times more voice calls can be provided, ifTrFO/TFO Interworking is used between the core nodes.

Functional Description: TFO for AMR-FR and AMR-HR will be supported for calls thatare within the same network or to another GSM / UMTS network that supports TFOversion 6.3. With either AMR-FR or AMR-HR at the local end the TFO can be used witha GSM AMR-FR, GSM AMR-HR or UMTS-AMR2 (narrowband AMR) call at the remoteend.

To ensure TFO compatible operation with best voice quality in all these cases the 3GPPrecommended AMR narrow band configuration is used, with fixed modes of 12.2, 7.4,5.9, 4.75 kbit/s for AMR-FR and fixed modes of 7.4, 5.9, 4.75 kbit/s for AMR-HR.Note: AMR-FR <-> AMR-HR call in TFO keeps the AMR-FR radio channel, so that theTFO is available while keeping the optimum radio channel setup at both ends of the call.In this case the AMR-FR side is constrained to only use the 3 lower codec rates, which




matches the AMR-HR codec set.

If WB-AMR is also used in the network then the Immediate Codec Type optimisation willensure that AMR-WB call with TFO is used if both ends of the call support the AMR-WBoperation.

The existing TFO for the GSM FR, EFR and HR codecs is still supported, as TFOversion 0.0 operation, so that if both ends of the call use the same (FR, EFR or HR)codec then TFO is used. This TFO operation is a separate feature from the AMR TFOoperation and can be active in a network at the same time as AMR TFO operation, butthere is no TFO operation if one end (local or remote) of a call is using AMR and theother end (remote or local) is using FR, EFR or HR codec.

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

present in the signal path, but the transcoding functions are bypassed. TFO uses in bandsignaling for control. In-band TFO provides no direct saving of transmission costs, bute.g. proprietary G.711 removal schemes may be used.

Transcoder Free Operation (TrFO): call configuration where no transcoder device isphysically present and hence no control or conversion or other functions associated withit are activated. TrFO is specified only for WCDMA and not for GSM Radio and is thusnot applicable to BSS14. TrFO uses out-of-band signaling for control. TrFO providesdirect transmission savings in core network.

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

(BB2E or BB2F) is needed for this feature


MS: AMR capable MS required

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - CX7 CXM7 N N N N EP3.0 OSS5.2 - M14 - X




4.5 A5/3 ciphering


Summary: A5/3 is a new, more secure; 3GPP standardized ciphering method and isbased on the same core algorithm as used in WCDMA. Ciphering is performed by theBTS. BSC selects the ciphering algorithm based on the information received from theMSC and the information about allowed and supported algorithms in the BSS and MS.

Benefits for the Operator : A5/3 gives the possibility to use more secure cipheringmethod over radio interface.

Functional Description: A new, more secure ciphering method has been standardizedand is advised to take in use to replace the A5/1 algorithm. A5/3 is based on Kasumi F8which is also used in WCDMA RAN.Ciphering is performed by the BTS burst by burst. The BSC selects the ciphering

algorithm based on the information received from the MSC and the information aboutallowed (and supported) algorithms in the BSS.

In the BTS, the A5/3 algorithm will be supported only by the EDGE BB of the TRX,because in EDGE BB has enough DSP capacity for this feature. Therefore, the BSCmust check if the TRX is A5/3 capable before selecting the ciphering algorithm. BSC willuse the BB Unit Type parameter, which was added to the Abis O&M interface in S13.

Note: Current standardisation sets a restriction for changing ciphering algorithm duringDTM reallocation. DTM Assignment Command message does not include Cipher ModeSetting IE before 3GPP Rel-7 and that's why ciphering algorithm could not be changedfor Rel-6 MSs during reallocations between EDGE TRXs supporting A5/3 and GPRS

TRXs supporting A5/1. For Rel-6 MSs ciphering mode shall be changed with assignmentprocedure, which means leaving the DTM mode for a while. A Rel-7 MS will indicate itssupport for ciphering mode change during DTM assignment procedure.

BTS HW: Edge MetroSite TRX is needed for this featureUltraSite Edge Baseband unit (BB2E or BB2F) is needed for this

Operational Aspects: BSC have to know the ciphering capability of each TRX in theBSS or else non-homogeneous BSS can not be supported.


MS: A5/3 capable MS required

Dependency Table:

BSS BSCS DX200Platform

BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - CX7.0 CXM7.0 N N N N EP3.0 OSS5.2 - - - X




4.6 SDCCH and PS Data on DFCA TRX


Summary: The gains from the feature Dynamic Frequency and Channel Allocation(DFCA) introduced in BSS11.5 can be fully exploited by also supporting the SDCCH andGPRS/EDGE channels in the DFCA layer. No separate planning for additional non-DFCA TRX is then required which saves frequency bands significantly.

Benefits for the Operator: Capacity: DFCA gains to its full potential. SDCCHcapacity no more limited to regular TRXs.OPEX: No separate planning for additional non-DFCA TRX.

Functional Description: The current DFCA feature can handle only Circuit Switched(CS) traffic and thus Packet Switched (PS) layer and CS layer must be separated(different TRXs). As PS traffic is increasing it often requires more than one TRX (BCCH)which consumes frequencies from dynamic DFCA layer and decreases spectralefficiency, and causes some extra needs for planning/management as well.

With this extension to the DFCA feature it will be possible to assign SDCCH and PStraffic also to DFCA TRXs. Then it would be only BCCH TRX that remains out of DFCA'sreach.PS territory would upgrade and downgrade freely over TRXs without DFCA relatedrestrictions. Similarly, both static and dynamic SDCCH channels would be possible inDFCA layer.


BTS HW: MetroSite Edge TRX is needed for this feature.UltraSite Edge Baseband unit (BB2E or BB2F) is needed for this feature.

Dependency Table:

BSS BSCS DX200Platform

BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - CX7.0 CXM7.0 N N N N EP3.0 OSS5.2 - - - -




4.7 AMR Unpacking Optimisation


Summary:With this feature also quality and level thresholds will be considered by intracell FR/HRHOs to avoid possibly unviable unpacking.

Benefits for the Operator : Call drop rate can be improved.

Functional Description:

Optimal functionality of unpacking is very important for AMR. To further optimizeunpacking two new parameters are introduced in HO algorithm.

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

If RX level is below this threshold then AMR unpacking, packing and interferencehandovers (the new type) are not allowed.

In case of rapid field strength drop, quality also typically drops. This easily triggers AMRunpacking handovers. If the field drop is high enough quality goes such bad that themobile cannot possibly decode the handover assignment, thus the mobile cannotperform HO. Normally radio link timeout timer controls the time how long the mobile canbe unreachable before the TCH is deactivated and the call is seen as a drop. This canbe e.g. 16 seconds. But when a handover is started is used a fixed 6 seconds timer tocontrol handover success. If the MS does not answered during this time eithersuccessful or not successful handover, the BSC deactivates the target channel and alsothe source channel. This is a drop. So without an intracell handover start the MS haveabout 10 seconds more time to get out off bad coverage.

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

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

Basically this is the same thing than the level limit but based on quality. When the MSmoves around a corner it can happen that it's own RX level is not changing but theinterferer gets rapidly a lot stronger. This can cause that MSs quality drops to e.g. 7thlevel. In the 7th level can easily happen that the MS fails SACCH decoding and hencecannot identify any handover assignment request. Consequences of this are then thesame as when a handovers is started in rapid field drop case.

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




Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 - - - - - - - - - - - - - -




5 Packet Switched Data

5.1 Improved Extended UL TBF


Summary: This feature saves mobile battery by allowing MS not to transmit dummyblocks when having no real data to send.

Benefits for the Operator :- Increased battery lifetime in mobile terminals.- Reduced uplink interference.- Enables more effective use of Extended UL TBF mode.

Functional Description:Currently MS in Extended UL TBF mode having no RLC data blocks to send transmitsdummy data block when uplink resource is allocated by USF. Obviously this may causeunwanted battery consumption in the mobile station and unwanted interference in uplink.

BSS may allow, with broadcasted cell parameter, MS not to transmit above mentioneddummy blocks. With this feature, the network may keep MS longer in Extended UL TBFmode and also use more regular USF scheduling resulting in shorter latency or Round-trip Time (RTT).

A potential drawback of this solution could be that the network cannot know for sure if asilent period means that the mobile station has not send, or that the mobile station sentsomething which got lost due to e.g. uplink interference. However, the BSS mayregularly poll for an RLC/MAC control block on the uplink by using the RRBP field andthus such a discrepancy can be avoided.


BSC HW: PCU2

MS: GPRS/EDGE capable MS with support for improved extended UL TBF.

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalk

Family

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexi

EDGE


Release BSS14 S14 - - - - - - - - OSS5.2 - - - X




5.2 Robust EDGE Retransmission


Summary: This feature enables original 8PSK modulated RLC block to be split into twoGMSK modulated blocks for retransmission in case of poor radio conditions.

Benefits for the Operator : This feature makes link adaptation between modulationsmore robust, thus bit rates especially at cell border area can be improved. In additionimproved GMSK RX performance of DARP mobile stations can increase the coverage.Larger latency contributions can be as well reduced because TBF started in 8PSK cancontinue fluently in GMSK. This may improve also abnormal TBF release KPI.

Functional Description: RLC Re-Segmentation in DL is triggered when reported DLMean 8PSK BEP is poor or 8PSK report is missing and re-segmentation is stopped by

link adaptation i.e. 8PSK becomes usable.RLC Re-Segmentation in UL is triggered when8PSK RLC headers are not easily decoded and stopped when BEP reports improves.

If RLC Re-Segmentation is not available original 8PSK transmission will be retransmittedwith 8PSK. This means that more robust GMSK can't be used as a fallback. Incrementalredundancy is not possible if headers are not correctly decoded.


BSC HW: PCU2

MS: GPRS/EDGE capable MS

Dependency Table:


BTSUltra

Site

BTSMetro

Site

BTSTalk

Family

BTSPrime

Site

BTSInSite

2ndGen

BTS

BTSFlexi

EDGE


Release BSS14 S14 - - - - - - - - OSS5.2 - - - X




5.3 Downlink Dual Carrier


Summary: This feature enables the possibility to allocate two parallel separate DLcarriers for one user in the same cell.

Benefits for the Operator : This feature doubles downlink peak throughput up to 592kbps. The average throughput can exceed 300kbps which enables e.g. streaming of highquality video exploiting the latest video capabilities of handsets.DLDC also significantly increases the resource efficiency (up to 160%) due to thetrunking gain.

Functional Description: In a downlink dual carrier configuration, radio resources areassigned to a single MS on two radio frequency channels (much in the same way asusing two radio time slots today). One of these channels can be e.g. the in BCCH carrier

and other in a TCH with frequency hopping.MS receives both radio frequency channels, thus DL throughput can be doubled. In theUL direction the MS may dynamically alternate between the carriers, to maximiseutilisation of uplink resources.




With this feature it is possible to add more PS users in the network to experience e.g.100 kb/s as shown in figure.


BSC HW: PCU2

MS: GPRS/EDGE capable Rel-7 MS

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - - - N N N N - - SG8 - - 3GPPRel-7




6 Operability

6.1 Energy saving mode for BCCH TRXS


Summary: This feature introduces a new configurable power saving mode for BTSBCCH TRXs,.

Benefits for the Operator : Lower network OPEX by reduced energy consumption.

Functional Description: With Energy Saving Modes for BCCH TRX the dummy burstson idle timeslots of the BCCH carrier are transmitted at 2 dB lower power level, and theBSC will use 2 dB dynamic power control on circuit switched TCHs in the BCCH TRX.

Together these features give reduced electricity consumption throughout the whole day. Also the Energy saving mode for BCCH TRX feature can be set according to the time ofday, so that (for example) it is active overnight, during the period of low traffic.

Figure:

Current Implementation: This is a new functionality


BTS HW: Edge UltraSite TRXs or FlexiEDGE is needed to support this feature




Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - CX7 N N N N N EP3.0 OSS5.2 - - - -

6.2 Flexi EDGE DTRX Automatic Power Down


Summary: This feature introduces new energy saving mechanism for FlexiEDGE BTS.With this feature operator can shutdown DTRX to save energy (electricity) during the low

traffic times i.e night time.Benefits for the Operator : Lower network OPEX by reduced energy consumption.

Functional Description: Feature brings in functionality to shutdown TRXs. During thelow traffic hours the BSC can take the TRX out of service and command the Flexi EDGEBTS to turn off the -48V supply to the DTRX.

Estimated Power Saving for DTRX is around 40 Watts. Feature can be used forconfiguration where is there more than one DTRX in a cell.

Estimated power savings in different configurations:Epsilon 4+4+4 shutdown to 2+2+2 120 Watts

Epsilon 6+6+6 shutdown to 2+2+2 240 WattsEpsilon 8+8+8 shutdown to 2+2+2 360 WattsEpsilon 12+12 shutdown to 2+2 400 Watts

This feature can be utilised in Flexi EDGE BTS configurations were there are 2-6 DTRXs(3 ... 12 carriers) in the cell.

Interdependencies between Features: Feature cannot be utilised for DTRXs that haveBaseband Hopping or Antenna Hopping enabled


BTS HW: This feature requires Flexi EDGE BTS

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - N N N N N N EP3 OSS5.2 - - - -




6.3 Secure remote MMI


Summary: Secure Shell protocol (SSH) could be utilised in remote BSC MML sessions.

Benefits for the Operator : Enhanced risk management is achieved because ofimproved O&M network security.

Functional Description: Telnet is replaced with SSH (Secure Shell) protocol in MMLinterface (MMI)SSH protocol provides encryption, integrity protection and server authentication, whichimproves the security of MML interface. Especially the user names and passwords arenot delivered in clear text any more.Integrity protection and server authentication prevents manipulation of MML commandsduring the transfer.

Figure:




Current Implementation: Telnet is supported in remote man to machine interface(MMI).

Interdependencies between Features: When this feature is turned on, Telnet

connection cannot be used anymore in BSC MML sessions.


Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - - - - - - - - OSS5.2 - - - -

6.4 PCU Restart Handling


Summary: This feature introduces support for single PCU restart in BSC.

Benefits for the Operator : Recovery actions for PCU card failure and someconfiguration changes has less effects to traffic carried by BSC.

Functional Description: This feature makes it possible to restart only one logical PCU

in case of failure so that whole BCSU unit will not need to be restarted. In the existingimplementation whole BCSU unit has to restart when some PCU unit becomes faulty.This new feature is useful especially with the new High Capacity BSC3i in which therecan be maximum 10 logical PCUs (five PCU plug-in units) in one BCSU unit. In BSC3ithere are two logical PCUs in each PCU plug-in units. If some PCU becomes faulty firstthe faulty PCU will be restarted and if that will not help, then restart or switchover ofwhole BCSU unit occurs.


BSC HW: PCU1 and PCU2

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 B13 - - - - - - - - - - - -




6.5 OSI over TCP/IP

Feature ID: BSS719

Summary: This feature introduces TCP/IP protocol support for BSS Q1 and Q3 O&MInterfaces and interface towards Cell Broadcast Center (CBC).

Benefits for the Operator : Reduced Capex and Opex due TCP/IP usage instead of ISOIP.

Functional Description: Feature introduces tunneling the Q3 based BSC - NetActinterface inside TCP/IP. This feature removes the need for using ISO IP routers in DCNNetwork. Licenses for these kinds of OSI routers are expensive compared to today’sTCP/IP routers. Current situation can be seen in picture below:

BSC

Current situation with ISO IP routing

OMU

S

W

UCisco 3750

L2 / L3

NetAct

Cisco

2811

L3

IP backboneCisco

3845

O&M

VLAN

CLNS

over IP

tunnel

router fortunneling

CLNS over IP

BSC site

router

NetAct siterouter

ISO IP traffic

ISO IP traffic insideIP tunnel

This feature brings changes to functionality that is at the moment responsible for datadivision between digital X.25 and LAN (ISO IP). With OSI over TCP implementation all IPtraffic coming from OMU ethernet port is pure TCP/IP. This means:

– extra router (Cisco 2811) for OSI traffic tunneling is not needed – simplifies BSC site IP configuration – no dependence on Cisco routers any more – O&M Security can be enabled

▪ can be utilized with IPSec feature• OSI traffic comes also through TCP/IP stack of OMU

▪ Improves handling of usernames & passwords of OSI services – O&M redundancy




▪ Existing BSC site IP implementation is redundant. It can be fullyutilized

TCP/IP based interface can also utilized now towards Cell Broadcast Center.

Current Implementation: O&M interface is based on 'OSI based interface' where PCMor ISO IP can be utilised

BTS HW Requirements: TCP/IP routers have be used instead of ISO IP routers


Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 B13 - - - - - - - OSS5.2 - - - -




6.6 Automated RNW O&M log collection


Summary: This feature introduces new logging functionality in BSC.

Benefits for the Operator : Opex saving due to to faster troubleshooting time

Functional Description:Storing of Radio Network Fault Data feature stores all relevant RNW specific operationsin BSC into the log file in OMU's disk.

RNW O&M operations which will be log are:o initializationo recoveryo TRX swap

o SI sendingo lock/unlocko conf data sendingo BCF/BTS/TRX reseto system restarto BCSU/PCU restarto BVC creation/deletion/state changingo Gb up/downo plan activation

In fault cases the operator can now sends the log file to Nokia Technical Support for faulttracing.

Begin of RNW specific operation BSC program block writes to the log detailedinformation about operation. This is fingerprint what the system is going to do. Onlyrelevant information is written into the log which helps fault tracing. After RNW operationhas been executed BSC program block writes to the log how operation was succeeded. Also all error situations are written into the log. So fault solving is easier when we cantrace from every single operation what was planned and how it was succeeded.

BSC & TCSM HW Requirements: This feature can be used only with PCU2

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 - - - - - - - - - OSS5.2 - - - -




7 Multiradio Interworking

7.1 Load Aware ISHO Admission


Summary: Source system load info is carried through CN to target system. Handovertarget system evaluates the load of the source cell and accepts or rejects the handoverrequest accordingly. This feature prevents inter-system handovers to already highlyloaded target but admits urgent handovers even in case of activated penalty timers.

Inter-system handover cause is transferred as well to the target system for criticalityevaluation. With this criticality information the target system can admit handover requesteven in high load situations and correspondingly reject the non-critical handoverattempts.

Benefits for the Operator : Radio network behavior is optimized in high load conditionswhile keeping the number of unnecessary handover attempts towards already loadedsystem and related signaling load at moderate level.

Criticality information allows handover target system to accept a critical request even inhigh load and thus to avoid severe quality deterioration or call drop in source system.

Functional Description: This feature introduces load and criticality informationexchange between BSC and RNC via the core NW. Load info is transferred transparentlyon relocation and HO messages. The criticality is derived from handover cause. Thetarget system then can evaluate the urgency of ISHO and accept or reject with penalty

timer accordingly.



Figure:

Source load aware ISHO admission

• Source cell load info is carried through CN to target system

• Target system evaluates the load of the source and target cells as well as theurgency of ISHO and then accepts or rejects the handover request accordingly

• Prevents non-urgent ISHO to already highly loaded cell but triggers and admitsurgent handovers even in case of active penalty timer

Optimized high load behavior while keeping the number of unnecessaryhandover attempts and related signaling load at moderate level.

Optimized high load behavior while keeping the number of unnecessaryhandover attempts and related signaling load at moderate level.

Load of the source BSC and

ISHO criticality indication are

included in the ISHO request

Current load of the sourceBSC and target RNC available

for ISHO admission decision

RNCBSC

Core network

Sourcesystem

Targetsystem

WCDMAWCDMA

GSM/EDGEGSM/EDGE

MS: Dual Mode MS

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

BSC SW: Application Software

Dependency Table:


BTSUltraSite

BTSMetroSite

BTSTalkFamily

BTSPrimeSite

BTSInSite

2ndGenBTS

BTSFlexiEDGE


Release BSS14 S14 - - - - - - - - OSS5.2 - X X -

BSS_14_Feature_Candidates_(FCD)_Ver_1.5.0.pdf

Documents