rg20 feature svu

5/27/2018 RG20 Feature SVU

1/62

1 Nokia Siemens Networks Presentation / Author / Date

For internal use

RG20 Features - SVU


2/62


For internal use

RG20 Features

Energy Optimised TCH Allocation BSS21222 Orthogonal sub channel (BSS21309, BSS30385)

Local Switching for Packet Abis BSS21327

CCCH Improvements in BSS (BSS20738, BSS21538, BSS101411)

Merged P- & E-GSM900 BSS21238

LTE System Information and NACC improvements (21353,20083,21045,21355)

Downlink Dual Carrier (DLDC) RG10 BSS21228, RG20 BSS21343,BSS21392

Flexi BTS auto connection BSS21316

Packet Abis Synchronisation BSS21439 & BSS30450

Automatic EDAP reallocation in PCU (BSS21232 & BSS20045)

RG20 (BSS) Network Engineering Information A over IP BSS21341

Abis Delay Measurement (TDM, PWE3) BSS21271

NoteRG20 enabling can be found from IMS: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/410495798

Features to be introduced

In Annex
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/410495798https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/410495798https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/410495798https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/410495798


3/62


For internal use

Energy Optimised TCH Allocation

BSS21222


4/62


For internal use

The existing allocation rules are not optimal from the point of view of a DL RX levelexperienced by MSs:

Solution:Energy optimised TCH Allocation provides GSM operators with agreater means to control the allocation of TCH channels, now also including theaspect of power consumption


Call far away from BTS

call is on TCH

=>Full power is usedCall near the BTS

Call is on BCCH

=> Full power is used

In both cases full power is used!!

TCH Allocation


5/62


For internal use

The TCH allocation at a call setup is done based on the DL RX level reported inmeasurement reports by an MS at the SDCCH signalling phase

upperDL RX level threshold for the BCCH TRX preference

lower DL RX level threshold for the BCCH TRX preference

if the level is between the thresholds then the BCCH TRX is selected for the TCH

allocation, otherwise the TCH TRX is selected


TCH Allocation

power distribution BCCH

0

500000

1000000

1500000

2000000

2500000

3000000

-120 -100 -80 -60 -40 -20

power [dBm]

#samples

candidates for BCCH layer

candidates for TCH layer

apply RXLEV PC


6/62


For internal use


1. Impact on KPIs less power is used Interference level is decreased If better quality => possible less drops, improved HOSR and PS KPIs

2. Counters / parameters New parameters (2) / counters (4) are introduced Parameter threshold setting is playing important role

3. Dimensioning Not affecting

4. Other Feature is working

On call setup procedures

During all internal (intra-BSC) imperative and non-imperative HOs External HOs, according to TRP parameter

Note!the DL RX level is NOT a trigger for the HO procedure to switch between BCCH andTCH TRXs

Green feature

Impact on Planning


7/627 Nokia Siemens Networks Presentation / Author / Date

For internal use

Orthogonal Sub-channelOSC Half Rate with SAIC MS (BSS21309)Circuit Switched Dynamic Abis Pool (BSS30385)



For internal use

Orthogonal Sub-channel

OSC serves 4 AMR Half Rate calls in the same GSM timeslot

Different training sequencesseparate users in downlink and uplink

Two standard SAIC handsetsreceive their own sub channel in QPSK

MIMO receiver in the BTS receives two standard GMSKsignals Normal 2-way diversity antennain BTS

Standard AMR transcoding and TRAU frames

Adaptation(e.g. AMR FRAMR HRDHR) to maintain quality & coverage

I(A)

Q(B)

(0,0) (1,0)

(0,1) (1,1)

Users (A,B) in QPSK

Decoding

Decoding

MIMO

Receiver

A

B

QPSK

Transmitter

Encoding

Encoding B

B

A

A



For internal use

Characteristics of OSC

General rule for MU-MIMO: RX Antenna per user Exploits (orthogonal) multi path propagations

Pairing of users with similar path loss is preferred

Level offset between two users minimized by power control

Some limitations

For Flexi EDGE BTS (SW:EX4.0)

