Size indication for feedback signaling

Abstract

A method for operating a user device (10) in a radio access network is described. The method comprises transmitting feedback signals using a range of feedback resources, determined from a received feedback size indication and a received scheduling allocation indication. This range of feedback resources is part of a range of signaling resources configured for transmission on the user device (10). This description also covers related devices and methods.

Description

Technical Field

[0001] This disclosure pertains to wireless communication technology, in particular in the context of feedback signaling in a radio access network (RAN).Background

[0002] In modern communication systems, feedback signaling is provided in a network for improved communication. Such feedback signaling may for example comprise measurement report signaling and / or acknowledgement signaling, e.g. in the context of acknowledgement processes. Based on feedback signaling, it may for example be determined whether data blocks have to be retransmitted (e.g., in the context of acknowledgement signaling processing), or which transmission mode / operational characteristics are suitable for reported channel conditions (e.g., in the context of measurement reporting). Feedback signaling is usually not provided as only transmission in a given transmission timing structure, but in parallel and / or multiplexed (e.g., time and / or frequency multiplexed) with other transmissions or signalings, e.g. data transmission and / or other control signaling. Moreover, feedback signaling may pertain to a plurality of different and changing processes, accordingly, it may be quite variable (e.g., in size) over time, for example between different occurrences and / or different transmission timing structures like slots or subframes.

[0003] Documents WO 2017 / 030489 A1, WO 2016 / 123372 A1, US 2016 / 294529 A1 and US 2016 / 285608 A1 discuss aspects of feedback signaling for radio access networks.Summary

[0004] An object of this disclosure is to provide approaches allowing improved handling of feedback signaling, in particular in the context of radio access networks. The approaches may in particular enable reliable and predictable handling of feedback signaling, respectively corresponding signaling structures. The approaches are particularly advantageously implemented in a 5 th< Generation (5G) telecommunication network or 5G radio access technology or network (RAT / RAN), in particular according to 3GPP (3 rd< Generation Partnership Project, a standardisation organization). A suitable RAN may in particular be a RAN according to NR, for example release 15 or later, or LTE Evolution.

[0005] The present invention is represented by the independent claims. Preferred embodiments are iterated in the dependent claims.Brief description of the drawings

[0006] The drawings are provided to illustrate concepts and approaches described herein, and are not intended to limit their scope. The drawings comprise: Figure 1, showing a slot interval with PUSCH and PUCCH resource ranges; Figure 2, showing an exemplary radio node, implemented as user equipment; and Figure 3, showing an exemplary radio node, implemented as network node. Detailed description

[0007] In the following, concepts and approaches are described in the context of NR technology by way of example.

[0008] Operation of NR requires the transmission of various control information from the UE to the network. Examples of uplink control information (UCI) are hybrid-ARQ acknowledgements (acknowledgement signaling) and channel-state information (measurement reporting). The UCI can be transmitted on for example a separate control channel, PUCCH, occurring for example at the end of a slot or during a slot, and / or multiplexed with data and transmitted on PUSCH ("UCI on PUSCH").

[0009] Multiplexing of UCI and data can be provided in different ways, e.g. based on rate matching, i.e. to adjust the set of coded bits representing the data to "make room" for the UCI. The UE and network should have a common understanding of whether UCI is present or not, otherwise the network may not be able to decode the uplink data.

[0010] Inconsistency between the UE and network regarding UCI presence can occur due to a missed scheduling assignment, e.g. in a previous slot. In such a case, the network expects the UE to transmit an acknowledgement relating to the downlink data transmission but, since the UE did not receive the scheduling assignment in the earlier slot (or earlier in the same slot, in some applications), it will not include any hybrid-ARQ feedback.

[0011] The amount (size) of feedback information, in particular the amount of hybrid-ARQ acknowledgements, may vary from time to time. One reason for variations may be a varying number of downlink transmissions (across slots and / or carriers) to acknowledge in one uplink slot. Sometimes there is only a single transport block to acknowledge, sometimes there could be multiple transport blocks (several downlink slots, several carriers) or even multiple code block groups (a transport block consists of multiple code blocks and it has been agreed to have the possibility for per-code-block-group acknowledgements).

[0012] Using a single bit in the uplink grant to indicate presence / absence of UCI may not be efficient in case of a dramatically varying UCI size. The largest possible UCI size might have to be used even if only a few UCI bits are to be transmitted.

[0013] There is proposed to allow indication of multiple feedback signaling or UCI sizes or size ranges, e.g. no, small, medium, and large feedback signaling size / UCI. This may facilitate reduced uplink overhead. To each such size classification, a size in resources and / or bits or bit rate may be associated, e.g. configured or configurably.

[0014] Including information in the scheduling grant about the amount of resource to reserve for UCI (a feedback size indication) is suggested for some variants. A small number of bits, e.g. indicating no / small / medium / large sizes or size classes / ranges, could be sufficient in order not to increase the DCI overhead too much. However, direct indication with an index of parameter indicating a size out of a continuous range of sizes (e.g., integer) could be conceived for more precision with slightly larger overhead. The size / s associated to classes or ranges may be configured or configurable, e.g. based on higher layer control signaling, e.g. MAC or RRC signaling.

[0015] The UE may reserve resources for UCI based on the size information received with the size indication. In case of hybrid-ARQ acknowledgements not requiring all the resources, the UE could pad the message to fill up the reserved resources, e.g. if one or more scheduling assignments have been missed and / or the UE provides acknowledgment information for a lower number of processes than expected according to the scheduling assignments transmitted by the network (representing a network node). Similarly, if the amount of hybrid-ARQ information to feed back is larger than the amount of resources reserved, the UE need to follow some predefined rule on how to compress the information, for example by grouping transmission together and reporting ACK only if all the members of the group are correctly received.

