Professional Documents
Culture Documents
NOKIA 2004
COMPANY CONFIDENTIAL
Agenda
HSDPA Logical Split & Responsibilities Quality of Service in HSDPA Measurements and UE capabilities Flow Control RRM in the RNC QoS Summary & TCP results RRM in RAN05
NOKIA 2004
COMPANY CONFIDENTIAL
NOKIA 2004
COMPANY CONFIDENTIAL
SM-SC C
A R TE MT
Iu Uu
Gr
NOKIA 2004
UTRAN Architecture
Uu
RNS
Iu CS
Node B Node B
Iub
RNC RNC
Iur
ME ME
UE
Node B Node B
RNC
RNS
Iu PS
SGSN SGSN
CN
UTRAN
NOKIA 2004
COMPANY CONFIDENTIAL
DTCH DCCH
DCCH
DTCH
COMPANY CONFIDENTIAL
Option b
NOKIA 2004
Option b
NOKIA 2004
QoS settings QoS settings UE capabilities UE capabilities & state & state Link Link Adaptation Adaptation
NOKIA 2004
COMPANY CONFIDENTIAL
Decides whether a user is admitted or not. Located in CRNC RNC Admission Admission Control Control Capacity request User data Resource Resource Allocation Allocation
QoS settings QoS settings UE capabilities UE capabilities & state & state Link Link Adaptation Adaptation
10
NOKIA 2004
COMPANY CONFIDENTIAL
Decides whether a user is admitted or not. Located in CRNC RNC Admission Admission Control Control Capacity request User data Resource Resource Allocation Allocation
QoS QoS control control Takes care of resource allocation for HSDPA. Located in CRNC
QoS settings QoS settings UE capabilities UE capabilities & state & state Link Link Adaptation Adaptation
11
NOKIA 2004
COMPANY CONFIDENTIAL
Decides whether a user is admitted or not. Located in CRNC RNC Admission Admission Control takesrequest Capacity care of ControlQoS Control quality of service and UE capabilities User sends this and data information to the Node-B. Located in SRNC Resource Resource Allocation Allocation Codes (and power)
QoS QoS control control Takes care of resource allocation for HSDPA. Located in CRNC
QoS settings QoS settings UE capabilities UE capabilities & state & state Link Link Adaptation Adaptation
12
NOKIA 2004
COMPANY CONFIDENTIAL
Decides whether a user is admitted or not. Located in CRNC RNC Admission Admission Control takesrequest Capacity care of ControlQoS Control quality of service and UE capabilities User sends this and data information to the Node-B. Located in SRNC Resource Resource Allocation Allocation Codes (and power)
UE sends feedback Functional Split Overviewuplink information in (ACK/NACK & CQI) Node-B Flow Control Flow Control Data Buffer Data Buffer HSDPA resource HSDPA resource monitor unit monitor unit Uplink UE Uplink UE information information (HS-DPCCH) (HS-DPCCH) ACK/NACK CQI & ACK/NACK HS-DSCH Packet Packet Scheduler Scheduler HS-SCCH Node-B Node-B measurements measurements
QoS QoS control control Takes care of resource allocation for HSDPA. Located in CRNC
QoS settings QoS settings UE capabilities UE capabilities & state & state Link Link Adaptation Adaptation
13
NOKIA 2004
COMPANY CONFIDENTIAL
Decides whether a user is admitted or not. Located in CRNC RNC Admission Admission Control takesrequest Capacity care of ControlQoS Control quality of service and UE capabilities User sends this and data information to the Node-B. Located in SRNC Resource Resource Allocation Allocation Codes (and power)
UE sends feedback Functional Split Overviewuplink information in (ACK/NACK & CQI) Node-B Flow Control Flow Control Data Buffer Data Buffer HSDPA resource HSDPA resource monitor unit monitor unit Uplink UE Uplink UE information information (HS-DPCCH) (HS-DPCCH) ACK/NACK CQI & ACK/NACK HS-DSCH Packet Packet Scheduler Scheduler HS-SCCH Node-B Node-B measurements measurements
QoS QoS control control Takes care of resource allocation for HSDPA. Located in CRNC
QoS settings QoS settings UE capabilities UE capabilities & state & state Link Link Adaptation Adaptation
Total power used by the Node-B and power of the DPCH per UE
14
NOKIA 2004
COMPANY CONFIDENTIAL
15
NOKIA 2004
COMPANY CONFIDENTIAL
If end-to-end QoS is to be guaranteed for the complete UTRAN architecture, all components must be specified to behave according to certain rules and have a certain well-defined responsibility. The rules should be configurable such that in the case of HSDPA, we can achieve a dynamic (e.g. time-varying depending on traffic) trade-off between tight QoS control and high system capacity.
RAN
Quality of Service : the collective effect of service performances that determine the degree of satisfaction of a user of a service.
16 NOKIA 2004 HSDPA, June 2004.
COMPANY CONFIDENTIAL
Streaming has a guaranteed bitrate and maximum delay and is thus more complex to deal with.
HDSPA
Background
17
NOKIA 2004
COMPANY CONFIDENTIAL
What is QoS?
Key QoS parameters for different traffic classes: Conversational Blocking, Call Dropping Delay Call Quality (BLER) Interactive Throughput Transmission Delay Queuing Delay Streaming Blocking Call Dropping Delay Jitter Call Quality (BLER) Background Throughput Transmission Delay Queuing Delay
18
NOKIA 2004
COMPANY CONFIDENTIAL
Traffic class (TC): Is set for each Integer representing conversational (=0), RNC user/PDP combination (can be re- streaming (=1), interactive (=2), and background negotiated on very slow basis). (=3) traffic. Traffic handling priority (THP): Is set for each user/PDP combination (can be renegotiated on very slow basis). Integer [0-2] where 0 denotes the highest priority. Only valid for the interactive traffic class (TC=2). RNC
19
NOKIA 2004
COMPANY CONFIDENTIAL
One value per PDP context, which indicates the discard timer per MAC-d packet. This timer indicates when the Node-B can discard a SDU. This indicates the guaranteed number of bits per second that Node B should deliver over the air interface under normal operating conditions (provided there is data to deliver).
Guaranteed bitrate
With the discard timer and the guaranteed bitrate the bitrate and delay jitter can be With the discard timer and the guaranteed bitrate the bitrate and delay jitter can be controlled. controlled.
20 NOKIA 2004 HSDPA, June 2004.
COMPANY CONFIDENTIAL
21
NOKIA 2004
COMPANY CONFIDENTIAL
"The transfer delay requirements for streaming are typically in a range where at least in a part of this range RLC re-transmission may be used. It is assumed that the application's requirement on delay variation (delay jitter) is expressed through the transfer delay attribute, which implies that there is no need for an explicit delay variation attribute." The transfer delay attribute of streaming class STILL defines the transfer delay, exactly as for the Conversational class. The network designer may derive the delay variation tolerance implicitly from the given transfer delay value. In other words, delay variation allowed in the network is NOT subject to any limit, as long as the transfer delay value is met. In practice, the allowed delay variation must be less than or equal to the transfer delay.
This implies
1. 2. 3. 4.
The discard time value given by the RNC to the Node-B should be set, while taking The discard time value given by the RNC to the Node-B should be set, while taking the e2e delay and other delay components (for instance in the CN) into account. the e2e delay and other delay components (for instance in the CN) into account. This is not used in Nokias first HSDPA release. This is not used in Nokias first HSDPA release.
22 NOKIA 2004 HSDPA, June 2004.
COMPANY CONFIDENTIAL
23
NOKIA 2004
COMPANY CONFIDENTIAL
Fulfill the discard timer and guaranteed bitrate constraints of all traffic. If it is not possible to fulfill these constraints (overload), then the delay constraints of the traffic with the highest SPI priority must be fulfilled first.
By having the SPI mapping and the discard timer and guaranteed bit rate values, the operator can specify the amount of QoS control for all future services. For instance setting the SPI to one value for all traffic and setting the discard timer values to infinity and the guaranteed bitrate to zero means there is no QoS control (everything is best effort). Another possibility is to only define discard timer and guaranteed bitrate values for the streaming traffic and giving streaming the highest priority (lowest SPI value).
24
NOKIA 2004
COMPANY CONFIDENTIAL
Retransmissions in HSDPA
HSDPA introduces L1 H-ARQ on top of the existing RLC ARQ. For traffic based on TCP there is an additional layer of retransmissions (TCP retransmissions) Internet server Node-B RNC
RLC layer retransmissions TCP layer retransmissions. (incl. slow start effect)
25 NOKIA 2004 HSDPA, June 2004.
L1 retransmissions.
UE
COMPANY CONFIDENTIAL
UE
COMPANY CONFIDENTIAL
Scheduling delay modelled as M/M/1/N queing with queing load of 50 and 80%
DCH 2003
COMPANY CONFIDENTIAL
600,00
500,00
400,00
200,00
100,00
0,00
Scheduling delay modelled as M/M/1/N queing with queing load of 50 and 80%
COMPANY CONFIDENTIAL
29
NOKIA 2004
COMPANY CONFIDENTIAL
Node-B measurements
Non HSDPA Power measurement: The amount of transmitted carrier power of all codes not used by HS-PDSCH or HS-SCCH transmission over a measurement period. HS-DSCH required power, reports the minimum necessary power per priority class to meet the Guaranteed Bit Rate for all the established HS-DSCH connections belonging to this priority class (SPI). For each priority class, a list of UEs requiring a particularly high amount of power to meet the Guaranteed Bit Rate for their established HS-DSCH connections may be included. HS-DSCH provided bitrate, reports the total number of MAC-d PDU bits per priority class transmitted over the radio interface during the measurement period, divided by the duration of the measurement period. Only bits from acknowledged MAC-hs PDUs are taken into account. A code utilization measurement is expected to be added to the specs, but in what form is still being discussed in 3GPP.
30
NOKIA 2004
COMPANY CONFIDENTIAL
UE reference combinations
Reference combination 1.2 Mbps class 3.6 Mbps class 50 6 7 Mbps class 100 8 10 Mbps class 150 8 RLC and MAC-hs parameters Total RLC AM and MAC-hs buffer size (kbytes) 50 Maximum number of AM RLC entities PHY parameters FDD HS-DSCH category 1 5 5 2 7,300 57,600 7 10 2 14,600 115,200 9 15 2 20,432 172,800 6
Maximum number of HS-DSCH codes received 5 Minimum inter-TTI interval (ms) Maximum transport block size per TTI (bits) Total number of soft channel bits 6 7,300 19,200
31
NOKIA 2004
COMPANY CONFIDENTIAL
Flow Control
32
NOKIA 2004
COMPANY CONFIDENTIAL
CAPACITY REQUEST
The HS-DSCH Capacity Request procedure provides means for the RNC to request HS-DSCH capacity by indicating the user buffer size in the RNC for a given priority level (CmCH-PI). The RNC is allowed to reissue the HS-DSCH Capacity Request if no CAPACITY ALLOCATION has been received within an appropriate time threshold.
33
NOKIA 2004
COMPANY CONFIDENTIAL
HS-DSCH Capacity Allocation procedure is generated within the Node B. It may be generated either in response to a HS-DSCH Capacity Request or at any other time. The current understanding in 3GPP is that the Node-B is in control of the flow, so the flow control is mainly controlled by the Node-B sending capacity allocation messages. The Node-B does know the status of the buffers in the RNC by the capacity request. So the Node B may use this message to modify the capacity at any time, irrespective of the reported user buffer status.
34 NOKIA 2004 HSDPA, June 2004.
COMPANY CONFIDENTIAL
Any capacity previously granted is replaced. If HS-DSCH Credits = 0, the RNC shall immediately stop transmission of MAC-d PDUs. If HS-DSCH Credits = 2047, the RNC can transmit MAC-d PDUs with unlimited capacity. If the HS-DSCH Repetition Period = "unlimited repetition period" it indicates that the RNC may transmit the specified number of MAC-d PDUs for an unlimited period according to the bounds of Maximum MAC-d PDU Length, HS-DSCH Credits and HS-DSCH Interval .
35 NOKIA 2004 HSDPA, June 2004.
COMPANY CONFIDENTIAL
UE1 Scheduling
36
NOKIA 2004
COMPANY CONFIDENTIAL
38
NOKIA 2004
When the RNC has been granted capacity by the Node B via the HSDSCH CAPACITY ALLOCATION Control Frame or via the HS-DSCH initial capacity allocation and the RNC has data waiting to be sent, then the HS-DSCH DATA FRAME is used to transfer the data. Multiple MAC-d PDUs of same length and same priority level (CmCHPI) may be transmitted in one MAC-d flow in the same HS-DSCH DATA FRAME.
39
NOKIA 2004
COMPANY CONFIDENTIAL
0 FT CmCH-PI
The data is coming from the RNC to Node-B in MAC-d PDUs. For HS-DSCH the MAC-d PDU format equals the MAC-d PDU format for the non HS-DSCH case. These MAC-d PDU contain a header, a tail and a data field. The minimum size of the header is 22 bits.
MAC-d PDU Length MAC-d PDU Length NumOfPDU User Buffer Size User Buffer Size ( cont) Spare bits 7-4 MAC-d PDU 1 Spare bits 2-0 header
40
NOKIA 2004
COMPANY CONFIDENTIAL
MAC-d PDU
MAC-hs header MAC-hs SDU MAC-hs SDU Mac-hs payload Padding (opt)
The different header fields in the MAC-hs PDU are given by:
- Queue identifier (Queue ID) provides identification of the reordering queue in the receiver (3 bits). - Transmission Sequence Number (TSN) provides an identifier for the transmission sequence number on the HS-DSCH (6 bits). - Size index identifier (SID) identifies the size of a set of consecutive MAC-d PDUs (3 bits). - Number of MAC-D PDUs (N) identifies the number of consecutive MAC-d PDUs with equal size (7 bits). The maximum number of PDUs transmitted in a single TTI shall be assumed to be 70. If more PDUs are received, the UE behaviour is unspecified. - Flag (F) is a flag indicating if more SID fields are present in the MAC-hs header or not. If the F field is set to "0" the F field is followed by a SID field. If the F field is set to "1" the F field is followed by a MAC-d PDU.
41 NOKIA 2004 HSDPA, June 2004.
COMPANY CONFIDENTIAL
42
NOKIA 2004
COMPANY CONFIDENTIAL
Admission Control
Admission Control is located in the CRNC and decides whether or not a user is allowed to start using HS-DSCH (and other channels). The challenge for admission control is on how the CRNC can know whether the Node-B has room for a new user. The measurements: Non HSDPA Power measurement, Total Power, HS-DSCH required power and HS-DSCH provided bitrate can be used. In Nokia first HSDPA release admission simply consist of checking whether the number of HSDPA users is below a certain threshold (16 users) This solution however does not allow streaming users on the HS-DSCH, since no guarantees can be given that they can be served. This solution is simple.
43
NOKIA 2004
COMPANY CONFIDENTIAL
at different Node-Bs
Intra Node-B HS-DSCH to HS-DSCH handover: handover between two HS-DSCH
Compressed mode and HSDPA is supported in Nokias first release and thus are interfrequency handovers from HSDPA possible (10 ms gaps).
44
NOKIA 2004
COMPANY CONFIDENTIAL
previously best P-CPICH in its active set. A hysteresis margin can be included.
Inter Node-B HO requires reset of the MAC-hs for the user in in the source Node-B. Hence, buffered PDUs in the source Node-B are lost, i.e., Source Node-B needs to be recovered by higher layers (typically RLC layer). HS-DSCH HSDPA is not supported over the Iur in Nokias implementation, so the Node-Bs need to be below the same RNC. Otherwise relocation is used, which may lead to the loss of more PDUs
SRNC
Target Node-B
HS-DSCH
UE
45
NOKIA 2004
COMPANY CONFIDENTIAL
RLC
MAC-d
Flow control
MAC-hs
RLC
MAC-d
MAC-hs
46
NOKIA 2004
COMPANY CONFIDENTIAL
47
NOKIA 2004
COMPANY CONFIDENTIAL
Handover from HS-DSCH to DCH requires reset of the MAC-hs, so recovery of lost PDUs in the MAC-hs is required. Thus, from a logical point of view intra Node-B HS-DSCH to HS-DSCH handover is simpler than handover from HS-DSCH to DCH. Handover from DCH to HS-DSCH should in principle be relative simple to implement, but it is questionable whether it is really needed.
48
NOKIA 2004
COMPANY CONFIDENTIAL
HS-DSCH
49
NOKIA 2004
COMPANY CONFIDENTIAL
HSDPA coverage area. This may cause problems, since a minimum of 6-8 HSDPA UEs is required per cell to obtain the multi-user diversity gain from intelligent scheduling. For a lower number of HSDPA UEs per cell , it may also be difficult to have 100% utilization of the HS-DSCH.
The HSDPA cell capacity gain is lower for the limited coverage
scenario, since HSDPA capable UEs in SHO-mode are forced to use Rel99 DCH.
50
NOKIA 2004
COMPANY CONFIDENTIAL
51
NOKIA 2004
COMPANY CONFIDENTIAL
52
NOKIA 2004
COMPANY CONFIDENTIAL
53
NOKIA 2004
COMPANY CONFIDENTIAL
QoS thoughts
54
NOKIA 2004
COMPANY CONFIDENTIAL
55
NOKIA 2004
COMPANY CONFIDENTIAL
100 kB webpage 100 kB webpage download download Including TCP slow Including TCP slow start (RTT = 200 ms) start (RTT = 200 ms)
High bitrates give a gain in download time, but the improvement is not linear High bitrates give a gain in download time, but the improvement is not linear with the bitrate increase due to the TCP slow start with the bitrate increase due to the TCP slow start
56 NOKIA 2004 HSDPA, June 2004.
COMPANY CONFIDENTIAL
Utilisation on Utilisation on dedicated channels is dedicated channels is low for high bitrates, low for high bitrates, while the utilisation of while the utilisation of the HS-DSCH can get the HS-DSCH can get very close to 100% due very close to 100% due to the time duplex to the time duplex nature. This is aapart of nature. This is part of the gain from HSDPA! the gain from HSDPA! 100 kB webpage 100 kB webpage download download
57
NOKIA 2004
COMPANY CONFIDENTIAL
58
NOKIA 2004
COMPANY CONFIDENTIAL
59
NOKIA 2004
COMPANY CONFIDENTIAL
60
NOKIA 2004
COMPANY CONFIDENTIAL
Interfaces
Open Iub; the same req. for RNC and BTS
Rel-5 Do we support the private messages? If not we miss: Non HSDPA power measurement BTS init is different Private messages also preferred to not to use Common measurement procedure at all in RN2.1 Work amount: 0 person weeks
Iu: PS+CS Iu interface supported like in RN2.1 Iur: No Iur support for HSDPA
Rejection of HS-DSCH setup in DRNC
61
NOKIA 2004
COMPANY CONFIDENTIAL
HSDPA performance
Pico cell HSDPA RL throughput ~ 2 Mbit/s Macro cell HSDPA RL throughput ~ 1 Mbit/s RNC: Peak HSDPA throughput Iub: 2Mbit/s
Divided between # of subscribers
RNC internal: Peak for one subs: 1 Mbit/s Handling of RAB maximum bit rate:
Ignored by RRM Can be the input for platform / transport resources
62
NOKIA 2004
COMPANY CONFIDENTIAL
Reference RABs
No Multi RAB
HSDPA + 64 kbit/s UL + SRB HSDPA + 384 kbit/s UL + SRB RN2.1 reference RABs for non HSDPA UEs
separately, preferred
Option2: The HS-DSCH and its RAB is cleared Functionality not guaranteed with other vendors CN Option3: reject the new RABs and wait for escalation
63
NOKIA 2004
COMPANY CONFIDENTIAL
idle will cause capacity problems due to long inactivity detection time even with the small amount of HSDPA UEs
The resource reservation is done based on max. bit rate in DMCU
Inactivity detection as currently must be further studied for HSDPA (Jukka N.)
One additional parameter for HSDPA inactivity in MCC
64
NOKIA 2004
COMPANY CONFIDENTIAL
From idle:
RANAP: RAB Assignment 0/0 DCH allocated, no changes, depends on basic RN2.1 implementation NBAP: Radio Link Reconfiguration & RRC: Radio Bearer Reconfiguration & AAL2 setup
From Cell_FACH
NBAP: Radio Link Setup & RRC: Radio Bearer Reconfiguration & AAL2 setup
Release
Moving to DCH 0/0 (evaluated elsewhere)
65
NOKIA 2004
COMPANY CONFIDENTIAL
Static power budget for BTS (WCEL) CQI, ACK, NACK, T1, Discard Timer (PIIFIL) MAC, RLC, HS-DPCCH, HS-DSCH parameters (PIIFIL) Fixed HS-SCCH code Enabling/disabling HSDPA support in the cell (WCEL parameter) Parameter needs for RNC & transport resources
Min (RAB maximum, operator parameter (WCEL max 2M))? UL DCH bit rate (64 or 384) SRB bit rate 3.4 Change of DMCU in HS-DSCH setup HSDPA, June 2004.
66
NOKIA 2004
COMPANY CONFIDENTIAL
PIIFIL parameters
Handovers
No mobility for HSPDA No SHO for HSDPA and associated DCH No macrodiversity for associated DCH or HSDPA return CH No Inter System HO No Hard HO for HSDPA No handover from DCH to HSDPA Rapid channel type switching from HSDPA to DCH 0/0 Normal HOs for non HSDPA RABs In case of HO is triggered the UE is moved from Cell_DCH to Cell_PCH state directly? Alternatively moving to DCH 0/0 could be applied, preferred The HSDPA usage is forbidden by MCC/BRM for x seconds for the UE
DCH will be allocated
67
NOKIA 2004
COMPANY CONFIDENTIAL
Security
Ciphering is supported for non HSDPA services Ciphering is supported for HSPDA services
If it was found problems while testing, the ciphering will be deactivated
68
NOKIA 2004
COMPANY CONFIDENTIAL
Interoperabilty
Enhanced load and service based HO will be done if high pressure from customers
HSDPA Ues differentiated and treated specificly Also non HSDPA Ues can be directed to wanted cell Requires 2 layers (frequencies)
69
NOKIA 2004
COMPANY CONFIDENTIAL