Method and apparatus for packet scheduling

0001The present invention relates to packet scheduling methods and apparatus for use, for example, in wireless communication systems.

0002Fig. 1 shows parts of a wireless communication system 1. The system includes a plurality of base stations 2, only one of which is shown in Fig. 1. The base station 2 serves a cell in which a plurality of individual users may be located. Each user has an individual user equipment (UE). Only the user equipments UE2, UE11 and UE50 are shown in Fig. 1. Each-UE is, for example, a portable terminal (handset) or portable computer.

0003As is well known, in a code-division multiple access (CDMA) system the signals transmitted to different UEs from the base station (also known as "node B") are distinguished by using different channelisation codes. In so-called third generation wireless communication systems a high speed downlink packet access (HSDPA) technique has been proposed for transmitting data in the downlink direction (from the base station to the UEs). In this technique a plurality of channels are available for transmitting the data. These channels have different channelisation codes. For example, there may be ten different channels C1 to C10 available for HSDPA in a given cell or sector of a cell. In HSDPA, downlink transmissions are divided up into a series of transmission time intervals (TTI), and a packet of data is transmitted on each different available channel to a selected UE. A new choice of which UE is served by which channel can be made in each TTI.

0004Fig. 2 shows an example of the operation of the HSDPA technique over a series of transmission time intervals TTI1 to TTI9. As shown in Fig. 2, in TTI1 it is determined that two packets will be sent to UE50, four packets will be sent to UE11 and four packets will be sent to UE2. Accordingly, two channels are allocated to UE50 and four channels each are allocated to UE11 and UE2. Thus, as shown in Fig. 1, UE50 is allocated channels C1 and C2, UE11 is allocated channels C3 to C6, and UE2 is allocated channels C7 to C10.

0005In the next transmission time interval TTI2 a new user equipment UE1 is sent one packet, and the remaining UEs specified in TTI1 continue to receive packets.

0006Thus, effectively the HSDPA system employs a number of parallel shared channels to transmit data in packet form from the base station to the different UEs. This system is expected to be used, for example, to support world wide web (WWW) browsing.

0007In order to decide which UE should be served on which channel in each TTI a packet scheduling technique is employed. Conventionally, two basic types of scheduling technique have been considered for use in HSDPA: a round-robin (RR) scheduling technique and a maximum carrier-to-interference ratio (max C/I) technique.

0008The basic round-robin technique first compiles a list of the UEs which currently have data waiting at the transmitter (base station) for transmission. For each TTI the last UE in the list will have the highest priority for the next TTI. Accordingly, the UEs are serviced in a round robin fashion. In the simplest round-robin scheduling technique, it is assumed that the UE with the highest priority takes all of the channels. However, a packet-weighted round-robin technique is also known. This allocates the available channels to a group of users in each TTI based on the relative amounts of data for the different UEs. In this packet-weighted technique UEs which have more data waiting for transmission are allocated more channels.

0009The round-robin scheduling techniques emphasise fairness amongst the competing UEs in terms of radio resource allocation. However, they tend to provide relatively poor total throughput of data.

0010The max C/I scheduling technique is similar to the round-robin scheduling technique except that the list of UEs having waiting data is sorted in each TTI based on a carrier-to-interference ratio (C/I) reported by each UE. The C/I is a measure of the quality of the channel. By sorting the list of UEs based on C/I, UEs which have a better channel quality are given a higher chance to be selected. In the simplest version of the technique, all of the channels are allocated to the UE with waiting data that has the highest C/I. A packet-weighted variant is also possible, in which instead of selecting a single UE having the highest C/I, a group of UEs with the highest C/I values is selected, and the available channels are divided up amongst the group of UEs based on the relative amounts of data which those UEs have waiting for transmission.

0011The max C/I scheduling technique tends to maximise the total throughput of data but this is at the expense of fairness. It can be seen that UEs which report poor C/I values, for example because they are far from the base station or because there are many other interfering UEs in the vicinity, will only very rarely be selected. Thus, these UEs are likely to suffer from unacceptably long delays in receiving packets.

0012Another scheduling technique is disclosed in "A proposal of all-IP mobile wireless network architecture - QoS packet scheduler for base stations", Masahiro Ono et al, NEC Corporation, Technical Report of IEICE, MoMuC2002-3 (2002-05), pp.13-18. This packet scheduling technique aims to meet quality of service (QoS) requirements of different UEs and to maximise the system capacity by adaptively allocating time-slots according to the wireless link quality and the required QoS levels. The technique employs a hierarchy of different individual schedulers including a max C/I scheduler, a proportional fairness (PF) scheduler, a weighted round robin (WRR) scheduler and a priority round robin (PRR) scheduler. Packets to be scheduled are pre-classified by a classifier according to the different QoS requirements of the different UEs. Packets belonging to different classes are then applied to different schedulers in the first level of schedulers in the hierarchy. Further scheduling is carried out in second and third levels of the hierarchy. In this way, multiple individual schedulers are used to cater for the different requirements of different classes of services. However, partitioning the scheduling process in a fixed way or slow-changing dynamic way proves difficult and inefficient because of the fast-changing dynamics of the radio channels. The result may be that the scheduler assigned to one partition (class of service) will be under a high pressure to provide the required QoS level, but the scheduler assigned to another partition (class of service) is underutilised and has spare capacity. It is also found that the efficiency and performance of such partitioned schedulers degrade considerably as the amount of the shared bandwidth and the range of services having differing requirements increase. Attempts to recover some of the lost efficiency in such partitioned schedulers in practice result only in increased computational complexity and attendant costs.

0013In United Kingdom patent application no. 0303859.3, from which the present application claims priority, the present inventor has proposed a packet scheduling method for scheduling packets of data for transmission from a transmitter via at least one channel to a plurality of receivers, for example in an HSDPA system of a wireless communications network. Weightings are assigned to at least two different aspects of scheduling performance, for example quality of service, delay and fairness. For each individual receiver at least one combined measure of the scheduling performance in the different aspects is produced according to the assigned weightings. The respective combined measures for different receivers are employed to decide the receiver(s) to which packets are to be transmitted. PCT application no. PCT/GB2004/000649 , filed on the same date as the present application, corresponds to GB 0303859.3. Copies of these applications have been filed with the present application.

0014This packet scheduling method enables scheduling of data to be carried out for all the receivers as a single group, without having to classify the receivers into different scheduling classes such as different service types. The method also enables the scheduling to take account of several different performance aspects without significant computational complexity.

0015In this method, the weights are assigned values taking account of the expected traffic scenario. For example, various simulations were carried out, each relating to a simulated traffic environment in which there are 40 UEs in total. 10 of these UEs were assumed to be attempting to receive real-time video and the remaining 30 UEs were assumed to be attempting WWW browsing sessions. In one simulation, the total aggregate traffic load was assumed to be approximately constant over a series of 5,000 TTIs (ten second period). In another simulation, the WWW users were assumed to become active in a staggered manner, giving rise to a variable input load on the scheduler. In a third simulation, it was assumed that a slowing mechanism was provided by the HSDPA system for WWW browsing. Such a slowing mechanism prevents the downloading of a new session unless a previous session has been successfully downloaded completely.

0016It was found from these simulations that the weightings which must be applied to the different aspects of scheduling performance need to be significantly different for the different traffic scenarios. In view of this, it was envisaged that the weightings could be adjustable by an operator of the scheduler so that when the expected traffic scenario changes the weights can be changed as well. It was also envisaged in United Kingdom patent application no. 0303859.3 that the weights could be adjusted automatically during operation of the apparatus.

0017In S. Abedi, S. Vadgama, "Hybrid Genetic Packet Scheduling and radio Resource Management for High Speed Downlink Packet Access", WPMC 2002 Conference, Hawaii, pp. 1192-1196 the present inventor has also proposed a packet scheduling technique employing a genetic algorithm. In this technique, a plurality of candidate scheduling solutions are generated for each TTI. Each candidate solution corresponds to an individual in the genetic algorithm and specifies which receivers are to be allocated which channels in the TTI concerned. The fitness of each candidate scheduling solution is determined. The fitness may take into account several different measures of performance of the scheduling solution concerned, for example throughput, delay and fairness. The individual performance measures may be weighted when determining the fitness for each candidate solution. Individuals in the current generation are selected as parents based on the fitness values of the corresponding candidate solutions. Fitter solutions have a higher chance of being selected as parents. Children (candidate solutions for the next generation) are produced by the selected parents in accordance with genetic operators such as crossover and mutation. In this way, over a series of iterations (generations) the genetic algorithm refines the candidate scheduling solutions until, at some point, a single best solution is selected for the TTI under consideration.

0018Such a genetic algorithm offers the potential for achieving much better scheduling performance than conventional techniques such as round robin scheduling and max C/I scheduling.

0019Another packet scheduling method has been proposed by the present inventor in S. Abedi, S. Vadgama, "A Radio Aware Random Iterative Scheduling Technique for High Speed Downlink Packet Access", VTC 2002, Fall, vol. 4, pp. 2322 - 2326, 24-28, Sept. 2002. This method also generates a plurality of candidate scheduling solutions for each TTI. At least one of the candidate solutions is generated randomly. The fitness of each candidate solution may be determined in the same way as for the proposed scheduling method based on a genetic algorithm, as described above.

0020The success of such packet scheduling methods is also heavily dependent on the choice of appropriate weights for weighting the individual performance measures when determining the fitness for each candidate solution. In particular, different weights are required to deal with different traffic scenarios.

0021The same problem of assigning proper weights under different conditions also arises in other types of packet schedulers conceived for use in wireless networks. For example, a so-called proportionally fair (PF) scheduler is described in R. Agrawal, et. al. "Class and Channel Condition Based Scheduler for EDGE/GPRS", Proc. of SPIE, vol.#4531, Aug 2001, and A. Jalali, R. Padovani, R. Pankaj; "Data throughput of CDMA-HDR a high efficiency-high data rate personal communication wireless system", VTC 2000, Spring, vol. 3, pp. 1854-1858, May 2000. The PF scheduler also requires the assignment of proper weights under different traffic load and channel conditions.

0022The dynamic mobile cellular environment makes the setting of appropriate weights a challenging task. Firstly, there may be enormous variation between channel conditions. Figure 3(A) is a graph illustrating schematically how the reported C/I values for four different UEs vary over a series of N TTIs under first channel conditions. In this case, the C/I values are relatively stable but there is a consistent difference in C/I values from one UE to the next. Some UEs have relatively poor channel conditions over the entire series of N TTIs, and others have relatively good channel conditions over the entire series. Under these channel conditions, many of the scheduling methods outlined above will tend to have difficulty in achieving fairness as between the different UEs. Other aspects of the scheduling performance, such as overall throughput, are not likely to be a problem.

0023Figure 3(B) illustrates the variation of C/I values for four different UEs under second channel conditions different from the first channel conditions the subject of Figure 3(A). In this case, the variation in C/I values of each individual UE is much greater than in Figure 3(A) and at different times over the series of N TTIs the different UEs each have good channel conditions. In this situation, it is not a challenge to achieve fairness. Instead, it may be difficult to achieve a high overall throughput or some other desired aspect of scheduling performance.

0024As well as dealing with variable channel conditions of the kind described with reference to Figures 3(A) and 3(B), an effective packet scheduling method must also cope with input traffic load dynamics (variable input pipes) and UEs whose profiles change rapidly as they move and change to using difference services. In particular, a UE may move rapidly from one cell to another. In this case, the packet data which has already been buffered in the existing Node B must be transferred to the new Node B. If there are many such transfers, there may be frequent step-function-like changes in the total load to be handled by a packet scheduler at a given Node B. In some cases, as described later in the present specification, this load variation has been found empirically to lead to a so-called "run-away" phenomenon and instability of the packet scheduler when the weights are fixed. The empirical studies described later have also shown that radical input pipe variations may lead to a significant drop in performance for one or more of the desired aspects of scheduling performance.

0025The drop in performance may affect only one class of service, for example, real-time services, whilst not affecting another class of service such as non-conversational services. Some schedulers, such as the PF scheduler, purport to address this problem by partitioning the scheduling according to the type of service, and assigning different fixed weights to the different partitions. However, in practice this may prove inefficient since the numbers of UEs using each type of service may change, with the result that the fixed weights are unable to provide a good QoS for the service concerned. For example, if the weights assigned to the different services are fixed and the number of high-bit-rate non-real-time users downloading WWW sessions increases significantly, the Node B would be under huge pressure to provide an acceptable QoS for the real-time video conversational sessions.

0026It is therefore desirable to provide a packet scheduling method which enables the weights applied to different measures of scheduling performance to be adjusted automatically so as to enable the scheduler to work efficiently under a variety of different traffic scenarios.

0027According to a first aspect of the present invention there is provided a packet scheduling method, for scheduling packets of data from transmission from a transmitter via at least one channel to a plurality of receivers, which method comprises producing first measures of scheduling performance in at least two different aspects and employing a weighted combination of the first measures to decide the receiver(s) to which packets are to be transmitted, said weighted combination being produced by combining the first measures according to respective corresponding weights assigned to the different aspects; producing at least one second measure of scheduling performance; for the or each said second measure, classifying the weights into at least two different classes of weights according to a probably influence the weight is expected to have on the second measure concerned; and employing the or each said second measure, together with the classification of the weights for the or each second measure, to adapt said weights.

