769

RANPAR 1

Embed Size (px)

Citation preview

Page 1: RANPAR 1
Page 2: RANPAR 1
Page 3: RANPAR 1
Page 4: RANPAR 1
Page 5: RANPAR 1
Page 6: RANPAR 1
Page 7: RANPAR 1
Page 8: RANPAR 1
Page 9: RANPAR 1
Page 10: RANPAR 1

WCDMA system is said to be interference limited. All cells and users are transmittingon the same frequency and information from individual users is retrieved by coding.The level of interference governs the likelihood of recovering the wanted signal.Minimising the levels of unwanted interference in both the forward and reverse linksimpacts link quality, cell capacity and cell coverage areas. Nokias RRM is responsiblefor using the air interface resources optimally and hence maximising cell capacity,cell coverage and ultimately the user link quality for each service.

Page 11: RANPAR 1

Real time non-controllable load has priority over NRT as QOS attributes for RT RABare more stringent.

Page 12: RANPAR 1

Two areas in the functional split Cell based functions apply to all the current or evenpotential connections to a single cell, say of a 3 sector site.Connection based functions apply to every UE currently connected to the cell

Page 13: RANPAR 1
Page 14: RANPAR 1
Page 15: RANPAR 1

Preventative load control aims to avoid getting the node B in an overload condition (iewhen it runs out of downlink power (Ptx) or where the UL interference is too high(Prx)) and maintain the optimal cell load by blocking new RT RAB admissions andstopping the Packet schduler scheduling anymore NRT bit ratesOverload control acts quickly to reduce the NRT load if preventative load control isunsuccessful. New RT users are not admistted and existing NRT user bit rates aredown-graded.Note that the load status is effectively the Prx Total in the reverse link and the PtxTotal in the forward link.The message Radio Resource Indication is sent from the node B to the RNC every200ms (or RRI period) to advise of the levels of Ptx Total and Prx total (ie load status)in each cell

Page 16: RANPAR 1
Page 17: RANPAR 1

Eb/No is simply energy per bit divided by noise spectral density. It is a performanceindicator always associated with a target BLERNote that the RNC contains a look up table for EbNo values required per service.EbNo is related to the SIRBER--->BLER---->Eb/No---->SIR derivation used in PCTransmission mode is either TM (Transparent Mode no protocol overhead added tohigher layers), UM (Unacknowledged mode, delivery not guarenteed) or AM(Acknowledged mode, delivery guarenteed).TFS is Transport Format Set in basic terms is the mapping of RAB bearer rate (0, 16,32, 64, 128) to signalling channel rate TFS - set of TFs associated to a TrCH.

Page 18: RANPAR 1

Note that Prx Total is a measured dynamic value by the node B whereas Prx_targetis a thresholds set by Radio Network Planning parameters. Prx_target_BS is acalculated threshold including some offsets.

PrxTotal is the total received interference in the Reverse Link.

Page 19: RANPAR 1

Relevance of lower load threshold:No power-based AC if Load is below lower thresholdNo admission, if overall DCH Load is above upper threshold

Page 20: RANPAR 1
Page 21: RANPAR 1

PS works in conjunction with AC and LC (error on slide)UE specifc part manages traffic volume measurement for each UECell specifc part that controls the cell load

Page 22: RANPAR 1

Performance gain comes from features in oval

Page 23: RANPAR 1
Page 24: RANPAR 1
Page 25: RANPAR 1
Page 26: RANPAR 1

Soft handover ‘make before break’Hard handover ‘break before make’ (as in GSM/TDMA)Intra-system handovers are either soft(er) or hard. Hard handovers can be inter-frequency (ie between carriers) or intra-freqency…..e.g across an RNC boundaries ifthe Iur wasn’t in place.Inter-system inter-RAT handovers are always hard

Page 27: RANPAR 1
Page 28: RANPAR 1

Resource manager looks after node B H/W resources.

Orthogonal codes are all synchronised, hence interference from other users in thecell is minimised.

Note that User data is first spread using a spreading (chanelisation) code and thenscrambled using a scrambling code. In the downlink the scrambling code identifiesthe cell whereas in the uplink the scrambling code is call specific.

Code de-fragmentation takes place to ensure that the channelisation code tree isbeing used efficiently to ensure maximum use of the available codes.

Page 29: RANPAR 1
Page 30: RANPAR 1
Page 31: RANPAR 1

Performance gain comes from features in oval

Page 32: RANPAR 1
Page 33: RANPAR 1
Page 34: RANPAR 1
Page 35: RANPAR 1

For all managed objects, G refers to GSM, I refers to inter-frequency (ie betweencarriers of the same system) and S refers to same carrier, same system (or ‘Soft’),red/dashed boxes indicate relationship to optional features.Functions are as follows:-RNC……Radio Network ControllerWBTS…..WCDMA Base StationWCEL…..cell of WBTSFMC……Frequency Measurement Control. Contains information concerning thefrequency measurement functionality of the RNCADJ……Adjacency for WCDMA Cell. Contains information concerning theneighbouring cells of a particular WCDMA CellHOP…..Handover Path. Stores values used in handover. Note that one HOP can berelated to several Adjacency objectsCOCO….Radio Network Connection Configuration (transmission parameters etc).WANE …. WCDMA Authorized NEtworkWSG …. WCDMA subscriber groupCMOB …. Congestion Management ObjectWLCSE …. WCDMA Location Services EntityWSMLC …. WCDMA Serving Mobile Location Center

Dashed boxes are related to optional features.

Page 36: RANPAR 1
Page 37: RANPAR 1
Page 38: RANPAR 1

Interfaces Iur soft-handover interfaces between RNCsIu-PS, Iu-CS link RNC to core network

Page 39: RANPAR 1
Page 40: RANPAR 1
Page 41: RANPAR 1
Page 42: RANPAR 1
Page 43: RANPAR 1
Page 44: RANPAR 1
Page 45: RANPAR 1
Page 46: RANPAR 1
Page 47: RANPAR 1
Page 48: RANPAR 1
Page 49: RANPAR 1
Page 50: RANPAR 1
Page 51: RANPAR 1
Page 52: RANPAR 1
Page 53: RANPAR 1
Page 54: RANPAR 1
Page 55: RANPAR 1
Page 56: RANPAR 1
Page 57: RANPAR 1
Page 58: RANPAR 1

Does not perform PS in DRNC -> send to SRNC for PS decisionDifferent FMCS can be configured for HSDPA and HSDPA+HSUPA caseADJD excluded for

Page 59: RANPAR 1
Page 60: RANPAR 1
Page 61: RANPAR 1
Page 62: RANPAR 1
Page 63: RANPAR 1
Page 64: RANPAR 1
Page 65: RANPAR 1
Page 66: RANPAR 1
Page 67: RANPAR 1
Page 68: RANPAR 1
Page 69: RANPAR 1
Page 70: RANPAR 1
Page 71: RANPAR 1
Page 72: RANPAR 1

In GSM, we distinguish between logical and physicalchannels. In UMTS there are three different types ofchannels:•Logical ChannelsLogical Channels were created to transmit a specificcontent. There are for instance logical channel to transmitthe cell system information, paging information, or user data.Logical channels are offered as data transfer service by theMedium Access Control (MAC) layer to the next higher layer.Consequently, logical channels are in use between themobile phone and the RNC.•Transport Channels (TrCH)The MAC layer is using the transport service of the lowerlower, the Physical layer. The MAC layer is responsible toorganise the logical channel data on transport channels.This process is called mapping. In this context, the MAClayer is also responsible to determine the used transportformat. The transport of logical channel data takes placebetween the UE and the RNC.•Physical Channels (PhyCH)The physical layer offers the transport of data to the higherlayer. The characteristics of the physical transport have to bedescribed. When we transmit information between the RNCand the UE, the physical medium is changing. Between theRNC and the Node B, where we talk about the interface Iub,

Page 73: RANPAR 1
Page 74: RANPAR 1
Page 75: RANPAR 1
Page 76: RANPAR 1
Page 77: RANPAR 1

In GSM all common channels have the same power – in WCDMA each channel canhave it’s own power setting!In GSM there is no need to consider the power setting of common channels as allcommon channels are on full power. In GSM we have to decide how many TSLs todedicate to common tasks, I.e. how many SDCCH TSL are required per cell.Although not all common channels transmit at the same time, we have to considerhow much power is used for each common channel.

Page 78: RANPAR 1

We have to ensure that all common channel have the same coverage.

Page 79: RANPAR 1
Page 80: RANPAR 1

The setting of the pilot cannot be done on an isolated orindividual manner since the dominance area for a given cellis a result of the setting of PtxPrimaryCPICH in the adjacentcells. It is possible to set different PtxPrimaryCPICH forvarious cells to adjust the dominance areas. However, thereis a penalty on this in terms of interference since the cellselection will be based on the difference in thePtxPrimaryCPICH.

CPICH power is used for the initial DL power allocation alsofor the UL power calculations of pathloss.CPICH reference to RAB that has to be a realistic simulationbased value which should correspond to the availability ofthe service in accordance to the realistic service availability.

Page 81: RANPAR 1

The setting of the pilot cannot be done on an isolated orindividual manner since the dominance area for a given cellis a result of the setting of PtxPrimaryCPICH in the adjacentcells. It is possible to set different PtxPrimaryCPICH forvarious cells to adjust the dominance areas. However, thereis a penalty on this in terms of interference since the cellselection will be based on the difference in thePtxPrimaryCPICH.

CPICH power is used for the initial DL power allocation alsofor the UL power calculations of pathloss.CPICH reference to RAB that has to be a realistic simulationbased value which should correspond to the availability ofthe service in accordance to the realistic service availability.

Page 82: RANPAR 1

This is only to indicate that increasing the powers can eliminate the CPICH coverageholes. But there are limitations in this approach as well:Power is limited. Any increase in CPICH will lead to reduction in (DCH) capacity.Antenna tilting might be more suitable. By reducing interference Ec/Io can beimproved without need to power increase.

Page 83: RANPAR 1

