hsdpa principles

HSDPA Principles SeminarCorrado Carbone - RO/QoS South

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. Capacity Management4. Accessibility & Mobility Principles7. KPIs

OutlineLets get used with the main concepts of the HSDPA.

HSDPA introduces new technologies in the UMTS world and consequently a new way to manage PS traffic. The most important impacts of it are on:ModulationRetransmission schemesSchedulingUsage of Power and Code

This presentation reports an overview of the main issues to take in mind.

HSDPA Basic Principles

1 - Shared Channel Transmission (1/2)Shared-channel transmission implies that a certain amount of radio resources of a cell (codes and power) is seen as a common resource that is dynamically shared between users.The idea is that a part of the total downlink code resource is dynamically shared between a set of packet-data users, primarily in the time domain. The codes are allocated to a user only when they are actually to be used for transmission, leading to efficient code and power utilization.For P4 only 5 codes (SF = 16) will be available for the HSDPA feature and they will be shared on a time base.

1 - Shared Channel Transmission (2/2)The Shared-channel transmission allows:Higher peak bit rate: all the resource can be allocated to a single user in case of low load.Better application performance being closer to the model TCP has being designed for.More efficient utilization of available code resources compared to the use of a dedicated channel, i.e. reduced risk for code-limited downlink.

The Shared-channel transmission impacts:Scheduling become more complex

2 - Short 2 ms TTI (1/2)The Transmission Time Interval becomes extremely short in HSDPA; 2 ms compared to the 10 ms used by R99 high bit rate radio bearer.The HS channels are organised in sub-frame of 3 slots each; this means that the slot time 2/3 ms/slot is the same as for R99 slots (10/15 ms/slot).The scheduling and the link adaptation algorithms work at this frequency!

2 - Short 2 ms TTI (2/2)The shorter TTI allows:Reduced air-interface delay: this is required by the the TCP at high data rates to Improved end-user performance

The shorter TTI is necessary to benefit from other HSDPA features:Fast Link AdaptationFast hybrid ARQ with soft combiningFast Channel-dependent Scheduling

3 - HSDPA Power AllocationHS-DSCH allocated power is decided by the RNC, prioritizing the DCH channelHS-DSCH adjusts the data rate to match the instantaneous radio conditions and the available transmission power in the RBSNo closed loop power control is specified for HS-DSCH, unlike the DCH channelThe system adjusts the data rate byvarying the effective code ratechanging the modulation schemeThis leads to a higher efficiency in the usage of power.

4 - Fast Link Adaptation (1/3)The target for the link adaptation is to select a TFRC (Transport Format and Resource Combination) resulting in transmitting an as large transport block as possible with a reasonable error probability.

Link AdaptationAvailable PowerChannel ConditionBit RateUE categoryTraffic (buffers state)

4 - Fast Link Adaptation (2/3)Adjust transmission parameters to match instantaneous channel conditionsHSDPA: Adapt on 2 ms TTI basis the Rate (constant power)Adaptive coding Adaptive modulation (QPSK or 16QAM)Link adaptation is implemented by allowing the MAC-hs to set the TFRC (Transport Format and Resource Combination) independently for each 2 ms HS-DSCH TTI

High data rateLow data ratefeedback

4 - Fast Link Adaptation (3/3)

In order to estimate current channel conditions, an estimate of the Channel Quality is reported by the UE to RBS (CQI). Based on the channel conditions and the available power, the network will select the Transport Format to have the maximum throughput achievableHigh data rateLow data ratefeedback

5 - Fast Channel-dependent Scheduling (1/2)Scheduling =which UE to transmit to at a given time instant

There is a main tradeoff to choose between: fairness vs. cell throughputEvery user has the same rights to access the resourceThe user with better radio condition transmit moreUser1User2User3User4time2 ms2 ms

5 - Fast Channel-dependent Scheduling (1/2)2 opposite strategies are: Round Robin: radio resources are allocated to communication links on a sequential basis.Proportional Fair: transmit at fading peaks. This may lead to large variations in data rate between users.

6 - Fast Hybrid ARQ with Soft Combining (1/2)HSDPA introduces a new retransmission level under the RLC scheme in the RNC.This new level allows rapid retransmissions of erroneous data:Hybrid ARQ protocol terminated in RBS short RTT (typical example: 12 ms)Soft combining in UE of multiple transmission attempts reduced error rates for retransmissionsP1,1P1,1NACKP1,2P1,2ACKP2,1P2,1NACKP2,2P2,2ACKP3,1ACKP1,1P2,1P3,1++

6 - Fast Hybrid ARQ with Soft Combining (2/2)A fundamental difference between conventional ARQ (used in RLC) and HARQ is that: in the latter case received data blocks that cannot be correctly decoded are not discarded but buffered They are soft combined with later received retransmissions of the same set of information bits. Finally, decoding is applied to the combined signal.

7 - UE capabilitiesThe UE capabilities are divided into a number of parameters:Total RLC AM and MAC-hs buffer sizeMaximum number of HS-DSCH transport channel bits received within a HS-DSCH TTISupport of HS-PDSCH Yes/NoMaximum number of HS-DSCH codes receivedTotal number of soft channel bits in HS-DSCHMinimum inter-TTI interval in HS-DSCHSupporting 16QAMThese physical layer UE capabilities can be translated in a limit on the requirements for 3 different UE resources: the de-spreading resource (codes decoded in parallel)the soft buffer memory used by the hybrid ARQ functionalitythe turbo decoding speed (the maximum number of transport channel bits received within an HS-DSCH TTI and the minimum inter-TTI interval).

Throughput level: UE type cat 12There are several levels for throughput calculation: lets clarify!The biggest MAC-HS transport block size is 3440 including HS header and padding bits:X 10 =++= 3440 bitsRLC SDU = 320RLChead = 16MAC- HS SDU head = 3360MAC- HS head = 21Padding bits = 59That means the DSCH max scheduled bit rate could be 1720 kb/s: That is including headers, padding and every type of retransmissionThis is the level used by the RBS counters and Couei!

This corresponds to a max RAB bit rate of 1600 kb/s =320*10/2

In reality considering at least the HS retransmissions at this level the maximum bit rate could not be higher than 1600*0.9 =1440 bit/s

Protocol stacks (1/4)UERBSSRNCPHYAAL2 ATMFPMAC-hsL1RLCUser DataPHYPHYAAL2 ATMAAL5 ATMGTP-U UDP/IPFPRLCMACCNPHYAAL5 ATMGTP-U UDP/IPUser DataUuIubIuThe figure shows the R99 protocol stack.Note in particular that MAC is a protocol between the RNC and the UE

MACL1

Protocol stacks (2/4)UERBSSRNCPHYL1AAL2 ATMMAC-hsHS-DSCH FPMAC-dMAC-hsL1RLCUser DataPHYPHYAAL2 ATMAAL5 ATMGTP-U UDP/IPHS-DSCH FPRLCMAC-dCNPHYAAL5 ATMGTP-U UDP/IPUser DataUuIubIuThe new radio interface layer 2 functionality required by the HS-DSCH (hybrid ARQ signaling, scheduling, etc) was placed in a new functional entity of the MAC layer, called MAC-hs. The physical layer was updated with new functionalities for HS-DSCH (soft combining of retransmitted transport blocks, new physical channels, etc.).

Protocol stacks (3/4)UERBSSRNCPHYL1AAL2 ATMMAC-hsHS-DSCH FPMAC-dMAC-hsL1RLCRRCPHYPHYAAL2 ATMAAL5 ATMGTP-U UDP/IPHS-DSCH FPRLCMAC-dCNPHYAAL5 ATMGTP-U UDP/IPRRCUuIubIuA new user-plane frame-handling protocol (UP FP) between the SRNC, DRNC and Node B needed to be developed for the radio network layer (RNL). It was based on the release 99 DSCH UP FP used over Iur.The layer 3 control-plane protocols (RRC, RNSAP and NBAP) needed to be updated with control procedures, handling HS-DSCH.

Protocol stacks (4/4)UERBSSRNCPHYL1AAL2 ATMMAC-hsHS-DSCH FPMAC-dMAC-hsL1RLCTCP/IPPHYPHYAAL2 ATMAAL5 ATMGTP-U UDP/IPHS-DSCH FPRLCMAC-dCNPHYAAL5 ATMGTP-U UDP/IPTCP/IPUuIubIuNote that RLC does not have significant impactWhen the HS-DSCH transport channel is used with AM RLC, it is expected that RLC re-transmissions will be required only in rare circumstances where the inner hybrid ARQ fails. E.g. in handover situations, the transmit and receive buffers in the MAC-hs layer may need to be re-initialized. This may cause data loss, which would be taken care of by RLC retransmission.

General impacts of the new architectureThere will be impacts on the buffer capabilitiesfor data in the RBS a new buffer is needed to store data of different usersThe mobile has to store erroneous PDU for Soft Combining Requirements on buffer could be different due to the new amount of transmitted dataAlgorithms have to be adapted:Admission and Congestion Control for example need new way to estimate the load and accept new users.Closed loop power control does not apply to HS.New algorithms that manage the new functionalities have to be introduced (buffer, scheduling).Mobility algorithm in particular is conditioned since the fast link adaptation does not allow the Soft Handover anymore.The e2e performance of the PS users significantly improves due to a smaller RTT.

HSDPA Basics: Node ImpactsRBSNew TX board in RBS

RNCNo HW upgradesOnly SW!!Setup of HS-DSCH/HS-SCCHR99: Scheduling, TF selection, Link layer retransmission (ARQ)Core NetworkRNCNode BHSDPA: Scheduling, Link Adaptation, Hybrid ARQ

Node Functionality

HSDPA new channelsHSDPA introduces specific channels, 1transport and 3 physical channels:The transport channel High Speed Downlink Shared Channel (HS-DSCH) is a resource existing only in downlink and carries user data in HSDPA.The High Speed Physical Downlink Shared Channel (HS-PDSCH) is a downlink physical channel, to which the HS-DSCH channels are mapped.The High-Speed Shared Control Channels (HS-SCCH) is used for downlink control signaling and carries indication about UE scheduling. One Associated Dedicated Channel (A-DCH) pair (UL & DL) per HSDPA user in connected state, used for control signaling and uplink data transmission. The uplink control information is carried by the Uplink High Speed Dedicated Physical Control Channel (HS-DPCCH).

Channel StructureControl ChannelHS-PDSCH High-Speed Physical Downlink Shared Channel (Physical)HS-DPCCH High-Speed (related uplink) Dedicated Physical Control Channel (Physical)A-DCH Associated Dedicated Channel A-DCH (Transport)HS-SCCH High-Speed Shared Control Channel(s) (Physical)HS-DSCH High-Speed Downlink Shared Channel (Transport)

An overview of HS-DSCH and its associated channels CN RNC RBS UE - User 1 User 2 User n Radio Access Bearers: - Interactive - Background Logical Channels:-Dedicated Control Channel, DCCH-Dedicated Traffic Channel, DTCHTransport Channels:-Dedicated Channel, DCH-High-Speed Downlink Shared Channel, HS-DSCH

Physical Channels:-Dedicated Physical Channel, DPCH -DPCCH, Dedicated Physical Control Channel-DPDCH, Dedicated Physical Data Channel-HS-DPCCH, HS-DSCH Dedicated Physical Control Channel-HS-DSCH Shared Control Channel, HS-SCCH-High Speed Physical Downlink Shared Channel, HS-PDSCHIuIubUu

HS-DSCH : High-Speed Dedicated Shared ChannelHS-DSCH is the transport channel used for data transmission on the downlink and is shared by all users in the cell. In the HSDPA first phase product release:the sharing of code resource is done in the time domain on a 2 ms time basis (TTI). The shared code resource consists of 5 channelization codes with fixed spreading factor SFHS-DSCH = 16, in this time frame.The HS-DSCH cannot be in soft/softer handover and no fast power control is used. The HS-DSCH uses all the excess power from the available transmission power at the base station left from the common and dedicated channels