For SAIC-capable MS (penetration 30-40%)

User-A

User-B

Deciphering Decoding

Deciphering Decoding

MU-MIMO

Receiver Abis

MU-MIMO

TRX

RG20



For internal use

Orthogonal Sub-channel Double Half Rate

1. Impact on KPIs If frequencies can be removed => better quality In refarmingsame good quality with less frequencies! If quality is improved => drops / HOSR /PS KPIs will be improved

2. Counters / parameters New parameters (20) / counters (24) are introduced

OSC RX Quality Measurements: counters (122000-122079) Parameter threshold setting is playing important role

3. Dimensioning Max 4 calls per RTSL => is effecting on capacity planning heavily Good solution in refarming case

4. Other Is effecting on abis capacitysee next slides Important feature in refarming caseGSM capacity can be handled with this

feature

Capacity strategy can be based on this feature

Impact on Planning



For internal use

Orthogonal Sub-channelOSC Half Rate with SAIC MS (BSS21309)Circuit Switched Dynamic Abis Pool (BSS30385)



For internal use

Introduction

Orthogonal Sub-channelCircuit Switched Dynamic Abis Pool

For OSC DHR mode more Abis transmission isneeded for radio timeslot because two calls aremultiplexed in one HR channel

a single RTSL carrying FR cal is mapped toa single Abis sub-TSL

a single RTSL carrying HR (1 or 2 calls) is

mapped to a single Abis sub-TSL in OSC mode 2 DHR calls are transmitted in

the same time (i.e. time slot as these callsare distinguished by different TSC):

OSC-0 channels always use PCM resourcesreserved for TCH

OSC-1 channels always use PCM resourcesreserved in CSDAP

MS1

FR

MS1

HR

MS2

HR

HR (time)multiplexing

HR (time)multiplexing

MS3OSC-0

MS2OSC-1

OSC

multiplexing

MS4OSC-1

MS1OSC-0

FR HR OSC DHR



For internal use

Orthogonal Sub-channelCircuit Switched Dynamic Abis Pool

1. Impact on KPIs Abis/PCU blocking should be monitored. CSDAP is reducing normal EDAP capacity

2. Counters / parameters New parameters(9) / counter (4) are introduced

OSC RX Quality Measurements: counters (122000-122079)

3. Dimensioning Abis / PCU capacity must be monitored carefully

4. Other

Requirements:Circuit Switched Dynamic Abis Pool (BSS30385) or packet

Abis configured

Impact on Planning



For internal use

Local Switching for Packet Abis

BSS21327



For internal use

IntroductionPacket Abis overview

Packet Abismeans introduction of a new transport concept:

Abis framesconveying traffic and signaling information between BTS and BSC aresubject to packetizationprocess prior to sending them to the transmission path as a result of packetization the incoming TRAU/PCU/LAPD framesare converted to

new (Packet Abis specific) formats which are encapsulated and form IP packetseventually transmitted over Abis

these principles are valid regardless of physical media used in transportnetwork; inRG20there are 2 possible realizations of transport network for Packet Abis:

Packet Abis over TDM Packet Abis over PSN (Ethernet)

With Packet Abis bandwidth savings compared to legacy Abis: removal of unneeded bits (e.g. header information of TRAU/PCU frames) or even the

entire frames (e.g. idle frames)

silence suppression statistical multiplexing due to unbalanced sectors load and reuse of common bandwidthby different types of traffic (trunking gain)

efficient usage of bandwidth which is allocated according to the actual needs (i.e. nobandwidth is wasted due to granularity, no empty packets are transmitted)



For internal use

Normally, MS-to-MS calls are always transferred through all network elements of the GERAN

network, i.e. BTSs, BSCs, trans-coders and a core network

Such the concept, known as local switching, is valid for speech data only => signalling datawould be transferred traditionallyto allow using existing features

Local switching does not apply to PS calls as well because normally a PS call is establishednon-locallybetween MS and a server (GGSN) and not between two MSs


BSC1BTS1 MSC1TRAU1 MSC2 TRAU2 BSC2 BTS2MS1

