WO2017191360A1

WO2017191360A1 - Utilisation of uplink allocation

Info

Publication number: WO2017191360A1
Application number: PCT/FI2017/050321
Authority: WO
Inventors: Suresh Kalyanasundaram; Klaus Ingemann Pedersen; Sheshachalam B S
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2016-05-02
Filing date: 2017-04-28
Publication date: 2017-11-09
Anticipated expiration: 2018-11-02

Abstract

In one aspect, this specification describes a method comprising determining a number of resource blocks required to transmit data stored in a transmission buffer of user equipment and, if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, utilising the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and leaving a remaining number of the allocated number of resource blocks unused.

Description

Utilisation of Uplink Allocation Field

This specification relates to the utilisation of an uplink allocation by user equipment.

Background

One of the aims with future E-UTRA (Advanced LTE) networks is to achieve ultra-reliable low-latency communications (URLLC) with over-the-air latencies of l millisecond or less. Even for applications which do not demand such low-latency requirements, for instance traditional mobile broadband (MBB) applications, it is in general beneficial to achieve low-latency in order to provide a better end-user experience.

One way in which low latencies may be achieved is the allocation of a number of resource blocks to one or more user equipments (UEs) that is larger than the UE is expected to require. This process may be referred to as "over-dimensioning".

Summary

In a first aspect, this specification describes a method comprising determining a number of resource blocks required to transmit data stored in a transmission buffer of user equipment and, if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, utilising the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and leaving a remaining number of the allocated number of resource blocks unused.

The method may comprise providing signalling data to indicate to the eNodeB the number of resource blocks of the allocated number of resource blocks that have been utilised for transmission of the data in the transmission buffer. The method may additionally or alternatively comprise providing signalling data to indicate to the eNodeB whether the entire number of resource blocks allocated to the user equipment have been utilised for the transmission of the data in the transmission buffer. The signalling data may be independently decodable relative to the data transmitted in the resource blocks.

The method may comprise reading data from the buffer into the required number of resource blocks in a pre-defined order. The pre-defined order may be upwards from a lowest-numbered allocated resource block or downwards from a highest-numbered allocated resource block. Alternatively, the pre-defined order may start from a middle resource block of the allocated resource blocks. In such examples, the pre-defined order may be alternately, either side of the middle resource block. The pre-defined order may be indicated to the user equipment via a message received from the eNodeB. The message may be an uplink scheduling grant.

The method may comprise determining which resource blocks of the allocated resource blocks to utilise for the transmission of the data so as to optimise frequency-selective scheduling gains. In a second aspect, this specification describes a method comprising prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, determining whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.

The method may comprise determining whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised by performing blind detection on an uplink channel during the transmission time interval to determine a number of resource blocks utilised for transmission of the transport block. The method may further comprise performing blind detection on the uplink channel during the transmission time interval to determine the number and an identity of the resource blocks utilised by the user equipment. The method may alternatively or additionally comprise performing blind detection on the uplink channel during the transmission time interval based on a minimum number of resource blocks which the user equipment is expected to utilise. The method may comprise performing blind detection on the uplink channel during the transmission time interval based on the minimum number of resource blocks which the user equipment is expected to utilise and a pre-defined order in which the user equipment is required to utilise the allocated resource blocks. The method may comprise determining whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised based on independently decodable signalling data.

The method may comprise indicating to the user equipment an order in which the user equipment is required to utilise the allocated resource blocks. The order may be selected from two or more available options. The method may alternatively or additionally comprise determining the order thereby to maximise a transport block size required by the user equipment or to minimise a number of resource blocks required by the user equipment.

In a third aspect, this specification describes apparatus configured to perform a method according to either of the first and second aspects.

In a fourth aspect, this specification describes computer-readable instructions, which when executed by computing apparatus, cause the computing apparatus to perform a method according to either of the first and second aspects.

In a fifth aspect, this specification describes apparatus comprising at least one processor, and at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus: to determine a number of resource blocks required to transmit data stored in a transmission buffer of user equipment; and if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, to utilise the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and to leave a remaining number of the allocated number of resource blocks unused.

The computer program code, when executed by the at least one processor, may cause the apparatus to provide signalling data to indicate to the eNodeB the number of resource blocks of the allocated number of resource blocks that have been utilised for transmission of the data in the transmission buffer.

The computer program code, when executed by the at least one processor, may cause the apparatus to provide signalling data to indicate to the eNodeB whether the entire number of resource blocks allocated to the user equipment have been utilised for the transmission of the data in the transmission buffer.

The signalling data may be independently decodable relative to the data transmitted in the resource blocks.

The computer program code, when executed by the at least one processor, may cause the apparatus to read data from the buffer into the required number of resource blocks in a pre-defined order. The pre-defined order may be upwards from a lowest-numbered allocated resource block or downwards from a highest-numbered allocated resource block. Alternatively, the pre-defined order may start from a middle resource block of the allocated resource blocks. In such examples, the pre-defined order may be alternately, either side of the middle resource block. The pre-defined order may be indicated to the user equipment via a message, which may be an uplink scheduling grant, received from the eNodeB.

The computer program code, when executed by the at least one processor, may cause the apparatus to determine which resource blocks of the allocated resource blocks to utilise for the transmission of the data so as to optimise frequency-selective scheduling gains.

In a sixth aspect, this specification describes apparatus comprising at least one processor and at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus, prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, to determine whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.

The computer program code, when executed by the at least one processor, may cause the apparatus to determine whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised by performing blind detection on an uplink channel during the transmission time interval to determine a number of resource blocks utilised for transmission of the transport block. The computer program code, when executed by the at least one processor, may cause the apparatus to perform blind detection on the uplink channel during the transmission time interval to determine the number and an identity of the resource blocks utilised by the user equipment. The computer program code, when executed by the at least one processor, may cause the apparatus to perform blind detection on the uplink channel during the transmission time interval based on a minimum number of resource blocks which the user equipment is expected to utilise. The computer program code, when executed by the at least one processor, may cause the apparatus to perform blind detection on the uplink channel during the transmission time interval based on the minimum number of resource blocks which the user equipment is expected to utilise and a pre-defined order in which the user equipment is required to utilise the allocated resource blocks.

The computer program code, when executed by the at least one processor, may cause the apparatus to determine whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised based on independently decodable signalling data.

The computer program code, when executed by the at least one processor, may cause the apparatus to indicate to the user equipment an order in which the user equipment is required to utilise the allocated resource blocks. The computer program code, when executed by the at least one processor, may cause the apparatus to select the order from two or more available options.

The computer program code, when executed by the at least one processor, may cause the apparatus to determine the order thereby to maximise a transport block size required by the user equipment or to minimise a number of resource blocks required by the user equipment.

In a seventh aspect, this specification describes a computer-readable medium having computer-readable code stored thereon, the computer readable code, when executed by a least one processor, causing performance of at least: determining a number of resource blocks required to transmit data stored in a transmission buffer of user equipment; and if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, utilising the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and leaving a remaining number of the allocated number of resource blocks unused. The computer-readable code stored on the medium of the seventh aspect may further cause performance of any of the operations described with reference to the method of the first aspect.

