You are on page 1of 62

RG20 Features - SVU

For internal use 1 © Nokia Siemens Networks

Presentation / Author / Date

RG20 Features
Features to be introduced
• 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

In Annex
• • • • •
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

Note RG20 enabling can be found from IMS: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/410495798
For internal use 2 © Nokia Siemens Networks Presentation / Author / Date

Energy Optimised TCH Allocation
BSS21222

For internal use 3 © Nokia Siemens Networks

Presentation / Author / Date

Energy Optimised TCH Allocation TCH Allocation • The existing allocation rules are not optimal from the point of view of a DL RX level experienced by MSs: Call far away from BTS • call is on TCH =>Full power is used Call near the BTS • Call is on BCCH => Full power is used In both cases full power is used!! • Solution: „Energy optimised TCH Allocation‟ provides GSM operators with a greater means to control the allocation of TCH channels. now also including the aspect of power consumption For internal use 4 © Nokia Siemens Networks Presentation / Author / Date .

otherwise the TCH TRX is selected power distribution BCCH 3000000 2500000 # samples 2000000 1500000 1000000 500000 0 -120 candidates for BCCH layer candidates for TCH layer -100 -80 apply RXLEV PC -60 -40 -20 power [dBm] For internal use 5 © Nokia Siemens Networks Presentation / Author / Date .Energy Optimised TCH Allocation TCH Allocation • The TCH allocation at a call setup is done based on the DL RX level reported in measurement reports by an MS at the SDCCH signalling phase – upper DL 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.

improved HOSR and PS KPIs New parameters (2) / counters (4) are introduced Parameter threshold setting is playing important role Not affecting 2.Energy Optimised TCH Allocation Impact on Planning 1. according to TRP parameter • Note! the DL RX level is NOT a trigger for the HO procedure to switch between BCCH and TCH TRXs “Green” feature For internal use 6 © Nokia Siemens Networks Presentation / Author / Date . Other • Feature is working • • • On call setup procedures During all internal (intra-BSC) imperative and non-imperative HOs • External HOs. Dimensioning 4. Counters / parameters • • • 3. Impact on KPIs • less power is used • Interference level is decreased • If better quality => possible less drops.

Orthogonal Sub-channel OSC Half Rate with SAIC MS (BSS21309) Circuit Switched Dynamic Abis Pool (BSS30385) For internal use 7 © Nokia Siemens Networks Presentation / Author / Date .

0) A (0.g.1) I(A) B Receiver Users (A.Orthogonal Sub-channel A QPSK Transmitter Encoding Encoding B A MIMO Decoding Decoding B (0.B) in QPSK OSC serves 4 AMR Half Rate calls in the same GSM timeslot • Different training sequences separate users in downlink and uplink • Two standard SAIC handsets receive their own sub channel in QPSK • MIMO receiver in the BTS receives two standard GMSK signals • Normal 2-way diversity antenna in BTS • Standard AMR transcoding and TRAU frames • Adaptation (e. AMR FR<->AMR HR<->DHR) to maintain quality & coverage For internal use 8 © Nokia Siemens Networks Presentation / Author / Date .1) Q(B) (1.0) (1.

0) • For SAIC-capable MS (penetration 30-40%) For internal use 9 © Nokia Siemens Networks Presentation / Author / Date .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 User-A TRX MUMIMO Receiver User-B MU-MIMO Deciphering Deciphering Decoding Decoding RG20 Abis Some limitations • For Flexi EDGE BTS (SW:EX4.

Impact on KPIs • • • If frequencies can be removed => better quality In refarming – same 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 Max 4 calls per RTSL => is effecting on capacity planning heavily Good solution in refarming case Is effecting on abis capacity – see next slides Important feature in refarming case – GSM capacity can be handled with this feature Capacity strategy can be based on this feature 3. Dimensioning 4.Orthogonal Sub-channel – Double Half Rate Impact on Planning 1. Other For internal use 10 © Nokia Siemens Networks Presentation / Author / Date .

Orthogonal Sub-channel OSC Half Rate with SAIC MS (BSS21309) Circuit Switched Dynamic Abis Pool (BSS30385) For internal use 11 © Nokia Siemens Networks Presentation / Author / Date .

time slot as these calls are distinguished by different TSC): ▪ OSC-0 channels always use PCM resources reserved for TCH ▪ OSC-1 channels always use PCM resources reserved in CSDAP FR MS1 FR HR MS1 MS2 HR HR OSC DHR MS1 MS3 OSC-0 OSC-0 MS4 MS2 OSC-1 OSC-1 HR (time) multiplexing OSC multiplexing For internal use 12 © Nokia Siemens Networks Presentation / Author / Date HR (time) multiplexing .e.Orthogonal Sub-channel Circuit Switched Dynamic Abis Pool Introduction • For OSC DHR mode more Abis transmission is needed for radio timeslot because two calls are multiplexed in one HR channel – a single RTSL carrying FR cal is mapped to a 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.