[0016] In addition to the size information received in the DCI, the amount of resources to use for UCI could depend on the configuration, e.g. a measurement configuration. For example, if periodic CSI reports have been configured and a report is to be transmitted in the slot, the UE knows that "large" means more bits for UCI on PUSCH than "large" received in a slot with no periodic CSI reporting. The size information in the DCI could also be interpreted in combination with other DCI information, e.g. if the DCI indicates transmission of an aperiodic CSI report in this slot, the size information should be interpreted differently than in absence of an aperiodic CSI being requested.

[0017] In the following, an example is outlined how a few bits in the UL grant can indicate the required resources for UCI "relative" to the amount of scheduled assignments: Assuming each TB (Transport Block), or generally a data block subject to an acknowledgement signaling process, would require the same amount of feedback (in bits), the ACK / NACK feedback size can be calculated as N DL assignments · N with N DL assignments the number of DL assignments and N the number of HARQ feedback bits needed per data block / transport block. The UL grant (scheduling grant) could contain a small bit field representing parity bits P generated by a code / function which takes the number of scheduled assignments N DL assignments as input. The number of received assignments (which could be smaller than the number of scheduled assignments N DL assignments due to errors) together with the parity bits P would allow the UE to determine the number of scheduled assignments N DL assignments or at least a useful estimate thereof. If the UE knows N DL assignments (or the estimate) and N it can determine the size of resources the e / gNB assumes for UCl / the feedback resource range. Error cases can be avoided. P may be considered as feedback size indication in this case.

[0018] One possible choice to calculate the bit field P could be based on modulo arithmetic: A bit field size of 2 bits (which can represent 0 to 3) may be assumed for bit field P. The code point 0 (bit field setting 00) may be reserved to indicate "do not include ACK / NACK". The bit field can then be calculated as P = 1 + (N DL assignments mod 4) for N DL assignments >0 and included in the UL grant. The UE receives assignments and calculates .

[0019] N̂ DL assignments is correct for up to 2 missed assignments and represent a useful estimate. If P would be of 3 bit size, up to 6 missed assignments could be corrected. In Table 1, the cases are shown up to 5 scheduled assignments and if the UE misses 1 DL assignment (P is 2 bit wide). Table 2 shows the same example with 2 missed assignments, respectively. Each assignment may be considered to pertain to one acknowledgment signaling process. The modulo function is assumed to form a ring over 0 to 2 in this case also for negative operators. A radio node like a UE may be adapted to determine the feedback size, respectively an associated frequency resource range, as described herein.

[0020] Other functions than the mod-function to calculate P can be envisioned as well as long as they enable to calculate N DL assignmets or a useful estimate based on and P. Table 1:N DL assignments PN̂ DL assignments 000With code point 0:N̂ DL assignments = 012012312312342345345 Table 2: N DL assignments PN̂ DL assignments 000With code point 0:N̂ DL assignments = 012012302311342245335

[0021] As indicated in Figure 1, simultaneous transmission of PUSCH and PUCCH may be considered, such that PUCCH may be inside the scheduled PUSCH region and / or neighbor it in time and / or frequency space. Figure 1 indicates how PUCCH is moved into the PUSCH region for illustration, as comparison to separate / non-simultaneous PUSCH and PUCCH. Also in this case, the e / gNB must be aware that UCI is included within the scheduled PUSCH region and on how many resources. The same approaches as outlined above also apply here.

[0022] In particular, Figure 1 shows how, in case of simultaneous transmission of PUSCH and PUCCH, PUCCH resources are moved inside PUSCH for simultaneous transmission of PUSCH and PUCCH (the dashed PUCCH is not transmitted). The region of PUCCH may be considered to represent the feedback resource range, and the region of PUSCH may in this case be considered to represent a signaling resource range.

[0023] Figure 2 schematically shows a radio node, in particular a terminal or wireless device 10, which may in particular be implemented as a UE (User Equipment). Radio node 10 comprises processing circuitry (which may also be referred to as control circuitry) 20, which may comprise a controller connected to a memory. Any module of the radio node 10, e.g. a communicating module or determining module, may be implemented in and / or executable by, the processing circuitry 20, in particular as module in the controller. Radio node 10 also comprises radio circuitry 22 providing receiving and transmitting or transceiving functionality (e.g., one or more transmitters and / or receivers and / or transceivers), the radio circuitry 22 being connected or connectable to the processing circuitry. An antenna circuitry 24 of the radio node 10 is connected or connectable to the radio circuitry 22 to collect or send and / or amplify signals. Radio circuitry 22 and the processing circuitry 20 controlling it are configured for cellular communication with a network, e.g. a RAN as described herein, and / or for sidelink communication. Radio node 10 may generally be adapted to carry out any of the methods of operating a radio node like terminal or UE disclosed herein; in particular, it may comprise corresponding circuitry, e.g. processing circuitry, and / or modules.

[0024] Figure 3 schematically show a radio node 100, which may in particular be implemented as a network node 100, for example an eNB or gNB or similar for NR. Radio node 100 comprises processing circuitry (which may also be referred to as control circuitry) 120, which may comprise a controller connected to a memory. Any module, e.g. transmitting module and / or receiving module and / or configuring module of the node 100 may be implemented in and / or executable by the processing circuitry 120. The processing circuitry 120 is connected to control radio circuitry 122 of the node 100, which provides receiver and transmitter and / or transceiver functionality (e.g., comprising one or more transmitters and / or receivers and / or transceivers). An antenna circuitry 124 may be connected or connectable to radio circuitry 122 for signal reception or transmittance and / or amplification. Node 100 may be adapted to carry out any of the methods for operating a radio node or network node disclosed herein; in particular, it may comprise corresponding circuitry, e.g. processing circuitry, and / or modules. The antenna circuitry 124 may be connected to and / or comprise an antenna array. The node 100, respectively its circuitry, may be adapted to perform any of the methods of operating a network node or a radio node as described herein.