HS-SCCH: High-Speed Shared Control ChannelHS-SCCH is a downlink physical channel used to carry HS-DSCH related control signaling (Physical Layer signaling). It is shared among the HSDPA users on time division basis (TTI), with the same scheduling as for HS-DSCH.All UEs listen to the same HS-SCCH channel and after decoding, decide whether the information to start listening the HS-PDSCH was intended to that UE. Informs the UE about:HS-DSCH code setModulation scheme (QPSK/16QAM)HS-DSCH transport format (number of transport blocks per TTI and number of bits per transport block)Hybrid ARQ informationNever in soft handoverThe HS-SCCH has a spreading factor SFHS-DSCH = 128

A-DCH: Associated Dedicated Channel One A-DCH pair is set up for every HSDPA user in connected state. It is used for control signaling (RRC and NAS) in UL and DL.It is a new Radio Bearer corresponding to a 3.4 kbps SRB in the DL (Sf 256). In the uplink A-DCH is also used as the channel for data transmission, where the rate can be either 384 kbps or 64 kbps. The uplink data rate 384 kbps is selected as first priority and 64 kbps is used as a fall back rate if the path loss is judged to be too large or 384 kbps radio bearer setup fails for any reason (e.g. lack of radio or hardware resources).The uplink A-DCH channel also contains the High-Speed Dedicated Physical Control Channel (HS-DPCCH), the new physical channel that carries the L1 related signaling in UL.

HS-DPCCH: High-Speed Dedicated Physical Control ChannelIt is used for transmitting the following information from UE to RBS:HARQ acknowledgement (1 bit coded in 10)Channel quality indicator (5 bits coded to 20 bits in 2 slots)channel quality measurements based on CPICHreporting rate is configurable through RRC/NBAP signalinginformation reflecting the instantaneous downlink radio channel conditions to assist the RBS in the transport format selection (fast link adaptation) and the scheduling The HS-DPCCH has a spreading factor SFHS-DSCH = 256The A-DCH both UL and DL can be in soft/softer handover whilst the HS-DPCCH can never be in soft handover (softer is possible). HS-DPCCH (UL) is transmitted within a dedicated channel. The main idea is that it is power controlled from the other part of the A-DCH.

HSDPA Channel Operation HS-DPCCH: CQIHS-SCCH: DL Transfer InformationHS-DSCH: Data TransferHS-DPCCH: ACK/NACKPhysical Channels:-Dedicated Physical Channel, DPCH -DPCCH, Dedicated Physical Control Channel-DPDCH, Dedicated Physical Data Channel-HS-DPCCH, HS-DSCH Dedicated Physical Control Channel-HS-DSCH Shared Control Channel, HS-SCCH-High Speed Physical Downlink Shared Channel, HS-PDSCH

UserPlane: OverviewThere are 8 steps to transmit on the HS-DSCH:In the RNC, the Interactive RAB is mapped to a radio bearer to be transmitted on the HS-DSCH. The radio bearer is then processed by the RLC and MAC-d layer 2 protocols in the RNC. The resulting MAC-d PDUs are transmitted over Iub to the RBS using the HS-DSCH frame protocol. The MAChs receive the Channel Quality Indicator adjusted by the Node BThe MAC-hs scheduling function selects in each TTI the user to which the HS-DSCH is transmitted. Following the selection of a user, the user data to transmit on the HS-DSCH is put into one of several HARQ processes in the MAC-hs HARQ protocol. The amount of data to transmit is determined by the TFRC selection algorithm. Hence the data is transmitted to the UE over the air interface.

RAB/RB Combination OverviewInteractive and background Packet ServiceNew RABs defined:Interactive PS 64/HSPS 384/HS (optional)DL bit rate up to 4.32 Mbps in P4 (user data rate)About HS-DSCH:Max. 5 codesDL: QPSK orDL: 16QAM (optional)UL 64 kbps interactive radio bearerSupported by symmetric 3.4 kbps signaling radio bearer (SRB)

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. Capacity Management4. Accessibility & Mobility Principles7. KPIsAccessibility:Call setup phases

Radio network functionsf2 HSRNCRNCIurIubIubIuIuAssociated Dedicated ChannelsHS-DSCHHS-SCCHHS-DPCCHIubf1f1f2 HSf2 HSf1f1f1f11Camping in idle1Access the HSDPA system223Move within the system34Move out of the system4Control the power55Decide which mobile and how much to transmit to it 66RRM policy77

State Diagram non HSDPA-P4

State Diagram only HSDPA

The diagram is clearly much easier. What does it means?Few transitions

Only 2 HS RABs existThe choice between 64 or 384 is done at the beginning and cannot be changed during the connection.

Idle mode & RRC Connection EstablishmentIn idle mode there is no difference between a user with HSDPA capability or not.The UEs select the the cell with best Ec/N0 with the procedure cell reselection as in R99. In second carrier sites, HSDPA is deployed in the second carrier onlyMost idle UEs will camp on f1Most HS users must be moved to f2 in order to get the HS serviceThere is no difference in the RRC Connection Establishment procedure between a user with HSDPA capability or notRRC Connection Request and Radio Connection Setup Complete contains information about the UE capabilityf1f1f1f2 HSf2 HSf2 HSHS+ f1HS+f1Ec/Nof1f2

RAB establishment UTRAN RANAP: RAB Assignment Request (establish PS Interactive/Background RAB) Radio Bearer setup RANAP: RAB Assignment Response Serving HS-DSCH cell selection SGSN UE HSDPA capability analysis SRB - DCH Possible Inter frequency hard handover 12340

Capability analysisAt the reception of RANAP RAB Assignment Request, if:the present UE state is SRB-DCH and if the RAB mapping gives as result PS interactive or PS background the Access stratum release indicator received from UE indicates Rel-5 or later release, the Physical channel capability received from UE indicates that the UE supports FDD HS-PDSCH (any HS-DSCH-physical-layer-category shall be supported), if the existing UE capability check for L2 are successful

1Otherwise the RAB is established in design base system.

Serving HS-DSCH cell selectionWhen, at RAB establishment, the UE starts the procedure 3 results are possible:

If the HS-DSCH is enabled in the best cell, the connection is set up in that cell. Otherwise the RNC check the coverage relation of the best cell.

If the HS-DSCH is enabled in the target cell, an hard handover is tried to the new selected cell.

If no cells are available and the connection is established on an interactive DCH. Current active setNew active setDCH2

Coverage relationsThe coverage relation is a unique uni-directional relation between two cells, a source and a target cell. The purpose of the coverage relation is to give the operator a possibility to distribute HSDPA downlink traffic among the cells of an RNC. The target cell covers almost the same area and can be assigned the same frequency or different ones. Typically the cells will be co-located.

A coverage relation is defined for a source cell with the parameters (3GPP R5 25.423):hsPathLossThreshold utranCellRef (the target cell) coverageIndicator2

Two Carriers scenario: IF HOIn case the HSDPA is deployed on a second layer and the mobile access the network from the first layer the step will be the following:f2 HSf1f2 HSf2 HSf1f1f1f1Start the RAB establishment and the Cell Selection procedure..When the attempt on the AS cells fails, check the coverage relation of the best cell and its path loss 2nd carrier1st carrier3

Interfrequency load distribution

It adds the possibility to configure a "load-sharing margin" which can be used to reserve output power, for e.g. HSDPA traffic, in selected cellsIt makes the cell appear more loaded than it actually isIt can be used to push traffic on a specific carrier

RB setup (1/2)If the result from the Serving HS-DSCH cell selection gives that a Serving HS-DSCH cell is selected-> the RB setup, SRB-DCH to PS interactive (64 or 384)/HS - HS-DSCH transition is performedIf the result gives that no Serving HS-DSCH cell is selected, but UE connection is still maintained-> the RAB establishment is performed as in the design base.

4

12. RRC: Radio Bearer Setup Complete

8. Iub and Iur Transport Bearer setup, AAL2 Connection setup

1. Admission request

7. NBAP: Radio Link Reconfiguration Ready

RBS

4. RNSAP: Radio Link Reconfiguration Prepare

9. NBAP: Radio Link Reconfiguration Commit

2. Allocate resources

9. NBAP: Radio Link Reconfiguration Commit

11. Perform actions at Activation time

DRNC


DRNC

10. RRC: Radio Bearer Setup R5

9. Set Activation time

SRNC

13. Release resources

UE

9.RNSAP: Radio Link Reconfiguration Commit


6. NBAP: Radio Link Reconfiguration Ready

6. RNSAP: Radio Link Reconfiguration Ready

4. NBAP: Radio Link Reconfiguration Prepare

3. NBAP: Radio Link Reconfiguration Prepare

4. Admission request


RBS

RB setup (2/2)Different levels of Admission control runs in the RNCFor the selected serving HS-DSCH cell, run Admission Control algorithm for the A-DCH configuration and for HS-DSCH configuration (number of serving links). For the other cells within SRNC, run Admission Control algorithm for the A-DCH configuration. The RANAP RAB Assignment Response is sent to the CN when the Radio Bearer Setup Complete has been received. The handling of UL/DL user data on RLC level is done as in the R99 for PS interactive RB. 4

UL: 64 or 384?Which UL A-DCH to set is decided during the AC phase.From an AC point of view, there are 2 guaranteed-hs service types:PS64/HS Interactive PS service with rate 64 kbps in uplink and HS-DSCH using up to 5 HS-PDSCH codes in downlink. PS384/HS Interactive PS service with rate 384 kbps in uplink and HS-DSCH using up to 5 HS-PDSCH codes in downlink.A part from the other AC check there are 2 special checks for the UL A-DCH:Histogram Admission Policy: requests demanding spreading factor 4 in uplink (PS384/HS radio connection type) are compared with sf4AdmUl.The path loss is checked in order to understand if a 384 UL bearer can be sustained.If the 384 RB is denied (or is accepted but the RBS dont find the synchronization in the establishment phase) the connection is established on the 64 RB.4

Release of Iu-PS connection due to inactivity in HS-DSCH state (1/2)When a user finishes its transmission has to release the resources.The procedure is really simple:An "HS-DSCH inactivity" timer is started when there is no data to transmit.When the timer expires a Iu Release request is sent and the resources are released.The value of the timer is a system parameter hsdschInactivityTimer

Please note that..No Channel Switching, cell_DCH -> Idle:No cell_FACH for HS users.No soft switch between HSDPA and DCHNo transition between the UL rate is possibleThe UE can regulate its rate in UL depending on the cell interference level. Hence a 384 RB in UL has to be considered as the maximum bit rate.

SRB-DCH Idle

HS-DSCH(uplink 64 or 384)

RAB Combinations:Interactive 64/HS kbps PS RAB UL: Interactive 64 kbps PS RB + 3.4 kbps SRBs on DPCHDL: Interactive PS RB on HS-PDSCH + 3.4 kbps SRBs on DPCHInteractive 384/HS kbps PSUL: Interactive 384 kbps PS RB + 3.4 kbps SRBs on DPCHDL: Interactive PS RB on HS-PDSCH + 3.4 kbps SRBs on DPCH

Incoming CS callA critical issue for the HSDPA in P4 is the management of the incoming call.Subsequent RAB assignments are rejected by RNC no multi RABs

Please note that..If the current PS Interactive RB is allocated HS-DSCH resources, the RAB Assignment response includes the unmapped RAB IDs in the RABs failed to setup or modify IE.

2. RANAP: RAB Assignment Response

SGSN

UE

PS Interactive 64/HS - HS-DSCH