In an eighth aspect, this specification describes a computer-readable medium having computer-readable code stored thereon, the computer readable code, when executed by a least one processor, causing performance of at least: prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, determining whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block. The computer-readable code stored on the medium of the eighth aspect may further cause performance of any of the operations described with reference to the method of the second aspect. In a ninth aspect, this specification describes apparatus comprising means for

determining a number of resource blocks required to transmit data stored in a

transmission buffer of user equipment; and if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, utilising the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and leaving a remaining number of the allocated number of resource blocks unused. The apparatus of the ninth aspect may further comprise means for causing performance of any of the operations described with reference to method of the first aspect.

In a tenth aspect, this specification describes means for, prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, determining whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block. The apparatus of the tenth aspect may further comprise means for causing performance of any of the operations described with reference to method of the second aspect. Brief Description of the Figures

For better understanding of the present application, reference will now be made by way of example to the accompanying drawings in which:

Figure 1 is an example of a mobile telecommunications radio access network including plural eNodeBs (eNBs) and one or more user equipments (UEs);

Figure 2 is a flow chart illustrating various operations which may be performed by a UE operating within the network of Figure 1;

Figure 3 is a flow chart illustrating various operations which may be performed by an eNB operating within the network of Figure 1;

Figure 4 is a schematic illustration of an example configuration of a UE which may be configured to perform various operations described with reference to Figures 1 and 2;

Figure 5 is a schematic illustration of an example configuration of an eNBs which may be configured to perform various operations described with reference to Figures 1 and 3;

Figure 6 is an illustration of a computer-readable medium upon which computer readable code may be stored; and

Figures 7 and 8 are flow charts illustrating various operations which may, according to some examples, be performed by a UE and an eNB respectively operating within a network such as that of Figure 1. Detailed Description

In the description and drawings, like reference numerals refer to like elements

throughout.

Various methods and apparatuses are described in detail below, by way of example only, in the context of a mobile telecommunications radio access network l, such as that illustrated in Figure l. The network l comprises one or more base stations or access points (eNodeBs, eNBs) 5-1 to 5-n (generally referred to by numeral 5). Only a small number of eNBs 5 are shown in FIG. 1, but a radio access network may typically comprise thousands of eNBs 5. Together, the eNBs 5 may provide radio coverage to one or more user equipment (UE) 4-1 to 4-n (generally referred to by numeral 4) over a wide geographical area. Each eNB 5 operates one or more cells, which are denoted in Figure 1, for illustrative purposes only, by the dashed circles 6-1 to 6-n or sectors thereof (generally referred to using numeral 6). Although most of the coverage areas of the cells are shown illustratively as circles in Figure 1, in reality, the coverage area of each cell depends on the transmission power and the directionality of the antenna (or antennas) by which the cell is operated. The coverage area of each cell may also depend on obstacles (such as buildings) which are in the vicinity of the eNB 5, carrier frequency and channel propagation characteristics etc.

The configuration of the coverage area of the cells 6 may be selected so as to serve UEs 4 in a particular area while not providing coverage to other areas. For instance, the

configuration of a coverage area of a cell may be selected so as to provide coverage for an area in which users are commonly present while not providing coverage for areas in which users are seldom present. For instance, in Figure 1, the first cell 6-1 operated by the first cell is depicted as only a sector of a circle. In one extreme example, an eNB 5 may be configured to provide coverage (via a cell) up and down a road but not either side of the road.

As mentioned above, a single eNB 5 may, in some examples, provide two or more cells. For instance, a first cell 6 may be provided in a first direction from the eNB 5 while a second cell 6 may be provided in a different direction. In Figure 1, this is illustrated by the second eNB 5-1 which is shown as operating two different cells 6-2A and 6-2B. The mobile telecommunications radio access network l may be, but is certainly not limited to, an Evolved Universal Terrestrial Radio Access (E-UTRA) network, which may sometimes be referred to as LTE Advanced network. The eNBs 4 and UEs 4 in the network 1 may be configured to communicate with one another using an OFDM -based access scheme, such as orthogonal frequency division multiple access (OFDMA) and/or single carrier frequency division multiple access (SC-FDMA). For instance, in some non- limiting examples OFDMA may be used for downlink communications whereas SC-FDMA may be used for uplink communications. One or more of the UEs 4 may be configured for bi-directional communication with one or more of the eNBs 5. In such examples, the transmission of data from the eNB 5 to the UE 4 may be referred to as "downlink". Transmission of data from the UE 4 to the eNB 5 may be referred to as "uplink". The eNBs 5, or some other entity within the network 1, may be operable to schedule uplink timeslots (transmission time intervals) for the UEs 4 within the cell 6 operated by the eNBs 5. Scheduling information including the scheduled time slot and a number of physical resource blocks (PRBs), or simply resource blocks, allocated for the UE 4 is then communicated to the UE 4, for instance by the eNB 5 operating the cell. The scheduling information may be transmitted as a message which may be referred to as an uplink scheduling grant.

As can be seen in Figure 4, the UE 4 comprises control apparatus 40 which is configured to control operation of other components forming part of the UE 4 thereby to enable transmission of data, via uplink, to the eNBs 5 as well as receipt of data from the eNBs 5, via downlink. The control apparatus 40 may additionally be configured to cause performance of any other operations described herein with reference to the UEs 4, for instance with reference to Figure 2. Example configurations of the control apparatus 40 and the UE 4 as a whole are discussed in more detail later in relation to Figure 4.

Similarly, as illustrated in Figure 5, the eNBs 5 may comprise control apparatus 50 for enabling bi-directional communication with one or more UEs 4, including transmission of scheduling information. The control apparatus 50 may additionally be configured to cause performance of any other operations described herein with reference to the eNBs 5, for instance with reference to Figure 3. Example configurations of the control apparatus 50 and the eNB 5 as a whole are discussed in more detail later in relation to Figure 5.

When allocating a number of resource blocks for an uplink transmission by a particular UE 4, the scheduling entity may take into account messages which are sent by the UE 4 to the serving eNB 5 and which indicate the amount of data that is currently present in the transmission buffer of the UE. These messages may be referred to as buffer status reports (BSRs). They may be sent periodically or in response to the occurrence of an event, for instance a particular condition being met. The transmit buffer may form part of a memory 402 (in Figure 4, it is denoted by 402-1B) of the control apparatus 40 or may form part of the transceiver circuitry405-2.

As will be appreciated, serving eNBs 5 may be configured, in some instances, to allocate resource blocks to a UE 4 even in the absence of a scheduling request or buffer status report being received from the UE. This may occur, for instance but not exclusively when, when the UE has particular (e.g. ultra-reliable low latency communication (URLLC)) requirements.

In some instances, the eNBs 5, or other scheduling entity, may be configured to allocate more resource blocks for a particular UE 4 than are expected or estimated to be required by the UE 4 (for instance, based on the buffer status report received from that UE 4). This may be referred to as a pro-active grant. A pro-active grant may enable the UE 4 to transmit more data than was indicated in the buffer status report (for instance when additional data arrives in the transmission buffer of the UE 4 after having sent a buffer status report but before performing an uplink transmission) without first having to send a new buffer status report including updated information. This may serve to reduce the latency within the network.