[0025] The timing of a mini-slot may generally be configured or configurable, in particular by the network and / or a network node. The timing may be configurable to start and / or end at any symbol of the transmission timing structure, in particular one or more slots.

[0026] References to specific resource structures like transmission timing structure and / or symbol and / or slot and / or mini-slot and / or subcarrier and / or carrier may pertain to a specific numerology, which may be predefined and / or configured or configurable. A transmission timing structure may represent a time interval, which may cover one or more symbols. Some examples of a transmission timing structure are subframe, slot and mini-slot. A slot may comprise a predetermined, e.g. predefined and / or configured or configurable, number of symbols, e.g. 6 or 7, or 12 or 14. A mini-slot may comprise a number of symbols (which may in particular be configurable or configured) smaller than the number of symbols of a slot, in particular 1, 2, 3 or 4 symbols. A transmission timing structure may cover a time interval of a specific length, which may be dependent on symbol time length and / or cyclic prefix used. A transmission timing structure may pertain to, and / or cover, a specific time interval in a time stream, e.g. synchronized for communication. Timing structures used and / or scheduled for transmission, e.g. slot and / or mini-slots, may be scheduled in relation to, and / or synchronized to, a timing structure provided and / or defined by other transmission timing structures. Such transmission timing structures may define a timing grid, e.g., with symbol time intervals within individual structures representing the smallest timing units. Such a timing grid may for example be defined by slots or subframes (wherein in some cases, subframes may be considered specific variants of slots). A transmission timing structure may have a duration (length in time) determined based on the durations of its symbols, possibly in addition to cyclic prefix / es used. The symbols of a transmission timing structure may have the same duration, or may in some variants have different duration. The number of symbols in a transmission timing structure may be predefined and / or configured or configurable, and / or be dependent on numerology.

[0027] There is generally considered a program product comprising instructions adapted for causing processing and / or control circuitry to carry out and / or control any method described herein, in particular when executed on the processing and / or control circuitry. Also, there is considered a carrier medium arrangement carrying and / or storing a program product as described herein.

[0028] A carrier medium arrangement may comprise one or more carrier media. Generally, a carrier medium may be accessible and / or readable and / or receivable by processing or control circuitry. Storing data and / or a program product and / or code may be seen as part of carrying data and / or a program product and / or code. A carrier medium generally may comprise a guiding / transporting medium and / or a storage medium. A guiding / transporting medium may be adapted to carry and / or carry and / or store signals, in particular electromagnetic signals and / or electrical signals and / or magnetic signals and / or optical signals. A carrier medium, in particular a guiding / transporting medium, may be adapted to guide such signals to carry them. A carrier medium, in particular a guiding / transporting medium, may comprise the electromagnetic field, e.g. radio waves or microwaves, and / or optically transmissive material, e.g. glass fiber, and / or cable. A storage medium may comprise at least one of a memory, which may be volatile or non-volatile, a buffer, a cache, an optical disc, magnetic memory, flash memory, etc.

[0029] In general, a numerology and / or subcarrier spacing may indicate the bandwidth (in frequency domain) of a subcarrier of a carrier, and / or the number of subcarriers in a carrier and / or the numbering of the subcarriers in a carrier. Different numerologies may in particular be different in the bandwidth of a subcarrier. In some variants, all the subcarriers in a carrier have the same bandwidth associated to them. The numerology and / or subcarrier spacing may be different between carriers in particular regarding the subcarrier bandwidth. A symbol time length, and / or a time length of a timing structure pertaining to a carrier may be dependent on the carrier frequency, and / or the subcarrier spacing and / or the numerology. In particular, different numerologies may have different symbol time lengths.

[0030] Signaling may generally comprise one or more symbols and / or signals and / or messages. A signal may comprise one or more bits. An indication may represent signaling, and / or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and / or represented by a message. Signaling, in particular control signaling, may comprise a plurality of signals and / or messages, which may be transmitted on different carriers and / or be associated to different signaling processes, e.g. representing and / or pertaining to one or more such processes and / or corresponding information. An indication may comprise signaling, and / or a plurality of signals and / or messages and / or may be comprised therein, which may be transmitted on different carriers and / or be associated to different acknowledgement signaling processes, e.g. representing and / or pertaining to one or more such processes.

[0031] Uplink or sidelink signaling may be OFDMA (Orthogonal Frequency Division Multiple Access) or SC-FDMA (Single Carrier Frequency Division Multiple Access) signaling.

[0032] Downlink signaling may in particular be OFDMA signaling. However, signaling is not limited thereto (Filter-Bank based signaling may be considered one alternative).

[0033] A radio node may generally be considered a device or node adapted for wireless and / or radio (and / or microwave) frequency communication, and / or for communication utilising an air interface, e.g. according to a communication standard.

[0034] A radio node may be a network node, or a user equipment or terminal. A network node may be any radio node of a wireless communication network, e.g. a base station and / or gNodeB (gNB) and / or eNodeB (eNB) and / or relay node and / or micro / nano / pico / femto node and / or other node, in particular for a RAN as described herein.