Counters / parameters New parameters(9) / counter (4) are introduced OSC RX Quality Measurements: counters (122000-122079) 3. Impact on KPIs • • • Abis/PCU blocking should be monitored. CSDAP is reducing “normal” EDAP capacity 2. Dimensioning • Abis / PCU capacity must be monitored carefully 4.Orthogonal Sub-channel Circuit Switched Dynamic Abis Pool Impact on Planning 1. Other • Requirements: Circuit Switched Dynamic Abis Pool (BSS30385) or packet Abis configured For internal use 13 © Nokia Siemens Networks Presentation / Author / Date .

Local Switching for Packet Abis BSS21327 For internal use 14 © Nokia Siemens Networks Presentation / Author / Date .

e. in RG20 there 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. no bandwidth is wasted due to granularity.Introduction Packet Abis overview • Packet Abis means introduction of a new transport concept: – Abis frames conveying traffic and signaling information between BTS and BSC are subject to packetization process prior to sending them to the transmission path – as a result of packetization the incoming TRAU/PCU/LAPD frames are converted to new (Packet Abis specific) formats which are encapsulated and form IP packets eventually transmitted over Abis – these principles are valid regardless of physical media used in transport network. header information of TRAU/PCU frames) or even the entire frames (e. no “empty” packets are transmitted) For internal use 15 © Nokia Siemens Networks Presentation / Author / Date . idle frames) – silence suppression – statistical multiplexing due to unbalanced sectors‟ load and reuse of common bandwidth by different types of traffic (trunking gain) – efficient usage of bandwidth which is allocated according to the actual needs (i.g.g.

is valid for speech data only => signalling data would be transferred ‟traditionally‟ to allow using existing features • Local switching does not apply to PS calls as well because normally a PS call is established ‟non-locally‟ between MS and a server (GGSN) and not between two MSs Abis MS2 Speech Signalling Abis capacity is saved For internal use MS1 © Nokia BTS 1 BSC1 16 Siemens Networks E1/T1 TRAU 1 MSC1 Presentation / Author / Date MSC2 TRAU2 BSC2 BTS2 . trans-coders and a core network Speech and signalling Abis Calls and related signalling are transferred through all network entities MS2 MS1 BTS1 E1/T1 BSC1 TRAU1 MSC1 MSC2 TRAU2 BSC2 BTS2 • Such the concept.e. i. BTSs.Local Switching for Packet Abis Introduction • Normally. known as local switching. BSCs. MS-to-MS calls are always transferred through all network elements of the GERAN network.

Dimensioning • Abis traffic due to voice will be reduced => abis dimensioning 4. Counters / parameters New parameters (4) / counters(15) are introduced 3. 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. Other For internal use 17 © Nokia Siemens Networks Presentation / Author / Date .Local Switching for Packet Abis Impact on Planning 1.

CCCH improvements in BSS BSS20738 CS Paging Coordination in NMO II BSS21538 Extended CCCH BSS101411 Extended BCCH For internal use 18 © Nokia Siemens Networks Presentation / Author / Date .

TLLI. IMSI database) when it receives info that active TBF for that MS exists.e. • CS Paging Coordination in NMO II means that MS in Packet Transfer Mode can be paged for CS connection with Packet Paging Request messages sent on PACCH • CS paging can be received via Gs-i/f or A-i/f (if no Gs-i/f between MSC and SGSN) • CS Paging makes MS to abort PS session before CS connection setup • BSC creates a record for MS (with IMSI. Segment ID and PCU address) into a hash table (i.CS Paging Coordination in NMO II Feature details • Currently BSC3i provides CS paging co-ordination only in NMO I regardless of the DTM feature state (enabled/disabled). For internal use 19 © Nokia Siemens Networks Presentation / Author / Date .

Impact on KPIs • Paging KPIs possible improved • Depending for example usage of PS services New parameters (1) /counters(2) are introduced Not affecting 2. 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 Transfer Mode. Dimensioning 4.CS Paging Coordination in NMO II Impact on Planning 1. Counters / parameters • • 3. Without this feature and w/o Gs interface MS in Packet Transfer Mode is unreachable what increase customer dissatisfaction (specially when automatic SMS is sent informing subscriber about unsuccessful incoming call) For internal use 20 © Nokia Siemens Networks Presentation / Author / Date .

CCCH improvements in BSS BSS20738 CS Paging Coordination in NMO II BSS21538 Extended CCCH BSS101411 Extended BCCH For internal use 21 © Nokia Siemens Networks Presentation / Author / Date .

Extended CCCH
Feature details
• 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, where BCCH channel number 0 is configured with 9 uncombined CCCH blocks.

• Extended CCCH channel contains 1 BCCH block and 9 uncombined CCCH
blocks (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.

For internal use 22 © Nokia Siemens Networks

Presentation / Author / Date

Extended CCCH
Impact on Planning

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 New parameters(3) are introduced No new counters are introduced

2. Counters / parameters
• • • •

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
For internal use 23 © Nokia Siemens Networks Presentation / Author / Date

CCCH improvements in BSS
BSS20738 CS Paging Coordination in NMO II BSS21538 Extended CCCH BSS101411 Extended BCCH

For internal use 24 © Nokia Siemens Networks

Presentation / Author / Date

can be reduced by moving SI 2 quater message sending to an extended BCCH sub channel in BCCH TRX. Information element L2 Pseudo Length RR management Protocol Discriminator Skip Indicator SI Type 2quater Message Type SI 2 quater Rest Octets Presentation / Author / Date Presence Format Length Mandatory Variable 1 Mandatory Variable 1/2 For internal use 25 © Nokia Siemens Networks Mandatory Variable Mandatory Variable Mandatory Variable 1/2 1 20 . it means more time for HO and Update • Typically System Information messages are scheduled over the BCCH channel of the BCCH frequency on the timeslot 0. • With Extended BCCH feature the time which is required for System Information (SI) update to mobile.Extended BCCH Feature details • This feature was requested by CMCC where TD-SCDMA is deployed as the mechanism to speed up cell reseletion and HO to 3G • With coexistance of GSM and TD-SCDMA. too long SI need more individual SI messages and UE need more time to read them. Unfortunately. there are more and more SI on GSM side.

This reduces CCCH capacity 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) For internal use 26 © Nokia Siemens Networks Presentation / Author / Date .Extended BCCH Feature details  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).