Instances in which additional resource blocks may be allocated to a UE 4 include, for example, situations in which all resource blocks in a particular shared transmission time interval would not be used if each UE 4 sharing the interval was allocated only based on their expected number of resource blocks. In determining which UEs should be granted an increased allocation of resource blocks, the eNB control apparatus 50 or other scheduling entity may take into account (or use) previous information relating to, for instance, the data arrival patterns from the different UEs and/or the quality of service (QoS) of the default bearer setups at the different UEs etc. By taking such information into account, the eNB control apparatus 50 is able to allocate the additional resource blocks to those UEs 4 that are more likely to require and/or make best use of them. Other situations in which additional resource blocks may be allocated to a UE 4 may include, for example those in which certain UEs 4 in a particular cell 7 have default bearer setups with ultra-reliable low latency communication (URLLC) requirements. In such cases, those UEs 4 may be allocated an additional number of resource blocks even if the expected resource block requirements of all the UEs in the cell account for all the resource blocks in a particular transmission time interval. The allocation of additional resource blocks to UEs having URLLC requirements may enable those UEs to achieve those requirements. In such instances, other UEs 4 in the cell may be allocated fewer resource blocks than indicated as being required by their buffer status reports.

As mentioned previously, information regarding the number of resource blocks allocated for an uplink transmission by a UE 4 in a particular transmission time interval may be transmitted to the UE 4 as scheduling information. After receiving the scheduling information, the UE 4 may respond by transmitting data to the serving eNB 5 at the scheduled time. In this regard, the UE control apparatus 40 may be configured to determine a number of resource blocks that are required to transmit the data stored in the UEs transmission buffer. If the required number of resource blocks is less than the number of resource blocks that have been allocated to the UE for the uplink transmission, the UE control apparatus 40 is configured to utilise the required number of resource blocks for the transmission, from the UE 4 to the eNB 5, of the data in the transmission buffer and to leave a remaining (non-zero) number of the allocated number of resource blocks unused. Put another way, the UE control apparatus 40 could be said to utilise only the required number of resource blocks of the allocated number of resource blocks to transmit the data stored in the transmission buffer. In some examples, no resource blocks (zero resource blocks) may be required by the UE. In such examples, no (zero) resource blocks may be used to transmit data and so all of the allocated resource blocks may be left unused.

Resource blocks being "left unused" may, in this context, be understood to mean that no signal is transmitted by the UE 4 during one or more portions of the transmission time interval allocated for the "unused" resource blocks. Leaving the resource blocks unused may contrast with padding the resource blocks, for instance with zeros or a padding buffer status report (a padding BSR), and then transmitting them to the eNB 5. By leaving allocated resource blocks unused when they are not required, the benefits of pro-active grants (e.g. reduced latency) may be obtained when the increased allocation is required, while reducing the amount of inter-cell interference due to transmission of padding data. Inter-cell interference may degrade performance in neighbouring cells, and so by reducing it, performance of the overall network 1 may be improved. The "used" resource blocks, which include the data from the transmission buffer, may be passed as a transport block to the UE's PHY layer for transmission to the eNB 5 as a data packet. The PHY layer may add CRC data as well a transmission header thereby to form the data packet. The UE may be configured such that no data packet is sent when the number of resource blocks required by the UE is equal to zero.

As a consequence of the UE control apparatus 40 being operable to leave allocated resource blocks unused, the eNB control apparatus 50 may be configured to determine, upon receipt of the data packet from the UE 4 at the eNB 5 and prior to decoding the transport block of the data packet, whether all resource blocks of the number of resource blocks allocated to the UE for uplink transmission during a transmission time interval have been utilised. By determining whether or not all allocated resource blocks have been used, the eNB 5 is able to avoid the need to attempt to decode data for the "unused" resource blocks, if applicable.

The determination as to whether all resource blocks of the number of resource blocks allocated to the UE 4 for uplink transmission during a transmission time interval have been utilised may be performed using blind detection on the relevant uplink channel, e.g. the physical shared uplink channel (PUSCH), during the transmission time interval allocated for the UE 4. An example of a suitable form of blind detection may be energy detection on the relevant resource blocks. Blind detection may be similar to discontinuous transmission (DTX) detection. In the current advanced LTE standard, this process is already applied by eNBs 5 to determine whether or not physical downlink control channel (PDCCH) uplink grant transmissions were received by the relevant UE. Specifically, the eNB 5 performs energy detection in the allocated PUSCH during the allocated

transmission time interval. As such, the use of blind detection to determine whether all resource blocks of the number of resource blocks allocated to the UE 4 for uplink transmission during a transmission time interval have been utilised does not place a significant additional burden on the eNB 5.

The performance of blind detection on the uplink channel during the transmission time interval may enable the eNB 5 to determine the number and/or an identity of the resource blocks utilised by the UE 4. Put another way, it may enable the determination as to how many and/or which of the allocated resource blocks are unused by the UE.

The blind detection may be performed during the allocated transmission time interval based on a minimum number of resource blocks N_mi_n which the UE 4 is expected to utilise. This may be determined by the eNB 5 based on, for instance, one or more of the most recent buffer status report received from the UE 4, the number of bits transmitted by the UE 4 in previous uplink transmissions since the transmission of the buffer status report by the UE, and the allocated MCS for the UL transmission.

In some examples, the blind detection during the transmission time interval may be performed based on the minimum number of resource blocks which the UE 4 is expected to utilise and a pre-defined order in which the UE 4 is required to make use of the allocated resource blocks (or, put another way, a pre-defined order in which the UE 4 is required to read data from the buffer into the resource blocks). For instance, the UE 4 may be configured to utilise the resource blocks as required from the lowest numbered resource block upwards or from the highest numbered resource block downwards. In other examples, the UE 4 may be preconfigured to start utilising the resource blocks from the middle block of the allocation and filling them with data from the transmission buffer alternately either side of the middle resource block.

If the eNB 5 knows the minimum number of resource blocks that the UE 4 is expected to use as well as the order in which the resource blocks are to be filled with data, the duration or number of instances for which blind detection needs to be performed in order to determine which resource blocks have been utilised can be reduced. For instance, if the resource blocks are utilised sequentially from either end, the eNB 5 may simply perform blind detection in respect of resource blocks between N_mi_n and the allocated number of resource blocks Naiiocated and may not need to perform blind detection in respect of the resource blocks lower than N_mi_n. For instance, if Naiiocated is equal to 11 and N_mi_n is equal to 6, the worst-case blind detection may be performed in respect of only the seventh to eleventh resource blocks (five in total). It will therefore be understood that the worst-case number of resource blocks for which blind detection may be performed when the blocks are used sequentially from one end of the allocation may be expressed generally as Naiiocated

The eNB 5 may be configured to take an average of signal energy over all resource blocks in excess of the minimum expected number of resource blocks N_mi_n in order to determine which resource blocks have been used by the UE 4. For instance, continuing with the example in which N_mi_n is equal to 6, the eNB may take an average signal energy of:

resource blocks 7 to 11, resource blocks 8 to 11, resource blocks 9 to 11, resource blocks 10 to 11, and resource block 11 alone. These average signal energies may then be used to determine which resource blocks the UE has used. In some examples, the eNB 5 may be configured to instruct the UE 4 as to the pre-defined order in which the UE 4 is required to make use of the allocated resource blocks. For instance, this may be indicated along with the scheduling information, e.g. in the uplink scheduling grant. The eNB 5 may be configured to select the order from a plurality of available pre-defined orders (e.g., left-to-right, right-to-left, from the middle alternately outwards). An indexing system for the available pre-defined orders which is known to both the eNB 5 and UE 4 may be utilised thereby to indicate the order in which the UE 4 is required to use the allocated resource blocks.