The worst-case scenario is when a terminal sees three strong pilots,which means the other cell interference factor is 2 (i.e. two otherpilots). For typical values, we have EbNo of 6.5 (raw value), and Gpilot= 240 and PtxTarget+PtxOffset = 20 W, then the PtxPrimaryCPICHbecomes 1.2 W, or for PtxTarget + PtxOffset of 15 W, thePtxPrimaryCPICH is 0.95 W. So we can say that a pilot power around1-2 W is just sufficient to ensure that the pilot is visible even at highloads. The value of 2W should tolearate even cases where the othercell interference factor exceeds 3 dB for a loaded cell.

It should be noted that the pilots signal strength always exceeds thesystem noise in the downlink. Therefore this serves as the referencenoise for the downlink bearers. Thus high values are not desirable interms of capacity.

Page 84: RANPAR 1
Page 85: RANPAR 1

Late Cell reselection – calls will hand out too late!Increased SHO overhead – the cell will be in the AS of too many UEs

Page 86: RANPAR 1

Primary sync channel: always the same 256 chipsSecondary sync channel: 64 sets of 256 code chipsOpt 4 UMTS: page 44

Page 87: RANPAR 1

15ksps=SF256The performance in SHO and softer, in cell DCH mode should be tested since the UEmust be able to read the SFN so that the active set update is possible.The decoding of the Primary CCPCH allows:

decoding of the BCH in the synchronization procedure allows to read thePLMN id and compare it with the ones provided by the NASdecoding of the BCH in the neighbour cell allows to check the cell iddecoding of the BCH in the handover procedure (where SCH1 and SCH2 arenot used) allows to check the cell id

Page 88: RANPAR 1

Transmits only when data availableSimilar to Paging and Access Grant channel in GSM – possible to go for “combined”or “non-combined”

Page 89: RANPAR 1
Page 90: RANPAR 1
Page 91: RANPAR 1

Same as in 2G the larger the LAC the more paging traffic > the more capacity in PCHis required (combined BCCH or non-combined BCCH)

FACH transports data to UE in known cell – will increasing LA reduce FACHtraffic???

Page 92: RANPAR 1

TFCI = Transport Format Combination Indicator used to indicateif multiple transport formats are used (data from 2 services)(Laiho page 43)

Page 93: RANPAR 1

The spreading factor is 256 leading to a data rate of about 3 kbps