Paging capacity must be monitored 4. Impact on KPIs • • speed up cell reseletion and HO to 3G => Cell reselection and HO KPIs might be improved Reduce CCCH capacity 2. Dimensioning • • Depends on the 2G / 3G capacity strategy Easier to put traffic to 3G => affecting on dimensiong • Reduce CCCH capacity. Other For internal use 27 © Nokia Siemens Networks Presentation / Author / Date .Extended BCCH Impact on Planning 1. Counters / parameters • • New parameters (1) are introduced No new counters are introduced 3.

& E-GSM900 For internal use 28 © Nokia Siemens Networks Presentation / Author / Date .BSS21238 Merged P.

915 MHz E-GSM Presentation / Author / Date 925 .960 MHz For internal use 29 © Nokia Siemens Networks E-GSM .Merged P. – The purpose to separate these 2 different band was ▪ to avoid problems with PGSM-only terminals and to assure that PGSM-only terminals are 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.& E-GSM900 Introduction • 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. even BCCH is on other band – BSC allows both PGSM900 and EGSM900 frequencies in an MA or DFCA MA list E-GSM P-GSM E-GSM P-GSM 880 .890 890 .935 935 .

Counters / parameters No new counters / parameters 3. Dimensioning Not affecting 4. 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.& E-GSM900 Impact on Planning 1. Other For internal use 30 © Nokia Siemens Networks Presentation / Author / Date .Merged P.