The selection of the order by the eNB 5 may be made so as to improve efficiency and/or performance of the network. For instance, the UE 4 may be configured to transmit reference signals, which may be similar to Sounding Reference Signals (SRS), based on which the eNB 5 may perform per-resource block interference measurements. Or put another way, the eNB 5 may be able to determine the interference at times corresponding to the transmission times of each resource block. Based on this determined interference, the eNB 5 may select the pre-defined order which would result in the best performance, for instance, use of a maximum transport block size (TBS) or a minimum number of resource blocks to transmit the data in the UE's transmission buffer. In order to minimise the signalling overhead, the pre-defined order may only be signalled to the UE 4 in the event that the eNB 5 has allocated more than the minimum number of resource blocks (e.g. has provided a proactive UL grant). Similarly, the eNB 5 may be configured to perform blind detection only in the event that the eNB 5 has allocated more than the minimum number of resource blocks to the UE. In this way, the use of additional computational resources required to perform the blind detection may be avoided unless it is necessary.

In some examples, the UE 4 may be configured to transmit signalling data that is decodable separately from the used resource blocks, thereby to indicate to the eNB 5 whether all allocated resource blocks have been used. This separately decodable signalling data may be provided, for example, in the transmission header.

In some examples, the separately decodable signalling data may take the form of a flag, for instance a single bit flag (i.e. "1" or "o") which indicates whether or not all allocated resource blocks have been utilised. Alternatively or additionally, the signalling data may include information allowing the eNB 5 to determine which resource blocks (i.e. the identities) have been used. For instance, the signalling data may indicate how many resource blocks of the allocation have been used. This, taken in combination with a known pre-defined order of use of the resource blocks, allows the eNB 5 to determine which resource blocks are used and which are unused. In other examples, the UE 4 may be configured to explicitly indicate which resource blocks are used and/or have been left unused.

As will be appreciated, the use of signalling data as described above may obviate the need for the eNB 5 to perform blind detection. As described above, the order and/or identity of which resource blocks of an allocation to use may be determined and indicated to the UE 4 by the eNB 5. In other examples, however, the UE 4 may be configured to determine the order autonomously. For instance, the UE 4 may select the resource blocks to use (e.g. from lowest upwards, from highest downwards or from the middle alternatively either side) so as to obtain the largest frequency-selective scheduling gains. For instance, the resource blocks of the allocation may be selected by the UE so as to minimize the number of resource blocks used. In some examples, the ability of the UE 4 to determine autonomously which resource blocks to use may depend on how much information regarding channel conditions is available to the UE 4-

In general, the UE 4may be unable to change the modulation and coding scheme (MCS) indicated by the eNB 5 in an uplink scheduling grant. In other examples, however, the UE 4 may be configured to select, if appropriate, an MCS that is different to that indicated by the eNodeB. The MCS selected by the UE may then be signalled to the eNB by the UE 4 as part of the separately decodable signalling data. This signalling data may then be decoded and utilised by eNB 5 when decoding the data carried by the utilised number of the allocated resource blocks.

The MCS allocated by the eNB 5 may have been selected on the basis of the over- dimensioned number of resource blocks, for instance in addition to a measured SINR for the UE. However, when a UE 4 does not require all the resource blocks that it has been allocated, the MCS selected by the eNB 5 may no longer be the most suitable. As such, the UE 4 may be configured to select an MCS which is more suitable. For instance, in some examples, the UE 4 may select the highest possible MCS and lowest number of resource blocks. Alternately, the UE 4 may select the lowest possible MCS to meet a target block error rate (BLER) while still using all the allocated resource blocks. The MCS selected by the UE may typically be less than or equal to the MCS indicated by the eNB, but may be selected such that all the bits in the UE's transmission buffer fit within the number of allocated resource blocks. The UE 4 may thus be configured to use the lowest MCS which allows all the data in the transmission buffer to be transmitted within the allocated number of resource blocks.

Examples in which the UE 4 selects an MCS that is different to that indicated by the eNB 5 are discussed in more detail with reference to Figures 7 and 8.

Figure 2 is a flow chart illustrating various operations which may be performed by a UE 4 operating within the network of Figure 1. As will be appreciated, some or all of the operations illustrated in Figure 2 may correspond with or relate to operations described above with reference to Figure 1.

In operation S2.1, the UE control apparatus 40 determines the amount of data that is awaiting transmission in the UE transmission buffer. This amount of data is indicative of the minimum number of resource blocks N_mi_n) that are expected to be required in the UE's next uplink transmission. As will be appreciated, in some examples, there may be no data for transmission and so the expected number of resource blocks may be zero. In operation S2.2, the UE control apparatus 40 may cause transmission of a message, which may be referred to as a buffer status report (BSR), which includes information indicative of the amount of data that is awaiting transmission in the UE transmission buffer (which is indicative of N_mi_n). This message may be a MAC control element, for instance an LTE MAC control element similar to LTE BSRs. As will be appreciated, BSRs may be sent intermittently, for instance periodically or in response to the occurrence of certain events. As such, multiple uplink transmissions may be performed by the UE 4 between instances of transmitting a buffer status report.

In operation S2.3, the UE control apparatus 40 receives the uplink scheduling

information, for instance in the form of an uplink scheduling grant from the serving eNB 5-

The scheduling information includes information indicative of the allocated number of resource blocks (N_aiiocated). It may also include an indication of the transmission time interval (TTI) for the allocated uplink transmission slot. The scheduling information may further include an indication of the modulation and coding scheme (MCS) that should be used by the UE 4. In operation S2.4, the UE control apparatus 40, determines whether the allocated number of resource blocks is greater than the number of resource blocks required to transmit the data stored in the transmission buffer.

In response to a negative determination in operation S2.4 (i.e. a determination that the number of resource blocks allocated is less than or equal to the number of resource blocks required to transport the data in the buffer), the UE control apparatus 40 may proceed to operation S2.5 in which data from the transmission buffer is transferred into all of the allocated resource blocks.

In response to a positive determination in operation S2.4 (i.e. a determination that the number of resource blocks allocated is greater than the number of resource blocks required to transport the data in the buffer), the UE control apparatus 40 may proceed to operation S2.6.

In operation S2.6, the UE control apparatus 40 may determine an order in which to fill the required ones of the allocated resource blocks. As discussed above, this may be defined by the eNB 5 and indicated to the UE 4, for instance as part of the scheduling information. In other examples, the UE control apparatus 40 may determine the order autonomously, for instance to optimise performance. In other examples, the UE 4 may be pre-configured to read data into the resource blocks in a single pre-defined order. In such, examples, operation S2.6 may be omitted.

Subsequent to operation S2.6 or, if operation S2.6 is not performed, subsequent to a positive determination in operation S2.4, operation S2.7 may be performed. In operation S2.7, the UE 4 transfers data from the transmission buffer into the required number of resource blocks. This may be performed in the order determined in operation S2.6 or an order which the UE 4 is preconfigured to use. Having transferred all the data in transmission buffer into the required resource blocks, the remainder of the allocated resource blocks are left unused.