This is just an indicator – not the real paging information (paging information iscarried on the S-CCPCH

Page 94: RANPAR 1

See Excel sheet for example!Laiho page 47 and page 156

Page 95: RANPAR 1

Laiho page 46

A test can be performed in the same measurement locations with RACH, and alsothe optimisation can be done together.

Before the optimisation it should be ensured that CPICH and P-CCPCH can bereceived sufficiently in the measurement locations. Also the RACH parametersshould be set such that RACH is working for sure, but also to the optimal values fromthe RACH optimisation case.

Each parameter setting should be tested in several known locations on ameasurement route (always at the same locations). At least one measurementlocation close to the BS (line-of-sight) is needed and one measurement location atnetwork edge (so that it is known to which cell the UE tries to access).

Perform the test with the values PtxAICH = -5dB, -8dB, -11dB, -14dB and -17dB,with at least 2 feasible parameter value combinations for PRACH, i.e. a conservativeand the optimal setting found from the PRACH optimisation case. =>value number ofmeasurement locations times 5 values for PtxAICH times 2 PRACH parameter sets.Start a MO speech call

Log the CPICH Ec/No (and RSCP) as measured by UE, AICH as read by UEand the total received and transmitted power of BS.Measure the time consumed in the random access procedure up to thecorrect reception of AI.The information from UE and BS should be synchronized and layed onto themeasurement routes on the map.

Page 96: RANPAR 1
Page 97: RANPAR 1
Page 98: RANPAR 1

With HSUPA the principles remain the sameOpen loop remains exactly the sameHSUPA closed loop follows DPCCHHSUPA outer loop has some changes in detail of algorithm operation

Page 99: RANPAR 1

In GSM the initial access is done on full power and if not successful repeated (on fullpower) after a short delay. In WCDMA the initial access it at low power, and it notsuccessful the power is increased (timing is not changed).

Page 100: RANPAR 1

Using these parameters also affects the initial power on DPCCH.

Page 101: RANPAR 1

SIB 7 is repeated very frequently to provide accurate info on level of IF at BTS UL.

Page 102: RANPAR 1
Page 103: RANPAR 1
Page 104: RANPAR 1
Page 105: RANPAR 1
Page 106: RANPAR 1
Page 107: RANPAR 1
Page 108: RANPAR 1
Page 109: RANPAR 1
Page 110: RANPAR 1

To combat the deep fades in the fading channel, it is required to transmit with higherpower > thus transmit power rise.

Page 111: RANPAR 1
Page 112: RANPAR 1

If one were to consider the target SIR for the worst case, i.e. for high speed mobile, one wouldwaste capacity for all the other connection at low speed.The higher the variation in received power, the higher the SIR target needs to beEnvironment dependent 10 – 100 Hz

CRC okay then SIR is lowered – CRC not okay then SIR is increased

Same to EDGE: depending on the data rate a different C/I is required – the C/I has tobe adjusted to provide the throughput

Page 113: RANPAR 1

If one were to consider the target SIR for the worst case, i.e. for high speed mobile, one wouldwaste capacity for all the other connection at low speed.The higher the variation in received power, the higher the SIR target needs to beEnvironment dependent 10 – 100 Hz

CRC okay then SIR is lowered – CRC not okay then SIR is increased

Same to EDGE: depending on the data rate a different C/I is required – the C/I has tobe adjusted to provide the throughput

Page 114: RANPAR 1

One entity for each transport channel

Page 115: RANPAR 1
Page 116: RANPAR 1
Page 117: RANPAR 1

1 At the RAB set-up the BTS gets the initial value of SIR target from AC.

2 This piece of information, together with the bearer specific PC parameters for each DCH(e.g. BLER (block error rate) target for low quality bearers; BER target for high quality bearers; minimumand maximum values for SIR target; activity reporting period; minimum and maximum step-size for SIRtarget modifications, Entity selected to be active), is given also to the uplink Outer Loop Power Control(UL OLPC) Controller.

3-4 The UL OLPC Controller sets up the UL OLPC Entities and gives the needed parameters, including:

Parameters received from AC: BLER target or BER target; Entity selected to be active; activityreporting period; minimum and maximum step-size for SIR target modifications.

Parameters determined by the Controller: actual step-size for SIR target modifications; activitystate.

Set-up is done also in case of RAB modification.

The PC Entity of the first RAB of a RL is selected to transmit the new SIR target value tothe BTS (MDC).

5 At this point in time the connection is up and the PC Entities receive quality estimatesfrom the MDC. The quality information is obtained after combining the SHO branches. Depending on thetype of RAB, PC Entity gets either BLER estimation result calculated according to the CRC bits of theselected frame and/or BER estimation result calculated in the BTS. In case any CRC check is not ok, theMDC selects the best one of the BER estimations.

6 The PC Entities are now able to calculate the change of SIR target.

7 Only one of the PC Entities set-up for the same RL (the one in active state) sends theresult to the Controller using the SIR target modification command.

In fact the PC Entities can have four activity states:

Active: the entity transmits the modification command.

Semi-active: for very high quality bearers (BLER very low); it can transmit only SIR target upcommand.

Inactive: it doesn't transmit the message or it transmits zero.

Overload: it is not allowed to increase the SIR target (not used in RAN1).

At RAB set-up, AC informs the Controller which Entity is first selected to be active (theone corresponding to the bearer with the highest initial SIR target). During the connection, the Controller

Page 118: RANPAR 1

UL outer loop PC entity receives the UL quality informationfrom the MDC. The quality information is made aftercombining the SHO branches. Depending on the type of theRadio Bearer, PC entity gets either BLER estimation resultcalculated according to CRC-bits of the selected frameand/or BER estimation result calculated in the WCDMA BTSIn case any CRC-check is not OK, the MDC selects the bestone of the BER estimations.

All hidden parametersIn case of AMR (TTI = 20 msec) the BLER estimation is yesno. For 384 with 240 TTI the estimation is 1/12 in granularityas 1/12 can be wrongBLER_target is set by hidden parameters tables in RNCwhich are influenced by SDU table from HLRStep size is 0.5 dBReduction is 0.01 * step sizeIncrease is 0.99 * step size

The transport channel BER is an estimate of the average bit

Page 119: RANPAR 1
Page 120: RANPAR 1

The quality deterioration report from the UL outer PCcontroller may initiate a bearer reconfiguration procedure; orif the serving cell (or cells participating in soft handover) hasneighboring cells in another carrier frequency or system, theRNC may tell the mobile station to start inter-frequency/system measurements when it receives thequality deterioration report from the UL outer loop PCcontroller.

Page 121: RANPAR 1
Page 122: RANPAR 1
Page 123: RANPAR 1
Page 124: RANPAR 1
Page 125: RANPAR 1
Page 126: RANPAR 1
Page 127: RANPAR 1
Page 128: RANPAR 1
Page 129: RANPAR 1
Page 130: RANPAR 1

WBTS: Cell Id is given in Measurement ReportNB/RS: A Measurement ID is given in Measurement Report, which is mapped to CellID at (Re-)Start

Page 131: RANPAR 1
Page 132: RANPAR 1
Page 133: RANPAR 1

There also exists another definition of etaDL=1-1/power rise over common channels.

Page 134: RANPAR 1

Slide shows load estimation methods. 3 curves show the relationship betweenwideband power level and cell loading. ‘i’ denotes the ratio of the interference due tousers within a cell to the interference caused by users outside the cell. Hence, thegreater this ratio, the more outer-cell interference there is an the less availablecapacity there is within a cell hence steeper curve.There are two ways that cell load can be estimated, either based on throughput, ie theamount of data being handled by the cell, or based on power, ie base stationtransmitted or received power levels. Both methods are used, although we willconcentrate largely on the power based method.

Page 135: RANPAR 1
Page 136: RANPAR 1
Page 137: RANPAR 1
Page 138: RANPAR 1
Page 139: RANPAR 1
Page 140: RANPAR 1
Page 141: RANPAR 1
Page 142: RANPAR 1
Page 143: RANPAR 1
Page 144: RANPAR 1

NB = NodeBRS = Radio Server

Page 145: RANPAR 1
Page 146: RANPAR 1
Page 147: RANPAR 1
Page 148: RANPAR 1
Page 149: RANPAR 1
Page 150: RANPAR 1
Page 151: RANPAR 1
Page 152: RANPAR 1
Page 153: RANPAR 1
Page 154: RANPAR 1
Page 155: RANPAR 1

L1 measurement period in 25.133

Page 156: RANPAR 1
Page 157: RANPAR 1
Page 158: RANPAR 1
Page 159: RANPAR 1
Page 160: RANPAR 1
Page 161: RANPAR 1
Page 162: RANPAR 1
Page 163: RANPAR 1
Page 164: RANPAR 1
Page 165: RANPAR 1
Page 166: RANPAR 1
Page 167: RANPAR 1

Note 1 – AC resides in RRM of RNC

Bullet 3.1- Admission decision is done when RRC connection or RAB setup isrequested

RRC connection setup due to emergency call is different than due to RT RAB or NRTRAB establishmentAdmission control for RAB setup is different for RT and NRT

•RT criterion is applied for conversational and streaming class RABs (for bothemergency and non-emergency calls)•NRT criterion is applied for interactive and background class RABs

RT RAB setup procedure over NRT is possibleRT RAB pre-emption procedure can be applied (release of resources)

Bullet 4.2 – If RAB request is for set-up AC load estimation is performed for both ULand DL. Also, the initial DL Tx power for the RL is calculated separately from the DLload increase estimate.

If the RAB request is for handover AC load estimation is only performed for DL as it isassumed that a new branch addition does not increase the UE power. Also, forhandover the initial DL power is used for DL load change estimation

Bullet 6.3 – AC does not produce an initial SIR target for DL but does calculate DLEb/No target from RAB attributes

Page 168: RANPAR 1
Page 169: RANPAR 1
Page 170: RANPAR 1
Page 171: RANPAR 1
Page 172: RANPAR 1
Page 173: RANPAR 1
Page 174: RANPAR 1
Page 175: RANPAR 1
Page 176: RANPAR 1
Page 177: RANPAR 1
Page 178: RANPAR 1
Page 179: RANPAR 1
Page 180: RANPAR 1
Page 181: RANPAR 1
Page 182: RANPAR 1

Residual BER is mapped to BLER which is mapped to Eb/No.Residual BER (RBER) indicates the undetected bit error ratio in the delivered SDUs iferror detection has been requested, otherwise it indicates the BER in the deliveredSDUs.AC maps these RBER from the RAB Service attribute table to BLER using look uptables. These are in turn converted to Eb/No values from another look up tableresiding in the RNC, and SIR targets calculated accordingly.

Page 183: RANPAR 1

Residual BER is mapped to BLER which is mapped to Eb/No.Residual BER (RBER) indicates the undetected bit error ratio in the delivered SDUs iferror detection has been requested, otherwise it indicates the BER in the deliveredSDUs.AC maps these RBER from the RAB Service attribute table to BLER using look uptables. These are in turn converted to Eb/No values from another look up tableresiding in the RNC, and SIR targets calculated accordingly.

Page 184: RANPAR 1

Residual BER is mapped to BLER which is mapped to Eb/No.Residual BER (RBER) indicates the undetected bit error ratio in the delivered SDUs iferror detection has been requested, otherwise it indicates the BER in the deliveredSDUs.AC maps these RBER from the RAB Service attribute table to BLER using look uptables. These are in turn converted to Eb/No values from another look up tableresiding in the RNC, and SIR targets calculated accordingly.

Page 185: RANPAR 1

Residual BER is mapped to BLER which is mapped to Eb/No.Residual BER (RBER) indicates the undetected bit error ratio in the delivered SDUs iferror detection has been requested, otherwise it indicates the BER in the deliveredSDUs.AC maps these RBER from the RAB Service attribute table to BLER using look uptables. These are in turn converted to Eb/No values from another look up tableresiding in the RNC, and SIR targets calculated accordingly.

Page 186: RANPAR 1
Page 187: RANPAR 1
Page 188: RANPAR 1
Page 189: RANPAR 1
Page 190: RANPAR 1
Page 191: RANPAR 1

RB is a Radio Bearer. RLC is Radio Link Control which provides segmentation/re-assembly and re-transmission services for both user data (Radio Bearer) and controldata (Signalling Radio Bearer). RLC Is a layer2 function.

Transmission mode is either TM (Transparent Mode no protocol overhead added tohigher layers), UM (Unacknowledged mode, delivery not guarenteed) or AM(Acknowledged mode, delivery guarenteed).

In RAS06 there is feature to provide QoS for PS Streaming RAB

Page 192: RANPAR 1

In UTRAN, the data carried at higher layers is carried over the air interface usingtransport channels mapped on to different physical channels.Transport Formats describe how Transport Channels are mapped to Physicalchannels at layer 1.The Transport Format is the format offered by L1 to MAC. MAC is responsible formapping logical channels on to transport channels.MAC selects the appropriate TF within an assigned TFS for each active TrCHdepending on the source rate (efficient use of transport channels), given the TFCSassigned by the RRC.

A Transport Format Combination is a combination of valid TFs that can be submittedsimulataneously to layer 1 on a Coded Composite transport channel (CCTrCH)of aUE. Ie containing one TF from each TrCH that is part of the combination.Transport Format Combination Sets is defined as a set of TFC on a CCTrCH and isproduced by a proprietry algorithm in the RNC. The TFCS is given to MAC by L3 forcontrol. When mapping data to L1, MAC chooses between the different TFCsspecified within the TFCSTransport Format Indicator (TFI) is a label for a specifc TF within a TFS. It is used inthe inter-layer communication between MAC and L1, each time a TBS is exchangedbetween the two layers on a transport channel.SL=signalling, RT RB = Real Time Radio Bearer

The PHY layer can multiplex several Transport Channels in one „internal“ TransportChannel, called Coded Composite Transport Channel (CCTrCH). This CCTrCH canbe transmitted on one or several physical channels. Consequently, the TFCSs ofdifferent Transport Channels can be found in one radio frame.The Transport Format Combination Set (TFCS) lists all allowed Transport FormatCombinations (TFC). A Transport Format Combination Indicator (TFCI) is then usedto indicate, what kind of Transport Format Combination is found on the radio frame.You can find TFCI-fields for instance in the S-CCPCH. The TFCS is set by the RRCprotocol.

Page 193: RANPAR 1
Page 194: RANPAR 1
Page 195: RANPAR 1
Page 196: RANPAR 1
Page 197: RANPAR 1
Page 198: RANPAR 1

This parameter determines the DL/UL load measurement averaging window size innumber of NBAP: Radio Resource Indication message periods. This window is usedin averaging the total transmission power measurement results of a cell that arereceived from the BTS in the NBAP: Radio Resource Indication messages. Slidingtype of window is used: the oldest measurement result is removed when a new one isreceived from BTS.

Page 199: RANPAR 1
Page 200: RANPAR 1
Page 201: RANPAR 1
Page 202: RANPAR 1
Page 203: RANPAR 1
Page 204: RANPAR 1
Page 205: RANPAR 1
Page 206: RANPAR 1
Page 207: RANPAR 1
Page 208: RANPAR 1

NST = Non-Scheduled Transmission = PS Streaming on E-DCHNST is under RNC scheduling, but uses E-DCH-related physical channels includingL1 retransmission

Page 209: RANPAR 1
Page 210: RANPAR 1
Page 211: RANPAR 1
Page 212: RANPAR 1
Page 213: RANPAR 1
Page 214: RANPAR 1
Page 215: RANPAR 1
Page 216: RANPAR 1
Page 217: RANPAR 1

RAB will not be admitted under this condition if either or both criterion are satisfied.Formula indicates estimated power increase in UL (Aprx_nc) of admitting a RAB aswell as existing UL power (Prx_nc) and compares it to Prx_target (PrxNoise +PrxTarget)

Page 218: RANPAR 1

The increase of the non-controllable load DPrx_nc is estimated on the basis of the Prx_Total

Where Prx_Total is the total interference power (all the UL power including own cell users,other cell users and external interference) received by the BTS (WTR)

Page 219: RANPAR 1

The increase of the non-controllable load DPrx_nc is estimated on the basis of the Prx_Total

Where Prx_Total is the total interference power (all the UL power including own cell users,other cell users and external interference) received by the BTS (WTR)

Page 220: RANPAR 1
Page 221: RANPAR 1

Here it should be noted that NRT RAB requests can always be admitted due to thatthe PS can schedule the NRT service bit rates according to the current load situation(NRT RAB can be admitted and bitrates can be throttled back down to 0kbit/s = NRTservice does not mean immediate UL load increase)

Upper threshold PrxNoise +PrxTarget+PrxOffset is Prx_Target_BS….this is not aparameter, as it is calculatedLower threshold PrxNoise+PrxTarget is PrxTargetNote that the offset allows for instaneous overload conditions to arise in particularcells

Page 222: RANPAR 1

Case 1 - RT admission will begranted (as well as NRT) in ULfrom cell powers point of view (stillRM needs to allocate necessarycodes etc.)

Case 2 - RT RAB admitted as onlythe Non Controllable load is havingeffect on the admission decision(nothing has changed from case I)

Page 223: RANPAR 1

Case 1 - RT admission will begranted (as well as NRT) in ULfrom cell powers point of view (stillRM needs to allocate necessarycodes etc.)

Case 2 - RT RAB admitted as onlythe Non Controllable load is havingeffect on the admission decision(nothing has changed from case I)

Page 224: RANPAR 1

Case 3 - RT admission will begranted (as well as NRT) in UL.Case 4 - RT RAB will be denieddue to Non Controllable load isover the target but NRT RAB ispermitted

Page 225: RANPAR 1

Case 3 - RT admission will begranted (as well as NRT) in UL.Case 4 - RT RAB will be denieddue to Non Controllable load isover the target but NRT RAB ispermitted

Page 226: RANPAR 1
Page 227: RANPAR 1
Page 228: RANPAR 1

Power level is a function of pathloss, interference and SIR. Note thatDPCCH_Power_offset is not a parameter but a calculated value.

Page 229: RANPAR 1
Page 230: RANPAR 1
Page 231: RANPAR 1
Page 232: RANPAR 1

The total transmitted wideband power is all the power that the cell is transmitting (i.e.traffic load of radio resources)Higher layer filtering used with OpenIub (RAS51 and after), alpha filter Nokiau Iub(RAN4)

Page 233: RANPAR 1

The total transmitted wideband power is all the power that the cell is transmitting (i.e.traffic load of radio resources)Higher layer filtering used with OpenIub (RAS51 and after), alpha filter Nokiau Iub(RAN4)

Page 234: RANPAR 1
Page 235: RANPAR 1
Page 236: RANPAR 1
Page 237: RANPAR 1
Page 238: RANPAR 1
Page 239: RANPAR 1

Case 1 - RT admission will begranted (as well as NRT) in DLfrom cell powers point of view (stillRM needs to allocate necessarycodes etc.) Both Non controllableload and the Total load is below thetarget.

Case 2 - RT RAB admitted as theNon Controllable load is below thetarget (nothing has changed fromcase I)

Page 240: RANPAR 1

Case 3 - RT admission will begranted (as well as NRT) in DL.Case 4 - RT RAB will be denieddue to Non Controllable load isover the target but NRT RAB ispermitted.

Page 241: RANPAR 1
Page 242: RANPAR 1
Page 243: RANPAR 1
Page 244: RANPAR 1
Page 245: RANPAR 1
Page 246: RANPAR 1
Page 247: RANPAR 1
Page 248: RANPAR 1

PtxDLabsMax =The planned maximum downlink transmission power ofa radio link. This parameter is used in the downlinkpower allocation when the CCTrCH includes one ormore DCHs of interactive or background traffic classRABs. The allocated power of a radio link cannotexceed the value of this parameter. This parameter is theplanned maximum, not the physical limit.PtxPSstreamAbsMaxPlanned maximum transmitted code power of the radiolink for the PS streaming RAB. The parameter definesthe maximum code power of the radio link for the realtime services, when the CCTrCH includes a DCH of thePS streaming traffic class RAB.

Page 249: RANPAR 1
Page 250: RANPAR 1
Page 251: RANPAR 1
Page 252: RANPAR 1
Page 253: RANPAR 1
Page 254: RANPAR 1
Page 255: RANPAR 1
Page 256: RANPAR 1
Page 257: RANPAR 1
Page 258: RANPAR 1
Page 259: RANPAR 1
Page 260: RANPAR 1
Page 261: RANPAR 1
Page 262: RANPAR 1
Page 263: RANPAR 1
Page 264: RANPAR 1
Page 265: RANPAR 1
Page 266: RANPAR 1
Page 267: RANPAR 1
Page 268: RANPAR 1
Page 269: RANPAR 1

If the IE Establishment Cause of the RRC: RRC Connection Request has any of thevalues "Emergency call", "Registration", "Detach", "Originating High PrioritySignalling", "Terminating High Priority Signalling", "Inter-RAT cell reselection", or"Inter-RAT cell change order", then the RRC connection request is not rejected eitherfor received wide band power or transmitted power reasons.

When the IE Establishment Cause has any of the values "Originating ConversationalCall", "Terminating Conversational Call", "Originating Streaming Call", "TerminatingStreaming Call", "Originating Interactive Call", "Originating Background Call","Terminating Interactive Call", "Terminating Background Call", "OriginatingSubscribed traffic Call", "Originating Low Priority Signalling", "Terminating LowPriority Signalling", "Call reestablishment", or "Terminating - cause unknown", theRRC connection request is admitted if non-controllable load is below targetthreshold

Page 270: RANPAR 1
Page 271: RANPAR 1
Page 272: RANPAR 1
Page 273: RANPAR 1

SC:= Load in Spreading code domain

Page 274: RANPAR 1
Page 275: RANPAR 1
Page 276: RANPAR 1
Page 277: RANPAR 1
Page 278: RANPAR 1
Page 279: RANPAR 1
Page 280: RANPAR 1
Page 281: RANPAR 1
Page 282: RANPAR 1

APN = Access Point Name, important for CN

Page 283: RANPAR 1
Page 284: RANPAR 1
Page 285: RANPAR 1
Page 286: RANPAR 1
Page 287: RANPAR 1
Page 288: RANPAR 1

Changes in non-controllable load are due to establishment of new RABs or newpower requirements of existing RABsSimilar principle to GPRS territory allocation – realtime users get desired capacity andnon-realtime users utilise remaining capacity (RAN 1.5)Differences: Available capacity has to be checked in all cells of Active Set

In soft(er)-HO, the NRT from the servingBTS is RT traffic in other BTS

Scheduling of capacity occurs in regularintervals (not event driven, i.e. when a call is cleared)In subsequent RAN releases PS will be enhanced to provide QoS also to NRT traffic.

Page 289: RANPAR 1

PS done for DCH and common control channels (RACH/FACH)

For more information on Packet Access on HSPA, see RRM of HSDPA/HSUPANOLS documents.

Page 290: RANPAR 1
Page 291: RANPAR 1
Page 292: RANPAR 1
Page 293: RANPAR 1

AC Admission control BTS Base transceiver station HC Handover control LC Loadcontrol MAC Medium access control NBAP Node B application protocol PS Packetscheduler RLC Radio link control RM Resource manager RRC Radio resource controlTRM Transport resource manager

Page 294: RANPAR 1
Page 295: RANPAR 1
Page 296: RANPAR 1
Page 297: RANPAR 1
Page 298: RANPAR 1

C-Iub = Common Iub = exSiemens NodeB connected to NSN RNC

Page 299: RANPAR 1
Page 300: RANPAR 1
Page 301: RANPAR 1
Page 302: RANPAR 1
Page 303: RANPAR 1
Page 304: RANPAR 1
Page 305: RANPAR 1
Page 306: RANPAR 1
Page 307: RANPAR 1
Page 308: RANPAR 1
Page 309: RANPAR 1
Page 310: RANPAR 1

Infrequent small data > FACH/RACH > CELL_FACHFrequent or large data > DCH > CELL_DCH

Page 311: RANPAR 1
Page 312: RANPAR 1
Page 313: RANPAR 1
Page 314: RANPAR 1
Page 315: RANPAR 1
Page 316: RANPAR 1
Page 317: RANPAR 1
Page 318: RANPAR 1
Page 319: RANPAR 1
Page 320: RANPAR 1
Page 321: RANPAR 1
Page 322: RANPAR 1
Page 323: RANPAR 1
Page 324: RANPAR 1
Page 325: RANPAR 1
Page 326: RANPAR 1

Uplink traffic volume measurement reports

Uplink traffic volume measurement reports are included in RRC: MEASUREMENTREPORT messages. Traffic volume measurement reports from the UE are handledas uplink capacity requests in the RNC. The actions that the RNC takes on the basisof these reports depend on a number of factors

Downlink traffic volume measurement reports

Downlink traffic volume measurement reports are RNC internal messages. Trafficvolume measurement reports from the MAC-layer are handled as downlink capacityrequests in the RNC. The actions that the RNC takes on the basis of these reportsdepend on a number of factors:

Page 327: RANPAR 1
Page 328: RANPAR 1
Page 329: RANPAR 1
Page 330: RANPAR 1
Page 331: RANPAR 1
Page 332: RANPAR 1
Page 333: RANPAR 1
Page 334: RANPAR 1
Page 335: RANPAR 1
Page 336: RANPAR 1
Page 337: RANPAR 1
Page 338: RANPAR 1
Page 339: RANPAR 1
Page 340: RANPAR 1

The dedicated channel upgrade can only be done if at least the initial bit rate hasbeen allocated to all queued capacity requests and there is spare capacity toschedule. The dedicated channel upgrade procedure is performed in CELL_DCHstate and it requires the reconfiguration of radio link, transmission and RNC internalresources.

Page 341: RANPAR 1
Page 342: RANPAR 1
Page 343: RANPAR 1
Page 344: RANPAR 1
Page 345: RANPAR 1
Page 346: RANPAR 1
Page 347: RANPAR 1
Page 348: RANPAR 1
Page 349: RANPAR 1
Page 350: RANPAR 1
Page 351: RANPAR 1
Page 352: RANPAR 1
Page 353: RANPAR 1
Page 354: RANPAR 1
Page 355: RANPAR 1
Page 356: RANPAR 1
Page 357: RANPAR 1
Page 358: RANPAR 1
Page 359: RANPAR 1
Page 360: RANPAR 1
Page 361: RANPAR 1
Page 362: RANPAR 1
Page 363: RANPAR 1
Page 364: RANPAR 1
Page 365: RANPAR 1
Page 366: RANPAR 1
Page 367: RANPAR 1
Page 368: RANPAR 1
Page 369: RANPAR 1
Page 370: RANPAR 1
Page 371: RANPAR 1
Page 372: RANPAR 1
Page 373: RANPAR 1
Page 374: RANPAR 1
Page 375: RANPAR 1
Page 376: RANPAR 1
Page 377: RANPAR 1
Page 378: RANPAR 1
Page 379: RANPAR 1

The reason why the total transmission power is checked is that, from the interferencepoint of view, it is less efficient to use the FACH (no closed loop power control) than adedicated channel.

Page 380: RANPAR 1
Page 381: RANPAR 1
Page 382: RANPAR 1
Page 383: RANPAR 1
Page 384: RANPAR 1
Page 385: RANPAR 1
Page 386: RANPAR 1
Page 387: RANPAR 1
Page 388: RANPAR 1

Non-HSDPA transmitted power (Transmitted carrier power of all codes notused for HS-PDSCH or HS-SCCH transmission) is used instead of totaltransmitted power in:

Downlink channel type selection between FACH and DCHDL packet schedulingDL overload control

Page 389: RANPAR 1
Page 390: RANPAR 1
Page 391: RANPAR 1
Page 392: RANPAR 1
Page 393: RANPAR 1

Minimum available uplink load Lallowed_minDCH in the uplink DCHscheduling

Page 394: RANPAR 1
Page 395: RANPAR 1
Page 396: RANPAR 1
Page 397: RANPAR 1
Page 398: RANPAR 1
Page 399: RANPAR 1
Page 400: RANPAR 1
Page 401: RANPAR 1
Page 402: RANPAR 1
Page 403: RANPAR 1
Page 404: RANPAR 1
Page 405: RANPAR 1
Page 406: RANPAR 1
Page 407: RANPAR 1
Page 408: RANPAR 1
Page 409: RANPAR 1
Page 410: RANPAR 1
Page 411: RANPAR 1
Page 412: RANPAR 1
Page 413: RANPAR 1

rnew and rold : the planned Eb/N0 values for the modified RB ;new Eb/N0 (new) value and old Eb/N0 (old) valueRnew and Rold : bit rates, new being the current bitrate inthe load increase/decrease algorithmPtx_average,RL : radio link average transmission power,which reported to RNC by BTS

Page 414: RANPAR 1
Page 415: RANPAR 1

When PS has detected the overload situation in downlink and scheduled a subsetfrom the original TFCS, it reconfigures the L2 by sending the TFC subset to the UEspecific MAC-d entity of RNC. After the procedure data transmission can begin usingTFC subset.The original TFCS is taken into use using the same procedure, when the overloadsituation is over.

Page 416: RANPAR 1
Page 417: RANPAR 1
Page 418: RANPAR 1
Page 419: RANPAR 1
Page 420: RANPAR 1

rnew and rold : the planned Eb/N0 values for the modified RB ;new Eb/N0 (new) value and old Eb/N0 (old) valueRnew and Rold : bit rates, new being the current bitrate inthe load increase/decrease algorithmPtx_average,RL : radio link average transmission power,which reported to RNC by BTS

Page 421: RANPAR 1
Page 422: RANPAR 1
Page 423: RANPAR 1
Page 424: RANPAR 1
Page 425: RANPAR 1
Page 426: RANPAR 1
Page 427: RANPAR 1
Page 428: RANPAR 1
Page 429: RANPAR 1
Page 430: RANPAR 1
Page 431: RANPAR 1
Page 432: RANPAR 1
Page 433: RANPAR 1
Page 434: RANPAR 1
Page 435: RANPAR 1
Page 436: RANPAR 1
Page 437: RANPAR 1
Page 438: RANPAR 1

Difference to GSM. GSM uses periodic signal strength reporting. Every 480 ms themobile reports signal levels to BSC. WCDMA uses event-driven reporting, only whenevent occurs will UE report signal levels to network.

Maximum Ratio Combining before do-coding, based on EbNo of received signals.Frame Selection Combining, after coding, select frame with least errors.

Three stages for HO: 1 define adjacent cells (which cells to measure = same inGSM), 2 define measurement control (when to measure), 3 define what to do withmeasurements (which decision to make = if DLSigLev < -95dBm HO)

Page 439: RANPAR 1
Page 440: RANPAR 1
Page 441: RANPAR 1
Page 442: RANPAR 1
Page 443: RANPAR 1

The stages in WCDMA are similar to GSM (not identical).In Intra-freq case we can have 32 adjS. And each cell (not adj has one set ofparameters that define how to trigger adj reporting for RT (and one for NRT)). Eachadj has a list attached, defining the thresholds to be met before HO)Same principle also for Inter-Freq and Inter-System.adjS stands for intra-freqadjI stands for inter-freqadjG stands for inter-system parametersMAX: 31 intra-freq adj 32 inter-freq adj (48 in RAN1.5 but only 32 can have thesame freq – so other 16 have to have other freq = third freq) 32 inter-syst adj100 FMCx lists and 100 HOPx lists

