Professional Documents
Culture Documents
Channel Elements Usage
Channel Elements Usage
Figure 55: Channel Elements usage service mix, Downlink target 256
Figure 56: Channel Elements usage service mix, Uplink target 64 In both graphs, we see that the target thresholds (256 CE in Downlink and 64 CE in UL) were reached within the interpolation range. Therefore, only the best fit for both cases (using the mean values as a data set) are presented in the next table.
144
Downlink Channel Elements (target 256) Quadratic Fit: y=a+bx+cx^2 Coefficient Data: a= b= c= Value at Y=256 ODV per cell per hour ODV per cell per second ODV Kbps/cell Uplink Channel Elements (target 256) Exponential Fit: y=ae^(bx) Coefficient Data: a= b= Value at Y=64 ODV per cell per hour ODV per cell per second ODV Kbps/cell 12.8075 0.0002 6518.6300 1143.619298 0.317672027 317.6720 Mbps/hour/Km^2 Mbit/hour/cell Mbit/sec/cell Kbps/cell 18.3079 5.11E-03 7.27E-07 14899.40 2613.929825 0.7260 726.0916 Mbps/hour/Km^2 Mbit/hour/cell Mbit/sec/cell Kbps/cell
Table 48: Channel Elements usage, service mix, uplink and downlink channel elements target: 256, 64 So far we can appreciate that the Downlink Channel Element threshold is reached after the Blocking and Dropping Target, but the UL channel Element threshold is reached before the Dropping Target. However, we must continue with the analysis to see which the order of occurrence of each target is.
145
Iub traffic [DL] 2000.0000 1800.0000 1600.0000 1400.0000 1200.0000 1000.0000 800.0000 600.0000 400.0000 200.0000 0.0000 2617.6919 4320.2870 7195.8725 9881.1036
Kbps
Figure 57: Iub utilization, Traffic Mix, Target = 1.07 Mbps For this analysis, only a data set with 4 points was considered as the corresponding simulation with the highest traffic density level presented errors in the results. However, the Iub target is reached within the 4 selected points. The result of the analysis with the best fit is presented in the next table.
Linear Fit: y=a+bx Coefficient Data: a= b= Value at Y=1070 ODV per cell per hour ODV per cell per second ODV Kbps/cell -132.5321 0.1951 6164.99 1081.577193 0.300438109 300.4381 Mbit/hour/Km^2 Mbit/hour/cell Mbit/sec/cell Kbps/cell
Table 49: Downlink Iub utilization, service mix, Downlink target 1070 Kbps Therefore, Iub downlink utilization, so far, is the second factor after the blocking target that is reached first.
146
UL Load [%] 100.0000% 90.0000% 80.0000% 70.0000% 60.0000% 50.0000% 40.0000% 30.0000% 20.0000% 10.0000% 0.0000% 2617.6919 4320.2870 7195.8725 9881.1036 11776.6783
UL Load [%]
UL Load threshold = 0.60 = 60% Quadratic Fit: y=a+bx+cx^2 Coefficient Data: a= b= c= Value at Y=0.6 ODV per cell per hour ODV per cell per second ODV Kbps/cell -0.1363 8.39E-05 8.16E-10 8135.76 1427.3263 0.39647 396.4795 Mbit/hour/Km^2 Mbit/hour/cell Mbit/sec/cell Kbps/cell
Table 50: Uplink load, service mix, target 60% According to the graph we clearly see that the threshold level for soft congestion triggering (60% Uplink load) is reached within the interpolation range, therefore only the best fit is provided. Taking a look at the results, we see that so far Uplink load is, after Dropping probability, the least frequent reached KPI threshold.
147
DL_TxPower [dBm] 43.0000 42.0000 41.0000 40.0000 39.0000 38.0000 37.0000 36.0000 35.0000 34.0000 2617.6919 4320.2870 7195.8725 9881.1036 11776.6783
Power [dBm]
DL_TxPower [dBm]
Quadratic Fit: y=a+bx+cx^2 Coefficient Data: a= b= c= Value when Y=38.7 ODV per cell per hour ODV per cell per second ODV Kbps/cell 3.68 -1.97E-05 3.75E-08 7360.59 1291.331579 0.3587 358.7032 Mbit/hour/Km^2 Mbit/hour/cell Mbit/sec/cell Kbps/cell
Table 51: Downlink power usage, service mix, target 38.7 dBm According to the Figure 60, again the target threshold level (38.7 dBm) is reached within the interpolation range, therefore only the best fit is presented. The Downlink transmitted power, which was the main limiting factor especially for Data Services in the single-service simulations, now it is still important but in the place after Downlink Channel Elements utilization according to the simulation results.
148
DL_Code tree usage[%] Code tree usage [%] 0.6000 0.5000 0.4000 0.3000 0.2000 0.1000 0.0000 2617.6919
Quadratic Fit: y=a+bx+cx^2 Coefficient Data: a= b= c= Value when y = 0.6 ODV per cell per hour ODV per cell per second ODV Kbps/cell 0.009300566 4.19E-05 8.67E-10 11406.08 2001.066667 0.555851852 555.851852 Mbit/hour/Km^2 Mbit/hour/cell Mbit/sec/cell Kbps/cell
Target Level to trigger soft congestion mechanism = 60% (0.6 in linear scale)
Table 52: Downlink code tree usage, service mix, target 0.6 (60%) In this experiment, the last simulation presented some errors so the value corresponding to the highest load had to be discarded and an extrapolation is provided based on the interpolation of the first four points of the data set. According to the best fit, the Downlink code tree usage would be, with the assumed traffic densities, the less important capacity limiting factor. Next table shows the order of capacity factors according to the number of supported users, i.e. according to the Figure ODV
4320.2870
7195.8725
9881.1036
11776.6783
149
Kbps/cell. This order would be the order of occurrence of the factors in the simulated scenario, ordered for lowest ODV Figure (the one that reaches first the target level) to highest ODV.
KPI Blocking probability Iub utilization Downlink Power usage Uplink load Dropping probability Code Tree usage
Table 53: Summary Table, capacity limiting factors The first result is not surprising, as there are many sources that causes blocking, not only to new calls but also is possible to have some blocking level for hand-over calls, although the priority to block calls is given to the non-guaranteed, non-handover calls according to Ericsson RRM algorithms. The most frequent blocking reasons that were found are as follows: DL transmit power limit exceeded (cell) DL Code usage limit exceeded 21: DL congestion DL ASE usage limit exceeded
Iub Downlink utilization is another expected result, as it was assumed just 1 E1 of capacity between Node B and RNC, from which there is just 1070 Kbps available, which means that few users working at their maximum data transfer rate would be able to block the complete cell. Given the presence of Data Services and given that in the conversion of units the service that presents major contribution in the calculated ODV is the web service, the Downlink Load, more than the Uplink, is expected to be one of the most important capacity limitations. In fact, no call blocked or dropped due to the Uplink load was registered in the simulation output. About dropping probability, it was expected to be one of the last factors to happen, mostly because the Ericsson RRM algorithms specify the dropping of a call as the last action to take to resolve congestion situations, before dropping can happen, a series of corrective measurements that involves Down switching of the non guaranteed connections have to be tried in the system with the aim of freeing radio resources.
150
The surprise was to see the Downlink Code Usage as one of the last factors. However in this case we must remember that the last part presented an error so the extrapolation performed may not be accurate. Simulations with higher loads than the assumed ones are proposed in order to verify the number for Downlink Code usage.
Kbps
DL Throughput
Kbps
DL Throughput
151
Kbps
DL Throughput
Kbps
250.0000 200.0000 150.0000 100.0000 50.0000 0.0000 2617.6919 4320.2870 7195.8725 9881.1036 11776.6783 DL Throughput
Some conclusions can be drawn by taking a look at the Figures 61 to 64: The critical value of 100 Kbps is always reached for any of the data services, between 9881 and 11776 Mbit/hour/Km^2 The performance, in terms of throughput of the indoor and outdoor users of the respective users is almost equivalent; this shows then that the 18 additional dBs for the indoor users has more impact on coverage rather than on capacity.
152
Surprisingly, the performance of the FTP service was lower than the performance (in Kbps) of the Web service for the given scenario. This is something that needs to be verified with more simulations in a further study.
The expected behavior, as it was also mentioned in [Haverkampcpichstudy] is that the unbalance in the power levels caused by the different downlink losses (and therefore different CPICH levels per each cell) creates zones where the mobile is forced to transmit with its highest power even though it is close in distance to a cell where theoretically it could be connected to, and because of this at some point in time the power of the mobile is not sufficient and the call is dropped. Additionally, as it is mentioned in [Ericssonhandover], unbalance in the CPICH powers causes also bigger zones with Pilot Pollution problems, i.e. zones where there are many potentially dominant CPICH levels that causes problems for the receiver to determine which one is the best one and probably cause ping-ponging effects changing back and forth of best CPICH (high Handover signaling). Then, preferably only one dominant CPICH per area should exist. Pilot pollution gives a high average number of active radio links, which decrease the traffic capacity and reduce the probability that the UE get all neighboring cells included due to the size limited monitored set [Ericssonhandover].
153
pgina anterior
A.F. COSME. UMTS CAPACITY SIMULATION STUDY
siguiente pgina