Subsequent to either of operations S2.5 and S2.7, in operation S2.8, a header and CRC information are added to the transport block created in operation S2.5 or operation S2.7 thereby to form a data packet. In some examples, the header may include the

independently decodable signalling data, which may indicate one or more of: whether all allocated resource blocks have been used, how many resource blocks have been used, which resource blocks have been used, an order in which resource blocks have been used, and the coding and modulation scheme that has been used by the UE. After formation of the data packet, in operation S2.9, the data packet is caused to be transmitted to the eNB 5. During transmission of a data packet which includes unused resource blocks, the signal energy may drop to zero (or some other relatively low value) in the frequencies corresponding to the unused resource blocks. Although not shown in Figure 2, after transmission of the data packet, the UE control apparatus 40 may return to operation S2.1. As mentioned previously, the transmission of a buffer status report may not be performed between each uplink transmission. As such, in some iterations, operation S2.2 may be omitted from the flow of operations depicted in Figure 2.

Figure 3 is a flow chart illustrating various operations which may be performed by an eNB 5 operating within the network of Figure 1. As will be appreciated, some or all of the operations illustrated in Figure 3 may correspond with or otherwise relate to operations described above with reference to Figure 1.

In operation S3.1, the eNB 50 may receive a message from a one of the UEs 4 it is currently serving. The message, which may be referred to as a buffer status report (BSR), includes information indicative of the amount of data that is awaiting transmission in the UE transmission buffer (which is indicative of N_mi_n). This message may be a MAC control element, for instance an LTE MAC control element similar to an LTE BSR.

In operation S3.2, the eNB control apparatus 50 (or other scheduling entity) may determine whether to grant the UE 5 more uplink resource blocks that are indicated as being required by the received message, N_mi_n. In other examples, for instance when a BSR is not received from the UE 4 between each allocated uplink transmission, the eNB may make an estimation of N_mi_n using one or more of: information in a previously-received BSR, an amount of data that is scheduled to be transmitted by the UE and the estimated SINR for the UE (which may be determined based on "acks" and "nacks" passed between the UE and the eNB).

As discussed above, additional resource blocks may be allocated to a UE if, for example, all resource blocks in a particular shared transmission time interval would not be used if each UE sharing the interval was allocated only based on their expected number of resource blocks Nmin. In determining which UEs should be granted an increased allocation of resource blocks (Naiiocated > Nmin), the eNB control apparatus 50 may take into account (or use) previous information relating to, for instance, the data arrival patterns from the different UEs and/or the quality of service (QoS) of the default bearer setups at the different UEs etc. By taking such information into account, the eNB control apparatus 50 is able to allocate the additional resource blocks to those UEs 4 that are more likely to require and/or make best use of them. In other examples, certain UEs in a particular cell may have default bearer setups with ultra-reliable low latency communication (URLLC) requirements. In such cases, the eNB control apparatus 50 may allocate an additional number of resource blocks to a particular UE even if the eNB 5 could allocate all of the resource blocks of the cell in the particular transmission time interval, based solely on the expected/ estimated resource block requirements N_mm of each of the UEs 4 in the cell. The allocation of additional resource blocks to UEs 4 having URLLC requirements may enable those UEs 4 to achieve those requirements.

If, in operation S3.2, it is decided not to grant additional resource blocks to the UE 4, the eNB control apparatus 50 may proceed to operation S3.3. In operation S3.3, the eNB control apparatus 50 causes transmission to the UE 4 of scheduling information (which may be an uplink scheduling grant) which indicates an allocated number of resource blocks, Naiiocated, that is less than or equal to the number of resource blocks that is expected to be required, Nmm. The scheduling information may additionally include information indicative of the transmission time interval as well as the modulation and coding scheme that is to be used by the UE 4 during the uplink.

If, in operation S3.2, it is decided that additional resource blocks are to be granted to the UE 4, the control apparatus 50 may proceed to operation S3.4. In operation S3.4, the eNB control apparatus 50 may, in some examples, determine an order in which the UE 4 should make use of the allocated resource blocks. As discussed above with reference to Figure 1, the order may be determined so as to maximise performance of the system.

In operation S3.5, the eNB control apparatus 50 causes transmission to the UE 4 of scheduling information (which may be an uplink scheduling grant) which indicates an allocated number of resource blocks, Naiiocated, that is greater than the number of resource blocks that is expected to be required, Nmm. If the determination of operation S3.4 was performed, the scheduling information may additionally include an indication of the order in which the UE 4 is required to use the allocated resource blocks. The scheduling information may additionally include information indicative of the transmission time interval as well as the modulation and coding scheme that is to be used by the UE 4 during the uplink.

Subsequent to operation S3.5, the eNB 5 in operation S3.6 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S3.5. Similarly, subsequent to operation S3.3, the eNB 5 in operation S3.7 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S3.3.

Subsequent to operation S3.6, the eNB control apparatus 50 may proceed to operation S3.8 in which blind detection may be performed in respect of the received packet, thereby to enable the eNB 5 to determine which of the allocated resource blocks have been utilised by the UE 5. Alternatively, the eNB control apparatus 50 may decode, separately from the transport block of the data packet, signalling information which indicates among other things whether all of the allocated resource blocks have been utilised and/or which of the allocated resource blocks have been utilised. As discussed previously, the signalling data may be included in the header of the received data packet.

Subsequently, based on the blind detection/signalling information, the eNB control apparatus 50 may determine, in operation S3.9, whether the entire allocation of resource blocks has been utilised. If it is determined that all of the resource blocks have been utilised, the eNB control apparatus 50 may proceed to operation S3.11 in which the data received during all of the resources allocated resource blocks is decoded.

If, however, it is determined in operation S3.9 that not all of the allocated resource blocks have been used (i.e. that some have been left unused), the eNB control apparatus 50 may proceed to operation S3.10 in which the resource blocks which have been used are identified. This may be performed on the basis of the blind detection or the signalling data, in conjunction with knowledge of an order in which the UE 4 has used the resource blocks of the allocation. As discussed above with respect to Figure 1, the order in which the resource blocks are used may, in some examples, be selected autonomously by the UE 4 and indicated to the eNB 5 in the separately decodable signalling information. Finally, in operation S3.11, the eNB control apparatus 50 may decode only the data received during the intervals corresponding to the used resource blocks.

Returning now to operation S3.7, because no additional resource blocks were allocated to the UE 4 in operations S3.2 and S3.3, subsequent to operation S3.7, operations S3.8 to S3.10 (including performing blind detection and or decoding of separately decodable signalling data) may not be performed, as such operations may not be necessary. Instead, after operation S3.7, the eNB control apparatus 50 may proceed directly to operation S3.11 in which data received during intervals corresponding to all resource blocks is decoded.