[0035] The terms wireless device, user equipment (UE) and terminal may be considered to be interchangeable in the context of this disclosure. A wireless device, user equipment or terminal may represent an end device for communication utilising the wireless communication network, and / or be implemented as a user equipment according to a standard. Examples of user equipments may comprise a phone like a smartphone, a personal communication device, a mobile phone or terminal, a computer, in particular laptop, a sensor or machine with radio capability (and / or adapted for the air interface), in particular for MTC (Machine-Type-Communication, sometimes also referred to M2M, Machine-To-Machine), or a vehicle adapted for wireless communication. A user equipment or terminal may be mobile or stationary.

[0036] A radio node may generally comprise processing circuitry and / or radio circuitry. Circuitry may comprise integrated circuitry. Processing circuitry may comprise one or more processors and / or controllers (e.g., microcontrollers), and / or ASICs (Application Specific Integrated Circuitry) and / or FPGAs (Field Programmable Gate Array), or similar. It may be considered that processing circuitry comprises, and / or is (operatively) connected or connectable to one or more memories or memory arrangements. A memory arrangement may comprise one or more memories. A memory may be adapted to store digital information. Examples for memories comprise volatile and non-volatile memory, and / or Random Access Memory (RAM), and / or Read-Only-Memory (ROM), and / or magnetic and / or optical memory, and / or flash memory, and / or hard disk memory, and / or EPROM or EEPROM (Erasable Programmable ROM or Electrically Erasable Programmable ROM). Radio circuitry may comprise one or more transmitters and / or receivers and / or transceivers (a transceiver may operate or be operable as transmitter and receiver, and / or may comprise joint or separated circuitry for receiving and transmitting, e.g. in one package or housing), and / or may comprise one or more amplifiers and / or oscillators and / or filters, and / or may comprise, and / or be connected or connectable to antenna circuitry and / or one or more antennas.

[0037] Any one or all of the modules disclosed herein may be implemented in software and / or firmware and / or hardware. Different modules may be associated to different components of a radio node, e.g. different circuitries or different parts of a circuitry. It may be considered that a module is distributed over different components and / or circuitries. A program product as described herein may comprise the modules related to a device on which the program product is intended (e.g., a user equipment or network node) to be executed (the execution may be performed on the associated circuitry).

[0038] A radio access network may be a wireless communication network, and / or a Radio Access Network (RAN) in particular according to a communication standard. A communication standard may in particular a standard according to 3GPP and / or 5G, e.g. according to NR or LTE, in particular LTE Evolution.

[0039] A wireless communication network may be and / or comprise a Radio Access Network (RAN), which may be and / or comprise any kind of cellular and / or wireless radio network, which may be connected or connectable to a core network. The approaches described herein are particularly suitable for a 5G network, e.g. LTE Evolution and / or NR (New Radio), respectively successors thereof. A RAN may comprise one or more network nodes. A network node may in particular be a radio node adapted for radio and / or wireless and / or cellular communication with one or more terminals. A terminal may be any device adapted for radio and / or wireless and / or cellular communication with or within a RAN, e.g. a user equipment (UE) or mobile phone or smartphone or computing device or vehicular communication device or device for machine-type-communication (MTC), etc. A terminal may be mobile, or in some cases stationary.

[0040] Transmitting in downlink may pertain to transmission from the network or network node to the terminal. Transmitting in uplink may pertain to transmission from the terminal to the network or network node. Transmitting in sidelink may pertain to (direct) transmission from one terminal to another. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered communication directions. In some variants, uplink and downlink may also be used to described wireless communication between network nodes, e.g. for wireless backhaul and / or relay communication and / or (wireless) network communication for example between base stations or similar network nodes, in particular communication terminating at such. It may be considered that backhaul and / or relay communication and / or network communication is implemented as a form of sidelink communication or similar thereto.

[0041] Signaling may generally comprise one or more signals and / or one or more symbols. Control information or a control information message or corresponding signaling (control signaling) may be transmitted on a control channel, e.g. a physical control channel, which may be a downlink channel or (or a sidelink channel in some cases, e.g. one UE scheduling another UE). For example, control information / allocation information may be signaled by a network node on PDCCH (Physical Downlink Control Channel) and / or a PDSCH (Physical Downlink Shared Channel) and / or a HARQ-specific channel. Acknowledgement signaling, e.g. as a form of uplink control information, may be transmitted by a terminal on a PUCCH (Physical Uplink Control Channel) and / or PUSCH (Physical Uplink Shared Channel) and / or a HARQ-specific channel. Multiple channels may apply for multi-component / multi-carrier indication or signaling.

[0042] Transmitting signaling, in particular control signaling, e.g. comprising or representing acknowledgement signaling and / or resource requesting information, may comprise encoding and / or modulating. Encoding and / or modulating may comprise error detection coding and / or forward error correction encoding and / or scrambling. Receiving control signaling may comprise corresponding decoding and / or demodulation. Error detection coding may comprise, and / or be based on, parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check). Forward error correction coding may comprise and / or be based on for example turbo coding and / or Reed-Muller coding, and / or polar coding and / or LDPC coding (Low Density Parity Check). The type of coding used may be based on the channel (e.g., physical channel) the coded signal is associated to.

[0043] An indication generally may explicitly and / or implicitly indicate the information it represents and / or indicates. Implicit indication may for example be based on position and / or resource used for transmission. Explicit indication may for example be based on a parametrisation with one or more parameters, and / or one or more index or indices, and / or one or more bit patterns representing the information. It may in particular be considered that control signaling as described herein, based on the utilised resource sequence, implicitly indicates the control signaling type.

