You are on page 1of 36

RAN1906: Dual-cell HSDPA 42Mbps (On

Top)
Feature functionality, planning and optimisation
GS/MS/NPO/Radio

Soc Classification level
1
© Nokia Siemens Networks

Presentation / Author / Date

DC HSDPA

Background (I)

• The release 8 version of the specifications allow 2 adjacent channels to be
combined to generate an effective HSDPA channel bandwidth of 10 MHz
– Prior to 3GPP Release 8, HSDPA channel bandwidths are limited to 5 MHz
• RU20 implementation of Dual Cell HSDPA is based upon release 8 of
3GPP
– Release 8 version of the specifications allow Dual Cell HSDPA to be combined
with 64QAM but not with MIMO (Release 9 allows combination with MIMO)
Basic Approach

Dual Cell Approach

2 UE, each using 5 MHz RF Channel
Peak Connection Throughput = 28 Mbps
5 MHz

5 MHz

F1

F2

MIMO (28 Mbps), or
64QAM (21 Mbps)
Soc Classification level
2
© Nokia Siemens Networks

Presentation / Author / Date

1 UE, using 2 × 5 MHz RF Channels
Peak Connection Throughput = 42 Mbps
10 MHz
F1

F2

DC HSDPA and
64QAM (42 Mbps)

DC HSDPA

Background (II)

• The release 9 version of the specifications allow 2 non-adjacent channels
(potentially in different operating bands) to be combined to generate an
effective HSDPA channel bandwidth of 10 MHz
– Discussions are ongoing within 3GPP for introducing the capability to combine
4 RF channels to provide a 20 MHz aggregate channel bandwidth

• The combination of multiple RF carriers provides greater flexibility to the
HSDPA Scheduler
– the scheduler can allocated resources in the frequency domain as well as in the
code and time domains
Channel conditions good
on both RF carriers

Channel conditions good
on RF carrier 1

F2

F1

UE1

Soc Classification level
3
© Nokia Siemens Networks

F1

UE1

Presentation / Author / Date

F2

UEx

Channel conditions good
on RF carrier 2

F1

UEx

F2

UE1

DC HSDPA Physical Channels • The primary serving cell provides the full set of physical channels – Inner loop power control is driven by the primary serving cell – HARQ ACK/NACK and CQI are reported to the primary serving cell – Uplink data is sent to the primary serving cell • The secondary serving cell provides only the downlink HS-SCCH and HSPDSCH • The return channel must be HSUPA Downlink Channels HS-SCCH HS-PDSCH F-DPCH HS-SCCH HS-PDSCH Soc Classification level 4 © Nokia Siemens Networks Presentation / Author / Date Uplink Channels E-DPDCH E-DPCCH HS-DPCCH DPCCH Primary RF Carrier Serving cell Secondary RF Carrier Secondary Serving cell .

..w9 b0.a9 5 to 10 bits meaning that coding Channel Channel rate increases from rate 1/3 to rate ½ Coding Coding – Coding is different to MIMO although MIMO can also involve 2 CQI reports and 2 ACK/NACK Soc Classification level 5 © Nokia Siemens Networks Presentation / Author / Date w0.b19 Physical Channel Mapping ..DC HSDPA HS-DPCCH • HS-DPCCH is responsible for signalling • • • • – CQI reports – HARQ ACK/NACK For DC-HSDPA there is a requirement to signal CQI and ACK/NACK information for both cells with the cell pair Physical channel capacity of the HS-DPCCH remains the same so the level of redundancy is reduced ACK/NACK coding is modified to incorporate information applicable to second cell ACK / NACK CQI CQI raw data increases from a0.

Serving Cell Sec. Serving Cell Soc Classification level 7 © Nokia Siemens Networks Presentation / Author / Date . Serving Cell DC-HSDPA UE1 Serving Cell HSPA UE1 Serving Cell HSPA UE2 Sec.DC HSDPA Flexible Configuration • The flexible configuration requires the HSUPA and F-DPCH features to be enabled on both RF carriers belonging to a cell pair • The flexible configuration allows both cells to simultaneously act as: – primary serving HSDPA cell for some DC-HSDPA capable UE – secondary HSDPA serving cell for other DC-HSDPA capable UE – single carrier HSDPA/HSPA serving cell for non DC-HSDPA capable UE – member of the Active Set for other UE Pri. Serving Cell DC-HSDPA UE2 Pri.