Page 444: RANPAR 1
Page 445: RANPAR 1

100 sets for intra-freq, 100 sets for inter-freq and 100 sets for inter-systemBenefit of Parameter Sets: Modification of Set is simple, one change implementschanges to all cells on RNC

HOPS parametersCell Re-selection HCS PriorityCell Re-selection HCS ThresholdCell Re-selection Minimum QualityCell Re-selection Minimum RX LevelCell Re-selection Penalty TimeCell Re-selection Quality Offset 1Cell Re-selection Quality Offset 2Cell Re-selection Temporary Offset 1Cell Re-selection Temporary Offset 2CPICH Ec/No Averaging WindowEnable Inter-RNC Soft HandoverEnable RRC Connection ReleaseHHO Margin for Average Ec/NoHHO Margin for Peak Ec/NoRelease Margin for Average Ec/NoRelease Margin for Peak Ec/No

Page 446: RANPAR 1
Page 447: RANPAR 1
Page 448: RANPAR 1
Page 449: RANPAR 1

System Information Block type 11bis (SIB11bis) provides extension segments for SIB11 andsolves an inconsistency problem in 3GPP TS 25.331, which has prevented the usage ofcomplete neighbouring cell lists for idle mode UEsSystem Information Block type 11/11bis: contains measurement control information to be usedin the cell. This SIB is read by MSs in idle mode and in CELL_FACH, CELL_PCH andURA_PCH state. It is used also in CELL_DCH stateComplete neighbouring cell lists can be provided to guarantee optimal cell re-selection andend-user QoSAllows the definition of 32 intra-frequency, 32 inter-frequency and 32 inter-systemneighbouring cells for idle mode UEs