LTE System Information and NACC improvements LTE 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) For internal use 31 © Nokia Siemens Networks Presentation / Author / Date .

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 the Core Network translates the VoIP Call across as an incoming CS Handover for GSM PS HO LTE active 2G PS DTM 2G CS LTE idle CS&RS 2G idle For internal use 32 © Nokia Siemens Networks Presentation / Author / Date .where Voice Services / Emergency Calls are directed from LTE to GSM (via NACC) – Single Radio Voice Call Continuity (SRVCC) .

CPICH RSCP of the 3G cell ≥ FDD_RSCP_threshold .Only minimum signal strength criteria of the neighbouring cells are considered for higher priority cells (and also minimum quality criteria in case of 3G cell) For internal use 33 © Nokia Siemens Networks Presentation / Author / Date .gsmPriority. wcdmaPriority.CPICH RSCP of the 3G cell > RLA_C of the serving (GSM) cell + FDD_Qoffset . lteAdjCellPriority .LTE System Information 2G → 3G cell reselection:  Old Case: Suitable 3G cell is selected if for the period of 5 sec all the conditions are met: .For serving and all measured neighbouring GSM cells during T_reselection (timeHysteresis): .There is no measured non serving cell with higher priority inter-RAT frequency for which conditions related to Case 1 (see previous slide) are satisfied AND .CPICH Ec/No of the 3G cell ≥ FDD_Qmin – FDD_Qmin_Offset .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 .

is affecting on dimensioning 4. Counters / parameters New parameters (24) are introduced No new counters 3. Other For internal use 34 © Nokia Siemens Networks Presentation / Author / Date .LTE System Information Impact on Planning 1. Impact on KPIs • • • • • Idle mode mobility to LTE => Better 2G / LTE traffic handling These are affecting on basic KPIs 2. Dimensioning Better 2G /3G/LTE interworking.

LTE System Information and NACC improvements LTE 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) For internal use 35 © Nokia Siemens Networks Presentation / Author / Date .

RG20 (BSS) Introduction NACC Improvements – Feature details • The aim of the Network Assisted Cell Change (NACC) feature is to provide with certain target cell system information already on the source cell in order to reduce the service outage time during the reselection process.5 NACC 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 For internal use 36 © Nokia Siemens Networks Presentation / Author / Date . • Three features are introduced in RG20 for improving BSS11.

Impact on KPIs • • More NACCs. data services will be improved reduction of service outage time during reselection process. Other For internal use 37 © Nokia Siemens Networks Presentation / Author / Date . Counters / parameters • New parameters(3) / counters(5) are introduced 3.NACC Improvements Impact on Planning 1. Dimensioning • 2G / LTE interworking => affect on PS capacity planning 4. • Throughput and delay KPIs will be improved 2.

Downlink Dual Carrier (DLDC) RG10:BSS21228 DLDC. RG20:BSS21343: DLDC-aware EGPRS territory management RG20:BSS21392: TRX-specific Link Adaptation for DLDC For internal use 38 © Nokia Siemens Networks Presentation / Author / Date .