UTRAN

MSC

1. RANAP: RAB Assignment Request (CS RAB)

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. Capacity Management4. Accessibility & Mobility Principles7. KPIsMobility:Intra-HSDPA

HSDPA Mobility: introduction (1/3)After the cell selection, the network has to guarantee the mobility of the HSDPA usersSince No Soft/Softer HO exist for HS-DSCH, there will be only one serving cell for the HS-DSCH.

2 algorithms are interested in the mobility of HSDPA users in connected mode:Serving HS-DSCH Cell ChangeA-DCH Soft/Softer HO

HSDPA Mobility: introduction (2/3)The HSDPA mobility will be splitted here in different issues:Measurement reporting handlingHandover for A-DCHServing HSDPA cell change

HSDPA Mobility: introduction (3/3)Note that when the UE is PS Interactive using HSDPA, the MEASUREMENT CONTROL includes only neighbor cells of type intra-frequency and no Compressed Mode is triggered, that means that Inter-Frequency and Inter-RAT Handover are not possible to be performedWhat happens when the mobile move to area without HSDPA coverage?

Measurement reporting (1/2)While user moves in the network, it continues to perfom measurement on the CPICH of the detected cells.When a UE is setup on a dedicated channel:

the SRNC sends a MEASUREMENT CONTROL (some information are broadcasted in the system information on the BCCH channel) orders the UE to start Intra frequency measurement.As soon as the triggering conditions are fullfilled, the UE sends a MEASUREMENT REPORT message to the SRNC indicating which event occurred and which among the measured cells fulfilled the event criteria.

Measurement reporting4 types of intra-frequency measurements are defined in the 3GPP:Event 1a: Add cell - A primary CPICH enters the reporting rangeEvent 1b: Delete cell - A primary CPICH leaves the reporting rangeEvent 1c: Replace cell - A Non-active primary CPICH becomes better than an active primary CPICHEvent 1d: Change of best cell - A primary CPICH becomes better than the previously best primary CPICH Event 1e: A primary CPICH becomes better than an absolute threshold Event 1f: A primary CPICH becomes worse than an absolute threshold

Note that the RNC can configure more than 1 measurement report for the same event.

Mobility Example051015-20-15-10-50time [s]Ec/N0 [dB]cell 1cell 2cell 3event 1d: Change of best cell, to cell 3Active set handling: (Max active set = 3)event 1a: Add cell 2, to the ASAdd cell 3, to the ASevent 1b: Delete cell2213

Measurement reporting for HSDPAWhen PS Interactive using HSDPA is started, an extra MEASUREMENT CONTROL related only to the event 1d HS , is sent to the UE having another MEASUREMENT ID than the ones dealing with the conventional event 1d for Soft Handover evaluation. The reason for having a separate event 1d HS isto be able to get UE reports triggered by only Active Set cells to be able to use different hysteresis and time to trigger parameters to trigger HS-DSCH Cell Change.to use a different quality criteria (RSCP of the cells in the Active Set)Since the 1d Hs reported cell is already a member of the current Active Set, this event do not trigger any change in the AS.

A-DCH handoverIn the previous slide it is stated that there will be only one serving cell for the HS-DSCH. This does not mean that the UE is connected to only one cell.For what concerns the A-DCH they continue to perfrom soft and softer hand-over as in normal R99 case.Note that HS-DPCCH can be only in softer HO.In the example supposing the best server does not change... R99R99R99 HSHSHS HSHSHS HSHS-DSCHA-DCH

Serving HSDPA Cell Change (1/2)When the UE moves between cells, the HSDPA connection is maintained by means of intra frequency serving HS-DSCH Cell Change. HS-DSCH Cell Change evaluation performs the evaluation of a valid target cell within the current Active Set, only towards a suitable HS-DSCH cells.A suitable HS-DSCH Cell is a cell that satisfies the following conditions: Cell in the current Active Set. Internal UTRAN cell. Cell having HS-DSCH enabled.

Serving HSDPA Cell Change (2/2)Serving HS-DSCH cell change is triggered by:Change of Best cell as indicated by receiving an event 1d, UE measurement reportRemoval of the Serving HS-DSCH cell from the active set due to receiving an event 1b, UE measurement report.Removal of the Serving HS-DSCH cell from the active set due to receiving an event 1c, UE measurement report.any other reason where the current serving HS-DSCH cell is to be removed from the active set. No support for HS-DSCH over Iur: RRC Directed Signaling Connection Re-establishment

Soft/softer HO for A-DCH and cell change for HSDPA channelsMeasurement quantitytimeP_CPICH 1Reporting event 1d-hsP_CPICH 2Reporting event 1aRep. Range 1aRep. Range 1bReporting event 1bNote, there is of course a time-to-trigger also for event 1d-hs

Serving HSDPA Cell ChangeIf a suitable HS-DSCH cell can not be found within the current RNS a RRC connection release is triggered. After this a new cell selection can follow:Another connection establishment with a new Cell selectionnormal connection establishment on R99A connection establishment on GSM

R99f2 HSHSHSf2 HSf1 HSf1 HSR99R99f2 HSf2 HSf2 HSf2 HSHSHSEx1Ex 2Ex 5f2 HSf1 HSf1 HSCell SelectionCell SelectionRNCRNCf2 HSR99R99f2 HSf2 HSR99R99R99R99Ex3R99R99R99R99R99R99f2 HSHSHSf2 HSf2 HSf2 HSGSMGSMGSMGSMGSMGSMEx 4

Radio Connection SupervisionSeparate parameter hsdschRcLostT determines how long time a HS user can be out-of-sync before the connection is releasedFor HS users only the RL in the serving HS-DSCH cell is supervised.Sync status may change at serving HS-DSCH cell changeWhatever casef2 HSf2 HSf2 HSGSMGSMGSMGSMGSMGSMRadio Connection supervision is the algorithm monitoring the synchronization of a mobile, that is, if the mobile is still connected or not.

Carrier mobilityA user conected with a UMTS network on a certain carrier can move out of the its layer coverage. There are 2 mechanisms to avoid the drop, at least for some services:

Inter-RAT HandoverInter-Frequency Handover

f2 HSHS-SCCHf1f1f2 HSf2 HSf1f1f1f1GSMGSMGSMGSMGSMGSMGSMGSMGSMGSMGSMGSMMost of the time anyway the passage between carriers happens in idle mode

IRAT/IF Handover in five steps(IRAT HO in the example)UTRANCore NetworkGSM/Other Carrier

IF&IRAT Handover: basic

Main stepsWhen the quality of the connection overcomes a certain thresholds (event 2d or 6a) UE reports a Measurement report and the network orders the UE to activate the CM and check the other layer.If the connection quality further degrades and the other layer has a quality high enough the HO is triggered (events 3a and 2b).If the connection quality turns out to be good, the UE signals it to the network and the mobile stops the CM (events 2f or 6b).

IRAT & IFHO procedures

The evaluation process for HO execution depends on the quantity that started measurements (CPM) among:CPICH RSCPCPICH Ec/IoUE TX powerAt the same time, the cell in the target layer should have the quality good enough. That means:For GSM: the quality of the measured GSM cells is above a gsmThresh3a. For the second UMTS layer: the measured best cell on unused frequency is above both the thresholds nonUsedFreqThresh4_2bEcno and nonUsedFreqThresh4_2bRscpBoth of the HO are hard HO:This means that there will be small interruptions in the data flow to and from the UE. Evaluated In parallel

Initial CellTarget LayerCPICH Ec/NoOther layer good enoughCPM start and HO trigger

IRAT HO and Cell ChangeUntil here, concerning 3G to 2G switch, only IRAT HO has been mentioned. Anyway when the UE is in connected mode with a PS RAB, the switching procedure to 2G is called IRAT Cell Change.

Compared to IRAT HO:

There is no difference in the evaluation procedure.In the Inter-RAT Cell Change case there are no resources reserved in the target cell before the Inter-RAT Cell Change is executed.There is significant outage period and a certain number of lost packets when moving toward 2G that have to be carefully evaluated (If the Inter-RAT Cell Change is evaluated and executed by the UE in Idle mode or connected mode on common channels it is denoted Cell Reselection or Inter-RAT Cell Reselection, see Idle Mode and Common Channel Behaviour for more details)

IF or IRAT?A decision has to be made to evaluate either Inter-Frequency handover or Inter-RAT Handover/Cell Change. This decision is based on parameters on RNC level, cell level, and UeRc state.

Inter-Frequency handover is only attempted if C_IfHoAllowed is set to Allowed for the current UeRc state, and FddIfHoSupp (RNC) is set to On .Inter-RAT handover is only attempted if C_GsmHoAllowed is set to Allowed for the current UeRc state, and FddGsmHoSupp (RNC) is set to On.If both the conditions are verified the decision is based on a configurable parameter, hoType (cell), defined per cell (IFHO preferred, GSM preferred, None).

Hence, for a certain cell only one of the 2 Handover types will be allowed.

Where?

CIPICH dimensioningDimensioning exampleCPICH power = 0.87 WIn the dimensioning process the power found with CPICH is done in order to guarantee an adeguate CPICH level (Ec/N0 > -16) within the cell area (Range = 1.17 km). Does that mean that the boundary of a UMTS cell corresponds to CIPICH_EC/N0 = -16?

Which is the real area of a UMTS cell?When a GSM network or a second carrier is deployed the question is not easy to be answered.Only looking at the Ec/N0 suggested threshold for IF/IRAT HO we note that:usedFreqThresh2dEcno = -12utranRelThresh3aEcno = -1 (relative to 2d thr.) = -13

Different terminals have different behaviours.

The load changes the cell border.

Impact on coverageWCDMA RBS

Notes for HSDPAHSDPA users, when in connected mode with a HSDSCH: will not be allowed to perform IF and IRAT HO.will not experience CM. Anyway:they can experiment it when in connected mode with a R99 RAB or in other dedicated connection.They can impact on other users behaviorDont forget idle mode!Users change carrier or network even in idle mode and the coprresponding parameters have to be carefully tuned as well.

IRAT Cell ReselectionOverall description of thresholds

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. Capacity Management4. Accessibility & Mobility Principles7. KPIsCapacity ManagementAlgorithm

Capacity Management (Overview)Capacity Management solution controls the load in the WCDMA cells.It includes 3 main algorithms:

Admission Control controls the utilization of dedicated monitored resources by accepting or refusing requests for utilization of these resources

Congestion Control detects overload situations on some dedicated monitored resources and initiates congestion resolve actions to decrease the load

Dedicated Monitored Resource Handling gathers and provides information about the current usage of critical resources

Dedicated ResourcesThe Dedicated Monitored Resource Handling function collects and provides information about the current usage of resources that are critical to the load of the cell. There are three reasons for blocking:

RF POWER:

the total transmitted carrier power is constantly monitored by the algorithm. When the value exceeds some configurable thresholds the admission/congestion take decisions for guaranteed and non-guaranteed service class connections

CODE Code Usage: the total number of codes is monitored.

Code Hystogram: the number of codes used for each SF are monitored. The max number of code for each SF is configurable. A control is also done on the maximum number of compressed mode connections

ASE (Air-Speech Equivalent):This monitor is based on the estimation of the air-interface usage per radio link type (RB type) in a cell. Thresholds can be defined separately for the uplink and downlink, for guaranteed or non-guaranteed connections

Admission Control AlgorithmRequests arrive to the AC at several moments: Radio Link Setup Radio Link Addition Radio Link Reconfiguration Compressed Mode CommandDifferent thresholds exist for different types of request: (g,ho) guaranteed, handover (g,nho) guaranteed, non-handover (ng,ho) non-guaranteed, handover (ng,nho) non-guaranteed, non-handoverThe AC accepts requests until a certain threshold on a monitored resource (power in this case) is reached.Downlink Transmitted Carrier Power Monitor (for Admission purpose)35%75%85%default values