0028In such a method, such a weighted combination of the first measures may be produced per individual receiver (as in the method of GB 0303859.3), so that for example the respective weighted combinations for the different receivers can then be compared with one another to decide the receiver(s) to which packets are to be transmitted. Alternatively, such a weighted combination of the first measures may be produced per candidate scheduling solution, as in the methods described in S. Abedi, S. Vadgama, "Hybrid Genetic Packet Scheduling and radio Resource Management for High Speed Downlink Packet Access", WPMC 2002 Conference, Hawaii, pp. 1192-1196 and S. Abedi, S. Vadgama, "A Radio Aware Random Iterative Scheduling Technique for High Speed Downlink Packet Access", VTC 2002, Fall, vol. 4, pp. 2322 - 2326, 24-28, Sept. 2002. In these cases, the respective weighted combinations produced for the different candidate scheduling solutions may be compared to select a best candidate scheduling solution or (in the case of a genetic algorithm) to select candidate scheduling solutions to evolve to a next generation.

0029Preferably, at least one said first measure is independent of at least one said aspect which influences another one of said first measures. This enables the measures to be independent of one another, enabling accurate control of the scheduling performance to be achieved by controlling the weightings.

0030At least one said first measure may be influenced by a priority assigned to a type of service (e.g. WWW browsing, video) provided to a receiver.

0031Preferably, at least one said first measure is adjusted to reduce a mismatch between it and another one of said first measures. The measures may be adjusted such that all of them are in the same range, e.g. 0 to 1, so that equal weightings have equal effect on the different measures.

0032One or more of said first measures may be normalised, for example the value for any one receiver may be normalised relative to the sum of the values for all the receivers.

0033In a preferred embodiment, the or each said weighted combination is produced by forming a product of said first measures for the receiver concerned.

0034There may be a plurality of channels available for transmitting data to the receivers, as in an HSDPA system. In this case, one method embodying the invention further comprises: producing respective first and second such weighted combinations for each said individual receiver; ranking the receivers based on their respective first weighted combinations and forming a list of the receivers in the order in which they are ranked; and allocating channels to the receivers in the list, based on their respective second weighted combinations, starting from the highest-ranked receiver in the list.

0035In this embodiment the decision on the receivers to which packets are to transmitted is influenced by both the first and second weighted combinations, which gives greater flexibility over the scheduling decision.

0036There are many different aspects of scheduling performance which it may be desirable to consider. These may include: success or failure in delivering data to the receiver within a tolerable delay threshold; a quality of a channel between the transmitter and the receiver; how much data is estimated to be deliverable successfully to the receiver; how much data is waiting at the transmitter for transmission to the receiver; delay in delivering data to the receiver; and fairness as between different receivers. The aspects do not have to be operational ones. For example, a purely commercial aspect could be considered such as profitability for the operator in providing a service to the receiver.

0037The method is preferably carried out iteratively for a series of scheduling instants, for example TTIs. In one embodiment, for each said scheduling instant, new weighted combinations are produced for the receivers and a new decision is made on the receiver(s) to which packets are to be transmitted.

0038The transmission may be a wireless transmission, the transmitter may be part of a base station of a wireless communication system, and each receiver may be part of a user equipment of that system.

0039According to a second aspect of the present invention there is provided packet scheduling apparatus, for scheduling packets of data for transmission from a transmitter to a plurality of receivers via at least one channel, which apparatus comprises: means for producing first measures of scheduling performance in at least two different aspects and for employing a weighted combination of the first measures to decide the receiver(s) to which packets are to be transmitted, said weighted combination being produced by combining the first measures according to respective corresponding weights; means for producing at least one second measure of scheduling performance; means for classifying the weights for the or each second measure into at least two different classes of weights according to a probable influence the weight is expected to have on the second measure concerned; and means for employing the or each second measure, together with the classification of the weights for the or each second measure, to adapt the weights.

0040According to a third aspect of the present invention there is provided a transmitter comprising: packet scheduling apparatus embodying the aforesaid second aspect of the invention; and transmitting means connected operatively to said packet scheduling apparatus and operable to cause packets to be transmitted to the receiver(s) decided by the packet scheduling apparatus.

0041Reference will now be made, by way of example, to the accompanying drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li>Figure 1, discussed hereinbefore, shows parts of a wireless communication system employing a HSDPA technique for downlink transmissions;</li><li>Figure 2 shows an example of the operation of the HSDPA technique in the Figure 1 system;</li><li>Figures 3(A) and 3(B) are graphs for illustrating a variation of C/I values of four UEs under first and second different channel conditions;</li><li>Figure 4 shows a block diagram of packet scheduling apparatus embodying the present invention;</li><li>Figure 5 is a flowchart illustrating operation of a preferred embodiment of the present invention;</li><li>Figure 6 is a diagram showing example of a channel allocation process carried out in the Figure 5 embodiment;</li><li>Figure 7 is a schematic diagram for use in explaining a mixed-service traffic scenario in an HSDPA system;</li><li>Figure 8 is a schematic view for use in explaining a cellular environment in an HSDPA system;</li><li>Figure 9 is a diagram illustrating packet transmission activity in an HSDPA system in a first simulation example;</li><li>Figure 10 is a graph illustrating performance of a conventional FIFO weighted max C/I scheduler over a series of transmission time intervals in the first simulation example;</li><li>Figure 11 is a graph corresponding to Figure 10 but showing the performance over an initial period shown in Figure 10 in more detail;</li><li>Figure 12 is a graph illustrating performance of a scheduler described in GB 0303859.3 having roughly-assigned fixed weights over a series of TTIs in the first simulation example;</li><li>Figure 13 is a graph corresponding to Figure 12 but showing performance over an initial period in Figure 12 in more detail;</li><li>Figure 14 is a graph illustrating performance of packet scheduling apparatus according to one embodiment of the present invention over a series of TTIs in the first simulation example;</li><li>Figure 15 is a graph illustrating the performance of packet scheduling apparatus according to another embodiment of the present invention over a series of TTIs in the first simulation example;</li><li>Figure 16 is a graph illustrating variation of a variance of throughputs to different UEs over a series of TTIs in the first simulation example for packet scheduling apparatus embodying the present invention and other schedulers;</li><li>Figure 17 is a graph illustrating a variation of QoS of UEs receiving real-time video services over an initial period of TTIs in the first simulation example for packet scheduling apparatus embodying the present invention and for other schedulers;</li><li>Figures 18 (A) to 18(F) are graphs for comparing different aspects of performance of packet scheduling apparatus embodying the present invention with other schedulers over a series of TTIs in the first simulation example;</li><li>Figures 19(A), 19(B) and 19(C) show graphs illustrating a cumulative density function (CDF) of throughputs of all UEs over time in the first simulation example for packet scheduling apparatus embodying the present invention and for other schedulers;</li><li>Figures 20(A) to 20(F) are graphs corresponding respectively to those of Figures 18(A) to 18(F) but relating to a second simulation example;</li><li>Figure 21 is a diagram illustrating packet transmission activity in an HSDPA system in a third simulation example;</li><li>Figures 22(A) to 22(F) are graphs corresponding respectively to those of Figures 18(A) to 18(F) but relating to the third simulation example;</li></ul>

0042Figure 4 shows a block diagram of packet scheduling apparatus 10 embodying the present invention. The apparatus 10 is used to schedule packets of data for transmission from a transmitter to a plurality of receivers via at least one channel. A scheduling decision is made for each successive scheduling instant (eg each TTI). The transmitter is, for example, a base station (Node B) in a wireless communication system. The plurality of receivers in this case are different UEs served by the base station.

0043The apparatus 10 comprises a first measures producing unit 12 which receives data relating to performance of the scheduling apparatus. The data may include, for example, carrier-to-interference ratio (C/I) reports and information regarding the fill levels of source queues in which the data destined for different receivers is buffered in the transmitter prior to transmission.

0044Based on the received data, the first measures producing unit 12 produces a set of first measures of scheduling performance. The first measures relate to at least two different aspects of the scheduling performance. For example, as described later in more detail, one of the first measures may relate to throughput, while another of the first measures may relate to delay. Depending on the type of scheduling algorithm used in the apparatus (for which see below), a set of the first measures may be produced per receiver (UE) or per candidate scheduling solution.

0045The apparatus 10 further comprises a decision unit 16 which receives the set of first measures produced by the first measures producing unit 12. The decision unit 16 also receives a set of weights from a weight adapting unit 20. There is an individually-corresponding weight for each one of the first measures. The decision unit 16 produces a weighted combination of the first measures by combining the first measures according to the respective corresponding weights.

0046The decision unit 16 employs the weighted combination of the first measures to decide the receiver(s) to which packets are to be transmitted in the scheduling instant under consideration. For example, when a set of first measures is produced per receiver (as in the case of GB 0303859.3), the decision unit 16 may produce a weighted combination of the first measures per receiver, and compare the respective weighted combinations for different receivers to decide the receivers to which packets are to be transmitted. Alternatively, when a set of first measures is produced per candidate scheduling solution (as in the case of the methods in the two papers by S. Abedi et. al. referenced in the introduction) the decision unit 16 may produce a weighted combination per candidate scheduling solution. This weighted combination may, for example, be a fitness function used for comparing the different candidate solutions. The weighted combinations of different candidate solutions are then employed by the scheduling algorithm to decide the receiver(s) to which packets are to be transmitted, for example by selecting a single best candidate scheduling solution or by selecting some of the candidate scheduling solutions for genetic evolution. The way in which the weighted combinations of first measures may be employed to decide the receivers to which packets are to be transmitted in the present invention is not limited to the examples described above.

0047The apparatus 10 further comprises the weight adapting unit 20 mentioned above, a second measures producing unit 24 and a weight classifying unit 28. The second measures producing unit receives some or all of the data relating to performance of the scheduling apparatus that is supplied to the first measures producing unit 12. Although not shown in Figure 4, the second measures producing unit 24 may also receive one or more of the first measures produced by the first measures producing unit 12. The second measures producing unit 24 produces at least one second measure of scheduling performance. The or each second measure relates to some aspect of overall scheduling performance, ie taking account of all the receivers collectively. For example, as described later in more detail, the second measures may relate to overall QoS, overall throughput, average throughput for different receivers, and fairness. -

0048For the or each second measure, the weight classifying unit 28 classifies the previously-mentioned weights supplied to the decision unit 16 into at least two different classes of weights according to a probable influence the weight concerned is expected to have on the second measure. For example, the weights may be classified into friendly, hostile and neutral classes. The friendly class may be made up of each weight, if any, whose probable influence on the second measure is expected to be positive. The hostile class may be made up of each weight, if any, whose probable influence on the second measure is expected to be negative. The neutral class may be made up of each weight, if any, whose influence on the second measure is uncertain (not expected to be definitely positive or definitely negative).

0049The weight adapting unit 20 receives the or each second measure from the second measures producing unit 24 and also receives the information relating to the classification of the weights from the weight classifying unit 28. The weight adapting unit 20 employs the or each second measure, together with the classification of the weights for the or each second measure, to adapt the weights. For example, each weight in the friendly class for a second measure may be increased if the second measure is decreasing or unchanged. Each weight in the hostile class for a second measure may be decreased if the second measure is decreasing or not changing. Each weight in the neutral class for a second measure may be maintained unchanged irrespective of the change in the second measure.

0050The apparatus 10 is connected operatively to a transmission unit 32 which, when a scheduling instant occurs for which the decision unit 16 has made a scheduling decision, causes packets to be transmitted to the chosen receiver(s).

0051Next, an embodiment of the present invention suitable for use in an HSDPA system will be described in detail. This embodiment seeks to optimise the performance of the HSDPA system in terms of measures such as quality of service (QoS), channel quality, deliverable data packets, data waiting at the transmitter, and delay profile.

0052In this embodiment, a set of five first measures of scheduling performance is produced for each UE. The first of these five measures of scheduling performance is a QoS measure. In order to produce this measure, a tolerable delay threshold <i>Tolerance_Delay</i> is defined for each kind of service made available in the HSDPA system. For example, for real-time video services this tolerable delay threshold is assumed to be 100ms. For worldwide web (WWW) browsing sessions, the tolerable delay threshold is assumed to be 1.5s. In general, an HSDPA system seeks to deliver the highest possible number of data packets from the transmitter (Node-B) to each UE within the defined tolerable delay threshold.

0053Assume that N is the total number of UEs to which packets are being transmitted during the current TTI. <i>Oct</i>_{<i>Received n</i>} is the number of octets which have been delivered successfully (error-free) to the nth UE. These error-free delivered octets can be divided into QoS-satisfied and QoS-failed octets. QoS-failed octets are the octets delivered outside the tolerable delay threshold. Therefore, for each UE, the number of QoS-satisfied received octets may be defined as <maths id="math0001" num="(1)"><math display="block"><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mrow><mi>Received_Satisfied_QoS</mi></mrow><mi>n</mi></msub></mrow></msub><mo>=</mo><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mrow><mi>Received</mi></mrow><mi>n</mi></msub></mrow></msub><mo>−</mo><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mrow><mi>Received_Failed_QoS</mi></mrow><mi>n</mi></msub></mrow></msub><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0001.tif" /></maths> where <i>Oct</i>_{<i>Received_S atisficd_O aS</i><sub2><i>n</i></sub2>} is the number of QoS-satisfied octets and <i>Oct</i>_{<i>Receive_F ailed QoS</i><sub2><i>n</i></sub2>}&lt;J is the number of received QoS-failed octets for <i>n</i> th UE.