Downlink Dual Carrier Introduction Up to BSS13 Single carrier allocations in Downlink and Uplink  Up to 5 TSLs in DL . 7 MS) For internal use 39 © Nokia Siemens Networks Presentation / Author / Date c2 .max MS Multislot Class capability supported by PCU2 (Class 40-45)  Up to 296 kbps (5TSLs @ MCS9) of theoretical peak LLC data throughput RG10 c1 c1 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 theoretical peak LLC data throughput  Using two carriers requires new 2-receiver terminals (3GPP Rel.

Downlink Dual Carrier Introduction 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 2nd TRX if there is any DLDC capable MS having on 1 TRX only – PCU2 calculates the amount of needed TSLs and requests the territory 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 For internal use 40 © Nokia Siemens Networks Presentation / Author / Date .

Downlink Dual Carrier Affecting on Network Planning CS and PS peak values at the same time => bad for PS timeslot allocation => lots of downgrading For internal use 41 © Nokia Siemens Networks Presentation / Author / Date .

Downlink Dual Carrier Impact on Planning 1. Dimensioning More timeslots for PS => EDAP dimensioning 4. Counters / parameters • • New parameters(6) / counters(16) are introduced 3. Impact on KPIs • See next slide 2. Other For internal use 42 © Nokia Siemens Networks Presentation / Author / Date .

Downlink Dual Carrier Impact on KPIs 1. Handovers • • If more TRX due to data services => interference level will be increased HO failure will be increased 3. default area can not be used • PS Blocking => no fully advantage 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 Presentation / Author / Date • • • • For internal use 43 © Nokia Siemens Networks . Blocking 5. Quality • If TRX‟s 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. • More RTSLs for data must be available to get full advantage • CS Blocking => no TSLs for data services. Drops • If more TRX due to data services => interference level will be increased • Drops will be increased 4.

End of the presentation More features in Annex (See next slides) For internal use 44 © Nokia Siemens Networks Presentation / Author / Date .

Annex Some more features to be introduced For internal use 45 © Nokia Siemens Networks Presentation / Author / Date .

Packet Abis Synchronisation BSS21439 & BSS30450 For internal use 46 © Nokia Siemens Networks Presentation / Author / Date .

Frequency Stability For internal use 47 © Nokia Siemens Networks Presentation / Author / Date .Packet Abis Synchronisation Frequency Accuracy vs.

e. it makes use of a physical layer interface to pass timing from a master to a slave In BSS15 the synchronisation methods are employed to ensure the required frequency accuracy (precisely: syntonisation) at a base station only.Packet Abis Synchronisation Feature details • 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. i. frequency accuracy 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 traffic between a master clock and a slave clock => then the slave clock is able to regenerate a clock frequency according to a received bit stream – Synchronous Ethernet (SyncE) ▪ Synchronous Ethernet (SyncE) is a physical layer synchronisation method. time synchronisation is NOT required For internal use 48 © Nokia Siemens Networks Presentation / Author / Date .

Counters / parameters • New parameters are introduced 3. Dimensioning • Not affecting 4.Packet Abis Synchronisation Impact on Planning 1. Impact on KPIs • Possible less Abis synchronization problems • Less overflows or underflows of synchronisation buffers • Less errors in incoming bit stream 2. Other For internal use 49 © Nokia Siemens Networks Presentation / Author / Date .

Flexi BTS Autoconnection BSS21316 For internal use 50 © Nokia Siemens Networks Presentation / Author / Date .

– BTS installation times will be reduced For internal use 51 © Nokia Siemens Networks Presentation / Author / Date .Flexi BTS Autoconnection • 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 dedicated SCF file either fully automatically or in case of errors with remote admission control – BTS commissions are easier to perform.

Flexi BTS Autoconnection Impact on Planning 1. Counters / parameters 3. Other • • Fewer issues during roll-outs => time savings Quicker BTS installing time => time savings For internal use 52 © Nokia Siemens Networks Presentation / Author / Date . Impact on KPIs • • • Not affecting No New parameters / counters are introduced When feature powered on. Dimensioning • OMUSIG capacity must be enough in every PCM 4. BTS starts to scan all available interfaces in searching for OMUSIG candidates 2.

Automatic EDAP reallocation in PCU incl. PCU restart handling BSS21232 & BSS20045 For internal use 53 © Nokia Siemens Networks Presentation / Author / Date .

then the BCSU switchover is triggered – two types of PCU restart are possible ▪ PCU Hot restart – restart of dynamic Abis configuration in PCU ▪ PCU Cold restart – restarts whole PCU For internal use 54 © Nokia Siemens Networks Presentation / Author / Date .PCU restart handling Introduction • Before RG20 – if SW or HW fails in a PCU unit  BCSU 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 be restarted 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.

modification or PCU pool reallocation. deleted or moved to another PCU a BSC searches free space in PCUPCM for EDAP in question only and all other EDAPs remains in their original places – this might cause PCUPCM fragmentation => EDAP creation. instead of BCSU restart/ switchover which was recommended in earlier releases. i.Automatic EDAP reallocation in PCU General feature information • Up to now (RG10) – in the present BSC implementation EDAPs are completely rearranged in PCUPCMs only when the initial EDAP configuration is done. 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 BCSU and interruptions of PS data transmissions in every PCU in the BCSU – when EDAP is modified.e. PCU restart is enough to apply the changes in EDAP configuration For internal use 55 © Nokia Siemens Networks Presentation / Author / Date . added. PS territory upgrade may be very limited or even cannot be performed • In RG20 – Automatic EDAP reallocation in PCU feature removes the problem of the PCUPCM fragmentation in BSC – add-on in comparison to RG10 is that after any EDAP modification.

Other For internal use 56 © Nokia Siemens Networks Presentation / Author / Date . Counters / parameters • • • PCU restart handling => new parameters No new counters 3. Impact on KPIs • CS calls are not disturbed when EDAP operations are done => DCR will be improved when EDAp operations will be done 2. PCU restart handling Impact on Planning 1.Automatic EDAP reallocation in PCU incl. Dimensioning Not affecting 4.

RG20 (BSS) Network Engineering Information A over IP BSS21341 For internal use 57 © Nokia Siemens Networks Presentation / Author / Date .

AoIP feature can be realized in RG20 in two ways: – AoIP with Transcoding in BSS – AoIP with Transcoding in MGW Presentation / Author / Date For internal use 58 © Nokia Siemens Networks . synchronization chain is broken and new methods are required for generation and distribution of synchronization signal in GERAN.Introduction AoIP overview • 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 IP packets and transmitted every 20ms over Ethernet based A interface – There is no multiplexing in AoIP – each 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.

Impact on KPIs • • Speech quality (MOS) will be improved with TrFO New types of Internal Handovers are introduced with AoIP feature (BSS_int_HO.A over IP Impact on Planning 1. Dimensioning can be done with dimensioning tool SS7 calculator to estimate SIGTRAN bandwidth 4. Other Connectivity between NEs is most cost effective with usage of IP technology For internal use 59 © Nokia Siemens Networks Presentation / Author / Date . Dimensioning Affecting on number of Ater and A PCMs. Counters / parameters • • • • New parameters / counters are introduced 3. see also counters 4240…4250) 2.

PWE3) BSS21271 For internal use 60 © Nokia Siemens Networks Presentation / Author / Date .Abis Delay Measurement (TDM.

Abis Delay Measurement (TDM. DAP or TCH • This measurement channel is looped back in the BSC back to the BTS – the BTS is responsible for measuring time interval (Round Trip Time) between sending and receiving bit pattern Internal Delay Round Trip Time Network Delay Internal Delay BTS Network interface Network interface Measurement entity BSC GSWB (*1) 101101101 101101101 Measurement channel Measurement manager OMUSIG Measurement manager For internal use 61 © Nokia Siemens Networks Presentation / Author / Date NetAct . PWE3) Íntroduction • 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.

Other Abis KPIs – better way to monitore abis TDM and PWE3 backhaul lines New measuremenst have been implemented • 120 – TDM/PW Abis Delay Measurement For internal use 62 © Nokia Siemens Networks Presentation / Author / Date . Dimensioning Not affecting 4. Impact on KPIs • Abis KPIs might be improved 2. PWE3) Impact on Planning 1.Abis Delay Measurement (TDM. Counters / parameters • • • • New counters are introduced 3.