Congestion Control AlgorithmThe congestion control has an unique threshold for all the service types (pwrAdm+ pwrAdmOffset +pwrOffset) to regard the cell as congested.The action to decrease the load in the cell considers instead the different priorities of the services.

Downlink Transmitted Carrier Power Monitor (for Congestion control)Default values:pwrOffset = +5% 90%pwrHyst = 600 ms

Traffic AlgorithmsThe PS traffic (non-guaranteed) is managed by the RRM algorithms with a lower priority at several levels:Lower threshold on ACFirst user to be considered for Congestion actionsBesides RRM algorithms, even the Channel Switching algorithm acts to control the PS traffic.

HSDPA Monitored Resource HandlingThe way of measuring the resources has to be adapted to the HSDPA:

The monitored power in the RNC keeps track only of the usage of total non-HS downlink transmitted carrier power. The reports of the power measurements are adapted to the capability of a cell:HSDPA capable Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmissionHSDPA not capable Transmitted carrier power

2 new dedicated monitored resource is introduced: the number of HS-serving links in a cell.The usage of SF 4 in uplink (the usage of the optional PS384/HS radio connection type)

The measurement of code tree utilization considers the codes allocated for HS-PDSCH and HS-SCCH channels.

HSDPA Admission Control AlgorithmThe AC receives requests from a HS users in 2 moments:

At RAB establishment; in particular after the serving HS-DSCH cell selection.For mobility, e.g. A Radio link Addition for A-DCH handover

No AC is performed within a Cell Change procedure

Note that there are neither Compressed Mode requests nor Radio Link Reconfiguration

f2 HSRNCIurIubIuAssociated Dedicated ChannelsHS-DSCHHS-SCCHHS-DPCCHf HSf2 HSR99R99R991AC

HSDPA Admission Control AlgorithmThe AC performs several types of check:

A-DCH:Total available codes (for A-DCH only).ASE (for A-DCH only).Power (for A-DCH) Code with SF=4 in UL (for A-DCH PS 384 in UL)(Hardware, new in P4)

HS-DSCH:Number of HS-serving links (for RAB set up only)

HSDPA - Code ControlThere is no check on HSDSCH and HSSCCH codes done by the AC.The operator configure and reserve the number of HS-PDSCH codes allocated in a cell for HSDPA (numHsPdschCodes)Increase lock of the cell and release of trafficDecrease no effect on ongoing traffic The number of HS-SCCH (SF=128) codes is one

16

8

4

2

1

DedicatedChannels

SF

Common Channels;HS-SCCH

HS-PDSCH

(default)

HSDPA Number of HS usersThe operator can limit the number of users that can be allocated to the HS-DSCH cell (hsdpaUsersAdm)

This limit enables the users allocated to the HS-DSCH (shared channel) to experience a sufficient end-to-end quality

The new policy is only applied to requests for new HSDPA connectionshsdpaUsersAdm

HSDPA UL Histogram ACThe operator can set a limit for the guaranteed-hs admission requests demanding spreading factor 4 in uplink that can be accepted (in cells where the PS384/HS is activated)

The threshold is set according to the parameter sf4AdmUl

This policy allows the operator to disable the PS384/HS feature on a cell basis

sf4AdmUl can be reduced if the uplink is experienced as problematic, for example due to high Received Total Wideband Power or transport network problems

New service class, guaranteed-hs, assigned to the A-DCHsHighest priority for guaranteed-hs service class in admission decisions to enable HSDPA users to use the excess power in high loaded (non-congested) cellsSoft congestion is not affected by the introduction of HSDPA HSDPA DL Power Admission

HSDPA Link Power AdmissionWhile the admission control on a session level is performed by the RNC, it is important to take in mind that the RBS control the HS access to the shared resources.Common channelsDedicated channelsTotal available cell power

HSDPA - Congestion ControlTimePowerCongestion threshold

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. Capacity Management4. Accessibility & Mobility Principles7. KPIsLoad Sharing Techniques

Load Sharing (1/2)Load sharing features pool together resources from different parts of the entire network.2 load-sharing features are available in the WCDMA RAN: Inter-Frequency Load Sharing Directed Retry to GSMBoth load-sharing features redirect calls during the connection setup phase:RRC connection setup for IF load SharingRAB setup for Directed retry

Both IF HO and Directed retry will be present at the same time but IF will act first!

Load Sharing (2/2)For load sharing purposes, cell load is defined as the ratio between the downlink transmitted carrier power and the admission limit, as given by the cell parameter pwrAdm. The load sharing algorithm acts only when the load of a cell overcomes a certain threshold:For IF, the threshold is set to 50%For directed retry both the threshold and the percentage of users to be redirected can be tuned TimeCell LoadDR

thrTimeCell LoadIF

50%Cell Load = Tx_power/PwrAdmFor HSDPA cells, only the non-HSDPA part is counted

Directed Retry algorithmSpeech call (without packet connection) is the only service that is targeted since it is also the only one that is safe to divert to GSMDirected Retry is performed during the RAB establishment procedure; the first request will be rejected with cause "Directed retrya request is made to the core network to relocate the UE to a specific GSM cell, using the Inter-RAT handover procedure. This handover is a blind HO since the target cell is chosen not based on UE measurements. Therefore, the target cell must be co-located with the WCDMA cell.

There are 2 control parameters:loadSharingGsmThreshold specifies the minimum cell load at which off-loading to GSM begins. loadSharingGsmFraction specifies the percentage of Directed Retry candidates to be diverted to GSMTimeCell LoadDR

loadSharingGsmThreshold

Inter-Frequency Load Sharing (1/2)UMTS L2UMTS L1GSMIf the target cell is less loaded, the UE will not be instructed directly to go to the target cell but it will be told to scan for a suitable cell in the frequency of the target cell, by sending an RRC Connection Reject message.

33The mobile starts a RRC connection establishment procedure ( NO distinction in RRC cause is made)112If the cell load is higher than 50%, the load of the co-located load-sharing neighbor is compared with the accessed cell and the least loaded cell is chosen as target.250%

Free Resource = R[2]Power/pwrAdm33%L[2] = 33% -- L[1] = 60%L[1] - 20% > L[2] Select Second Carrier100%loadSharingThreshold (20%)DL power in use100%Free ResourcePower/pwrAdm60%To minimize excessive load sharing a hysteresis is used in the comparison, loadSharingThreshold. IF Load SharingHere an example of comparison between 2 different frequency is reported.LoadCell 2LoadCell 1> = < ?

HSDPA IF Load SharingSecond CarrierLoadCell 2LoadCell 1> = < ?50%loadSharingMargin is a cell-specific parameter that specifies the amount of resource excluded from load-sharing use (as a percentage of pwrAdm). When loadSharingMargin is greater than 0, the cell appears to be more loaded than it really is, resulting in more traffic being directed away from itThis parameter gives the operator the possibility to reserve a higher priority to the HSDPA users on the second carriers (in case this is deployed and HSDPA is introduced there)Free Resource = R[2]Power/pwrAdm33%100%loadSharingThreshold (20%)L[2] = 33% + 10% -- L[1] = 60%L[1] - 20% < L[2] 40% < 43%Stay on the First CarrierDL power in use100%Free ResourcePower/pwrAdm60%loadSharingMargin (10%)

Inter-Frequency Load SharingApart from the load sharing algorithm, other aspects have to be managed and tuned with the introduction of the second layer:Mobility: IF HO procedure is more critical compared to a normal SHO and has to be verified and tuned.The compressed mode activity increases in the border cells.Accessibility:The first IF Load Sharing will increase the call set up time.Terminal equipment limitations:At them moment, there are several terminal types not fully supporting the features to manage a second layer. In particular several models are not IF HO capable.

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. Capacity Management4. Accessibility & Mobility Principles7. KPIsCell Breathing