Various operations which may be performed by a UE 4, which is operable to determine an alternative modulation and coding scheme (MCS) to that specified by its serving eNB, will now be described with reference to Figure 7. In operation S7.1, the UE control apparatus 40 determines the amount of data that is awaiting transmission in the UE transmission buffer. As will be appreciated, this amount of data (which may be zero) is indicative of the minimum number of resource blocks that are expected to be required in the UE's next uplink transmission. In operation S7.2, the UE control apparatus 40 may cause transmission of a buffer status report (BSR), which includes information indicative of the amount of data that is awaiting transmission in the UE transmission buffer (which is indicative of N_mi_n). This message may be a MAC control element, for instance an LTE MAC control element similar to LTE BSRs. As discussed previously, for instance respect to Figure 2, BSRs may be sent intermittently, for instance periodically or in response to the occurrence of certain events. As such, multiple uplink transmissions may be performed by the UE 4 between instances of transmitting a buffer status report.

In operation S7.3, the UE control apparatus 40 receives the uplink scheduling

information, for instance in the form of an uplink scheduling grant from the serving eNB 5. The scheduling information includes information indicative of the allocated number of resource blocks (N_aiiocated). It also includes an indication of the modulation and coding scheme (MCS), for instance in the form of an MCS index. It may also include an indication of the transmission time interval (TTI) for the allocated uplink transmission slot. In operation S7.4, the UE control apparatus 40, determines whether the allocated number of resource blocks is greater than the number of resource blocks required by the data stored in the transmission buffer. In response to a negative determination in operation S2.4 (i.e. a determination that the allocated number of resource blocks is not larger than the number of resource blocks required for the data in the buffer), the UE control apparatus 40 may proceed to operation S7.5 in which data from the transmission buffer is transferred into all of the allocated resource blocks in accordance with the indicated MCS. Subsequently, in operation S7.8, a header and CRC data are added to the transport block including the allocated resource blocks, thereby to form a data packet which is caused to be transmitted in operation S7.9.

In response to a positive determination in operation S7.4 (i.e. a determination that the allocated number of resource blocks is greater than the required number of resource blocks), the UE control apparatus 40 may proceed to operation S7.6. In operation S7.6, the UE control apparatus 40 may select a modulation and coding scheme that is different to that indicated by the eNB.

One reason for selection of a different MCS is that because the UE does not need to make use of all allocated resource blocks, the MCS indicated by the eNB (which was selected on the basis of the over-dimensioned number of resource blocks) may no longer be the most appropriate. In some examples, when determining the different MCS, the UE 4 may select the highest possible MCS and lowest number of resource blocks. Alternately, the UE 4 may select the lowest possible MCS to meet lower target block error rate (BLER) while still using all the resource blocks allocated by the eNB in the uplink scheduling grant. The

MCS selected by the UE may be to be equal to or lower than that indicated by the eNB, but may be selected such that all the bits in the UE's transmission buffer would fit within the number of allocated resource blocks. According to some examples, the UE 4 may be configured to use the lowest MCS which allows all the data in the transmission buffer to be transmitted within the number of resource blocks allocated by the eNB 5.

Once the different MCS has been determined, the UE, in operation S7.7 reads the data from its buffer into the resource blocks in accordance with the determined MCS. Subsequently, in operation S7.8, a header and CRC information are added to the transport block created in operation S7.7 thereby to form a data packet. The header may include the independently decodable signalling data, which indicates (for instance using an MCS index) the coding and modulation scheme that has been used by the UE 4.

After formation of the data packet, in operation S7.9, the data packet is caused to be transmitted to the eNB 5. Although not shown in Figure 7, after transmission of the data packet, the UE control apparatus 40 may return to operation S7.1. However, as mentioned previously, the transmission of a buffer status report may not be performed between each uplink transmission. As such, in some iterations, operation S7.2 may be omitted from the flow.

Figure 8 is a flow chart illustrating various operations which may be performed by an eNB within a network such as that of Figure 1 in examples in which the UE is operable to determine an alternative modulation and coding scheme (MCS) to that specified by the eNB.

In operation S8.1, the eNB 50 may receive a message from one of the UEs 4 that it is currently serving. The message, which may be referred to as a buffer status report (BSR), includes information indicative of the amount of data that is awaiting transmission in the UE transmission buffer (which is indicative of N_mi_n). This message may be a MAC control element, for instance an LTE MAC control element similar to an LTE BSR. Operation S8.1 may be substantially the same as operation S3.1 and similarly to operation S3.1 may, in some examples, be omitted.

In operation S8.2, the eNB control apparatus 50 (or other scheduling entity) may determine whether to grant the UE 5 more uplink resource blocks that are indicated as being required by the received message, N_mi_n. In other examples, for instance when a BSR is not received from the UE 4 between each allocated uplink transmission, the eNB may make an estimate of N_mi_n using one or more of: information in a previously-received BSR, an amount of data that is scheduled to be transmitted by the UE and the estimated SINR for the UE, which may be determined based on "acks" and "nacks" passed between the UE and the eNB.

Operation S8.2 may be substantially the same as operation S3.2 described with reference to Figure 3. However, in addition to determining whether to over-provision resource blocks for a particular UE, the eNB controller (or other scheduling entity) may

additionally determine an appropriate MCS. This may be determined, for instance, based on the allocated number of resource blocks and the SINR for that UE. If a positive determination is reached (i.e. it is decided to allocate more resource blocks than are expected to be required), the eNB control apparatus 50 may in operation S8.3 cause transmission of an uplink scheduling grant which indicates the allocated number of resource blocks such that N_aiiocated> N_mi_n. The uplink scheduling grant also indicates the MCS to be used by the UE 4 for its uplink transmission. The uplink scheduling grant may additionally indicate the TTI to be used by the UE 4.

If a negative determination is reached in operation S8.2 (i.e. it is decided to allocate a number of resource blocks which is less than or equal to a number that are expected to be required), the eNB control apparatus 50 may in operation S8.4 cause transmission of an uplink scheduling grant which indicates the allocated number of resource blocks such that Naiiocated≤ N_mi_n. The uplink scheduling grant also indicates the MCS to be used by the UE for its uplink transmission. The uplink scheduling grant may additionally indicate the TTI to be used by the UE 4.

Subsequent to operation S8.3, the eNB 5 in operation S8.5 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S8.3. Similarly, subsequent to operation S8.4, the eNB 5 in operation S8.9 receives an uplink transmission of a data packet from the UE 4 to which the scheduling information was sent in operation S8.4.

Subsequent to operation S8.5, the eNB control apparatus 50 may proceed to operation S8.6 in which the eNB control apparatus 50 decodes, separately from the transport block of the data packet, the separately decodable signalling information. The signalling information may indicate whether the UE has utilised an MCS which is different to that indicated by the eNB in the uplink grant. The indication as to whether the UE has utilised a different UE may include a simple flag (e.g. 1 or o, yes or no) and/or may indicate the MCS (e.g. via an MCS index) which has been used by the UE 4.

If based on the signalling information, it is determined that a different MCS has been used by the UE 4, the eNB controller may (in operation S8.8) decode the resource blocks of the received data packets on the basis of the new MCS utilised by the UE 4. If, on the other hand, a negative determination is reached in operation S8.7 (put another wat, it is determined that the MCS specified by eNB has been used by the UE), operation S8.10 is performed in which the resource blocks are decoded in accordance with the MCS originally specified by the eNB in the uplink grant.

