okey, like Rishi explanation so for RAN12 is confirm about HSDPA using SoftHO![]()
okey, like Rishi explanation so for RAN12 is confirm about HSDPA using SoftHO![]()
If this document usefull, then giving some reputations is highly appreciated.
note : see default password
Hi, just to make a comment on this topic. In DCH SHO there is a macro diversity gain since the actual data is send in the SHO RL's which gives the diversity gain.
For HSDPA , pre R8 there is always HHO for HS-DSCH which is the channel that carries the actual payload, as well as HS-SCCH.
Post Release8 , there is enhancement to the HSDPA mobility SCC which allows the UE to read the signalling from target cell for the purpose of serving cell change once the cell is added to active set. Further to this, the UE is able to read the HS-SCCH channel of the target cell once there is indication of change in serving cell (e1d). This may be considered SHO, but the actual data is still only send on the serving cell and not to all cell in the active set (as per DCH SHO) but the performance should be better then the pre R8 SCC.
I've attached a report which shows this performance improvements.
Well, HSDPA uses SF 16 but don't forget that everything is scheduled on a TTI=2ms basis. HSDPA CM is implemented as higher layer scheduling (HLS) where during CM periods no data is transmitted (i.e. TTIs coinciding with CM periods are considered for schediling by the scheduler at the Node-B for this UE)
Now, for SRB you have two options:
1. if SRB is transmitted over DCH, this is using SF 256, and during CM we have again two alternatives (depending on the UTRAN vendor) either HLS (i.e. no tramsission at all during CM periods) or SF halving hence SF 128 is used.
2. In Rel7 we could have SRB over HSDPA, hence whatever we said earlier about HSDPA CM is applicable
hope this helps
Guys guys be careful
like i said HSDPA does not require SHO. don't forget SHO is there because of the associated-DCH for the SRB.
RAN12 also supports SRB over HSDPA which cancels the requirement for A-DCH. in this case if you use this feature then A-DCH is not activated at all and in the downlink the UE behaves like in GSM. just doing cell changes when moving from one cell to the other.
(for the uplink it depends what features you are using, but there is a possibility to have voice over HSPA calls which look identical to GSM calls in terms of mobility behaviour)
Why I can not download att. file??
Who know the problem about it
Bookmarks