Coverage vs. traffic load WCDMA RBSDL high Load UL high Load UL low load DL low load A well known effect of WCDMA CPICH coverage is that it changes depending on the load.The DL coverage (considering the Ec/N0 of the CPICH) in particular decreases with the DL total power (hence with the load).CPICH_Ec/N0 in a point:Ec/N0Cpich = RSCP/RSSI = Pcpich/( (PtotIntra + Ptotinter + Noise)(*P = received power)

DL Problem CPICH Ec/N0 triggering Low load CM AreaCM startIRATUL high Load DL high Load High load CM AreaCM startIRATWCDMA RBSExpected cell area

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. KPIs4. Accessibility & Mobility Principles6. Capacity ManagementAccessibility KPI

Accessibility (CSSR) KPIThe IF Load Sharing feature impacts on the RRC Establishment Success Rate since several RRC Connection Attempts are rejected to be redirected towards the other frequency. So it is expected that, in case of IFLS activated, the number of RRC Connection Success will be reduced because of the Load Sharing Reject events. To take into account this fact the LoadSharingRejects must be subtracted from the total number of RRC_Attempts:

RRC Establishment Success Rate (IFLS) = RRC_Success / ( RRC_Attempts LoadSharingRejects)CSSR is currently calculated by two factors:RRC Establishment Success Rate = RRC_Success / RRC_Attempts *RAB Establishment Success Rate = RAB_Success / RAB_AttemptsHowever the counter for Load Sharing Rejects (pmNoLoadSharingRrcConn) is unique and it does not distinguish between CS, PS or any other kind of RRC Connection cause. This make not easy to adjust the RRC Success Rate for CS and for PS in case of IFLS.

Proposed new formulaeHere we tried to evaluate the performance of some formulae to derive the RRC_Estab_Succ_Rate for PS and CS in case of IFLS. (The results are taken from RNC???) The tested formulae are:The basic idea is to calculate the load sharing reject for PS and CS by a wheight factor given by the fraction of the RRC_CS (or PS) respect to the total number of RRCs. In case of RRC Succ general the formula is muche more simple instead....

Load Sharing Impact on Accessibility (CSSR) KPI - ResultsThe RRC Succ estimation CS and PS are disturbed by the Load Sharing rejects. We registered strong fluctuations of values expecially in case of high IFLS activity....

Load Sharing Impact on Accessibility (CSSR) KPI - ResultsIn case of RRC Succ Rate calculated for all kinds of RRC, the estimation is much more stable instead and not affected by IFLS!

Load Sharing Impact on Accessibility (CSSR) KPI - ResultsHere it is quite evident the noise introduced by the load sharing in CS and PS RRC Succ estimations.>100% valuesStrong KPI deteriorationPlease consider that the values are calculated on daily base. So they should be quite stable

Conclusions (1/2)When Load sharing is introduce the accessibility formulae should be updated to take into consideration the RRC Connection Attempts rejected to be redirected towards the other frequency ().While no problem should exist for the tot accessibility formula:

2 new formulae are proposed for the CS and PS specific KPIs:

However the estimation given by this KPI is not extremely stable/reliable and accurate (the average error seems to be acceptable compared to the error that affects the other formulae but the fluctuation are high).

ConclusionsAn alternative suggestion could be to use the following formula for CSSR

CSSR_CS = RRC_Succ_Global x RAB_CS_SuccCSSR_PS = RRC_Succ_Global x RAB_PS_Succ The estimation given by this KPI is much more stable/reliable and the average error seems to be acceptable compared to the error that affects the other formulae.

The main drawback of this solution is that the Global RRC Succ is often a little bit worse compared with the real CS and PS values. (This is probably related to different radio environment: i.e. the major part of RRC Connections are established for registration purpose, when the UE is entering back to 3G coverage; those radio procedures often occur at cell coverage borders and so are affected by a worse performance.)

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. KPIs4. Accessibility & Mobility Principles6. Capacity ManagementRBS KPI

RBS Counters KPIsThis appendix reports the main KPIs that could be used for HS testing divided by:ThroughputScheduling Ratio and Transmission efficiencyCQI/ACK/NACKPowerRBS RSSI

Note that performing tests with a single HS user in a unloaded network is useful to:Have specific user information for a userVerify counters/KPI meanings and compare them with UE based KPI

Throughput CountersCounters:pmSumAckedBits: the number of Media Access Control high-speed (MAC-hs) bits received and acknowledged by the UE.pmSumTransmittedBits: the number of transmitted bits at MAC-hs, level including retransmissionspmSumNonEmptyUserBuffers: The number of user buffers containing high-speed data.pmNoActiveSubFrames: the number of subframes containing high-speed data transmitted by the RBS.pmNoInactiveRequiredSubFrames: the number of empty subframes transmitted even though data is scheduled for priority queue.

Still not used:pmAverageUserRate (PDF): The distribution of the average user rate among all users allocated to high-speed-DSCH in the cell.

Throughput KPIs

DSCH UE Thr. NET = Av. Throughput (PS-HS) without retransmission: Sum(pmSumAckedBits)/(Sum(pmSumNonEmptyUserBuffers)*0.002s) DSCH UE Thr. GROSS = Av. Throughput (PS-HS) with retransmission: Sum(pmSumTransmittedBits)/(Sum(pmSumNonEmptyUserBuffers)*0.002)

DSCH Cell Thr. NET = The MAC-hs throughput on cell level pmSumAckedBits / (0.002s * pmNoActiveSubFrame)DSCH Cell Thr. GROSS = The MAC-hs data rate on cell levelpmSumTransmittedBits / (0.002 s* pmNoActiveSubFrame)

Cell Thr. NET = The MAC-hs throughput on cell level pmSumAckedBits / (ROP period)Cell Thr. GROSS = The MAC-hs data rate on cell levelpmSumTransmittedBits / (ROP period)

Throughput KPIs Values Live Network

Sheet1

RBS NameRBS SectorRBS Sector CarrierAverage Number Of UE In a QueueDSCH UE Throughput NETDSCH UE Throughput GROSSDSCH Cell Throughput NETDSCH Cell Throughput GROSS% Scheduling Ratio% Tranmission Ratio

RBS32601-0131192.32148.32194.89313.110.00%0.00%

RBS05314-01221164.11221.32265.44357.981.54%2.49%

RBS37058-01121183.97202.45292.65322.040.01%0.02%

RBS00003-01321218.77259.69218.77259.690.00%0.00%

RBS34645-01211242.96350.73242.96350.730.00%0.00%

RBS01281-01311248.4405.3248.4405.30.00%0.00%

RBS37058-01221324.44405.58324.79406.020.11%0.11%

RBS01780-01111352.6566.15491.79789.630.00%0.00%

RBS00357-01211389518.5389518.50.00%0.00%

RBS00429-01121399.94542.16399.94542.160.03%0.03%

RBS37242-01311424.5500.75424.5500.750.00%0.00%

RBS34375-01211.01449.73749.43461.94769.760.00%0.00%

RBS01263-01111456.78565.98456.78565.980.00%0.00%

RBS23074-01321509.66552.27509.66552.270.00%0.00%

RBS23066-01211518.67518.67518.67518.670.00%0.00%

RBS04995-01121556.41648.95557.03649.670.12%0.12%

RBS00370-01111632.88838.31632.88838.310.02%0.02%

RBS01546-01211652.58878.57751.291,011.470.06%0.07%

RBS01281-01111662.621,142.64662.621,142.640.00%0.00%

RBS34375-01311710.731,071.00710.731,071.000.15%0.15%

RBS23025-01311.01734.94901.09828.621,015.960.11%0.12%

RBS37058-01321764.56995.06817.151,063.510.01%0.01%

RBS00353-01111770.181,170.15775.241,177.840.03%0.03%

RBS34645-01111828.631,319.63933.181,486.140.34%0.38%

RBS23025-01211881.871,205.44913.161,248.200.09%0.09%

RBS05314-011211,183.361,390.581,193.881,402.940.06%0.06%

RBS00429-012211,200.851,605.631,200.851,605.630.07%0.07%

RBS01164-013211,285.291,503.111,285.651,503.530.03%0.03%

RBS01164-012211,318.851,537.491,354.041,578.520.14%0.15%

Sheet2

Sheet3

Transmission efficiency KPIsMAC Tx efficiency (or Efficiency factor ) = Sum(pmNoActiveSubFrame )/ (Sum(pmNoActiveSubFrame)+Sum(pmNoInactiveRequiredSubFrame)) Scheduling Ratio = This KPI simply highlights the percentage of time the HS-DSCH is used Sum(pmNoActiveSubFrame)*0.002/ (ROP period)

Transmission ratio = This highlight the percentage of time there is something to transmit. This is a good index on how efficiently the application level can exploit DSCH capabilities(Sum(pmNoActiveSubFrame)+Sum(pmNoInactiveRequiredSubFrame))*0.002 /(ROP period)

Av.# UEs in queueSum(pmSumNonEmptyUserBuffers) / ( Sum(pmNoActiveSubFrame)+ Sum(pmNoInactiveRequiredSubFrames) )

Transmission Efficiency (1/2)The first index to look at when talking about transmission efficiency is the ratio between the used TTI (the one where something is transmitted) and the total #TTI in the test period( + )Mac Tx Efficiency = 99.05%Scheduling Ratio = 81.3%Nothing transmittedPDU is transmittedBuffer not empty but PDU not transmittedTransmission Ratio = 82.8%( + )( + )( + + )

Transmission Efficient KPIs Values Live Network

Sheet1

RBS NameSectorCarrierAverage Number Of UE In a QueueDSCH UE Throughput NETDSCH UE Throughput GROSSDSCH Cell Throughput NETDSCH Cell Throughput GROSS% Scheduling Ratio% Tranmission Ratio

RBS32601-0131192.32148.32194.89313.110.00%0.00%

RBS05314-01221164.11221.32265.44357.981.54%2.49%

RBS37058-01121183.97202.45292.65322.040.01%0.02%

RBS00003-01321218.77259.69218.77259.690.00%0.00%

RBS34645-01211242.96350.73242.96350.730.00%0.00%

RBS01281-01311248.4405.3248.4405.30.00%0.00%

RBS37058-01221324.44405.58324.79406.020.11%0.11%

RBS01780-01111352.6566.15491.79789.630.00%0.00%

RBS00357-01211389518.5389518.50.00%0.00%

RBS00429-01121399.94542.16399.94542.160.03%0.03%

RBS37242-01311424.5500.75424.5500.750.00%0.00%

RBS34375-01211449.73749.43461.94769.760.00%0.00%

RBS01263-01111456.78565.98456.78565.980.00%0.00%

RBS23074-01321509.66552.27509.66552.270.00%0.00%

RBS23066-01211518.67518.67518.67518.670.00%0.00%

RBS04995-01121556.41648.95557.03649.670.12%0.12%

RBS00370-01111632.88838.31632.88838.310.02%0.02%

RBS01546-01211652.58878.57751.291,011.470.06%0.07%

RBS01281-01111662.621,142.64662.621,142.640.00%0.00%

RBS34375-01311710.731,071.00710.731,071.000.15%0.15%

RBS23025-01311734.94901.09828.621,015.960.11%0.12%

RBS37058-01321764.56995.06817.151,063.510.01%0.01%

RBS00353-01111770.181,170.15775.241,177.840.03%0.03%

RBS34645-01111828.631,319.63933.181,486.140.34%0.38%

RBS23025-01211881.871,205.44913.161,248.200.09%0.09%

RBS05314-011211,183.361,390.581,193.881,402.940.06%0.06%

RBS00429-012211,200.851,605.631,200.851,605.630.07%0.07%

RBS01164-013211,285.291,503.111,285.651,503.530.03%0.03%

RBS01164-012211,318.851,537.491,354.041,578.520.14%0.15%

Sheet2

Sheet3

CQI/ACK/NACK counterspmReportedCqi: the Channel Quality Indicators (CQI) reported by the UE in the cell and received by the RBS.pmUsedCqi: the CQI, used by the RBS for scheduling the priority queue for the HS-DSCH.Within the reportedCQI tables, there is a column called InvalidCQI. This counter will be used as well

pmAckReceived: The number of Acknowledgements (ACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-DSCH).pmNackReceived: The number of Negative-Acknowledgements (NACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-DSCH).

CQI/ACK/NACK KPIsHS-BLER: pmNackReceived /(pmNackReceived + pmAckReceived)RtxOverhead = Percentage of the Retransmitted bits over the total 100*(pmSumTransmittedBits - pmSumAckedBits) /(pmSumTransmittedBits)

CQI specificAv. ReportedAv. USed CQIDelta CQI = Difference between the 2 averaged values above. This is an index of how much CQI adjustment acts.CQIequalTo0 = Count(CQIreported=0)/Count(CQIreported). This is the main reason of MAC inefficiencyInvalidCQI = invalideCQI/Count(CQIreported). Not clear what invlid means

Proposal: (ACK+NACK)/ActiveTTI: still not clear WHAT WE CAN SEE FROM IT(pmNackReceived+pmAckReceived)/ActiveFrame

HS schedulingThe CQI=0 percentage drop to 0.01%, almost nothing.The BLER and the Retransmission rate are almost identical, that means the CQI adjustment has been able to reach the target BaselineTest 2Reported BLER [%]12,612,5RtxOverhead [%]14,815,0Av Reported CQI10,117,0Av Used CQI9,816,5Delta CQI0,320,48(ACK+NACK)/Active [%]98,6897,29CQI = 0 [%]0,790,01The BLER is the ratio between NACK and (ACK + NACK)The Rtx overhead is the ratio between the transmitted and the acked bitsDelta CQI could be seen as index of the CQI adjustment impactWhen 0 is received no transmission will be allowed to the mobile for the following TTI

Integrity KPIs Values Live Network

Sheet1

RBS NameRBS SectorRBS Sector Carrier% HS-BLER% Rtx OverheadMAC Transmission Efficiency

RBS23066-01210.00%0.00%100.00%

RBS37058-01124.14%9.13%62.87%

RBS37242-01318.85%15.23%100.00%

RBS23074-01329.43%7.72%100.00%

RBS05314-012210.01%25.85%61.83%

RBS04995-011211.74%14.26%99.89%

RBS01164-012212.03%14.22%97.41%

RBS05314-011212.99%14.90%99.12%

RBS01164-013213.28%14.49%99.97%

RBS01263-011113.64%19.29%100.00%

RBS23025-013114.18%18.44%89.32%

RBS37058-012214.34%20.01%99.89%

RBS00003-013215.38%15.76%100.00%

RBS37058-013218.06%23.16%93.56%

RBS34375-012118.24%39.99%98.14%

RBS01546-012118.33%25.72%87.02%

RBS00370-011118.44%24.51%100.00%

RBS00429-011219.62%26.23%100.00%

RBS32601-013121.05%37.76%47.37%

RBS23025-012122.70%26.84%96.60%

RBS34375-013123.36%33.64%100.00%

RBS01780-011123.64%37.72%71.70%

RBS00429-012224.27%25.21%100.00%

RBS00357-012125.00%24.98%100.00%

RBS34645-011127.50%37.21%88.80%

RBS00353-011128.36%34.18%99.35%

RBS34645-012130.77%30.73%100.00%

RBS01281-013133.68%38.71%100.00%

RBS01281-011138.09%42.01%100.00%

HS RBS Report RevPA2 Integrity

RBS NameRBS SectorRBS Sector Carrier% HS-BLER% Rtx OverheadMAC Transmission Efficiency

RBS23066-01210.00%0.00%100.00%

RBS37058-01124.14%9.13%62.87%

RBS37242-01318.85%15.23%100.00%

RBS23074-01329.43%7.72%100.00%

RBS05314-012210.01%25.85%61.83%

RBS04995-011211.74%14.26%99.89%

RBS01164-012212.03%14.22%97.41%

RBS05314-011212.99%14.90%99.12%

RBS01164-013213.28%14.49%99.97%

RBS01263-011113.64%19.29%100.00%

RBS23025-013114.18%18.44%89.32%

RBS37058-012214.34%20.01%99.89%

RBS00003-013215.38%15.76%100.00%

RBS37058-013218.06%23.16%93.56%

RBS34375-012118.24%39.99%98.14%

RBS01546-012118.33%25.72%87.02%

RBS00370-011118.44%24.51%100.00%

RBS00429-011219.62%26.23%100.00%

RBS32601-013121.05%37.76%47.37%

RBS23025-012122.70%26.84%96.60%

RBS34375-013123.36%33.64%100.00%

RBS01780-011123.64%37.72%71.70%

RBS00429-012224.27%25.21%100.00%

RBS00357-012125.00%24.98%100.00%

RBS34645-011127.50%37.21%88.80%

RBS00353-011128.36%34.18%99.35%

RBS34645-012130.77%30.73%100.00%

RBS01281-013133.68%38.71%100.00%

RBS01281-011138.09%42.01%100.00%

RBS00003-0112#DIV/0#DIV/0#DIV/0

RBS00003-0122#DIV/0#DIV/0#DIV/0

RBS00089-0111#DIV/0#DIV/0#DIV/0

RBS00089-0121#DIV/0#DIV/0#DIV/0

RBS00089-0131#DIV/0#DIV/0#DIV/0

RBS00253-0112#DIV/0#DIV/0#DIV/0

RBS00253-0122#DIV/0#DIV/0#DIV/0

RBS00342-0111#DIV/0#DIV/0#DIV/0

RBS00342-0121#DIV/0#DIV/0#DIV/0

RBS00342-0131#DIV/0#DIV/0#DIV/0

RBS00353-0121#DIV/0#DIV/0#DIV/0

RBS00353-0131#DIV/0#DIV/0#DIV/0

RBS00356-0111#DIV/0#DIV/0#DIV/0

RBS00356-0121#DIV/0#DIV/0#DIV/0

RBS00356-0131#DIV/0#DIV/0#DIV/0

RBS00357-0111#DIV/0#DIV/0#DIV/0

RBS00357-0131#DIV/0#DIV/0#DIV/0

RBS00359-0111#DIV/0#DIV/0#DIV/0

RBS00359-0121#DIV/0#DIV/0#DIV/0

RBS00359-0131#DIV/0#DIV/0#DIV/0

RBS00368-0111#DIV/0#DIV/0#DIV/0

RBS00368-0121#DIV/0#DIV/0#DIV/0

RBS00368-0131#DIV/0#DIV/0#DIV/0

RBS00370-0121#DIV/0#DIV/0#DIV/0

RBS00370-0131#DIV/0#DIV/0#DIV/0

RBS00395-0111#DIV/0#DIV/0#DIV/0

RBS00395-0121#DIV/0#DIV/0#DIV/0

RBS00395-0131#DIV/0#DIV/0#DIV/0

RBS00399-0111#DIV/0#DIV/0#DIV/0

RBS00399-0121#DIV/0#DIV/0#DIV/0

RBS00399-0131#DIV/0#DIV/0#DIV/0

RBS00429-0132#DIV/0#DIV/0#DIV/0

RBS00434-0111#DIV/0#DIV/0#DIV/0

RBS00434-0121#DIV/0#DIV/0#DIV/0

RBS00434-0131#DIV/0#DIV/0#DIV/0

RBS00440-0111#DIV/0#DIV/0#DIV/0

RBS00440-0121#DIV/0#DIV/0#DIV/0

RBS00440-0131#DIV/0#DIV/0#DIV/0

RBS00679-0111#DIV/0#DIV/0#DIV/0

RBS00679-0121#DIV/0#DIV/0#DIV/0

RBS00682-0112#DIV/0#DIV/0#DIV/0

RBS00682-0122#DIV/0#DIV/0#DIV/0

RBS00682-0132#DIV/0#DIV/0#DIV/0

RBS00689-0112#DIV/0#DIV/0#DIV/0

RBS00689-0122#DIV/0#DIV/0#DIV/0

RBS00710-0111#DIV/0#DIV/0#DIV/0

RBS00710-0121#DIV/0#DIV/0#DIV/0

RBS00710-0131#DIV/0#DIV/0#DIV/0

RBS00757-0111#DIV/0#DIV/0#DIV/0

RBS00757-0121#DIV/0#DIV/0#DIV/0

RBS00757-0131#DIV/0#DIV/0#DIV/0

RBS00866-0112#DIV/0#DIV/0#DIV/0

RBS00866-0122#DIV/0#DIV/0#DIV/0

RBS00866-0132#DIV/0#DIV/0#DIV/0

RBS00869-0111#DIV/0#DIV/0#DIV/0

RBS00869-0121#DIV/0#DIV/0#DIV/0

RBS00869-0131#DIV/0#DIV/0#DIV/0

RBS00873-0111#DIV/0#DIV/0#DIV/0

RBS00873-0121#DIV/0#DIV/0#DIV/0

RBS00873-0131#DIV/0#DIV/0#DIV/0

RBS00874-0111#DIV/0#DIV/0#DIV/0

RBS00874-0121#DIV/0#DIV/0#DIV/0

RBS00874-0131#DIV/0#DIV/0#DIV/0

RBS00877-0111#DIV/0#DIV/0#DIV/0

RBS00877-0121#DIV/0#DIV/0#DIV/0

RBS00877-0131#DIV/0#DIV/0#DIV/0

RBS00966-0111#DIV/0#DIV/0#DIV/0

RBS00966-0121#DIV/0#DIV/0#DIV/0

RBS00966-0131#DIV/0#DIV/0#DIV/0

RBS00969-0111#DIV/0#DIV/0#DIV/0

RBS00969-0121#DIV/0#DIV/0#DIV/0

RBS00969-0131#DIV/0#DIV/0#DIV/0

RBS01164-0112#DIV/0#DIV/0#DIV/0

RBS01263-0121#DIV/0#DIV/0#DIV/0

RBS01263-0131#DIV/0#DIV/0#DIV/0

RBS01281-0121#DIV/0#DIV/0#DIV/0

RBS01317-0111#DIV/0#DIV/0#DIV/0

RBS01317-0121#DIV/0#DIV/0#DIV/0

RBS01317-0131#DIV/0#DIV/0#DIV/0

RBS01546-0111#DIV/0#DIV/0#DIV/0

RBS01546-0131#DIV/0#DIV/0#DIV/0

RBS01549-0111#DIV/0#DIV/0#DIV/0

RBS01549-0121#DIV/0#DIV/0#DIV/0

RBS01549-0131#DIV/0#DIV/0#DIV/0

RBS01550-0111#DIV/0#DIV/0#DIV/0

RBS01550-0121#DIV/0#DIV/0#DIV/0

RBS01551-0111#DIV/0#DIV/0#DIV/0

RBS01551-0121#DIV/0#DIV/0#DIV/0

RBS01551-0131#DIV/0#DIV/0#DIV/0

RBS01553-0111#DIV/0#DIV/0#DIV/0

RBS01553-0121#DIV/0#DIV/0#DIV/0

RBS01607-0111#DIV/0#DIV/0#DIV/0

RBS01607-0121#DIV/0#DIV/0#DIV/0

RBS01607-0131#DIV/0#DIV/0#DIV/0

RBS01612-0111#DIV/0#DIV/0#DIV/0

RBS01612-0121#DIV/0#DIV/0#DIV/0

RBS01612-0131#DIV/0#DIV/0#DIV/0

RBS01615-0111#DIV/0#DIV/0#DIV/0

RBS01615-0121#DIV/0#DIV/0#DIV/0

RBS01615-0131#DIV/0#DIV/0#DIV/0

RBS01616-0111#DIV/0#DIV/0#DIV/0

RBS01616-0121#DIV/0#DIV/0#DIV/0

RBS01616-0131#DIV/0#DIV/0#DIV/0

RBS01780-0121#DIV/0#DIV/0#DIV/0

RBS01780-0131#DIV/0#DIV/0#DIV/0

RBS01789-0111#DIV/0#DIV/0#DIV/0

RBS01789-0121#DIV/0#DIV/0#DIV/0

RBS01789-0131#DIV/0#DIV/0#DIV/0

RBS01790-0112#DIV/0#DIV/0#DIV/0

RBS01790-0122#DIV/0#DIV/0#DIV/0

RBS01790-0132#DIV/0#DIV/0#DIV/0

RBS01832-0111#DIV/0#DIV/0#DIV/0

RBS01832-0121#DIV/0#DIV/0#DIV/0

RBS01832-0131#DIV/0#DIV/0#DIV/0

RBS01834-0111#DIV/0#DIV/0#DIV/0

RBS01834-0121#DIV/0#DIV/0#DIV/0

RBS01834-0131#DIV/0#DIV/0#DIV/0

RBS01848-0111#DIV/0#DIV/0#DIV/0

RBS01848-0121#DIV/0#DIV/0#DIV/0

RBS01848-0131#DIV/0#DIV/0#DIV/0

RBS01858-0111#DIV/0#DIV/0#DIV/0

RBS01858-0121#DIV/0#DIV/0#DIV/0

RBS01858-0131#DIV/0#DIV/0#DIV/0

RBS01859-0111#DIV/0#DIV/0#DIV/0

RBS01859-0121#DIV/0#DIV/0#DIV/0

RBS01859-0131#DIV/0#DIV/0#DIV/0

RBS01861-0111#DIV/0#DIV/0#DIV/0

RBS01861-0121#DIV/0#DIV/0#DIV/0

RBS01861-0131#DIV/0#DIV/0#DIV/0

RBS01879-0111#DIV/0#DIV/0#DIV/0

RBS01879-0121#DIV/0#DIV/0#DIV/0

RBS01879-0131#DIV/0#DIV/0#DIV/0

RBS01895-0111#DIV/0#DIV/0#DIV/0

RBS01895-0121#DIV/0#DIV/0#DIV/0

RBS01895-0131#DIV/0#DIV/0#DIV/0

RBS01920-0111#DIV/0#DIV/0#DIV/0

RBS01920-0121#DIV/0#DIV/0#DIV/0

RBS02902-0111#DIV/0#DIV/0#DIV/0

RBS02902-0121#DIV/0#DIV/0#DIV/0

RBS02902-0131#DIV/0#DIV/0#DIV/0

RBS02993-0111#DIV/0#DIV/0#DIV/0

RBS02993-0121#DIV/0#DIV/0#DIV/0

RBS02993-0131#DIV/0#DIV/0#DIV/0

RBS04321-0111#DIV/0#DIV/0#DIV/0

RBS04321-0121#DIV/0#DIV/0#DIV/0

RBS04995-0122#DIV/0#DIV/0#DIV/0

RBS04995-0132#DIV/0#DIV/0#DIV/0

RBS05314-0132#DIV/0#DIV/0#DIV/0

RBS06643-0111#DIV/0#DIV/0#DIV/0

RBS06643-0121#DIV/0#DIV/0#DIV/0

RBS06651-0112#DIV/0#DIV/0#DIV/0

RBS06651-0122#DIV/0#DIV/0#DIV/0

RBS07700-0111#DIV/0#DIV/0#DIV/0

RBS07700-0121#DIV/0#DIV/0#DIV/0

RBS07700-0131#DIV/0#DIV/0#DIV/0

RBS10081-0111#DIV/0#DIV/0#DIV/0

RBS10081-0121#DIV/0#DIV/0#DIV/0

RBS10081-0131#DIV/0#DIV/0#DIV/0

RBS11169-0111#DIV/0#DIV/0#DIV/0

RBS11169-0121#DIV/0#DIV/0#DIV/0

RBS11169-0131#DIV/0#DIV/0#DIV/0

RBS11325-0111#DIV/0#DIV/0#DIV/0

RBS22278-0112#DIV/0#DIV/0#DIV/0

RBS22290-0111#DIV/0#DIV/0#DIV/0

RBS22290-0121#DIV/0#DIV/0#DIV/0

RBS22290-0131#DIV/0#DIV/0#DIV/0

RBS22291-0112#DIV/0#DIV/0#DIV/0

RBS22291-0122#DIV/0#DIV/0#DIV/0

RBS22291-0132#DIV/0#DIV/0#DIV/0

RBS23004-0111#DIV/0#DIV/0#DIV/0

RBS23004-0121#DIV/0#DIV/0#DIV/0

RBS23004-0131#DIV/0#DIV/0#DIV/0

RBS23009-0111#DIV/0#DIV/0#DIV/0

RBS23009-0121#DIV/0#DIV/0#DIV/0

RBS23009-0131#DIV/0#DIV/0#DIV/0

RBS23013-0111#DIV/0#DIV/0#DIV/0

RBS23013-0121#DIV/0#DIV/0#DIV/0

RBS23025-0111#DIV/0#DIV/0#DIV/0

RBS23026-0111#DIV/0#DIV/0#DIV/0

RBS23026-0121#DIV/0#DIV/0#DIV/0

RBS23026-0131#DIV/0#DIV/0#DIV/0

RBS23032-0111#DIV/0#DIV/0#DIV/0

RBS23032-0121#DIV/0#DIV/0#DIV/0

RBS23032-0131#DIV/0#DIV/0#DIV/0

RBS23033-0111#DIV/0#DIV/0#DIV/0

RBS23033-0121#DIV/0#DIV/0#DIV/0

RBS23033-0131#DIV/0#DIV/0#DIV/0

RBS23065-0111#DIV/0#DIV/0#DIV/0

RBS23065-0121#DIV/0#DIV/0#DIV/0

RBS23065-0131#DIV/0#DIV/0#DIV/0

RBS23066-0111#DIV/0#DIV/0#DIV/0

RBS23066-0131#DIV/0#DIV/0#DIV/0

RBS23068-0111#DIV/0#DIV/0#DIV/0

RBS23068-0121#DIV/0#DIV/0#DIV/0

RBS23068-0131#DIV/0#DIV/0#DIV/0

RBS23074-0112#DIV/0#DIV/0#DIV/0

RBS23074-0122#DIV/0#DIV/0#DIV/0

RBS23405-0111#DIV/0#DIV/0#DIV/0

RBS23405-0121#DIV/0#DIV/0#DIV/0

RBS23405-0131#DIV/0#DIV/0#DIV/0

RBS30173-0111#DIV/0#DIV/0#DIV/0

RBS30173-0121#DIV/0#DIV/0#DIV/0

RBS30173-0131#DIV/0#DIV/0#DIV/0

RBS30428-0111#DIV/0#DIV/0#DIV/0

RBS30428-0121#DIV/0#DIV/0#DIV/0

RBS30428-0131#DIV/0#DIV/0#DIV/0

RBS31041-0111#DIV/0#DIV/0#DIV/0

RBS31350-0111#DIV/0#DIV/0#DIV/0

RBS31350-0121#DIV/0#DIV/0#DIV/0

RBS31350-0131#DIV/0#DIV/0#DIV/0

RBS32026-0111#DIV/0#DIV/0#DIV/0

RBS32026-0121#DIV/0#DIV/0#DIV/0

RBS32026-0131#DIV/0#DIV/0#DIV/0

RBS32601-0111#DIV/0#DIV/0#DIV/0

RBS32725-0111#DIV/0#DIV/0#DIV/0

RBS32725-0121#DIV/0#DIV/0#DIV/0

RBS32725-0131#DIV/0#DIV/0#DIV/0

RBS32926-0111#DIV/0#DIV/0#DIV/0

RBS32926-0121#DIV/0#DIV/0#DIV/0

RBS32926-0131#DIV/0#DIV/0#DIV/0

RBS33552-0111#DIV/0#DIV/0#DIV/0

RBS33552-0121#DIV/0#DIV/0#DIV/0

RBS33552-0131#DIV/0#DIV/0#DIV/0

RBS33655-0111#DIV/0#DIV/0#DIV/0

RBS33655-0121#DIV/0#DIV/0#DIV/0

RBS33655-0131#DIV/0#DIV/0#DIV/0

RBS33673-0111#DIV/0#DIV/0#DIV/0

RBS33688-0111#DIV/0#DIV/0#DIV/0

RBS33688-0121#DIV/0#DIV/0#DIV/0

RBS33693-0112#DIV/0#DIV/0#DIV/0

RBS33693-0122#DIV/0#DIV/0#DIV/0

RBS33693-0132#DIV/0#DIV/0#DIV/0

RBS33725-0111#DIV/0#DIV/0#DIV/0

RBS33725-0121#DIV/0#DIV/0#DIV/0

RBS33725-0131#DIV/0#DIV/0#DIV/0

RBS33908-0111#DIV/0#DIV/0#DIV/0

RBS34096-0111#DIV/0#DIV/0#DIV/0

RBS34096-0121#DIV/0#DIV/0#DIV/0

RBS34096-0131#DIV/0#DIV/0#DIV/0

RBS34107-0111#DIV/0#DIV/0#DIV/0

RBS34197-0112#DIV/0#DIV/0#DIV/0

RBS34197-0122#DIV/0#DIV/0#DIV/0

RBS34197-0132#DIV/0#DIV/0#DIV/0

RBS34303-0112#DIV/0#DIV/0#DIV/0

RBS34305-0112#DIV/0#DIV/0#DIV/0

RBS34307-0112#DIV/0#DIV/0#DIV/0

RBS34309-0112#DIV/0#DIV/0#DIV/0

RBS34311-0112#DIV/0#DIV/0#DIV/0

RBS34313-0112#DIV/0#DIV/0#DIV/0

RBS34315-0112#DIV/0#DIV/0#DIV/0

RBS34375-0111#DIV/0#DIV/0#DIV/0

RBS34558-0111#DIV/0#DIV/0#DIV/0

RBS34558-0121#DIV/0#DIV/0#DIV/0

RBS34558-0131#DIV/0#DIV/0#DIV/0

RBS34596-0111#DIV/0#DIV/0#DIV/0

RBS34903-0111#DIV/0#DIV/0#DIV/0

RBS34903-0121#DIV/0#DIV/0#DIV/0

RBS34903-0131#DIV/0#DIV/0#DIV/0

RBS34971-0111#DIV/0#DIV/0#DIV/0

RBS35332-0111#DIV/0#DIV/0#DIV/0

RBS35332-0121#DIV/0#DIV/0#DIV/0

RBS35332-0131#DIV/0#DIV/0#DIV/0

RBS35379-0111#DIV/0#DIV/0#DIV/0

RBS36419-0111#DIV/0#DIV/0#DIV/0

RBS36780-0111#DIV/0#DIV/0#DIV/0

RBS36780-0121#DIV/0#DIV/0#DIV/0

RBS36780-0131#DIV/0#DIV/0#DIV/0

RBS37242-0111#DIV/0#DIV/0#DIV/0

RBS37242-0121#DIV/0#DIV/0#DIV/0

RBS38081-0111#DIV/0#DIV/0#DIV/0

RBS38081-0121#DIV/0#DIV/0#DIV/0

RBS38081-0131#DIV/0#DIV/0#DIV/0

RBS38222-0111#DIV/0#DIV/0#DIV/0

RBS powerpmTransmittedCarrierPowerNonHs: The transmitted carrier power for all non high-speed codes in the cell.pmTransmittedCarrierPower: the transmitted carrier power measured at the TX reference point every 4 seconds.

Notes:Every 100 ms the transmitted carrier power for all non high-speed codes in the cell are sampled. The problem is that there are not necessary data enough to transmit in every slot: hence some kind of normalization should be investigated.

Tx Power examples (almost 100% of Scheduling Ratio)CCH power = 1.7The Max power = 8.7The power is calculated at the antenna reference point

Transmitted Power (2/2)The Average Tx power is: Total Carrier = 4.85 WR99 power = 1.63 WTotalHS_power = 3.22 W

Note that the HS power is an estimation of the power transmitted for the HS on average during the test period but it is NOT an estimate of the power that HS required in the cell!The activity of the HS (when we transmit something) is still low (80%).Maybe a more interesting KPI could be: TotalHS_power/SchedulingRatio*100 = 100*3.22/81.3 = 3.96 W

It is interesting to notice anyway that even with a single user the MaxTxPower is reached.

RBS list of counterspmTransmittedCarrierPowerNonHs: The transmitted carrier power for all non high-speed codes in the cell.pmTransmittedCarrierPower: the transmitted carrier power measured at the TX reference point every 4 secondspmNoActiveSubFrames: the number of subframes containing high-speed data transmitted by the RBS.pmNoInactiveRequiredSubFrames: the number of empty subframes transmitted even though data is scheduled for priority queue.pmSumNonEmptyUserBuffers: The number of user buffers containing high-speed data.pmSumAckedBits:the number of Media Access Control high-speed (MAC-hs) bits received and acknowledged by the UE.pmSumTransmittedBits: Description The number of transmitted bits at MAC-hs, level including retransmissionspmReportedCqi: the Channel Quality Indicators (CQI) reported by the UE in the cell and received by the RBS.pmUsedCqi: the CQI, used by the RBS for scheduling the priority queue for the HS-DSCH. pmAckReceived: The number of Acknowledgements (ACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-DSCH).pmNackReceived: The number of Negative-Acknowledgements (NACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-DSCH). pmAverageRssi: The average Received Signal Strength Indication (RSSI).

Agenda3. Channel Structure2. Architecture1. Overview5. InterFrequency Mobility Principles6. KPIs4. Accessibility & Mobility Principles6. Capacity ManagementRNC KPI

Cell Availability (1)The length of time in seconds that a cell is available for Packet Interactive HS service is defined as cell HS availability. in the example, the cell HS availability during 24 hour period is reported.1) HS cell Availability (24 Hours period)2) percentage of unplanned HS downtime (24 Hours period)3) percentage of planned HS downtime (24 Hours period)