[0044] A resource element may generally describe the smallest individually usable and / or encodable and / or decodable and / or modulatable and / or demodulatable time-frequency resource, and / or may describe a time-frequency resource covering a symbol time length in time and a subcarrier in frequency. A signal may be allocatable and / or allocated to a resource element. A subcarrier may be a subband of a carrier, e.g. as defined by a standard. A carrier may define a frequency and / or frequency band for transmission and / or reception. In some variants, a signal (jointly encoded / modulated) may cover more than one resource elements. A resource element may generally be as defined by a corresponding standard, e.g. NR or LTE. As symbol time length and / or subcarrier spacing (and / or numerology) may be different between different symbols and / or subcarriers, different resource elements may have different extension (length / width) in time and / or frequency domain, in particular resource elements pertaining to different carriers.

[0045] A resource generally may represent a time-frequency and / or code resource, on which signaling, e.g. according to a specific format, may be communicated, for example transmitted and / or received, and / or be intended for transmission and / or reception.

[0046] A border symbol may generally represent a starting symbol for transmitting or an ending symbol for receiving. A starting symbol may in particular be a starting symbol of uplink or sidelink signaling, for example control signaling or data signaling. Such signaling may be on a data channel or control channel, e.g. a physical channel, in particular a physical uplink shared channel (like PUSCH) or a sidelink data or shared channel, or a physical uplink control channel (like PUCCH) or a sidelink control channel. If the starting symbol is associated to control signaling (e.g., on a control channel), the control signaling may be in response to received signaling (in sidelink or downlink), e.g. representing acknowledgement signaling associated thereto, which may be HARQ or ARQ signaling. An ending symbol may represent an ending symbol (in time) of downlink or sidelink transmission or signaling, which may be intended or scheduled for the radio node or user equipment. Such downlink signaling may in particular be data signaling, e.g. on a physical downlink channel like a shared channel, e.g. a PDSCH (Physical Downlink Shared Channel). A starting symbol may be determined based on, and / or in relation to, such an ending symbol.

[0047] Configuring a radio node, in particular a terminal or user equipment, may refer to the radio node being adapted or caused or set to operate according to the configuration. Configuring may be done by another device, e.g., a network node (for example, a radio node of the network like a base station or eNodeB) or network, in which case it may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and / or comprise one or more instruction pertaining to a configuration, e.g. a configuration for transmitting and / or receiving on allocated resources, in particular frequency resources. A radio node may configure itself, e.g., based on configuration data received from a network or network node. A network node may utilise, and / or be adapted to utilise, its circuitry / ies for configuring. Allocation information may be considered a form of configuration data.

[0048] Generally, configuring may include determining configuration data representing the configuration and providing it to one or more other nodes (parallel and / or sequentially), which may transmit it further to the radio node (or another node, which may be repeated until it reaches the wireless device). Alternatively, or additionally, configuring a radio node, e.g., by a network node or other device, may include receiving configuration data and / or data pertaining to configuration data, e.g., from another node like a network node, which may be a higher-level node of the network, and / or transmitting received configuration data to the radio node. Accordingly, determining a configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities, which may be able to communicate via a suitable interface, e.g., an X2 interface in the case of LTE or a corresponding interface for NR. Configuring a terminal may comprise scheduling downlink and / or uplink transmissions for the terminal, e.g. downlink data and / or downlink control signaling and / or DCI and / or uplink signaling, in particular acknowledgement signaling, and / or configuring resources and / or a resource pool therefor.

[0049] A resource structure may be considered to be neighbored in frequency domain by another resource structure, if they share a common border frequency, e.g. one as an upper frequency border and the other as a lower frequency border. Such a border may for example be represented by the upper end of a bandwidth assigned to a subcarrier n, which also represents the lower end of a bandwidth assigned to a subcarrier n+1.

[0050] A resource structure may be considered to be neighbored in time domain by another resource structure, if they share a common border time, e.g. one as an upper (or right in the figures) border and the other as a lower (or left in the figures) border. Such a border may for example be represented by the end of the symbol time interval assigned to a symbol n, which also represents the beginning of a symbol time interval assigned to a symbol n+1.

[0051] Generally, a resource structured being neighbored by another resource structure in a domain may also be referred to as abutting and / or bordering the other resource structure in the domain.

[0052] A resource structure may general represent a structure in time and / or frequency domain, in particular representing a time interval and a frequency interval. A resource structure may comprise and / or be comprised of resource elements, and / or the time interval of a resource structure may comprise and / or be comprised of symbol time interval / s, and / or the frequency interval of a resource structure may comprise and / or be comprised of subcarrier / s. A resource element may be considered an example for a resource structure, a slot or mini-slot or a Physical Resource Block (PRB) or parts thereof may be considered others. A resource structure may be associated to a specific channel, e.g. a PUSCH or PUCCH, in particular resource structure smaller than a slot or PRB.

[0053] A carrier may generally represent a frequency range or band and / or pertain to a central frequency and an associated frequency interval. It may be considered that a carrier comprises a plurality of subcarriers. A carrier may have assigned to it a central frequency or center frequency interval, e.g. represented by one or more subcarriers (to each subcarrier there may be generally assigned a frequency bandwidth or interval). Different carriers may be non-overlapping, and / or may be neighboring in frequency domain.

[0054] It should be noted that the term "radio" in this disclosure may be considered to pertain to wireless communication in general, and may also include wireless communication utilising microwave and / or millimeter and / or other frequencies, in particular between 100 MHz or 1 GHz, and 100 GHz or 20 or 10 GHz. Such communication may utilise one or more carriers.

[0055] A radio node, in particular a network node or a terminal, may generally be any device adapted for transmitting and / or receiving radio and / or wireless signals and / or data, in particular communication data, in particular on at least one carrier. The at least one carrier may comprise a carrier accessed based on a LBT procedure (which may be called LBT carrier), e.g., an unlicensed carrier. It may be considered that the carrier is part of a carrier aggregate.

