Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Date
Presentation / Author
Outline
HSDPA Aktivasi HSDPA di Nokia RAN Parameter HSDPA di Nokia RNC Resource Allocation untuk HSDPA di Nokia RAN
Date
Presentation / Author
HSDPA
Part of 3GPP release 5 specifications System of new physical channels for UTRAN Downlink data rates up to 14.4 Mbit/s per user It uses shared channel concept -Rather than constantly allocating and deallocating dedicated channels to individual users, users share a high bandwidth channel - the HS-DSCH (High Speed Downlink Shared Channel). -It allows the system to operate with a fat pipe Fixed SF16 multicode transmission
Date
Presentation / Author
Fast scheduling
Fast retransmission
To improve QoS data Packets are further compressed and BTS schedules data transmission instead of RNC. Fast interleaving(2ms).
Data retransmission is handled by BTS. UE combines correct bits from original transmission and re transmission (Hybrid ARQ). This provides fastest possible response.
Date
Presentation / Author
16 QAM
(Quadrature Amplitude Modulation)
Q 0001 0000 0011 0010 I
Date
Presentation / Author
1symbol=2 bits 1 channel SF16 in QPSK = (symbol x chiprate)/16 = (2 x 3840)/16 = 480 kbps 1 fat pipe = 5 codes = 5 x 480 x (3/4) = 1.8 Mbps 1symbol=4 bits 1 channel SF16 in 16 QAM = (symbol x chiprate)/16 = (4 x 3840)/16 = 960 kbps 1 fat pipe = 5 codes = 5 x 960 x (3/4) = 3.6 Mbps
Presentation / Author
Date
16 16 QPSK 16 16 16 16QAM 16 16
Note: * In theory
Date
Presentation / Author
2. Fast Scheduling
RNC
Node B
Terminal
ARQ
Decoding
Packets
Soft Buffer
& Combining ACK/NACK & Feedback Generation
Flow Control
Presentation / Author
Schedulers
The scheduler schedules the information that will be sent from the Node B to the UE. The scheduler requires important information from the uplink HS-DPCCH
User History How long has user been waiting Traffic Model What type of traffic model should be used - according to period of the day Peak/Off Peak
QoS and Subscriber Profile Who is the subscriber? Platinum, Gold, Silver, Normal. What type of service is the subscriber allowed? High priority, Best effort
Uplink Feedback CQI and Ack/Nack information Node B buffer status How much data How fast is the data arriving
Scheduler
Users are scheduled according to their requirements for transmission by the Node B over the air interface
Date
Presentation / Author
3. Fast Retransmission
Fast Transmission Time Interval (TTI) reduced from 10 ms to 2 ms
Retransmission between UE and BTS by layer 1 UE and RNC by RLC UE and data server by TCP
Retransmissions handled in BTS in layer 1 Retransmission process Hybrid Automatic Retransmission reQuest (HARQ) Note: HSDPA does not support soft handover
Date
Presentation / Author
HSDPA Activation
Hardware requirements HSDPA requires the following hardware: . In the base transceiver station (BTS), at least one WSPC card is required. . In the radio network controller (RNC), all data and macro diversity combining units (DMCUs) must be of type CDSP-C Software requirements The RNC and BTS software have to be upgraded to RAS05 level for basic HSDPA. The new features require RAS05.1.
Presentation / Author
Date
HSDPA Activation
Activation in RNC 1. Check Service Pool Information 2. Change Pool Allocation based on RNC Capacity step 3. Execute the Pool Change (restart RNC, restart DMPG, or Performed a controlled DMPG state change) Activation in WBTS HSDPA support can be enabled or disabled with a cellspecific management parameter HSDPAenabled.
Date
Presentation / Author
HSDPA Activation
Date
Presentation / Author
DCH + CCH
CCH
R5 DCH+HSDPA
Fixed power is allocated for HSDPA transmissions (HS-DSCH). AMC is used instead of fast PC. Associated UL HS-DPCCH is under fast PC loop. Different power levels for ACK and CQI part. Transmit power of associated DL HS-SCCH is tuned adaptively
Date
Presentation / Author
Shared HSDPA Flow Control Allocation Size SHFCAS Shared HSDPA AAL2 Allocation Size - SHAS
Date
Presentation / Author
WBTS Parameter SharedHSDPAallocation Indicates the guaranteed bit rate in the Iub for HSDPA traffic Reservation only made when the first HSDPA user enters the cell If the DCH reservation is high so that the requested capacity is not available, then the largest possible available capacity will be allocated If new HSDPA users arrive in the cell the reservation will be upgraded if possible to the full value of the configured SharedHSDPAallocation size The value of the parameter depends on the priority required for the HSDPA traffic if HSDPA traffic is not as important as DCH traffic then assign a low value 300Kbps is the recommended minimum size 1Mbps is the recommended size for a 1+1+1 site with only 1 WSPC Mandatory creation parameter Range 0 to 7.2 Mbps in 0.1 Mbps steps
Presentation / Author
Date
WBTS parameter SharedHSDPAFlowControlAllocation Indicates the maximum data rate the RNC may use to send mac-d data on the Iub DCH traffic has strict priority except for the reserved capacity allocated by the SharedHSDPAallocation parameter Initially this parameter could be set at 1.25 X average air interface throughput Maximum value should be Total Iub capacity signalling traffic requirements Too high DCH usage and aggressive setting of SHFCAS will result in mac-d data buffering at AAL2 level Buffer overflow will cause the RLC layer to retransmit data in Ack mode By monitoring HOs and buffer overflows and comparing the retransmission distributions on the mac-hs and RLC layer can provide a rough indication about the feasibility of the SHFCAS setting
Date
Presentation / Author
WBTS parameter NbrOfOverbookedHSDPAUsers The parameter defines the allowed number of MAC-d flows if the Shared HSDPA AAL2 allocation has failed. Value 0 can be used to switch the parameter off The amount of MAC-d flows is not restricted if the HSDPA AAL2 allocation fails and the parameter is not used
Date
Presentation / Author
HSDPA Parameter
TN_RNC_SW_2006_078
TN_3GBTS_SW_2006_0035
HSDPA_Overview
Date
Presentation / Author
4 users
8 users
4 users
One WSPC unit supports max. 3 HSDPA cells. One WSPC unit supports max. 16 HSDPA users. 1) Those 16 HSDPA users can be divided freely between three cells. Packet Scheduler in MAC-hs schedules all users equally regardless of their cell. -> Cells get resources depending on the amount of users and traffic in each. Max. one HSDPA WSPC in BTS -> Max. three HSDPA cells in BTS.
Note 1: The actual amount of supported HSDPA users per WSPC depends heavily on the used Uplink DCH channel speed associated with HSDPA user, see dimensioning rules
Date
Presentation / Author
16 users
16 users
16 users
RAS05.1 The maximum number of HSPDA users served by a single WBTS is increased to 48 (if QPSK modulation is used). The maximum number of HSDPA users per cell is 16. HS-DSCH can be transmitted to all cells in the WBTS at the same time. 1 WSPC per HSDPA-capable cell is needed. One WSPC unit supports one HSDPA cell. One WSPC unit (one cell) supports max. 16 HSDPA users, i.e, there will be maximum 16 users per cell. Packet Scheduler in MAC-hs schedules all users in a cell (RAS05.1) instead of all users in the BTS (RAS05). Cells get resources depending on the amount of users and traffic in each.
Date
Presentation / Author
H-ARQ
Frame Size
High capacity (RAS05.1) Maximum number of HSDPA users per cell: 16 HS-DSCH can be transmitted to all cells in the BTS at the same time
HSDPA
HSDPA with 16 users per cell brings the HSDPA performance gains for each cell independently of the data rate in the other cells in the same BTS
Availability of sufficient baseband processing and transport resources required
Date
Presentation / Author
Carrier InterFace
WAM
WSP
WSP
WSP
WSM
RT-bus
WSC DSC-BUS WSP-C assigned for HSDPA use. handles L1, R-bus MAC-hs and FP WSP WSP WSP WTR WSM
WAF
R-bus
Date
Presentation / Author
WN3.0 Software installed on the BTS Due to the capacity requirements only the WSP-C supports HSDPA At least one WSP-C need to be installed in the BTS to support HSDPA using 5 codes A software update for the WSP-C is required to support HSDPA No changes are required to any other units for HSDPA to be taken into operation and their dimensioning can be done according to the normal guidelines All types of WSP units can be combined in one cabinet All BTS types that can support the WSP-C unit will be able to support HSDPA
Date
Presentation / Author
Processing power on the WSP = Channel Elements 32 CEs are required to handle the 5 code HSDPA implementation (HS-SDCH, HS-SCCH and HS-DPCCH) The 32 CEs for HSDPA will be reserved from one WSP-C only This leaves 32 CEs available for CCH and DCH use. Reservation of the CEs for HSDPA is static and made at BTS start up if the flag is set (HSDPAenabled=1) in the RNC 1 to 3 cells are supported depending on the SW release and customer parameters For RAS05 1 WSP-C will support HSDPA for the whole BTS
Date
Presentation / Author
CEs 32 64 32 16
CEs required for CCHs 8 per cell 16 CEs not reduced for CCHs CEs not reduced for CCHs
Bearer (Kbps)
CEs required
AMR voice
16 32 64 128 384
1
1 2 4 4 16
If all types of WSP units were installed in the same BTS the CCH allocation would follow this priority: 1) All CCHs to WSPA 2) WSPC if WSPA fully loaded or does not exist 3) WSPD if WSPA/C fully loaded or does not exist 4) WSPE if WSPA/C/D fully loaded or does not exist
Date
Presentation / Author
WSPC has 64 CEs 32 CEs for HSDPA -16 CEs for CCHS = 16 CEs left for use by associated channels and AMR channels Using associated channel 16/128 for HSDPA requires 4 CEs from same WSP 16/4 = 4 rem 0 so support for 4 HSDPA users + 0 AMR users Using associated channel 384 requires 16 CEs from same WSP 16/16 =1 rem 0 so support for 1 HSDPA user and 0 AMR users WSPC 1has 64 CEs - 32CEs for HSDPA 16 CEs for CCH s= 16 CEs left for use by associated channels and AMR channels WSPC 2 has 64 CEs by associated channels and AMR channels Using associated channel of 64/128 for HSDPA requires 4 CEs from same WSP WSPC 1 = 16/4 = 4 r 0 WSPC 2 = 64/4 = 16 r 0 RAS05 only supports 16 HSDPA users/NodeB (WSPC 2 fulfills this) and therefore all remaining WSPC 1 CEs must be used for AMR so support for 16 HSDPA users and 16 AMR users Using associated channel 384 requires 16 CEs from same WSP WSPC 1 = 16/16 = 1 r 0 WSPC 2 = 64/16 = 4 so support for 5 HSDPA users and 0 AMR users
Presentation / Author
Date
Date
Presentation / Author
HSDPA carriers
384
576
768
960
1152
1152
1152
Date
Presentation / Author