All these neighbours were originally intended to be included in SIB11, but inthe specifications the physical size of SIB11 data has capacity only for 47cells

Page 450: RANPAR 1
Page 451: RANPAR 1

It is always important to be connected to the best server (best Ec/Io). Since there isno periodic reporting -HO the evaluation is done by UE. To inform RNC about thesecase, 3 events are defined.

Page 452: RANPAR 1

In the CELL_DCH state the UE physical layer measurement period for intra frequencyCPICH Ec/No measurements is 200 ms. The Filter Coefficient parameter controls thehigher layer filtering of physical layer CPICH Ec/No measurements before the eventevaluation and measurement reporting is performed by the UE. The higher layerfiltering is described in 3GPP TS 25.331 RRC Protocol Specification. This parameteris part of System Information Block 11/12.0 (Filtering period of 200 ms ), 1 (Filtering period approximates 300 ms), 2 (Filteringperiod approximates 400 ms), 3 (Filtering period approximates 600ms), 4 (Filteringperiod approximates 800 ms), 5 (Filtering periodapproximates 1100 ms), 6 (Filtering period approximates 1600 ms)Default value notes : 0=Higher layer filtering is not used

This parameter determines the number of event triggered periodic intrafrequencymeasurement reports from which the RNC calculates the averaged CPICH Ec/Novalues.Default: 8 MeasReport Range 1 ... 32 MeasReport, step 1MeasReportHigh UE speed (60km/h) 50-200 ms are ideal to eliminate characterise the signaleven when fading – low UE speeds (6km/h) longer times might be required (1s) tocompensate effect of fading

Page 453: RANPAR 1
Page 454: RANPAR 1

System Info: how should UE measureMeasurement control: threshold for when to report

The AS should always contain the X cells with the strongest CPICH – if the CPICH iswithin a certain range of the strongest CPICH. Three events can occur: enter, leave,replace.

Page 455: RANPAR 1

Active Set Weighting Coefficient (W) is used to weight either the measurement resultof the best active set cell (M_best) or the sum of measurement results of all active setcells (M_sum) when the UE calculatesthe reporting range for the events 1A (cell addition) and 1B (dropping of cell).The formula is: W * M_sum + ( 1 - W )* M_best 0 is default: thismeans that it is the Best cell that determines values such as windowAdd orwindowDrop.This parameter is part of System Information Block 11/12.

Page 456: RANPAR 1

In this case the AS is NOT full event 1A – otherwise it would be event 1C!

1) Determine reference level (either strongest CPICH or mixture of AS CPICH)2) Threshold when to add new CPICH3) How long the new CPICH has to be above threshold before is reported as 1A4) If not added to AS when to notify network again

Page 457: RANPAR 1

Is Time to trigger: AdditionTime / 0 = 0 ms a sensible value??

Page 458: RANPAR 1
Page 459: RANPAR 1

There is no replacement for P CPICH 3 – otherwise it would be 1C replace

Page 460: RANPAR 1
Page 461: RANPAR 1
Page 462: RANPAR 1

1C Event: ReplacementWindow = 4dB is default – isn’t this a relatively high value?In Parameter Dictionary the formula shown is: MNew >= MInAs + ReplacementWindow / 2 (What does“/2” mean? Why a division by 2???)

Page 463: RANPAR 1

Default parameters to be used for Window_add/Window_dropNRT/

Page 464: RANPAR 1
Page 465: RANPAR 1
Page 466: RANPAR 1

The offset has a range of –10dB to +10dB so it is possible to also make a cell lessattractive

How much use is made of these features???What are the corresponding parameters in 2G(T31 / T32)?

Page 467: RANPAR 1

Like T31 and T32 in GSM

Page 468: RANPAR 1

Not hear that this option is widely used.

Page 469: RANPAR 1
Page 470: RANPAR 1

Active Set Weighting Coefficient (W) is used to weight either the measurement resultof the best active set cell (M_best) or the sum of measurement results of all active setcells (M_sum) when the UE calculatesthe reporting range for the events 1A (cell addition) and 1B (dropping of cell).

The formula is: W * M_sum + ( 1 - W )* M_best 0 is default: this means that itis the Best cell that determines values such as windowAdd or windowDrop.

This parameter is part of System Information Block 11/12.

Page 471: RANPAR 1

This parameter defines the absolute threshold which is used by the UE to trigger thereporting event 6F due to UE Rx-Tx time difference. The MS sends an event 6Ftriggered measurement report to the RNC whenthe UE Rx-Tx time difference for a radio link included in the active set becomes largerthan the threshold. The RNC uses the measurement report to adjust the DL DPCHair-interface timing of the radio link. The RNC adjusts the DL DPCH air-interfacetiming by replacing the old radio link (which triggered the reporting event 6F) by a newradio link (with renewed air-interface timing) in the same active set cell.

2560 chips per timeslot (10ms divided by 15)

Page 472: RANPAR 1