AccessibilityThe new and existing cell counters used in the PS RAB establishment procedure are given in the following list: The number of attempted RAB establishments for PS Interactive RAB mapped on HS-DSCH (stepped for the selected Serving HS-DSCH cell at RAB establishment and before possible Inter-Frequency HO).The number of successful RAB establishments for PS Interactive RAB mapped on HS-DSCH.Number of successful Hard HO for serving HS-DSCH cell selection (in the source cell).Number of successful Hard HO for serving HS-DSCH cell selection (in the target cell).Number of failed Hard HO for serving HS-DSCH cell selection and UE connection maintained (in the source cell).Number of failed Hard HO for serving HS-DSCH cell selection and UEconnection maintained (in the target cell).

Accessibility/ IF counters

AccessibilityPS Interactive Total RAB establishment, success rate =

pmNoRabEstablishAttemptPacketInteractiveHs100 *pmNoRabEstablishSuccessPacketInteractive(pmNoRabEstablishAttemptPacketInteractive pmNoOutgoingHsHardHoAttempt + pmNoIncomingHsHardHoAttempt +pmNoHsHardHoReturnOldChSource- pmNoHsHardHoReturnOldChTarget )

PS Interactive HS RAB establishment success rate =100 *pmNoRabEstablishSuccessPacketInteractiveHs