DC HSDPA Fixed Configuration • The fixed configuration applies when the HSUPA and F-DPCH features are enabled on only 1 of the 2 RF carriers belonging to a cell pair • In the case of the fixed configuration. Serving Cell • single carrier HSDPA/HSPA serving cell for non DC-HSDPA capable UE • member of the Active Set for other UE Serving Cell HSPA UE1 Serving Cell HSPA UE2 • The RF carrier with HSUPA and F-DPCH disabled can act as: • secondary serving HSDPA cell for DCHSDPA capable UE • single carrier HSDPA/HSPA serving cell for non DC-HSDPA capable UE • member of the Active Set for other UE Soc Classification level 8 © Nokia Siemens Networks Presentation / Author / Date . the RF carrier with HSUPA and F-DPCH enabled can act as: Serving Cell DC-HSDPA UE1 • primary serving HSDPA cell for DCHSDPA capable UE Sec.

DC HSDPA HSDPA Scheduler (I) • A single HSDPA shared scheduler for baseband efficiency is required per DC-HSDPA cell pair • 3 HSDPA shared schedulers are required for a 2+2+2 Node B configuration with DC-HSDPA • Each scheduler is able to serve both HSDPA and DC-HSDPA UE on both RF carriers • Link Adaptation is completed in parallel for each RF carrier HSDPA UE1 on f2 Shared Scheduler per DC-HSDPA cell pair DC-HSDPA UE2 with primary serving cell on f2 HSDPA UE3 on f1 DC-HSDPA UE4 with primary serving cell on f1 Soc Classification level 9 © Nokia Siemens Networks Presentation / Author / Date .

i.e.DC HSDPA HSDPA Scheduler (II) • Round Robin. a UE which is scheduled high throughput in cell 1 (possibly because it is the only active UE) will have a reduced scheduling metric for being allocated resources in cell 2  Traffic balancing Metric Cell1  Shared Scheduler per DC-HSDPA cell pair Soc Classification level 10 © Nokia Siemens Networks Metric Cell2  Presentation / Author / Date TBS Cell1 Average TBS Cell1Cell2 TBS Cell2 Average TBS Cell1Cell2 DC-HSDPA UE . Proportional Fair or PF-RAD-DS schedulers can be used • A scheduler metric is calculated for each RF carrier – The instantaneous Transport Block Size (TBS) is generated separately for each cell by Link Adaptation – The Average TBS is based upon the previously allocated TBS in both cells belonging to the DC-HSDPA cell pair. it represents the total average throughput allocated to the UE • Thus.

DC HSDPA HSDPA Scheduler (III) • Single cell and dual cell • • • • users are scheduled in fair manner simultaneously in both cells. Based on cell specific scheduling decisions per TTI. Fairness of a dual cell user takes into account the scheduling decisions in both cells. the DC user can be scheduled in none of the cells. Single cell Tx for UE2 on TTI5 UE2 Es/No UE2 DC UE1 Es/No f1 Soc Classification level 11 © Nokia Siemens Networks TTI 5 UE3 UE1 SC . Proportional fair scheduler decides the scheduled users on each cell separately per TTI Dual Cell HSDPA user is included in scheduling in both cells. in one of the cells or in both of the cells. TTI 1 UE3 TTI 2 UE2 UE2 Es/No TTI 3 UE3 TTI 4 UE2 Presentation / Author / Date Scheduled user on f2 UE3 Es/No UE3 SC f2 TTI 1 UE1 TTI 2 UE2 TTI 3 UE1 TTI 4 UE2 TTI 5 UE2 Scheduled user on f1 Dual cell Tx for UE2 on TTI 2 and TTI 4.

