Resource assignment for single and multiple cluster transmission
Abstract
A transmission apparatus comprising: a generator that, in the operation, generates downlink control information that includes a resource allocation field to signal resource allocation information indicating resources allocated to a partner device, wherein when a plurality of groupings are attributed to the partner apparatus and a number of available bits in the resource allocation field is less than a number of bits necessary to indicate the plurality of allocated groupings, the generator, in operation, allocates a portion of the necessary bits to indicate the plurality of groupings attributed to the available bits in the resource allocation field and assumes that the remaining bit or bits of the necessary bits to indicate that the plurality of attributed groupings is a defined value , and in which when the number of available bits in the resource allocation field is equal to or greater than the number of bits necessary to indicate the plurality of allocated pools, the generator, in the operation, assigns the necessary bits to indicate the plurality of groupings attributed to the available bits in the resource allocation field; and a transmitter that, in operation, transmits the downlink control information generated.

Term
5.5 yearsto projected expiry
Projected expiry 8 March 2032, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
16 claims: 2 independent, 14 dependent
- 1ES 2 697 347 T3 ES 2 697 347 T3 CLAIMS REIVINDICACIONES 1. A transmission apparatus comprising:1. Un aparato de transmisión que comprende: a generator that, in operation, generates downlink control information including a resource allocation field for signaling resource allocation information indicating resources allocated to un generador que, en la operación, genera información de control de enlace descendente que incluye un campo de atribución de recursos para señalizar información de atribución de recursos que indica recursos asignados a 5 a talker apparatus, wherein when a plurality of pools are allocated to the talker apparatus and a number of available bits in the resource allocation field is less than a number of bits necessary to indicate the plurality of allocated pools, the generator , in the operation, allocates a portion of the bits necessary to indicate the plurality of groupings allocated to the bits available in the resource allocation field 5 un aparato de interlocutor, en el que cuando una pluralidad de agrupaciones se atribuyen al aparato de interlocutor y un número de bits disponibles en el campo de atribución de recursos es menor que un número de bits necesarios para indicar la pluralidad de agrupaciones atribuidas, el generador, en la operación, asigna una porción de los bits necesarios para indicar la pluralidad de agrupaciones atribuidas a los bits disponibles en el campo de atribución de recursos 10 and assumes that the remaining bit or bits of the bits necessary to indicate that the plurality of allocated groupings is a defined value, and wherein when the number of available bits in the resource allocation field is equal to or greater than the number of bits necessary to indicate the plurality of groupings allocated, the generator, in the operation, allocates the bits necessary to indicate the plurality of groupings allocated to the bits available in the field 10 y supone que el bit o los bits restantes de los bits necesarios para indicar que la pluralidad de agrupaciones atribuidas es un valor definido, y en el que cuando el número de bits disponibles en el campo de atribución de recursos es igual o mayor que el número de bits necesarios para indicar la pluralidad de agrupaciones atribuidas, el generador, en la operación, asigna los bits necesarios para indicar la pluralidad de agrupaciones atribuidas a los bits disponibles en el campo 15 de atribución de recursos;y un transmisor que, en la operación, transmite la información de control de enlace descendente generada. fifteen resource allocation;and a transmitter that, in operation, transmits the generated downlink control information.
- 9A transmission procedure comprising:9. Un procedimiento de transmisión que comprende: generar información de control de enlace descendente que incluye un campo de atribución de recursos para 40 señalizar información de atribución de recursos que indica recursos asignados a un aparato de interlocutor, en el que cuando una pluralidad de agrupaciones se asignan al aparato de interlocutor y un número de bits disponibles en el campo de atribución de recursos es menor que un número de bits necesarios para indicar la pluralidad de agrupaciones atribuidas, la generación incluye asignar una porción de los bits necesarios para indicar la pluralidad de agrupaciones atribuidas a los bits disponibles en el campo de atribución de recursos y generating downlink control information including a resource allocation field for signaling resource allocation information indicating resources allocated to a peer apparatus, wherein when a plurality of groupings are assigned to the peer apparatus and a number available bits in the resource allocation field is less than a number of bits necessary to indicate the plurality of allocated groupings, the generation includes allocating a portion of the bits necessary to indicate the plurality of groupings allocated to the available bits in the resource allocation field and 45 suponer que el bit o bits restantes de los bits necesarios para indicar la pluralidad de agrupaciones atribuidas son un valor definido, y en el que el número de bits disponibles en el campo de atribución de recursos es igual o mayor que el número de bits necesarios para indicar la pluralidad de agrupaciones atribuidas, la generación incluye asignar los bits necesarios para indicar la pluralidad de agrupaciones atribuidas a los bits disponibles en el campo de atribución Four. Five assume that the remaining bit or bits of the bits required to indicate the plurality of allocated groupings are a defined value, and wherein the number of bits available in the resource allocation field is equal to or greater than the number of bits required to indicate the plurality of allocated groupings, the generation includes assigning the necessary bits to indicate the plurality of allocated groupings to the available bits in the allocation field 50 de recursos;y transmitir la información de control de enlace descendente generada. fifty of resources;and transmitting the generated downlink control information.
Independent claims2
428 paragraphs in 17 sections, as filed
ES 2 697 347 T3
DESCRIPTION
Resource allocation for single and multiple pool transmission
Field of the invention
The present invention relates generally to signaling resource allocation information to a terminal of a mobile communication system to allocate resources to the terminal. In particular, the invention relates to resource allocation signaling using downlink control information for single pool and multi pool allocations in 3GPP LTE or 3GPP LTE-A. More specifically, one aspect of the invention provides a concept for signaling resource allocation information for cases where the number of available bits in the downlink control information is insufficient to represent all possible resource allocations that are supported by the system. For example, all allowed combinations of single pool and multiple pool attributions. In principle, the disclosed invention can be applied to signaling uplink resource allocation information and downlink resource allocation information, while achieving additional advantages over a certain configuration of uplink resource allocations in 3GPP LTE. or 3GPP LTE-A.
Technical background of the invention
In mobile communication systems, a base station allocates downlink resources to a terminal, which the base station can use for downlink transmissions to said terminal, and / or allocates uplink resources to a terminal, which said terminal can use. for uplink transmissions. The allocation (or allocation) of downlink and / or uplink resources is signaled from the base station (or other related network device) to the terminal. Downlink and / or uplink resource allocation information is typically signaled as part of downlink control information having multiple predefined flags and / or predefined fields, one of which being a specialized field for signaling the resource attribution information.
Typically, the number of available bits that can be used to signal resource allocation information to terminals is predetermined by a technical specification. For example, the technical specification defines the size and format of the downlink control information in which the resource allocation information is transmitted to the terminals.
Similarly, resource allocations or the size of resource allocations are predetermined by a technical specification. Furthermore, the allocation of the uplink or downlink resources to the terminals is usually defined and provided by a technical specification. For example, uplink resources can be expressed as resource blocks, which means that the granularity in which a user or terminal can allocate uplink resources is the number and position of the assignable uplink resource blocks. In this case, the technical specification usually defines the allowed combinations of resource blocks that are supported by the mobile communication system. Since the allowed resource allocations, the size of the resource allocations, or the supported combinations of assignable resources are defined or predetermined, the number of bits required to indicate the entire (or combinations of) resource or resource is efficiently provided. supported resources.
Therefore, neither the number of available bits that can be used to signal the resource allocation information nor the number of bits required to indicate the (or combinations of) supported resource (s) can be freely chosen.
The present invention has recognized that situations may occur where the number of bits that is available to signal resource allocation information is insufficient to represent all possible resource allocations that are supported by the communication system.
The general concepts of the invention are described below with respect to 3GPP LTE and LTE-A communication systems and particularly for multiple cluster allocations specified in 3GPP LTE (-A). However, it is to be understood that the reference to 3GPP LTE and LTE-A is only an example in accordance with specific embodiments of the invention, but the general concepts of the invention may be applied to different resource allocation procedures of different communication systems. communication.
The disclosed embodiments of the invention for signaling uplink resource information to a terminal can be applied to signaling downlink resource information without departing from the invention. For example, downlink resources according to LTE (-A) are allocated by the scheduler as resource blocks (RB) as the smallest possible unit of resources. The downlink component carrier (or cell) is subdivided in the time-frequency domain into sub-frames, each divided into two downlink slots to signal control channel region symbols (PDCCH region) and OFDM. As such, the resource grid as illustrated in Figure 3 for uplink resources in LTE (-A) has the same structure for downlink resources. Therefore, signaling downlink resources allocated with fewer bits than what would be required to express
ES 2 697 347 T3 all allowed resource block allocations that are supported by the communication system can be achieved in the same way as suggested herein with respect to downlink resources.
Furthermore, the terms resource allocation and resource allocation are used in this specification to both indicate the same technical meaning of allocating or allocating resources.
Both expressions are therefore interchangeable without any change in content and technical meaning.
Long-term evolution (LTE)
Third generation (3G) mobile systems based on WCDMA radio access technology are deployed on a large scale around the world. A first stage in improving or evolving this technology involves introducing High Speed Packet Downlink Access (HSDPA) and an enhanced uplink, also referred to as High Speed Packet Uplink Access (HSUPA), which provides a radio access technology that is highly competitive.
To be prepared for a greater increase in user demands and to be competitive in the face of new radio access technologies, the 3GPP introduced a mobile communication system called Long Term Evolution (LTE). LTE is designed to meet the carrier needs for high-speed data and multimedia transport, as well as high-capacity voice support for the next decade. The ability to provide high bit rates is a primary measure for LTE.
The Long Term Evolution (LTE) Working Paper (WI) specification called UMTS Terrestrial Radio Access Evolved (UTRA) and UMTS Terrestrial Radio Access Network (UTRAN) was finalized as Version 8 (LTE) . The LTE system represents efficient packet-based radio access and radio access networks that provide comprehensive IP-based functionalities with low latency and low cost. According to LTE, multiple scalable transmission bandwidths such as 1.4, 3.0, 5.0, 10.0, 15.0 and 20.0 MHz are specified to achieve flexible system deployment using a spectrum dice. On the downlink, radio access based on Orthogonal Frequency Division Multiplexing (OFDM) was adopted due to its intrinsic immunity to multipath interference (MPI) produced by a low symbol rate, the use of a cyclic prefix (CP) , and its affinity to different transmission bandwidth arrangements. Radio access based on Single Carrier Frequency Division Multiple Access (SC-FDMA) was adopted in the uplink, since the provision of wide area coverage was prioritized over the improvement in the peak data rate considering the restricted transmit power of user equipment (UE). Many major packet radio access techniques are employed including multiple input multiple output (MIMO) channel transmission techniques, and a highly efficient control signaling structure is achieved in LTE (eg Version 8).
LTE architecture
The global architecture of a communication system according to LTE (-A) is shown in Figure 1. A more detailed representation of the E-UTRAN architecture is provided in Figure 2.
The E-UTRAN comprises an eNodeB that provides the E-UTRA user plane (PDCP / RLC / MAC / PHY) and control plane protocol (RRC) terminations towards the user equipment (UE). The eNodeB (eNB) houses the Physical (PHY), Media Access Control (MAC), Radio Link Control (RLC) and Packet Data Control Protocol (PDCP) layers that include compression functionality of headers and user plane encryption. It also offers Radio Resource Control (RRC) functionality that corresponds to the control plane. Performs many functions including radio resource management, admission control, scheduling, negotiated uplink Quality of Service (QoS) application, cell information broadcast, user plane data encryption / decryption and control and compression / downlink / uplink user plane packet header decompression. The eNodeBs are interconnected with each other through the X2 interface.
The eNodeBs are additionally connected via the S1 interface to the EPC (Evolved Packet Core). More specifically, the eNodeBs are connected to the MME (Mobility Management Entity) through S1-MME and to the Server Gateway (SGW) through S1-U. The S1 interface supports a many-to-many relationship between MME / Server Gateways and eNodeBs. The SGW routes and forwards user data packets, while also acting as the mobility anchor for the user plane during inter-eNodeB handovers and as the anchor for mobility between LTE and other 3GPP technologies (terminating the S4 interface and relaying traffic between 2G / 3G and PDN gW systems). For user equipment in the idle state, the SGW terminates the downlink data path and activates paging when downlink data arrives for the user equipment. Manages and stores user equipment contexts, eg IP bearer service parameters, internal network routing information. It also replicates user traffic in the event of legal interception.
ES 2 697 347 T3
The MME is the primary control node for the LTE access network. It is responsible for the procedure of tracing and radio searching for user equipment in standby mode which includes retransmissions. She is involved in the carrier up / down procedure and is also responsible for choosing the SGW for a user equipment at the initial connection time and at the intra-LTE handover time that involves the relocation of the Main Network node ( CN). It is responsible for authenticating the user (interacting with the HSS). Signaling of No Access Stratum (ÑAS) ends at the MME and is also responsible for the generation and attribution of temporary Identities to user equipment. Checks the authorization of the user equipment to camp on the service provider's Public Land Mobile Network (PLMN) and enforces the user equipment internment restrictions. The MME is the termination point in the network for encryption / integrity protection for NAA signaling and supports primary security management. Lawful interception of signaling is also supported by the MME. The MME also provides the control plane function for mobility between LTE and 2G / 3G access networks with the S3 Interface terminating at the MME from the SGSN. The MME also terminates the S6a Interface to the home HSS for overseas user equipment.
Component carrier structure in LTE
The downlink component carrier of a 3GPP LTE (such as Version 8) is subdivided in the time-frequency domain into so-called sub-frames. In 3GPP LTE each sub-frame is divided into two downlink slots as illustrated in Figure 3, in which the first downlink slot comprises the control channel rung (PDCCH rung) in the first symbols of OFDM. Each subframe consists of a given number of OFDM symbols in the time domain (12 or 14 OFDM symbols in 3GPP LTE Version 8), with each of the OFDM symbols spanning the entire bandwidth of the component carrier. Therefore, each OFDM symbol consists of a number of modulation symbols
JV<sup>DL</sup> he/<sup>rb</sup> transmitted in respective <sup>2V</sup>rb <sup>aj</sup>'sc subcarriers as also shown in Figure 4.
Assuming a multi-carrier communication system, for example, employing OFDM, as used for example in 3GPP Long Term Evolution (LTE), the smallest unit of resources that can be allocated by the
DL scheduler is a resource block. A physical resource block is defined as OFDM symbols / v symbols<sup>RB</sup> consecutive in the time domain and '' sc consecutive subcarriers in the frequency domain as illustrated in Figure 4. In 3GPP LTE (such as Version 8), a downlink physical resource block x / v<sup>RB</sup> therefore consists of <sup>simb x</sup> resource elements, which correspond to an Interval in the time domain and 180 kHz in the frequency domain. Additional details on the downlink resource grid can be obtained, for example, from 3GPP TS 36.211, Evolved Universal Terrestrial Radio Access (E-UTRA); Physlcal Channels and Modulatlon (Release 8), version 8.9.0 or 9.0.0, section 6.2, available at http://www.3gpp.org. Similarly, the sub-frame structure in a downlink component carrier and the downlink resource grid illustrated in Figures 3 and 4 are derived from 3GPP TS 36,211.
For LTE uplink resource allocation, the resource block structure is comparable to the previous downlink resource grid structure. For uplink resources, each OFDM symbol consists of a number of modulation symbols transmitted in respective
TO(<sup>UL</sup>x2V<sup>RB</sup>
RB SC <sub>its</sub>b carriers as also shown in Figure 5. The exemplary uplink resource grid structure illustrated in Figure 5 corresponds to the exemplary downlink resource grid structure illustrated in Figure 4. The uplink resource grid structure The exemplary uplink resources in Figure 4 is derived from the 3GPP document TS 36.211 V10.0.0, which provides additional details of uplink resources in LTE (Version 10).
L1 / L2 control signaling - downlink control information in LTE (-A)
To inform a planned user or terminal about its allocation status, transport format, and other data-related information (e.g. HARQ information), L1 / L2 control signaling (Layer1 / Layer2) is transmitted on the downlink along with the data. The L1 / L2 control signaling is multiplexed with the downlink data in a sub-frame, assuming that the user allocation can change from sub-frame to sub-frame. It should be noted that user allocation can also be performed on a TTI (Transmission Time Interval) basis, where the TTI length is a multiple of the sub-frames. The TTI length can be set in a service area for all users, it can be different for different users, or it can even be dynamic for each user. In general, L1 / 2 control signaling only needs to be transmitted once per TTI. L1 / L2 control signaling is transmitted on the Physical Downlink Control Channel (PDCCH). It should be noted that in 3GPP LTE, the assignments for uplink data transmissions, also referred to as uplink scheduling grants or uplink resource assignments, are also transmitted on the PDCCH.
ES 2 697 347 T3
In general, Information sent in L1 / L2 control signaling (particularly LTE (-A) Version 10) can be categorized into the following elements:
User identity, indicating the user who is assigned. This is normally included in the checksum by masking the CRC with the user identity;
Resource attribution information, which indicates the resources (Resource Blocks, RB) in which a user is attributed. Note that the number of BRs in which a user is allocated can be dynamic;
Carrier indicator, which is used if a control channel transmitted on a first carrier allocates resources that refer to a second carrier, that is, resources on a second carrier or resources related to a second carrier;
Modulation and coding scheme that determines the modulation scheme and the coding rate used;
HARQ information, such as a new data indicator (NDI) and / or a redundancy version (RV) that is particularly useful in retransmissions of data packets or parts thereof;
Power control commands for adjusting the transmission power of the assigned uplink data or transmission of control information;
Reference signal information such as applied cyclic offset and / or orthogonal cover code index, to be used for transmission or reception of assignment related reference signals;
Uplink or downlink assignment index that is used to identify an order of assignments, which is particularly useful in TDD systems;
Hopping information, eg an indication of whether and how to apply hopping resources to increase frequency diversity;
CQI Request, which is used to trigger the transmission of channel status information on an allocated resource; and
Multiple pool information, which is a flag used to indicate and control whether the transmission takes place in a single pool (contiguous set of RBs) or in multiple pools (at least two non-contiguous sets of contiguous RBs). Multiple pool attribution has been introduced using 3GPP LTE- (A) Version 10.
It is to be noted that the above enumeration is not exhaustive, and that not all the mentioned information elements need to be present in every PDCCH transmission depending on the DCI format that is used.
DCI takes place in several formats that differ in their overall size and the field information that is used. The different DCI formats that are currently being defined for LTE (-A) Version 10 are described in detail in document TS 36.212 v10.0.0 in section 5.3.3.1, available at http://www.3gpp.org.
The following two specific DCI formats defined in LTE exemplarily illustrate some of the functionality of the various DCI formats:
• The DCI 0 format is used for planning the PUSCH (Physical Uplink Shared Channel) using single antenna port transmissions in the uplink 1 or 2 transmission mode, • The DCI 4 format is used for planning the PUSCH (Physical Uplink Shared Channel) using closed-loop spatial multiplexing transmissions in uplink transmission mode 2.
Uplink transmission modes 1 and 2 are defined in TS 36.213 v10.0.1 in section 8.0, single antenna port is defined in section 8.0.1, and closed-loop spatial multiplexing is defined in section 8.0.2, which are available at http://www.3gpp.org.
There are several different ways how exactly to convey the aforementioned pieces of information. In addition, the L1 / L2 control information may also contain additional information or may omit some of the information, such as:
the HARQ procedure number may not be necessary in case of a synchronous HARQ protocol, as used, for example, in the uplink, control information related to spatial multiplexing may additionally be included, such as, for example, precoding, in control signaling, or
ES 2 697 347 T3 In case of spatial multiplexing transmission of multiple codewords, the
MCS and / or HARQ information for multiple code words.
For uplink resource assignments (for example, with respect to the Physical Uplink Shared Channel, PUSCH) signaled on the PDCCH (Physical Downlink Control Channel) in LTE, the L1 / L2 control information does not contain a HARQ procedure number, since a synchronous HARQ protocol is used for LTE uplink transmissions. The HARQ procedure to be used for an uplink transmission is determined and provided by the specified timing. Additionally, it is to be noted that the redundancy version information (RV) and the MCS information are coded together.
Downlink and uplink data transmissions in LTE (-A)
This section provides additional background on downlink and uplink data transmissions in accordance with the LTE (-A) technical specification that may be helpful in understanding the background, structure, and full usability of the embodiments of the invention discussed below. This section therefore provides only illustrative information with respect to background information, one skilled in the art in the field of the invention will consider this to be common knowledge.
Regarding downlink data transmission in LTE, the L1 / L2 control signaling is transmitted on a separate physical channel (PDCCH), along with the downlink packet data transmission. This L1 / L2 control signaling typically contains information about:
- The physical resource or resources on which the data is transmitted (for example, subcarriers or blocks of subcarriers in the case of OFDM, codes in the case of CDMA). This information allows the UE (receiver) to identify the resources on which the data is transmitted.
- When the user equipment is configured to have a Carrier Indication Field (CIF) in the L1 / L2 control signaling this information identifies the component carrier for which the specific control signaling information is intended. This enables assignments to be sent to one component carrier that are intended for another component carrier (cross carrier scheduling). This other cross-scheduling component carrier could for example be a component carrier without PDCCH, ie the cross-scheduling component carrier does not carry any L1 / L2 control signaling.
- The Transport Format, which is used for transmission. This can be the data transport block size (payload size, information bit size), the MCS (Modulation and Coding Scheme) level, the Spectral Efficiency, the coding rate, etc. This information (usually together with the resource allocation (for example, the number of resource blocks allocated to the user equipment)) enables the user equipment (receiver) to identify the bit size of the information, the modulation scheme and the code rate to initiate demodulation, rate mismatch, and decoding procedure. The modulation scheme can be explicitly signaled.
- Information about ARQ Hybrid (HARQ):
HARQ procedure number: allows the user equipment to identify the hybrid ARQ procedure to which the data is mapped.
Sequence number or new data indicator (NDI): allows the user equipment to identify whether the transmission is a new packet or a retransmitted packet. If flexible combining is implemented in the HARQ protocol, the sequence number or new data indicator together with the HARQ procedure number enables flexible combining of the transmissions for a PDU before decoding.
Redundancy and / or constellation version: indicates to the user equipment, which version of hybrid ARQ redundancy is used (required for speed mismatch) and / or which version of modulation constellation is used (required for demodulation).
- UE Identity (UE ID): indicates for which user equipment the L1 / L2 control signaling is intended. In typical implementations this information is used to mask the L1 / L2 control signaling CRC to prevent other user equipment from reading this information.
To enable uplink packet data transmission in LTE, L1 / L2 control signaling is transmitted on the downlink (PDCCH) to indicate the user equipment about the details of the transmission. This L1 / L2 control signaling typically contains information about:
- The physical resource (s) on which the user equipment should transmit the data (eg subcarriers or blocks of subcarriers in the case of OFDM, codes in the case of CDMA).
ES 2 697 347 T3
- When the user equipment is configured to have a Carrier Indication Field (CIF) in the L1 / L2 control signaling this information identifies the component carrier for which the specific control signaling information is intended. This enables assignments to be sent on one component carrier that are intended for another component carrier. This other cross-scheduling component carrier may for example be a component carrier without PDCCH, ie the cross-scheduling component carrier does not carry any L1 / L2 control signaling.
- L1 / L2 control signaling for uplink grants is sent on the DL component carrier that joins the uplink component carrier or on one of several DL component carriers, if multiple DL component carriers DL component bind to the same UL component carrier.
- The Transport Format, which the user equipment should use for transmission. This can be the data transport block size (payload size, information bit size), the MCS level (Modulation and Coding Scheme), the Spectral Efficiency, the coding rate, etc. This information (usually together with the resource allocation (for example, the number of resource blocks allocated to the user equipment)) enables the user equipment (transmitter) to collect the information bit size, modulation scheme and rate. encoding to initiate modulation, rate adaptation, and encoding procedure. In some cases the modulation scheme can be explicitly signaled.
- Hybrid ARQ information:
HARQ procedure number: indicates to the user equipment from which hybrid ARQ procedure it should get the data.
Sequence number or new data indicator: Instructs the user equipment to transmit a new packet or to retransmit a packet. If flexible combining is implemented in the HARQ protocol, the sequence number or new data indicator together with the HARQ procedure number enables flexible combining of transmissions for a protocol data unit (PDU) before decoding .
Constellation and / or redundancy version: indicates to the user equipment, which hybrid ARQ redundancy version to use (required for rate adaptation) and / or which modulation constellation version to use (required for modulation).
- UE Identity (UE ID): indicates which user equipment should transmit data. In typical implementations this information is used to mask the L1 / L2 control signaling CRC to prevent other user equipment from reading this information.
There are several different ways available how to accurately transmit the aforementioned pieces of information in uplink and downlink data transmission in LTE. Furthermore, in uplink and downlink, the L1 / L2 control information may also contain additional information or it may omit some of the information. For example:
- The HARQ procedure number may not be required, ie not signaled, in case of a synchronous HARQ protocol.
- A redundancy and / or constellation version may not be necessary, and therefore not signaled, if Tracking Combination is used (always the same redundancy and / or constellation version) or if the sequence of the redundancy version and / or constellation are predefined.
- Power control information may additionally be included in the control signaling.
- MIMO-related control information, such as for example precoding, may additionally be included in the control signaling.
- In case of MIMO transmission transport format of multiple codewords and / or HARQ information for multiple codewords can be included.
For uplink resource assignments (on the Physical Uplink Shared Channel (PUSCH)) signaled on the PDCCH in LTE, the L1 / L2 control information does not contain a HARQ procedure number, since a protocol is employed of synchronous HARQ for LTE uplink. The HARq procedure to be used for an uplink transmission is provided by timing. Additionally it should be noted that the redundancy version information (RV) is coded together with the transport format information, that is, the RV information is embedded in the transport format (TF) field. The Transport Format (TF) respectively modulation and coding scheme (MCS) field has for example a size of 5 bits, which corresponds to 32 entries. 3 TF / MCS table entries are reserved to indicate redundancy versions (RV) 1, 2, or 3. The remaining
ES 2 697 347 T3 MCS table are used to signal the level of MCS (TBS) that Implicitly Indicates RVO. The size of the CRC field of the PDCCH is 16 bits.
For downlink assignments (PDSCH) signaled on the PDCCH in LTE the Redundancy Version (RV) is signaled separately in a two-bit field. Additionally the modulation order information is coded together with the transport format information. As in the uplink case there is a 5-bit MCS field signaled on the PDCCH. 3 of the inputs are reserved to signal an explicit modulation order, which does not provide transport format information (transport block). For the remaining 29 inputs, the modulation order and the transport block size information are signaled. Resource allocation fields for uplink resource allocations
According to 3GPP TS 36.212 vIO.OO, DCI 0 formats can be used, for example, for uplink resource allocations. DCI 0 formats contain - among others - a so-called Resource Block Allocation and Hop Resource Allocation field, which has a size of
<img file="ES2697347T3_D0001.tif" />
bits, where
UL
RB Indicates the number of resource blocks on the uplink.
LTE- (A) currently envisions three possible uplink resource allocation schemes, which are single pool allocation with no-hopping PUSCH (Physical Uplink Shared channel), single pool allocation with hop PUSCH, and multi-pool allocation. . Multiple pool attribution is Introduced in Version 10 and is supported only with non-hopping PUSCH.
In the case of a single pool allocation with no-hopping PUSCH, the entire resource block allocation and hop resource allocation field of the DCI is used to signal the resource allocation in the uplink sub-frame.
In the case of a single pool allocation with hop PUSCH, the A / uL_saito MSB (most significant bits) of the field that are used to specify the detailed hop configuration, while the rest of the field provides the resource allocation in the first Interval in the uplink subframe. A / uL_saito can be determined in this way from the system bandwidth according to table 1. Table 1 is obtained from table x / UL
8.4-1 of the 3GPP TS 36.213 v10.0.1 document. System bandwidth '<sup>V</sup>RB Indicates the number of uplink physical resource blocks.
Table 1
<td>n<sup>ul</sup>System bandwidth <sup>RB</sup></td><td>Number of hop bits for second interval A / uL_saito</td>
<td> 6-49</td><td> 1</td>
<td> 50-110</td><td> 2</td>
In the case of a multi-pool allocation with no-hopping PUSCH, the uplink resource allocation is signaled using the concatenation of the frequency hopping flag field and the resource block allocation and the hopping resource allocation field of the DCI.
The case of multi-pool allocation with hop PUSCH is not defined in LTE. For this reason, the frequency hopping flag field (as required for single cluster allocation) can be used to signal uplink resource allocation in case of multiple cluster allocation.
For multiple cluster attributions, l ° g are required<sub>2</sub>
ΙΛ ^ / Ρ + Ι li bits to indicate or specify all allowed and supported combinations. According to the 3GPP LTE (-A) multi-pool allocation, the smallest unit of uplink resources that can be allocated is a resource block group (RBG) as noted below in more detail.
The size of the RBG can be determined from the system bandwidth according to table 2. The table
A / DL to / LIL is obtained from table 7.1.6.1-1 of the 3GPP document TS 36.213 v10.0.1 substituting <sup>1 RB</sup> for '<sup>V</sup>RB x, UL accordingly. The RB system bandwidth indicates the number of uplink physical resource blocks.
ES 2 697 347 T3
Table 2
<td><sub>w</sub>ul System bandwidth '<sup>V</sup>RB</td><td>RBG size (P)</td>
<td> <10</td><td> 1</td>
<td> 11-26</td><td> 2</td>
<td> 27-63</td><td> 3</td>
<td> 64-110</td><td> 4</td>
to/<sup>ul</sup> ^ RB
Interpretation of multiple cluster attribution
As mentioned above, hopping is not supported for LTE multi-pool RBAs. The DCI jump flag is therefore prepended to the RBA field, which increases the size by 1 bit. Whereas for single pool the allocation is based on a resource block granularity, for multiple pool allocations the granularity is based on a resource block group (RBG). An RBG is the junction of adjacent P RBs, where P can be set using Table 2 for any bandwidth of <sub>V</sub>UL uplink system supported by LTE. The only exception is the case where RB is not an integer multiple of P, and where therefore the last RBG contains the remaining RBs. Each RB is part of only one A / UL
RBG. The number of uplink RBGs<sup>IV</sup>RBG can then be calculated as =
Since multi-pool attribution is known and defined in 3GPP LTE Version 10, the additional details of the RBGs and the allowed combination of RBs (which make up the RBGs) that are supported by the system and therefore are not required are omitted. Multiple pool allocation according to 3GPP LTE Version 10 and specifically DCI 0 format for signaling multiple pool resource allocation is defined in 3GPP TS 36.212 V10.0.0 document.
According to 3GPP LTE Version 10, multi-pool allocations are restricted to support only two pools, where the first pool is identified by the initiating RBG so and the ending RBG si-1, and where the second pool is identified by the start RBG S2 and the end RBG s<sub>3</sub>-1. These four parameters are then joined to a single r value that represents the multiple pool attribution using the following formula:
<sup>N</sup>-<sup>s</sup>or\<sub>+</sub>/<sup>N</sup>~<sup>s</sup>i
M / \ Ml
Ns<sub>2</sub>
M ~ 2
M-3 where M = 4 (corresponding to the four starting and ending RBGs that define a multiple pool consisting of two pools),
UL
RBG and 1 <So <Si <s<sub>2</sub> <s<sub>3</sub> <N and where
X) λ! y) y '.- (xy) x> yx <y
Additionally, 3GPP LTE Version 10 requires that the two pools are not adjacent, that is, there is a spacing of at least one RBG between the end of the first pool and the start of the second pool. These conditions lead to the previous formula and to the inequality relations between the values so, Si, S2, s<sub>3</sub>.
The present invention has recognized that for most cases (i.e., for most uplink system bandwidth values defined by the 3GPP TS 36.213 specification), the number of bits available in the DCI and of bits required to indicate all allowed RBG allocation combinations supported by the system are matched. However, for some cases an insufficient number of bits is available in the DCI as noted above.
Summary of the invention
The invention is intended to overcome one or more of the discussed and noted problems of known resource allocation concepts of mobile communication systems or to improve the signaling of known resource allocation concepts.
It is an object of the invention to provide an improved method for signaling resource allocation information to a terminal of a mobile communication system used to allocate resources to the terminal, as well as a corresponding terminal and a corresponding base station.
ES 2 697 347 T3
This objective is achieved by the subject matter of the independent claims.
Preferred embodiments of the invention are defined by the dependent claims.
The present invention has recognized that situations may occur where the number of bits available to signal resource allocation information is insufficient to represent the allowed resource allocations that are supported by the communication system. In case of LTE, the allowed resource allocations can be the different RBG resource allocations (ie, the allowed combinations of RBs) that are supported by the system for multi-pool allocation.
A first embodiment of the invention relates to a method performed by a terminal of a mobile communication system to receive and determine resource allocation information indicating to the terminal resources allocated for the terminal. The terminal receives, in accordance with this embodiment, downlink control information (DCI), comprising a field for indicating a resource allocation for the terminal. This resource allocation field in the DCI has a predetermined number of bits. The terminal determines its allocated resource allocation information from the contents of that field in the received DCI, even though - at least for one or more specific resource allocation cases - the default bit size of the resource allocation field in the DCI received is insufficient to represent all allowed resource allocations that are supported by the communication system. According to this embodiment, it is therefore suggested that the received bits that are signaled to the terminal in the mentioned field of the DCI represent (a subset of) predetermined bits of the resource allocation information. All the remaining one or more bits of the resource allocation information that are not included in the received DCI field are set to a predetermined value, eg, 1 or 0.
The DCI used to signal the resource allocation information can have a predetermined format, in which case the number of bits of the field that is used to signal the resource allocation information in the DCI can be predefined for any allowed bandwidth supported by the system. This implies that the terminal can determine the expected bit size of the signaled resource allocation information (ie, the size of the field in the received DCI that contains the resource allocation information).
Another embodiment of the invention relates to a method for transmitting resource allocation information for allocating resources to a terminal of a mobile communication system. For this, a base station determines the resource allocation information to be transmitted to the terminal. The base station may further determine the number of bits that are available to signal resource allocation information in the downlink control information (DCI). The number of available bits can thus be the size of one or more field or fields for transmitting resource allocation information in the DCI. The number of bits that is available to signal the resource allocation information (i.e. the bit size of the field mentioned in the DCI) is predetermined for a given bandwidth (and can therefore be determined by the base station, and via the terminal as soon as it becomes aware of the relevant bandwidth).
If the number of bits available to signal the resource allocation information is insufficient to represent the plurality of allowed resource allocations, the base station transmits a predetermined subset of bits of the resource allocation information in the DCI field to said terminal. All the remaining one or more bits of the resource allocation information that are not transmitted, or cannot be transmitted, to the terminal have a predetermined value or are set to a predetermined value.
According to a specific embodiment of the invention the mobile communication system is a 3GPP LTE system or a 3GPP LTE-A system. In this case, the terminal is a user equipment (UE) or a forwarding node. Similarly, the base station is an evolved Node B (eNodeB) or a forwarding node. The DCI format in this case can be DCI 0 format as defined in 3GPP LTE or 3GPP LTE-A. Alternatively, the DCI 4 format as defined in 3GPP LTE or 3GPP LTE-A may be used for some embodiments of the invention.
The remaining one or more bits of the aforementioned resource allocation information that are not signaled in said field of said DCI may be the most significant bit or bits, MSB, or the least significant bit or bits, LSB, of said information of resource allocation.
Furthermore, the position and / or value of these remaining one or more bits in the resource allocation information can be predefined (for example, in the system according to a specification of technical requirements), or predetermined by the base station and then be signaled to the terminal.
Further embodiments of the inventions relate to 3GPP LTE, where the resource allocation information represents the resource block allocation, RB, according to a single pool resource allocation in either DCI 0 format or defined DCI 4 format. in 3GPP LTE or in 3GPP LTE-A.
Alternatively or additionally, the resource allocation information may represent the resource block group allocation, RBG, according to a multi-pool resource allocation in DCI 0 format or DCI 4 format defined in 3GPP LTE or in 3GPP LTE-A, where an RBG comprises a
ES 2 697 347 T3 predefined plurality of adjacent RBs.
It is further envisaged according to an embodiment of the invention that the value and positions of said remaining one or more bits of the resource allocation information (which are not signaled in the DCI field) are predetermined to limit the number of RB combinations that are assignable to that terminal.
Alternatively, the value and positions of the remaining one or more bits may be predetermined to limit the number or combinations of RBGs that are assignable to the terminal.
According to this embodiment of the invention, the predetermined value and the predetermined positions of the remaining one or more bits can be chosen to exclude an allocation of one or more endpoint physical resource blocks, PRBs, for example, usable by the system of communication for physical uplink control channel transmissions, PUCCH. It may be further advantageous to exclude an allocation of one or more end physical resource blocks since this reduces the amount of out-of-band interference generated, ie, power leaking out of the allowed bandwidth.
Additional embodiments of the invention propose a re-interpretation or re-mapping scheme for the signaled resource allocation information that is applied by the base station and / or the terminal to change the RB, RBG or combinations thereof that are assignable to that terminal.
This reinterpretation scheme may include a replication from low RB or RBG indices to high RB or RBG indices, respectively, and vice versa. Alternatively or additionally, the reinterpretation scheme may include an offset of the resource allocation information signaled by a predetermined offset, where the offset is defined as an RB or RBG number.
The reinterpretation scheme can be configured by a base station or can be signaled by said base station to said terminal.
According to a further embodiment of the invention there is provided a method for transmitting resource allocation information for allocating uplink resources to a terminal of a 3GPP LTE or 3GPP LTE-A communication system. The procedure is performed by a base station or forwarding node. The base station is configured to transmit resource allocation information in a downlink control information field, DCI, to the terminal. The resource allocation information may thus represent different resource block groups, RBG, according to a multi-pool resource allocation in said 3GPP LTE or 3GPP LTE-A communication system. The available bit size of the DCI field used to transmit the resource allocation information is thus sufficient to represent a plurality of possible uplink resource allocations, since the RBG size is determined according to a novel.
The RBG size according to this embodiment of the invention can be determined for a given number of uplink resource blocks according to:
<td>n<sup>ul </sup> RB</td><td>pUL RBG</td>
<td> <6, 8</td><td> 1</td>
<td> 7, 9-26</td><td> 2</td>
<td> 27-54</td><td> 3</td>
<td> 55-84, 91-100</td><td> 4</td>
<td> 85-90, 101-110</td><td> 5</td>
Alternatively, the RBG size according to this embodiment of the invention can be determined for a given number of uplink resource blocks according to:
<td>RB</td><td>pUL 'RBG</td>
<td> <6</td><td> 1</td>
<td> 7-26</td><td> 2</td>
<td> 27-54</td><td> 3</td>
<td> 55-84</td><td> 4</td>
<td> 85-110</td><td> 5</td>
N<sup>UL</sup>
In both cases, the value <sup>RB</sup> indicates the number of uplink resource blocks and the value indicates the corresponding RBG size in number of RBs.
pUL 'RBG
According to a still further embodiment of the invention there is provided a method for receiving resource allocation information for allocating uplink resources to a terminal of a 3GPP LTE or 3GPP LTE-A communication system. The procedure is performed through the terminal or the forwarding node. The
ES 2 697 347 T3 terminal is configured to receive downlink control information, DCI comprising a field for signaling the resource allocation information of said terminal. This field has a predetermined number of bits and the resource allocation information represents resource block groups, RBG, according to a multi-pool resource allocation in said 3GPP LTE communication system or
3GPP LTE-A. The bit size of the DCI field used to signal the resource allocation information is thus sufficient to represent a plurality of possible uplink resource allocations, since the RBG size is determined according to a novel way . The way to determine the RBG size for a given number of uplink resource blocks is based on either of the two tables shown above.
According to yet another embodiment of the invention the terminal is provided for receiving resource allocation information for allocating resources to said terminal in a mobile communication system. The terminal comprises means for receiving downlink control information, DCI comprising a field for indicating the resource allocation information of the terminal. The field has a predetermined number of bits. The terminal further comprises means for determining the resource allocation information from the bits of the field in the received DCI. The predetermined number of bits of the field in the received DCI is thus insufficient to represent the plurality of allowed resource allocations that are supported by the communication system, for example, insufficient to represent the plurality of allowed multiple pool resource allocations. . Therefore, it is suggested that the bits of the field in the received DCI represent predetermined bits of the resource allocation information, while all the remaining one or more bits of the resource allocation information that are not included in the field of the DCI received are set to the default value.
According to a further embodiment of the invention there is provided a base station for transmitting resource allocation information for allocating resources to a terminal of a mobile communication system. The base station comprises means for determining resource allocation information to be transmitted to the terminal. The base station further comprises means for determining the number of bits available to signal resource allocation information in downlink control information, DCI. The number of available bits is thus the size of the field for transmitting the resource allocation information in said DCI. Furthermore, the DCI has a predetermined format and for a given bandwidth the number of bits available to signal the resource allocation information in the DCI is specified. The base station further comprises means for transmitting a predetermined subset of the resource allocation information bits in the DCI field to the terminal, if the number of bits available to signal the resource allocation information is insufficient to represent the plurality of allowed resource allocations, while all the remaining one or more bits of the resource allocation information that are not transmitted have a predetermined value.
Brief description of the figures
In the following, embodiments and aspects of the invention are described in more detail with reference to the accompanying figures. Similar or corresponding details in the figures are marked with the same reference numerals.
Figure 1 Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 7A
Figure 8 shows an exemplary architecture of a 3GPP LTE system, shows an exemplary overview of the global E-UTRAN architecture of 3GPP LTE, shows an exemplary sub-frame structure in a downlink component carrier as defined for 3GPP LTE (Version 10), shows an exemplary downlink resource grid of a downlink interval as defined for 3GPP LTE (Version 8/9), shows an exemplary uplink resource grid of an uplink range as defined for 3GPP LTE (Version 10), shows the number of bits available in DCI 0 format to specify the allocated RBG and the number of bits required to specify all allowed RBGs as supported and defined by 3GPP LTE (Version 10) with respect to one aspect of the present invention, shows an exemplary procedure for receiving and determining resource allocation information in a terminal of a mobile communication system in accordance with one aspect of the present invention, shows exemplary steps of determining resource allocation information of the exemplary procedure of the Figure 7 according to another embodiment of the present invention, and shows an exemplary procedure for determining and transmitting resource allocation information by a base station of a mobile communication system in accordance with a
ES 2 697 347 T3 aspect of the present invention.
Detailed description of the invention
This section will describe various embodiments of the Invention. For exemplary purposes only, most of the embodiments are noted in relation to an orthogonal single carrier uplink radio access scheme in accordance with 3GPP LTE (such as Version 8 or 9) and LTE-A ( such as Version 10) discussed in the Technical Background section above. It is to be noted that the Invention may be advantageously used in conjunction with a mobile communication system such as 3GPP LTE and LTE-A communication systems described above, but the Invention is not limited to this particular exemplary communication system.
The details provided herein of 3GPP LTE and LTE-A are intended to provide a better understanding of the Invention and should not be construed as limiting the Invention to the specific Implementation details described of the described mobile communication system.
As discussed above, the Invention has recognized that situations may occur where the number of bits available to signal Resource Allocation Information is insufficient to represent the allowed resource allocations that are supported by the communication system. In case of multiple LTE pool allocation, the allowed resource allocations are the different RBG allocation combinations (that is, the allowed RB combinations) that are supported by the system.
For the specific case of LTE multiple pool allocations according to the DCI 0 format, the number of bits for the resource allocation field that is required to select all combinations
Γ | 7pV¿ £ / P + lff) of RBG allowed is (as explained above) * ° S2 The available bits in the
DCIs to signal the allocation of uplink resources to the terminal can be calculated from
<img file="ES2697347T3_D0002.tif" />
as discussed in the background section and as specified in 3GPP LTE-A Version 10.
For most of the numerical cases covered by the 3GPP LTE specification for multi-pool allocation, the number of available bits and required bits does not show a problem. However, in some cases there are not enough bits available, as shown in Figure 6.
Specifically, Figure 6 shows the number of bits available in DCI 0 format to specify the allocated RBG and the number of bits required to specify all allowed RBG combinations as supported and defined by 3GPP LTE, Version 10, for allocation of multiple groupings.
As can be obtained from Figure 6 or the formulas provided above, the number of bits ,, UL.
available in the DCI format 0 is Insufficient for the following number of '' RB7, 9, 10, 55-63, 85-90, 101110 (where only the Range of 6-110 has been considered exemplary and therefore simplicity). How has it
JV<sup>UL</sup>
Indicated above, <sup>RB</sup> Indicates the bandwidth of the system in terms of the number of physical uplink resource blocks.
For the 3GPP LTE- (A) specification, the currently supported system bandwidth for uplink transmissions ranges from 6 to 110, while at least the values 5, 15, 25, 50, 75 and 100 are currently commonly used values. . Therefore, for commonly used system bandwidths the number of bits available in the DCI is sufficient to represent all allowed resource allocations.
These allowed resource allocations are the allocations that are supported by the LTE (-A) technical specifications. For single pool allocation, the allowed resource allocations are the different sets of uplink resource blocks that are assignable to UEs and supported by the LTE (-A) system. More specifically, for single pool allocation, the assigned uplink resources are each of the adjacent uplink resource blocks (RB). The assigned uplink resources are specified in the DCI by the first RB and the length of the uplink resource, that is, the number of RBs. The first RB and the Length Information are combined into a RIV Resource Indication value, as provided by TS 36.213 v10.0.1 section 8.1.1, to be signaled in the DCI. Additionally, the DCI includes a flag to indicate if frequency hopping is used for attribution.
For multiple pool allocation, the allowed resource allocations are the different combinations of uplink Resource Block Groups (RBGs) that are assignable to UEs and supported by the LTE (-A) system. More specifically, LTE multi-pool allocation supports allocation of
ES 2 697 347 T3 multiple clusters with two clusters, where each cluster is a portion of adjacent RBG (and therefore RB) and where the two clusters are separated by at least one RBG (as indicated above and specified in LTE-A version 10). Therefore, the plurality of different resource allocations allowed for multi-pool allocation can be seen as all different combinations of RBG in two pools that are supported by the LTE-A specification. As noted above, the multiple pool allocation assigned according to LTE Version 10 is signaled as a value r which is determined based on the start and end RB of the two pools according to a rule defined in the LTE specification. -A (for example, document TS 36.213 v10.0.1 section 8.1.2). As noted above also, the LTE-A specification further defines that the DCI hop flag used for single pool allocation is to be used also when multiple pool allocation information r is signaled.
For future releases, the allowed number of pools may be greater than two and multiple pool allocation may be entered for downlink resource allocation as well. However, the allowed resource allocations, ie the different RBs or RBGs, and a way to signal them to UEs in the DCI will also be provided by future releases. The number of bits that are required to represent all allowed resource allocations is provided by and can be unambiguously determined from the technical specification itself.
According to the example in Figure 6, one or two additional Resource Information bits would be required (i.e., for bandwidths 7, 9, 10, 55-63, 85-90, 101-110) to be able to dlrecclonar all allowed RBGs that are supported by LTE, that is, to represent all allowed values of the Multiple Pool Allocation Information r.
Since the number of bits is predefined by the LTE technical specification (as noted above), the UE can determine the size of the Resource Allocation Information signaled by itself, or the UE can be preset to a size of Resource attribution information given. In other / yUL = 7 words, the LTE technical specification requires that for a given bandwidth (for example, RB in the example in Figure 6) the Resource Allocation Information (for example, the value r) has a certain yyUL size <sub>=</sub> 7 bits (eg 7 in the example in Figure 6 for RB). Similarly, the LTE specification defines the DCI format that includes the size of the field to signal the Resource Allocation Information to the UE. IF this size is Insufficient to represent all the allowed values r, the UE expects to receive Resource Allocation Information with a certain bit size, but the Information actually received in the DCI has a smaller bit size. The behavior of the UE to handle such a situation is not specified and is therefore Undefined. The UE preferably Ignores all the Information received in this Undefined situation to avoid behavior that negatively affects the terminal or the performance of the system.
To solve the problem of Insufficient bits in the DCI to represent all allowed allocable resource allocations (for example, for bandwidths 7, 9, 10, 55-63, 85-90, 101-110 in Figure 6), the simplest solution is to add the one or more additionally required bits to the respective field in the DCI so that all allocations of assignable resources can be expressed and signaled to the UE.
However, this feasible solution has the disadvantage that it would not be backward compatible to older LTE versions (eg versions 8 and 9), specifically for UEs that were made to fit those versions only. Furthermore, it has the disadvantage that the Resource Allocation Information signaled to the UE as part of the DCI has different sizes (i.e. different numbers of bits) for single allocation and for multiple pool allocation, which adds substantial complexity since a The additional DCI size that needs to be detected increases the hidden decoding efforts required to detect the DCI in the UE.
The Invention proposes a different solution to this problem produced by Insufficient available bits in the DCI, including, but not limited to, LTE multiple pool allocations according to the DCI 0 format. The proposed solution does not increase the number of bits used in the transmitted DCI to signal the allocated resources, for example, the allocated RBGs for LTE multi-pool allocations according to the DCI 0 format, and thus maintains the complexity DCI detection in the UE at the same level.
According to one embodiment of the Invention, only as many bits of Resource Allocation Information are signaled to the UE as can be sent in the DCI if the number of bits available in the DCI is Insufficient. All remaining bits of the Resource Allocation Information (that is, those bits for which additional bits would be required as discussed above) are assumed to be, or are set to, a predefined value. In other words, these remaining bits of the Resource Allocation Information (eg representing the r value discussed above for multi-pool allocation) that cannot be signaled in the DCI due to insufficient bits are set to 0 or 1. Resource Allocation Information in this context is the Information required to represent all allocations (eg, all RBGs for multi-pool allocation) that are supported by the LTE specification.
ES 2 697 347 T3
Consequently, it is suggested to provide a new interpretation of the signaled bits on the transmitter (eNodeB) and receiver (UE) sides so that the known and invariable DCI format can still be used to signal resource allocation information. significant.
Next, this approach to 3GPP LTE multi-pool attribution is being developed using the DCI 0 format. For this, the following mathematical properties are used:
<td></td><td></td>
<td> =</td><td> +</td>
<td>J l and J</td><td></td>
(Equation 1)
It can be seen that each of these terms is 0 or a positive integer for any non-negative integer x and y. Since the invention relates to uplink or downlink resource allocations, these conditions are always satisfied.
y-1
<img file="ES2697347T3_D0003.tif" />
wly)
In-<sub>Sq</sub>\ / N-sA
To analyze the value r, it is useful to analyze the relationship between the first two terms \ / V \ M '
Assuming that N-s or> MyN-s ^> M-1, it is possible to write these terms as l respectively.
The first term can be converted according to Equation 1 into:
f / V- (s<sub>0</sub>+ l) W / V- (s<sub>0</sub> + l, «Η MJ [MI
Therefore, the following applies:
Ml
Equality holds only if N - (so + 1) = 0, that is, so = N -1. In this case the left side of the f 'Ί inequality becomes II<sup>,it is</sup> that is, only M = 1 applies. However, as discussed above, M = 4 due to the two clusters of LTE multiple cluster allocation.
pv-Jokpv-si
Since so <if and | <sub>Ax</sub> , »I * <sup>I know</sup> deduces that | <sub>MM</sub> _j j · Equality holds
M ~ \ </ ν-Ά (m ~<sup>s</sup>i only if si = so + 1. Consequently, it holds that l I>
Ml
The same can be applied mutatis mutandis for the other terms, so that the following relationships are obtained:
f / v-sA pv-,<sub>3</sub>
[M-2 (M-3
ES 2 697 347 T3
It therefore becomes clear that / V-JQ applies
M
Ns \ Μ -1 <sub>> N</sub>-<sub>S2</sub>\ \ M-2j \ M-3 unless one of these terms equals zero. Specifically, the case that the first term is not the largest value can only occur if:
<img file="ES2697347T3_D0004.tif" />
With t) - θ x <yy M = 4, it can be concluded that:
vi> N - 4> N - 3 s<sub>2</sub>> / V-2 s<sub>3</sub>> N- 1
With 1 <s or <if <s<sub>2</sub> <S3 <Λ /, it additionally holds that:
<N - 3 <N-2 s<sub>2</sub><N-1 s<sub>3</sub> <N
When these two restrictions are combined, the inequality holds only in the following condition:
<sup>=</sup> N - 3 = N-2 s<sub>2</sub> = N-1 s<sub>3</sub> = N
To determine the largest value of r, it is sufficient to consider those cases where each term is not zero. Then, in this specific case, r can be expressed as:
<img file="ES2697347T3_D0005.tif" />
Each term becomes the largest if the term N - s<sub>n</sub> is as large as possible, that is, in the following case:
ES 2 697 347 T3 <sup>r</sup>max
N ~ l
Ων-2ή Γ / ν-33 ίΝ-'ό
The following formula can be applied additionally:
Γλγ-Λ <tv-E. -,
<td></td><td></td><td>4M</td><td> +</td><td></td>
<td>, υ<sup>=</sup></td><td><sup>4</sup> j</td><td>l 3 J</td><td></td><td> , 2 ></td>
<td></td><td></td><td></td><td></td><td></td><td>íOv-33 í</td>
<td> =</td><td></td><td> +</td><td></td><td></td><td> +</td>
<td></td><td> , <sup>4</sup> )</td><td></td><td> , 3 ,</td><td></td><td>l <sup>2</sup> J l</td>
<img file="ES2697347T3_D0006.tif" />
<td></td><td></td><td>fw-34</td><td></td><td></td>
<td></td><td> +</td><td> +</td><td></td><td> +</td>
<td></td><td>L 3 J</td><td>l 2 J</td><td>k <sup>1</sup> ></td><td>l 0 J</td>
<td></td><td></td><td></td><td>'Nl'</td><td>(Λ7-3Ί</td><td></td><td>ÓV-4 ^</td>
<td></td><td> =</td><td> +</td><td></td><td> +</td><td> +</td><td></td>
<td></td><td></td><td>l <sup>4</sup>)</td><td> , 3 ,</td><td>l 2 J</td><td></td><td> < 1 ></td>
(V (N-2 \ (N-3 \ +
/ k
<img file="ES2697347T3_D0007.tif" />
'N-4, 1.
Λ0 <sup>4</sup>>
Furthermore, for the maximum value of r that can result for the supported resource allocations, it applies <sup>r</sup>max -. I.
Ν- * θ \
Additionally, the largest values of rse are obtained when 1 / is the largest, that is, for so = 1.
In LTE (-A), the end PRBs (Physical Resource Blocks) are likely to be used, configured, reserved or occupied by PUCCH (Physical Uplink Control Channel) transmissions. Therefore, the probability of assigning the extreme PRBs (on both sides of the spectrum) is quite low. It follows that the probability that these end PRBs (eg all RBGs containing end PRBs) are allocated in a multiple pool allocation is comparatively low. Additionally, not using the end PRBs reduces the out-of-band emissions generated by the transmissions, so it is advantageous even if those PRBs are not used, configured, reserved or occupied by PUCCH transmissions.
The largest signaled values for multi-pool allocations occur when the start of the first pool is at RBG 1, that is, at the first RBG of the uplink bandwidth. The smallest flagged values for multiple cluster allocations cannot be predicted so easily.
For example, if the bandwidth of the uplink system is 7 PRB, the following values apply:
ES 2 697 347 T3
UL
RB
P = 1 ^ RBG = 7 <j<sub>0</sub> <<j<sub>2</sub> <Γ<sub>3</sub> < 8 <sup>8-5</sup>ο \ <sub>+</sub> /<sup>8-5,</sup>ι <sup>F</sup>8-j<sub>2</sub>
8-¿3 <sup>r</sup>max ~
8' <sup>4</sup>, = 69.
Consequently, for the example that the uplink system bandwidth is 7 PRB, there are seventy different r-values (0 to 69). These different values of r are the allowed uplink resource allocations supported by the system. To represent seventy allowed values, 7 bits are required. For these 7 PRB exemplary system bandwidth parameters, the equation ^ (WrbXVrb + 1) / 2) 1 +1 = pog<sub>2</sub>(7-8 / 2) 1 +1 = r »og<sub>2</sub>(28) l +1 = 6 provides that only 6 bits are available for signaling r, even though 7 bits were required to cover all of the allowed seventy values of r. The seventy allowable values and corresponding RBG multiple pool attributions for this example are shown in Table 2.
It can be further observed from Table 2 that the values 64-69 (shown in italics) have in common that the first RBG so of the first grouping is RBG number 1, that is, the first RBG of the system bandwidth. . These states therefore correspond to those valid states where the MSB (that is, the bit that represents decimal 64) of r is set to 1. On the other hand, it can be seen that the states that are represented by the LSB of reset to 0 (shown in bold) do not share similar characteristics, for example, they do not share any identical starting or ending RBG of any grouping
Table 2
<td>SW</td><td>Yes</td><td>s<sub>2</sub></td><td>S3</td><td>r</td><td>SW</td><td>Yes</td><td>s<sub>2</sub></td><td>S3</td><td>r</td>
<td> 1</td><td> 2</td><td> 3</td><td> 4</td><td> 69</td><td> 2</td><td> 3</td><td> 4</td><td> 5</td><td> 34</td>
<td> 1</td><td> 2</td><td> 3</td><td> 5</td><td> 68</td><td> 2</td><td> 3</td><td> 4</td><td> 6</td><td> 33</td>
<td> 1</td><td> 2</td><td> 3</td><td> 6</td><td> 67</td><td> 2</td><td> 3</td><td> 4</td><td> 7</td><td> 32</td>
<td> 1</td><td> 2</td><td> 3</td><td> 7</td><td> 66</td><td> 2</td><td> 3</td><td> 4</td><td> 8</td><td> 31</td>
<td> 1</td><td> 2</td><td> 3</td><td> 8</td><td> 65</td><td> 2</td><td> 3</td><td> 5</td><td> 6</td><td> 30</td>
<td> 1</td><td> 2</td><td> 4</td><td> 5</td><td> 64</td><td> 2</td><td> 3</td><td> 5</td><td> 7</td><td> 29</td>
<td> 1</td><td> 2</td><td> 4</td><td> 6</td><td> 63</td><td> 2</td><td> 3</td><td> 5</td><td> 8</td><td> 28</td>
<td> 1</td><td> 2</td><td> 4</td><td> 7</td><td> 62</td><td> 2</td><td> 3</td><td> 6</td><td> 7</td><td> 27</td>
<td> 1</td><td> 2</td><td> 4</td><td> 8</td><td> 61</td><td> 2</td><td> 3</td><td> 6</td><td> 8</td><td> 26</td>
<td> 1</td><td> 2</td><td> 5</td><td> 6</td><td> 60</td><td> 2</td><td> 3</td><td> 7</td><td> 8</td><td> 25</td>
<td> 1</td><td> 2</td><td> 5</td><td> 7</td><td> 59</td><td> 2</td><td> 4</td><td> 5</td><td> 6</td><td> 24</td>
ES 2 697 347 T3 (continued)
<td>SW</td><td>Yes</td><td>s<sub>2</sub></td><td>S3</td><td>r</td><td>SW</td><td>Yes</td><td>s<sub>2</sub></td><td>S3</td><td>r</td>
<td> 1</td><td> 2</td><td> 5</td><td> 8</td><td> 58</td><td> 2</td><td> 4</td><td> 5</td><td> 7</td><td> 23</td>
<td> 1</td><td> 2</td><td> 6</td><td> 7</td><td> 57</td><td> 2</td><td> 4</td><td> 5</td><td> 8</td><td> 22</td>
<td> 1</td><td> 2</td><td> 6</td><td> 8</td><td> 56</td><td> 2</td><td> 4</td><td> 6</td><td> 7</td><td> 21</td>
<td> 1</td><td> 2</td><td> 7</td><td> 8</td><td> 55</td><td> 2</td><td> 4</td><td> 6</td><td> 8</td><td> 20</td>
<td> 1</td><td> 3</td><td> 4</td><td> 5</td><td> 54</td><td> 2</td><td> 4</td><td> 7</td><td> 8</td><td> 19</td>
<td> 1</td><td> 3</td><td> 4</td><td> 6</td><td> 53</td><td> 2</td><td> 5</td><td> 6</td><td> 7</td><td> 18</td>
<td> 1</td><td> 3</td><td> 4</td><td> 7</td><td> 52</td><td> 2</td><td> 5</td><td> 6</td><td> 8</td><td> 17</td>
<td> 1</td><td> 3</td><td> 4</td><td> 8</td><td> 51</td><td> 2</td><td> 5</td><td> 7</td><td> 8</td><td> 16</td>
<td> 1</td><td> 3</td><td> 5</td><td> 6</td><td> 50</td><td> 2</td><td> 6</td><td> 7</td><td> 8</td><td> 15</td>
<td> 1</td><td> 3</td><td> 5</td><td> 7</td><td> 49</td><td> 3</td><td> 4</td><td> 5</td><td> 6</td><td> 14</td>
<td> 1</td><td> 3</td><td> 5</td><td> 8</td><td> 48</td><td> 3</td><td> 4</td><td> 5</td><td> 7</td><td> 13</td>
<td> 1</td><td> 3</td><td> 6</td><td> 7</td><td> 47</td><td> 3</td><td> 4</td><td> 5</td><td> 8</td><td> 12</td>
<td> 1</td><td> 3</td><td> 6</td><td> 8</td><td> 46</td><td> 3</td><td> 4</td><td> 6</td><td> 7</td><td> 11</td>
<td> 1</td><td> 3</td><td> 7</td><td> 8</td><td> 45</td><td> 3</td><td> 4</td><td> 6</td><td> 8</td><td> 10</td>
<td> 1</td><td> 4</td><td> 5</td><td> 6</td><td> 44</td><td> 3</td><td> 4</td><td> 7</td><td> 8</td><td> 9</td>
<td> 1</td><td> 4</td><td> 5</td><td> 7</td><td> 43</td><td> 3</td><td> 5</td><td> 6</td><td> 7</td><td> 8</td>
<td> 1</td><td> 4</td><td> 5</td><td> 8</td><td> 42</td><td> 3</td><td> 5</td><td> 6</td><td> 8</td><td> 7</td>
<td> 1</td><td> 4</td><td> 6</td><td> 7</td><td> 41</td><td> 3</td><td> 5</td><td> 7</td><td> 8</td><td> 6</td>
<td> 1</td><td> 4</td><td> 6</td><td> 8</td><td> 40</td><td> 3</td><td> 6</td><td> 7</td><td> 8</td><td> 5</td>
<td> 1</td><td> 4</td><td> 7</td><td> 8</td><td> 39</td><td> 4</td><td> 5</td><td> 6</td><td> 7</td><td> 4</td>
<td> 1</td><td> 5</td><td> 6</td><td> 7</td><td> 38</td><td> 4</td><td> 5</td><td> 6</td><td> 8</td><td> 3</td>
<td> 1</td><td> 5</td><td> 6</td><td> 8</td><td> 37</td><td> 4</td><td> 5</td><td> 7</td><td> 8</td><td> 2</td>
<td> 1</td><td> 5</td><td> 7</td><td> 8</td><td> 36</td><td> 4</td><td> 6</td><td> 7</td><td> 8</td><td> 1</td>
<td> 1</td><td> 6</td><td> 7</td><td> 8</td><td> 35</td><td> 5</td><td> 6</td><td> 7</td><td> 8</td><td> 0</td>
According to one embodiment of the Invention, the following approach is used if Insufficient bits are available to signal the entire Interval of r as with the previous example listed in Table 2:
• The bits that can be signaled represent the LSBs of r • Any remaining bits of r that cannot be signaled, that is, the remaining MSB (s) of r (if any), are set to 0.
In accordance with another embodiment of the Invention, it is further proposed that:
• The eNodeB, when determining the allocation of multiple pools, avoids assigning the allocations of multiple pools that cannot be transmitted in the DCI. In other words, only those attributions for which the MSB (s) are 0 are determined, if applicable. In this case, there is no need to Inform the UE of the value of the MSB (s), since it assumes that they are zero according to this Invention. Alternatively, the UE may be informed of the value of the MSB (s), eg, as part of Control Information signaled to the UE.
The following advantages are obtained for these embodiments:
• Multiple pool allocations can be supported for all A / A bandwidth values.<sup>UL</sup> system '' RB, Even if Insufficient bits are available to signal the Unrestricted Range of values of r.
• Only allocations can not be made where the first RBG of the allocation is in the first RBG of the uplink system bandwidth. However, it is expected that the first RBG will not be allocated normally due to the aforementioned aspects, so that the relative loss to the system is comparably negligible.
• Some allocations where the first RBG of the allocation is in the first RBG of the uplink system bandwidth can still be performed (for example, signaling values of r between 35 and 63):
• In contrast, if for example the MSB is set to 1, only allocations 64-69 could be signaled,
ES 2 697 347 T3 which is a comparatively strong restriction on the usability of multi-pool resource allocation.
• In contrast, if for example the LSB is set to either 0 or 1, only 35 of the previous 70 cases in Table 2 could be signaled, which is also to put strong restrictions on the usability of multi-pool resource allocation. Furthermore, these attributions do not follow a particular pattern.
• In contrast, if only a defined restricted portion of the bandwidth can be allocated by multiple pool allocations, it follows that for example the first RBG can never be allocated for multiple pool allocations. In the example in Table 2, this would affect settings 35-69 that would not be usable, that is, 50% of the time.
According to another embodiment of the invention the same approach is applied as noted above, ie to set the unsigned MSB bits to zero. However, the Interpretation of the indicated values is also modified. For example, the last RBG can be blocked from being assignable instead of the first RBG as in the example above. This approach is a replication of the flagged allocations and can be achieved by re-mapping the flagged information, such as flagged values so as<sub>3</sub> Indicating the two pools of the RBGs for LTE multiple pool allocation. Remapping can be achieved according to a further embodiment of the Invention by the following equations:
applied _ _ marked applied <sup>J</sup>1
N + 1- j signaling applied _. signaled ¡2 - (V +1 J | applied, signaled
3 ** 1 **0
According to yet another embodiment, replication can also be obtained by defining a reinterpretation of the values of r. For the previous example of Table 3, Table 4 shows possible relationships, which are obtained from the previous rules to re-interpret the values so as<sub>3</sub> and the rule to obtain a value r from the values s or as<sub>3 </sub>discussed above.
Table 4
<td>^ enaiizaao</td><td>r & piicaao</td><td>^ penalized</td><td>r & piicaao</td><td>^ penalized</td><td>r & piicaao</td><td>^ penalized</td><td>r & piicaao</td>
<td> 69</td><td> 0</td><td> 51</td><td> 37</td><td> 33</td><td> 8</td><td> 15</td><td> 66</td>
<td> 68</td><td> 1</td><td> 50</td><td> 10</td><td> 32</td><td> 18</td><td> 14</td><td> 14</td>
<td> 67</td><td> 5</td><td> 49</td><td> 20</td><td> 31</td><td> 38</td><td> 13</td><td> 24</td>
<td> 66</td><td> 15</td><td> 48</td><td> 40</td><td> 30</td><td> 11</td><td> 12</td><td> 44</td>
<td> 65</td><td> 35</td><td> 47</td><td> 26</td><td> 29</td><td> 21</td><td> 11</td><td> 30</td>
<td> 64</td><td> 2</td><td> 46</td><td> 46</td><td> 28</td><td> 41</td><td> 10</td><td> 50</td>
<td> 63</td><td> 6</td><td> 45</td><td> 56</td><td> 27</td><td> 27</td><td> 9</td><td> 60</td>
<td> 62</td><td> 16</td><td> 44</td><td> 12</td><td> 26</td><td> 47</td><td> 8</td><td> 33</td>
<td> 61</td><td> 36</td><td> 43</td><td> 22</td><td> 25</td><td> 57</td><td> 7</td><td> 53</td>
<td> 60</td><td> 9</td><td> 42</td><td> 42</td><td> 24</td><td> 13</td><td> 6</td><td> 63</td>
<td> 59</td><td> 19</td><td> 41</td><td> 28</td><td> 23</td><td> 23</td><td> 5</td><td> 67</td>
<td> 58</td><td> 39</td><td> 40</td><td> 48</td><td> 22</td><td> 43</td><td> 4</td><td> 34</td>
<td> 57</td><td> 25</td><td> 39</td><td> 58</td><td> 21</td><td> 29</td><td> 3</td><td> 54</td>
<td> 56</td><td> 45</td><td> 38</td><td> 31</td><td> 20</td><td> 49</td><td> 2</td><td> 64</td>
<td> 55</td><td> 55</td><td> 37</td><td> 51</td><td> 19</td><td> 59</td><td> 1</td><td> 68</td>
<td> 54</td><td> 3</td><td> 36</td><td> 61</td><td> 18</td><td> 32</td><td> 0</td><td> 69</td>
<td> 53</td><td> 7</td><td> 35</td><td> 65</td><td> 17</td><td> 52</td><td></td><td></td>
<td> 52</td><td> 17</td><td> 34</td><td> 4</td><td> 16</td><td> 62</td><td></td><td></td>
This embodiment is particularly advantageous if for example the last RBG consists of less PRB than the first one your UL _ qc
RBG. For example, assuming that RB 'then the exemplary interpretation illustrated in the definition of the
ΛΖ UL - 99
Table 4 and a RBG size of P = 4 (that is, the RBG has 4 PRBs) it can be determined that RBG
ES 2 697 347 T3
Preferably ^ RBG 1 - 21 RgQ <sub>I know</sub> each set to a size of P = 4 and the remaining 22<sup>d0</sup> RBG is composed of only 1 PRB. In general, it is possible that either all RBGs are the same size P (if xz UL az UL «<sup>/ V</sup>RB is an integer multiple of P), or RBG <sup>1</sup> be of size P and an Irregular RBG be of size in the a /<sup>ul</sup>
Interval {1,2, ..., P-1}. This normally occurs if<sup>, V</sup>RB is not an integer multiple of P.
It can be seen that the loss to the system is minimal if the Irregular RBG cannot be allocated by multiple pool allocations. However, this loss only applies to multiple pool attribution and Irregular RBG PRBs can still be assigned by single pool attributions, or by multiple pool attributions that do not employ this re-interpretation, for example by other UEs.
Preferably, the Irregular RBG is any of the first or last RBG. IF it is the first RBG, the approach without reinterpretation is beneficial, while, in the other case, the approach that includes the re-interpretation of the signaled value can be advantageously applied.
According to yet another embodiment, the re-Interpretation step can be applied by adding an offset to the offset, i.e., by applying F<sup>pfcat,</sup>° = f<sup>mark</sup>° + <sub>For</sub> example,<sup>r</sup> = <sup>r</sup>'_ flagged max' max value of r flagged, it is flagged flagged <sup>r</sup>max as the maximum value that can be signaled with the available bits. Alternatively, max be configured via the eNodeB and / or signaled to the UE. The advantage is the simplicity of an Implementation.
can
As a simple approach (from the Implementation perspective) but not as effective, the re-interpretation may consist of subtracting the signaled value from the maximum value ^ fallen _ _ penalized, <sub>is c</sub>|<sub>ec</sub>¡<sub>r in e</sub>| <sub>and</sub>j<sub>em</sub>p |<sub>0</sub> previous
Use p<sup>3</sup>P<sup>l</sup>’<sup>csc! or</sup> _ QQ ^ marked
According to another embodiment of the Invention, the re-interpretation to be applied could also be configured or signaled from the eNodeB. With such signaling, the flexibility of possible assignments via eNodeB is increased, at the expense of more complex implementation on the UE side and possibly also on the transmitter side. In another aspect of this embodiment the reinterpretation behavior is configured by the base station for each UE individually and is signaled the same, for example using higher layer signaling such as RRC or MAC signaling in the context of LTE. or LTE-A. For example, a first UE is configured without reinterpretation, while a second UE is configured with reinterpretation. The first RBG can then be allocated to the second UE and the last RBG can be allocated to the first UE in the same subframe using allocations from multiple pools each, so that all RBGs in the system can actually be used simultaneously from one perspective. system.
With respect to embodiments of the Invention with respect to proposed re-interpretation aspects, either DCI format 0 or 3GPP LTE DCI format 4 (-A) can be used, eg Version 10. Both DCI formats with respect to attribution of multiple clusters as discussed above.
Figure 7 shows an exemplary procedure for receiving and determining resource allocation information at a terminal of a mobile communication system as may be used with respect to the discussed embodiments of the present invention.
The exemplary procedure of Figure 7 can be performed by a terminal, such as a UE or a forwarding node in an LTE or UMTS system. The terminal receives Control Information Indicating allocated resources, such as RB or RBG allocated for uplink or downlink transmissions from the terminal. The allocated resources can be received as part of a DCI, as illustrated by step 701.
The terminal will then extract the bits of the signalized Resource Allocation Information from the received Control Information, as shown by step 703. In case of LTE, the DCI includes specialized fields and / or flags to indicate at least the resources attributed (i.e. RB or RBG), as discussed above. Typically, the received Resource Allocation Information represents one or more bit values indicating the resources allocated to the terminal as discussed above.
The terminal determines in step 705 the Resource Information allocated from the received and extracted bits. As previously discussed, steps 703 and 705 can be one and the same stage, if the signaled information (for example, the signaled bits in the DCI resource allocation field) directly specify the allocated resource, as in systems previous ones analyzed in the background section. According to embodiments of the Invention, there could be Insufficient bits available to signal all allowed combinations of allocated resources, in which case, the signalized bits received by the terminal do not directly indicate the allocated resource as discussed above. For some embodiments of the invention, the unsigned bits are set to a predefined value. In this case, the terminal may set these unsigned bits according to the predefined scheme (which may be set at the terminal or signaled to the UE) as part of step 705 to result in the actual Resource Allocation Information. As an alternative, the
ES 2 697 347 T3 terminal is configured to interpret received bits in accordance with the predefined scheme to identify actual allocated resources without actively setting the unsigned bits to a given value. In different embodiments of the invention, the number of signaled bits is sufficient to represent the allowed resource allocation and steps 703 and 705 may be one step.
As an optional step 707, the terminal may apply a reinterpretation or re-mapping of the signaled and received resource allocations that may be applied in accordance with the discussed embodiments of the reinterpretation invention. As also discussed, the reinterpretation can also be signaled to the terminal, in which case an additional step can be performed to receive and extract a reinterpretation flag, separately or as part of steps 703 and 705.
Figure 7A shows exemplary steps that may be performed as part of the determination step 705 of Figure 7 in accordance with another embodiment of the present invention. As indicated above, the terminal can determine the format and size of the received dCi, including the number (and location) of bits used to signal resource allocations. The number of signaled bits is also referred to as the number of available bits in the above description of the different aspects of the present invention. As also discussed above, the terminal can further determine the number of bits that is required to address or signal all allowed resource allocations that are supported by the communication system. As such, the terminal can determine if the signaled bits (that is, the number of bits in the received DCI that are extracted in step 703 of Figure 7) is sufficient to represent all the allowed resource allocations that are supported by the communication system, as illustrated in step 710 of Figure 7A.
If the number of signaled bits is sufficient, the bits extracted from step 703 of Figure 7 are determined to be the resource allocation information, as shown in step 712 of Figure 7A.
If the number of signaled bits is insufficient, the bits extracted from step 703 of Figure 7 are only a part of the resource allocation information. In this case, as shown by step 714, the one or more predetermined bits that are not signaled to the terminal (also referred to as the remaining bit or bits in the previous description of the different aspects of the present invention) are added below to the bits marked as extracted bits in step 703 of Figure 7. As discussed above, the position and value of the unmarked bits to be added are predetermined. The result of combining the predetermined bits and unsigned bits as illustrated in step 714 is used below as the resource allocation information. Subsequently, the reinterpretation step 707 of Figure 7 can be performed using the result of either step 712 or step 714.
Figure 8 shows an exemplary method for determining and transmitting resource allocation information by a base station of a mobile communication system as may be used with respect to the discussed embodiments of the present invention.
The exemplary procedure of Figure 8 can be performed at a base station, such as an eNodeB / NodeB or a forwarding node in an LTE or UMTS system. The base station determines the allocation of resources allocated for a terminal, such as RB or RBG allocated for uplink or downlink transmissions from the terminal, as illustrated by step 801.
In accordance with step 803, the base station determines if the number of available bits is sufficient to represent the allowed resource allocations supported by the system as discussed above for various embodiments of the invention.
If the number of available bits is sufficient, the base station can create the DCI in the common way as illustrated by step 807.
If the number of available bits is insufficient, the base station may set one or more predetermined bits of the resource allocation information (that is, the resource allocation information that would have to be signaled to address all allowed resource allocations supported by the system) to a predetermined value, as illustrated by step 809 and as discussed above for various embodiments of the invention.
According to step 811, the base station creates the DCI with those bits to be signaled according to the respective embodiments of the invention.
Steps 803, 805 and 809 can be performed once by the base station or only under given circumstances, but not for each control information signaling step. The result can then be applied in multiple subsequent signaling stages and to create and transmit multiple DCIs to the terminal (s) served by the base station. Alternatively, the determined values and bit numbers can be predefined or set, in which case steps 803, 805 and 809 do not have to be performed by the base station. Furthermore, some embodiments of the invention refer to the case where enough bits are available, such as embodiments of the invention with respect to the reinterpretation aspect that can be implemented with and
ES 2 697 347 T3 without enough bits as discussed above. For these embodiments steps 803, 805 and 809 may not be performed by the base station.
Once the DCI is created, the base station can transmit the DCI to the terminal as illustrated in step 813.
The exemplary procedures shown in Figures 7 and 8 may refer to the same communication system in which the received DCI was transmitted by the terminal in step 701 by the base station in step 813.
Instead of setting the MSB (s) of the Resource Allocation Information (for example, the RBGs allocated) to 0 as discussed above, the bit or bits that are set and / or the value to which they are set can be set using the eNodeB.
Whether or not a re-interpretation is applied, it can also be configured through the eNodeB, preferably by UE. According to another embodiment, the status of whether the re-interpretation is applied is signaled in the Control Information carrying the resource allocation. This could be achieved by a single bit (on / off). If this bit is taken from the LTE DCI resource allocation field according to the previous example in Table 3, an additional MSB is set to zero. This means that, with the above example, instead of 6 bits available, 1 bit is used as a reinterpretation flag (on / off), while the remaining 5 bits indicate the LSBs of r. Accordingly, the resources that can be allocated to a UE are limited to the values 0-31 in Table 3. IF the re-interpretation bit is set to off, this means that states 0-31 of the table can be allocated. IF the re-interpretation flag is set, this means that states 0-31 can be signaled and a reinterpretation scheme is applied. According to another embodiment of the Invention, the reinterpretation bit set to a first value means that a first set of states can be assigned by the available bits, and the reinterpretation bit set to a second value means that a second set of states can be assigned. set of states using the available bits. The first and second sets of states can be configured and signaled by the base station.
As discussed above, the embodiments of the present invention allow defining (preferably by UE) which RBs or RBGs or combinations thereof can actually be cleared with the number of bits available if the signaling is insufficient to allocate all RBs or combinations of RBGs allowed in the multiple pool approach.
However, according to yet another embodiment of the Invention, the number of RBGs (eg, for multiple pool allocation) or the number of RBs (eg, for single pool allocation) that can be set by an available number of bits can be determined and set by the system or the base station. For example, the number of receivable RBGs can be determined by:
<img file="ES2697347T3_D0008.tif" />
+ Vi 24.2 available
Therefore, the flagged bits can be interpreted to define a multiple grouping allocation in the addressable k, addressable
Interval from RBG 1 to RBG ”RBG · then another parameter can be conflgurable that defines if a re-interpretation is applied to the same as the previously mentioned solutions. Those skilled in the art will recognize that the given formula can also be applied to determine the number of addressable κι addressable \ jdirectable RBs by substituting ”RBG ροΗ'κβ
It is to be noted that this embodiment of the Invention can be used to limit the allocations of allocable resources for a UE, even if the available number of signaling bits would be Insufficient to delete all the allowable resource allocations.
n<sup>ul</sup>
In addition, a re-Interpretation can be defined so that the RB or RBG indices on the RB RBs are set first. In case RBs are defined, those RBs are formed in RBG, where in general non-adjacent RBs can be located in an RBG. The multiple pool allocation signal is then used to allocate RBG from this restricted set of RBGs. There is a choice as to whether the size of
RBG P is determined from the value ”RB o '<sup>v</sup>RBG · The former has the advantage that the RBG size is Identical for all UEs under the eNodeB, which simplifies the scheduling algorithm because only the single RBG size has to be taken into account. On the other hand, the second way improves the granularity of the recclonable RBGs, particularly if a very restricted subset of RB is defined for
<img file="ES2697347T3_D0009.tif" />
Normal RBG is P = 3. The network might wish or decide to use only 16 of these 50 PRBs (which for example corresponds to a frequency reutilation factor of about 1/3 which is quite common in cellular communication systems). This means for the first aforementioned way that 6 RBG, each of
ES 2 697 347 T3 size of 3 PRBs, selected for multiple pool allocation. For the second way mentioned above, there would be 8 RBGs of size 2 available for multi-pool allocation, since for a 16 PRB system the RBG size is 2. Therefore, granularity and planning flexibility is increased. It can be seen that, with the second way, it is possible again that more bits are required than are available. However, in such a case, the present invention has proposed a solution for signaling the attributions.
UL <sup>RB</sup> as well as
Since the number of bits required for multiple pool allocations depends on / yUL on the size of RBG P (which is itself a function of <sup>BB</sup>), it is also possible to modify the definition of the size of RBG P so that the number of available bits is sufficient to maintain the allocation of multiple pools for the resulting number of RBG.
From the number of bits available for multi-pool allocation, the number of RBG addressable
KTÜ dlrecclonables can be determined by <sup>7V</sup> rbg | 2 ^ .. bits available
Therefore, the RBG size is determined from the number of uplink resource blocks and the number of eligible RBGs is determined by:
pUL _ * r £ / £ / xrd addressablei <sup>r</sup>RBG "I <sup>/ v</sup> RB l <sup>2V</sup> RBG I
According to yet another embodiment of the Invention, it is therefore suggested to determine the RBG size for a given number of uplink resource blocks of a 3GPP LTE or 3GPP LTE-A communication system by means of Table 5 (obtained using the formula above) instead of the suggested Table 2 of the 3GPP LTE specification discussed in the background section.
Table 5
<td><sub>w</sub>«, <sup>n</sup>RB</td><td>pUL 'RBG</td>
<td> <6, 8</td><td> 1</td>
<td> 7, 9-26</td><td> 2</td>
<td> 27-54</td><td> 3</td>
<td> 55-84, 91-100</td><td> 4</td>
<td> 85-90, 101-110</td><td> 5</td>
pUL
It can be seen that Table 5 determines the smallest possible RBG size <sup>r</sup>RBG for which the number of bits is sufficient. Therefore, Table 5 provides the highest quality scheduler granularity and consequently the most efficient allocability in the scheduler (eg, NodeB) for all uplink resource block numbers. However, from an Implementation perspective it may be beneficial if the RBG size is a non-decreasing function of the number of uplink resource blocks. From that perspective, once the RBG size is a first value for a certain number of resource blocks, the RBG size should not be smaller than the first value for any larger number of resource blocks. Consequently, to take this into account, Table 5 can be modified to resemble Table 6:
Table 6
<td>fjUL ™ RB</td><td>pUL 'RBG</td>
<td> <6</td><td> 1</td>
<td> 7-26</td><td> 2</td>
<td> 27-54</td><td> 3</td>
<td> 55-84</td><td> 4</td>
<td> 85-110</td><td> 5</td>
Another aspect of the Invention relates to the Implementation of the various described embodiments using hardware and / or software. One skilled in the art will appreciate that the various embodiments of the Invention can be implemented or carried out using computing devices or one or more processors. A computing device or processor can be for example a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field of programmable gate matrix (FPGA) or other logic devices. programmable, etc. The various embodiments of the Invention may also be made or incorporated by a combination of these devices.
ES 2 697 347 T3
Additional embodiments of the invention relate to a terminal configured or adapted to perform the terminal-side steps of the different procedures and functionalities of the previously discussed embodiments.
Still further embodiments of the invention relate to a base station configured or adapted to perform the base station side steps of the different procedures and functionalities of the previously discussed embodiments.
Furthermore, the various embodiments of the invention may also be implemented by means of software modules or computer-readable instructions stored on one or more computer-readable media, which when executed by a processor or device component, perform the various described embodiments of the invention. Similarly, any combination of software modules, computer-readable media, and hardware components is anticipated by the invention. The software modules can be stored on any type of computer-readable storage medium, for example, RAM, EPROM, EEPROM, flash memory, registers, hard drives, CD-ROM, DVD, etc.
One skilled in the art will appreciate that numerous variations and / or modifications can be made to the present invention as disclosed by the specific embodiments without departing from the scope of the invention as defined in the appended claims. The discussed embodiments are, therefore, to be considered in all respects to be illustrative and not restrictive.
Contents17
42 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31 Sheet 32 Sheet 33 Sheet 34 Sheet 35 Sheet 36 Sheet 37 Sheet 38 Sheet 39 Sheet 40 Sheet 41 Sheet 42
68 members in 21 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 11159463 | European Patent Office (EPO) | A | |
| 11159463 | European Patent Office (EPO) | A | |
| 11159463 | European Patent Office (EPO) | – | |
| 11159463 | – | – | – |
| EP20110159463 | – | – | – |
Members68
| Document | Office | Kind | |
|---|---|---|---|
| EP2503835A1 | European Patent Office (EPO) | A1 | |
| WO2012126577A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW201244516A | Taiwan Province of China | A | |
| MX2013010739A | Mexico | A | |
| CN103548407A | China | A | |
| EP2689620A1 | European Patent Office (EPO) | A1 | |
| US2014029537A1 | United States of America | A1 | |
| KR20140027115A | Republic of Korea | A | |
| JP2014512114A | Japan | A | |
| RU2013142762A | Russian Federation | A | |
| EP2689620B1 | European Patent Office (EPO) | B1 | |
| ES2549048T3 | Spain | T3 | |
| DK2689620T3 | Denmark | T3 | |
| EP2953412A1 | European Patent Office (EPO) | A1 | |
| JP5881811B2 | Japan | B2 | |
| TWI526103B | Taiwan Province of China | B | |
| RU2577318C2 | Russian Federation | C2 | |
| US9392594B2 | United States of America | B2 | |
| JP2016136730A | Japan | A | |
| MX342679B | Mexico | B | |
| EP2953412B1 | European Patent Office (EPO) | B1 | |
| US2016353418A1 | United States of America | A1 | |
| EP3101979A1 | European Patent Office (EPO) | A1 | |
| DK2953412T3 | Denmark | T3 | |
| ES2612881T3 | Spain | T3 | |
| US9713138B2 | United States of America | B2 | |
| JP6179786B2 | Japan | B2 | |
| BR112013023927A2 | Brazil | A2 | |
| EP3101979B1 | European Patent Office (EPO) | B1 | |
| US2017289977A1 | United States of America | A1 | |
| CN103548407B | China | B | |
| EP3255946A1 | European Patent Office (EPO) | A1 | |
| JP2017225129A | Japan | A | |
| DK3101979T3 | Denmark | T3 | |
| ES2651563T3 | Spain | T3 | |
| BR112013023927A8 | Brazil | A8 | |
| CN107769904A | China | A | |
| JP6365996B2 | Japan | B2 | |
| US10051619B2 | United States of America | B2 | |
| EP3255946B1 | European Patent Office (EPO) | B1 | |
| JP2018164304A | Japan | A | |
| LT3255946T | Lithuania | T | |
| US2018332569A1 | United States of America | A1 | |
| TR2018016354T4 | Türkiye | T4 | |
| TR201816354T4 | Türkiye | T4 | |
| PT3255946T | Portugal | T | |
| DK3255946T3 | Denmark | T3 | |
| SI3255946T1 | Slovenia | T1 | |
| HRP20181921T1 | Croatia | T1 | |
| ES2697347T3This record | Spain | T3 | |
| KR101943670B1 | Republic of Korea | B1 | |
| HUE040140T2 | Hungary | T2 | |
| PL3255946T3 | Poland | T3 | |
| RS58013B1 | Serbia | B1 | |
| MX363919B | Mexico | B | |
| CY1120868T1 | Cyprus | T1 | |
| JP6620848B2 | Japan | B2 | |
| US10542534B2 | United States of America | B2 | |
| US2020100228A1 | United States of America | A1 | |
| CN107769904B | China | B | |
| US11234231B2 | United States of America | B2 | |
| US2022104186A1 | United States of America | A1 | |
| BR112013023927B1 | Brazil | B1 | |
| US11696308B2 | United States of America | B2 | |
| US2023284238A1 | United States of America | A1 | |
| US11963196B2 | United States of America | B2 | |
| US2024237006A1 | United States of America | A1 | |
| US12267852B2 | United States of America | B2 |
Numbers
- Publication
- 2697347
- Publication, DOCDB
- 2697347
- Publication, EPODOC
- ES2697347T
- Application
- 17182318
- Application, DOCDB
- 17182318
- Application, EPODOC
- ES20170182318T
Titles2
- Spanish
- Asignación de recursos para transmisión de agrupaciones únicas y múltiples
- English
- Allocation of resources for transmission of single and multiple groupings
Classification
- CPC, 6
- H04L5/001
- H04W72/23
- H04W72/04
- H04L5/0044
- H04L5/0094
- H04W72/0446
- IPC, 1
- H04W72 04