[0056] Receiving or transmitting on a cell or carrier may refer to receiving or transmitting utilizing a frequency (band) or spectrum associated to the cell or carrier. A cell may generally comprise and / or be defined by or for one or more carriers, in particular at least one carrier for UL communication / transmission (called UL carrier) and at least one carrier for DL communication / transmission (called DL carrier). It may be considered that a cell comprises different numbers of UL carriers and DL carriers.

[0057] Alternatively, or additionally, a cell may comprise at least one carrier for UL communication / transmission and DL communication / transmission, e.g., in TDD-based approaches.

[0058] A channel may generally be a logical, transport or physical channel. A channel may comprise and / or be arranged on one or more carriers, in particular a plurality of subcarriers. A channel carrying and / or for carrying control signaling / control information may be considered a control channel, in particular if it is a physical layer channel.

[0059] In general, a symbol may represent and / or be associated to a symbol time length, which may be dependent on the carrier and / or subcarrier spacing and / or numerology of the associated carrier. Accordingly, a symbol may be considered to indicate a time interval having a symbol time length in relation to frequency domain. A symbol time length may be dependent on a carrier frequency and / or bandwidth and / or numerology and / or subcarrier spacing of or associated to a symbol. Accordingly, different symbols may have different symbol time lengths.

[0060] A sidelink may generally represent a communication channel (or channel structure) between two UEs and / or terminals, in which data is transmitted between the participants (UEs and / or terminals) via the communication channel, e.g. directly and / or without being relayed via a network node. A sidelink may be established only and / or directly via air interface / s of the participant, which may be directly linked via the sidelink communication channel. In some variants, sidelink communication may be performed without interaction by a network node, e.g. on fixedly defined resources and / or on resources negotiated between the participants. Alternatively, or additionally, it may be considered that a network node provides some control functionality, e.g. by configuring resources, in particular one or more resource pool / s, for sidelink communication, and / or monitoring a sidelink, e.g. for charging purposes.

[0061] Sidelink communication may also be referred to as device-to-device (D2D) communication, and / or in some cases as ProSe (Proximity Services) communication, e.g. in the context of LTE. A sidelink may be implemented in the context of V2x communication (Vehicular communication), e.g. V2V (Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure) and / or V2P (Vehicle-to-Person). Any device adapted for sidelink communication may be considered a user equipment or terminal.

[0062] A sidelink communication channel (or structure) may comprise one or more (e.g., physical or logical) channels, e.g. a PSCCH (Physical Sidelink Control CHannel, which may for example carry control information like an acknowledgement position indication, and / or a PSSCH (Physical Sidelink Shared CHannel, which for example may carry data and / or acknowledgement signaling). It may be considered that a sidelink communication channel (or structure) pertains to and / or used one or more carrier / s and / or frequency range / s associated to, and / or being used by, cellular communication, e.g. according to a specific license and / or standard. Participants may share a (physical) channel and / or resources, in particular in frequency domain and / or related to a frequency resource like a carrier) of a sidelink, such that two or more participants transmit thereon, e.g. simultaneously, and / or time-shifted, and / or there may be associated specific channels and / or resources to specific participants, so that for example only one participant transmits on a specific channel or on a specific resource or specific resources, e.g., in frequency domain and / or related to one or more carriers or subcarriers.

[0063] A sidelink may comply with, and / or be implemented according to, a specific standard, e.g. a LTE-based standard and / or NR. A sidelink may utilise TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex) technology, e.g. as configured by a network node, and / or preconfigured and / or negotiated between the participants. A user equipment may be considered to be adapted for sidelink communication if it, and / or its radio circuitry and / or processing circuitry, is adapted for utilising a sidelink, e.g. on one or more frequency ranges and / or carriers and / or in one or more formats, in particular according to a specific standard. It may be generally considered that a Radio Access Network is defined by two participants of a sidelink communication. Alternatively, or additionally, a Radio Access Network may be represented, and / or defined with, and / or be related to a network node and / or communication with such a node.

[0064] Communication or communicating may generally comprise transmitting and / or receiving signaling. Communication on a sidelink (or sidelink signaling) may comprise utilising the sidelink for communication (respectively, for signaling). Sidelink transmission and / or transmitting on a sidelink may be considered to comprise transmission utilising the sidelink, e.g. associated resources and / or transmission formats and / or circuitry and / or the air interface. Sidelink reception and / or receiving on a sidelink may be considered to comprise reception utilising the sidelink, e.g. associated resources and / or transmission formats and / or circuitry and / or the air interface. Sidelink control information (e.g., SCI) may generally be considered to comprise control information transmitted utilising a sidelink.

[0065] Generally, carrier aggregation (CA) may refer to the concept of a radio connection and / or communication link between a wireless and / or cellular communication network and / or network node and a terminal or on a sidelink comprising a plurality of carriers for at least one direction of transmission (e.g. DL and / or UL), as well as to the aggregate of carriers. A corresponding communication link may be referred to as carrier aggregated communication link or CA communication link; carriers in a carrier aggregate may be referred to as component carriers (CC). In such a link, data may be transmitted over more than one of the carriers and / or all the carriers of the carrier aggregation (the aggregate of carriers). A carrier aggregation may comprise one (or more) dedicated control carriers and / or primary carriers (which may e.g. be referred to as primary component carrier or PCC), over which control information may be transmitted, wherein the control information may refer to the primary carrier and other carriers, which may be referred to as secondary carriers (or secondary component carrier, SCC). However, in some approaches, control information may be send over more than one carrier of an aggregate, e.g. one or more PCCs and one PCC and one or more SCCs.