Like throughing balls from different positions to catcher, if the timing of the throughsare not optimised, the catcher can not catch all these.In GSM Timing Advance is used to counter this effect. And an upper limit exists in thevalue of the timing advance (35km). Otherwise the timing offset of the busts will runinto the next Time Slot.

2560 chips per timeslot (10ms divided by 15)UpperRxTxTimeDiff default: 1174 chips range:1152 ... 1280 chips, step 1 chipLowerRxTxTimeDiff default: 874 chips range: 768 ... 896 chips, step 1 chip

More Measurement Event 6 in Power Control.

Page 473: RANPAR 1

When mobile is connected to more than 1 cell (SHO) which cell determine the HOPSand ADJS parameters? Controlling cells = cells where call started or strongest cell ifstarting cell has left AS

Page 474: RANPAR 1

When mobile is connected to more than 1 cell (SHO) which cell determine the HOPSand ADJS parameters? Controlling cells = cells where call started or strongest cell ifstarting cell has left AS

Page 475: RANPAR 1

After every active set modification (addition, deletion orreplacement) the Handover algorithm ranks the active set cells (1-3) inorder from best to worst according CPICH EcNo measurement results.

( The controlling cell remains the same as far as the cell is included in the active setcell. When the old controlling cell is removed from the active set the best (CPICHEcNo) Scell is selected to be the new controlling cell. )

After the Handover algorithm has ranked active set cells it ranks the neighbor s ofactive set cell for the monitoring list. Because the neighbor cell lists of two or moreactive cells, which are participating in soft Handover, can be different, the Handovercontrol of the RNC shall combine the lists into one neighborcell list which is transmitted to the mobile station. Note that the monitoring list (max32 cells) includes also active set cells (1-3) and the neighbor cells (max 31-29neighbor s)

The combination of intra-frequency neighbor cell list is to the monitoring list isfollowing:1. Step: Active set cells2. Step: Neighbour cells which are common to three active set cells3. Step: Neighbour cells which are common to two active set cells

If 32 is exceeded, cells from second step are removed at random4. Step: Neighbour cells which are defined for only one cell

If 32 is exceeded, cells are removed, starting with those defined forweakest AS cell

If the total number of monitored cells exceeds the maximum number of 32 during anystep, the Handover control stops themonitoring cell list preparation and sends the measurement control modification to UEincluding the updated monitoring cell list.

Page 476: RANPAR 1

AveEcNoDownlink + HHoMarginForAveEcNo(n) < AvEcNoNcell(n) islike in GSM PGBT Level in other cell is better than level in current cell

If Soft-HO would always possible, then UE would always be connected to the bestcell. Only if soft-HO is not possible is HHO required.

Page 477: RANPAR 1
Page 478: RANPAR 1
Page 479: RANPAR 1
Page 480: RANPAR 1

Default parameters to be used for Window_add/Window_dropNRT/

Page 481: RANPAR 1

When would a RB be released??? When it is not possible to add Neighbouring Cell(NS)

Page 482: RANPAR 1
Page 483: RANPAR 1
Page 484: RANPAR 1
Page 485: RANPAR 1
Page 486: RANPAR 1
Page 487: RANPAR 1
Page 488: RANPAR 1
Page 489: RANPAR 1
Page 490: RANPAR 1
Page 491: RANPAR 1
Page 492: RANPAR 1

The SRNC and DRNC support the following inter-frequency handover signallingprocedures over Iur:

Inter-frequency handover within DRNS when all radio links in theactive set are controlled by the target DRNCInter-frequency handover from the SRNS to the DRNS whenone (or more) radio link in the active set is controlled by thetarget DRNCInter-frequency handover from the SRNS to the DRNS when noradio link in the active set is controlled by the target DRNCInter-frequency handover from the DRNS back to the SRNSInter-frequency handover between two DRNSs when no radiolink in the active set is controlled by the target DRNC

Page 493: RANPAR 1
Page 494: RANPAR 1
Page 495: RANPAR 1
Page 496: RANPAR 1
Page 497: RANPAR 1
Page 498: RANPAR 1
Page 499: RANPAR 1
Page 500: RANPAR 1

Time to trigger is done for 6B only: InterfreqUETxPwrTimeHyst (IF HOenabled only), GsmUETxPwrTimeHyst (IS HO enabled only) or Time-to-trigger (both IF and IS HO enabled)InterfreqUETxPwrTimeHyst, GsmUETxPwrTimeHyst:Range: 0 ms, 10 ms, 20 ms, 40 ms, 60 ms, 80 ms, 100 ms, 120 ms,160 ms, 200 ms, 240 ms,320 ms, 640 ms, 1280 ms, 2560 ms, 5000 ms

Default: 1280 msThe maximum allocated user bitrate HHoMaxAllowedBitrateUL:Range 32 kbit/s, 64 kbit/s, 128 kbit/s, 256 kbit/s, 320 kbit/s, 384 kbit/s

Default : 32 kbits/s

HO Enabling parameters RangeDefault

IFHOcauseTxPwrUL 0 (Not used), 1 (In use) 0GSMcauseTxPwrUL 0 (Not used), 1 (In use) 0

Page 501: RANPAR 1
Page 502: RANPAR 1

Measurement threshold parameters: (FMCI, FMCG object inparamerer dictionary)Name (FMCI) Range DefaultInterfreqUETxPwrThrAMR-10 ... 0 dB, step 1 dB -3 dBInterfreqUETxPwrThrCS -10 ... 0 dB, step 1 dB -3 dBInterfreqUETxPwrThrNrtPS-10 ... 0 dB, step 1 dB -3 dBInterfreqUETxPwrThrRtPS -10 ... 0 dB, step 1 dB -3 dBAdjiPriorityCoverage 0 ... 7 , step 1 0

Page 503: RANPAR 1

DL_CODE_PWR - PowerOffsetDLdpcchPilot >= CPICH_POWER +MAX_DL_DPCH_TXPWR + DL_DPCH_TXPWR_THRESHOLDMAX_DL_DPCH_TXPWR indicates the maximum transmission power level a basestation can use on the DPCH (see Admission Control SFS [9] for more information),expressed as a relative value (dB) with respect to the primary CPICH power (dBm)

Page 504: RANPAR 1

DL_CODE_PWR = power of pilot bitsPower of Data Bits > 33dBm + (-3dB) + (-1dB) => Power of

Data Bits > 29dBmSignal of Data Bits (=DL_Code_PWR-PowerOffsetDLdpcchPilot) >CPICH-Power – MaxLimit on DPCH – service specific offset•PowerOffsetDLdpcchPilot = offset pilots to data (-3dB)•Primary CPICH power = 33 dBm•MAX_DL_DPCH_TXPWR (PtxDPCHmax) indicates the maximumtransmission power level a base station can use on the DPCH (seeAdmission Control SFS [9] for more information), expressed as arelative value (dB) with respect to the primary CPICH power (dBm).(default = -3dB)

•DL_DPCH_TXPWR THRESHOLD (dB) is controlled with the followinginter-frequency measurement control parameters, depending on theservice type (see also Packet Scheduler SFS [8]):

InterFreqDLTxPwrThrRtPS for real time packet switched services(default = -3dB)

InterFreqDLTxPwrThrNrtPS for non-real time packet switched services

InterFreqDLTxPwrThrCS for circuit switched data services (default = -3dB)

InterFreqDLTxPwrThrAMR for circuit switched voice services (default= -1dB)

Page 505: RANPAR 1
Page 506: RANPAR 1

Despite increasing the SIR target to the maximum allowed value thequality is poor! Need to change frequency.

Main Parameters

EnableULQualDetRep indicates whether the UL outer loop PC cansend a quality deterioration report to the Handover control in situationswhen the quality stays worse than the BER/BLER target despite of theuplink SIR target increase.

HHoMaxAllowedBitrateUL: bit rate first has tobe reduced to this level before a HO is possibleULQualDetRepThreshold determines the time period (default 5 s)during which the quality must stay worse than the BER/BLER target(despite of uplink SIR target increase) before the UL outer loop PCmay send a quality deterioration report.

In case of RT data connection (CS or PS), the maximum allocated userbitrate on the uplink DPCH must be lower than or equal to thethreshold HHoMaxAllowedBitrateUL (default 32 kbits/s), before theinter-frequency Handover is possible.

Page 507: RANPAR 1
Page 508: RANPAR 1
Page 509: RANPAR 1
Page 510: RANPAR 1
Page 511: RANPAR 1
Page 512: RANPAR 1
Page 513: RANPAR 1
Page 514: RANPAR 1
Page 515: RANPAR 1
Page 516: RANPAR 1
Page 517: RANPAR 1
Page 518: RANPAR 1
Page 519: RANPAR 1
Page 520: RANPAR 1

Compressed mode is not ideal from a “spectral efficiency point of view” only usedwhen necessary

Spreading Factor Halving: like switching temporarily from ISDN64kbit to ISDN128kbitto transmit more data. Then use the time to carry out more measurements)

Page 521: RANPAR 1

A rough estimation how the compressed mode (CM) effects the cellscapacity if 10% of the cells users are in CM, every 3rd frame iscompressed and the required Eb/No is 1.5 dB higher in CM.Note: This is only an example. There are different CM methods andmeasurement patterns that can be used. According to the situation(service in use, cell load, etc.) one or the other might be preferrable.

Page 522: RANPAR 1
Page 523: RANPAR 1
Page 524: RANPAR 1

ngLimitDLPuncturiPRPR cmoriginal ³×

originalPR

cmPR

Page 525: RANPAR 1
Page 526: RANPAR 1

Whether a UE can be switched on compressed mode in downlink shallbe checked in the following way:If PtxTotal is below PtxTarget and number of UEs in compressed modeis less than MaxNumbUECMcoverHO parameter indicates, a UE canbe switched on compressed mode. If PtxTotal is between PtxTargetand PtxTarget + PtxOffset and MaxNumbUECMcoverHO parameterallows, during the RRI (radio resources indication) interval one moreUE can be switched on compressed mode. If PtxTotal is abovePtxTarget + PtxOffset, no more UE can be switched on compressedmode.Whether a UE can be switched on compressed mode in uplink shall bechecked analogously as in previous paragraphs. Now usedmeasurement result is PrxTotal and RNP parameters to set thresholdpoints are PrxTarget and PrxOffset. MaxNumbUECMcoverHOparameter is used in both uplink and downlink.If a UE is to be switched on compressed mode both in uplink anddownlink, both uplink and downlink checkings has to be done andpassed. If uplink or downlink compressed mode is not needed,corresponding checking shall not be done, because power budget ofthat direction is not affected.

