HSUPA (E-DCH) introduction & parameters Jens Kuhr – Network Engineering COO RA RD SA NE
For internal use 1 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Outline HSUPA Channels HSUPA Scheduling mechanism HARQ Process HSUPA RAB-Handling HSUPA Mobility aspects HSUPA Admission Control HSUPA Congestion Control HSUPA OLPC UE categories + E-TFCI selection
For internal use 2 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Outline HSUPA (High Speed Speed Uplink Packet Packet Access) is used to improve improve uplink uplink data rates in • HSUPA WCDMA networks. using enhanced techniques (e.g. • It is reusing the available infrastructure by using adaptive coding) thus allowing to make better use of the available ressources. peak rates and increases coverage coverage for high datarates • Provides higher peak WCDMA network more interesting interesting • Shorter round trip times (RTT) make the HSPA WCDMA for real time applications like online gaming dedicated transport channel in uplink (E-DCH), (E-DCH), unlike • HSUPA uses an enhanced dedicated HSDPA, where only one downlink channel is shared among the users. HSUPA is specified specified for data rates of up to 5.76 Mbps • HSUPA
For internal use 3 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Comparison between HSUPA and HSDPA Similarities with HSDPA: - NodeB controlled scheduling - HARQ process - Shorter TTI than classic DCH (10ms, 2ms (HSDPA 2ms TTI only)) - Fast link adaptation techniques
Differences to HSDPA: - dedicated channel (E-DCH) instead of shared channel in HSDPA - no adaptive modulation - full mobility (soft handover possible)
Like HSDPA, HSUPA is based on scheduling in the NodeB, link adaptation and HARQ process For internal use 4 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
In UMR and RAS currently only 10ms TTI implemented.
HSUPA Princ Principles iples
1-4 Code Multi-Code transmission
TTI TTI = 2 / 10 10 ms
Hybrid ARQ with incr. redundancy
Fast Power Control
Benefit Higher Uplink Peak rates: 2-5.76 Mbps Higher Capacity: +50-100% Reduced Latency: ~50-75 ms
For internal use 5 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduling
HSPA Scheduling
- A H C D - B H C D - C H C D
Node B Rel. 99
Dedicated pipe for every UE
i n g l u d h e c S
- A
B H C D E H C D E
C , B , A
Node B w/ HSDPA HSDPA 3GPP Rel. 5
Fast pipe is shared among UEs For internal use 6 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
H C D E
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
- C
Node B w/ HSUPA 3GPP Rel. 6
Dedicated pipe for every UE in UL Pipe (codes and grants) changing with time E-DCH scheduling
HSUPA Channels - Uplink
For internal use 7 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Channel mappin mapping g introduced as a new transport transport channel • For HSUPA, the E-DCH is introduced for carrying user data on the uplink.
• On physical layer, this translates translates into 2 new uplink uplink channels.
E-DCH
E-DPDCH
For internal use 8 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Transport channel
E-DPCCH
Physical channel
E-DCH: Enhanced Dedicated Channel Dedicated uplink transport channel • Dedicated uplink
• Dedicated to 1 UE • 2ms or 10ms TTI • Controlled by NodeB scheduling process • Holds one or more dedicated physical data channels (E-DPDCH)
For internal use 9 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DPDCH: E-DCH Dedicated Physical Data Channel uplink physical channel • Dedicated uplink 10ms TTI TTI • 2ms or 10ms
• Controlled by NodeB NodeB scheduling process • The E-DPDCH E-DPDCH is used by E-DCH for the transmissi transmission on of user data and Scheduling information (SI) E-DPDCH per radio link link for higher throughpu throughputt • Up to 4 E-DPDCH handover • Supports soft handover
For internal use 10 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DPCCH: E-DCH Dedicated Physical Control Channel Dedicated uplink physical channel. • Dedicated uplink
• Transmits control information about the E-DPDCH transmission: – E-TFCI (Transport block format combination indicator) – RSN (Retransmission sequence number) for the HARQ process – Happy Bit
• There is at most one E-DPCCH on each radio link. • Carries the „Happy Bit“
For internal use 11 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
With the Happy Bit the UE tells the NodeB scheduler every 2ms whether the ressource allocation was sufficient to transmit all data or not.
E-DPDCH & E-DPCCH
E - -D P D D P C D H C H ( u us s
e er r d d a at t a a, S I I) )
E - -D P D C ( c P C co n C H o nt t r C H ro l l d o d a at t a a, e .g H H a ap p p py B y B i it t ) )
For internal use 12 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH serving cell • E-DCH and HSDPA serving link is always assigned by RNC to the same cell (Best Cell) based on UE measurements.
NodeB 1
Non Serving RLS (1 RL)
NodeB 2
Serving RLS Serving E-DCH Cell
same RG information information (per RLS)
RG information per RL HICH information per RLS
same HICH information information (per RLS)
E-HICH E-AGCH E-RGCH
For internal use 13 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA Channels - Downlink
For internal use 14 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-AGCH: E-DCH Absolute Grant Channel • Common downlink physical channel channel • Time-multiplexed shared channel with explicit UE addressing addressing using ERNTI
• On the E-AGCH, E-AGCH, the NodeB NodeB tells the UE an absolute power absolute power level (alsolute grant, AG) AG ) for the E-DPDCH relative the DPCCH (precise value, thus also more information to be transmitted)
• In soft handover handover state, state, the E-AGCH E-AGCH is transmitted by the serving E-DCH cell only
• Uses SF256 E - - AG C C H H ( a ab b
s so ol l u t t e u p e p w wr r ) )
E - -R R G GC CH ( H u u p p
,d o o w wn , h o o l ld ) d )
E - -D P D D P C D H C H
( u us e r r d d at a) For internal use 15 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
d ) l d w n, h o o d ( C H
E - R G
D C H E - D P t a a )
d a ( u s e r
E-AGCH: primary & secondary absolute grant allocated (primary (primary & secondary secondary E-RNTI) E-RNTI) that it needs • An UE can get two E-RNTIs allocated to listen to on the E-AGCH. follows the AG transmitted transmitted for the primary primary E-RNTI (primary (primary AG). • The UE always follows – It can be commanded commanded to follow the AG transmitted transmitted for the secondary secondary E-RNTI E-RNTI as well.
mechanism can be used to control a group of UEs together (which (which will then • This mechanism all have the same secondary E-RNTI assigned) – E.g. group of “always on” UEs, that only occasionally send data – They will then be controlled controlled as a group by a limited “secondary “secondary AG” AG” – If one of that UE that UE have needs to send more uplink data , it will then get an primary an primary grant assigned grant assigned via the primary R-RNTI.
– As soon the primary primary grant is not needed anymore, anymore, the UE can be switched to secondary grant again.
For internal use 16 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-AGCH power settings in RNC Name
Q3-Name
Shortname
Longname
LMT-Name
Type
Range
Unit
R/ W
Default
E-AGCH Power Offset
sbs3gRanAg chPwrOffset
AGCHPWR OFF
agchPower Offset
po_agch
Integer
0..255 (0..2.55)
LMT: dB
RW
128 (RC)
Mapping to -32..+31.75 by step of 0.25 Indicates the Power offset relative to the pilot bits on the DL DPCCH
Example of command execution (hmi): cre hsupa cellid=1 hsupa cellid=1 nodebid=1 no_rgch_hich=4 po_agch=1.25 no_rgch_hich=4 po_agch=1.25 po_hich=1.25 po_hich=1.25 po_rgch=1.25 pr_edch=30
For internal use 17 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
RC: 0.01*d B
1.28 (LMT)
Scheduler in NodeB, O&M parameter description Name
Range
Unit
R/W
Default
hsupaPowerOffsetEAGCH
Range: -32..31.75
dB
V
76 (-13 dB)
Step: 0.25 Mapped in database to range 0..255 Power offset of E-AGCH (secondary (secondary E-RNTI) (configurable only at CHC start-up start-up time). Relative to CPICH power. Vendor power. Vendor parameter: not recommended to be changed by the operator. Name
Range
Unit
R/ W
Default
maxSecondAbsGrant
Value range: [0…31]
-
R
5
5 ~ 32 kbps 9 ~ 128 kbps 9 shall not be exeeded
index value of 3GPP 25.212, section4.10.1A.1, table 16B Upper limit to the Secondary AG that may be assigned to all UEs in a radio cell. When doing RTT ("ping") measurements, note that the default value of 5 will have negative impacts on the RTT, as it does not allow a ping of 32 bytes to be sent within one MAC-e PDU: 2 PDUs are needed. To have an optimal RTT, either ensure that you have a Primary Grant active or set this value to a minimum of 7. Name maxNumberPrimaryGrantUe
Range 0..255
Unit
R/W
Default
-
V
4
Example of command execution (xml):
Maximum number of simultaneous UEs with Primary_Grant_Available = “True” Vendor parameter: not recommended to be changed by the operator.
">
Name
Range
Unit
R/W
Default
">
ueInactivityTimer
0..1023
-
V
25
label="maxNumberPrimaryGrantUe label="maxNumberPrimaryGrantUe">
"/>
The info shall provide a time constant for UE inactivity detection. It indicates the number of idle subframes after that a UE’s Serving Grant may be set to zero and the UE may be switched from state Primary_Grant_Available = “True” to “False”. ms Vendor parameter: not recommended to be changed by the operator. equals to 2ms * 25 = 50 ms Vendor For internal use 18 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
"> "/>
E-RGCH: E-DCH Relative Grant Channel • • • • •
Dedicated downlink downlink physical channel channel Additional to the E-AGCH channel Used by the NodeB to transmit transmit relative relative grants (RG) for the the UL E-DPDCH channel channel Relative Relative grants are are UP, DOWN and HOLD HOLD commands commands In soft handover handover state, the E-RGCH E-RGCH can be transmitted transmitted by every cell in the AS set can send UP, DOWN, HOLD – cells in the serving E-DCH link set – other cells can send only DOWN and HOLD HOLD
• For the Serving the Serving E-DCH RLS RLS there there is always one always one logical RG information RG information but it is transmitted in each cell belonging to the serving RLS to allow the UE a softer combining.
• For Non Serving Serving RLS(s) RLS(s) the RG informatio information n is per RL • Requires much lower signaling overhead than E-AGCH • Uses SF128
Serving E-DCH radio link set: Cells belonging to the NodeB that transmits the Serving E-DCH
Serving E-DCH RL E - - AG C CH ( a H a b b
s so ol l u t te u p e p w wr r ) )
E - -R RG C G C H H ( u up p
,d o o w wn , h o ol l d ) d )
E - -D P D D P C D H C H
( u us e r r d d at a) For internal use 19 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
C H E - R G
d ) , h o l d ( d o w n
D C H P D E a ) t a
d a ( u s e r
E-RGCH power settings in RNC Name
Q3-Name
Shortname
Longname
LMT-Name
Type
Range
Unit
R/ W
Default
E-RGCH Power Offset
sbs3gRanRgch PwrOffset
RGCHPWRO FF
rgchPowerOff set
po_rgch
Integer
0..255 (0..2.55)
LMT: dB
RW
128 (RC)
Mapping to -32..+31.75 by step of 0.25
RC: 0.01*dB
1.28 (LMT)
Indicates the Power offset relative to the pilot bits on the DL DPCCH Name
Q3-Name
Shortname
Longname
LMT-Name
Type
Range
Unit
R/ W
Default
Number of ERGCH/E-HICH
sbs3gRanNoRg chHich
NORGCHHIC H
numberErgch Ehich
no_rgch_hich
Integer
1,..,4
-
RW
-
Number of E-RGCH/E-HICH
Example of command execution (hmi): cre hsupa cellid=1 hsupa cellid=1 nodebid=1 no_rgch_hich=4 no_rgch_hich=4 po_agch=1.25 po_agch=1.25 po_hich=1.25 po_hich=1.25 po_rgch=1.25 pr_edch=30 po_rgch=1.25 pr_edch=30
For internal use 20 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-RGCH power settings in NodeB Name
Range
Unit
R/W
Default
hsupaPowerOffsetErgch
Range: -32..31.75
dB
V
112 (-4 dB)
Step: 0.25 mapped in database to range 0..255 Power offset of E-RGCH of UEs having a non-serving RLS in this NodeB relative to CPICH (configurable only at CHC start-up time) Vendor parameter: not recommended to be changed by the operator.
Example of command execution (xml): class="LocalCellE"> "> "/>
For internal use 21 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-RGCH: Condition for sending RG DOWN commands non-serving RG DOWN DOWN commands when: when: • A cell may send non-serving – Experienced total RTWP > Target RTWP signalled by CRNC – && – Non-serving E-DCH to total E-DCH power ratio > Target ratio
from Non-serving E-DCH to total E-DCH power ratio is the ratio of power from UEs for which this cell is a non-serving RL and RL and the total the total E-DCH power E-DCH power . R Target RTWP is calculated from HSUPA_schedule HSUPA_scheduler_offset r_offset T W P
Congestion Level (N_ul+CCThreshold) Congestion Level – CC Hysteresis HSUPA Scheduler Offset
Maximum Target RTWP Current Cell Load
TIME For internal use 22 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Condition for sending RG DOWN commands RNC parameters Name
Q3-Name
Shortname
Longna me
LMT-Name
Type
Range
Unit
R/ W
Default
Target Nonserving EDCH to Total E-DCH Power ratio
sbs3gRanTa rgNonServE dchPwrRat
TRGTNSEDC HPRAT
targetNo nServEd chTotEd chPwrR at
pr_edch
Integer
0,..,100
%
RW
30
Target Non-serving E-DCH to Total E-DCH Power ratio. This parameter can be updated only when HSUPA is not Active.
Name
Q3-Name
Shortname
Longna me
LMTName
Type
Range
Unit
R/ W
Default
HSUPA_sc heduler_off set
sbs3gRanH supaSched Off
SCHDOFF SHSUPA
schedule rOffsetHs upa
hsupa_oft
LMT: Real RC: Integer
LMT: 0..10 step by 0.1 RC: 0..100
LMT : dB RC: 0.1* dB
R W **)
LMT: 0.5 RC: 5
Offset value to calculate Maximum Target Received Total Wide Band Power
Example of command execution (hmi): cre hsupa cellid=1 hsupa cellid=1 nodebid=1 no_rgch_hich=4 po_agch=1.25 po_hich=1.25 po_rgch=1.25 pr_edch=30 po_rgch=1.25 pr_edch=30 cre cell cctl cellid=1 cctl cellid=1 nodebid=1 ul_cngt=10.0 ul_cngh=2.0 dl_cngt=0.90 dl_cngh=0.15 mmti_rtwbp=10.00 mmti_tcp=10.00 k=1 ebd=ena etpchr=ena peri_cngh=0.5 mmfc_rtwp=0 mmfc_tcrp=0 cc_emg=false hsupa_oft=0.5 hsupa_oft=0.5 For internal use 23 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Condition for sending RG DOWN commands NodeB parameters Name
Range
Unit
R/W
Default
targetRatioOtherRlEdchPower
Value range: 0..100%
%
V
50
Unit: % Step: 1%
Target ratio of average E-DCH powers per UE of Other E-DCH RLs within Serving RLS for scheduling of Internal Relative Grants. Vendor parameter: not recommended to be changed by the operator.
• For balancing of traffic load from UEs with different serving RLs between the cells of a Node B, a target ratio for the average non-serving E-DCH power of these UEs shall be provided. Example of command execution (xml): class="LocalCellE"> "/> For internal use 24 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-HICH: E-DCH HARQ Indicator Channel physical channel • Dedicated downlink physical Carries the HARQ ACK/ NACK NACK messages messages for the UL E-DCH • Carries transmitted by all cells in the active set. UE continues continues to transmit on • Is transmitted E-DPDCH as long there is at least one ACK. always send per RLS (Serving and Non Serving E-DCH RLS) RLS) • HICH information is always but it is transmitted in each cell belonging to the RLS to allow the UE a softer combining of the physical channels.
• Uses SF128 Cells not belonging to belonging to the serving E-DCH link set transmit set transmit only ACKs • Cells not Serving E-DCH RLS
E-DPDCH (user data)
E-DPDCH (user data)
E-HICH (ACK) E-HICH (ACK)
E-HICH (ACK,NACK) E-HICH (ACK,NACK)
Only ACKs are send to save DL power. Cells that don‘t belong to the serving serving RLS expected expected to have For internal use 25 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
a much larger NACK ratio due to worse channel HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
conditions
E-HICH power settings Name
Q3-Name
Shortname
Longname
LMTName
Type
Range
Unit
R/ W
Default
E-HICH Power Offset
sbs3gRanHichP wrOffset
HICHPWROFF
hichPowerOff set
po_hich
Integer
0..255 (0..2.55)
LMT: dB
RW
128 (RC)
Mapping to -32..+31.75 by step of 0.25
RC: 0.01*dB
1.28 (LMT)
Indicates the Power offset relative to the pilot bits on the DL DPCCH
Name
Q3-Name
Shortname
Longname
LMT-Name
Type
Range
Unit
R/ W
Default
Number of ERGCH/E-HICH
sbs3gRanNoRg chHich
NORGCHHIC H
numberErgch Ehich
no_rgch_hich
Integer
1,..,4
-
RW
-
Number of E-RGCH/E-HICH
Example of command execution (hmi): cre hsupa cellid=1 hsupa cellid=1 nodebid=1 no_rgch_hich=4 no_rgch_hich=4 po_agch=1.25 po_agch=1.25 po_hich=1.25 po_hich=1.25 po_rgch=1.25 po_rgch=1.25 pr_edch=30
For internal use 26 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Examples for AG, RG and HICH transmission Non Serving RLS (1 RL)
NodeB 1
NodeB 2
Example 1: 2 radio links in serving RLS. RG & HICH is combined.
Serving RLS Serving E-DCH Cell
same RG information information (per RLS)
RG information per RL HICH information per RLS
same HICH information information (per RLS)
E-HICH E-AGCH E-RGCH
Serving RLS
NodeB 1
NodeB 2 Non Serving RLS
Example 2: 2 radio links in nonserving RLS. Only HICH is combined. RG is individual
Serving E-DCH Cell
RG information per RL E-HICH E-AGCH
For internal use 27 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
E-RGCH HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
RG information per RL same HICH information information (per RLS)
Overwiev of all physical channels assigned to UE in HSUPA (NodeB with serving E-DCH RLS)
For internal use 28 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA Scheduling mechanism
For internal use 29 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler • The scheduler resides resides in the NodeB and manages the the data transmission of the Rel.6 UEs on the air interface.
• The goal is, to assign as many resource resources s as required required to a single single UE while preventing cell overload caused by many UEs transmitting too many data.
• The scheduling algorithm algorithm is vendor specific, however however the mechanism to communicate the scheduling results to the UE as well as certain input parameters are defined by 3GPP.
involved in the scheduling scheduling process process • Channels involved – Uplink ▪ E-DPCCH (Happy Bit) Bit) ▪ E-DPDCH (Scheduling (Scheduling Information, Information, SI) – Downlink ▪ E-AGCH E-AGCH (to send send the AG) ▪ E-RGCH E-RGCH (to send RG: UP, DOWN, HOLD commands) commands) For internal use 30 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler Design Principles applications (e.g., web browsing, file download) require • Many HSDPA applications high data rate in downlink, but only moderate data rate in uplink Support of large large number number of UEs w/o need for channel type switching switching – Support – Minimized delay for uplink channel access – Fast control of RTWP resource usage by Node B (scheduler) to avoid overload on air interface Secondary Absolute Grant
• Applications requiring a high uplink data rate should should be served on demand Primary Absolute Grant
For internal use 31 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Performance Performa nce Requi Requirements rements scheduling and one dedicated scheduling scheduling cycle per cell per • One common scheduling TTI E-DCH scheduled scheduled on the same CHC CHC • Up to 3 cells with E-DCH – Scheduling of 1 radio cell on a CHC ▪ ▪ ▪ ▪ ▪
At least 32 HSUPA HSUPA users users / cell At least 32 users simultaneously transmitting transmitting on E-DPDCH / cell Maximum peak user throughput of at least 1.46Mbps 1.46Mbps One E-AGCH E-AGCH / cell cell One Secondary Secondary E-RNTI / cell
– Scheduling of 3 radio cells on the same CHC ▪ ▪ ▪ ▪ ▪
At least 20 HSUPA HSUPA users users / cell At least 10 users simultaneously transmitting transmitting on E-DPDCH / cell Maximum peak user throughput of at least 1.46Mbps 1.46Mbps One E-AGCH E-AGCH / cell cell One Secondary Secondary E-RNTI / cell
For internal use 32 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler in NodeB • The scheduler in the NodeB controls the UL transmission on the E-DPDCH • Main input factors from the UE are: – SI (Scheduling information) (periodically send on E-DPDCH or when triggered) – Happy Bit (send on E-DPCCH) – Transmitted bit rate by the UE
• Main output factors to the UE are: – Absolute allowed transmission power ratio E-DPDCH/DPCCH send on E AGCH
– Relative grants (UP, DOWN, HOLD) send on E-RGCH
For internal use 33 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler in NodeB, O&M parameters 1/2 NodeB O&M parameters parameters influence the the scheduler operation: • The following NodeB – Target ratio of average non-serving E-DCH powers for scheduling of internal Relative Grants: (targetRatioOtherRlEdchPower (targetRatioOtherRlEdchPower ) ▪ For balancing of traffic traffic load from UEs with different different serving RLs between the the cells of a Node B, a target ratio for the average non-serving E-DCH power of these UEs shall be provided.
( maxSecondAbsGrant) – Maximum Secondary Absolute Grant: (maxSecondAbsGrant value is an upper upper limit to the Secondary Secondary AG that may be assigned to all UEs in a radio cell. cell. ▪ This value secondary AG and are upgraded upgraded to primary AG upon demand (rise (rise in ▪ In UMR, all UEs start with secondary uplink traffic needs)
– Maximum number of simultaneous UEs with Primary_Grant_Available ="True": (maxNumberPrimaryGrantUe) ▪ This value is an upper limit limit to the number of UEs in a cell that may be simultaneously simultaneously operating operating with a Primary AG.
For internal use 34 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler in NodeB, O&M parameters 2/2 NodeB O&M parameters parameters influence the the scheduler operation: • The following NodeB ( ueInactivityTimer ) – Time constant for UE inactivity detection: (ueInactivityTimer ▪ ξinactivity indicates the number of idle subframes (2ms) after that a UE may be switched from state Primary_Grant_Available = "True" to "False".
transmission is less than what could be be send with current secondary current secondary AG for AG for the ▪ If data transmission timeframe of ueInactivityTimer ueInactivityTimer , UE is reduced to secondary AG.
hsupaSchedulerWeight)) – Scheduling priority weighting factors: ( hsupaSchedulerWeight shall be provided one weighting weighting factor per scheduling scheduling priority. ▪ The scheduler shall
For internal use 35 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler in NodeB, O&M parameter description Name
Range
Unit
R/W
Default
hsupaPowerOffsetEAGCH
Range: -32..31.75
dB
V
76 (-13 dB)
Step: 0.25 Mapped in database to range 0..255 Power offset of E-AGCH (secondary (secondary E-RNTI) (configurable only at CHC start-up start-up time). Relative to CPICH power. Vendor power. Vendor parameter: not recommended to be changed by the operator. Name
Range
Unit
R/ W
Default
maxSecondAbsGrant
Value range: [0…31]
-
R
5
5 ~ 32 kbps 9 ~ 128 kbps 9 shall not be exeeded
index value of 3GPP 25.212, section4.10.1A.1, table 16B Upper limit to the Secondary AG that may be assigned to all UEs in a radio cell. When doing RTT ("ping") measurements, note that the default value of 5 will have negative impacts on the RTT, as it does not allow a ping of 32 bytes to be sent within one MAC-e PDU: 2 PDUs are needed. To have an optimal RTT, either ensure that you have a Primary Grant active or set this value to a minimum of 7. Final value is still under evaluation.
Name maxNumberPrimaryGrantUe
Range 0..255
Unit
R/W
Default
-
V
4
Example of command execution (xml): ">
Maximum number of simultaneous UEs with Primary_Grant_Available = “True” Vendor parameter: not recommended to be changed by the operator.
"/>
Name
Range
Unit
R/W
Default
">
ueInactivityTimer
0..1023
-
V
25
label="maxNumberPrimaryGrantUe label="maxNumberPrimaryGrantUe">
The info shall provide a time constant for UE inactivity detection. It indicates the number of idle subframes after that a UE’s Serving Grant may be set to zero and the UE may be switched from state Primary_Grant_Available = “True” to “False”. ms Vendor parameter: not recommended to be changed by the operator. equals to 2ms * 25 = 50 ms Vendor For internal use 36 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
"> "/>
Scheduler in NodeB, O&M parameter description Name
Range
Unit
R/W
Default
targetRatioOtherRlEdchPower
Value range: 0..100%
%
V
50
Unit: % Step: 1%
Target ratio of average E-DCH powers per UE of Other E-DCH RLs within Serving RLS for scheduling of Internal Relative Grants. Vendor parameter: not recommended to be changed by the operator.
• For balancing of traffic load from UEs with different serving RLs between the cells of a Node B, a target ratio for the average non-serving E-DCH power of these UEs shall be provided. Example of command execution (xml): class="LocalCellE"> "/> For internal use 37 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler in NodeB, O&M parameter description Name
Range
Unit
R/W
Default
hsupaSchedulerWeight
Formula: x/1000
-
R/W
1000
Value range: 1 to 1000 Specifies the weighting factors (alpha(k)) for each HSUPA scheduling priority level k 0...15. The attribute is applicable only if the LocalCellE is HSxPA-capable, otherwise it shall be ignored. There shall be one value per priority level and per radio cell.
• HSUPA and HSDPA packet schedulers in the NodeB take the Scheduling Priority Indicator (SPI) into account. • HSUPA and HSDPA packet schedulers weight different priority queues based on SPI values. • There is a weight value per SPI value in the NodeB (hsupaSchedulerWeight ), which sets the magnitude how often queues of different SPI classes get scheduled in relation to other SPI classes. Traffic class
Traffic handling priority
Scheduling Priority Indicator Indicator (SPI)
Interactive
1 (highest)
15
…
…
15 (lowest)
1
N/A
0
Background
For internal use 38 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler in NodeB: Input parameters Random Errors / Defects
Node B TTI Timer
OMC
LMT
t c e f e d C H C
O &M c o om m m a m nd a s s , P a ar r a a m me t t e e er r s s
NBAP log. O&M
, n d s m a m o s s c e r t e O & M a r a m e P W P R T L R
r e l u i a f
CHC
HSUPA Scheduler
UL congestion indication
, o f , n t I i B g n S y i B p l u T p d a e H h c S
UE
For internal use 39 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
NBAP UE-related procedures
HSDPA Scheduler
RNC
NodeB Scheduler Schedu ler Interf Interface ace
From Frame Protocol
Measurements Scheduler / CHC Internal From E-DPCCH or E-DPDCH
For internal use 40 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
NodeB Scheduler Schedu ler Interf Interface ace Scheduler Parameters
Output Data
Input Data
-Relative Grant (non-serving RLS) -Absolute Grant -Primary / Secondary Indicator
1 1
1
*
1
UE-related information
Congestion info from RNC -UE / MAC-d flow ID -Reference Congestion Limit -Indication of TNL Limitation
1
1
For internal use 41 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
1
* *
UE-specific -Relative Grant -Minimum SF
1..*
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
1 * Neighbour cell specific -Internal Relative Grant
NodeB Scheduler Schedu ler Interf Interface ace Scheduler Parameters
1
Configuration Data
Input Data
1 Node B Configuration -Filter Coefficients -Constant Psi
1 0..*
1
1 1
1
1
*
1
*
E-DCH Cell Configuration -E-AGCH channelisation codes -Maximum Target RTWP -Reference RTWP -Target Non-serving Non-serving E-DCH to Total E-DCH Power Ratio -Target Ratio of Avg. Pwrs. of Other E-DCH RLs (for Int. RG) -Maximum Secondary Absolute Grant -Max. No. of Simult. UEs with Primary_Grant_Available = "True" -Time Constant for UE Inactivity Detection -Scheduling Priority Weighting Factors -Rx Antennas -Scheduler Type -E-AGCH 3-Index-Step Threshold -E-AGCH 2-Index-Step Threshold -Time Constant for Assignment of Primary Absolute Grants -Init Value for Overhead Factor -Time constant for determination of TEBS status 0..*
For internal use 42 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Node B / CHC internal signals signals -RTWP -E-DCH pwr (serving RLs) -E-DCH pwr (Other E-DCH RLs) -E-DCH pwr (non-serv. RLs) -Numbers -Numbers of Other E-DCH RLs -BB Resource Status
UE-related information
Congest -UE / MA -Referen -Indicatio
1
1
1..* UE group related info -Stored Secondary Gran
* Info from UE -Happy Bit -UPH -TEBS -HLBS
* Node B internal info -HARQ process state -Duration of inactivity -Serving Grant -Prima -Primarr Grant Grant Available Available
NodeB Scheduler Schedu ler Interf Interface ace
For internal use 43 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduling Information • Periodically or if triggered the UE may transmit scheduling information (SI) on the E-DPDCH to the NodeB.
• The information in the SI includes: Amount of data waiting waiting to be transmitted transmitted in the buffer (TEBS) – Amount – The priority of that data and the amount of the data with highest priority – UPH: UE power headroom, the ratio of the maximum UE tx power and the DPCCH power
information n from the SI is taken taken into account account by the NodeB for the • The informatio scheduling process
• The SI contains contains a lot of information, information, is complex to encode encode and produces produces a large overhead in signalling data 2nd, more lean and faster mechanism via the “Happy Bit” is available in addition.
A
For internal use 44 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduling Information: RNC O&M Parameter Name
Q3Name
Shortna me
Longname
LMTName
Range
Unit
R/W
Default
Periodicity for Schedulin g Info – no grant
sbs3g RanPe riodNo Grant
PERIN OGRAN T
periodSche dInfoNoGr ant
pesc_ng
{everyEDCHTTI, ms4, ms10, ms20, ms50, ms100, ms200, ms500, ms1000}
ms
RW
everyEDCHTTI
Periodicity for the UE to transmit scheduling information when Serving Grant is not assigned.
Name
Q3Name
Shortn ame
Longname
LMTName
Range
Unit
R/W
Default
Periodicity for Schedulin g Info – grant
sbs3gR anPerio dGrant
PERIG RANT
periodSche dInfoGrant
pesc_g
{everyEDCHTTI, ms4, ms10, ms20, ms50, ms100, ms200, ms500, ms1000}
ms
RW
everyEDCHTTI
Periodicity for the UE to transmit scheduling information when Serving Grant is assigned.
Example of command execution (hmi): cre edcinf edch_pref=rv0 edch_pref=rv0 etfci_idx=1 pesc_ng=every etfci_idx=1 pesc_ng=every pesc_g=every maxrm_edch=15 pesc_g=every maxrm_edch=15 edch_po=0
For internal use 45 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Happy Bit indicates every TTI on the E-DPCCH whether whether it is happy happy with the currently currently • The UE indicates assigned assigned E-DPDCH resources resources or not via the “Happy “Happy Bit”. – Happy Bit = 0 “not happy” – Happy Bit = 1 “happy” transmission, on, the Happy Bit shall shall be set to "unhappy" "unhappy" if the three • For every E-DCH transmissi following criteria are met: (TS25.321) – UE is transmitting as much scheduled data as allowed by the current Serving_Grant in
E-TFC selection; and – UE has enough power available available to transmit at higher data rate; and – More than “Happy “Happy Bit Delay Condition” Condition ” ms is required under the current conditions to transmit the data in the UE buffer (TEBS).
Otherwise, the Happy Happy Bit shall be set to "happy". "happy". • Otherwise, information into account when assigning assigning • The NodeB scheduler takes that information resources for the next transmissions.
For internal use 46 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
TEBS: Total TEBS: Total E-DCH buffer status HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Happy Bit – RNC system internal parameter • Happy Happy bit delay condition is a system internal (hidden) (hidden) parameter parameter in UMR6.5.
• Per UE category Name
Type
Range
Unit
Default
Description
Happy bit delay condition
Enumerated
2ms, 10ms, 20ms, 50ms, 100ms, 200ms, 500ms, 1000ms
ms
10ms
Used when determining the setting of the happy bit (as specified in specified in 3GPP TS25.321).
• It is a operator operator configurable configurable parameter parameter in RAS06 (HappyBitDelayConditionEDCH HappyBitDelayConditionEDCH). ). Default: 50ms
For internal use 47 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler Algorithm UE addressed individually UE gets PAG “inactive”
UE using PAGs at the same time is limited
UE on SAG stops transmission
UE on SAG may start transmission arbitrarily
UE is modified with RGs
Grant/Rate
Time
Maximum Primary Absolute Grant
UEs addressed as a group
UE gets assigned PAG Maximum Secondary Absolute Grant
Maximum SAG is reached
Current Secondary Absolute Grant UE may use current SAG
UEs For internal use 48 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduling illustration Serving Node B sends Relative Grant “UP “ “DOWN “ “HOLD “
serving Node B
NB
Each Node B has fast control over the UE transmit power . The noise rise is controlled via fast Node B scheduling.
u p - d o w n - h o l d
n non serving NB w Node B‘s o d Non Serving NB d l o h NB d l d
h o
Serving Node B sends Absolute Grant (limits (limits the UE‘s sending po wer)
UE sends rate request to serving Node B
For internal use 49 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
A “DOWN “ command received by a non serving Non Serving NB Node B, has highest priority priority !
Non serving Node Bs may only send Relative Grants to the UE “DOWN “ or “HOLD “
HARQ: Hybrid automatic repeat request
For internal use 50 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HARQ Process There is one HARQ entity entity per UE. • There – For the 10ms TTI, 4 HARQ processes are configured – For the 2ms TTI, 8 HARQ processes are configured
2ms TTI not yet supported by NSN implementations.
• HARQ messages messages (ACK/NA (ACK/NACK) CK) are send on the E-HICH E-HICH to the UE • For retransmission, NodeB NodeB supports Chase Combining Combining (CC) and Incremental Redundancy (IR)
• HARQ messages messages are send send by all NodeBs NodeBs in the E-DCH active set: – The NodeB with the serving E-DCH RLS send ACK and NACK msg. – Other NodeBs only send ACK messages Nod eB 1
Non Serving RLS (1 RL)
Node B 2
Serving RLS
ServingE-DCH Cell
• For each RLS, one common common HARQ information information is send. send.
same RG information (per RLS)
RG information per RL HICH information per RLS
same HICH information (per RLS)
E-HICH E-AGCH E-RGCH
continues to transmit transmit as long there is at least one ACK message • The UE continues received
For internal use 51 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HARQ Process in soft handover RLC performs reordering of data PDU
RNC
The Node B that correctly received the data, forwards it to the RNC ( RLC)
Non Serving Node Bs send back only ACK
NB Non Serving NB
K C A
NB Serving NB
NB
A C K , N A C K
UE sends transport format format and data packet
K A C Non Serving NB
x t t x r e -
If one Node B receives the data packet correctly, further retransmissions from the UE can be stopped. Regardless what result the other involved Node Bs have received, the correctly received data packet will be delivered to the higher layers. The UE needs to r e t r an an s m i t o n l y w h e n a l l i n v o l v e d N o d e B s a s k f o r i t . For internal use 52 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
UE sends retransmission if no ACK message is o n l y if received
4 HARQ processes for the 10ms TTI required HARQ processes results from from the • The number of required - TTI size, - processing time in the NodeB, NodeB, - propagation delay delay on the air-interface. i-3
CPICH / P-CCPCH
5 – 8 slots
DL DPCH
i- 2
i-2
i-3 1 i-3
Tx (UE)
E-DPDCH / E-DPCCH
Rx (NB)
E-HICH
Tx (NB)
2048
chips
i-3
i-1
i-3
i
i-1
i
i+1
2
3
0
1
i-2
i-1
i
i+1
i-2
i-1
i
i+1
38400 chips i-2
i- 1
i
i+1
Processing time at Node B 30ms = 115200 chips
Timing relation between uplink data transmissions and ACK/NACK sent on E-HICH for the 10ms TTI
processes per UE are sufficien sufficientt • For the 10ms TTI, 4 HARQ processes For internal use 53 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HARQ Process: O&M Parameter I Name
Q3-Name
Shortname
Longname
LMT-Name
Range
R/W
Default
HARQ Info for E-DCH Preference
sbs3gRanEd chHarqInfoPr ef
EDCHHARQI NFP
edchHarqInfo Preference
edch_pref
{rv0, rvtable}
RW
rv0 Rec: rvtable
“rv0” “rv0” indicates indicates that the UE will only use E_DCH E_DCH RV index 0. “rvtable” indicates that the UE will use an RSN based RV index as specified in 3GPP TS25.212 Recommendation: rvtable
• edch_pref selects the HARQ method that will be used: – rv0: Redundancy version 0, Chase Combining – rvtable: Incremental redundancy Name
Q3-Name
Shortname
Longname
LMT-Name
Range
R/ W
Default
Maximum Number of retransmissions for E-DCH
sbs3gRanMaxN oRetransEdch
MAXRETRE DCH
maxNumberR etransmission Edch
maxrm_edch
0,..,15
R W
15 Rec: 5
E-DCH MAC-d flow maximum number of retransmissions.
Recommendation: Set maxrm_edch to 5 • Recommendation: For internal use 54 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HARQ Process: O&M Parameter II Name
Q3-Name
Shortname
Longname
LMT-Name
Range
Unit
R/ W
Default
E-DCH HARQ Power Offset FDD
sbs3gRanE dchHarqPo wOffFdd
EDCHHAR QPWROFD
edchHarqP owerOffset Fdd
edch_po
0,..,6
dB
RW
0
The E-DCH HARQ Power Offset FDD is used to calculate the unquantised gain factor for an E-TFC (bed,j,uq ( bed,j,uq)) as defined in 3GPP TS25.213.
• MAC-d flow specific specific power offset offset that is added on top of the transport transport block specific power offset. A larger power offset means a lower propability of needing a retransmission and, thus, lower latency. However, a higher power offset offset will likely result in a lower lower chosen • However, transport block size, what will cause lower throughput. Example of command execution (hmi): cre edcinf edch_pref=rv0 etfci_idx=1 edch_pref=rv0 etfci_idx=1 pesc_ng=every pesc_g=every maxrm_edch=5 pesc_g=every maxrm_edch=5 edch_po=0
For internal use 55 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HARQ Process: Impacts of parameter settings parameters rs could be set in a way that: • The two paramete
- Delay tolerant services can have a lower power offset ( edch_po) and higher retransmission propability,
- Streaming services can have a lower max. retransmission count (maxrm_edch) as they tolerate a few lost packets.
For internal use 56 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA RAB Handling
For internal use 57 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Supported HSUPA RAB Combinations RABs
Traffic Class
CS/PS
Max Rates for each RAB kbps 1
1
2
Packet
-
Interactive/Background
Packet
NB-AMR
Packet
Conversational Transparent Data
3GPP Reference 25.993
2
UL
DL
UL
DL
PS
E-DCH
HSDSCH
-
-
7.5.1
Interactive/Background Interactive/Background + Conversational
PS + CS
E-DCH
HSDSCH
12.2
12.2
7.5.4
Interactive/Background Interactive/Background + Conversational
PS + CS
E-DCH
HSDSCH
64
64
7.5.8
• HSUPA establishment always requires the UE and the cell to be HSDPA capable • Single NRT call as well as multi call possible • In case of a multi call, only 64/64 kbps Rel.99 possible in addition to E-DCH • Only the RLC the RLC PDU size of 336 bits shall bits shall be supported for E-DCH
For internal use 58 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
State Model (DCH_INACTIVITY is ON) with new E-DCH state Single PS I/B PS I/B Setup
AMR + PS I/B AMR RAB Setup/ RAB or IU Release
Cell_DCH
In-/outward Mobility
HS-DSCH + E-DCH Cell_DCH + UL BRA HS-DSCH
PS I/B Setup
SBHO "Directed Retry"
In-/outward Mobility
AMR RAB Setup/RAB or I U Release In-/outward Mobility
HS-DSCH_ E-DCH ACTIVE
In-/outward Mobility T_DCH_FA CH
T_FACH_P CH
HS-DSCH ACTIVE
UL BRA
TVM 4A (RACH) or DL DTCH overflow or "Directed Retry"
T_HSDSCH_FACH
PS I/B Setup Set up
PS I/B Setup
DCH_ACTIVE
FACH_ACTIVE T_FACH_PC H
CS RAB or IU Release AMR RA B Setup
T_HSDSCH_FACH
TVM 4A or DL DTCH Activity
UL or DL DTCH Activity
DCH_INACTIVE State
FACH_INACTIVE DL DTCH Activity
DCCH Inactivity
UL or DL DCCH Activity
Cell_PCH
For internal use 59 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
AMR RAB Setup/ CS RAB or IU Release AMR RAB Release CS IU Release
DCCH_ACTIVE DCCH Activity/ Inactivity detection
DCCH_INACTIVE
PS I/B Setup
State Model (DCH_INACTIVITY is OFF) with new E-DCH state UDI + PS I/B or AMR + PS I/B (DCH_INACTIVITY = FALSE)
Single PS I/B
PS I/B Setup Setup
AMR/UDI RAB Setup/RAB or IU Release
Cell_DCH
DCH_ACTIVE
In-/outward Mobility
PS I/B Setup
HS-DSCH + E-DCH Cell_DCH + UL BRA HS-DSCH
PS I/B Setup SBHO "Directed Retry"
In-/outward Mobility
AMR/UDI RAB Setup/RAB or IU Release In-/outward Mobility
In-/outward Mobility T_DCH_FA CH
FACH_ACTIVE
CS RAB Setup/ RAB or IU Release AMR/UDI RAB Setup
UL or DL DTCH Activity
T_FACH_P CH
FACH_INACTIVE DL DTCH Activity
DCCH Inactivity
UL or DL DCCH Activity
Cell_PCH
For internal use 60 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HS-DSCH_ E-DCH ACTIVE HS-DSCH_ ACTIVE
UL BRA
TVM 4A (RACH) or DL DTCH overflow or "Directed Retry"
T_HSDSCH_FACH
PS I/B Setu
CS RAB Setup
PS I/B Setu
Inactivity Inacti vity detecti detection on • When the the UE is is in HS-DSCH in HS-DSCH + E-DCH or HS-DSCH_E-DCH-ACTIVE HS-DSCH_E-DCH-ACTIVE
state (HSUPA mode), inactivity detection is based on the existing timer T_HS-DSCH_FACH.
Name
Q3-Name
Shortname
Longname
LMT-Name
Type
Range
Unit
R/W
Default
Timer for the switch from HSDSCH to FACH
sbs3gRan HsDschF achSwitch Tmr
HSDSCHFC HSWTMR
hsDschFachS witchTmr
thsdsch_fach
Integ er
0,.., 65535
s
RW
30
Period of uplink and downlink inactivity before the PS I/B RAB is switched from HS-DSCH to FACH 0 means that inactivity is not monitored and the connection is not switched to FACH
Example of command execution (hmi): cre rbc tfach_dchue=20 rbc tfach_dchue=20 tbra_riue=1280 tbra_rdue=1280 tdch_fachr=65535 tfach_pchr=300 tpch_idler=7200 tpch_idler=7200 thsdsch_fach=30 ulbra_ript=64K ulbra_rdpt=8K ul_fdpt=256 dl_upt=512 max_ccros=20 srbr=13.6 dch_inact=true ch_nonrab=comm ch_ibrab=dedc ini_pib=64_64 t_strminact=0 flag_preempt=false ini_hsulpib=64 pc_csudi=false pc_psbe=false
For internal use 61 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA Mobility aspects
For internal use 62 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Overwiew supports soft handover handover • HSUPA supports the active set acts acts as Serving E-DCH cell • One cell out of the the E-AGCH and E-RGCH for for scheduling • The serving E-DCH cell uses the operation
• The other other cells only use the E-RGCH E-RGCH and only send DOWN or HOLD • Cells belonging belonging to the same NodeB as the E-DCH E-DCH serving cell, belong belong to the “Serving E-DCH radio link set” Serving E-DCH RLS E - - AG C C H H ( a ab b
s so l lu o t te u p e p w wr r ) )
E - -R G R GC CH ( u H u p p
,d o ow n w , h o o l ld ) d )
E - -D P D D P C D H C H
( u us e r r d d at a)
For internal use 63 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
d ) l d w n, h o o d ( C H
E - R G
D C H E - D P t a a )
d a ( u s e r
E-DCH Active Set Size: E-DCH and DCH Active Set Size identical
For internal use 64 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH Active Set Size: E-DCH subset of DCH Active Set
For internal use 65 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Active set summary contains one Serving Serving E-DCH RLS with • For each UE, the E-DCH active set contains one Serving E-DCH RL. ‘zero’, ‘one’ or ‘more’ ‘more’ E-DCH RLs, which which belong to • It is possible to have ‘zero’, the Serving E-DCH RLS but which are not the Serving E-DCH RL. And, the E-DCH active set can contain ‘zero’, ‘one’, or ‘more’ Non-Serving EDCH RLs (which does not belong to the Serving E-DCH RLS). Grant transmitted transmitted by the Serving • For each UE, there is only one Absolute Grant E-DCH Cell via the E-AGCH. (optional) transmitted • For each UE, there is one common Relative Grant (optional) per Serving E-DCH RLS, and, also one per Non-Serving E-DCH RL.
For internal use 66 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA mobility impact • The main areas of E-DCH Mobility Mobility impacts are the followings: followings: – UE Differentiation Algorithm – E-DCH Serving Cell Selection – E-DCH Inward Mobility (Intra freq. and Inter freq. HO case) – E-DC E-DCH H Serv Servin ing g Cell Cell Chan Change ge (Int (Intra ra freq freq.. and and Inte Interr freq freq.. HO case case)) – E-D E-DCH Outw utward Mob Mobilit ility y (Int (Intrra freq. req. and and Int Inter freq freq.. HO case case)) – SHO handling for Non-Serving E-DCH RLs – Inter System HO – SRNS Relocation* • [Note]: Compressed Compressed Mode with E-DCH is not supported supported • [Note]: [Note]: E-DCH over Iur is not supported supported Relocation is not supported supported • *[Note]: E-DCH Relocation For internal use 67 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA Mobility aspects UE differe differentiati ntiation on algo algorithm rithm
For internal use 68 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH UE differentiation algoritm Differentiation algorithm is applied during during RRC Connection Setup and CTS CTS • UE Differentiation CtoD transition (due to NRT traffic overflow trigger). direct the E-DCH Capable Capable UE with NRT with NRT RAB related RRC • UTRAN shall direct signalling establishment to establishment to the freq. carrier which supports E-DCH. works only with Inter-Frequency Inter-Frequency Cells of the same sector (i.e. same (i.e. same • The algorithm works antenna flags set flags set to TRUE) If attempt on RF3 fails, further attempts on RF 4 is performed
RF4 (E-DCH/HS-DSCH) (E-DCH/HS-DSCH)
E-DCH/HS-DSCH Capable UE shall be first attempted on RF3
RF3 (E-DCH/HS-DSCH) (E-DCH/HS-DSCH) RF2 (Rel99)
E-DCH/HS-DSCH Capable UE Camps on RF 1
RF1 (Rel99) For internal use 69 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH UE differentiation algoritm • To reserve the E-DCH/HS-DSCH Cell as much as possible for E-DCH/HS-DSCH capable UEs, HCS UEs, HCS priorities for priorities for the different layers should be set: Non-E-DCH/HS-DSCH Cell (highest Priority) >> HS-DSCH Capable Cell >> E-DCH/HS-DSCH Capable Cell (lowest Priority)
For internal use 70 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Establishment Cause for UE Differentiation • The UE differentiat differentiation ion algorithm algorithm attempts attempts to redirect a Rel6 UE to the appropriate frequency layer, if at RRC setup or setup or CTS CTS from FACH the – Establishment cause IE contains a cause value with corresponding bit in “Establishment Cause for UE Differentiation” Differentiation ” flag set to ‘1’ Name
Q3-Name
Shortname
longname
LMT-Name
Type
Range
Default
Establishment Cause for UE Differentiation
sbs3gRanEst CauseForUeD iffer
CAUSEUEDIF
esatblCauseF orUeDifferenti ation
ecuedif
LMT: Integer (hex) RC: BitString [32]
LMT: 0,..., 4294967295 (hex: 0,..,FFFFFFFF)
LMT: 16796 (hex: 0000419C)
Specifies Establishment Cause which will be considered in UE Differentiation procedure as HSDPA or HSUPA Capable. “Establishment Cause for UE Differentiation” flag is a bitmap of 32bits long. Each bit of this flag will correspond to an Establishment Cause. Bit 0 corresponds to “originatingConversationalCall”, bit 1 corresponds to “originatingStreamingCall” and so on. Following table shows how the each bit of “Establishment Cause for UE Differentiation“ flag is mapped to Establishment Cause and the default setting of this flag. bit
3 1
3 0
2 9
2 8
2 7
2 6
2 5
2 4
2 3
2 2
2 1
2 0
1 9
1 8
1 7
1 6
1 5
1 4
1 3
1 2
1 1
1 0
0 9
0 8
0 7
0 6
0 5
0 4
0 3
0 2
0 1
0 0
Default Setting
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
1
1
0
0
1
1
1
0
0
E s t a b l i s h m e n t C a u s e
T e r m ( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
( S p a r e
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
v a l u e )
For internal use 71 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
i n a t i n g – c a u s e u n k n o w n
T e r m i n a t i n g L o w P r i o r i t y S i g n a l l i n g
T e r m i n a t i n g H i g h P r i o r i t y S i g n a l l i n g
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
C a l l r e e s t a b l i s h m e n t
O r i g i n a t i n g L o w P r i o r i t y S i g n a l l i n g
O r i g i n a t i n g H i g h P r i o r i t y S i g n a l l i n g
D e t a c h
R e g i s t r a t i o n
I n t e r -R A T c e l l c h a n g e o r d e r
I n t e r -R A T c e l l r e s e l e c t i o n
E m e r g e n c y C a l l
T e r m i n a t i n g B a c k g r o u n d C a l l
T e r m
T e r m
i n a t i n g I n t e r a c t i v e C a l l
i n a t i n g S t r e a m i n g C a l l
T e r m i n a t i n g C o n v e r s a t i o n a l C a l l
O r i g i n a t i n g S u b s c r i b e d t r a f f i c C a l l
O r i g i n a t i n g B a c k g r o u n d C a l l
O r i g i n a t i n g I n t e r a c t i v e C a l l
O r i g i n a t i n g S t r e a m i n g C a l l
O r i g i n a t i n g C o n v e r s a t i o n a l C a l l
A Rel6 UE, that establishes a AMR speech call will not will not be redirected to the HSPA layer.
UE Differentiation SWP data • Enhanced UE differentiation differentiation algorithm is an optional optional feature which is not included in the standard feature set. enable it, the “UE differentiat differentiation” ion” flag in the SWP data must be • In order to enable set to “true”
Name
Type
Range
Default
Description
HSDPA UE differentiation function switch flag
Boolean
1 : off
1
Flag set to ‘0’ when operator has bought the feature
1 : off
0 : on
0 : on
For internal use 72 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA Mobility aspects E-DCH serving cell selection E-DCH inward mobility E-DCH serving cell change E-DCH outward mobility SHO of non serving radio links Blind IFHO Timing re-initialized IFHO Intersystem Handover SRNS relocation
For internal use 73 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH serving cell selection • The serving serving E-DCH Cell is selected selected based on best downlink downlink quality quality cell: – Considers a cell which provides the highest reliability for DL transmission of AG to the UE – A common DL best quality measure shall be beneficial generally for overall performance of HSPA.
• For the Serving Serving E-DCH Cell: Cell : Select the Best Quality E-DCH/HS-DSCH
Cell for which the UE has reported the highest DL CPICH Ec/N0 or CPICH RSCP or smallest Pathloss value in the received RRC Measurement Report 1A/1B/1C/1D.
Serving g E-DCH RLS RLS : Select the Node-B (RLS) where Serving E• For the Servin DCH Cell is determined.
• Event Event 1D triggers the change change of the best cell
For internal use 74 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH inward mobility – 1/2 •
E-DCH Inward Mobility is is triggered, if the Measurement Measurement Report 1A/1B/1C/1D 1A/1B/1C/1D is received and received and the the reported E-DCH/HS-DSCH Cell has the best quality. Also, the quality difference between the best Serving E-DCH Cell and others shall be greater than a predefined hysteresis ( cr cre e if ifmr mrms ms hy hyst st1d 1d).
•
When E-DCH Inward Mobility Mobility is triggered, active set update update (ASU) procedure procedure (if Event 1A/1B/1C is received) is performed first, in preparation for the E-DCH Inward Mobility procedure. SRNC
Rel99
Rel99
E-DCH/HS-DSCH
E-DCH/HS-DSCH
Serving E-DCH/HS-DSCH E-DCH/HS-DSCH RL
RLs in DCH Active Set
SRNC
Serving E-DCH/HS-DSCH Cell
Rel99
Rel99
E-DCH/HS-DSCH
E-DCH/HS-DSCH
1A: this cell is newly added added and it is Best Quality Cell
For internal use 75 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH inward mobility – 2/2 •
Supported Inward Mobility procedures: –
From DCH/DCH to E-DCH/HS-DSCH
–
From DCH/HS-DSCH DCH/HS-DSCH to E-DCH/HS-DSCH - Intra Node-B Node-B Case
–
From DCH/HS-DSCH DCH/HS-DSCH to E-DCH/HS-DSCH - Inter Node-B Node-B Case
For internal use 76 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH serving cell change – 1/2 •
E-DCH Serving Cell Change Change (SCC) is triggered triggered if the the quality of existing Serving Serving E-DCH/HS-DSCH Cell becomes worse than an other E-DCH/HS-DSCH Cell within the DCH Active Set.
•
When SCC is is triggered, ASU ASU procedure (if Event 1A/1B/1C 1A/1B/1C is received) received) is performed first, in preparation for the E-DCH SCC procedure. SRNC Serving E-DCH/HS-DSCH RL Serving E-DCH/HS-DSCH Cell
Rel99
Rel99
RLs in DCH Active Set
E-DCH/HS-DSCH
E-DCH/HS-DSCH
SRNC Serving E-DCH/HS-DSCH Cell
Rel99
Rel99
E-DCH/HS-DSCH
E-DCH/HS-DSCH
1A: this cell is newly added and it is Best Quality Cell For internal use 77 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH serving cell change – 2/2 •
Trigger 1: Measurement Report 1A/1B/1C/1D 1A/1B/1C/1D is received and the Quality Quality of the current Serving E-DCH Cell is worse than other reported Cell (new best EDCH Serving Cell). Also, the quality difference between the current Serving E-DCH and new best E-DCH Cell is greater than a predefined hysteresis (cr cre e if ifmr mrms ms hy hyst st1d 1d).
•
Trigger 2: Measurement Measurement Report 1B/1C is received received and the current Serving EDCH Cell is removed, but another E-DCH Cell is available in the Active Set and the quality of this cell is the best.
•
Supported Serving Cell Change (SCC) procedures: – –
SCC – Intra Node-B Case SCC – Inter Node-B Case
For internal use 78 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH outward mobility – 1/3 •
E-DCH E-DCH Outward Mobili Mobility ty is triggered triggered if the UE leaves leaves the E-DCH E-DCH coverage coverage or if the quality of the Non-E-DCH Cell is the best (among the Active Set cells).
•
When Outward Mobility Mobility is triggered, ASU procedure (if Event Event 1A/1B/1C is received) is performed first, in preparation for the E-DCH Outward Mobility procedure. SRNC
Serving E-DCH/HS-DSCH Cell
Rel99
Rel99
E-DCH/HS-DSCH
E-DCH/HS-DSCH
Serving E-DCH/HS-DSCH RL
RLs in DCH Active Set SRNC
Rel99
Rel99 New l ink added via 1A
For internal use 79 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
E-DCH/HS-DSCH
E-DCH/HS-DSCH
Quality of this link is worse than Non-E-DCH Cell(s )
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH outward mobility – 2/3 •
Trigger 1: Event 1A/1B/1C/1D 1A/1B/1C/1D is is received, and, the Quality of Non-E-DCH Cell is better than all E-DCH Cell(s) within active set. Also, the quality difference between the current E-DCH Serving Cell and new best Non-E-DCH cell is greater than a predefined hysteresis (cr cre e if ifmr mrms ms hy hyst st1d 1d).
•
Trigger Trigger 2: Event 2D (IFHO (IFHO Triggers) Triggers) is received received and if ‘IFHO ‘IFHO with InterInterFrequency measurement (2A/2B)’ is triggered. [Note]: Blind IFHO does not invoke Outward Mobility.
•
Trigger 3: Event 2D’/2D’’ 2D’/2D’’ (Inter System System 3A/3A’ 3A/3A’ Triggers)
•
Trigger 4: Upon Upon reception of NBAP: RL RL Failure Indication Indication to the current Serving E-DCH Cell.
For internal use 80 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
E-DCH outward mobility – 3/3 •
Supported E-DCH Outward Mobility procedures: –
From E-DCH/HS-DSCH E-DCH/HS-DSCH to DCH/DCH
–
From E-DCH/HS-DSCH E-DCH/HS-DSCH to DCH/HS-DSCH DCH/HS-DSCH – Intra Node-B Node-B Case
–
From E-DCH/HS-DSCH E-DCH/HS-DSCH to DCH/HS-DSCH DCH/HS-DSCH – Inter Node-B Node-B Case
For internal use 81 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
SHO of non-serving E-DCH RLs •
RNC configures configures all potential potential E-DCH links constituting constituting towards towards E-DCH Active Set. realise the Soft/Softer Soft/Softer HO gains gains for E-DCH configurations. – This is to realise
•
When When Even Eventt 1A/1 1A/1C C is rece receiv ived ed,, and and if the the UE cont contex extt has has been been configured with E-DCH, any newly to-be-added to-be-added E-DCH RL shall be configured as part of E-DCH Active Set. Firstly, y, Rel6 Rel6 NBAP: NBAP: RL Setup Setup/Ad /Addit dition ion Request Request messag message e is appli applied ed to – Firstl perform SHO, and, to configure the E-DCH Link as part of E-DCH Active Set. Secondly, Rel6 Rel6 RRC: Active Set Update Update is applied applied to perform SHO, plus, plus, – Secondly, the configuration of new E-DCH info.
For internal use 82 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Blind IFHO •
SRNC attempts attempts to keep E-DCH/HS-DSC E-DCH/HS-DSCH H configuration configuration (i.e. E-DCH Outward Mobility is not performed), in case if Timing Maintained Hard Handover Handover is initiated initiated (Blind (Blind IFHO – reception reception of Event 2D). 2D).
•
Supported Blind IFHO procedures: – E-DCH Inward Mobility - From ‘DCH/DCH or DCH/HS-DSCH’ to ‘E-DCH/HSDCH’
– E-DCH Serving Cell Change DCH/HS-DSCH – E-DCH Outward Mobility to DCH/HS-DSCH DCH/DCH – E-DCH Outward Mobility to DCH/DCH
For internal use 83 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Timing Timin g Re-ini Re-initializ tialized ed IFHO •
If Timing Re-Initialised IFHO is invoked, SRNC performs performs E-DCH Outward Mobility to DCH/HS-DSCH, in preparation for ‘Timing ReInitialised IFHO with Inter-Frequency measurement(2A/2B)’ procedure.
•
Supported E-DCH Timing Re-initialised Re-initialised IFHO procedures: procedures: – E-DCH Inward Mobility - From ‘DCH/DCH or DCH/HS-DSCH’ to ‘E-DCH/HSDCH’
For internal use 84 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Intersystem Intersys tem Handove Handover r •
When UE is leaving leaving the UMTS coverag coverage e with currently currently configu configured red EDCH/HS-DSCH, the reception of ISHO Event 2D’/2D’’ shall lead to EDCH Outward Mobility to DCH/DCH, in preparation for the ISHO procedure.
For internal use 85 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
SRNS Relocation •
For the the case case if SRNS SRNS Relocati Relocation on Type Type of “UE “ UE Involved without Iur ” is to be triggered, E-DCH Outward Mobility to DCH/HS-DSCH or DCH/DCH (depending on the Target RNC RRC Container support version) is first performed, in preparation to relocation procedure.
•
[Note]: [Note]: For the the case of SRNS SRNS Relocatio Relocation n Type of “UE “ UE Not Involved with Iur ” or “UE “UE Involved with Iur ”, ”, the UE state would have been moved to either DCH/DCH or DCH/HS-DSCH, prior to the relocation trigger. This is due to the fact that E-DCH is not supported over Iur, and, the trigger for abovementioned relocation types is when the entire entire Active Active Set belongs belongs to DRNC.
For internal use 86 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA Admission control
For internal use 87 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA Admission control • Admission Admission control control is triggered by procedures procedures which set-up, add, delete or reconfigure a radio link.
• A new radio bearer is admitted only, if the required resources resources are available in the cell and the QoS requirements of the already existing connections can be met after admission.
• To maintain the satisfact satisfactory ory throughput throughput on HSUPA, it must be prevented that too many HSUPA UEs are accepted in a cell. For
the new UL E-DCH channel, the existing AC algorithm has been extended .
For internal use 88 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
“BLOCK BE to E-DCH” Flag • Admission control sets in each HSUPA cell the “BLOCK BE to E-DCH” flag (true, false), based on the – number of serving E-DCH RLs ( nth1, nth2) – cell cell load load utiliza utilization tion ( cell_util_th )
• The “BLOCK BE to E-DCH” flag is set to TRUE, if – Number of serving E-DCH RLs >= Nth1 >= Nth1 && Cell load Utilization Utilization > Cell_util_th – Number of serving E-DCH RLs >= Nth2 >= Nth2 (>= (>= Nth1 Nth1))
Example of command execution (hmi): cre cell adc2 cellid=1 adc2 cellid=1 nodebid=1 nth1=10 nodebid=1 nth1=10 nth2=32 cell_util_th=0.90 aul_hsupa=1.50
For internal use 89 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Cell load utilization calculation • The cell load utilization is defined as – Cell Load Utilization = (Cell Load) / (Target Cell Load) Cell Load: Cell Load: Cell Load calculated with measured and higher layer filtered RTWP Target Cell Load: Cell Load: Cell Load calculated with Target RTWP (Cell Load = 1 – Nul/RTWP Nul/RTWP and Target Cell Load = 1-Nul/Tar 1-Nul/Target get RTWP) Target RTWP: derived RTWP: derived from the O&M Parameter HSDPA HSDPA Scheduler Offset (hsupa_oft)
R T W P
Congestion Level (N_ul+CCThreshold) Congestion Level – CC Hysteresis HSUPA Scheduler Offset
Example of command execution (hmi): cre cell cctl cellid=1 cctl cellid=1 nodebid=1 ul_cngt=10.0 ul_cngh=2.0 dl_cngt=0.90 dl_cngh=0.15 mmti_rtwbp=10.00 mmti_rtwbp=10.00 mmti_tcp=10.00 k=1 ebd=ena etpchr=ena peri_cngh=0.5 mmfc_rtwp=0 mmfc_tcrp=0 cc_emg=false cc_emg=false hsupa_oft=0.5 For internal use 90 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
Maximum Target RTWP Current Cell Load
TIME HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
“BLOCK BE to E-DCH” flag parameters cre cr e ce cell ll ad adc2 c2 Name
Q3Name
Shortn ame
Longna me
LMTName
Type
Range
Defa ult
Description
Nth1
sbs3g RanNt h1
NTH1
nth1
nth1
Integer
0,..,100
10
Maximum number of Serving EDCH RLs acceptable in a serving cell in case Cell load Utilization > Cell_util_th Note : Nth2 >= Nth1
Nth2
sbs3g RanNt h2
NTH2
nth2
nth2
Integer
0,..,100
32
Maximum number of Serving EDCH RLs acceptable in a serving cell Note : Nth2 >= Nth1
Cell_util_th
sbs3g RanC ellUtil Thres
CELLU TLTHR
cellUtilT hres
cell_util _th
LMT: Real RC: Integer
LMT: 0,..,1 step by 0.01 RC: 0,..,100
LMT: 0.9 RC: 90
Cell load utilization threshold to apply Nth1 as Maximum number of Serving E-DCH RLs acceptable in a serving cell
Example of command execution (hmi): cre cell adc2 cellid=1 adc2 cellid=1 nodebid=1 nth1=10 nodebid=1 nth1=10 nth2=32 cell_util_th=0.90 aul_hsupa=1.50
For internal use 91 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Update of admission control UL scaling factor E-DCH channels channels can not be estimated estimated as it is the case for DCH • UL load of the E-DCH – The actual load in UL created by an E-DPDCH is variable depending on the decisions of the HSUPA scheduler algorithm-internal UL scaling factor can not be updated updated • Because of this fact, the algorithm-internal correctly in the conventional way if E-DPDCH traffic existing in the cell factor update rule for UMR6.5: UMR6.5: • UL AC Scaling factor
– IF the E-DCH/HS-DSCH cell has no Radio Link to any HSUPA UEs
use conventional averaged UL scaling factor in AC
– ELSE
For internal use 92 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
use fixed HSUPA fixed HSUPA UL scaling factor ( ( aul_hsupa) in AC
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
UL scaling factor HSUPA Parameter cre cr e ce cell ll ad adc2 c2 Name
Q3-Name
Shortname
Longna me
LMT-Name
Type
Range
Default
aUL_HSUPA
sbs3gRan HsupaScal Fact
SCFACTHSU PA
scaling FactorH supa
aul_hsupa
LMT: Real RC: Integer
LMT: 0,..,10 step by 0.01 RC: 0,..,1000
LMT: 1.5 RC: 150
HSUPA UL scaling factor used as fixed scaling factor in a cell, in case of HSUPA UEs which allocate Serving E-DCH RL exists in that cell
Example of command execution (hmi): cre cell adc2 cellid=1 adc2 cellid=1 nodebid=1 nth1=10 nth2=32 cell_util_th=0.90 aul_hsupa=1.50 aul_hsupa=1.50
For internal use 93 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Admission Control for HSDPA/HSUPA call New Call Establishment • Step1 Step1 : HSDPA / HSUPA blocking blocking check – ‘BLOCK BE to E-DCH’ and ‘BLOCK BE to HS-DSCH’ flags must be set to FALSE
• Step 2 : Load based based HSDPA/HSUPA HSDPA/HSUPA AC control control – Only the load of non-scheduled dedicated channels are considered. – The load is calculated in a conventional way using physical layer characteristics of the bearers mapped on these channels (UL/DL) and the scaling factor of AC (UL/DL):
– UL and DL DPCH for SRB signalling – UL DPCH for the HS-DPCCH (serving cell only) For internal use 94 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Admission Control for HSDPA/HSUPA call HSUPA Soft Handover based HSDPA/HSUPA HSDPA/HSUPA AC control: control: only the load of non• Load based scheduled dedicated channels is considered. calculated in a convention conventional al way using physical physical layer • The load is calculated characteristics of the bearers mapped on these channels (UL/DL) and the scaling factor of AC (UL/DL): – UL and DL DPCH for SRB signalling
• AC shall use admission control control load threshold threshold for handover handover bearers bearers for the UL/DL DPCH
For internal use 95 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Admission Control for HSDPA/HSUPA call Interfrequency Interfr equency Handover • DCH to E-DCH and E-DCH to E-DCH – Step1 : HSDPA / HSUPA blocking check – ‘BLOCK BE to E-DCH’ and ‘BLOCK BE to HS-DSCH’ flags must be set to FALSE
– Step 2 : Load based HSDPA/HSUPA AC control non-scheduled dedicated dedicated channels are considered. considered. – Only the load of non-scheduled conventionall way using physical layer – The load is calculated in a conventiona characteristics of the bearers mapped on these channels (UL/DL) and the scaling factor of AC (UL/DL):
– UL and DL DPCH for SRB signalling – UL DPCH for the HS-DPCCH (serving cell only)
• E-DCH to DCH – The conventional load based AC will be done for admission to DCH For internal use 96 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Admission Control for HSDPA/HSUPA call Inward Mobility • DCH/DCH to HS-DSCH/E-DCH – Step1 : HSDPA / HSUPA blocking check – ‘BLOCK BE to E-DCH’ and ‘BLOCK BE to HS-DSCH’ flags must be set to FALSE HSDPA/HSUPA UPA AC control control – Step 2 : Load based HSDPA/HS – UL and DL DPCH for SRB signalling – UL DPCH for the HS-DPCCH
•
HS-DSCH/DCH to HS-DSCH/E-DCH – Step1 : blocking check – ‘BLOCK BE to E-DCH’ flags must be set to FALSE – ‘BLOCK BE to HS-DSCH’ flags must be set to FALSE if serving cell changes HSDPA/HSUPA UPA AC control control – Step 2 : Load based HSDPA/HS – UL and DL DPCH for SRB signalling – UL DPCH for the HS-DPCCH
For internal use 97 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Admission Control for HSDPA/HSUPA call Serving Cell Change • Step1 : HSDPA / HSUPA blocking check – ‘BLOCK BE to E-DCH’ and ‘BLOCK BE to HS-DSCH’ flags must be set to FALSE
• Step 2 : Load based HSDPA/H HSDPA/HSUPA SUPA AC control – UL DPCH for the HS-DPCCH
For internal use 98 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Congestion Control
For internal use 99 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Congestion handling • Event Event Triggered common measurements measurements are used for congestion detection
• Two staged congestion resolution handling – Stage1 : BRA, CTS – Stage2 : BRA, CTS, Call Dropping
• HSDPA HSDPA DL/HSUPA DL/HSUPA UL UEs will be considere considered d only in Stage Stage 2 • UEs selection criteria for congestion handling handling – In DL or DL/UL Congestion: Downlink spreading factor (HSDPA DL/DCH UL UEs and HSDPA DL/HSUPA UL UEs, the SF of their associated DPCH channel will be used)
– UL Congestion: Minimum UL Channelisation Code Length For internal use 100 100 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
DL congestion handling Stage1 • Following Following UEs are handled in Stage1 Stage1 beginning beginning with the one having having the lowest SF: Single PS BE UEs (excludin (excluding g HSDPA DL/HSUPA DL/HSUPA UL and – For CTS: Single HSDPA DL/DCH UL UEs)
– For BRA: Multi-call PS BE UEs (except UEs with minimum rate, HSDPA DL /DCH UL multi-call and ,HSDPA DL/HSUPA UL multi-call)
Stage2 • Firstly, pre-emptable RLs are ordered ordered in ascending order of priority class and ascending order of DL SF
• Secondly, all non-pre-emptable non-pre-emptable RLs are ordered ordered in ascending order of DL SF Dropping are applied applied in every congestion congestion handling handling • CTS , BRA or Call Dropping period
• For single-call HSDPA DL/DCH UL, single-call HSDPA DL/HSUPA UL bearers CTS is applied For internal use 101 101 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
UL congestion handling Stage1 • Following UEs are handled in Stage1 beginning with the the one having the lowest Min. UL Channelisation Code length: Single PS BE UEs (excluding (excluding HSDPA DL/HSUPA DL/HSUPA UL , including including – For CTS : Single HSDPA DL/DCH UL UEs)
– For BRA : Multi-call PS BE UEs (except UEs with minimum rate, HSDPA DL/HSUPA UL multi-call)
Stage2 • Firstly, pre-emptable RLs are ordered ordered in ascending order of priority class and ascending ascending order order of Min. UL Channelisatio Channelisation n Code length.
• Secondly, all non-pre-emptable non-pre-emptable RLs are ordered ordered in ascending order of Min. UL Channelisation Code length. dropping are applied in every congestion congestion handling handling • CTS , BRA or call dropping period – For single-call HSDPA DL/DCH UL, single-call HSDPA DL/HSUPA UL bearers CTS is applied For internal use 102 102 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Congestion Control – Interactions with Scheduler R T W P
Congestion Level (N_ul+CCThreshold) Congestion Level – CC Hysteresis HSUPA Scheduler Offset
Maximum Target RTWP Current Cell Load
TIME
• It must be assured assured that HSUPA Traffic Traffic will not cause congestion congestion in a cell – Maximum Target RTWP value for scheduler is defined according to Congestion Control Thresholds in a cell
• Maximum Target RTWP is derived from from the O&M Parameter HSUPA HSUPA Scheduler Offset ( Offset (hsupa_oft hsupa_oft))
For internal use 103 103 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Scheduler offset parameter
Name
Q3-Name
Shortname
Longna me
LMTName
Type
Range
Unit
R/ W
Default
HSUPA_sc heduler_off set
sbs3gRanH supaSched Off
SCHDOFF SHSUPA
schedule rOffsetHs upa
hsupa_oft
LMT: Real RC: Integer
LMT: 0..10 step by 0.1 RC: 0..100
LMT : dB RC: 0.1* dB
R W **)
LMT: 0.5 RC: 5
Offset value to calculate Maximum Target Received Total Wide Band Power
Example of command execution (hmi): cre cell cctl cellid=1 cctl cellid=1 nodebid=1 ul_cngt=10.0 ul_cngh=2.0 dl_cngt=0.90 dl_cngh=0.15 mmti_rtwbp=10.00 mmti_tcp=10.00 k=1 ebd=ena etpchr=ena peri_cngh=0.5 mmfc_rtwp=0 mmfc_tcrp=0 cc_emg=false hsupa_oft=0.5 hsupa_oft=0.5
For internal use 104 104 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Outer loop power control
For internal use 105 105 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA OLPC Outer loop power control control is located located in the RNC and operates operates with block • Outer errors (CRC indication) as input to achieve a certain desired block error rate (BLER). retransmissions sions are performed performed by a • In HSUPA only case, MAC level retransmis HARQ protocol between the UE and the Node B The
BLER seen by the OPLC in the RNC will be much lower than the BLER seen by the HARQ process in the NodeB
OLPC Handling: without HARQ For internal use 106 106 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
with HARQ
HSUPA OLPC Becaus use e of this this fact fact,, for for HSUP HSUPA A it is more more reli reliab able le to have have an OLPC OLPC • Beca algorithm which considers the number of retransmission information.
• For For each each TTI TTI in whic which h E-DP E-DPDC DCH H tran transp spor ortt bloc block k is rece receiv ived ed or HARQ HARQ failure indication is signalled from NodeB, OLPC will update the SIR target of DPCCH as following: E-DPDCH
SIR target of DPCCH
[Number of HARQ Retransmissions > NHR_th > NHR_th AND AND Number of HARQ Retransmissions ≠ {13,14,15} ] OR HARQ Failure Indication Received
STEP_UP
[Number of HARQ Retransmissions <= NHR_th <= NHR_th AND AND Number of HARQ Retransmissions ≠ {13,14,15} ] AND NO HARQ Failure Indication Received
STEP_DOWN
Number of HARQ Retransmissions = {13,14,15}
No change in SIR target
NHR_th = min[NHR_th min[NHR_th,, Max_number_of_re Max_number_of_retransmissions_for_HSUP transmissions_for_HSUPA A] • NHR_th = For internal use 107 107 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Update of SIRtarget SIR ............................. step _ UP OLPC target HSUPA SIROLPC _ target : SIROLPC target ............... No _ chang _ in _ SIRtarget HSUPA BLERt arget ... step _ DOWN SIROLPC target 1 BLER t arget ΔHSUPA=step_sizeHSUPA.
(step_hsupa )
• In HSDPA/HSUP HSDPA/HSUPA A only case, the SIR target will be signalled to the closed loop loop powe powerr cont contro roll (CLP (CLPC) C) in the the Node Node B if the the foll follow owin ing g cond condit ition ion is satisfied:
SIROLPC _ t arget SIRCLPC _ t arget Update _ Threshold _ for _ SUP • ‘Update_threshold_for HSUPA’ is a new O&M parameter ( upthr_hsupa) For internal use 108 108 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
OLPC parameters for HSUPA Name
Q3Name
Shortn ame
Longna me
LMTName
Range
Unit
Defa ult
Description
Step size HSUPA
sbs3gRan HsupaStep Size
STEPSH SUPA
stepSize Hsupa
step_hsu pa
LMT: 0.0,..,25.5 step by 0.1 RC: 0,..,255
LMT: dB RC: 0.1*d B
LMT: 0.3 RC: 3
Step size of the outer loop power control for HSDPA DL/HSUPA UL only case
Update threshold for HSUPA
sbs3gRan UpdateThr esHsupa
UPDTHR HSUPA
updateTh resHsupa
upthr_hsu pa
LMT: 0.0,..,25.5 step by 0.1 RC: 0,..,255
LMT: dB RC: 0.1*d B
LMT: 0.1 RC: 1
Threshold value for updating the SIR target in NodeB for HSDPA DL/HSUPA DL/HSUPA UL only case
NHR_th
sbs3gRan NhrThres
NHRTHR
nhrThres hold
nhr_th
0..15
-
0
NHR to decide bad E-DPDCH quality. It is recommended to set this parameter smaller than ‘Max number of retransmissions for HSUPA’ for an effective functioning OLPC. The values 13,14 and 15 are not recommended to set, because in 3GPP these values are reserved. Should not be changed to values greater than 0 in order to avoid throughput degradation.
Example of command execution (hmi): cre olpc thr_upd=0.1 olpc thr_upd=0.1 step_size=0.3 lowthr_sirerr=-3 upthr_sirerr=3 mmfc_sirerr=0 ofs_thr2e=1.0 ofs_thr2f=2.0 hyst_tme=80 hyst_tmf=80 step_hsupa=0.3 hyst_tmf=80 step_hsupa=0.3 upthr_hsupa=0.1 upthr_hsupa=0.1 nhr_th=0 For internal use 109 109 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
OLPC parameters for HSUPA: NHR_th When NHR_th NHR_th is set to a value value >0, lab tests tests have shown negati negative ve impac impactt on UL • When throughput. (assign the least needed resources resources to maintain maintain • Due to the nature of power control (assign a given QoS), the OLPC will adapt the SIR target in a way, that the majority of the E-DPDCH transmissions will be done with NHR_th-times NHR_th-times retransmissions (e.g. 1 retransmission for NHR_th=1). With 1 retr retran ansm smis issi sion on made made for for near nearly ly each each tran transm smis issi sion on (NHR (NHR_t _th= h=1) 1),, the the • With expected throughput is halved with respect to an environment, where no or only little retransmission are done.
For the moment, the recommendation is to leave NHR_th at 0 in order to have maximum throughput and minimum latency.
For internal use 110 110 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
UE categories
For internal use 111 111 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
HSUPA UE categories different UE categories categories are defined • Like in HSDPA, also in HSUPA different categories s exist • 6 HSUPA UE categorie mainly differ in the number number of supported supported E-DPDCHs and SFs as well • They mainly as in the supported TTI sizes
• Category 6 offers the highest throughput, throughput, category 1 the lowest. E-DCH category
Maximum number of E-DCH codes transmitted
Minimu m spreadin g factor
Support for 10 and 2 ms TTI EDCH
Maximum number of bits of an E-DCH transport block transmitted within a 10 ms E-DCH TTI
Maximum number of bits of an E-DCH transport block transmitted within a 2 ms E-DCH TTI
Category 1
1
SF4
10 ms TTI only
7110
-
Category 2
2
SF4
10 ms and 2 ms TTI
14484
2798
Category 3
2
SF4
10 ms TTI only
14484
-
Category 4
2
SF2
10 ms and 2 ms TTI
20000
5772
Category 5
2
SF2
10 ms TTI only
20000
-
Category 6
4
SF2
10 ms and 2 ms TTI
20000
11484
Cat. 1+3 are fully supported in UMR6.5 and RAS06. Others only with 10ms TTI and SF4
NOTE: When 4 codes are transmitted in parallel, two codes shall be transmitted with SF2 and two with SF4 For internal use 112 112 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
TS 35.306 HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
User plane architecture for a single MAC-d flow
RLC
DCCH / DTCH
RLC PDU:
DATA
Header
MAC-d DATA
MAC-d PDU:
Disassembly
Reordering
MAC-es
MAC-es PDU:
MAC-d Flow
Iub FP:
MAC-e PDU:
DDI
DDI1
TSN
N1
DDI0
DATA1
HARQ
L1
For internal use 113 113 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
Transport block: E-DPDCH
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
DATA
N
MAC-e header
MAC-e
DATA
DATA
SI
Padding (Opt)
Transport block strukture Transport block of E-DPDCH, MAC-e
DDI
N
TSN
6bit
6bit
6bit
H e a d e r 1 6
Payload 320 bit
H e a d e r 1 6
H e a d e r 1 6
Payload 320 bit
Payload 320 bit
SI (opt.) 18 bit
( o p t i o n a l )
P a d d i n g
RLC PDU (w/ header) DDI: Data DDI: Data Description Indicator N: Number N: Number of MAC-es PDU, fixed to 1 in UMR and RAS TSN: Transmission TSN: Transmission sequence number SI: Scheduling SI: Scheduling information, per TTI or also only periodic
MAC-es
Example:
• Transport block size: 2058 bit (E-TFCI: 71) (as the result of the E-TCF selection process) • Bits available for RLC PDUs: 2058 bit – (6+6+6) bit = 2040 bit • Number of 336 bit RLC PDU per TB: 2040 / 336 = 6.07
6 PDUs
• Max. RLC throughput: bit/PDU *100 = 0.192 = 0.192 Mbps throughput: 6 PDU * 320 bit/PDU
• The size of the MAC-e/es PDU (and so the number of RLC PDUs per TTI) is determined by the E-TFC selection process in the UE. For internal use 114 114 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Example: HSUPA UE 3 throughput @ 10ms TTI category 3 UE has a max. TB size of 14484 bit@10ms bit@10ms TTI • A category transmitted d per TTI • With a PDU size of 336 bit, max. 43 RLC PDUs can be transmitte – (14484 bit – 18 bit) / 336 bit = 43.1 ( 43 PDUs, rest of the TB is padding)
• Payload Payload of one RLC PDU: 320 bit bit (336 bit – 16 bit header) header) • Max. throughput: throughput : 43 PDU * 320 bit/PDU * 100 = 1.376 Mbps E-DCH category
Maximum number of E-DCH codes transmitted
Minimum spreading factor
Support for 10 and 2 ms TTI EDCH
Maximum number of bits of an E-DCH transport block transmitted within a 10 ms E-DCH TTI
Maximum number of bits of an E-DCH transport block transmitted within a 2 ms EDCH TTI
Category 1
1
SF4
10 ms TTI only
7110
-
Category 2
2
SF4
10 ms and 2 ms TTI
14484
2798
Category 3
2
SF4
10 ms TTI only
14484
-
Category 4
2
SF2
10 ms and 2 ms TTI
20000
5772
Category 5
2
SF2
10 ms TTI only
20000
-
Category 6
4
SF2
10 ms and 2 ms TTI
20000
11484
For internal use codes are transmitted in parallel, shall be transmitted 115 115NOTE:©When Noki Nokia a4 Siem Si emen ens s Netw Ne twor orks ks HSUP HStwo UPA Acodes / JKuh JKuhr r / Sept Se ptem embe berr 2007 2007with SF2 and two with SF4
Transport Block Size Selection (TS25.321) different E-TFC Transport Block Size tables that shall shall be • 3GPP has standardized different used by the UE for the TB size selection on the E-DCH selects one E-TFCI out of that table table according according to it‘s capabilties it‘s capabilties (e.g. (e.g. max • The UE selects TB size of the UE), the grant the grant assigned by assigned by the scheduler and the amount the amount of data to be transfered. transfered. (2ms, 10ms), different TB Size tables are defined defined • For the different TTIs (2ms, implementation, only the tables for the 10ms TTI are applicable applicable • In the current implementation, Via O&M parameter it it can be chosen, which table the UE shall use. • Via O&M
E-TFC: E-DCH Transport Format Combination E-TFCI: E-DCH Transport Format Combination Indicator For internal use 116 116 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
10ms TTI E-DCH Transport Block Size Table 0 E-TF E-TFCI CI
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
TB Size Size (bits) 18 120 124 130 135 141 147 153 159 166 172 180 187 195 203 211 220 229 239 249 259 270 281 293 305 317 331 344 359 374
E-TF E-TFCI CI
TB Size Size (bits)
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59
For internal use 117 117 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
389 405 422 440 458 477 497 517 539 561 584 608 634 660 687 716 745 776 809 842 877 913 951 991 1032 1074 1119 1165 1214 1264
E-TF E-TFC CI
60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89
TBSize TBSize (bits)
ETFCI
TB Size Size (bits)
ETFCI
TB Size Size (bits)
1316 1371 1428 1487 1549 1613 1680 1749 1822 1897 1976 2058 2143 2232 2325 2421 2521 2626 2735 2848 2966 3089 3217 3350 3489 3634 3784 3941 4105 4275
90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119
4452 4636 4828 5029 5237 5454 5680 5915 6161 6416 6682 6959 7247 7547 7860 8186 8525 8878 9246 9629 10 10028 10 10444 10 10877 11 11328 11 11797 12 12286 12 12795 13 13325 13 13877 14 14453
120 121 122 123 124 125 126 127
15 15051 15 15675 16 16325 17 17001 17 17706 18 18440 19 19204 20 20000
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
In UMR6.5, UMR6.5, the parameter etfci_idx is used to select the table. UMR6.5 default: default: Table1 In RAS06, RAS06, always Table 1 is used.
10ms TTI E-DCH Transport Block Size Table 1 E -T -T F CI CI
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
T B S iz iz e (bits) 18 186 204 354 372 522 540 690 708 858 876 1026 1044 1194 1212 1362 1380 1530 1548 1698 1716 1866 1884 2034 2052 2370 2388 2706 2724 3042 3060 3378 3396 3732 3750 4068 4086 4404 4422 4740 4758
For internal use 118 118 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
E -T -T F CI CI
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81
T B S iz iz e (bits) 5076 5094 5412 5430 5748 5766 6084 6102 6420 6438 6756 6774 7092 7110 7428 7464 7764 7800 8100 8136 8436 8472 8772 8808 9108 9144 9444 9480 9780 9816 10116 10152 10452 10488 10788 10824 11124 11178 11460 11514 11796
E -T -T F CI CI
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
T B S iz iz e (bits) 11850 12132 12186 12468 12522 12804 12858 13140 13194 13476 13530 13812 13866 14148 14202 14484 14556 14820 14892 15156 15228 15492 15564 15828 15900 16164 16236 16500 16572 17172 17244 17844 17916 18516 18606 19188 19278 19860 19950
In UMR6.5, UMR6.5, the parameter etfci_idx is used to select the table. UMR6.5 default: default: Table1 In RAS06, RAS06, always Table 1 is used.
Transport Block Size Table: O&M Parameter
Name
Q3-Name
Shortname
Longn ame
LMTName
Type
Range
Unit
R/ W
Default
E-TFCI Table Index
sbs3gRanEt fciTableIdx
ETFCITBIDX
etfciTabl eIndex
etfci_idx
Integer
0,..,1
-
RW
1
Indicates which standardised E-TFCS Transport Block Size Table shall be used. The related tables are specified in 3GPP TS25.321.
Example of command execution (hmi): cre edcinf edch_pref=rv edcinf edch_pref=rv0 0 etfci_idx=1 pesc_ng=every etfci_idx=1 pesc_ng=every pesc_g=every maxrm_edch=15 edch_po=0
For internal use 119 119 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
Overview: New Objects and Parameters related to HSUPA in UMR6.5
For internal use 120 120 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007
New HMI objects & parameters (office data) ver=00000_06/13/07 size=0005449055 # New Header field containing the number of HSUPA licenses. Not relevant for HSUPA operation but only for consistency check purposes. hsupa_license=1026 # New HDHT HW Card for HSUPA operation. cre eq eqp p hd hdht1 ht1010 0100 0 cp0 cp00 0 # Existing OLPC object is extended by 3 parameters for HSUPA power control. cre olpc thr_upd=0.1 step_size=0.3 lowthr_sirerr=-3 lowthr_sirerr=-3 upthr_sirerr=3 upthr_sirerr=3 mmfc_sirerr=0 ofs_thr2e=1.0 ofs_thr2f=2.0 ofs_thr2f=2.0 hyst_tme=80 hyst_tme=80 hyst_tmf=80 step_hsupa=0.3 step_hsupa=0.3 upthr_hsupa upthr_hsupa=0.1 =0.1 nhr_th=0 # New object for HSUPA admission control. One instance per HSUPA cell. cre cell adc2 cell cellid=1 id=1 node nodebid= bid=0 0 nth1 nth1=10 =10 nth2 nth2=32 =32 cell cell_uti _util_th l_th=0.9 =0.90 0 aul_ aul_hsup hsupa=1. a=1.50 50 # Existing congestion control object extended by one paramater for HSUPA congestion control cre cell cctl cellid=1 cellid=1 nodebid= nodebid=0 0 ul_cngt= ul_cngt=10.0 10.0 ul_cngh=2 ul_cngh=2.0 .0 dl_cngt=0 dl_cngt=0.90 .90 dl_cngh= dl_cngh=0.15 0.15 mmti_rtw mmti_rtwbp=1 bp=10.00 0.00 mmti_tcp mmti_tcp=10. =10.00 00 k=1 ebd=ena ebd=ena etpchr=e etpchr=ena na peri_cng peri_cngh=0. h=0.5 5 mmfc_rtw mmfc_rtwp=0 p=0 mmfc_tcrp mmfc_tcrp=0 =0 cc_emg=f cc_emg=false alse hsupa_oft=0.5 # New object for E-DCH channel configuration. One instance per RNC. cre edci edcinf nf edch edch_pre _pref=rv f=rv0 0 etfc etfci_id i_idx=1 x=1 pes pesc_ng= c_ng=ever every y pesc pesc_g=e _g=every very maxr maxrm_edc m_edch=15 h=15 edch edch_po= _po=0 0 # New object for HSUPA channel power and HARQ process handling. One instance per HSUPA cell. cre hsup hsupa a cell cellid=1 id=1 node nodebid= bid=0 0 no_r no_rgch_ gch_hich hich=4 =4 po_a po_agch= gch=1.25 1.25 po_h po_hich= ich=1.25 1.25 po_r po_rgch= gch=1.25 1.25 pr_e pr_edch=3 dch=30 0
For internal use 121 121 © Noki Nokia a Siem Siemen ens s Netw Networ orks ks
HSUP HSUPA A / JKuh JKuhrr / Sept Septem embe berr 2007 2007