MS2

Speech andsignalling

E1/T1

Abis

Calls and related signalling are

transferred through all network entities

BSC1BTS1 MSC1TRAU1 MSC2 TRAU2 BSC2 BTS2MS1

MS2Speech Signalling

E1/T1

Abis

Introduction

Abis capacity is saved



For internal use


1. Impact on KPIs Voice is causing less traffic for abis => more PS traffic can be

allocated

TrFO is applied => speech quality (MOS) will be improved

2. Counters / parameters New parameters (4) / counters(15) are introduced

3. Dimensioning Abis traffic due to voice will be reduced => abis dimensioning

4. Other

Impact on Planning


18/62


For internal use

CCCH improvements in BSSBSS20738 CS Paging Coordination in NMO II

BSS21538 Extended CCCHBSS101411 Extended BCCH


19/62


For internal use

Currently BSC3i provides CS paging co-ordination only in NMO I

regardless of the DTM feature state (enabled/disabled).

CS Paging Coordination in NMO II means that MS in PacketTransfer Mode can be paged for CS connection with PacketPaging Request messages sent on PACCH

CS paging can be received via Gs-i/f or A-i/f (if no Gs-i/fbetween MSC and SGSN)

CS Paging makes MS to abort PS session before CSconnection setup

BSC creates a record for MS (with IMSI, TLLI, Segment ID and PCUaddress) into a hash table (i.e. IMSI database) when it receives info thatactive TBF for that MS exists.

Feature details

CS Paging Coordination in NMO II


20/62


For internal use

CS Paging Coordination in NMO II

1. Impact on KPIs Paging KPIs possible improved Depending for example usage of PS services

2. Counters / parameters New parameters (1) /counters(2) are introduced


4. Other This feature is very important in case of SMART phones as those mobiles

generates huge PS traffic volume and are very often in Packet TransferMode. Without this feature and w/o Gs interface MS in Packet Transfer Modeis unreachable what increase customer dissatisfaction (specially whenautomatic SMS is sent informing subscriber about unsuccessful incomingcall)

Impact on Planning


21/62


For internal use




22/62


For internal use

With the Extended CCCH feature operator can define 1, 2 or 3 extended CCCH

channels continuously to the time slot numbers 2, 4 and 6 in the TRX, whereBCCH channel number 0 is configured with 9 uncombined CCCH blocks.

Extended CCCH channel contains 1 BCCH block and 9 uncombined CCCHblocks (each timeslot with CCCH contains 1 BCCH block)

SCH and FCCH channels are not present and they are replaced by dummy bursts(IDLE).

It is required that the non-combined BCCH (MBCCH) is configured on time slot 0.

Feature details

Extended CCCH


23/62


For internal use

Extended CCCH

1. Impact on KPIs Paging KPIs possible improved, for example paging success rate More CCCH capacity available

If lots of short TBFs => more CCCH capacity is needed

2. Counters / parameters New parameters(3) are introduced No new counters are introduced

3. Dimensioning More CCCH capacity, less TCH capacity. Might affect on TCH

dimensioning.TCH capacity must be monitored

TRXSIG capacity might needs to be enhanced

4. Other

Impact on Planning


24/62


For internal use




25/62


For internal use

This feature was requested by CMCC where TD-SCDMA is deployed asthe mechanism to speed up cell reseletion and HO to 3G

With coexistance of GSM and TD-SCDMA, there are more and more SIon GSM side. Unfortunately, too long SI need more individual SI

messages and UE need more time to read them, it means more time for

HO and Update

Typically System Information messages are scheduled over the BCCHchannel of the BCCH frequency on the timeslot 0.

With Extended BCCH feature the time which is required for SystemInformation (SI) update to mobile, can be reduced by moving SI 2 quater

message sending to an extended BCCH sub channel in BCCH TRX.

Feature details

Extended BCCH

Information element Presence Format LengthL2 Pseudo Length Mandatory Variable 1RR management ProtocolDiscriminator

Mandatory Variable 1/2

Skip Indicator Mandatory Variable 1/2SI Type 2quater Message Type Mandatory Variable 1