Page 527: RANPAR 1
Page 528: RANPAR 1
Page 529: RANPAR 1

The compressed mode uses predefined transmission gap pattern parametersaccording to compressed mode method used.

TGSN, Transmission Gap Starting Slot Number

A transmission gap pattern begins in a radio frame, henceforward called first radio frame of thetransmission gap pattern, containing at least one transmission gap slot. TGSN is the slotnumber of the first transmission gap slot within the first radio frame of the transmission gappattern;

TGL 1 & 2, Transmission Gap Length

This is the duration of the first and second transmission gap within the transmission gap pattern,expressed in number of slots

TGD , Transmission Gap start Distance

This is the duration between the starting slots of two consecutive transmission gaps within atransmission gap pattern, expressed in number of slots

TGPL1 & 2,Transmission Gap Pattern Length 1&2This is the duration of transmission gap pattern 1&2. If TGPL2 is not explicitly set by higherlayers, then TGPL2 = TGPL1.

TGPL1 depends on the type of service, the method used and themeasurement purpose

Page 530: RANPAR 1
Page 531: RANPAR 1

AVE_RSCP_NCELL (n) > AdjiMinRSCP (n) + max( 0, AdjiTxPwrDPCH (n) – P_MAX )

Where AVE_RSCP_NCELL(n) averaged RSCP values of the best (according to CPICHEc/No) neighbor ing cell (n), measured

AdjiMinRSCP(n) determines the minimum required CPICH RSCP(dBm) level in the best neighbor ing cell (n) , I.e –97dBm

AdjiTxPwrDPCH(n) indicates the maximum transmission powerlevel (dBm) an UE can use on the DPCH, I.e. 24 dBm

P_MAX indicates the maximum RF output power capability of theUE (dBm), 24 dBm corresponds to the UE power class 3

In case the mobile power is lower than the allowed power on channel, this difference is addedas a requirement

AVE_EcNo_NCELL (n) > AVE_CPICH EcNo + AdjiEcNoMargin(n)

Where AVE_EcNo_NCELL (n) is the averaged CPICH Ec/No value of the best(according to CPICH Ec/No) neighbor ing cell (n).

AVE- CPICH_EcNo is the averaged CPICH Ec/No of the bestactive set cell

AdjiEcNoMargin(n) determines the margin (dB) by which theCPICH Ec/No of the best neighbor ing cell (n) must exceed the CPICH Ec/No of the best activeset cell before the inter-frequency Handover is possible.

AVE_EcNo_NCELL (n) > AdjiMinEcNo (n)

Where AVE_EcNo_NCELL (n) is averaged CPICH Ec/No values of the best (accordingto CPICH Ec/No) neighbor ing cell (n)

AdjiMinEcNo(n) determines the minimum required CPICH Ec/No(dB) in the best neighbor ing cell (n).

Page 532: RANPAR 1
Page 533: RANPAR 1
Page 534: RANPAR 1
Page 535: RANPAR 1
Page 536: RANPAR 1
Page 537: RANPAR 1
Page 538: RANPAR 1
Page 539: RANPAR 1
Page 540: RANPAR 1
Page 541: RANPAR 1
Page 542: RANPAR 1
Page 543: RANPAR 1

Missing neighbors can occur in SHO if combined neighbor list is less than allneighbors of all AS cells (as a result of neighbor list combination)

Page 544: RANPAR 1

Inter-System measurements may be started in the UE due to the radio coverage andconnection quality (uplink DCH quality, UE TX power, downlink DPCH power, CPICHRSCP or CPICH Ec/No) reasons .

When the inter-system measurements are completed, the target cell selection takesplace.

The inter-system measurement phase takes a few seconds and during that time theconditions in the WCDMA layer may change.

During the inter-system measurements the UE measures also intra-frequencyWCDMA neighbors.

If the intra-frequency measurements indicate that the conditions have improved in theWCDMA layer so that defined cancellation thresholds are exceeded, the RNC stopsthe handover and compressed mode measurements.

Also, if the UE Internal Measurements or the RL Quality measurements indicate thatthe radio conditions have improved, the ongoing inter-system Handover is interruptedor cancelled.

Active set update due to cell addition/replacement during the measurements alsocauses the inter-system handover cancellation.

With this feature unnecessary Inter-System Handovers can be cancelled in the UEthus retaining the call in current WCDMA network.

Page 545: RANPAR 1
Page 546: RANPAR 1
Page 547: RANPAR 1
Page 548: RANPAR 1
Page 549: RANPAR 1
Page 550: RANPAR 1
Page 551: RANPAR 1
Page 552: RANPAR 1
Page 553: RANPAR 1
Page 554: RANPAR 1
Page 555: RANPAR 1
Page 556: RANPAR 1
Page 557: RANPAR 1
Page 558: RANPAR 1
Page 559: RANPAR 1

WCDMA -> GSM: only coverage reason HOGSM -> WCDMA: load reason and service reason HO

Page 560: RANPAR 1

After a successful Handover new Handover for the same connection isnot allowed in 30 secondsAfter an unsuccessful Handover attempt it is not allowed to initiate a new Handoverattempt to the same cell within time defined by the parameter

MIN_INTERVAL_BETWEEN_UNSUCC_ISHO_ATTEMPT

In BSC the Parameters are as follows:

THRESHOLD FOR MULTI-RAT MS ..................... -74dBm, Qsearch IMIN TRAFFIC LOAD FOR SPEECH CALL ............... 00 %,Load_thresholdMIN TRAFFIC LOAD FOR NON-TRANSPARENT DATA CALL . 00 %,Load_thresholdNUMBER OF MEASURED FDD CELLS ................... 02,FDD_multirap_reportMIN INTERVAL BETWEEN UNSUCC ISHO ATTEMP ........ 03 sADJACENT WCDMA RAN CELL AVERAGING WINDOW SIZE .. 06NUMBER OF WCDMA RAN ZERO RESULTS ............... 05ALL ADJACENT WCDMA RAN CELLS AVERAGED .......... N

Page 561: RANPAR 1
Page 562: RANPAR 1
Page 563: RANPAR 1
Page 564: RANPAR 1
Page 565: RANPAR 1
Page 566: RANPAR 1
Page 567: RANPAR 1
Page 568: RANPAR 1
Page 569: RANPAR 1
Page 570: RANPAR 1
Page 571: RANPAR 1
Page 572: RANPAR 1
Page 573: RANPAR 1
Page 574: RANPAR 1

SLHOUseBackgroundPSNRTData , SLHOUseConvCSSpeech ,SLHOUseConvPSRTData , SLHOUseConvPSSpeech ,SLHOUseInteractivePSNRTData , SLHOUseStreamCSNTData ,SLHOUseStreamPSRTData

Page 575: RANPAR 1
Page 576: RANPAR 1
Page 577: RANPAR 1
Page 578: RANPAR 1

GSMWCDMAWCDMA macro cell

HCS priorities from 0 to 3WCDMA micro cell

HCS priorities from 4 to 7Not defined (WCDMA or GSM)

Page 579: RANPAR 1
Page 580: RANPAR 1
Page 581: RANPAR 1
Page 582: RANPAR 1
Page 583: RANPAR 1
Page 584: RANPAR 1
Page 585: RANPAR 1
Page 586: RANPAR 1
Page 587: RANPAR 1
Page 588: RANPAR 1
Page 589: RANPAR 1
Page 590: RANPAR 1
Page 591: RANPAR 1
Page 592: RANPAR 1
Page 593: RANPAR 1
Page 594: RANPAR 1

Allocates: UL scrambling and spreadingDL spreading (but not scrambling as this is fixed per cell

by RNP)Different types of RNTI (Radio Network Temporary

Identifiers) to UEs

Page 595: RANPAR 1

Application of spreading code already generates wideband data, application ofscrambling code doesn’t change bandwidth.

Page 596: RANPAR 1
Page 597: RANPAR 1

Like a lorry with a capacity to carry 1000kg (SF1), it can have 2 * 500 kg packages(SF2), 4 * 250 kg packages(SF3), etc.

Draw picture with square that can be divided into sub-squares. Re-arranging the usedsquares can help to gain capacity.

Page 598: RANPAR 1
Page 599: RANPAR 1
Page 600: RANPAR 1
Page 601: RANPAR 1
Page 602: RANPAR 1
Page 603: RANPAR 1
Page 604: RANPAR 1
Page 605: RANPAR 1
Page 606: RANPAR 1
Page 607: RANPAR 1
Page 608: RANPAR 1
Page 609: RANPAR 1
Page 610: RANPAR 1
Page 611: RANPAR 1
Page 612: RANPAR 1
Page 613: RANPAR 1
Page 614: RANPAR 1
Page 615: RANPAR 1
Page 616: RANPAR 1
Page 617: RANPAR 1
Page 618: RANPAR 1
Page 619: RANPAR 1
Page 620: RANPAR 1
Page 621: RANPAR 1
Page 622: RANPAR 1
Page 623: RANPAR 1
Page 624: RANPAR 1
Page 625: RANPAR 1
Page 626: RANPAR 1
Page 627: RANPAR 1
Page 628: RANPAR 1
Page 629: RANPAR 1
Page 630: RANPAR 1
Page 631: RANPAR 1
Page 632: RANPAR 1
Page 633: RANPAR 1
Page 634: RANPAR 1
Page 635: RANPAR 1
Page 636: RANPAR 1
Page 637: RANPAR 1
Page 638: RANPAR 1
Page 639: RANPAR 1
Page 640: RANPAR 1

The HARQ method that is defined to be used in the HSPA serving cell defines theHARQ method for the RRC connection in question. Information about the selectedHARQ method is signalled to the BTS using the NBAP: HARQ Info for E-DCH and tothe UE using the RRC: HARQ RV Configuration information elements. ChaseCombining is denoted with ‘rv0’ and Incremental Redundancy Combining with‘rvtable’.