0054Incidentally, it is possible for the Node-B to find out the delivery delays of the packets it transmits to each UE based on acknowledge messages ACK transmitted back to the Node-B by the UE after received. Further information concerning these acknowledge messages is provided, for example, in our co-pending United Kingdom patent application no. 0216245.1.

0055For each UE the proportion of throughput which satisfies the QoS requirement may be defined as <maths id="math0002" num="(2)"><math display="block"><mrow><msub><mrow><mi>Throughput_Satisfy_QoS</mi></mrow><mi>n</mi></msub><mo>=</mo><mfrac><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mrow><mi>Received_Satisfied_QoS</mi></mrow><mi>n</mi></msub></mrow></msub></mrow><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mrow><mi>Arrived_Node_B</mi></mrow><mi>n</mi></msub></mrow></msub></mrow></mfrac><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0002.tif" /></maths> where <i>Oct</i>_{<i>Arrived_Node_B</i><sub2><i>n</i></sub2>} is the number of octets originally delivered to a source queue for the <i>n</i>th UE at Node B.

0056In the case in which no packet has arrived at Node B for the <i>n</i>th UE, it is assumed that <i>Throughput_Satisfy_Q oS</i>_<i>n</i><i>=</i> 0 for that U E .

0057This value then becomes subject to a nonlinear transform so that <maths id="math0003" num="(3)"><math display="block"><mrow><msub><mrow><mi>Ratio_Satisfy_QoS</mi></mrow><mi>n</mi></msub><mo>=</mo><mrow><mn>1</mn><mo>/</mo><mrow><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mrow><mi>Throughput_Satisfy_QoS</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow></mrow></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0003.tif" /></maths>

0058The QoS measure for each UE then is defined as <maths id="math0004" num="(4)"><math display="block"><mrow><msub><mrow><mi>Metric_QoS</mi></mrow><mi>n</mi></msub><mo>=</mo><mrow><mrow><msub><mrow><mi>Ratio_Satisfy_QoS</mi></mrow><mi>n</mi></msub></mrow><mo>/</mo><mrow><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mi>N</mi></munderover><mrow><msub><mrow><mi>Ratio_Satisfy_QoS</mi></mrow><mi>i</mi></msub></mrow></mstyle></mrow></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0004.tif" /></maths>

0059This normalisation is applied to the final measure in order to map the values of the QoS measures to a range between 0 and 1.

0060The second of the five first measures in this embodiment is based on the reports of C/I values received from the UEs. In order to map the C/I measure for each UE to a range between 0 and 1 each reported C/I value is scaled relative to the sum of all of the reported C/I values: <maths id="math0005" num="(5)"><math display="block"><mrow><mrow><mrow><mi>Metric_C</mi></mrow><mo>/</mo><mrow><msub><mi>I</mi><mi>n</mi></msub></mrow></mrow><mo>=</mo><mrow><mi>C</mi><mo>/</mo><mrow><mrow><mrow><msub><mi>I</mi><mi>n</mi></msub></mrow><mo>/</mo><mrow><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mi>N</mi></munderover><mrow><mrow><mi>C</mi><mo>/</mo><mrow><msub><mi>I</mi><mi>i</mi></msub></mrow></mrow></mrow></mstyle></mrow></mrow></mrow></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0005.tif" /></maths> where <i>C</i>/<i>I</i>_<i>n</i> is the reported value of C/I for the nth UE.

0061The third of the five first measures in this embodiment relates to an estimated number of efficiently deliverable octets <i>Eff_Oct</i>_<i>n</i> for each UE. In this case, it is assumed that the HSDPA system employs an adaptive modulation and coding (AMC) technique to enable the transmitter (Node-B) to select different modulation and/or coding schemes under different channel conditions. In the AMC technique, each UE produces a measure of a downlink channel quality it is experiencing from the base station, and reports this measure to the Node-B. The measure is, for example, a C/I value for the downlink channel. The Node-B then employs the reported channel measures for each UE, as well as information relating to the system limitations and available modulation and coding scheme (MCS) levels, to identify the most efficient MCS level for the particular UE. Thus, UEs that have better channels or are located in the vicinity of the Node-B can employ higher MCS levels and therefore enjoy higher transmission rates. This selection can be carried out, for example, by imposing C/I value thresholds (eg -8dB,-2dB,+4dB) for moving to the next MCS level. Effectively, the result is a classification of the transmission rates based on the channel quality of each UE.

0062In the present embodiment, it is assumed that each UE reports a C/I value in every TTI and that Node-B is capable of setting a new MCS level for each available channel in every TTI.

0063Another factor which impacts the number of efficient deliverable octets for each UE is the way in which erroneously-received packets are dealt with. In the present embodiment, it is assumed that a so-called chase combining process is applied to such erroneously-received packets (failed packets). In the chase combining process a failed packet is resent by the Node-B and subsequently the UE "soft" combines (for example using maximal ratio combining) all received copies of the same packet. The effective carrier-to-interference ratio (C/I) is then the sum of the respective C/Is of the two packets being combined. Thus the chase combining process improves the C/I of the transmitted packets.

0064It is also assumed that all retransmissions have a higher priority than first transmissions. This means that all retransmission packets are given the opportunity to be transmitted before the first transmissions of new packets.

0065To estimate the number of efficiently deliverable octets for a UE, firstly the most efficient MCS level MCS_n for the UE_n is determined. Secondly, it is determined if the UE_n is in transmission mode (ready to receive a new packet for the first time) or in retransmission mode (waiting for the Node-B to retransmit a packet which was previously erroneously received by the UE).