SI 2 quater Rest Octets Mandatory Variable 20


26/62


For internal use

TDMA frame mapping for BCCH channel 0 (uncombined) with extended BCCH

(FCCH + SCH + BCCH + ext BCCH + CCCH/8):

Extended BCCH channel contains 2 BCCH blocks and in uncombined

configuration only 8 CCCH blocks are available (instead of 9).This reduces CCCHcapacity by 1 block (in scenario with 1 CCCH this means reduction by 11%)

TDMA frame mapping for BCCH channel 0 (combined) with extended BCCH

(FCCH + SCH + BCCH + ext BCCH + CCCH/4 + SDCCH/4):

In combined configuration only 2 CCCH blocks are available (33% of CCCH

capacity reduction)

Feature details

Extended BCCH


27/62


For internal use

Extended BCCH

1. Impact on KPIs speed up cell reseletion and HO to 3G=> Cell reselection and HO KPIs might be improved

Reduce CCCH capacity

2.Counters / parameters New parameters (1) are introduced

No new counters are introduced

3. Dimensioning Depends on the 2G / 3G capacity strategy

Easier to put traffic to 3G => affecting on dimensiong

Reduce CCCH capacity. Paging capacity must be monitored

4. Other

Impact on Planning


28/62


For internal use

BSS21238 Merged P- & E-GSM900


29/62


For internal use

Introduction

Merged P- & E-GSM900

E-GSM

890 - 915 MHz880 - 890

P-GSM

935 - 960 MHz925 - 935

P-GSME-GSM

E-GSM E-GSM

History In the Nokia Siemens Networks BSS BSC solution E-GSM frequency band

covers only the frequencies that are outside the PGSM 900 frequency band.

The purpose to separate these 2 different band was

to avoid problems with PGSM-only terminals and to assure that PGSM-only terminalsare exposed only to the frequencies that they support

Merged PGSM and EGSM means that: E-GSM and P-GSM are merged, both resources can be used

GPRS/EDGE is allowed to be use, even BCCH is on other band

BSC allows both PGSM900 and EGSM900 frequencies in an MA or DFCA MAlist


30/62


For internal use

Merged P- & E-GSM900

1. Impact on KPIs Easier to frequency planning => quality will be improved

If quality is improved => most of CS and PS KPIs will be improved

2. Counters / parameters No new counters / parameters


4. Other

Impact on Planning


31/62


For internal use

LTE System Information and NACC improvementsLTE System Information (21353)Inter-BSC Network-Assisted Cell Change (20083)Inter-System Network Assisted Cell Change (21045)Inter-System Network-Assisted Cell Change from LTE (21355)


32/62


For internal use

LTE System Information

Service Continuity for dual mode 2G & LTE Operation

GSM/EDGE-LTE Interworking may consist of different mobility mechanisms for PS Services: Cell Selection (CS) and Re-selection (RS) - NC0 and NC1

Network Assisted Cell Change (NACC) from LTE to GSM (BSS21355)

Options for Voice Call Continuity from LTE to GSM/EDGE: CS Fallback- where Voice Services / Emergency Calls are directed from LTE to GSM (via NACC) Single Radio Voice Call Continuity(SRVCC) - where the Core Network translates the VoIP Call

across as an incoming CS Handover for GSM

DTM

LTE idle

LTE active

2G idle

2G PS 2G CS

PS HO

CS&RS


33/62


For internal use


2G 3G cell reselection:

Old Case:Suitable 3G cell is selected if for the period of 5 sec all the conditionsare met:

- CPICH RSCP of the 3G cell > RLA_C of the serving (GSM) cell +FDD_Qoffset

- CPICH Ec/No of the 3G cell FDD_QminFDD_Qmin_Offset

- CPICH RSCP of the 3G cell FDD_RSCP_threshold

-

New case:New algorithm for inter-RAT reselection from 2G- There is at least one measured non serving cell with higher priority inter-RAT

frequency- gsmPriority, wcdmaPriority, lteAdjCellPriority

- There is no measured non serving cell with higher priority inter-RAT frequencyfor which conditions related to Case 1 (see previous slide) are satisfied