InterFrequency Handover2) PS Interactive HS Hard Handover incoming success rate 3) PS Interactive HS Hard Handover return to old channel rate (source Cell) 4) PS Interactive HS Hard Handover return to old channel rate (target Cell) 1) PS Interactive HS Hard Handover outgoing success rate 5) PS Interactive HS Hard Handover outgoing Lost connection rate 6) PS Interactive HS Hard Handover incoming Lost connection rate

RetainabilityThe new and existing cell counters used for Retainability are given in the following list: The number of signalling connection releases triggered for PS Interactive RAB mapped on HS-DSCH due to inactivity (Channel Switching Evaluation algorithms request the execution of a switch to idle). The counter is stepped at the reception of RANAP Iu Release Command from CN, for HS channel cell or RANAP RAB assignment Request (when the RAB is released) and the RANAP cause is User Inactivity.Number of system releases of packet RABs mapped on HS-DSCH in the Serving HS-DSCH cell.Number of successful normal releases of packet RABs mapped on HS-DSCH in the Serving HS-DSCH cell.

RetainabilityHS Radio Bearer retainability, drop rate = 100 *pmNoSystemRbReleaseHs pmNoSystemRbReleaseHs + pmNoNormalRbReleaseHsTotal PS Interactive retainability, drop rate =100 *( pmNoSystemRabReleasePacket ) pmNoSystemRabReleasePacket + pmNoNormalRabReleasePacket