cell) priority queue (per MAC-d flow) Soc Classification level 12 © Nokia Siemens Networks Presentation / Author / Date HARQ process . Cell) Adaptation of TBS according to HARQ rate Shared Scheduler: Proportional Fair (per cell)/Round Robin (per cell) Shared functionality per DC cell pair Separate functionality per DC cell ACK1/NACK1. CQI2 report transmission (HSDPCCH in serv.DC HSDPA HSDPA Scheduler (IV) HS-DPCCH (Serv. ACK2/NACK2 transmission (HS-DPCCH in serv. cell) Link adaptation CQI1.

DC-HSDPA activation DC HSDPA • Allocation of DC HSDPA is tried always when it is possible – When existing algorithms trigger channel type switch from DCH to HS-DSCH (DL) or from DCH to E-DCH (UL) – In fixed DC HSDPA configuration UE is currently in potential primary cell – PS NRT service • DC HSDPA can be configured to the UE by including Downlink secondary cell info FDD IE into one of the following messages – Active Set Update – Cell Update Confirm – Physical Channel Reconfiguration – Radio Bearer Reconfiguration – Radio Bearer Setup – RRC Connection Setup – Transport Channel Reconfiguration • DC HSDPA configuration is removed from the UE by leaving out the Downlink secondary cell info FDD IE from the RRC messages Soc Classification level 13 © Nokia Siemens Networks Presentation / Author / Date .Channel type selection.

Supported RAB Combinations DC HSDPA • DC-HSDPA is not allocated to a standalone SRB • DC-HSDPA supports up to 3 Interactive or Background RAB mapped to HSPA – Streaming RAB can be configured but must be inactive (mapped to DCH 0/0 kbps instead of HSPA) – A maximum of 4 MAC-d flows per UE can be configured – Establishment of a conversational or streaming RAB triggers the release of the DC-HSDPA configuration – DC-HSDPA can be configured after the release of a conversation or streaming RAB Soc Classification level 14 © Nokia Siemens Networks Presentation / Author / Date .

Connection Establishment DC HSDPA • RRC Connection Request message includes a flag to indicate whether or not the UE supports DC-HSDPA • RRC Connection Setup Complete message includes UE HSDPA Category information Used by network when DC-HSDPA is disabled Used by network when DC-HSDPA is enabled Soc Classification level 15 © Nokia Siemens Networks Presentation / Author / Date .

DC-HSDPA UEs away from DC-HSDPA layer Service and load based HO and HSPA capability based handover are not triggered when DC-HSDPA is allocated for the UE DC-HSDPA can not be active during HSDPA inter-frequency handover – DC-HSDPA requires HSUPA DCellHSDPAFmcsId identifies the measurement control parameter set (FMCS object) controlling the intra-frequency measurements of a user having DC HSDPA allocated .Mobility with DC-HSDPA layer DC HSDPA • Directed RRC connection setup (for HSDPA) (IDLE  CELL_DCH) • • • • • – DC-HSDPA UE to primary DC-HSDPA layer (F-DPCH and HSUPA enabled) HSPA layering for UEs in common channels (CELL_FACH  CELL_DCH) – DC-HSDPA UE to primary DC-HSDPA layer DC-HSDPA Capability Based Handover (CELL_DCH) – DC-HSDPA UE to DC-HSDPA layer – Non.Proposal – The RNC uses periodical intra-frequency CPICH Ec/No and RSCP measurement when HS-DSCH is allocated for the RRC connection ?? (More details in Multilayer planning guideline and presentation) Soc Classification level 16 © Nokia Siemens Networks Presentation / Author / Date .

Number of HSPA users DC HSDPA • DC HSDPA user is counted only in the primary cell • HS-DSCH MAC-d flow of the certain DC HSDPA user is counted only in the primary cell • SC HSDPA and certain DC HSDPA user are counted once per scheduler – new RNW-parameter MaxNumbHSDPAUsersS is used for defining the maximum allowed number of SC HSDPA and DC HSDPA users in the scheduler – max two cell per scheduler with DC HSDPA Soc Classification level 17 © Nokia Siemens Networks Presentation / Author / Date .

Shared Scheduler for Baseband Efficiency. HSUPA • The dual cell HSDPA feature is optional and requires a long term RNC license for a specific number of cells Soc Classification level 18 © Nokia Siemens Networks Presentation / Author / Date . HSDPA 15 codes. HSDPA 14 Mbps per User. Downlink Flexible RLC.Requirements DC HSDPA UE Requirements • UE must support dual cell HSDPA Network Hardware Requirements • Flexi Node B must have release 2 hardware • UltraSite Node B must have EUBB • RNC must be equipped with CDSP-DH cards Feature Requirements • The following features must be enabled: • Fractional DPCH.

306 • HSDPA UE categories 21 to 24 support DCHSDPA • Maximum transport block sizes are supported by UE categories 22 and 24 • Maximum transport block sizes are the same as those used for MIMO • Peak throughput of dual cell HSDPA equals peak throughput of dual stream MIMO (when using same modulation scheme) Soc Classification level 19 © Nokia Siemens Networks Presentation / Author / Date . 8 version of 3GPP TS 25.UE Categories DC HSDPA Extracted from Rel.

84 Mcps • Spreading Factor = 16 => Symbol Rate = 240 ksps • Number of HS-PDSCH codes = 15 => Aggregate Symbol Rate per RF Carrier = 3.096 Mbps • Number of Transport Blocks = 2 => Bit Rate = 42.6 Mbps • Number of RF Carriers = 2 => Bit Rate = 43.6 Mbps • Number of bits per Symbol = 6 => Aggregate Bit Rate per RF Carrier = 21.192 Mps (peak) Presentation / Author / Date Soc Classification level 20 © Nokia Siemens Networks coding rate of 0.2 Mbps (peak) Physical Layer (based upon UE maximum transport block size) • Category 24 maximum transport block size = 42 192 bits • Transmission Time Interval = 2 ms => Bit Rate per transport block = 21.98 .DC HSDPA DC-HSDPA Throughputs (I) Physical Layer (based upon Physical Channel capability) • Chip Rate = 3.

or 16 bits without the TSN and SI Segmentation Index (SI) – 2 bits Length (L) – 11 bits Flag (F) – 1 bit • TSNn and SIn fields are only required if LCH-Idn <> LCH-Idn-1 Total header size = 72 bits when MAC-ehs PSU accomodates 4 re-ordering PDU with the same LCH-Id TSN1 LCH-ID1 L12 SI1 F1 LCH-ID2 L2 F2 LCH-ID3 L3 F3 L4 LCH-ID4 Maximum transport block size = 42192 bits. Maximum RLC PDU size = 11216 bits So total RLC payload size = 3 × 11216 + 8472 = 42120 bits Soc Classification level 21 © Nokia Siemens Networks Presentation / Author / Date F4 .DC HSDPA MAC-ehs PDU • MAC-ehs header fields – – – – – Logical Channel Identifier (LCH-ID) – 4 bits Transmission Sequence Number (TSN) – 6 bits 24 bits total.

032 Mbps Soc Classification level 22 © Nokia Siemens Networks Presentation / Author / Date DC HSDPA .7 % => Application throughput = 36.43 Mbps Application Layer (based upon TCP/IP protocol stack) • IP header size = 20 bytes • TCP header size = 36 bytes • MTU Size = 1500 bytes => TCP/IP overhead = 3.056 Mbps • MAC-ehs re-transmission rate = 10 % • RLC re-transmissions rate = 1 % => Net Bit Rate = 37.DC-HSDPA Throughputs (II) RLC Layer (based upon maximum transport block size payload) • Maximum transport block size payload = 2 × 42120 bits • RLC header size per transport block = 4 × 16 = 64 bits => RLC payload = 2 × 42056 bits • Transmission Time Interval = 2 ms => Peak instantaneous bit rate = 42.

Reported CQI • UE categories 21 to 24 are specified to use CQI mapping tables C and D when 64QAM is not configured • Otherwise CQI mapping tables F and G are used Soc Classification level 23 © Nokia Siemens Networks Presentation / Author / Date DC HSDPA .

DC HSDPA CQI Reporting (III) Table F • CQI mapping tables do not include the maximum transport block sizes • Table F does not include the use of 15 codes • Node B is left with the decision of when to schedule the maximum transport block sizes Soc Classification level 24 © Nokia Siemens Networks Presentation / Author / Date Table G .

DC HSDPA Performance • DC-HSDPA improves user bit rates and cell capacity by allowing dynamic usage of two HSDPA carriers for a HSDPA user • Improvement is due to multiple mechanisms – Higher peak bit rate via combination of bit rate of two carriers – Cell capacity gain via statistical multiplexing of larger number of users – Performance improvement in fading conditions by frequency selective scheduling and carrier specific link adaptation  separate CQI for both carriers Soc Classification level 25 © Nokia Siemens Networks Presentation / Author / Date .

4 10th 0.5 1 1.23 2xSC. mean = 1. mean = 1.480 28 50th 0. 2Rx.1 0 DC. 18 DC 2xSC DC 2xSC 20 . 2Rx.6 PedA. DC (Mbps) DC Gain (%) 0.7 cdf 0.35 DC.5 4 DL user throughput (Mbps) Soc Classification level 26 © Nokia Siemens Networks Presentation / Author / Date 4. 0. PedA. PedB. 1.8 0. mean = 1. mean = 1.5 3 3.2 PedA. 2xSC (Mbps) PedA.04 10 8 4 0. PedB.8-2 Mbps throughput increase) 2 0 0 18-24% cell throughput gain from DC at 20 PedA UEs 6 5 2 4 6 8 10 PedA PedA PedA PedA 12 number of users 14 16 1Rx.5 (ca. 1Rx.64 2xSC.9 12 mean DL cell throughput (Mbps) 0.219 28 90th 3.950 1.672 18 0.3 0. 2Rx MMSE) 14 0.114 3.374 0.5 2 2.5 Percentile 0.DC HSDPA Cell edge throughput and capacity • DC HSDPA compared to two separate carriers • Example simulation results show >25% increase on cell edge throughput and >20% on cell throughput Throughput Gain over entire Cell Range (8 users) 1 Receiver Diversity Gain (1Rx MMSE vs.

8 0.42 2xSC MIMO. mean = 12.9 0.7 •DC HSDPA gain 22% •MIMO gain 18% cdf 0.5 0. mean = 12. coverage gain decreasing with cell load additional spatial signal dimension.6 0. MIMO Performance (PedA. mean = 10. margin in other cells throughput gain uniformly mappable to + coverage gain of DC UEs over cell area _ Soc Classification level 27 © Nokia Siemens Networks Presentation / Author / Date throughput gain not uniformly mapped to coverage gain over cell area .DC HSDPA Performance comparison to MIMO • DC and MIMO offer a similar sector DL throughput increase Comparative DC vs. margin in secondary cell.71 2xSC.4 0.1 0 0 5 10 15 20 25 DL cell throughput (Mbps) • The mapping of DC and MIMO throughput increase onto cell range gain occupied by different cost & performance factors DC MIMO + no/negligible additional HW/SW cost _ antenna & HW cost (if not provided) _ rise of interf.2 DC. 8 users) 1 0.27 0. no + rise of interf.3 0.

belong to the same sector and have the same Tcell value • WCEL . If it is not possible to enable DC HSDPA for a new cell then the cell setup does not succeed and error is printed out.Tcell parameter defines the start of SCH.UARFCN parameter defines the downlink channel number and the downlink carrier frequency of the cell • WCEL .SectorID parameter gives a unique identifier to a sector of the base station where the cell belongs to • WCEL . Primary CCPCH and DL Scrambling Code(s) in a cell relative to BFN Soc Classification level 28 © Nokia Siemens Networks Presentation / Author / Date .DC HSDPA Enabling the Feature (I) • The DCellHSDPAEnabled parameter must be set to enabled for both cells belonging to the cell pair Range Name 0 (Disabled). • Two cells form a potential DC HSDPA cell pair when they have adjacent RF carriers. CPICH. 1 (Enabled) DCellHSDPAEnabled (WCEL) Default 0 (Disabled) Description The parameter indicates whether or not the DC HSDPA feature is enabled in the cell. the system checks that the maximum amount of DC HSDPAcapable cells is not exceeded. Before the feature is enabled in the cell.

bit rate based on UE capability. (RNC) 65535 (no restriction) Default Description 65535 The parameter can be used to limit the maximum bit rate of NRT MAC-d flow. is 42112 kbps If the value 65535 is used. max. Soc Classification level 29 © Nokia Siemens Networks Presentation / Author / Date . is 9600 kbps .42112. Value of the parameter is compared to the user bitrate excluding MAC-hs header.license for HSDPA 15 Codes.license for HSDPA 15 Codes and 10Mbps per User. max. Maximum value depends on the features licensed: . max. max. This parameter does not limit the max. max.license for HSDPA 15 Codes and 64QAM. is 3456 kbps . is 6784 kbps . max. activated HSDPA bit rate features and the value of this parameter.license for HSDPA 15 Codes and 14Mbps per User. bit rate of RAB. is 21120 kbps . max. The bit rate used in the reservation of resources for the MAC-d flow is the minimum of max. is 13440 kbps . RLC header and padding (includes just RLC PDU payload).no license for HSDPA 15 Codes. step 128. instantaneous air interface bit rate. then this parameter does not restict the maximum bit rate.license for DC HSDPA..DC HSDPA Enabling the Feature (II) • The MaxBitRateNRTMACDFlow parameter should be configured to 42112 kbps (or 65535) to allow the peak throughput Name Range MaxBitRateNRTMACDFlow 128.

must be same as that used for HSUPA) • The HSPAQoSEnabled parameter must be configured with the same value in both cells of a cell pair Soc Classification level 30 © Nokia Siemens Networks Presentation / Author / Date .Enabling the Feature (III) DC HSDPA • HSDPA serving cell change must be enabled using the HSDPAMobility parameter • Downlink Flexible RLC must be enabled using the FRLCEnabled parameter • HSDPA 14 Mbps per User must be enabled using the HSDPA14MbpsPerUser parameter • The HSDPA 15 codes feature must be enabled with at least a 10 code license and these codes must be enabled using the HSPDSCHCodeSet parameter • HSUPA must be enabled for at least one of the RF carriers using the HSUPAEnabled parameter • F-DPCH must be enabled for at least one of the RF carriers using the FDPCHEnabled parameter (if enabled for only one RF carrier.

DC HSDPA SectorID Configuration • Cells which are paired for DC-HSDPA must belong to the same sector SectorID = 1 SectorID = 3 SectorID = 2 RF Carrier 2 SectorID = 1 RF Carrier 1 Soc Classification level 31 © Nokia Siemens Networks Presentation / Author / Date SectorID = 3 SectorID = 2 .

DC HSDPA Tcell Configuration (I) Tcell Groups • Group 1: Tcell values 0. 7. 4. 1. 2 • Group 2: Tcell values 3. 8 • Group 4: Tcell value 9 • 2+2+2 Node B with DC-HSDPA requires: • each cell belonging to the same sector must have the same Tcell value • Tcell values belonging to different sectors must belong to different Tcell groups Tcell = 0 • Configuration requires 3 HSDPA Efficient Baseband Schedulers Tcell = 3 RF Carrier 2 • RF carriers 1 and 2 must be Tcell = 0 adjacent RF Carrier 1 Soc Classification level 32 © Nokia Siemens Networks Presentation / Author / Date Tcell = 6 Tcell = 6 Tcell = 3 . 5 • Group 3: Tcell values 6.

DC HSDPA Tcell Configuration (II) • 3+3+3 Node B with DC-HSDPA requires: • each DC-HSDPA cell belonging to the same sector to have the same Tcell value Tcell = 0 • DC-HSDPA Tcell values belonging to different sectors must belong to different Tcell groups Tcell = 2 RF Carrier 3 Tcell = 3 • Configuration requires 4 HSDPA Efficient Baseband Schedulers • RF carriers 1 and 2 must be Tcell = 1 Tcell = 6 Tcell = 9 RF Carrier 2 adjacent Tcell = 3 • Cells belonging to RF carriers 1 and 2 must be within the same LCG • Cells belonging to RF carrier 3 must be within a second LCG Soc Classification level 33 © Nokia Siemens Networks Presentation / Author / Date RF Carrier 1 Tcell = 6 Tcell = 9 .

Connection Establishment (I) DC HSDPA • RRC Connection Request message includes a flag to indicate whether or not the UE supports DC-HSDPA • RRC Connection Setup Complete message includes UE HSDPA Category information Used by network when DC-HSDPA is disabled Used by network when DC-HSDPA is enabled Soc Classification level 34 © Nokia Siemens Networks Presentation / Author / Date .

lowest parameter values of cells forming scheduler shall be used. SC HSDPA and DC HSDPA user is a user that has one or more HS-DSCH MAC-d flows established. they do not impact the number of connections within the Secondary Serving Cell • The MaxNumberHSDPAUsers parameter defines the maximum number of HSDPA connections per cell • The MaxNumbHSDPAUsersS parameter defines the maximum number of HSDPA connections per scheduler Name Range MaxNumbHSDPAUsersS 1 to 511. step 1. RNC does not exceed the maximum number but admission of SC HSDPA and DC HSDPA user is inhibited in the scheduler if the maximum number is to be exceeded. 0 (unrestricted) (WCEL) Soc Classification level 35 © Nokia Siemens Networks Presentation / Author / Date Default 0 Description Defines the maximum number of SC HSDPA and DC HSDPA users in the MAC-hs/ehs specific BTS scheduler. i.e. This parameter is defined per cell and because scheduler consists of several cells.Maximum Number of Connections (I) DC HSDPA • DC-HSDPA connections are only counted within the Serving Cell. Certain SC HSDPA and certain DC HSDPA user are counted once per scheduler. .

i. HS-DSCH MAC-d flow of the certain SC HSDPA and DC HSDPA user is counted once per scheduler.Maximum Number of Connections (II) DC HSDPA • MAC-d flows are only counted within the Serving Cell. 0 (unrestricted) (WCEL) Soc Classification level 36 © Nokia Siemens Networks Presentation / Author / Date Default 0 Description Defines the maximum allowed number of HSDSCH MAC-d flows of SC HSDPA and DC HSDPA users in the MAC-hs/ehs specific BTS scheduler. lowest parameter values of cells forming scheduler shall be used. they do not impact the number of MAC-d flow within the Secondary Serving Cell • The MaxNumbHSDSCHMACdFS parameter defines the maximum number of MAC-d flows per scheduler Name Range MaxNumbHSDSCHMACdFS 1 to 1023. This parameter is defined per cell and because scheduler consists of several cells. Each HS-DSCH MAC-d flow of each SC and DC HSDPA user is counted when the total number of HS-DSCH MAC-d flows in the scheduler is calculated. step 1. RNC does not exceed the maximum number but admission of SC HSDPA and DC HSDPA user is inhibited in the scheduler if the maximum number is to be exceeded. .e.

step 1 0 to 300.DC HSDPA Power Saving Mode • DC-HSDPA has an impact upon the Power Saving Mode for BTS (RAN955) • The number of DC HSDPA users in a cell must be lower than or equal to the value of the PWSMSDLimitDCHSDPA parameter before shutdown is possible • Each DC HSDPA user is counted separately in the primary and secondary cells • This new criteria is an addition to the existing crieteria. . and all criteria must be fulfilled to shutdown a cell • The PWSMAVLimitDCHSDPA parameter defines the corresponding threshold for activating a cell in terms of the minimum number of DC-HSDPA capable UE Range Name PWSMSDLimitDCHSDPA (WCEL) Range Name PWSMAVLimitDCHSDPA (WCEL) Soc Classification level 37 © Nokia Siemens Networks 0 to 300. Default 10 Description This parameter defines the limit for DC HSDPA user amount for cell activation decision. step 1 Presentation / Author / Date Default 5 Description This parameter defines the limit for DC HSDPA user amount for cell shutdown decision.