HARQRVConfiguration : This parameter defines the HARQ method that is to be used inthis BTS. Possible choices are Chase Combining and Incremental RedundancyCombining. Nokia BTS supports both methods. The HARQ method that is defined tobe used in the HSPA serving cell defines the HARQ method for the RRC connectionin question. Information about the selected HARQ method is signalled to the BTSusing the NBAP: HARQ Info for E-DCH and to the UE using the RRC: HARQ RVConfiguration information elements. Chase Combining is denoted with ‘rv0’ andIncremental Redundancy Combining with ‘rvtable’.

Page 641: RANPAR 1
Page 642: RANPAR 1
Page 643: RANPAR 1
Page 644: RANPAR 1

The PFR fast scheduling method shall be used in RAN06 to select the transmissionturn for each priority queue if licence for it exists. Otherwise, Round Robin schedulingmethod is used.The scheduling is made at the cycle of TTI (2ms) and based on the RICQ expressedas following:RICQ = Ntb/RWhere Ntb is the supported transport block size in the next TTI, and R is thedelivered average transport block size to the priority queue.At each scheduling interval (2ms), PS shall calculate the RICQ for every priorityqueue, which has data in the BTS buffer or pending retransmissions in HARQprocesses. However, if the UE can not be scheduled due to the minimum inter-TTIinterval capability (see TF_RAN06_SFS_MACHS.15&92), PS shall not calculate theRICQ for any priority queue of the UE. Based on the calculated RICQ, PS shall selectthe priority queue for the transmission on HS-DSCH in next TTI.The PS operation in MAC-hs shall be synchronized with the timing of HS-SCCH andHS-PDSCH.

When PS calculates the RICQ, it shall request LA to provide the supported transportblock size information for each UE. The required parameters to LA from PS areavailable HS-PDSCH transmitting power PHS-PDSCH (seeTF_RAN06_SFS_MACHS.19) and the maximum number of HS-PDSCH codes.Then, the LA shall make CQI offset compensation and adjustment as described in thenormal LA processes (see 5.2.3.3) for each UE. After that, LA shall return therecommended TB size for each UE to PS. The TB size used to calculate the RICQ isthe recommended TB size from LA.

Page 645: RANPAR 1
Page 646: RANPAR 1
Page 647: RANPAR 1
Page 648: RANPAR 1
Page 649: RANPAR 1
Page 650: RANPAR 1
Page 651: RANPAR 1
Page 652: RANPAR 1
Page 653: RANPAR 1
Page 654: RANPAR 1
Page 655: RANPAR 1
Page 656: RANPAR 1
Page 657: RANPAR 1
Page 658: RANPAR 1
Page 659: RANPAR 1
Page 660: RANPAR 1

•MaxDLPowerCapability is calculated by system based on NBAP BTS capabilitymessage at HS-DSCH setup. The value in this message is based on license value(Flexi).•The cell PtxMax is then calculated as min (MaxDLPowerCapability,PtxCellMax)

RNC does not set or signal HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH Total Power IE inNBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message

Page 661: RANPAR 1

Note:- PtxHSDPA is the power allocated to HSDPA, i.e. the instantaneous power in activeTTI- PtxTotal is the total DL power reported by BTS, PtxTotal = average(PtxNC +PtxNRT + PtxHSDPA), where the average HSDPA power depends on the ratio ofscheduled TTIs

Page 662: RANPAR 1
Page 663: RANPAR 1
Page 664: RANPAR 1
Page 665: RANPAR 1
Page 666: RANPAR 1
Page 667: RANPAR 1
Page 668: RANPAR 1
Page 669: RANPAR 1

HSPDSCHMarginSF128 :The parameter defines the required number of free SF128 channelisation codes leftfor DPCHs. The number of free DPCH codes after the HS-PDSCH code upgrade hasto be equal or higher than the parameter value, otherwise the HS-PDSCH codeupgrade is not allowed. Also, if the number of free DPCH codes is lower than thevalue of the parameter, periodical HS-PDSCH code downgrade can be initiated.Def=8

Page 670: RANPAR 1

DPCHOverHSPDSCHThreshold:This parameter defines the number of allocated HS-PDSCH codes that are notallowed to pre-empt by NRT DPCH in the case NRT DPCH code congestion. Thevalue of the parameter is an offset from the maximum allowed number of HS-PDSCHcodes.

Page 671: RANPAR 1
Page 672: RANPAR 1

DPCHOverHSPDSCHThreshold:This parameter defines the number of allocated HS-PDSCH codes that are notallowed to pre-empt by NRT DPCH in the case NRT DPCH code congestion. Thevalue of the parameter is an offset from the maximum allowed number of HS-PDSCHcodes.

Page 673: RANPAR 1
Page 674: RANPAR 1
Page 675: RANPAR 1
Page 676: RANPAR 1
Page 677: RANPAR 1
Page 678: RANPAR 1
Page 679: RANPAR 1
Page 680: RANPAR 1

In this case the AS is NOT full event 1A – otherwise it would be event 1C!

1) Determine reference level (either strongest CPICH or mixture of AS CPICH)2) Threshold when to add new CPICH3) How long the new CPICH has to be above threshold before is reported as 1A4) If not added to AS when to notify network again

Page 681: RANPAR 1

In this case the AS is NOT full event 1A – otherwise it would be event 1C!

1) Determine reference level (either strongest CPICH or mixture of AS CPICH)2) Threshold when to add new CPICH3) How long the new CPICH has to be above threshold before is reported as 1A4) If not added to AS when to notify network again

Page 682: RANPAR 1

In this case the AS is NOT full event 1A – otherwise it would be event 1C!

1) Determine reference level (either strongest CPICH or mixture of AS CPICH)2) Threshold when to add new CPICH3) How long the new CPICH has to be above threshold before is reported as 1A4) If not added to AS when to notify network again

Page 683: RANPAR 1
Page 684: RANPAR 1
Page 685: RANPAR 1
Page 686: RANPAR 1

Step 1R99 UE camping already on correct layer, remains in R99 cellR5 / R6 UE camping on wrong layer, it is attempted to shift it to R5 / R6capable layer (see step 2)

Step 2If service requested by R5 / R6 UE not allowed within R5 / R6 capablelayer, it remains in R99 cellOtherwise it is shifted to R5 / R6 capable layer (see step 3)

Step 3R5 UE shifted either to R5 or R6 capable layer, the better oneaccording load balancing is selectedR6 UE shifted to R6 capable layer, without considering load balancing

Page 687: RANPAR 1
Page 688: RANPAR 1
Page 689: RANPAR 1

-These does not trigger switch itself, because there are some preconditions that mustbe fulfilled before actual switch, just checking of preconditions is triggered-Releasing of HSDPA resources does not trigger directly any DCH to HS-DSCHswitch, released resources are given to that who asks them first (initial reservation orswitch)

Page 690: RANPAR 1
Page 691: RANPAR 1
Page 692: RANPAR 1
Page 693: RANPAR 1
Page 694: RANPAR 1
Page 695: RANPAR 1
Page 696: RANPAR 1
Page 697: RANPAR 1
Page 698: RANPAR 1
Page 699: RANPAR 1
Page 700: RANPAR 1
Page 701: RANPAR 1
Page 702: RANPAR 1
Page 703: RANPAR 1
Page 704: RANPAR 1
Page 705: RANPAR 1
Page 706: RANPAR 1
Page 707: RANPAR 1
Page 708: RANPAR 1
Page 709: RANPAR 1
Page 710: RANPAR 1
Page 711: RANPAR 1
Page 712: RANPAR 1
Page 713: RANPAR 1
Page 714: RANPAR 1
Page 715: RANPAR 1
Page 716: RANPAR 1
Page 717: RANPAR 1
Page 718: RANPAR 1
Page 719: RANPAR 1
Page 720: RANPAR 1
Page 721: RANPAR 1
Page 722: RANPAR 1

SF256 -> 300 bits /frame -> 5 repeats : 60 bits

Abs grant value 5+ scope 1= 6 -> appended with 16 bits CRC masked with 16 bits ID6+16=22 -> R=1/3 then 90 bits -> rate matching down to 60 bits

Page 723: RANPAR 1

SF256 -> 300 bits /frame -> 5 repeats : 60 bits

Abs grant value 5+ scope 1= 6 -> appended with 16 bits CRC masked with 16 bits ID6+16=22 -> R=1/3 then 90 bits -> rate matching down to 60 bits

Page 724: RANPAR 1

SF256 -> 300 bits /frame -> 5 repeats : 60 bits

Abs grant value 5+ scope 1= 6 -> appended with 16 bits CRC masked with 16 bits ID6+16=22 -> R=1/3 then 90 bits -> rate matching down to 60 bits

Page 725: RANPAR 1
Page 726: RANPAR 1
Page 727: RANPAR 1
Page 728: RANPAR 1
Page 729: RANPAR 1
Page 730: RANPAR 1
Page 731: RANPAR 1
Page 732: RANPAR 1
Page 733: RANPAR 1
Page 734: RANPAR 1
Page 735: RANPAR 1
Page 736: RANPAR 1
Page 737: RANPAR 1
Page 738: RANPAR 1
Page 739: RANPAR 1
Page 740: RANPAR 1
Page 741: RANPAR 1
Page 742: RANPAR 1
Page 743: RANPAR 1
Page 744: RANPAR 1
Page 745: RANPAR 1
Page 746: RANPAR 1
Page 747: RANPAR 1
Page 748: RANPAR 1
Page 749: RANPAR 1
Page 750: RANPAR 1
Page 751: RANPAR 1
Page 752: RANPAR 1
Page 753: RANPAR 1
Page 754: RANPAR 1
Page 755: RANPAR 1
Page 756: RANPAR 1
Page 757: RANPAR 1
Page 758: RANPAR 1
Page 759: RANPAR 1
Page 760: RANPAR 1
Page 761: RANPAR 1
Page 762: RANPAR 1
Page 763: RANPAR 1
Page 764: RANPAR 1
Page 765: RANPAR 1
Page 766: RANPAR 1
Page 767: RANPAR 1
Page 768: RANPAR 1
Page 769: RANPAR 1