AND

-For serving and all measured neighbouring GSM cells during T_reselection(timeHysteresis):

- Only minimum signal strength criteriaof the neighbouring cells are consideredfor higher priority cells (and also minimum quality criteria in case of 3G cell)


34/62


For internal use


1. Impact on KPIs Idle mode mobility to LTE => Better 2G / LTE traffic handling

These are affecting on basic KPIs

2. Counters / parameters New parameters (24) are introduced

No new counters

3. Dimensioning Better 2G /3G/LTE interworking, is affecting on dimensioning

4. Other

Impact on Planning


35/62


For internal use

LTE System Information and NACC improvementsLTE System Information (21353)Inter-BSC Network-Assisted Cell Change (20083)Inter-System Network Assisted Cell Change (21045)Inter-System Network-Assisted Cell Change from LTE (21355)

RG20 (BSS)


36/62


For internal use

The aim of the Network Assisted Cell Change(NACC)feature is to provide with certain target cell system informationalready on the source cell in order to reduce the serviceoutage time during the reselection process.

Three features are introduced in RG20 for improving BSS11.5NACC functionality by means of:

Inter-BSC NACC (IB-NACC) NACC between different BSCs

Inter-System NACC (IS-NACC) NACC from UTRAN to GSM

Inter-System NACC from LTE (LTE-NACC) NACC from LTE to GSM

Introduction

RG20 (BSS)NACC Improvements Feature details

NACC I t


37/62


For internal use

NACC Improvements

1. Impact on KPIs More NACCs, data services will be improved

reduction of service outage time during reselection process.

Throughput and delay KPIs will be improved

2. Counters / parameters New parameters(3) / counters(5) are introduced

3. Dimensioning 2G / LTE interworking => affect on PS capacity planning

4. Other

Impact on Planning


38/62


For internal use

Downlink Dual Carrier (DLDC)RG10:BSS21228 DLDC,RG20:BSS21343: DLDC-aware EGPRS territory managementRG20:BSS21392: TRX-specific Link Adaptation for DLDC

Downlink Dual Carrier


39/62

39 Nokia Siemens Networks Presentation / Author / DateFor internal use

Downlink Dual CarrierIntroduction

Single carrier allocations in Downlink and Uplink

Up to 5 TSLs in DL - max MS Multislot Class capability supported by PCU2(Class 40-45)

Up to 296 kbps (5TSLs @ MCS9) of theoretical peak LLC data throughput

Up to BSS13

RG10

c1

c1

c2

DL TBF may be allocated on 2 carriers

Higher number of TLSs allocated for DL TBFs

Up to 10 TSLs in DL (with 2 carriers)

Up to 592 kbps (10TSLs @ MCS9) of theoreticalpeak LLC data throughput

Using two carriers requires new 2-receiver terminals(3GPP Rel. 7 MS)

D li k D l C i


40/62


Downlink Dual CarrierIntroduction

RG20 (BSS21343 & BSS21392)

BSS21343: DLDC-aware EGPRS territory management DLDC allocations are possible even if default EGPRS territory is

configured on 1 TRX only

PCU2 may request EGPRS territory to be extended over the 2ndTRXif there is any DLDC capable MS having on 1 TRX only

PCU2 calculates the amount of needed TSLs and requests theterritory upgrade accordingly

BSS21392: TRX-specific Link Adaptation for DLDC

an individual MCS is used for each TRX quality aware TRX scheduling: frequency hopping TRXs have higher

priority than non-FH ones

D li k D l C i


41/62


Downlink Dual CarrierAffecting on Network Planning

CS and PS peak values at

the same time => bad forPS timeslot allocation =>lots of downgrading

D li k D l C i


42/62



1. Impact on KPIs See next slide

2. Counters / parameters New parameters(6) / counters(16) are introduced

3. Dimensioning More timeslots for PS => EDAP dimensioning

4. Other

Impact on Planning

D li k D l C i


43/62



1. Quality

If TRXs must be added due to data services => interference level will be increased All frequencies must be as clean as possible (MCS selection) so Frequency planning

