Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals

Definitions

• the invention relates to transmission of control information in a
• LTE Long Term Evolution
• OFDM Orthogonal Frequency Division Multiplexing
• DFT-spread Discrete Fourier Transform
• OFDM Orthogonal Frequency Division Multiplexing
• the basic LTE downlink physical resource can thus be seen as a time-frequency grid as illustrated in figure 1, where each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval.
• resource allocation in LTE is typically described in terms of resource blocks, where a resource block corresponds to one slot of 0.5 ms in the time domain and 12 contiguous subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain, starting with 0 from one end of the system bandwidth.
• Downlink transmissions are dynamically scheduled in LTE, i.e., in each subframe, a base station transmits control information concerning which mobile terminals data is transmitted to, and upon which resource blocks the data is transmitted in the current downlink subframe. Typically, this control signaling is transmitted in the first 1, 2, 3 or 4 OFDM symbols in each subframe. A downlink system with 4 OFDM symbols as control region is illustrated in figure 4.
• hybrid-ARQ is used, where, after receiving downlink data in a subframe, a mobile terminal attempts to decode it and reports to a base station whether the decoding was successful or not. When the decoding has been successful, the report comprises an "ACK" (ACKnowledgment), and when the decoding was not successful, the report comprises a "NAK" (Negative
• the base station can retransmit the erroneous data.
• LTE uplink control signaling from a mobile terminal to a base station comprises:
• the L1/L2 (Layerl/Layer2) control information i.e., channel-status reports, hybrid-ARQ acknowledgments and scheduling requests
• uplink resources i.e. resource blocks, specifically assigned for uplink L1/L2 control on a Physical Uplink Control CHannel (PUCCH).
• PUCCH Physical Uplink Control CHannel
• these resources are located at the edges of the total available cell uplink transmission bandwidth.
• Each such resource consists of 12 subcarriers, i.e., one resource block, within each of the two slots of an uplink subframe.
• these frequency resources may be shifted between different parts of the spectrum at the slot boundary, using so called frequency hopping, as illustrated in figure 5.
• Figure 5 shows an example of frequency hopping in the uplink, with one resource consisting of 12 subcarriers at the upper part of the spectrum within the first slot of a subframe and an equally sized resource at the lower part of the spectrum during the second slot of the subframe. If more resources are needed for the uplink L1/L2 control signaling, e.g. in case of very large overall transmission bandwidth supporting a large number of users, additional resource blocks can be assigned next to the previously assigned resource blocks.
• the location at the edges maximizes the frequency diversity experienced by the control signaling
• the bandwidth of one resource block during one subframe is larger than the control signaling needs of a single terminal. Therefore, to efficiently exploit the resources set aside for control signaling, multiple terminals can share the same resource block. This is done by assigning the different terminals different orthogonal phase rotations of a cell-specific length-12 frequency-domain sequence and/or different orthogonal time-domain covers covering the subframes within a slot or subframe.
• the LTE Release-8 standard supports bandwidths up to 20 MHz. In order to meet the IMT-Advanced requirements, bandwidths larger than 20 MHz need to be supported. However, one important requirement is to assure backward
• FIG. 7 shows a schematic view illustrating five component carriers 702-710 of 20MHz each, together forming an aggregated bandwidth 700 of 100MHz.
• CC component carrier
• Carrier aggregation implies that an LTE-Advanced terminal can receive multiple CCs, where each CC has, or is at least able to have, the same structure as a
• DCI Downlink Control Information
• DCI messages for downlink assignments contain, among other things, resource block assignment, modulation and coding scheme related parameters, hybrid-ARQ redundancy version, etc.
• most DCI formats for downlink assignments also contain a bit field for carrying Transmit Power Control (TPC) commands. These TPC commands are used to control the uplink power of the corresponding Physical Uplink Control Channel (PUCCH) that is used by terminals to transmit the hybrid-ARQ feedback.
• TPC Transmit Power Control
• an LTE-Advanced terminal could be assigned more resources than a legacy terminal, and on several component carriers, increases the need for control information, e.g. since more resources need to be addressed, and more feedback needs to be transmitted, as compared to a Release-8 scenario.
• the number of ACK/NAK bits to be transmitted in the uplink as a response to a downlink assignment/transmission is limited to lbit for single code word, and 2 bits for dual code word transmission, while in Release-10, when a mobile terminal, also denoted UE (User Equipment), is assigned e.g.
• UE User Equipment
• the ACK/NAKs associated with these component carriers will require no less than 3 bits assuming single code word, and 6 bits assuming dual code word transmission on all component carriers, respectively.
• the number of required feedback bits increases even further, to 5 and 7bits,
• the component carriers can be of different bandwidths, e.g. 5, 10 or 20 M Hz, and thus comprise different amounts of resources, which need to be addressed.
• a wide component carrier will therefore require more control bits for addressing the resources within the carrier than a comparatively narrow component carrier.
• a mobile terminal In LTE, a mobile terminal has to blindly decode DCI control messages to establish if it is currently scheduled. To reduce the complexity, a mobile terminal may be instructed to only monitor, i.e. blindly decode, DCI message formats of certain payload sizes. Forcing a mobile terminal to monitor DCI formats with a large variety of payload sizes increases the number of blind decodings a mobile terminal has to perform and thus also the mobile terminal complexity.
• control messages and e.g. address fields of equal size In order to maintain or reduce blind detection, it is desirable to have control messages and e.g. address fields of equal size. This implies that an address field suitable for addressing the resources within a 5 MHz component carrier will be too scarce for addressing the resources within a 20 MHz component carrier, and an address field large enough to address the resources within a 20 MHz component carrier will be unnecessarily large for addressing the resources within a 5 MHz component carrier. Thus, a too small addressing space will only allow for a rough addressing in wide CCs, while a larger addressing space will waste resources when used for relatively narrow component carriers.
• a method is provided in a network node.
• information bits related to power control of a physical uplink control channel are allocated in a bit field for power control, in a message on a first physical downlink control channel associated with a first downlink component carrier.
• other control information bits, not related to power control are allocated in a bit field, corresponding to the bit field used for power control in the message on the first physical downlink control channel, in a message on a second physical downlink control channel associated with a second one of said at least two downlink component carriers.
• the allocated control information is then transmitted to the mobile station.
• an arrangement in a network node.
• the arrangement comprises a functional unit adapted to determine if resources on at least two downlink component carriers are being assigned to a mobile terminal at the same time.
• the arrangement further comprises a functional allocating unit adapted to allocate bits related to power control of a physical uplink control channel, in a bit field for power control in a message to be transmitted on a first physical downlink control channel associated with a first downlink component carrier.
• the functional allocating unit is further adapted to allocate bits when it has been determined that resources on at least two downlink component carriers are being assigned to a mobile terminal, allocate other control information bits not related to power control in a bit field, corresponding to the bit field used for power control in the message on the first physical downlink control channel, in a message on a second physical downlink control channel associated with a second one of said at least two downlink component carriers.
• the arrangement further comprises a functional unit, adapted to transmit the allocated control information to the mobile terminal being assigned the resources on the at least two downlink component carriers
• a method is provided in a mobile terminal.
• bits related to power control of a physical uplink control channel are obtained from a bit field for power control in a message on a first physical downlink control channel associated with a first downlink component carrier.
• other control information bits not related to power control are obtained from a bit field, corresponding to the bit field for power control in the message on the first physical downlink control channel, in a message on a second physical downlink control channel associated with a second one of said at least two downlink component carriers.
• the obtained other control information not related to power control is then used in the mobile terminal for locating information related to downlink or uplink transmissions.
• an arrangement in a mobile terminal.
• the arrangement comprises a functional unit adapted to determine if resources on at least two downlink component carriers have been assigned to the mobile terminal at the same time.
• the arrangement further comprises a functional obtaining unit adapted to obtain bits related to power control, from a bit field for power control in a message on a first physical downlink control channel associated with a first downlink component carriers.
• the functional obtaining unit is further adapted to obtain, when it has been determined that resources on at least two downlink component carriers have been assigned to the mobile terminal, other control information bits not related to power control from a bit field,
• the arrangement further comprises a functional unit, adapted to use said obtained other control information not related to power control for locating information related to downlink or uplink transmissions.
• the method and arrangement according to the third and fourth aspect may be used for supporting the reduction of downlink overhead in a wireless
• control information bits not related to power control could be indicators to PUCCH or PUSCH resources; extensions of the resource assignment; or extension to other parameters that do not exist or are smaller in the message format used on the PDCCH conveying the bits related to power control.
• the identity of the PDCCH conveying the true TPC command is then determined in the mobile terminal in a corresponding way.
• the identity of the physical downlink control channel which is to convey the bits related to power control could be configured or determined according to e.g. a set of rules. This identity could be explicitly or implicitly signaled from a network node to a mobile terminal.
• Figure 1 is a schematic view illustrating an LTE time-frequency grid, according to the prior art.
• Figure 2 is a schematic view illustrating an LTE radio frame, according to the prior art.
• Figure 3 is a schematic view illustrating the location of certain downlink channels in LTE, according to the prior art.
• Figure 4 is a schematic view illustrating a downlink LTE subframe, according to the prior art.
• FIG. 5 is a schematic view illustrating a shift of a physical uplink control channel (PUCCH) in LTE, according to the prior art.
• PUCCH physical uplink control channel
• Figure 6 is a schematic view illustrating the location of different uplink channels in LTE, according to the prior art.
• Figure 7 is a schematic view illustrating carrier aggregation, according to the prior art.
• Figure 8 is a schematic view illustrating LTE carriers of different bandwidth and the location of control information, according to the prior art.
• Figure 9 is a flow chart illustrating procedure steps executed in a network node, according to an embodiment.
• Figure 10 is a block diagram illustrating an embodiment of an arrangement in a network node, according to an embodiment.
• Figure 11 is a flow chart illustrating procedure steps executed in a mobile terminal, according to an embodiment.
• Figure 12 is a block diagram illustrating an embodiment of an arrangement in a mobile terminal, according to an embodiment.
• Figure 13 is a flow chart illustrating procedure steps executed in a network node, according to an embodiment.
• Figure 14 is a block diagram illustrating an embodiment of an arrangement in a network node, according to an embodiment.
• this bit field is used for conveying a TPC command in a DCI message, i.e. the bit field where a legacy terminal would expect to find a TPC command.
• this bit field could be used to convey other relevant information in certain situations, which will be explained in more detail later.
• bit field described above comprises certain bits, which may be referred to as the "available TPC bits” or the “former TPC bits”, when used for conveying other relevant information than power control commands.
• control information other than power control commands refers to "control information other than power control commands”, and may also be denoted “control information not related to power control” or “non-redundant control information”.
• non- redundant control information is used to distinguish the information from the redundant power control commands, which would otherwise be conveyed in the bit field described above.
• legacy used for example in expressions like “legacy terminals”, is used as referring to entities which operate according to a previously released version of a certain standard or protocol, such as for example Release-8 of LTE.
• LTE-Advanced used in expressions like “LTE-Advanced terminal” is here used as referring to entities which operate according to a more recent version of a standard or protocol, such as for example Release-10 of LTE.
• a control message on the PDCCH of the component carrier will comprise a transmission power command (TPC), which controls the transmit power of the PUCCH, which is to carry the feedback to e.g. how the downlink information is received.
• TPC transmission power command
• each of the PDCCHs associated with the respective component carriers will carry a control message comprising the bit field used for TPC commands. If the feedback related to the different component carriers are to be transmitted on different physical uplink control channels, it is adequate for each PDCCH associated with an assigned downlink component carrier to comprise a TPC-command.
• both symmetric and asymmetric uplink/downlink CC configurations are supported. For some of the configurations, the possibility to transmit the uplink control information on multiple PUCCHs or multiple uplink CCs may be considered. However, this option is likely to result in higher UE power consumption and a dependency on specific UE capabilities. This option may also create implementation issues due to inter- modulation products, and would lead to generally higher complexity for implementation and testing.
• the feedback control information for all assigned component carriers should be transmitted over the same physical uplink control channel or at least on the same uplink component carrier. Consequently, multiple TPC-commands, one for each assigned CC, would effectively try to control the transmit power of the same physical uplink control channel or the same uplink component carrier. Even if different physical uplink control channels on the same uplink component carrier are used a single TPC-command would be sufficient. At the best, this would imply a waste of resources due to redundancy, or, at the worst, lead to unpredictable behavior of a UE, due to conflicting TPC-commands.
• these freed former TPC-bits could be used for several alternatives. For example, these bits could be used to signal which PUCCH or PUSCH resources that should be used to convey the hybrid-ARQ bits of the corresponding downlink shared channel transmissions. It would also be possible to combine the former TPC-bits from more than one CC. For example, the former TPC-bits of all other CCs, i.e. all but the one carrying the true TPC command, could be combined, and together form a wider bit field. This wider bit field could be used for
• PUCCH or PUSCH resource addresses are explicitly signaled in therefore reserved bit fields, and the remaining part is signaled via the former TPC bit fields.
• implicit and explicit PUCCH or PUSCH resource signaling could be combined, e.g. by that some parts of the PUCCH or PUSCH resource addresses are explicitly signaled and the remaining part is implicitly indicated via, e.g. in which CC and/or in which control channel elements the PDCCH of the corresponding DL assignment is transmitted.
• Another possibility is to use the available former TPC bit fields to extend resource block assignments. This is especially useful if the true TPC command is sent on the CC having the narrowest downlink system bandwidth.
• the PDCCH of a CC could be located in another CC. Without restrictions on which downlink CC that could be scheduled from which downlink CC, the number of blind decodings could become very large, since a terminal has to monitor possible PDCCH candidates for each downlink CC on each downlink CC. If the CCs have different transmission bandwidths the control messages, i.e. the DCI messages in LTE, have different sizes resulting in an increased number of blind detections.
• a further possibility is to use the available former TPC bits to indicate which component carrier that is addressed by a certain PDCCH, in case one DL CC carries multiple PDCCHs associated with different CCs, respectively.
• one DL CC carries multiple PDCCHs associated with different CCs, respectively.
• the PDCCH associated with the DL CC carrying all of the PDCCHs includes the true TPC command.
• the other four PDCCHs could then include a 2 bit carrier indicator, indicating which of the four CCs that is addressed by the respective PDCCH.
• data is received in a step 902.
• the data could comprise e.g. mobile terminal reports related to the downlink channel conditions.
• the data is internal network node data, comprising information concerning component carrier assignments.
• the data correspond to data that should be transmitted to the mobile terminal.
• a next step 904 it is determined in a next step 904 if resources on at least two downlink component carriers are being assigned to a mobile terminal at the same time.
• resources on at least two downlink component carriers are being assigned 904:1 to a mobile terminal.
• predetermined number of bits related to power control of an physical uplink control channel are allocated, or assigned, in a next step 906, in a bit field for power control, in a message on a first physical downlink control channel associated with a first one of said at least two downlink component carriers.
• these bits are referred to as a TPC command, and the message is referred to as a DCI message.
• this is the true TPC command, but it may also be denoted differently, e.g. in other systems.
• bits related to power control are allocated in said bit field also when only resources on a single component carrier are assigned to a mobile terminal. Therefore, actions related to these bits could alternatively be performed in parallel to the described procedure, or before the evaluation of whether a mobile terminal has been assigned resources on more than one component carrier. Independently of where the allocating of power control bits is performed, a configuration, a set of rules or similar, concerning which CC that should carry the bits related to power control is required. The possibility of an alternative position of the action performed in step 906 is illustrated in figure 9 by that step 906 is outlined with a dashed line.
• a predetermined number of control information bits related to other relevant information not related to power control are allocated in the corresponding bit field normally used for power control, in a message on a second physical downlink control channel associated with at least a second one of said at least two downlink component carriers.
• These bits could be related e.g. to indicating certain PUCCH or PUSCH resources, to extending resource block assignments or to indicating which component carrier that is addressed by a certain PDCCH.
• the allocated control information is then transmitted in a step 910 to the mobile terminal being assigned the resources on the at least two downlink component carriers.
• the arrangement 1000 comprises a receiving unit 1002, which is adapted to receive signals transmitted from other network entities or internal information, depending on what functions that are considered to be comprised in the arrangement 1000.
• the arrangement further comprises a determining unit 1004, adapted to determine if resources on at least two downlink component carriers are being assigned to a mobile terminal at the same time, i.e. for simultaneous use.
• the arrangement further comprises an allocating unit 1006, adapted to, when it has been determined that resources on at least two downlink component carriers are being assigned to a mobile terminal, allocate a
• bits related to power control of an physical uplink control channel in a bit field for power control in a message on a first physical downlink control channel associated with a first one of said at least two downlink component carriers.
• these bits are referred to as a TPC command, and the message is referred to as a DCI message.
• These bits related to power control are allocated in said bit field also when only resources on a single component carrier are assigned to a mobile terminal. Thus, the action related to these bits could alternatively be performed in parallel with the described
• the allocating unit is further adapted to allocate a predetermined number of other relevant control information bits not related to power control in the corresponding bit field normally used for power control in a message on a second physical downlink control channel associated with at least a second one of said at least two downlink component carriers. That is, the allocating unit is adapted to place "non-power control" information in the bit field where a legacy terminal would expect to find a power control command.
• the bits not related to power control could be related e.g. to indicating certain PUCCH or PUSCH resources; to extending resource block assignments or to indicating which component carrier that is addressed by a certain PDCCH.
• the arrangement further comprises a transmitting unit 1008, adapted to transmit the allocated control information to the mobile terminal being assigned the resources on the at least two downlink component carriers.
• FIG. 10 is also illustrated a computer program product (CPP) 1014 which comprises instructions 1016, which when executed by a processor 1012, or similar, will cause the units 1002-1010 to perform their tasks according to any
• control data comprising downlink resource assignments is received in a step 1102.
• the assignments are determined 1104:1 to concern resources on at least two component carriers at the same time
• a predetermined number of bits related to power control of an physical uplink control channel are obtained, in a next step 1106, from the bit field for power control in a message received on a physical downlink control channel associated with a first one of said at least two downlink component carriers.
• the obtaining of power control bits, here placed in step 1106, is performed also when the
• step 1106 Independently of where the obtaining of power control bits is performed, a configuration, a set of rules or similar, concerning which CC that carries the bits related to power control is required.
• step 1106 is outlined with a dashed line.
• step 1108 a predetermined number of other relevant control information bits not related to power control are obtained from the corresponding bit field normally used for power control in a message received on a second physical downlink control channel associated with a second one of said at least two downlink component carriers.
• the obtained bits of other relevant control information not related to power control are then used in a step 1110 for locating information related to downlink or uplink transmissions. The locating of
• information could involve e.g. indicating certain PUCCH or PUSCH resources
• the arrangement 1200 comprises a receiving unit 1202, adapted to receive control messages comprising downlink resource assignments.
• the arrangement further comprises a determining unit 1204, adapted to determine whether the received assignments concern resources on more than one downlink component carrier at the same time.
• the arrangement further comprises an obtaining unit 1206, adapted to obtain a predetermined number of bits related to power control of a physical uplink control channel, from the bit field for power control in a message on a first physical downlink control channel associated with a first one of said at least two downlink component carriers.
• the obtaining unit 1206 is further adapted to obtain, when it is determined that the received assignments concern resources on more than one downlink component carrier at the same time, a predetermined number of other relevant control information bits not related to power control. These other relevant control information bits are obtained from the corresponding bit field normally used for power control, in a message on a second physical downlink control channel associated with a second one of said at least two downlink component carriers.
• the arrangement further comprises a utilizing unit 1208, adapted to use said obtained other relevant control information not related to power control for locating information related to downlink or uplink transmissions.
• the locating of information could involve e.g. indicating certain PUCCH or PUSCH resources;
• the arrangement may further comprise a transmitting unit 1210, adapted to transmit, e.g., reports related to the downlink channel conditions, to other network entities.
• FIG. 12 is also illustrated a computer program product (CPP) 1214 which comprises instructions 1216, which when executed by a processor 1212, or similar, will cause the units 1202-1210 to perform their tasks according to any
• the true power control command can be found. This could be configured, signaled or be determined based on a set of rules.
• An exemplary rule could be that the true power control command is conveyed on the PDCCH associated with the component carrier having a certain carrier index, or e.g. the lowest carrier index of the component carriers being assigned to the mobile terminal.
• Another exemplary rule could be based on the downlink system bandwidth, e.g. that the true power control command is conveyed on the PDCCH associated with the component carrier having the most narrow bandwidth of the component carriers being assigned to the mobile terminal.
• a combination of multiple rules could be used.
• the CC that is associated with the PDCCH which is to carry the true TPC command could be configured.
• Yet another alternative is to include information concerning the CC that is associated with the PDCCH which is to carry the true TPC command into an activation message, which is sent in order to activate a configured CC.
• the identity of the component carrier carrying the true power control command could be explicitly signaled to the mobile terminal or indicated by a combination of explicit and implicit signaling.
• a network node of the procedure for utilizing certain resources for conveying non-redundant control information in a wireless communication system supporting aggregation of component carriers will now be described with reference to figure 13.
• a TPC command is assigned in a next step 1304, to only one of the downlink control messages (DCIs) conveying the downlink assignments on the respective PDCCHs associated with the component carriers.
• DCIs downlink control messages
• the PDCCH which is to carry the true TPC command is explicitly configured or determined at the activation of a carrier, said PDCCH is determined, or identified, in a step 1306a.
• said PDCCH which is to carry the true TPC command is to be determined e.g. based on a set of rules
• said PDCCH is implicitly determined in a step 1306b.
• the determining in step 1306b could be based on a set of rules concerning e.g. the characteristics of the CC of which the PDCCH is to carry the true TPC command.
• the identity of the PDCCH which conveys the true TPC command is then obtained in the mobile terminal in a corresponding way.
• a step 1308 when appropriate, the bit fields in the DCIs on the remaining PDCCHs, corresponding to the bit field carrying the true TPC command, are applied, or used, to convey other relevant information, i.e. other than the TPC command.
• the arrangement 1400 comprises a first circuit 1402, adapted to assign, if it has been determined that multiple downlink component carriers (CCs) 1406 are simultaneously assigned to a mobile terminal 1408, a TPC command to only one of the Downlink Control Messages (DCIs) messages associated with the respective assigned component carriers, conveying the downlink assignments.
• CCs downlink component carriers
• DCIs Downlink Control Messages
• the circuit 1402 is further adapted to apply/use, where appropriate, the bit fields in the other DCI messages, corresponding to the bit field carrying the true TPC command, to convey other relevant information, i.e. other than the TPC command.
• the circuit 1402 could be adapted to select or determine this other relevant information, e.g. indicators to PUCCH or PUSCH resources; extensions of the resource assignment; or extension to other parameters that do not exist or are smaller in the DCI format used on the PDCCH conveying the true TPC command.
• the identity of the PDCCH conveying the true TPC command is then determined in the mobile terminal in a corresponding way.
• the identity of the PDCCH conveying the true TPC command could also be explicitly and/or implicitly signaled to the mobile terminal, as previously described.
• the arrangement 1400 may also comprise a second circuit 1404 adapted to perform at least one of: determine the PDCCH that is to carry the true TPC command when it is explicitly configured; and implicitly determine the PDCCH that is to carry the true TPC command.
• the implicit determining could be based on one or more of component carrier (CC) index, transmission bandwidth, and DCI formats configured on the different CCs, as previously mentioned.
• the circuit 1404 could have access to a set of rules assisting the determining.
• the first circuit 1402 could further be adapted to use the bit field
• the bit field carrying the true TPC command i.e. the one also referred to as the former TPC bit field, to accommodate the carrier indicator for the PDCCHs that are not transmitted on the component carrier which they address.
• FIG. 10 merely illustrate various functional units of the arrangements 1000, 1200 and 1400 in a logical sense.
• the functional units could also be denoted e.g. "modules” or “circuits", or be parts of circuits.
• the skilled person is free to implement these functions in practice using any suitable software and/or hardware means, such as e.g. ASICs (Application-Specific Integrated Circuit), FPGAs (Field-Programmable Gate Array) and DSPs (Digital Signal Processor).
• ASICs Application-Specific Integrated Circuit
• FPGAs Field-Programmable Gate Array
• DSPs Digital Signal Processor
• the procedure in a mobile terminal could also be described as follows: When a received assignment is determined to concern resources on at least two component carriers, the bits in a certain bit field in a message received over a first PDCCH are interpreted as power control bits, and the bits in a corresponding bit field in a message received over a second PDCCH are interpreted as other relevant control information, i.e. other than power control. Examples of such other control information is: an indication or part of an indication of PUCCH or PUSCH resources to be used for conveying e.g. H-ARQ related information; an indication or part of an indication of resource block assignments on a DL component carrier being assigned to the mobile terminal; and an indication of to which component carrier the PDCCH carrying the indication is associated. Other parts of the resource indications could be explicitly signaled e.g. in therefore reserved bit fields in control messages, and/or, be implicitly signaled or indicated, as described in connection with other embodiments.
• An exemplary advantage of the above embodiments is that overhead is reduced, since the total number of transmitted bits is kept constant while the amount of payload is increased. Furthermore, the situation is avoided where contradicting power control commands can be sent to the terminal leading to unpredictable terminal behavior.
• the invention also allows packing larger resource allocations/larger DCI formats into the payload size of smaller resource

Landscapes

• Engineering & Computer Science (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Mobile Radio Communication Systems (AREA)
• Radio Relay Systems (AREA)

Priority Applications (9)

Applications Claiming Priority (2)

Publications (1)

Family

ID=42357590

Family Applications (1)

Country Status (9)

Cited By (3)

Families Citing this family (21)

Family Cites Families (4)

• 2010
  • 2010-04-01 EP EP10718333.7A patent/EP2489145B1/en active Active
  • 2010-04-01 JP JP2012534140A patent/JP5613250B2/ja active Active
  • 2010-04-01 WO PCT/SE2010/050368 patent/WO2011046486A1/en not_active Ceased
  • 2010-04-01 ES ES10718333T patent/ES2789098T3/es active Active
  • 2010-04-01 ES ES19216471T patent/ES2940207T3/es active Active
  • 2010-04-01 PL PL19216471.3T patent/PL3731449T3/pl unknown
  • 2010-04-01 CN CN201080046971.XA patent/CN102577222B/zh active Active
  • 2010-04-01 DK DK10718333.7T patent/DK2489145T3/da active
  • 2010-04-01 PL PL10718333T patent/PL2489145T3/pl unknown
  • 2010-04-01 HU HUE10718333A patent/HUE048492T2/hu unknown
  • 2010-04-01 EP EP19216471.3A patent/EP3731449B1/en active Active
  • 2010-04-01 US US12/937,440 patent/US8472368B2/en active Active

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events