0066If the UE is in retransmission mode then the number of octets available for transmission <i>Oct</i>_<i>n</i> is determined based on <maths id="math0006" num="(6)"><math display="block"><mrow><msub><mrow><mi>Oct</mi></mrow><mi>n</mi></msub><mo>=</mo><mi>min</mi><mrow><mo>(</mo><mrow><mi>Oct</mi><mrow><mo>(</mo><mrow><msub><mrow><mi>MCS</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow><mo>,</mo><msub><mrow><mi>Oct_Retransmit</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0006.tif" /></maths> where <i>Oct(MCS</i>_<i>n</i><i>)</i> is the maximum number of octets that the MCS level selected for the nth UE can deliver, and <i>Oct_Retran smit</i>_<i>n</i> is the number of octets available for retransmission (ie the number of octets waiting at Node-B to be retransmitted to the UE).

0067If the UE is in transmission mode the number of octets available for transmission is determined based on <maths id="math0007" num="(7)"><math display="block"><mrow><msub><mrow><mi>Oct</mi></mrow><mi>n</mi></msub><mo>=</mo><mi>min</mi><mrow><mo>(</mo><mrow><mi>Oct</mi><mrow><mo>(</mo><mrow><msub><mrow><mi>MCS</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow><mo>,</mo><msub><mrow><mi>Oct_Waiting_in_Queue</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0007.tif" /></maths> where <i>Oct_Waiting_in _Queue</i>_<i>n</i> represents the number of octets in a Node-B queue for transmission to the nth UE.

0068The maximum number of octets available for transmission by any one of the UEs then is determined based on <maths id="math0008" num="(8)"><math display="block"><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><mi>n</mi><mi mathvariant="normal">max</mi></mrow></msub><mo>=</mo><mi mathvariant="normal">max</mi><mrow><mo>(</mo><mrow><msub><mrow><mi>Oct</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0008.tif" /></maths> where <i>n</i>_<i>m</i>ax represents the number of the UE with maximum number of available octets for transmission (the "best UE") and <i>Oct</i>_<i>n</i>max is the maximum number of available octets for transmission to that best UE.

0069The efficient estimated deliverable octets for the best UE is then determined based on <maths id="math0009" num="(9)"><math display="block"><mrow><msub><mrow><mi>Eff_Oct</mi></mrow><mrow><msub><mi>n</mi><mrow><mi mathvariant="normal">max</mi></mrow></msub></mrow></msub><mo>=</mo><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mi>n</mi><mrow><mi mathvariant="normal">max</mi></mrow></msub></mrow></msub><mo>.</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>−</mo><msub><mrow><mi>FER</mi></mrow><mrow><msub><mi>n</mi><mrow><mi>max</mi></mrow></msub></mrow></msub></mrow><mo>)</mo></mrow></mrow></math><img file="EP1595369B1_D0009.tif" /></maths> where <i>FER</i>_<i>n</i>max is an estimated frame error rate for the <i>n</i>_max th UE.

0070The efficient number of deliverable octets for the nth UE is then normalised relative to this maximum value so that the third individual measure becomes <maths id="math0010" num="(10)"><math display="block"><mrow><msub><mrow><mi>Metric_Oct</mi></mrow><mi>n</mi></msub><mo>=</mo><mrow><mrow><msub><mrow><mi>Oct</mi></mrow><mi>n</mi></msub><mo>.</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>−</mo><msub><mrow><mi>FER</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>/</mo><mrow><msub><mrow><mi>Eff_Oct</mi></mrow><mrow><msub><mi>n</mi><mrow><mi mathvariant="normal">max</mi></mrow></msub></mrow></msub></mrow></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0010.tif" /></maths>

0071The fourth of the five first measures of performance in this embodiment is a measure of how much data is waiting at the Node-B for transmission to each UE. This is related inversely to throughput of data to each UE.

0072For the <i>n</i>th UE the throughput is defined as <maths id="math0011" num="(11)"><math display="block"><mrow><mi>T</mi><msub><mi>h</mi><mi>n</mi></msub><mo>=</mo><mfrac><mrow><msub><mrow><mrow><mo>(</mo><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><mi>Received</mi></mrow></msub></mrow><mo>)</mo></mrow></mrow><mi>n</mi></msub></mrow><mrow><msub><mrow><mrow><mo>(</mo><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><mi>Arrived_Node_B</mi></mrow></msub></mrow><mo>)</mo></mrow></mrow><mi>n</mi></msub></mrow></mfrac><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0011.tif" /></maths>

0073Then a ratio <i>Metric_Waiting_Ratio</i>_<i>n</i> of data waiting to be delivered is defined as <maths id="math0012" num="(12)"><math display="block"><mrow><msub><mrow><mi>Metric_Waiting_Ratio</mi></mrow><mi>n</mi></msub><mo>=</mo><mn>1</mn><mo>−</mo><mi>T</mi><msub><mi>h</mi><mi>n</mi></msub><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0012.tif" /></maths>

0074The last of the five first measures of performance in this embodiment relates to the delays being experienced by each UE. Firstly, the oldest undelivered octet waiting in the Node-B for transmission to the UE is considered, and the amount of delay to which that octet is subject is determined. <maths id="math0013" num="(13)"><math display="block"><mrow><msub><mrow><mi>Delay</mi></mrow><mi>n</mi></msub><mo>=</mo><mi>M</mi><mo>.</mo><mi>TTI</mi><mo>−</mo><msub><mrow><mi>Arrival_Time_Earliest</mi></mrow><mi>n</mi></msub><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0013.tif" /></maths> where <i>M.TTI</i> represents current time and <i>Arrival_Time_Earliest</i>_<i>n</i> represents the time of arrival at the Node-B source queue for the nth UE of the oldest undelivered octet.

0075Next, using the same tolerable delay thresholds established for different services as described above in relation to the first measure, the distance by which the worst delay experienced by the UE is from its tolerable delay threshold is calculated. <maths id="math0014" num="(14)"><math display="block"><mrow><msub><mrow><mi>Delay_Distance</mi></mrow><mi>n</mi></msub><mo>=</mo><msub><mrow><mi>Delay</mi></mrow><mi>n</mi></msub><mo>−</mo><msub><mrow><mi>Tolerance_Delay</mi></mrow><mi>n</mi></msub><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0014.tif" /></maths> where <i>Delay_Distance</i>_<i>n</i> is the distance from the threshold for the nth UE.

0076The delay distances of all the UEs then are mapped to positive values. To perform the positive mapping first the minimum distance is determined so that <maths id="math0015" num="(15)"><math display="block"><mrow><msub><mrow><mi>Delay_Distance</mi></mrow><mrow><mi>min</mi></mrow></msub><mo>=</mo><mi mathvariant="normal">min</mi><mrow><mo>(</mo><mrow><msub><mrow><mi>Delay_Distance</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0015.tif" /></maths>

0077The adjusted delay distance then is defined as <maths id="math0016" num="(16)"><math display="block"><mrow><msub><mrow><mi>Adjusted_Delay_Distance</mi></mrow><mi>n</mi></msub><mo>=</mo><msub><mrow><mi>Delay_Distance</mi></mrow><mi>n</mi></msub><mo>−</mo><msub><mrow><mi>Delay_Distance</mi></mrow><mrow><mi>min</mi></mrow></msub><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0016.tif" /></maths>

0078Then a nonlinear mapping is applied. The result is <maths id="math0017" num="(17)"><math display="block"><mrow><msub><mrow><mi>Mapped_Delay</mi></mrow><mi>n</mi></msub><mo>=</mo><mrow><mrow><msub><mi>β</mi><mi>n</mi></msub></mrow><mo>/</mo><mrow><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mrow><mi>Adjusted_Delay_Distance</mi></mrow><mi>n</mi></msub></mrow><mo>)</mo></mrow></mrow></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0017.tif" /></maths> where <i>Mapped_Delay</i>_<i>n</i> is the mapped delay value for the <i>n</i>th UE and β_<i>n</i> is a parameter which specifies the priority of the service being provided to the nth UE. Here, for example, a service is WWW browsing or real-time video. The higher <i>β</i>_<i>n</i>, the higher is the priority of the service.

0079The final measure relating to delay is determined as <maths id="math0018" num="(18)"><math display="block"><mrow><msub><mrow><mi>Metric_Delay</mi></mrow><mi>n</mi></msub><mo>=</mo><mrow><mrow><msub><mrow><mi>Mapped_Delay</mi></mrow><mi>n</mi></msub></mrow><mo>/</mo><mrow><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>n</mi><mo>=</mo><mn>1</mn></mrow><mi>N</mi></munderover><mrow><msub><mrow><mi>Mapped_Delay</mi></mrow><mi>n</mi></msub></mrow></mstyle></mrow></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>…</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0018.tif" /></maths> which guarantees that the measure <i>Metric_Delay</i>_<i>n</i> is mapped to a value between 0 and 1.

0080In this embodiment a first weighted combination of the first measures for each UE is calculated by forming a weighted product of the individual performance measures as follows <maths id="math0019" num="(19)"><math display="block"><mrow><msub><mrow><mi>Ranking_Metric</mi></mrow><mi>n</mi></msub><mo>=</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>W</mi><mn>1</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_QoS</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>W</mi><mn>2</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><mrow><mrow><mi>Metric_C</mi></mrow><mo>/</mo><mrow><msub><mi>I</mi><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>W</mi><mn>3</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_Oct</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>W</mi><mn>4</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_Waiting_Ratio</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>W</mi><mn>5</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><mi>γ</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_Delay</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></math><img file="EP1595369B1_D0019.tif" /></maths> where <i>w</i>_<i>k</i>(<i>m</i>) represents a first set of <i>k</i> weights (ranking weights) at the <i>m</i>th TTI and the index a denotes the nth UE, and <i>Metric</i>_<i>QoS</i>_<i>n</i>(<i>m</i>), <i>Metric_ClI</i>_<i>n</i><i>(m), Metric_Oct</i>_<i>n</i><i>(m), Metric_Waiting_Ratio</i>_<i>n</i>(<i>m</i>) and <i>Metric_Delay</i>_<i>n</i>(<i>m</i>) are the values of the five first measures defined in equations (1) to (18) above at the mth TTI.

0081γ(_<i>m,j</i>) is a variable delay tolerance related weight which is assigned to a group <i>j</i> of UEs with the same delay tolerance and which is used for fine tuning of priority of services. As described later in more detail, γ(_<i>m,j</i>) is adapted by the weight adapting unit 20 as well as the weights <i>W</i>_<i>k</i><i>(</i>_<i>m</i><i>).</i> The parameter β, which is included in <i>Metric_Delay</i>_<i>n</i><i>(m)</i> defined in equation (18), is a fixed value specifying the priority of the services. As noted above, for each group j of UEs with the same delay tolerance, the service weight β_<i>i</i> is assigned which is not subject to adaptation.

0082The value of <i>γ</i>(_<i>m,j</i>) which is used in equation (19) is chosen according to the group to which UE_n belongs. Thus, if UE27 belongs to group 2, the final term of equation (19) for calculating <i>Ranking_Metric</i>_<i>27</i> becomes (1+<i>W</i>_<i>5</i><i>(m).γ(m,2)·Metric_Delay</i>_<i>27</i><i>(m))</i>.

0083A second weighted combination of the first measures for each UE in this embodiment is calculated as follows: <maths id="math0020" num="(20)"><math display="block"><mrow><msub><mrow><mi>Channel_Allocation_Metric</mi></mrow><mi>n</mi></msub><mo>=</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>V</mi><mn>1</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_QoS</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>V</mi><mn>2</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><mrow><mrow><mi>Metric_C</mi></mrow><mo>/</mo><mrow><msub><mi>I</mi><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>V</mi><mn>3</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_Oct</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>V</mi><mn>4</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_Waiting_Ratio</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow><mo>⋅</mo><mrow><mo>(</mo><mrow><mn>1</mn><mo>+</mo><msub><mi>V</mi><mn>5</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><mi>γ</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>⋅</mo><msub><mrow><mi>Metric_Delay</mi></mrow><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></math><img file="EP1595369B1_D0020.tif" /></maths> where <i>V</i>_<i>k</i>(<i>m</i>) represents a second set of <i>k</i> weights (channel allocation units) at the <i>m</i>th TTI.

0084Figure 5 is a flowchart for explaining an example of the operation of the decision unit 16 in the Figure 4 apparatus in the present embodiment. The series of steps shown in Figure 5 is carried out for every scheduling instant (eg TTI) under consideration.

0085In a first step S1 the decision unit 16 calculates for each UE the first weighted combination of the first measures for the UE concerned (ranking metric) according to equation (19). The first measures are weighted using the current values of the first set of weights (ranking weights) <i>W</i>_<i>k</i>(<i>m</i>) when producing this first weighted combination.

0086In step S2 the decision unit 16 ranks the UEs based on their respective ranking metrics. The decision unit produces a list of the UEs by rank, with the highest-ranked UE at the top of the list. The list only includes UEs which have data waiting in a source queue at the transmitter for transmission to the UE concerned.

0087In step S3, the decision unit 16 calculates for each UE the second weighted combination of the first measures for the UE concerned (channel allocation metric) according to equation (20). The first measures are weighted using the second set of weights (channel allocation weights) <i>v</i>_<i>k</i><i>(m</i>) when producing the second weighted combination. The channel allocation weights may be different from the ranking weights.

0088In step S4 the decision unit 16 refers to the list of UEs produced in step S2. Starting from the top of the list, the decision unit 16 allocates channels to the UEs in the list based on their respective channel allocation metrics, as described in more detail with reference to Figure 6. The processing in step S4 continues until no channel remains for allocation.

0089This completes the processing for the current scheduling instant (TTI m). The processing is then repeated for the next scheduling instant (TTI m+i).

0090The channel allocation process in step 54 starts from the top of the list of ranked UEs, and allocates channels according to the relative values of the channel allocation measures produced in equation 20.

0091This process is illustrated schematically in Figure 6.

0092Suppose that the list of UEs contains five UEs in total, with UE 30 at the top of the list, followed by UEs 2, 9, 11 and 17. Also, assume that the channel allocation measure produced by equation 20 for these UEs are 1.5, 4.3, 1.2, 2.0 and 3.2 respectively.

0093In the first step, the sum of the channel allocation measures for all of the UEs yet to be allocated channels (ie all of the UEs in this case) is calculated to be 12.2. The highest-ranked UE yet to be allocated is UE 30. Its channel allocation measure of 1.5 is then "normalised" relative to the sum of all the channel allocation measures and becomes 0.12. It is assumed in this example that there are ten channels available in total. Accordingly, the normalised channel allocation measure for UE 30 is multiplied by 10 to yield 1.23. This is then rounded down using a "floor function" to produce the final result that UE 30 is allocated one channel. This leaves 9 channels remaining for allocation in subsequent steps. Incidentally, if the final result is less than 1 it is set to 1 in this embodiment so that the minimum channel allocation is 1 channel.

0094In the second step the sum of the channel allocation measures of the UEs remaining to be allocated (UEs 2, 9, 11 and 17) is recalculated as 10.7. The channel allocation measure 4.3 of the highest-ranked remaining UE (UE 2) is normalised relative to the new sum and becomes 0.40. This is multiplied by the number of remaining channels, ie 9, to produce the result of 3.62 channels, which is rounded down to 3 channels in the final allocation. This leaves 6 channels remaining for the next step. The procedure is followed again in the third step, with the result that UE 9 is allocated 1 channel, leaving 5 channels left over. In the fourth step, it is calculated that UE 11 should also be allocated 1 channel, leaving 4 channels remaining at this stage. Finally, in the fifth step UE 17 is a-llocated the remaining 4 channels, and the process ends.

0095It will be appreciated that other channel allocation processes are possible in embodiments of the invention.

0096In this embodiment, a set of four second measures of scheduling performance is produced. The first of these four second measures of scheduling performance is an overall QoS measure.

0097For each UE the proportion of throughput which satisfies the individual QoS requirement for the UE concerned was defined in equation (2) above. The second measure relating to overall QoS of the scheduling process is then defined as simply the average of the individual values of <i>Throughput_Satisfy_QoS</i> for the different UEs: <maths id="math0021" num="(21)"><math display="block"><mrow><mi>Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mfrac><mn>1</mn><mi>N</mi></mfrac><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mi>N</mi></munderover><mrow><msub><mrow><mi>Throughput_Satisfy_QoS</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow></mstyle></mrow></math><img file="EP1595369B1_D0021.tif" /></maths>

0098Here, as in equations (19) and (20) above, the term "(<i>m</i>)" simply denotes the value of the parameter in the mth TTI.

0099The second of the four second measures relates to the total throughput to all the UEs for the mth TTI. This total throughput measure is calculated as <maths id="math0022" num="(22)"><math display="block"><mrow><mi>Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mfrac><mrow><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mi>N</mi></munderover><mrow><mrow><mo>(</mo><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mrow><mi>Received</mi></mrow><mi>i</mi></msub></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></mstyle></mrow><mrow><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mi>N</mi></munderover><mrow><mrow><mo>(</mo><mrow><msub><mrow><mi>Oct</mi></mrow><mrow><msub><mrow><mi>Arrived_Node_B</mi></mrow><mi>i</mi></msub></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></mstyle></mrow></mfrac></mrow></math><img file="EP1595369B1_D0022.tif" /></maths> where <i>Oct</i>_{<i>Receivedi</i>}<i>(m)</i> is the total number of octets delivered to the <i>i</i>th UE in the mth TTI.

0100The third of the four second measures in this embodiment relates to an average of the throughputs to the different UEs in the mth TTI. This is simply the average of the individual throughputs calculated in equation (11) above: <maths id="math0023" num="(23)"><math display="block"><mrow><mi>Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mfrac><mn>1</mn><mi>N</mi></mfrac><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>n</mi><mo>=</mo><mn>1</mn></mrow><mi>N</mi></munderover><mrow><mi>T</mi><msub><mi>h</mi><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow></mstyle><mo>,</mo></mrow></math><img file="EP1595369B1_D0023.tif" /></maths>

0101The last of the four second measures relates to fairness. In this embodiment, fairness is considered to be related to the extent of variance of the throughputs to the individual UEs. Starting from equation (11) above, the vector of the individual throughputs is <maths id="math0024" num="(24)"><math display="block"><mrow><mover accent="true"><mrow><mi>T</mi><mi>h</mi></mrow><mo stretchy="true">‾</mo></mover><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mrow><mo>{</mo><mrow><mi>T</mi><msub><mi>h</mi><mi>n</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>}</mo></mrow><mo>,</mo><mi> </mi><mi>n</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mi>N</mi></mrow></math><img file="EP1595369B1_D0024.tif" /></maths>

0102Defining the variance of vector of individual throughputs as <maths id="math0025" num="(25)"><math display="block"><mrow><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mi>var</mi><mrow><mo>(</mo><mrow><mover accent="true"><mrow><mi>T</mi><mi>h</mi></mrow><mo stretchy="true">‾</mo></mover><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>)</mo></mrow></mrow></math><img file="EP1595369B1_D0025.tif" /></maths>

0103The fairness is defined as <maths id="math0026" num="(26)"><math display="block"><mrow><mi>Fairness</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mfrac><mn>1</mn><mrow><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow></mfrac></mrow></math><img file="EP1595369B1_D0026.tif" /></maths>

0104As will be readily understood, the ranking weights W_k(m) and channel allocation weights V_k(m) used by the decision unit 16 as part of the scheduling process can be expected to have different probable influences on different aspects of the scheduling performance. Depending on the channel conditions and the traffic load, some of the weights are expected with a high probability to contribute to an improvement of a particular second measure, whereas others of them are expected with a high probability to contribute to a deterioration in a particular second measure. The probable influence of each of the five weights in each set of weights in the present embodiment on the four second measures was investigated by incrementing or reducing each of the five weights individually whilst setting all of the other weights in the set to 1. The results of this investigation are presented in Table 1 below. <tables id="tabl0001" num="0001"><img file="EP1595369B1_D0027.tif" /></tables>

0105In Table 1, a weight is classified as belonging to a friendly class of weights ("F") for a second measure if an increase in that weight is expected with a high probability to result in the second measure improving. A weight is considered to belong to a hostile class of weights ("H") for a second measure if an increase in that weight is expected with a high probability to result in a deterioration of the second measure. Weights which are not expected with any high probability to cause either an improvement or a deterioration in a second measure are classified as belonging to a neutral class (blank in Table 1).

0106The probable influences of the weights on the second measures can be assessed by considering the first measures (different aspects of scheduling performance) to which those weights correspond, and how these are likely to affect each different second measure.

0107Consider, for example, the second measure <i>Total_Th(m)</i> relating to overall throughput.

0108The first measure <i>Metric_C</i>/<i>I</i>_<i>n</i>(<i>m</i>) is defined based on the current reported Carrier-to-Interference (C/I) ratios and the first measure <i>Metric_Oct</i>_<i>n</i>(<i>m</i>) is defined based on the efficient number of deliverable octets for the <i>n</i>th UE. If the history of the second measure relating to overall throughput reveals a drop in performance, most probably by intensifying the weights <i>W</i>_<i>2</i>(<i>m</i>), <i>W</i>_<i>3</i>(<i>m</i>), <i>V</i>_<i>2</i>(<i>m</i>) and <i>V</i>_<i>3</i>(<i>m</i>) associated with these first measures in both ranking and channel assignment processes, total throughput will recover. These weights are therefore classified as friendly. In contrast <i>Metric_Waiting_Ratio</i>_<i>n</i>(<i>m</i>) with a high probability counteracts against the total throughput. The weights <i>W</i>_<i>4</i>(<i>m</i>) and <i>V</i>_<i>4</i>(<i>m</i>) associated with this first measure can be classified as hostile to the total throughput. Reducing these weights with a high probability leads to recovery of throughput. In fact handling <i>W</i>_<i>2</i>(<i>m</i>), <i>W</i>_<i>3</i>(<i>m</i>), <i>V</i>_<i>2</i>(<i>m</i>), <i>V</i>_<i>3</i>(<i>m</i>), <i>W</i>_<i>4</i>(<i>m</i>) and <i>V</i>_<i>4</i>(<i>m</i>) in this way for a couple of TTIs will shift the behaviour of the decision unit towards the behaviour of a Max C/I packet scheduler.

0109By using the second measures, together with the classifications of the weights, to adapt or tune the weights it is possible to transform the scheduling apparatus to become a more efficient scheduler, i.e. to perform differently in response to different conditions. By producing and adapting the weights using several different second measures, it is possible to achieve a balance amongst the aspects of performance they measure.

0110An example of the way in which the weights may be adapted will now be described with reference to equations (24) to (64) below.

0111For each weight (ranking weight and channel allocation weight) two values are maintained and used. The first value is a "real" value which is the value supplied by the weight adapting unit 20 to the decision unit 16 for use by the decision unit to make its decision regarding the receiver(s) to which packets are to be transmitted. This first value is subject to certain prescribed conditions. For example, in this embodiment it must always be greater than or equal to zero, and it must not exceed some predetermined maximum value. The maximum value may, for example, be the highest value in an initial set of weight values supplied by an operator of the apparatus when the apparatus is first activated. Suitable initial sets of weight values have been disclosed in GB 0303859.3.

0112The second value of each weight is a "virtual" value which is used internally by the weight adapting unit 20 but is not supplied to the decision unit 16. This second value is what the weight adapting unit 20 uses to adjust the weights. In each TTI, new virtual values are calculated from previous virtual values within the weight adapting unit 20. These virtual values are not subject to the prescribed conditions which apply to the real values and are adapted freely. The real values are derived from the virtual values using a mathematical transformation process which ensures that the real values meet the prescribed conditions.

0113The real values of the ranking weights in the mth TTI are <maths id="math0027" num="(24)"><math display="block"><mrow><mover accent="true"><mi>W</mi><mo>‾</mo></mover><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mrow><mo>{</mo><mrow><msub><mi>W</mi><mn>1</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>W</mi><mn>2</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>W</mi><mn>3</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>W</mi><mn>4</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>W</mi><mn>5</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>}</mo></mrow></mrow></math><img file="EP1595369B1_D0028.tif" /></maths> and the real values of the channel allocation weights in the <i>m</i>th TTI are <maths id="math0028" num="(25)"><math display="block"><mrow><mover accent="true"><mi>V</mi><mo>‾</mo></mover><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mrow><mo>{</mo><mrow><msub><mi>V</mi><mn>1</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>V</mi><mn>2</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>V</mi><mn>3</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>V</mi><mn>4</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo><msub><mi>V</mi><mn>5</mn></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow><mo>}</mo></mrow></mrow></math><img file="EP1595369B1_D0029.tif" /></maths>

0114Similarly the virtual values of the ranking weights <i>Virtual_W̅</i> for current mth TTI are represented by <maths id="math0029" num="(26)"><math display="block"><mrow><mi mathvariant="italic">Virtual_</mi><mover><mrow><mi>W</mi></mrow><mrow><mo>‾</mo></mrow></mover><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo></mrow><mrow><mo>=</mo><mo>{</mo><msub><mrow><mi mathvariant="italic">virtual_W</mi></mrow><mrow><mn>1</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo></mrow><mo>,</mo><msub><mrow><mi mathvariant="italic">virtual_W</mi></mrow><mrow><mn>2</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo></mrow><mo>,</mo><mi> </mi><msub><mrow><mi mathvariant="italic">virtual_W</mi></mrow><mrow><mn>3</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo><mo>,</mo><mi> </mi><msub><mrow><mi mathvariant="italic">virtual_W</mi></mrow><mrow><mn>4</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo><mo>,</mo><mi> </mi></mrow></mrow><msub><mrow><mi mathvariant="italic">virtual_W</mi></mrow><mrow><mn>5</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo></mrow><mo>}</mo></mrow></mrow></math><img file="EP1595369B1_D0030.tif" /></maths> and the virtual values of the channel allocation weights <i>Virtual_V̅</i> are represented by <maths id="math0030" num="(27)"><math display="block"><mrow><mi mathvariant="italic">Virtual_</mi><mover><mrow><mi>V</mi></mrow><mrow><mo>‾</mo></mrow></mover><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo><mo>=</mo></mrow><mrow><mo>{</mo><msub><mrow><mi mathvariant="italic">virtual_V</mi></mrow><mrow><mn>1</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo></mrow><mo>,</mo><msub><mrow><mi mathvariant="italic">virtual_V</mi></mrow><mrow><mn>2</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo></mrow><mo>,</mo><mi> </mi><msub><mrow><mi mathvariant="italic">virtual_V</mi></mrow><mrow><mn>3</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo><mo>,</mo><mi> </mi><msub><mrow><mi mathvariant="italic">virtual_V</mi></mrow><mrow><mn>4</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo><mo>,</mo><mi> </mi></mrow></mrow><msub><mrow><mi mathvariant="italic">virtual_V</mi></mrow><mrow><mn>5</mn></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>,</mo><mi>s</mi><mo>)</mo></mrow><mo>}</mo></mrow></mrow></math><img file="EP1595369B1_D0031.tif" /></maths>

0115A one-to-one relationship between the real and virtual values <i>Virtual_W̅</i>(<i>m</i>) and <i>W̅</i>(<i>m</i>) is established. For example if <i>W</i>₁ is friendly to <i>Total_QoS</i>(<i>m</i>), <i>Virtual_W</i>₁ is also friendly to <i>Total_Qos(m).</i>

0116In the present embodiment, the adaptation of the virtual values of the weights is carried out in a series of four steps in each TTI. The index s in equations (26) and (27) denotes the step number and Virtual_W_i(m,s) (or Virtual_V_i(m,s)) denotes the virtual value of the weight W_i (or V_i) in step s of the <i>m</i>th TTI. The adaptations carried out in the four steps are now described in detail below.

Step 1:

0117For the first of the second measures, <i>Total_QoS(m),</i> a history of the changes in value of the measure is employed to assess a trend in the measure over the last <i>L</i> TTIs (eg L = 100): <maths id="math0031" num="(28)"><math display="block"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow><mi>L</mi></munderover><mrow><mrow><mo>[</mo><mrow><mi>Total_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>Total_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi></mrow><mo>)</mo></mrow></mrow><mo>]</mo></mrow></mrow></mstyle></mrow></math><img file="EP1595369B1_D0032.tif" /></maths>

0118The virtual values of the weights held from the last step (step 4) of the previous TTI (the <i>m</i>-1th TTI) are then adapted in step 1 based on the trend in the first of the second measures <i>Total_QoS</i>(<i>m</i>) and on the classification of the weights in Table 1.

0119For ranking weights friendly to <i>Total_Qos(m)</i> we have <maths id="math0032" num="(29)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>−</mo><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo></mrow></math><img file="EP1595369B1_D0033.tif" /></maths><i>i=1,4,5</i> where ε is a constant real number with a value between 0.001 and 0.01.

0120For channel allocation weights friendly to <i>Total_Qos</i>(<i>m</i>) weights we have <maths id="math0033" num="(30)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>−</mo><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo></mrow></math><img file="EP1595369B1_D0034.tif" /></maths><i>i=1,4,5</i>

0121For ranking weights hostile to <i>Total_QoS(m)</i> we have <maths id="math0034" num="(31)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>+</mo><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo></mrow></math><img file="EP1595369B1_D0035.tif" /></maths><i>i=2,3</i> and for channel allocation weights hostile to <i>Total_QoS(m)</i> we have <maths id="math0035" num="(32)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>+</mo><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_QoS</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo></mrow></math><img file="EP1595369B1_D0036.tif" /></maths><i>i=2,3</i>

0122It can be seen that as a result of equations (29) to (32) the virtual values of weights friendly to <i>Total_QoS</i>(<i>m</i>) are increased if that second measure is decreasing or not changing, and are maintained unchanged if that second measure is increasing. The virtual values of weights hostile to <i>Total_QoS(m),</i> on the other hand, are decreased if that second measure is decreasing or not changing, and are maintained unchanged if that second measure is increasing.

0123There are no neutral values in step 1 in the present example.

Step 2:

0124In this step the virtual values of the weights are adjusted again in response to a trend in the second measure <i>Var_Th</i> relating to fairness over the last <i>L</i> TTIs. This trend is judged based on <maths id="math0036" num="(33)"><math display="block"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow><mi>L</mi></munderover><mrow><mrow><mo>[</mo><mrow><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi></mrow><mo>)</mo></mrow></mrow><mo>]</mo></mrow></mrow></mstyle></mrow></math><img file="EP1595369B1_D0037.tif" /></maths>

0125The virtual values of weights friendly to fairness are adapted as <maths id="math0037" num="(34)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>+</mo><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≥</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>&lt;</mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow></math><img file="EP1595369B1_D0038.tif" /></maths> and <maths id="math0038" num="(35)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>+</mo><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≥</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>&lt;</mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>,</mo><mn>4</mn></mrow></math><img file="EP1595369B1_D0039.tif" /></maths>

0126The virtual values of weights hostile to fairness are adapted as <maths id="math0039" num="(36)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>−</mo><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≥</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>&lt;</mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>2</mn><mo>,</mo><mn>3</mn></mrow></math><img file="EP1595369B1_D0040.tif" /></maths> and <maths id="math0040" num="(37)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>−</mo><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≥</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_</mi><mi>var</mi><mi>_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>&lt;</mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>2</mn><mo>,</mo><mn>3</mn></mrow></math><img file="EP1595369B1_D0041.tif" /></maths>

0127The rest of the weights are neutral and they are left unchanged <maths id="math0041" num="(38)"><math display="block"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>∈</mo><mi>Neutral Weights</mi></mrow></math><img file="EP1595369B1_D0042.tif" /></maths> and <maths id="math0042" num="(39)"><math display="block"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>∈</mo><mi>Neutral Weights</mi></mrow></math><img file="EP1595369B1_D0043.tif" /></maths>

0128Equations (34) to (37) above differ from the corresponding equations (29) to (32) used in Step 1. This is because the second measure <i>Var</i>_<i>Th</i> relates to variance of the throughputs, i.e. it relates inversely to fairness.

Step 3:

0129In this step a trend in the second measure <i>Avg_Th</i> relating to average throughput is assessed: <maths id="math0043" num="(40)"><math display="block"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow><mi>L</mi></munderover><mrow><mrow><mo>[</mo><mrow><mi>Avg_Th</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>Avg_Th</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi></mrow><mo>)</mo></mrow></mrow><mo>]</mo></mrow></mrow></mstyle></mrow></math><img file="EP1595369B1_D0044.tif" /></maths>

0130The virtual values of weights friendly to average throughput are adapted as <maths id="math0044" num="(41)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>−</mo><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>4</mn></mrow></math><img file="EP1595369B1_D0045.tif" /></maths> and <maths id="math0045" num="(42)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>−</mo><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>4</mn></mrow></math><img file="EP1595369B1_D0046.tif" /></maths>

0131The virtual values of weights hostile to average throughput are adapted as <maths id="math0046" num="(43)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>+</mo><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>2</mn></mrow></math><img file="EP1595369B1_D0047.tif" /></maths> and <maths id="math0047" num="(44)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>+</mo><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Avg_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>2</mn></mrow></math><img file="EP1595369B1_D0048.tif" /></maths>

0132The rest of the weights are neutral and they are left unchanged: <maths id="math0048" num="(45)"><math display="block"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>∈</mo><mi>Neutral Weights</mi></mrow></math><img file="EP1595369B1_D0049.tif" /></maths> and <maths id="math0049" num="(46)"><math display="block"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>2</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>∈</mo><mi>Neutral Weights</mi></mrow></math><img file="EP1595369B1_D0050.tif" /></maths>

Step 4:

0133The trend in the second measure <i>Total_Th</i> relating to total throughput is assessed as <maths id="math0050" num="(47)"><math display="block"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow><mi>L</mi></munderover><mrow><mrow><mo>[</mo><mrow><mi>Total_Th</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi><mo>+</mo><mn>1</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>Total_Th</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi></mrow><mo>)</mo></mrow></mrow><mo>]</mo></mrow></mrow></mstyle></mrow></math><img file="EP1595369B1_D0051.tif" /></maths>

0134The virtual values of weights friendly to total throughput are adapted as <maths id="math0051" num="(48)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>−</mo><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>2</mn><mo>,</mo><mn>3</mn></mrow></math><img file="EP1595369B1_D0052.tif" /></maths> and <maths id="math0052" num="(49"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>−</mo><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>2</mn><mo>,</mo><mn>3</mn></mrow></math><img file="EP1595369B1_D0053.tif" /></maths>

0135The virtual values of weights hostile to total throughput are adapted as <maths id="math0053" num="(50)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>+</mo><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>4</mn></mrow></math><img file="EP1595369B1_D0054.tif" /></maths> and <maths id="math0054" num="(51)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>−</mo><mi>ε</mi><mo>+</mo><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi>Decisive_Total_Th</mi><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>4</mn></mrow></math><img file="EP1595369B1_D0055.tif" /></maths>

0136The neutral weights are left unchanged <maths id="math0055" num="(52)"><math display="block"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>∈</mo><mi>Neutral Weights</mi></mrow></math><img file="EP1595369B1_D0056.tif" /></maths> and <maths id="math0056" num="(53)"><math display="block"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>3</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>∈</mo><mi>Neutral Weights</mi></mrow></math><img file="EP1595369B1_D0057.tif" /></maths>

0137At this stage the virtual values are used to update the real values. To do that first the minimum virtual value is determined as <maths id="math0057" num="(54)"><math display="block"><mrow><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>min</mi></mrow></msub><mo>=</mo><mi mathvariant="normal">min</mi><mrow><mo>(</mo><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn><mo>,</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn></mrow><mo>)</mo></mrow></mrow></math><img file="EP1595369B1_D0058.tif" /></maths>

0138A further adjustment is carried out on the virtual values to make them positive: <maths id="math0058" num="(55)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>−</mo><mn>2</mn><mo>⋅</mo><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>min</mi></mrow></msub><mo>,</mo><mi> </mi><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_V</mi></mrow><mi>i</mi></msub><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>−</mo><mn>2</mn><mo>⋅</mo><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>min</mi></mrow></msub></mrow></mtd><mtd columnalign="left"><mrow><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>min</mi></mrow></msub><mo>&lt;</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><msub><mrow><mi>Virtual_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_V</mi></mrow><mi>i</mi></msub><mo>=</mo><msub><mrow><mi>Virtual_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mn>4</mn></mrow><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>min</mi></mrow></msub><mo>≥</mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow></mrow></math><img file="EP1595369B1_D0059.tif" /></maths> where <i>Virtual</i>2_<i>W</i>_<i>i</i>(<i>m</i>) and <i>Virtual</i>2_<i>V</i>_<i>i</i>(<i>m</i>) are the adjusted positive values.

0139Next, the maximum of these adjusted positive values is found: <maths id="math0059" num="(56)"><math display="block"><mrow><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>max</mi></mrow></msub><mo>=</mo><mi>max</mi><mrow><mo>(</mo><mrow><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_W</mi></mrow><mi>i</mi></msub><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn><mo>,</mo><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_V</mi></mrow><mi>i</mi></msub><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn></mrow><mo>)</mo></mrow></mrow></math><img file="EP1595369B1_D0060.tif" /></maths>

0140As mentioned previously, in this embodiment no weight is permitted to have a real value exceeding a maximum weight in an initial set of weights applied, for example, by an operator: <maths id="math0060" num="(57)"><math display="block"><mrow><mi>max</mi><mi>_initial_weight</mi><mo>=</mo><mi>max</mi><mrow><mo>(</mo><mrow><msub><mi>W</mi><mi>i</mi></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn><mo>,</mo><msub><mi>V</mi><mi>i</mi></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn></mrow><mo>)</mo></mrow></mrow></math><img file="EP1595369B1_D0061.tif" /></maths>

0141Then for the real values of the weights we have <maths id="math0061" num="(58)"><math display="block"><mrow><msub><mi>W</mi><mi>i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_W</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><mrow><mrow><mi>max</mi><mi>_initial_weight</mi></mrow><mo>/</mo><mrow><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>max</mi></mrow></msub></mrow></mrow><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn></mrow></math><img file="EP1595369B1_D0062.tif" /></maths> and <maths id="math0062" num="(59)"><math display="block"><mrow><msub><mi>V</mi><mi>i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mi>Virtual</mi><mn>2</mn><msub><mrow><mi>_V</mi></mrow><mi>i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>⋅</mo><mrow><mrow><mi>max</mi><mi>_initial_weight</mi></mrow><mo>/</mo><mrow><msub><mrow><mi>Virtual</mi></mrow><mrow><mi>max</mi></mrow></msub></mrow></mrow><mi> </mi><mi>i</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mn>5</mn></mrow></math><img file="EP1595369B1_D0063.tif" /></maths>

0142The mathematical transformations introduced from (54) to (59) put a limit on the growth of the real values of the weights and prevent divergence in one or some of performance measures of QoS provisioning. These formulae are derived through extensive experimental studies.

0143Referring back to equations (19) and (20) it can be seen that the decision unit 16 also employs an adaptive further weight γ(<i>m,j</i>) relating to delay tolerance. There is such an adaptive weight <i>γ</i>(<i>m,j</i>) per group j of UEs which have the same delay tolerance. These per-group adaptive weights γ (<i>m,i</i>) are also adapted by the weight adapting unit 20. For each group j a measure <i>Avg_Group_QoS(m, j)</i> of the average quality of service experienced in the mth TTI by the UEs belonging to the group is calculated as <maths id="math0063" num="(60)"><math display="block"><mrow><mi>Avg_Group_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>=</mo><mfrac><mn>1</mn><mrow><msub><mi>N</mi><mi>j</mi></msub></mrow></mfrac><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>i</mi><mo>=</mo><mn>1</mn></mrow><mrow><msub><mi>N</mi><mi>j</mi></msub></mrow></munderover><mrow><msub><mrow><mi mathvariant="normal">Throughput_Satisfy_QoS</mi></mrow><mi mathvariant="normal">i</mi></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow></mstyle><mo>,</mo><mi> </mi><mi>j</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mi>J</mi></mrow></math><img file="EP1595369B1_D0064.tif" /></maths> where <i>N</i>_<i>j</i> is the number of UEs in group <i>j</i> and <i>Throughput_Satisfy_QoS</i> is calculated for each UE in the group according to equation (2) above.

0144A trend of the average group quality of service for each group j over the last <i>L</i> TTIs is then assessed as <maths id="math0064" num="(61)"><math display="block"><mrow><mi>Decisive_Avg_Group_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>l</mi><mo>=</mo><mn>1</mn></mrow><mi>L</mi></munderover><mrow><mrow><mo>[</mo><mrow><mi>Avg_Group_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi><mo>+</mo><mn>1</mn><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>−</mo><mi>Avg_Group_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mi>l</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow></mrow><mo>]</mo></mrow></mrow></mstyle></mrow></math><img file="EP1595369B1_D0065.tif" /></maths>

0145This trend is then employed to calculate a parameter ω<i>(m,j)</i> as follows <maths id="math0065" num="(62)"><math display="block"><mrow><mrow><mo>{</mo><mrow><mtable columnalign="left"><mtr columnalign="left"><mtd columnalign="left"><mrow><mi>ω</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>=</mo><mi>γ</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>+</mo><mi>ε</mi><mo>−</mo><mi mathvariant="normal">Decisive_Avg_Group_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>,</mo></mrow></mtd><mtd columnalign="left"><mrow><mi mathvariant="normal">Decisive_Avg_Group_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>≤</mo><mn>0</mn></mrow></mtd></mtr><mtr columnalign="left"><mtd columnalign="left"><mrow><mi>ω</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>=</mo><mi>γ</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>−</mo><mn>1</mn><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow></mrow></mtd><mtd columnalign="left"><mrow><mi mathvariant="normal">Decisive_Avg_Group_QoS</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>></mo><mn>0</mn></mrow></mtd></mtr></mtable></mrow></mrow></mrow></math><img file="EP1595369B1_D0066.tif" /></maths>

0146The per-group adaptive QoS weights γ<i>(</i>_<i>m</i><i>,</i>_<i>j</i><i>)</i> are then updated as <maths id="math0066" num="(63)"><math display="block"><mrow><mi>γ</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow><mo>=</mo><mrow><mrow><mi>ω</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow></mrow><mo>/</mo><mrow><msub><mi>ω</mi><mrow><mi mathvariant="normal">min</mi></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow></mrow></mrow><mo>,</mo><mi> </mi><mi>j</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mi>J</mi></mrow></math><img file="EP1595369B1_D0067.tif" /></maths> where <maths id="math0067" num="(64)"><math display="block"><mrow><msub><mi>ω</mi><mrow><mi mathvariant="normal">min</mi></mrow></msub><mrow><mo>(</mo><mi>m</mi><mo>)</mo></mrow><mo>=</mo><mi>min</mi><mrow><mo>(</mo><mrow><mi>ω</mi><mrow><mo>(</mo><mrow><mi>m</mi><mo>,</mo><mi>j</mi></mrow><mo>)</mo></mrow></mrow><mo>)</mo></mrow><mo>,</mo><mi> </mi><mi>j</mi><mo>=</mo><mn>1</mn><mo>⋯</mo><mi>J</mi></mrow></math><img file="EP1595369B1_D0068.tif" /></maths>

0147The transformations introduced from (62) to (64) guarantee that all the UEs get positive values of group QoS weights γ(_{<i>m</i>,<i>j</i>}) while the group with lowest priority of service always gets a weight value of 1. The transformations also try to avoid unlimited growth of the group QoS weights γ(<i>m</i>,<i>j</i>). These mappings are preferable to prevent divergence in the performance measures related to individual QoS of UEs and those related to overall QoS. These transforms are derived and verified experimentally.

0148At this stage all the weights have been updated for the mth TTI. They can be applied to the decision unit to enable it to produce the ranking and channel allocation metrics defined in (19) and (20). The steps in the flowchart of Figure 5 may then be carried out by the decision unit.

0149Next, various simulation results for a preferred embodiment of the invention are provided. These simulation results relate to a simulated traffic environment in which there are multiple UEs. A first group of these UEs are assumed to be attempting to receive real-time video data and a second group of UEs are assumed to be attempting WWW browsing sessions. This scenario is illustrated schematically in Figure 7. As shown in Figure 7, WWW download packets are delivered to an application receiver buffer in a UE via the Internet and via an HSDPA system. Real-time video is delivered to the UE's application receiver buffer via the HSDPA system directly.

0150The real-time video data is made up of real time protocol (RTP) packets. In the present simulation, a video traffic model confirming to ITU H.263 is employed. This traffic model concentrates on the traffic characteristics related to video encoding and RTP packet transport. The model generates 7.5 video frames per second with a target bit rate of the output video stream of 32 kbps. The video frames are segmented into one or several RTP packets, depending on the size of the video frame.

0151WWW browsing sessions are considered to consist of a sequence of packet calls as defined in TR 25.848, ver 1.0.0, RP-010191, TSG-RAN#11, March 2001. A slowing mechanism is assumed to be applied to the WWW browsing sessions. This slowing mechanism prevents the downloading of a new session unless a previous session has been successfully downloaded completely. For example, if a first web page has a link to a second web page, the slowing mechanism would not permit the second page to be downloaded until all of the first page had been successfully downloaded.

0152The real-time video data and WWW data share the same channelisation codes (channels) in the HSDPA system.

0153The cellular environment which is assumed in the present simulation is illustrated schematically in Figure 8. In Figure 8 the spacing between adjacent base stations (Node-Bs) 30 is assumed to be 6km. There is a base station for each cell. Each cell is divided up into three sectors, and the sector boundaries are shown in Figure 8. As illustrated in Figure 8, it is assumed that the UEs are initially distributed uniformly across the cells and that they then move around.

0154It is also assumed in relation to the cellular environment that the Node-Bs have fixed transmission powers. This is a realistic assumption for a fully-loaded HSDPA system which does not employ power control. Adjacent cell interference is the result of transmissions from adjacent Node-Bs. The level of adjacent cell interference is determined based on the fixed power levels from transmitting Node-Bs. Another assumption is that path loss is present and affects the signal quality. It is also assumed that one packet scheduling apparatus embodying the present invention is provided per sector to handle the data for all of the UEs in that sector.

0155To model the impact of Rayleigh fading, an ETSI 6-path Rayleigh vehicular A channel model is employed. It is assumed that the speed of each UE is 3.6km/h. Table 2 below illustrates the relative delay and average power of the six different paths assumed to make up the channel. <tables id="tabl0002" num="0002"><table frame="all"><title><b><i>Table 2</i></b></title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="12mm" colsep="1" /><colspec colnum="2" colname="col2" colwidth="26mm" colsep="1" /><colspec colnum="3" colname="col3" colwidth="24mm" colsep="1" /><thead><row><entry namest="col1" nameend="col1" morerows="1" rowsep="1" align="center" valign="top">Path</entry><entry namest="col2" nameend="col3" colsep="1" rowsep="1" align="center" valign="top">Channel A</entry></row><row><entry namest="col2" nameend="col2" align="center" valign="top">Rel. Delay (nS)</entry><entry namest="col3" nameend="col3" align="center" valign="top">Avg. Pwr (dB)</entry></row></thead><tbody><row><entry namest="col1" nameend="col1" align="center" valign="top">1</entry><entry namest="col2" nameend="col2" align="center" valign="top">0</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.0</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">2</entry><entry namest="col2" nameend="col2" align="center" valign="top">310</entry><entry namest="col3" nameend="col3" align="center" valign="top">-1.0</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">3</entry><entry namest="col2" nameend="col2" align="center" valign="top">710</entry><entry namest="col3" nameend="col3" align="center" valign="top">-9.0</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">4</entry><entry namest="col2" nameend="col2" align="center" valign="top">1090</entry><entry namest="col3" nameend="col3" align="center" valign="top">-10.0</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">5</entry><entry namest="col2" nameend="col2" align="center" valign="top">1730</entry><entry namest="col3" nameend="col3" align="center" valign="top">-15.0</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">6</entry><entry namest="col2" nameend="col2" align="center" valign="top">2510</entry><entry namest="col3" nameend="col3" align="center" valign="top">-20.0</entry></row></tbody></tgroup></table></tables>

0156The shadowing is assumed to have a log-normal distribution. The shadowing parameters that are assumed are set out in Table 3 below. <tables id="tabl0003" num="0003"><table frame="all"><title><b><i>Table 3</i></b></title><tgroup cols="2" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="68mm" colsep="1" /><colspec colnum="2" colname="col2" colwidth="15mm" colsep="1" /><thead><row><entry namest="col1" nameend="col1" align="center" valign="top">Parameters</entry><entry namest="col2" nameend="col2" align="center" valign="top">Values</entry></row></thead><tbody><row><entry namest="col1" nameend="col1" align="center" valign="top">Log-normal Shadow fading standard deviation</entry><entry namest="col2" nameend="col2" align="center" valign="top">8 dB</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Decorrelation Distance</entry><entry namest="col2" nameend="col2" align="center" valign="top">20 m</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Correlation between sites</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.5</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Correlation between sectors</entry><entry namest="col2" nameend="col2" align="center" valign="top">1</entry></row></tbody></tgroup></table></tables>

0157Figure 9 shows the assumed packet data arrivals for the different UEs in a first simulated example. UEs 1 to 10 are video users. UEs 11 to 90 are WWW users. In the first example, the total aggregate traffic load is assumed to be approximately constant over a series of 30,000 TTIs (60 second period). As can be seen from Figure 9, each video user (UE1 to UE10) has an almost continuous stream of packet arrivals. For WWW users (UE 11 to UE 90), the packet arrivals are discontinuous. However, when data is arriving, the instantaneous data rate may be much larger than the video data rate of 32kbps. Thus, the aggregate offered load for WWW users is assumed to be large compared to that for video users. In other words, video users have a narrow pipe, whereas WWW users have a wide pipe.

0158It is assumed that the channel estimation performed by each UE is perfect, and that the feedback signalling is error free. Also, a minimum reporting delay is considered to be 3TTIs.

0159It is also assumed that the tolerable delay threshold for WWW sessions is 1.5 seconds. For video services the tolerable delay threshold is assumed to be 100 milliseconds. Chase combining is carried out, and the maximum number of transmissions of a packet is 6. A packet is dropped if it cannot be delivered within 6 retransmissions. It is assumed that video users belong to the service group j = 1 and WWW users belong to the service group j = 2. In all the following simulations, the service priority parameter β₁ for video users is fixed at 10, and the service priority parameter for WWW users is fixed at 1. It is also assumed that the trend of the second measures over <i>L</i> = 100 TTIs is taken into account, and that ε = 0.001. γ<i>(</i>_{<i>m, j</i>}<i>)</i> is assumed to be 1 for all the UEs.

0160In the following description with reference to Figures 10 to 22, the performance of scheduling apparatus embodying the present invention will be compared with the performance of a conventional FIFO weighted max C/I scheduler and with a previously-considered scheduler described in GB 0303859.3 having fixed weights.

0161Firstly, Figures 10 and 11 relate to the performance of the max C/I scheduler under the traffic scenario shown in Figure 9. Figure 10 shows how the four second measures defined in equations (21), (22), (23) and (26) vary over the simulation period of 30,000 TTIs. Figure 10 also shows the variation in the group measures Avg_Group_QoS for video services and for WWW services defined in equation (60).

0162Figure 11 is a graph corresponding to Figure 10 but showing just the variation over the first 2,000 TTIs (or 4 seconds) of the simulation period. It can be seen that, since all the real-time video users and the WWW users share the same channels, the HSDPA system performance in terms of QoS of real-time video and fairness collapses initially in response to the sudden admission of all of the video and WWW calls at the beginning of the simulation period. It can be seen that the QoS of real-time video initially rises to about 0.6 but then the performance deteriorates to around 0.3. The performance recovers later, but this "run-away" phenomenon is unsatisfactory for video users. No such "run-away" phenomenon occurs in the QoS for WWW users, for which the performance is steadily rising over the simulation period.

0163Next, Figures 12 and 13 present the same information as Figures 10 and 11 but for a scheduler as described in GB 0303859.3 having the following set of roughly-assigned fixed weights: <maths id="math0068"><math display="block"><mrow><msub><mi>W</mi><mn>1</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>2</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>10</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>3</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>4</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>5</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn></mrow></math><img file="EP1595369B1_D0069.tif" /></maths><maths id="math0069"><math display="block"><mrow><msub><mi>V</mi><mn>1</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>2</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>3</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>4</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>10</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>5</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>0.1</mn></mrow></math><img file="EP1595369B1_D0070.tif" /></maths>

0164These values are not the optimum values disclosed in GB 0303859.3. Instead, they are deliberately chosen to be non-optimum values because in practice the optimum initialisation of fixed weights in such a scheduler may not be possible.

0165As Figure 13 shows, there is still a run-away effect in the first 1,000 TTIs (or two seconds). The QoS of WWW users and the QoS of real-time video users clearly have two opposite trends in Figure 13. Furthermore, the variance of throughputs is steadily increasing during the first two seconds of the simulation period. It can be seen that the recovery in Figure 13 is faster than in Figure 11 (the max C/I scheduler). However, in some circumstances the period of recovery and the final level of achieved stable performance may not be acceptable for real-time video users.

0166Figure 14 shows the performance of an embodiment of the present invention in which the weights are adapted starting from the rough initial values set out above. The same performance measures as shown in Figures 10 to 13 are illustrated. In this example, however, the transformations of equations (54) to (59) and (62) to (64) are not applied when deriving the real values of the weights from the virtual values. Thus, effectively the virtual values, which are adjusted without limitation, are applied directly to the decision unit 16 in Figure 4.

0167From Figure 14 it can be seen that the QoS of WWW users is significantly lower than the QoS of video users within the first 30 seconds of the simulation period. The flat level of the QoS of WWW users means that within this initial period, the transmissions to video users are almost totally dominant and block any delivery of data to WWW users. This severe output bit pipe imbalance has a direct impact on the final delivered output bit rate which is more than 500 kbps lower than both the conventional FIFO weighted max C/I scheduler and the scheduler of GB 0303859.3 with roughly-assigned fixed weights. It is for this reason that the mathematical transformations (normalisations) of equations (54) to (59) and (62) to (64) are preferable in a mixed-service scenario to provide a balance among all the different aspects of QoS provisioning.

0168Figure 15 shows the performance of a scheduler embodying the present invention when the transformations of equations (54) to (59) and (62) to (64) are applied. It is assumed that the scheduler is initialised with the same set of rough weights used to produce the results shown in Figures 12 and 13. The weights are then adapted by the scheduler.

0169It is evident that the adaptive control mechanism has managed to improve the performance compared to the fixed-weight scheduler disclosed in GB 0303859.3 to a considerable degree (see Figure 12).

0170Figure 16 compares the variance of throughputs over time for (a) a FIFO-weighted max C/I scheduler, (b) the fixed-weight scheduler of GB 0303859.3 with roughly-assigned weights, and (c) a scheduler embodying the present invention. It can be seen that a scheduler embodying the present invention has an efficient fast response to the run-away phenomenon.

0171Figure 17 is a graph comparing the QoS of video users over time for the three different schedulers (a) to (c). Again the efficient fast response to the run-away phenomenon of a scheduler embodying the present invention is evident.

0172Figures 18(A) to 18(F) present other comparisons of performance between the three schedulers (a) to (c).

0173Figure 18(A) presents a graph for comparing total throughput (WWW and video) in the three schedulers. The lines indicate a cumulative density function (CDF) of the throughputs of all UEs.

0174Figure 18(B) is a graph for comparing average video throughput in the three schedulers. The lines indicate a mean CDF of the throughputs of the UEs 1 to 10 which are receiving video services.

0175Figure 18(C) is a graph corresponding to Figure 18(B) but for comparing average WWW throughput in the three schedulers. The lines indicate a mean CDF of the throughputs of the UEs 11 to 90 which are receiving WWW services.

0176Figure 18(D) is a graph for comparing the QoS for video users in the three schedulers.

0177Figure 18(E) is a graph for comparing the QoS of WWW users in the three schedulers.

0178Figure 18(F) is a graph for comparing overall throughput to all UEs in the three schedulers.

0179Table 4 below presents the performance comparisons for the first simulation example in quantitative form. The performance comparison measures are delivered bit rate (total throughput over the 30,000 TTIs divided by 60 seconds), average throughput, average delay, QoS for WWW services and QoS for video services. The average throughput is the average of the individual throughputs as defined by equation (23). The average delay is the average of the respective delays experienced by the successfully-delivered packets. The QoS for each service is the ratio of octets delivered error-free to the relevant UEs within the tolerable delay threshold for the service concerned to the total number of octets which arrived at node B. <tables id="tabl0004" num="0004"><table frame="all"><title><b><i>Table 4</i></b></title><tgroup cols="4" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52mm" colsep="1" /><colspec colnum="2" colname="col2" colwidth="22mm" colsep="1" /><colspec colnum="3" colname="col3" colwidth="22mm" colsep="1" /><colspec colnum="4" colname="col4" colwidth="15mm" colsep="1" /><thead><row><entry namest="col1" nameend="col1" align="center" valign="top">Scheduler</entry><entry namest="col2" nameend="col2" align="center" valign="top">(a)</entry><entry namest="col3" nameend="col3" align="center" valign="top">(b)</entry><entry namest="col4" nameend="col4" align="center" valign="top">(c)</entry></row></thead><tbody><row><entry namest="col1" nameend="col1" align="center" valign="top">Delivered Bit Rate</entry><entry namest="col2" nameend="col2" align="center" valign="top">1.969 Mbps</entry><entry namest="col3" nameend="col3" align="center" valign="top">2.186 Mbps</entry><entry namest="col4" nameend="col4" align="center" valign="top">2.1921</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Average Throughput</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.9127</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.9731</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.998</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Average Delay</entry><entry namest="col2" nameend="col2" align="center" valign="top">4.5966 sec</entry><entry namest="col3" nameend="col3" align="center" valign="top">1.4563 sec</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.6071</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Satisfied QoS Conditions (WWW)</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.6331</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.7949</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.8758</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Satisfied QoS Conditions (Video)</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.4958</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.6814</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.9783</entry></row></tbody></tgroup></table></tables>

0180It can be seen from Table 4 how efficiently the scheduler (c) embodying the present invention improves all the system performance features. It has successfully managed to deliver a fair output for all wireless end-users even over short periods of time.

0181The set of virtual weight values at the end of the simulation period are: <maths id="math0070"><math display="block"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mn>1</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>4.79</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual_W</mi></mrow><mn>2</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>0.4881</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual_W</mi></mrow><mn>3</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>38.4451</mn><mo>,</mo></mrow></math><img file="EP1595369B1_D0071.tif" /></maths><maths id="math0071"><math display="block"><mrow><msub><mrow><mi>Virtual_W</mi></mrow><mn>4</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>9.6</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual_W</mi></mrow><mn>5</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>30.87</mn></mrow></math><img file="EP1595369B1_D0072.tif" /></maths><maths id="math0072"><math display="block"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mn>1</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>4.79</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual_V</mi></mrow><mn>2</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mo>−</mo><mn>9.411</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual_V</mi></mrow><mn>3</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>38.4451</mn><mo>,</mo></mrow></math><img file="EP1595369B1_D0073.tif" /></maths><maths id="math0073"><math display="block"><mrow><msub><mrow><mi>Virtual_V</mi></mrow><mn>4</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>4.965</mn><mo>,</mo><mi> </mi><msub><mrow><mi>Virtual_V</mi></mrow><mn>5</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>30.87</mn></mrow></math><img file="EP1595369B1_D0074.tif" /></maths>

0182The set of real weight values (optimised and adjusted) at the end of the period are <maths id="math0074"><math display="block"><mrow><msub><mi>W</mi><mn>1</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>4.12</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>2</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>3.37</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>3</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>10</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>4</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>4.96</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>5</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>8.68</mn></mrow></math><img file="EP1595369B1_D0075.tif" /></maths><maths id="math0075"><math display="block"><mrow><msub><mi>V</mi><mn>1</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>4.12</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>2</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>1.64</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>3</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>10</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>4</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>4.96</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>5</mn></msub><mrow><mo>(</mo><mrow><mn>30000</mn></mrow><mo>)</mo></mrow><mo>=</mo><mn>8.68</mn></mrow></math><img file="EP1595369B1_D0076.tif" /></maths>

0183Figures 19(A) to 19(C) show respectively the performances of the three schedulers (a) to (c) in terms of the CDF of the throughput of each individual UE over the simulation period. In Figures 19(A) to 19(C) the dashed lines represent UEs of video users, and the solid lines represent UEs of WWW users. It can be seen that packets are delivered much faster in the scheduler (c) embodying the present invention.

0184Next, a second simulation example will be described in which the conditions are assumed to be generally similar to those of the first simulation example. However, in the second simulation example a "good" initial set of weights more appropriate to the conditions than the one used in the first simulation example is assumed. This "good" set of weights is that disclosed in GB 0303859.3 for use when a slowing mechanism is applied to WWW browsing, namely: <maths id="math0076"><math display="block"><mrow><msub><mi>W</mi><mn>1</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>2</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>10</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>3</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>4</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn><mo>,</mo><mi> </mi><msub><mi>W</mi><mn>5</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn></mrow></math><img file="EP1595369B1_D0077.tif" /></maths><maths id="math0077"><math display="block"><mrow><msub><mi>V</mi><mn>1</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>2</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>3</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>4</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>10</mn><mo>,</mo><mi> </mi><msub><mi>V</mi><mn>5</mn></msub><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow><mo>=</mo><mn>1</mn></mrow></math><img file="EP1595369B1_D0078.tif" /></maths>

0185The "good" set of weights is assumed to be the fixed set of weights applied to the scheduler (b) disclosed in GB 0303859.3 in the following results.

0186Figures 20(A) to 20(F) for the second simulation example correspond to those of Figures 18(A) to 18(F) for the first simulation example. It can be seen that the performance of the scheduler (b) in GB 0303859.3 is greatly improved by the use of the "good" set of weights (fixed weights). However, even in this case, the scheduler (c) embodying the present invention improves the performance still further by adapting the weights, see especially Figure 20(D).

0187Table 5 below compares the performance of schedulers (b) and (c) for the second simulation example in quantitative form, similar to Table 4 above. <tables id="tabl0005" num="0005"><table frame="all"><title><b><i>Table 5</i></b></title><tgroup cols="3" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52mm" colsep="1" /><colspec colnum="2" colname="col2" colwidth="20mm" colsep="1" /><colspec colnum="3" colname="col3" colwidth="15mm" colsep="1" /><thead><row><entry namest="col1" nameend="col1" align="center" valign="top">Scheduler</entry><entry namest="col2" nameend="col2" align="center" valign="top">(b)</entry><entry namest="col3" nameend="col3" align="center" valign="top">(c)</entry></row></thead><tbody><row><entry namest="col1" nameend="col1" align="center" valign="top">Delivered Bit Rate</entry><entry namest="col2" nameend="col2" align="center" valign="top">2.32 Mbps</entry><entry namest="col3" nameend="col3" valign="top" align="char" char="." charoff="15">2.1921</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Average Throughput</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.9869</entry><entry namest="col3" nameend="col3" valign="top" align="char" char="." charoff="15">0.9982</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Average Delay</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.5697 sec</entry><entry namest="col3" nameend="col3" valign="top" align="char" char="." charoff="15">0.6172</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Satisfied QoS Conditions (Video)</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.8994</entry><entry namest="col3" nameend="col3" valign="top" align="char" char="." charoff="15">0.9590</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Satisfied QoS Conditions (WWW)</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.8658</entry><entry namest="col3" nameend="col3" valign="top" align="char" char="." charoff="15">0.8535</entry></row></tbody></tgroup></table></tables>

0188From Figure 20(E) and Table 5 it can be seen that in order to achieve a better quality of service for video users, the scheduler (c) embodying the present invention reduces the quality of service for WWW users. This is because the fixed service priority parameter β₁ = 10) given to video services is much higher than that (β₂ = 1) given to WWW services. Figure 20(D) shows how successfully a scheduler embodying the invention manages to prevent the QoS drop for video services.

0189Next, a third simulation example relating to a changing traffic load scenario is considered. In this third example, there are 50 UEs in total, of which UEs 1 to 10 are video users, and UEs 11 to 50 are WWW users. The assumed packet data arrivals for the different UEs in the third simulation example are shown in Figure 21. At the beginning of the simulation period, all 10 video users are admitted and a single WWW user is admitted (UE 50). After 10 seconds, the first 19 WWW users are allowed to begin WWW browsing sessions. After 30 seconds, the remaining WWW users are allowed to begin WWW browsing sessions.

0190Figures 22(A) to 22(F) present the performance results for the three schedulers (a) to (c) in the third simulation example. The graphs correspond respectively to Figures 18(A) to 18(F) for the first simulation example.

0191From Figure 22(E) it can be seen that the performance of the scheduler (a) in terms of QoS drops significantly when new WWW users are admitted after 10 seconds. The scheduler (c) embodying the present invention manages to avoid this situation and provides greater robustness than the fixed-weight scheduler (b).

0192The balancing role of a scheduler embodying the present invention can be observed in Figure 22(A) which shows that the variance of individual throughputs has been reduced and fairness of delivery has been improved over the entire simulation period. Furthermore, the average throughput curves in Figures 22(B) and 22(C) confirm that adapting the weights improves the performance over a comparable fixed-weight scheduler (b). These graphs also show that the scheduler (c) can achieve simultaneously a better QoS for both video services and WWW services than the scheduler (b). Figure 22(F) shows how successfully the scheduler (c) embodying the invention manages to provide a better instantaneous overall throughput over all of the simulation period.

0193Table 6 below presents the performance comparisons for the third simulation example in quantitative form, similar to Tables 4 and 5 above. <tables id="tabl0006" num="0006"><table frame="all"><title><b><i>Table 6</i></b></title><tgroup cols="4" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="52mm" colsep="1" /><colspec colnum="2" colname="col2" colwidth="22mm" colsep="1" /><colspec colnum="3" colname="col3" colwidth="24mm" colsep="1" /><colspec colnum="4" colname="col4" colwidth="24mm" colsep="1" /><thead><row><entry namest="col1" nameend="col1" align="center" valign="top">Scheduler</entry><entry namest="col2" nameend="col2" align="center" valign="top">(a)</entry><entry namest="col3" nameend="col3" align="center" valign="top">(b)</entry><entry namest="col4" nameend="col4" align="center" valign="top">(c)</entry></row></thead><tbody><row><entry namest="col1" nameend="col1" align="center" valign="top">Delivered Bit Rate</entry><entry namest="col2" nameend="col2" align="center" valign="top">1.074 Mbps</entry><entry namest="col3" nameend="col3" align="center" valign="top">1.2487 Mbps</entry><entry namest="col4" nameend="col4" align="center" valign="top">1.2861 Mbps</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Average Throughput</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.9203</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.9960</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.9973</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Average Delay</entry><entry namest="col2" nameend="col2" align="center" valign="top">1.3508 sec</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.483 sec</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.2639 sec</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Satisfied QoS Conditions (WWW)</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.7276</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.9283</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.9592</entry></row><row><entry namest="col1" nameend="col1" align="center" valign="top">Satisfied QoS Conditions (Video)</entry><entry namest="col2" nameend="col2" align="center" valign="top">0.8322</entry><entry namest="col3" nameend="col3" align="center" valign="top">0.9662</entry><entry namest="col4" nameend="col4" align="center" valign="top">0.9770</entry></row></tbody></tgroup></table></tables>

0194The third simulation example shows that under a heavily-loaded traffic scenario, a scheduler embodying the present invention can improve the total throughput, QoS of services and the average delivery of packets simultaneously while increasing the robustness of the scheduler to the effects of varying traffic load. In a dynamic mobile cellular environment, many new calls with different QoS requirements and delay tolerances can be admitted to a base station. Therefore the nature of input traffic load changes radically as time progresses. A scheduler required to operate in such an environment faces a number of input pipes some of which are aligned and some of which are varied in terms of bit rate. A successful packet scheduler is one that can provide a stable output quality (similar to that which would be achieved in a wired connection as opposed to a wireless environment) despite these varying input bit pipes in a mixed service environment. The results shown in Figures 22(A) to (F) confirm that a scheduler embodying the present invention can provide such a stable "wired" output quality over the entire transmission period.

0195In the embodiment of the present invention described in detail above, a weighted combination of the first measures was produced for each different receiver, and the respective weighted combinations for the different receivers were then compared with one another to decide the receiver(s) to which packets are to be transmitted. However, in other embodiments, the present invention can also be applied to the packet scheduling methods described in S. Abedi, S. Vadgama, "Hybrid Genetic Packet Scheduling and radio Resource Management for High Speed Downlink Packet Access", WPMC 2002 Conference, Hawaii, pp. 1192-1196 and S. Abedi, S. Vadgama, "A Radio Aware Random Iterative Scheduling Technique for High Speed Downlink Packet Access", VTC 2002, Fall, vol. 4, pp. 2322 - 2326, 24-28, Sept. 2002. For example, in the latter reference a plurality of candidate scheduling solutions η₁ to η_n are generated. Each candidate solution η specifies at least the receiver(s) to which packets are to be transmitted in a scheduling instant (eg TTI) under consideration. At least one of the candidate solutions is generated randomly. For each candidate solution η a "unified measure of fitness" is calculated according to a fitness function <maths id="math0078" num="(65)"><math display="block"><mrow><mi>f</mi><mrow><mo>(</mo><mi>η</mi><mo>)</mo></mrow><mo>=</mo><mfrac><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>E</mi></mrow></msub><mo>+</mo><msub><mi>W</mi><mrow><mn>2</mn><mi>E</mi></mrow></msub><mo>⋅</mo><mi>u</mi><mrow><mo>(</mo><mrow><mi>Eff_Oct</mi></mrow><mo>)</mo></mrow></mrow><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>E</mi></mrow></msub></mrow></mfrac><mo>⋅</mo><mfrac><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>D</mi></mrow></msub><mo>+</mo><msub><mi>W</mi><mrow><mn>2</mn><mi>D</mi></mrow></msub><mo>⋅</mo><mi>v</mi><mrow><mo>(</mo><mrow><mi>Delay_Profile</mi></mrow><mo>)</mo></mrow></mrow><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>D</mi></mrow></msub></mrow></mfrac><mo>⋅</mo><mfrac><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>F</mi></mrow></msub><mo>+</mo><msub><mi>W</mi><mrow><mn>2</mn><mi>F</mi></mrow></msub><mo>⋅</mo><mi>x</mi><mrow><mo>(</mo><mrow><mi>Fairness</mi></mrow><mo>)</mo></mrow></mrow><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>F</mi></mrow></msub></mrow></mfrac><mo>⋅</mo><mfrac><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>R</mi></mrow></msub><mo>+</mo><msub><mi>W</mi><mrow><mn>2</mn><mi>R</mi></mrow></msub><mo>⋅</mo><mi>y</mi><mrow><mo>(</mo><mrow><mi>Ratio_Waiting_Oct</mi></mrow><mo>)</mo></mrow></mrow><mrow><msub><mi>W</mi><mrow><mn>1</mn><mi>R</mi></mrow></msub></mrow></mfrac></mrow></math><img file="EP1595369B1_D0079.tif" /></maths> where <i>u</i>(.), <i>v</i>(.), <i>x</i>(.) and <i>y</i>(.) are the mapping functions, <i>W</i>_1<i>E</i><i>, W</i>_2<i>E</i><i>, W</i>_1<i>F</i><i>, W</i>_2<i>F</i><i>, W</i>_1<i>D</i><i>, W</i>_2<i>D</i><i>, W</i>_1<i>R</i> and <i>W</i>_2<i>R</i> are the weighting coefficients, and <i>Eff_Oct, Delay_Profile, Fairness</i> and <i>Ratio_Waiting_Oct</i> are the first measures in this case. The first measure <i>Eff_Oct</i> is an estimate of the number of octets that will be delivered if the solution η is chosen. The first measure <i>Delay_Profile</i> is a measure of the delay experienced by the earliest undelivered octet which has arrived at the transmitter but has not yet been delivered. The first measure <i>Fairness</i> is a measure of the expected contribution of the candidate solution η to the fairness of the packet scheduling process. The first measure <i>Ratio_Waiting_Oct</i> is a measure of the ratio of octets waiting at the transmitter for transmission to the total number of octets arrived in the node B source queue for the UEs in the candidate solution concerned.

0196More information about the way in which these first measures are derived can be found in the inventor's paper referenced above, the entire content of which is incorporated herein by reference.

0197It will be appreciated that the first measures in this embodiment are not calculated per receiver. Instead, they are calculated per candidate scheduling solution. Often, this means that when producing the first measures, aspects of the performance of more than one UE must be taken into account. For example, aspects of the scheduling performance of all the UEs in the candidate scheduling solution may need to be taken into account.

0198It will be seen from equation (65) that the fitness function is a weighted combination of the first measures, produced in this case for each candidate scheduling solution rather than for each receiver. Once respective fitness functions (weighted combinations) have been produced for the different candidate scheduling solutions, these are then compared with one another to select a best one of the candidate solutions η_best based on the comparison results.

0199A similar fitness function is used in the packet scheduling method described in S. Abedi, S. Vadgama, "Hybrid Genetic Packet Scheduling and radio Resource Management for High Speed Downlink Packet Access", WPMC 2002 Conference, Hawaii, pp. 1192-1196. In this case, the packet scheduling method is based on a genetic algorithm, and the fitness functions for the different candidate solutions are compared with one another as part of the process for selecting parents of one generation to have children of a next generation. Thus, in this case, the fitness function is used over a series of generations to arrive at a best candidate scheduling solution. Nonetheless, the fitness functions (weighted combinations) are still employed to decide the receiver(s) to which packets are to be transmitted. Further details of the way in which the fitness function is employed are provided in the inventor's paper, the entire content of which is incorporated herein by reference.

0200Although an example of the present invention has been described above in relation to a wideband CDMA network having an asynchronous packet mode, it will be appreciated that the present invention can also be applied to any other networks in which a scheduling problem arises. These networks could be, or could be adapted from, other CDMA networks, such as an IS95 network. These networks could also be or be adapted from other mobile communication networks not using CDMA, for example networks using one or more of the following multiple-access techniques: time-division multiple access (TDMA), wavelength-division multiple access (WDMA), frequency-division multiple access (FDMA) and space-division multiple access (SDMA).

0201Although embodiments of the present invention have been described as having distinct "units", those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functions of the base station (Node-B) and/or user equipment in embodiments of the present invention.