[0066] A transmission may generally pertain to a specific channel and / or specific resources, in particular with a starting symbol and ending symbol in time, covering the interval therebetween. A scheduled transmission may be a transmission scheduled and / or expected and / or for which resources are scheduled or provided or reserved. However, not every scheduled transmission has to be realized. For example, a scheduled downlink transmission may not be received, or a scheduled uplink transmission may not be transmitted due to power limitations, or other influences (e.g., a channel on an unlicensed carrier being occupied). A transmission may be scheduled for a transmission timing substructure (e.g., a mini-slot, and / or covering only a part of a transmission timing structure) within a transmission timing structure like a slot. A border symbol may be indicative of a symbol in the transmission timing structure at which the transmission starts or ends.

[0067] Predefined in the context of this disclosure may refer to the related information being defined for example in a standard, and / or being available without specific configuration from a network or network node, e.g. stored in memory, for example independent of being configured. Configured or configurable may be considered to pertain to the corresponding information being set / configured, e.g. by the network or a network node.

[0068] A mini-slot may be transmitted and / or received based on a configuration.

[0069] A configuration, like a mini-slot configuration and / or structure configuration, may schedule transmissions, e.g. for the time / transmissions it is valid, and / or transmissions may be scheduled by separate signaling or separate configuration, e.g. separate RRC signaling and / or downlink control information signaling. It should be noted that downlink control information or specifically DCI signaling may be considered physical layer signaling, in contrast to higher layer signaling like MAC (Medium Access Control) signaling or RRC layer signaling. The higher the layer of signaling is, the less frequent / the more time / resource consuming it may be considered, at least partially due to the information contained in such signaling having to be passed on through several layers, each layer requiring processing and handling.

[0070] A scheduled transmission and / or mini-slot may pertain to a specific channel, in particular a physical uplink shared channel, a physical uplink control channel, or a physical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and / or may pertain to a specific cell and / or carrier aggregation. A corresponding configuration, e.g. scheduling configuration or symbol configuration may pertain to such channel, cell and / or carrier aggregation.

[0071] A configuration may be a configuration indicating timing, and / or be represented or configured with corresponding configuration data. A configuration may be embedded in, and / or comprised in, a message or configuration or corresponding data, which may indicate and / or schedule resources, in particular semi-persistently and / or semi-statically.

[0072] It may be considered that the scheduled transmission represents transmission on a physical channel, in particular a shared physical channel, for example a physical uplink shared channel or physical downlink shared channel. For such channels, semi-persistent configuring may be particularly suitable.

[0073] A control region of a transmission timing structure may be an interval in time for intended or scheduled or reserved for control signaling, in particular downlink control signaling, and / or for a specific control channel, e.g. a physical downlink control channel like PDCCH. The interval may comprise, and / or consist of, a number of symbols in time, which may be configured or configurable, e.g. by (UE-specific) dedicated signaling (which may be single-cast, for example addressed to or intended for a specific UE), e.g. on a PDCCH, or RRC signaling, or on a multicast or broadcast channel. In general, the transmission timing structure may comprise a control region covering a configurable number of symbols. It may be considered that in general the border symbol is configured to be after the control region in time.

[0074] The duration of a symbol of the transmission timing structure may generally be dependent on a numerology and / or carrier, wherein the numerology and / or carrier may be configurable. The numerology may be the numerology to be used for the scheduled transmission.

[0075] Scheduling a device, or for a device, and / or related transmission or signaling, may be considered comprising, or being a form of, configuring the device with resources, and / or of indicating to the device resources, e.g. to use for communicating. Scheduling may in particular pertain to a transmission timing structure, or a substructure thereof (e.g., a slot or a mini-slot, which may be considered a substructure of a slot). It may be considered that a border symbol may be identified and / or determined in relation to the transmission timing structure even if for a substructure being scheduled, e.g. if an underlying timing grid is defined based on the transmission timing structure. Signaling indicating scheduling may comprise corresponding scheduling information and / or be considered to represent or contain configuration data indicating the scheduled transmission and / or comprising scheduling information. Such configuration data or signaling may be considered a resource configuration or scheduling configuration. It should be noted that such a configuration (in particular as single message) in some cases may not be complete without other configuration data, e.g. configured with other signaling, e.g. higher layer signaling. In particular, the symbol configuration may be provided in addition to scheduling / resource configuration to identify exactly which symbols are assigned to a scheduled transmission. A scheduling (or resource) configuration may indicate transmission timing structure / s and / or resource amount (e.g., in number of symbols or length in time) for a scheduled transmission.

[0076] A scheduled transmission may be transmission scheduled, e.g. by the network or network node. Transmission may in this context may be uplink (UL) or downlink (DL) or sidelink (SL) transmission. A device, e.g. a user equipment, for which the scheduled transmission is scheduled, may accordingly be scheduled to receive (e.g., in DL or SL), or to transmit (e.g.,in UL or SL) the scheduled transmission. Scheduling transmission may in particular be considered to comprise configuring a scheduled device with resource / s for this transmission, and / or informing the device that the transmission is intended and / or scheduled for some resources. A transmission may be scheduled to cover a time interval, in particular a successive number of symbols, which may form a continuous interval in time between (and including) a starting symbol and an ending symbols. The starting symbol and the ending symbol of a (e.g., scheduled) transmission may be within the same transmission timing structure, e.g. the same slot. However, in some cases, the ending symbol may be in a later transmission timing structure than the starting symbol, in particular a structure following in time. To a scheduled transmission, a duration may be associated and / or indicated, e.g. in a number of symbols or associated time intervals. In some variants, there may be different transmissions scheduled in the same transmission timing structure. A scheduled transmission may be considered to be associated to a specific channel, e.g. a shared channel like PUSCH or PDSCH.