is playing very important role

2. Handovers If more TRX due to data services => interference level will be increased

HO failure will be increased

3. Drops

If more TRX due to data services => interference level will be increased Drops will be increased

4. Blocking More RTSLs for data must be available to get full advantage CS Blocking => no TSLs for data services, default area can not be used PS Blocking => no fully advantage

5. PS KPIs Throughput / timeslot is strongly depending on quality MCS is adjusted to the radio conditions of the poorer carrier => all frequencies must

be as clean as possible

TBF / tsl is decreasing if more timeslots for data available EDAP/ PCU/ Gb blocking can be higher due to increased data Transmission KPIs are more important due to increased data

Total throughput will be increase because up to 12 RTSL in DL available

Impact on KPIs


44/62


End of the presentationMore features in Annex (See next slides)


45/62


Annex

Some more features to be introduced


46/62


Packet Abis Synchronisation

BSS21439 & BSS30450



47/62



Frequency Accuracy vs. Frequency Stability



48/62


In BSS15 the following synchronisation techniques are

presented: IEEE 1588v2 Timing-over-Packet (ToP)

Master clock is sending sync packets to the slave clock periodically, frequencyaccuracy can be calculated from these packets

Adaptive clock recovery (ACR) already known from the BSS14

pseudo-wire emulation (PWE) feature The idea of the method is based on the assumption that there is a constant flow of

trafficbetween a master clock and a slave clock => then the slave clock is able toregenerate a clock frequency according to a received bit stream

Synchronous Ethernet (SyncE) Synchronous Ethernet (SyncE) is a physical layer synchronisation method, i.e. it

makes use of a physical layer interfaceto pass timing from a master to a slave


In BSS15the synchronisation methods are employed to ensure the requiredfrequency accuracy (precisely: syntonisation) at a base station only, time

synchronisation is NOTrequired

Feature details



49/62



1. Impact on KPIs Possible less Abis synchronization problems

Less overflows or underflows of synchronisation buffers Less errors in incoming bit stream

2. Counters / parameters New parameters are introduced


4. Other

Impact on Planning


50/62


Flexi BTS Autoconnection

BSS21316



51/62



RG10 and earlier commonly used BTS commissioning

Lots of time consuming work Lots of preparing work

File extracting

Some editing task had to do manually

Flexi BTS autoconnection enables delivery of BTS dedicatedSCF file either fully automatically or in case of errors withremote admission control

BTS commissions are easier to perform.

BTS installation times will be reduced



52/62



1. Impact on KPIs Not affecting2. Counters / parameters

No New parameters / counters are introduced

3. Dimensioning When feature powered on, BTS starts to scan all available interfaces insearching for OMUSIG candidates

OMUSIG capacity must be enough in every PCM

4. Other Fewer issues during roll-outs => time savings Quicker BTS installing time => time savings

Impact on Planning


53/62


Automatic EDAP reallocation in PCU incl. PCUrestart handling

BSS21232 & BSS20045

PCU restart handling


54/62


PCU restart handling

Before RG20

if SW or HW fails in a PCU unitBCSU serving the faulty PCU is switched over to the spare one

BCSU with the faulty PCU is restarted even if other PCUs work properly

it means that up to 5 PCU units (10 logical PCU in case of PCU2-D) must berestarted at the same time

these actions have several negative side effects

during forced BCSU switchover on-going CS calls are dropped

it is not possible to establish new CS calls during BCSU controlled switchover

break in PS services

In RG20 PCU restart handling allows restarting a single logical PCU instead of restarting the

whole BCSU unit, or restarting more than one logical PCU by a MML command if PCU restart does not solve the failure situation, then the BCSU switchover is triggered

two types of PCU restart are possible PCU Hot restartrestart of dynamic Abis configuration in PCU

PCU Cold restartrestarts whole PCU

Introduction

Automatic EDAP reallocation in PCU


55/62


Automatic EDAP reallocation in PCU

Up to now (RG10)

in the present BSC implementation EDAPs are completely rearranged in PCUPCMsonly when the initial EDAP configuration is done, i.e. at a BCSU restart or switchover