System UtilizationIt is possible to measure HS A-DCH utilisation in terms of code usage and average number of users per cell.Two new set of counters shall be implemented. The first set is used to observe the HS A-DCH code utilisation per cell. The KPI indicates the the total number of A-DCH radio bearers established in a cell.

( pmSumPsHsAdchRabEstablish /pmSamplePsHsAdchRabEstablish )

The second set is used to observe the average number of users per cell (hence the number of HS users), which is done by looking only at the best cell:

(pmSumBestPsHsAdchRabEstablish /pmSampleBestPsHsAdchRabEstablish )

Throughput

Throughput1) Average Throughput for PS interactive HS (RNC Level) 2) Retransmission Rate for PS interactive HS (RNC Level) 3) HSDPA total RLC data Traffic DL [MByte] (RNC Level)

Retrans rate live RNC

Sheet1

Object NameRetrans Rate PS Int HS

RNCCN199.63%

RNCKS199.49%

RNCKS2100.00%

RNCNY198.03%

HS RNC Report RevPA2

Object NameRetrans Rate PS Int HSpmSentPacketDataHs2pmSentPacketDataHs3pmSentPacketDataHs4pmSentPacketDataInclRetransHs4pmSentPacketDataInclRetransHs2pmSentPacketDataInclRetransHs3pmSentPacketDataInclRetransHs4

RNCCN199.63%638,992.00568136136640,592.00568136

RNCKS199.49%26,871,315.0037,737.0019,167.0019,245.0026,974,008.0038,031.0019,245.00

RNCKS2100.00%14,153.00440014,153.00440

RNCNY198.03%11,540,518.0031,674.0026,593.0026,740.0011,763,243.0032,120.0026,740.00

MobilityFor mobility only the HS serving cell change procedure is considered .The corresponding KPI is1) Success rate for HS Cell Change in target cell

Admission & Congestion ControlNumber of of radio links that are on SF=4 in ULpmSumSf4Ul /pmSamplesSf4Ul

RNC counter monitoring no. of admission rejects (RAB setup) of HSDPA userspmNoOfNonHoReqDeniedHs

RNC counters monitoring no. of HSDPA users (connections) released due to congestionpmNoOfTermHsCong & pmNoOfIurTermHsCong

Shared-channel transmissionIn case of shared channel transmission for packet data, a part of the total downlink code resource is seen as a shared resource that is dynamically shared between a set of packet-data users, primarily in the time domain. Thus, in case of shared channel transmission, codes are allocated to a user only when they are actually to be used for transmission. Shared-channel transmission is possible already in Release 99 of the WCDMA specification by means of the Downlink Shared Channel (DSCH) transport channel. The main benefit with DSCH transmission is to reduce/avoid the risk for code-limited capacity. However, in general, shared-channel transmission offers the possibility for several other benefits that are not supported by DSCH but that will be supported in case of HSDPA.Shared-channel transmission implies that a certain amount of radio resources of a cell (code space and power in case ofCDMA) is seen as a common resource that is dynamically shared between users, primarily in the time domain.Transmission by means of the WCDMA Downlink Shared Channel (DSCH) is one example of shared-channeltransmission. The main benefit with DSCH transmission is more efficient utilization of available code resourcescompared to the use of a dedicated channel, i.e. reduced risk for code-limited downlink. However, with the introductionof HS-DSCH, several other benefits of shared-channel transmission can be exploited, as described below.

Shared-channel transmissionIn case of shared channel transmission for packet data, a part of the total downlink code resource is seen as a shared resource that is dynamically shared between a set of packet-data users, primarily in the time domain. Thus, in case of shared channel transmission, codes are allocated to a user only when they are actually to be used for transmission. Shared-channel transmission is possible already in Release 99 of the WCDMA specification by means of the Downlink Shared Channel (DSCH) transport channel. The main benefit with DSCH transmission is to reduce/avoid the risk for code-limited capacity. However, in general, shared-channel transmission offers the possibility for several other benefits that are not supported by DSCH but that will be supported in case of HSDPA.Shared-channel transmission implies that a certain amount of radio resources of a cell (code space and power in case ofCDMA) is seen as a common resource that is dynamically shared between users, primarily in the time domain.Transmission by means of the WCDMA Downlink Shared Channel (DSCH) is one example of shared-channeltransmission. The main benefit with DSCH transmission is more efficient utilization of available code resourcescompared to the use of a dedicated channel, i.e. reduced risk for code-limited downlink. However, with the introductionof HS-DSCH, several other benefits of shared-channel transmission can be exploited, as described below.

HS-DSCH power allocationThere are two main alternatives for the allocation of power to HSDPA transmission:- Static power allocation, where a fixed amount of power is allocated for HS-DSCH transmission- Dynamic power allocation, where HS-DSCH is allocated the remaining power after power has been allocated to other channels.The two alternatives are illustrated on the next page. Dynamic power allocation is more efficient as it allows for full use of the overall available cell power.Typical power allocation for HS-DSCH can be in the range 30% to 80% of the overall base station power. In the higher case, the cell basically carries only HS-DSCH traffic, in addition to necessary control channels.The RNC is responsible for the 1.normal traffic handling: RAB establishment and release, 2. channel switching and 3. mobility. Other functions residing in the RNC are 4.resource handling and capacity management. 5.Layer 2 for HSDPA is divided between RNC and RBS: the RNC handles the MAC-d, 6.power control of the uplink HS control channel (HS-DPCCH) and some parts of flow control.The RBS is responsible for the 1.MAC-hs part of layer 2, which includes scheduling, HARQ process handling, transport format selection and parts of flow control.

2.RBS is also responsible for power control of downlink HS shared control channels. (HS-SCCH)

To enable HSDPA, new hardware is required in the RBS.I will go through the channels which we need to know for HSDPA dimensioning. Those are the dedicated and control channels for HSDPA.

HS-DSCH is used for data transmission and it is never in soft handover. One channel is shared by all users. HS-DSCH mobility (w/o loss off PDP context) supported by means of cell selection. An HSDPA user can fall back to DCH due to coverage when leaving an HSDPA cell. (One transport block of dynamic size per 2 ms TTI. Mapped to (multiple) HS-PDSCH)

HS-SCCH is used for control signaling needed for HS-DSCH and it is never in soft handover either.

A-DCH UL/DL: A set of dedicated UL and DL channels for uplink traffic and DL services that are not carried on HS-DSCH. One A-DCH channel pair is set up for every HSDPA user, inactive or active. A-DCH has inter-RNC mobility.

When a HS-DSCH is configured for an UE there is also an associated DCH configuration.The HS-DSCH Associated DCH configuration, A-DCH, is the DCH configuration that is used in combination with HS-DSCH, which implies both the SRB-DCH and the PS RB part mapped on DCHThe main task for HS-SCCH is to tell which UE that will receive data on HS-DSCH. It carries control information from MAC-hs such as identity of the terminal, HS dedicated shared channel code set, modulation scheme and transport format selected by link adaptation mechanism, One channel is shared by all users in P4. It is possible to have more than one HS-SCCH per cell if code multiplexing is used (not in P4). (In release 5 at most 4 HS-SCCHs can be monitored.) Never in SHO SF=128

(power control up to 4 as seen from UE, can be >4 per cell)

The user data throughput is the throughput for L1 excluding MAC/RLC headers. This is the useful data rate for an user.The UEs limit the capacity. UE: 3.36 Mbps. The system (P4) is capable of transmitting 4.32 Mbps (user data rate). 27*320 (payload bits in MAC-d PDU)/2ms (TTI) = 4.32 Mbps.Max data rate, max number of MAC-D PDUs in MAC-hs PDU depends on HS-DSCH physical layer category, # of codes and modulation type.

UL 384/HS: requirement of operators: also to have an increased rate in the uplink, when they have a high rate in downlink provided by the HS-RAB. affects RAB handling, resource handling and mobility handling A RB with 10 ms TTI is selected from the perspective of availability of UEs. In 3GPP there are two alternatives (10 or 20 ms). Qualcoms UE will support 10ms. DoCoMos UEs :20 ms.

A short repetition of channel structure and mobility from HSDPA Basics: HS-DSCH channel carrying DL user data is a shared transport channel and therefore cannot be in Soft/softer HO. We have intra-RNC mobility for this channel called Serving HS-DSCH cell change. A-DCH (Associated Dedicated CH) in DL consists of 3.4 kbps SRB and can be in soft/softer handover. It carries Release 99 signalling to support mobility between HS and non-HS cells. It will be able to carry Voice/video (multi-RAB) in P5.A-DCH UL consists of 384 (or 64) kbps data and + 3.4 kbps SRB + HS-DPCCH and can be in soft/softer handover except HS-DPCCH that only can be in softer since it is terminated in the RBS. It carries Release 99 signalling UL data transmission Voice/video (multi-RAB) HS-DPCCH carries in the UL ACK/NACK for Hybrid ARQ CQI for schedulingHS-SCCH: for control signaling needed for HS-DSCH and it is never in soft handover either.

A short repetition of channel structure and mobility from HSDPA Basics: HS-DSCH channel carrying DL user data is a shared transport channel and therefore cannot be in Soft/softer HO. We have intra-RNC mobility for this channel called Serving HS-DSCH cell change. A-DCH (Associated Dedicated CH) in DL consists of 3.4 kbps SRB and can be in soft/softer handover. It carries Release 99 signalling to support mobility between HS and non-HS cells. It will be able to carry Voice/video (multi-RAB) in P5.A-DCH UL consists of 384 (or 64) kbps data and + 3.4 kbps SRB + HS-DPCCH and can be in soft/softer handover except HS-DPCCH that only can be in softer since it is terminated in the RBS. It carries Release 99 signalling UL data transmission Voice/video (multi-RAB) HS-DPCCH carries in the UL ACK/NACK for Hybrid ARQ CQI for schedulingHS-SCCH: for control signaling needed for HS-DSCH and it is never in soft handover either.

A short repetition of channel structure and mobility from HSDPA Basics: HS-DSCH channel carrying DL user data is a shared transport channel and therefore cannot be in Soft/softer HO. We have intra-RNC mobility for

hsdpa principles

Documents

available transmission

transmission parameters

dedicated channel

power utilization

channel structure2

transmission time interval

hsdpa features

efficient code