[0077] A transmission timing structure may comprise a plurality of symbols, and / or define an interval comprising several symbols (respectively their associated time intervals). In the context of this disclosure, it should be noted that a reference to a symbol for ease of reference may be interpreted to refer to the time domain projection or time interval or time component or duration or length in time of the symbol, unless it is clear from the context that the frequency domain component also has to be considered. Examples of transmission timing structures include slot, subframe, mini-slot (which also may be considered a substructure of a slot), slot aggregation (which may comprise a plurality of slots and may be considered a superstructure of a slot), respectively their time domain component.

[0078] A transmission timing structure may generally comprise a plurality of symbols defining the time domain extension (e.g., interval or length or duration) of the transmission timing structure, and arranged neighboring to each other in a numbered sequence. A timing structure (which may also be considered or implemented as synchronisation structure) may be defined by a succession of such transmission timing structures, which may for example define a timing grid with symbols representing the smallest grid structures. A transmission timing structure, and / or a border symbol or a scheduled transmission may be determined or scheduled in relation to such a timing grid. A transmission timing structure of reception may be the transmission timing structure in which the scheduling control signaling is received, e.g. in relation to the timing grid. A transmission timing structure may in particular be a slot or subframe or in some cases, a mini-slot.

[0079] In this disclosure, for purposes of explanation and not limitation, specific details are set forth (such as particular network functions, processes and signaling steps) in order to provide a thorough understanding of the technique presented herein. It will be apparent to one skilled in the art that the present concepts and aspects may be practiced in other variants and variants that depart from these specific details.

[0080] For example, the concepts and variants are partially described in the context of Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or New Radio mobile or wireless communications technologies; however, this does not rule out the use of the present concepts and aspects in connection with additional or alternative mobile communication technologies such as the Global System for Mobile Communications (GSM). While the following variants will partially be described with respect to certain Technical Specifications (TSs) of the Third Generation Partnership Project (3GPP), it will be appreciated that the present concepts and aspects could also be realized in connection with different Performance Management (PM) specifications.

[0081] Moreover, those skilled in the art will appreciate that the services, functions and steps explained herein may be implemented using software functioning in conjunction with a programmed microprocessor, or using an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA) or general purpose computer. It will also be appreciated that while the variants described herein are elucidated in the context of methods and devices, the concepts and aspects presented herein may also be embodied in a program product as well as in a system comprising control circuitry, e.g. a computer processor and a memory coupled to the processor, wherein the memory is encoded with one or more programs or program products that execute the services, functions and steps disclosed herein.

[0082] The scope of protection of the invention is defined in the appended set of claims. AbbreviationExplanationCDMCode Division MultiplexCQIChannel Quality InformationCRCCyclic Redundancy CheckDCIDownlink Control InformationDFTDiscrete Fourier TransformDM-RSDemodulation Reference SignalFDMFrequency Division MultiplexHARQHybrid Automatic Repeat RequestOFDMOrthogonal Frequency Division MultiplexPAPRPeak to Average Power RatioPUCCHPhysical Uplink Control ChannelPRBPhysical Resource BlockRRCRadio Resource ControlUCIUplink Control InformationUEUser Equipment

[0083] Abbreviations may be considered to follow 3GPP usage if applicable.

Claims

1. Method of operating a user equipment (10) in a radio access network, the method comprising receiving, from a radio node (10, 100), a downlink transmission indicated by a received scheduling assignment indication, transmitting feedback signaling utilising a feedback resource range in response to the downlink transmission to the radio node (10, 100), the feedback resource range being determined based on a received feedback size indication and the received scheduling assignment indication, wherein the feedback resource range is a part of a signaling resource range configured to the user equipment (10) for transmission, wherein the feedback size indication is included in a scheduling grant scheduling the signaling resource range for feedback signaling on a Physical Uplink Control Channel, PUCCH, wherein the feedback size indication and the scheduling assignment indication are transmitted in different messages.

2. A user equipment (10) for a radio access network, the user equipment (10) being adapted for receiving, from a radio node (10, 100), a downlink transmission indicated by a received scheduling assignment indication, transmitting feedback signaling utilising a feedback resource range in response to the downlink transmission to the radio node (10, 100), the feedback resource range being determined based on a received feedback size indication and the received scheduling assignment indication, wherein the feedback resource range is a part of a signaling resource range configured to the user equipment (10) for transmission, wherein the feedback size indication is included in a scheduling grant scheduling the signaling resource range for feedback signaling on a Physical Uplink Control Channel, PUCCH, wherein the feedback size indication and the scheduling assignment indication are transmitted in different messages.

3. Method or device according to one of the preceding claims, wherein the feedback signaling comprises and / or represents acknowledgement signaling.

4. Method or device according to one of the preceding claims, wherein the feedback size indication is represented by two or more bits.

5. Method or device according to one of the preceding claims, wherein a scheduling assignment indication is included in a scheduling assignment message.

6. Method or device according to one of the preceding claims, wherein the scheduling grant configures the signaling resource range.

7. Method or device according to one of the preceding claims, wherein the scheduling assignment indication indicates a counter value or number of scheduling assignments.

8. Method or device according to one of the preceding claims, wherein the feedback signaling neighbors PUSCH transmission in frequency.

9. A computer program product comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method of any one of claims 1 or 3 to 8.

10. A computer-readable storage medium comprising instructions which, when executed by a computer, cause the computer to carry out the method of any one of claims 1 or 3 to 8.

Images