EDAP timeslots cannot be moved in the PCUPCMs without the BCSU switchover / restart

however BCSU restart or switchover causes interruptions of CS calls served by the BCSUand interruptions of PS data transmissions in every PCU in the BCSU

when EDAP is modified, added, deleted or moved to another PCU a BSC searchesfree space in PCUPCM for EDAP in question only and all other EDAPs remains intheir original places

this might cause PCUPCM fragmentation => EDAP creation, modification or PCUpool reallocation, PS territory upgrade may be very limited or even cannot beperformed

In RG20

Automatic EDAP reallocation in PCU feature removes the problem of the PCUPCMfragmentation in BSC

add-on in comparison to RG10 is that after any EDAP modification, instead of BCSUrestart/ switchover which was recommended in earlier releases, PCU restart isenough to apply the changes in EDAP configuration

General feature information

Automatic EDAP reallocation in PCU incl. PCU restart


56/62


Automatic EDAP reallocation in PCU incl. PCU restarthandling

1. Impact on KPIs CS calls are not disturbed when EDAP operations are done => DCR

will be improved when EDAp operations will be done

2. Counters / parameters PCU restart handling => new parameters

No new counters


4. Other

Impact on Planning


57/62


RG20 (BSS) Network Engineering InformationA over IPBSS21341

Introduction


58/62


Introduction

In AoIP feature frames on A interface between BSC and MGW are

transmitted in PSN: Each frame is a subject to packetization process prior to sending it to the

transmission path

as a result of packetization the incoming frames are encapsulated into IPpackets and transmitted every 20ms over Ethernet based A interface

There is no multiplexing in AoIPeach frame is a single packet AoIP is standardized in 3GPP (any vendor CN eligible to supports IP

based A interface can work with NSN AoIP solution)

Due to removal of PCM lines between BSC and CN, synchronizationchain is broken and new methods are required for generation and

distribution of synchronization signal in GERAN.

AoIP feature can be realized in RG20 in two ways:

AoIP with Transcoding in BSS

AoIP with Transcoding in MGW

AoIP overview

A over IP


59/62


A over IP

1. Impact on KPIs Speech quality (MOS) will be improved with TrFO New types of Internal Handovers are introduced with AoIP feature

(BSS_int_HO, see also counters 42404250)

2. Counters / parameters New parameters / counters are introduced

3. Dimensioning Affecting on number of Ater and A PCMs. Dimensioning can be done with

dimensioning tool

SS7 calculator to estimate SIGTRAN bandwidth4. Other

Connectivity between NEs is most cost effective with usage of IP technology

Impact on Planning


60/62


Abis Delay Measurement (TDM, PWE3)BSS21271

Abis Delay Measurement (TDM, PWE3)


61/62



This feature provides delay measurement on the Abis interface for either

TDM based networks or IP based when PWE3 is in use To measure delay BTS sends a bit pattern in every 5 second to BSC via

dedicated for this operation 16kbps sub-channel in the PCM line

the measurement channel cannot be used to allocate OMUSIG, TRXSIG, DAPor TCH

This measurement channel is looped back in the BSC back to the BTS

ntroduction

BSCBTS

GSWB (*1)Networ

kinterface

Netwo

rkinterface

Measu

remententity

101101101

101101101

Measurement

manager

Measurement

manager

Measurement channel

OMUSIG

NetActNetAct

Round Trip Time

Network DelayInternal Delay Internal Delay

the BTS is responsible

for measuring timeinterval (Round TripTime) between sendingand receiving bit

pattern



62/62


1. Impact on KPIs Abis KPIs might be improved

2. Counters / parameters New counters are introduced


4. Other Abis KPIsbetter way to monitore abis TDM and PWE3 backhaul lines New measuremenst have been implemented

120TDM/PW Abis Delay Measurement

Impact on Planning

rg20 feature svu

Documents

tch trx

allocation of tch channels

comopen41049 rg20 feature

rg20 bss21343

interference level

power dbm

bcch layercandidates

bcch trx preference