Returning now to operation S8.9 in which the data packet is received, the eNB control apparatus may subsequently proceed directly to operation S8.10 in which the resource blocks are decoded in accordance with the MCS originally specified by the eNB. The decoding of signalling data, similarly to operation S8.6 may be omitted (as may operation S.7). This is because, as the eNB has not allocated additional resource blocks to the UE 4, it can be confident that the MCS specified in the uplink grant has been used by the UE.

Figure 4 is a schematic illustration of an example configuration of one or more of the UEs 4 depicted in Figure 1, which may be used for communicating with the eNBs 5 via a wireless interface. The UE 4 may be any device capable of at least sending or receiving radio signals to or from the eNBs 5 and of performing operations as described above with respect to Figures 1, 23, 7 and 8.

The UE 4 may communicate via an appropriate radio interface arrangement 405 of the UE 4. The interface arrangement 405 may be provided for example by means of a radio part 405-2 (e.g. a transceiver) and an associated antenna arrangement 405-1. The antenna arrangement 405-1 may be arranged internally or externally to the UE 4.

As discussed above, the UE 4 comprises control apparatus 40 which is operable to control the other components of the UE 4 in addition to performing any suitable combinations of the operations described in connection with UE 4 with reference to Figures 1, 2 and 3 (where applicable). The control apparatus 40 may comprise processing apparatus 401 and memory 402. Computer-readable code 402-2A may be stored on the memory, which when executed by the processing apparatus 401, causes the control apparatus 40 to perform any of the operations described herein in relation to the UE 4. Also, as discussed previously, the memory may include a transmission buffer 402-1B.

Example configurations of the memory 402 and processing apparatus 401 will be discussed in more detail below

The UE 4 may be, for example, a device that does not need human interaction, such as an entity that is involved in Machine Type Communications (MTC). Alternatively, the UE 4 may be a device designed for tasks involving human interaction such as making and receiving phone calls between users, and streaming multimedia or providing other digital content to a user. Non-limiting examples include a smart phone, and a laptop

computer/notebook computer/tablet computer/e-reader device provided with a wireless interface facility. Where the UE 4 is a device designed for human interaction, the user may control the operation of the UE 4 by means of a suitable user input interface UII 404 such as key pad, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 403, a speaker and a microphone may also be provided. Furthermore, the UE 4 may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.

Figure 5 is a schematic illustration of an example configuration of one or more the eNBs 5 depicted in Figure 1, which may be used for communicating with the UEs 4 via a wireless interface. The eNB 5, which may be referred to a base station or access point (AP) comprises a radio frequency antenna array 501 configured to receive and transmit radio frequency signals. Although the eNB 5 in Figure 5 is shown as having an array 501 of four antennas, this is illustrative only. The number of antennas may vary, for instance, from one to many hundreds. The eNB 5 further comprises radio frequency interface circuitry 503 configured to interface the radio frequency signals received and transmitted by the antenna 501 and a control apparatus 50. The radio frequency interface circuitry 503 may also be known as a transceiver. The apparatus 50 may also comprise an interface 509 via which, for example, it can communicate (e.g. via X2 messages) with other network elements such as the other eNBs 5.

The eNB control apparatus 50 may be configured to process signals from the radio frequency interface circuitry 503, control the radio frequency interface circuitry 503 to generate suitable RF signals to communicate information to the UEs 4 via the wireless communications link, and also to exchange information with other network elements 5 via the interface 509. .

The control apparatus 50 may comprise processing apparatus 502 and memory 504. Computer-readable code 504-2A may be stored on the memory 504, which when executed by the processing apparatus 502, causes the control apparatus 50 to perform any of the operations assigned to the eNBs 5 and described with reference to any of Figures 1 to 5, 7 and 8 As should of course be appreciated, the apparatuses 4, 5 shown in each of FIGS. 4 and 5 described above may comprise further elements which are not directly involved with processes and operations in respect which this application is focussed.

Some further details of components and features of the above-described

apparatus/entities/apparatuses 4, 5, 40, 50 and alternatives for them will now be described. The control apparatuses 40, 50 may comprise processing apparatus 401, 502

communicatively coupled with memory 402, 504. The memory 402, 504 has computer readable instructions 402-2A, 504-2A stored thereon, which when executed by the processing apparatus 401, 502 causes the control apparatus 40, 50 to cause performance of various ones of the operations described with reference to Figures 1 to 5. The control apparatus 40, 50 may in some instance be referred to, in general terms, as "apparatus".

The processing apparatus 401, 502 may be of any suitable composition and may include one or more processors 401A, 502A of any suitable type or suitable combination of types. For example, the processing apparatus 401, 502 may be a programmable processor that interprets computer program instructions 402-2A, 504-2A and processes data. The processing apparatus 401, 502 may include plural programmable processors.

Alternatively, the processing apparatus 401, 502 may be, for example, programmable hardware with embedded firmware. The processing apparatus 401, 502 may be termed processing means. The processing apparatus 401, 502 may alternatively or additionally include one or more Application Specific Integrated Circuits (ASICs). In some instances, processing apparatus 401, 502 may be referred to as computing apparatus.

The processing apparatus 401, 502 is coupled to the memory (which may be referred to as one or more storage devices) 402, 504 and is operable to read/write data to/from the memory 402, 504. The memory 402, 504 may comprise a single memory unit or a plurality of memory units, upon which the computer readable instructions (or code) 402- 2A, 504-2A is stored. For example, the memory 402, 504 may comprise both volatile memory 402-1 and non-volatile memory 402-2. For example, the computer readable instructions/program code 402-2A, 504-2A may be stored in the non-volatile memory 402-2, 504-2 and may be executed by the processing apparatus 401, 502 using the volatile memory 402-1, 504-1 for temporary storage of data or data and instructions. In some examples, the transmission buffer 402-1B of the UE 4 may be constituted by volatile memory 402-1 of the UE control apparatus 40. Examples of volatile memory include RAM, DRAM, and SDRAM etc. Examples of non-volatile memory include ROM, PROM, EEPROM, flash memory, optical storage, magnetic storage, etc. The memories in general may be referred to as non-transitory computer readable memory media.

The term 'memory', in addition to covering memory comprising both non-volatile memory and volatile memory, may also cover one or more volatile memories only, one or more non-volatile memories only, or one or more volatile memories and one or more nonvolatile memories.

The computer readable instructions/program code 402-2A, 504-2A may be preprogrammed into the control apparatus 20. Alternatively, the computer readable instructions 402-2A, 504-2A may arrive at the control apparatus 40, 50 via an

electromagnetic carrier signal or may be copied from a physical entity 60 such as a computer program product, a memory device or a record medium such as a CD-ROM or DVD an example of which is illustrated in Figure 6. The computer readable instructions 402-2A, 504-2A may provide the logic and routines that enables the entities

devices/apparatuses 4, 5, 40, soto perform the functionality described above. The combination of computer-readable instructions stored on memory (of any of the types described above) may be referred to as a computer program product.

Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and/or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "memory" or "computer-readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

Reference to, where relevant, "computer-readable storage medium", "computer program product", "tangibly embodied computer program" etc., or a "processor" or "processing apparatus" etc. should be understood to encompass not only computers having differing architectures such as single/multi-processor architectures and sequencers/parallel architectures, but also specialised circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices and other devices. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device as instructions for a processor or configured or configuration settings for a fixed function device, gate array, programmable logic device, etc.

If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above- described functions may be optional or may be combined. Similarly, it will also be appreciated that flow diagrams of Figures 2 and 3 are examples only and that various operations depicted therein may be omitted, reordered and or combined.

Although the method and apparatus have been described in connection with an E-UTRA network, it will be appreciated that they are not limited to such networks and are applicable to radio networks of various different types.

Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.

It is also noted herein that while the above describes various examples, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

1. A method comprising:

determining a number of resource blocks required to transmit data stored in a transmission buffer of user equipment;

if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a

transmission time interval, utilising the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and leaving a remaining number of the allocated number of resource blocks unused.

2. The method of claim 1, comprising:

providing signalling data to indicate to the eNodeB the number of resource blocks of the allocated number of resource blocks that have been utilised for transmission of the data in the transmission buffer.

3. The method of claim 1, comprising:

providing signalling data to indicate to the eNodeB whether the entire number of resource blocks allocated to the user equipment have been utilised for the transmission of the data in the transmission buffer.

4. The method of claim 2 or claim 3 wherein the signalling data is independently decodable relative to the data transmitted in the resource blocks.

5. The method of any of claims 1 to 4, comprising:

reading data from the buffer into the required number of resource blocks in a predefined order.

6. The method of claim 5, wherein the pre-defined order is upwards from a lowest- numbered allocated resource block or downwards from a highest-numbered allocated resource block.

7. The method of claim 5, wherein the pre-defined order starts from a middle resource block of the allocated resource blocks.

8. The method of claim 7, wherein the pre-defined order is alternately, either side of the middle resource block.

The method of any of claims 4 to 8, wherein the pre-defined order is indicated to user equipment via a message received from the eNodeB.

10. The method of claim 9, wherein the message is an uplink scheduling grant.

11. The method of any of claims 1 to 4, comprising:

determining which resource blocks of the allocated resource blocks to utilise for the transmission of the data so as to optimise frequency-selective scheduling gains.

12. A method comprising:

prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, determining whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.

13. The method of claim 12, comprising determining whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised by performing blind detection on an uplink channel during the transmission time interval to determine a number of resource blocks utilised for transmission of the transport block.

14. The method of claim 13, comprising performing blind detection on the uplink channel during the transmission time interval to determine the number and an identity of the resource blocks utilised by the user equipment.

15. The method of either of claims 13 and 14, comprising performing blind detection on the uplink channel during the transmission time interval based on a minimum number of resource blocks which the user equipment is expected to utilise.

16. The method of claim 15 comprising performing blind detection on the uplink channel during the transmission time interval based on the minimum number of resource blocks which the user equipment is expected to utilise and a pre-defined order in which the user equipment is required to utilise the allocated resource blocks.

17. The method of claim 12, comprising determining whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised based on independently decodable signalling data.

18. The method of any of claims 12 to 17, comprising:

indicating to the user equipment an order in which the user equipment is required to utilise the allocated resource blocks.

19. The method of claim 18, comprising:

the eNodeB selecting the order from two or more available options.

20. The method of claim 18 or 19, comprising determining the order thereby to maximise a transport block size required by the user equipment or to minimise a number of resource blocks required by the user equipment.

21. Apparatus configured to perform a method according to any of claims 1 to 20.

22. Computer-readable instructions which, when executed by computing apparatus, cause the computing apparatus to perform a method according to any of claims 1 to 20.

23. Apparatus comprising:

at least one processor; and

at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus:

to determine a number of resource blocks required to transmit data stored in a transmission buffer of user equipment; and

if the required number of resource blocks is less than a number of resource blocks that have been allocated to the user equipment for an uplink transmission in a transmission time interval, to utilise the required number of resource blocks for transmission from the user equipment to an eNodeB of the data in the transmission buffer and to leave a remaining number of the allocated number of resource blocks unused.

24. The apparatus of claim 23, wherein the computer program code, when executed by the at least one processor, causes the apparatus to provide signalling data to indicate to the eNodeB the number of resource blocks of the allocated number of resource blocks that have been utilised for transmission of the data in the transmission buffer.

25. The apparatus of claim 23, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

provide signalling data to indicate to the eNodeB whether the entire number of resource blocks allocated to the user equipment have been utilised for the transmission of the data in the transmission buffer.

26. The apparatus of claim 24 or claim 25 wherein the signalling data is independently decodable relative to the data transmitted in the resource blocks.

27. The apparatus of any of claims 23 to 26, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

read data from the buffer into the required number of resource blocks in a predefined order.

28. The apparatus of claim 27, wherein the pre-defined order is upwards from a lowest-numbered allocated resource block or downwards from a highest-numbered allocated resource block.

29. The apparatus of claim 27, wherein the pre-defined order starts from a middle resource block of the allocated resource blocks.

30. The apparatus of claim 29, wherein the pre-defined order is alternately, either side of the middle resource block.

31. The apparatus of any of claims 27 to 30, wherein the pre-defined order is indicated to the user equipment via a message received from the eNodeB.

32. The apparatus of claim 31, wherein the message is an uplink scheduling grant.

33. The apparatus of any of claims 23 to 26, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

determine which resource blocks of the allocated resource blocks to utilise for the transmission of the data so as to optimise frequency-selective scheduling gains.

34. Apparatus comprising:

at least one processor; and at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus:

prior to decoding data in a transport block of a packet transmitted during a transmission time interval by user equipment to an eNodeB, to determine whether all resource blocks of a number of resource blocks allocated to the user equipment for uplink transmission during the transmission time interval have been utilised for transmission of the transport block.

35. The apparatus of claim 34, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

determine whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised by performing blind detection on an uplink channel during the transmission time interval to determine a number of resource blocks utilised for transmission of the transport block.

36. The apparatus of claim 35, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

perform blind detection on the uplink channel during the transmission time interval to determine the number and an identity of the resource blocks utilised by the user equipment.

37. The apparatus of either of claims 35 and 36, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

perform blind detection on the uplink channel during the transmission time interval based on a minimum number of resource blocks which the user equipment is expected to utilise.

38. The apparatus of claim 37 wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

perform blind detection on the uplink channel during the transmission time interval based on the minimum number of resource blocks which the user equipment is expected to utilise and a pre-defined order in which the user equipment is required to utilise the allocated resource blocks.

39· The apparatus of claim 34, wherein the computer program code, when executed by the at least one processor, causes the apparatus to: determine whether all resource blocks of the number of resource blocks allocated to the user equipment have been utilised based on independently decodable signalling data.

40. The apparatus of any of claims 34 to 39, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

indicate to the user equipment an order in which the user equipment is required to utilise the allocated resource blocks.

41. The apparatus of claim 40, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

select the pre-defined order from two or more available options.

42. The apparatus of claim 40 or 41, wherein the computer program code, when executed by the at least one processor, causes the apparatus to:

determine the order thereby to maximise a transport block size required by the user equipment or to minimise a number of resource blocks required by the user equipment.

43. A computer-readable medium having computer-readable code stored thereon, the computer readable code, when executed by a least one processor, causing performance of at least:

determining a number of resource blocks required to transmit data stored in a transmission buffer of user equipment; and

44. A computer-readable medium having computer-readable code stored thereon, the computer readable code, when executed by a least one processor, causing performance of at least: