Data signalling in wireless communication network

Abstract

The disclosure pertains to a method of operating a radio node in a wireless communication network The method comprises communicating utilising data signalling, the data sig- nalling comprising and / or representing a set of code blocks, each code block representing a bit pattern comprising an integer number of bits, the data signalling spanning a set of allocation units in time domain, wherein at least one code block of the set of code blocks is split into a first portion associated to a first allocation unit of the set of allocation units, and into a second portion associated to a second allocation unit of the set of allocation units, wherein the first portion is in a first range in frequency domain, and the second portion is in a second range in frequency domain. The disclosure also pertains to related devices and methods.

Description

[0001] Data signalling in wireless communication network

[0002] Technical field

[0003] This disclosure pertains to wireless communication technology, in particular for high frequencies.

[0004] Background

[0005] For future wireless communication systems, use of higher frequencies is considered, which 5 allows large bandwidths to be used for communication. Also, lower timescales as transmission timing intervals may be available. Improved approaches for utilising such resources

[0006] may be desirable.

[0007] Summary

[0008] It is an object of this disclosure to provide approaches for improved signalling for wire- 10 less communication, in particular for utilising resources and / or providing reliable signal quality. The approaches described may be utilised for one or more different frequencies ranges. For example, they may be implemented for frequency ranges (e.g., carrier bandwidth and / or system bandwidth) for communication signalling of 1 GHz or more, 2GHz

[0009] or more, 5 GHz or more, or 6 GHz or more, or 10 GHz or more, and / or for millimeter 15 wave communication, in particular for radio carrier frequencies around and / or above 52.6

[0010] GHz, which may be considered high radio frequencies (high frequency) and / or millimetre waves. The carrier frequency / ies may be associated to FR1 or FR2, or be between 52.6

[0011] and 140 GHz, e.g. with a lower border between 52.6, 55, 60, 71 GHz and / or a higher

[0012] border between 71, 72, 90, 114, 140 GHz or higher, in particular between 55 and 90 GHz, 20 or between 60 and 72 GHz; however, higher frequencies may be considered, in particular frequency of 71GHz or 72GHz or above, and / or 100 GHz or above, and / or 140 GHz or above. The carrier frequency may in particular refer to a center frequency or maximum frequency of the carrier. The radio nodes and / or network described herein may operate

[0013] in wide-band, e.g. with a carrier bandwidth (or bandwidth or carrier aggregation) of 25 200MHz or 400MHz or more, in particular 1 GHz or more, or 2 GHz or more, or even

[0014] larger, e.g. 6 GHz or more, or 8 GHz or more; the scheduled or allocated bandwidth may

[0015] be the carrier bandwidth, or be smaller, e.g. depending on channel and / or procedure. In

[0016] some cases, operation may be based on an OFDM wave-form or a SC-FDM wave-form

[0017] (e.g., downlink and / or uplink), in particular a FDF-SC-FDM-based wave-form. However, 30 operation based on a single carrier wave-form, e.g. SC-FDE (which may be pulse-shaped

[0018] or Frequency Domain Filtered, e.g. based on modulation scheme and / or MGS), may be considered for downlink and / or uplink. In general, different wave-forms may be used for different communication directions. Communicating using or utilising a carrier and / or

[0019] beam may correspond to operating using or utilising the carrier and / or beam, and / or 35

[0020] P113137WO01 1 / 79may comprise transmitting on the carrier and / or beam and / or receiving on the carrier and / or beam. Operation may be based on and / or associated to a numerology, which may indicate a sub-carrier spacing and / or duration of an allocation unit and / or an equivalent thereof, e.g., in comparison to an OFDM based system. A sub-carrier spacing or equivalent frequency interval may for example correspond to 30kHZ or more, e.g., 120kHz, or 40 480 kHz, or 960 kHz, or 1920 kHz, e.g. representing the bandwidth of a sub-carrier or equivalent.

[0021] The approaches are particularly advantageously implemented in a future 6th Generation

[0022] (6G) telecommunication network or 6G radio access technology or network (RAT / RAN),

[0023] in particular according to 3GPP (3rd Generation Partnership Project, a standardisation 45 organization). A suitable RAN may in particular be a RAN according to NR, for example

[0024] release 18 or later, or LTE Evolution. However, the approaches may also be used with

[0025] other RAT, for example future 5.5G systems or IEEE based systems.

[0026] There is disclosed a method of operating a radio node in a wireless communication network. The method comprises communicating utilising data signalling, the data signalling 50 comprising and / or representing a set of code blocks. Each code block represents a bit pattern comprising an integer number of bits, the data signalling spanning a set of allocation units in time domain. At least one code block of the set of code blocks is split

[0027] into a first portion associated to a first allocation unit of the set of allocation units, and

[0028] into a second portion associated to a second allocation unit of the set of allocation units, 55 wherein the first portion is associated to, and / or is in, a first range in frequency domain,

[0029] and the second portion is associated to, and / or is in, a second range in frequency domain.

[0030] Furthermore, a radio node for a wireless communication network is described. The radio

[0031] node is adapted for communicating utilising data signalling, the data signalling comprising and / or representing a set of code blocks. Each code block represents a bit pattern 60 comprising an integer number of bits, the data signalling spanning a set of allocation

[0032] units in time domain. At least one code block of the set of code blocks is split into a first portion associated to a first allocation unit of the set of allocation units, and into a second portion associated to a second allocation unit of the set of allocation units, wherein the

[0033] first portion is associated to, and / or is in, a first range in frequency domain, and the 65 second portion is associated to, and / or is in, a second range in frequency domain.

[0034] Approaches described herein may facilitate improved frequency diversity for data signalling, in particular on a code block level and / or for cases in which a code block has to

[0035] be split between allocation units.

[0036] The radio node may be a transmitting radio node, or a receiving radio node. Communicat- 70

[0037] P113137WO01 2 / 79ing may comprise transmitting or receiving of the data signalling. In some cases, the radio node may be a wireless device, or a network node. Communicating may comprise, and / or

[0038] be based on (e.g., for transmitting) interleaving and / or encoding and / or modulating, or

[0039] (e.g., for receiving) de-interleaving and / or decoding and / or demodulating.

[0040] A sub-pattern of a bit pattern may comprise one or more bits of the bit pattern; a sub- 75 pattern of a bit pattern may be considered a portion of the bit pattern and / or of the

[0041] code block. A bit-pattern may comprise and / or represent a bit sequence; a sub-pattern

[0042] may represent a sub-sequence of the bit sequence. Different portions and / or sub-patterns and / or sub-sequences may be non-overlapping and / or consist of non-shared bits of the

[0043] bit pattern (allowing for the obvious fact that all bits will have a value taken from the 80 set of values available for a bit, e.g., 0 and 1, or true and false, or similar, depending on

[0044] the convention used for bit values). In some cases, a first portion may have the same size

[0045] as the second portion, or a different size. The size of a bit pattern and / or sub-pattern

[0046] and / or portion may represent the number of bits of the (sub-)pattern or portion. The

[0047] same or different portion sizes may be associated to portions of different code blocks, e.g., 85 within the same allocation unit, and / or on different allocation units.

[0048] It may be considered that a bit pattern and / or sub-pattern may comprise and / or may

[0049] be interleaved based on interleaving sub-patterns; a portion may comprise one or more interleaving sub-patterns (e.g., complete interleaving sub-patterns); different interleaving

[0050] sub-pattern may be associated to different sub-carriers in frequency domain and / or differ- 90 ent layers or ranks of transmission. Signalling, and / or a bit-pattern, and / or code block, and / or portion or sub-pattern of a code block, may be considered to be associated to, and / or span one or more allocation units if the corresponding signalling or part thereof

[0051] (e.g., representing and / or indicating and / or carrying the (sub-)pattern and / or code block

[0052] and / or bit / s thereof) is transmitted and / or present on the allocation unit in time domain, 95 and / or intended to be so, e.g., at least for 50% or more, or 75% or more, or 90 % or more

[0053] of the duration of the allocation unit.

[0054] A range in frequency domain may refer to a contiguous range and / or part of the spectrum,

[0055] e.g., an interval in frequency domain. A range may comprise and / or span and / or consist of

[0056] a number of sub-carriers; the number of sub-carriers of a range may be an integer number 100 of 1 or more. A range may comprise a set of sub- carriers, wherein each sub- carrier may be neighbouring to one or two sub-carriers of the set (in frequency domain), and / or at most

[0057] two sub-carriers of the set may be neighbouring to only one sub-carrier (e.g., the lowest and highest sub-carrier in frequency domain). Within a range, bits or interleaving sub-patterns

[0058] of a the same code-block may be arranged on non-neighbouring sub-carriers, e.g., with a 105 gap of NCB-1 sub-carriers, wherein NCB may represent the number of code blocks carried

[0059] P113137WO01 3 / 79in the same allocation unit. For example, different bits and / or interleaving sub-patterns may be arranged of non-neighbouring sub-carriers. Sub-carriers in gaps between such

[0060] non-neighbouring sub-carriers may be associated to interleaving sub-patterns of one or

[0061] more other code blocks of the set of code blocks. Such an arrangement may be considered 110 for each code block associated to the same allocation unit, such that for example a combstructure in frequency domain may be considered, wherein combs of the same size for different code blocks are interleaved to fill the sub-carriers in the range, at least for a part

[0062] of the range, e.g., for 70% or more, or 90% of the range. A range in general may represent

[0063] a part of a carrier bandwidth, and / or of an allocatable bandwidth (e.g., allocatable for 115 transmission and / or reception of the data signalling). Different ranges may comprise different sub-carriers, and / or in some cases, there may be no shared sub-carrier / s between ranges. Complete and / or non-split code blocks may be on a range comprising the first

[0064] range and the second range. Should there be two code blocks split in one allocation units,

[0065] they may have different first ranges and second ranges from each other; in particular, a 120 portion of one of them may be in a first range being the higher frequency range of its

[0066] first and second range, and a portion of the second one may be in a first range being

[0067] the lower frequency range of its first and second range. This may correspond to the first partial / split / incomplete code block corresponding to a second portion of a previous code

[0068] block that could not fit on a preceding allocation unit being provided, and a first portion 125 of a code block being provided that cannot be fit at the end and has to be carried over

[0069] to a next allocation unit.

[0070] One or more, or each, of the allocation units (of the set) may carry and / or associated a number of code blocks, which may be an integer number and / or may be 2 or more, or

[0071] at least 3 or at least 4; for different allocation units, the number may be the same or 130 different. Two or more of the code blocks associated to the same allocation unit, and / or

[0072] to different allocation units, may have the same or different sizes. In some scenarios,

[0073] one, or two, of the code blocks may be incomplete on one of the allocation units (e.g.,

[0074] split between allocation units) and / or only one portion of two or more portions may be associated to one specific allocation unit; an incomplete code block may be considered 135 as one of the number of code blocks for each of the associated allocation units. In some

[0075] cases, one or more of the code blocks may be associated to exactly one allocation unit, and / or one or more of the code blocks may be associated to at most two allocation units, and / or no code block may be associated to more than two allocation units. The set

[0076] of allocation units may represent an interval in time domain, e.g., without gap or hole, 140 and / or may comprise an integer number of allocation units, which may be contiguous in

[0077] time domain; each allocation unit of the set may be neighbouring to one or two allocation

[0078] units of the set (in time domain), and / or at most two allocation units of the set may be

[0079] P113137WO01 4 / 79neighbouring to only one allocation unit of the set (e.g., the lowest and highest allocation unit in time domain). The set of allocation units may comprise two or more allocation 145 units, and / or may comprise the first allocation unit, and the second allocation unit (it

[0080] may comprise more than these). The first and second allocation unit may be neighbouring

[0081] in time domain, or may be non-neighbouring in some scenarios, e.g., in TDD operation

[0082] when a transmission direction change is interspersed, and / or should other transmission

[0083] be pre-empted. 150

[0084] The set of allocation units may correspond to a transmission time interval, and / or a transmission timing structure, and / or may carry one or exactly one data block (e.g., in

[0085] total, or per transmission layer or rank, and / or on the same carrier and / or same frequency

[0086] range (which may comprise the first and second range)).

[0087] It may be considered that a split code block may also be referred to as a partial code 155 block or incomplete code block, considering it will be distributed between two allocation

[0088] units; viewed over two allocation units, the complete code block may be provided. Unless

[0089] stated otherwise, a complete code block may refer to a code block completely mapped

[0090] to, and / or carried on, and / or associated to a single allocation unit. Signalling and / or

[0091] bits and / or a sub-pattern or code block or portion in a frequency range may refer to the 160 sub-carrier / s to which such is / are associated to and / or carried on being in the frequency

[0092] range. A range in frequency domain may be referred to as frequency (domain) range or frequency (domain) interval.

[0093] It may be considered that the first range does not overlap with the second range (e.g., in frequency domain). Thus, transmission diversity in frequency domain may be improved. 165 In some cases, the first and second range may be neighbouring in frequency domain.

[0094] In some cases, the first portion may be mapped to the first range based on and / or by interleaving, and / or the second portion may be mapped to the second range based on

[0095] and / or by interleaving. Interleaving may be performed by an interleaver. In some cases,

[0096] an interleaver may operate for each allocation unit, and / or there may be a sub- interleaver, 170 which may operate for an allocation unit individually (e.g., such that code blocks are interleaved in frequency domain for an allocation unit; non- fitting portion / s of a code

[0097] block may then be treated separately for another allocation unit. Multiple sub-interleavers

[0098] may be utilised in parallel, e.g., one for each allocation unit of the set of allocation units.

[0099] Interleaving, for a code-block, may be frequency-domain interleaving first; time-domain- 175 interleaving may be only for code blocks that do not fit completely on one allocation unit

[0100] (one or more code blocks may be completely on the same allocation unit).

[0101] To each allocation unit, there may be associated at least one code block. Efficient utilising

[0102] P113137WO01 5 / 79of time-domain resources may be provided.

[0103] It may be considered that the code blocks of the set of code blocks are associated to 180 the same data block, e.g., part of the same transport block or CBB. Interleaving and / or frequency domain diversity may be provided on data block and / or code block level, and / or parallel processing may be easy for signalling as described herein.

[0104] The first allocation unit and the second allocation unit may be neighbouring in time domain. This may facilitate transmission and / or processing with low latency. 185

[0105] It may be considered that the first range and / or the second range may comprise an integer number of sub-carriers, wherein sub-patterns of bits of a code block may be associated

[0106] to different sub-carriers; the sub-patterns may be interleaving sub-patterns. The ranges

[0107] may comprise the same or different numbers of sub-carriers. The sub-carriers in the same and / or different ranges may be on the same carrier, and / or may have the same numerology 190 and / or bandwidth.

[0108] In some cases, it may be considered that no more than two code blocks are split on the

[0109] first allocation unit and / or the second allocation unit. Such split code blocks may fill up available resources that are not sufficient to carry a full code block, optimising resource utilisation. 195

[0110] It may be considered that code blocks may be interleaved per allocation unit and / or may

[0111] be interleaved in frequency domain, for an allocation unit, and / or in frequency domain

[0112] before interleaving in time domain and / or in a second allocation unit. This may allow

[0113] fast processing and / or low latency.

[0114] In some cases, it may be considered a bit pattern of a, and / or at least one, and / or 200 each, code block may comprise error detection bits, e.g., a CRC, which may pertain to information bits of the code block. This may allow separate decoding of a code blocks

[0115] with low latency.

[0116] Bits of the code blocks may be interleaved in interleaving sub-patterns, wherein each interleaving sub-pattern may comprise an integer number NIS of bits. NIS may be de- 205 pendent on a modulation scheme and / or modulation and coding scheme, which may be utilised for transmission of the data signalling. It may be considered that NIS may be dependent on a rank of transmission and / or number of layers used for transmission. An interleaving sub-pattern may be considered an n-tuple, and / or may comprise a number of

[0117] bit that may be carried on one sub-carrier and / or in one modulation symbol, optionally 210 multiplied with the number of layers and / or transmission rank.

[0118] P113137WO01 6 / 79The bits of the code blocks may be interleaved based on a rectangular interleaver, and / or based on interleaving sub-patterns of different code blocks alternatingly, e.g., providing interleaving combs.

[0119] The method may be a method of operating a transmitting radio node in a wireless com- 215 munication network. The method may comprise transmitting data signalling utilising a plurality of transmission sources. The radio node may be a transmitting radio node for

[0120] a wireless communication network , which may be adapted for data signalling utilising

[0121] a plurality of transmission sources. The data signalling in general may represent a plurality of code blocks, e .g., the set of code blocks. Modulation symbols of a modulation 220 symbol sequence may be mapped to the plurality of transmission sources in c-tuples. The modulation symbol sequence may represent the plurality of code blocks, c may be dependent on, and / or based on, and / or represent, and / or indicate, the modulation used for transmitting the signalling.

[0122] The data signalling may be considered to carry and / or represent the code blocks, and / or 225 modulation symbols representing the information of the code blocks, e.g. information or payload bits and / or error coding bits, e.g. CRC and / or FEC bits. Each of the code blocks

[0123] may comprise payload bits and / or error correction coding bits and / or error detection

[0124] coding bits (e.g., FEC and / or CRC, respectively). A modulation symbol sequence may be considered to represent a plurality of code blocks if the modulation symbols of the sequence 230 represent and / or carry the bits of the code blocks, e.g. associated to a representation

[0125] in constellation space. The bits may be mapped to modulation symbols based on the modulation (or modulation scheme, or MCS) being used. A modulation may in general

[0126] be associated to, and / or represented by, a modulation scheme, or a modulation and

[0127] coding scheme (MCS), and / or may be indicated by, and / or indexed to a table, e.g. a 235 MCS table. An order of the modulation may indicate the possible values (e.g., associated

[0128] to positions in constellation space) represented by a modulation symbol according to the modulation. Larger orders (associated to higher modulations) may allow larger values,

[0129] and may carry more bits per symbol. Mapping to a plurality of transmission sources

[0130] based on c-tuples may correspond to consecutive c-tuples (each c-tuple consisting of c 240 consecutive modulation symbols) of the sequence being mapped to different layers; in particular, neighbouring c-tuples of the sequence may be mapped to different layers. The number of transmission sources may be 2 or larger, or 3 or larger, or 4 or larger, c may

[0131] be an integer number, e.g. 1 or larger. Different values of c may be associated to different modulations. It may be considered that transmission associated to all transmission sources 245 uses the same modulation and / or MCS, and / or is intended for the same receiving radio

[0132] node, c-tuples of modulation symbols associated or mapped to a transmission source

[0133] may be considered to be transmitted by the source and / or utilising the source, and / or

[0134] P113137WO01 7 / 79carried by the transmission source, e.g. a layer. In general, each c-tuple with c being even may comprise or consist of one or more pairs of interlinked modulation symbols, e.g. if 250 interlinking modulation is used.

[0135] Multi-layer or multi-transmission source transmission may be considered, e.g. for providing transmission diversity. In particular for interlinking modulation, approaches may facilitate mapping of interlinked modulation symbols to the same layer, e.g. for maintaining low PAPR. 255

[0136] It may be considered that for (e.g., at least two, or three or more) different sets of modulations, and / or for different (e.g., at least two, or three or more) modulations, c is different. Thus, flexibility in mapping may be provided. For a first set of modulations, c

[0137] may be 2 and / or c may be even. This may allow keeping an interlinking relation between modulation symbols alive, e.g. between a Re and Im part of a symbol pair. For a second 260 set of modulations, c may be 1, and / or c may be odd. This may in particular be suitable

[0138] for non-interlinking modulations. For example, more flexible mapping is facilitated. In particular, for pi / 2*BPSK modulation, and / or an interlinked modulation, c may be 2 or

[0139] an even number larger than 2. In some variants, for a Q AM-based modulation, and / or QPSK, c may be 1 or an odd number larger than 1. 265

[0140] Different transmission sources may correspond to different layers of transmission. Thus, multi-layer transmission may be facilitated, with layers carrying suitable tuples of modulation symbols; in particular, distribution of interlinked modulation symbols over layers

[0141] may be avoided. It may be considered that the code blocks of the plurality of code blocks

[0142] may be associated to the same data block, e.g. code block bundle or transport block, 270 and / or may be interleaved based on c. Interleaving may in general provide an output

[0143] bit sequence based on the bits of the code blocks. The modulation symbol sequence may represent the data block and / or the code blocks associated thereto. For different data blocks, e.g. CBBs or transport blocks, different modulation symbol sequences may be

[0144] used, and / or modulation symbol sequences may be mapped separately to transmission 275 sources. Thus, order of data blocks may be ensured. In some cases, interleaving may

[0145] be performed on a code block basis and on a data block basis. Different interleavers

[0146] may be used for code block based interleaving, and data block based interleaving; however, a combined interleaver providing both interleavings may be used instead. The data signalling may thus be provided with additional robustness against interference and / or 280 disturbances.

[0147] It may be considered that the modulation symbol sequence may be based on interleaving

[0148] of bits of the code blocks of the plurality of code blocks. The interleaving may provide an

[0149] output bit sequence, based on which the modulation symbol sequence may be provided,

[0150] P113137WO01 8 / 79e.g. by a modulator. 285

[0151] The transmission of the data signalling or data block or may in downlink, e.g. if the transmitting radio node is a network node, or in uplink or sidelink, e.g. if the transmitting

[0152] radio node is a wireless device or terminal. The transmission may in particular utilise a

[0153] OFDM-based and / or SC-FDM based waveform (also referred to as DFT-s-OFDM based waveform), in which a DFT-spreading operation is used, e.g. before utilising a IFFT to 290 provide time domain samples for transmission. Such waveforms may provide good PAPR characteristics for transmission, e.g. allowing optimised use of power amplifiers. However,

[0154] the approaches may also provide consistent behaviour for other modulation schemes.

[0155] In general, the terms “modulation”, “modulation format”, “modulation scheme” may pertain to the type of modulation used, e.g. BPSK, QAM , QPSK or similar; as such, 295 they may be considered synonyms. The transmission sources may be synchronised, or

[0156] quasi-synchronised, e.g. within a synchronisation threshold time shift. It may be noted

[0157] that due to path effects, a timing shift between signalling from different transmission

[0158] sources may appear for a receiver, which may be adapted to compensated for such, e.g. according to timing setup and / or cyclic prefix and / or configuration. 300

[0159] An interlinking modulation may be a modulation in which some modulation symbols are dependent on one or more other modulation symbols. For example, there may be a phase dependency between modulation symbols, e.g. a pair of modulation symbols, or an n-tuple

[0160] of modulation symbols. In general, modulation symbols may represent the data blocks,

[0161] e.g. one modulation symbol may represent one or more bits of a data block. Interlinked 305 modulation symbols (also referred to as interlinked symbols) may represent bits of the

[0162] data block. In general, a data block may comprise information bits (e.g., payload data

[0163] or user data), and / or error coding bits, e.g. for error detection coding (for example, a

[0164] CRC) and / or forward error coding. Different parts of a data block being transmitted utilising different transmission sources may comprise at least one, e.g. a first, part being 310 transmitted utilising a first transmission source, and another, e.g. a second, part being transmitted utilising a second transmission source. A code block or data block may be represented by a set or sequence of bits, or by a set or sequence of modulation symbols.

[0165] Modulation symbols (e.g., a set or sequence) representing the data block may also be referred to as codeword (CW). In general, bits or a sequence of bit may be mapped to 315 transmission sources, e.g. layers, before modulation. In some cases, however, bits may be modulated, and then modulation symbols may be mapped to transmission sources, e.g.

[0166] layers. Mapping may in general comprise interleaving. In general, interlinked modulation symbols may be mapped in sequence and / or consecutively in time domain.

[0167] The plurality or multiple of transmission sources may in particular consist of 2 transmis- 320

[0168] P113137WO01sion sources, e.g. for providing a rank 2 transmission or 2 layer transmission. However, cases with more than 2 transmission sources may be considered, e.g. 3 or more, 4 or

[0169] more transmission sources or layers. It may be considered that the data block or data signalling may be transmitted utilising a DFT-s-OFDM based waveform. Such waveform

[0170] is particularly suited for low PAPR. 325

[0171] In general, data signalling may carry, and / or represent, one or more data blocks. A data

[0172] block may be transmitted in a data block signalling time interval. In the data block signalling time interval, there may be transmitted a single data block (e.g., on multiple

[0173] layers or using multiple transmission sources); optionally, reference signalling, e.g. DMRS, and / or control information (e.g., leading the data block in time) may be transmitted in 330 the data block signalling time interval. The data block signalling time interval may consist

[0174] of one or more than one allocation units, e.g. symbol time intervals (e.g., associated to

[0175] OFDM symbols or DFT-s-OFDM symbols). Reference signalling may be associated to a reference allocation unit (e.g., a symbol).

[0176] Transmitting the data signalling or data block may be based on mapping the code blocks 335 and / or the data block to the plurality of transmission sources and / or to one or more symbol time intervals, and / or on modulating bits of the data block and / or code blocks.

[0177] A mapping of the data block or code blocks to transmission sources may map bits of the

[0178] data block or code blocks to transmission sources (e.g., in a transmission source domain mapping), or modulation symbols representing the bits to transmission sources. Receiving 340 may be based on a reverse operation or mapping. In general, the transmission of data signalling, e,g. a data block, may be part of data signalling covering one data block, or

[0179] a plurality of data blocks, e.g. of unspecified duration and / or according to an allocation; different allocation types may be considered (e.g., configured, or dynamically scheduled).

[0180] It may be considered that the data signalling or data block is transmitted utilising a modu- 345 lation from a set of modulations, the set including at least one interlinking modulation, e.g. pi / 2*BPSK modulation and / or TCM or another form of interlinking modulation. Thus,

[0181] a consistent approach of mapping may be used. The set may comprise non-interlinking modulations, e.g., one or more n-QAM based modulations. Which modulation to be used

[0182] may be based on link adaptation, e.g. based on channel estimates and / or threshold values 350 for signal quality and / or signal strength. For example, for low signal quality or signal strength, an interlinking modulation may be used. The modulation used may be signaled

[0183] to a wireless device or terminal, e.g. in a DCI or scheduling grant (if the wireless device

[0184] or terminal is the transmitting radio node) or a scheduling assignment (if the wireless

[0185] device or terminal is the receiving radio node). 355

[0186] The data signalling or data block may be transmitted utilising pi / 2*BPSK modulation.

[0187] P113137WO01 10 / 79This modulation facilitates low PAPR, and may provide a good signal quality even in bad channel conditions. In this case, c may be 2, or correspond to an even integer, or an

[0188] integer multiple or power of 2 that is larger than 2. It may be considered that the data signalling or data block may be transmitted utilising an interlinking modulation, wherein 360 interlinked modulation symbols are transmitted utilising the same transmission source.

[0189] In some variants, no interlinked symbols are transmitted utilising different transmission sources; however, it may be considered that (e.g., exactly, or a single) one modulation symbol transmitted utilising a transmission source may be linked to another modulation symbol transmitted utilising another transmission source. 365

[0190] It may be considered that a data block may be a code block bundle or transport block.

[0191] The data block may comprise the one or more code blocks. Each code block or data block

[0192] may be associated to a different acknowledgement process, e.g. HARQ process.

[0193] In general, to different transmission sources, there may be associated different reference signalling sequences. Reference signalling references may be shifted relative to each other, 370 e.g. based on the same root sequence, or may be based on different root sequences. Thus, correct association of signalling utilising different transmission sources may be facilitated.

[0194] It may be considered that bits of the code blocks or a data block are mapped to layers,

[0195] or transmission sources, before performing modulation. Thus, interlinked modulation symbols may be mapped to the same transmission source with low computation effort. 375 However, in some cases, mapping to transmission sources or layers may be performed

[0196] after modulation, such that modulation symbols may be mapped to transmission sources.

[0197] The mapping may be such that interlinked symbols are mapped to the same transmission

[0198] source, e.g. using a suitable interleaver.

[0199] In general, a data block may be transmitted in a data block signalling time interval 380 consisting of one or more allocation units. Bits of the data block, or modulation symbols representing it (based on it, e.g. after modulation) may be distributed across different transmission sources.

[0200] It may be considered that the code blocks or the data block may be mapped based on

[0201] a time domain mapping before a symbol domain mapping, for example for a data block 385 transmitted over multiple symbol time intervals or allocation units. This may facilitate keeping interlinked modulation symbols together.

[0202] It may be considered that the data block may correspond to a code block bundle (CBB) and / or one or more code blocks. In some cases, it may be a transport block, which may comprise, and / or have associated to it a joint error coding or CRC covering all the code 390

[0203] P113137WO01 11 / 79blocks included the transport block. The transport block may in general one or more code blocks.

[0204] It may be considered that the data signalling represents one occurrence of data signalling,

[0205] e.g. covering a data block signalling time interval, and / or one transmission on a data channel like PDSCH or PUSCH or PSSCH, and / or one transmission time interval (TTI). 395 The data signalling may be part of a longer data signalling sequence, which may cover, and / or be embedded in, and / or represent a data transmission (time) interval, and / or be of unspecified duration. Data signalling occurrences may be scheduled or configured jointly,

[0206] e.g. with a scheduling grant or assignment, or separately, e.g. with multiple scheduling assignments. A data block signalling time and / or data signalling sequence may comprise 400 at least 4, or at least 8 data signalling occurrences and / or data block signalling time intervals. It may be considered that to each data block signalling time interval, there

[0207] is associated on allocation unit associated to reference signalling associated to the data

[0208] block of the data block signalling time interval. The data transmission time and / or data signalling sequence may comprise these allocation units associated to reference signalling; 405 each of these allocation units may represent a reference allocation unit for the directly preceding data block signalling time interval and / or data block and7or associated data signalling (excepting the earliest of the data block signalling time intervals in the sequence and / or data transmission time).

[0209] It may be considered that the data signalling comprises control information preceding the 410 data block in time domain. The control information may be considered part of the data signalling. In some variants, the control information may be mapped to, and / or carried on

[0210] exactly one allocation unit. In particular, no signalling representing the data block or parts thereof may be associated to this allocation unit. The allocation unit carrying the control information may be a first (earliest) allocation unit of the data block signalling time 415 interval and / or may be the starting allocation unit; in some variants, it may be mapped to

[0211] and / or associated to and / or carried on the allocation unit preceding the starting allocation

[0212] unit. Front-loaded DM-RS and / or an allocation unit associated thereto may be leading

[0213] in time and / or neighbouring to the allocation unit associated to control information.

[0214] The same DM-RS and / or transmission parameter / s may be associated and / or used for 420 the control information and signalling carrying the data block. The control information

[0215] may be considered part of the data signalling in some cases, but not part of the data

[0216] block. The control information may be UCI (e.g., in uplink) or DCI (in downlink) or SCI

[0217] (in sidelink), and / or be mapped to a MAC control element. (Error) coding of control information may be separate from error coding of the data block or code block / s thereof. 425 The allocation unit associated to the control information may neighbour in time at least

[0218] one allocation unit carrying the data block and / or data signalling carrying the data block

[0219] P113137WO01 12 / 79or parts thereof.

[0220] It may be considered that the data block is mapped to allocation units to be carried by

[0221] data signalling. 430

[0222] It may be considered that reference allocation units occur periodically, e.g. configured

[0223] and / or configurable and / or pre-defined. The periodic occurrence may be relevant for at

[0224] least a data transmission time. The occurrence of reference allocation units (which in general may be associated to and / or carry DM- RS) may be basis for the data block size.

[0225] In general, the data block size may be dependent on one or more additional parameters, 435 in particular transmission parameter / s, for example MCS and / or code rate.

[0226] It may be considered that for multiple occurrences of data signalling, each data block may

[0227] be associated to a different acknowledgement signalling process and / or different ranges

[0228] of processes. A range of processes may comprise one or more acknowledgement signalling processes (e.g., HARQ processes); different ranges may comprise at least one non-shared 440 (between the ranges) process.

[0229] A data block signalling time interval may correspond to the number of allocation units or symbols carrying the data block or parts thereof, and / or data signalling, and / or of one

[0230] data signalling occurrence. A data transmission (time) interval may comprise and / or be associated to multiple data signalling occurrences and / or be associated to multiple data 445 blocks and / or data block signalling time intervals. In some variants, a data transmission

[0231] (time) interval may comprise and / or cover at least or exactly 5, or at least or exactly

[0232] 10 or at least or exactly 20 data signalling occurrences and / or data block signalling time intervals.

[0233] It may in general be considered that a data block is part or portion of itself. Different 450 parts of a data block may comprise and / or represent different bits of the data block, e.g. information bits and / or coding bits. In general, a part of a data block may comprise and / or represent information (payload) bits and / or coding bits. In some cases, a data

[0234] block may be represented by a code block; in other cases, a part of a data block may be

[0235] a code block (e.g., if the data block comprises more than one code block). The size of a 455 code block or data block may be represented or representable in bits, and / or in allocation

[0236] units covered by it or required to carry it. This may be dependent on, and / or associated

[0237] to bit size (e.g., in information bits, or information bits and error detection bits, and / or information bits and error detection and correction bits, depending on reference used) and / or bandwidth and / or MCS, in particular modulation; alternatively, or additionally, 460 the bit size may be associated to and / or based on the number of symbols available. A

[0238] code rate may indicate how many coding bits are used (high code rate may indicate

[0239] P113137WO01 13 / 79low number of coding bits). The coding bits may be error coding bits, in particular for error detection coding (e.g., CRC) and / or error correction coding, e.g. FEC like polar

[0240] coding and / or LPDC based coding or Muller-Reed coding or Turbo coding or similar. To 465 different data blocks, there may associated the same code rate, or in some cases, different

[0241] code rates. The associated code rate may be a maximum code rate. To each allocation

[0242] unit, different parts of the data blocks may be associated, e.g. such that each allocation

[0243] unit not carrying and / or not associated to reference signalling carries a different part.

[0244] A data block may be mapped to, and / or associated to an integer number of allocation 470 units. It may be considered that no allocation unit is associated to parts of different data blocks, or to different data blocks. Different parts of the same data block may be mapped

[0245] to subsequent (in time) and / or neighbouring allocation units. Two subsequent allocation

[0246] units may in general be arranged such that they share a border in time domain, such that

[0247] an earlier allocation unit ends when the later subsequent allocation unit begins. A series of 475 subsequent allocation units may represent the data block signalling time interval, e.g., in

[0248] the numbers discussed above. Subsequent allocation units may be considered continuous

[0249] in time.

[0250] In general, an allocation unit may correspond to a symbol time duration, e.g. of an

[0251] OFDM symbol and / or SC-FDM symbol. The data signalling may utilise an OFDM- 480 based waveform, in particular a SC-FDM based waveform (which is also referred to as

[0252] DFT-s-OFDM based waveform, and can be considered to be an OFDM-based waveform).

[0253] A data block may comprise, and / or consist of, one or more code blocks; code blocks may

[0254] be associated to data blocks and / or allocation units according to, and / or based on, a

[0255] code block distribution.. Rhe position and / or arrangement of reference signalling may be 485 indicated and / or configured, e.g. with higher layer signalling and / or with physical layer control signalling like DCI.

[0256] An allocation unit may be considered associated to signalling and / or a data block (or part thereof) if it carries and / or is intended to carry the signalling, e.g. reference signalling) and / or signalling representing the data block. For example, information and / or coding 490 bits associated to a data block or part thereof may be mapped to the allocation unit, e.g.

[0257] in time and / or frequency and / or code domain. The allocation unit may carry may be intended to carry one or more modulation symbols representing information of the data

[0258] block (e.g., information / payload and / or coding bits).

[0259] Communicating utilising data signalling may correspond to transmitting and / or receiv- 495 ing the data signalling. Transmitting data signalling may comprise mapping information

[0260] and / or error coding into a data block, e.g. according to a data block size. Transmitting

[0261] data signalling may comprise scheduling the data signalling for reception by a receiver

[0262] P113137WO01 14 / 79(e.g., another radio node, in particular a wireless device) and / or may be based on a resource allocation, which may be configured or scheduled, e.g. by a network node. Re- 500 ceiving data signalling may comprise monitoring an allocation unit associated to reference signalling for reference signalling and / or the allocation unit / s associated to a data block

[0263] and / or control information for such, e.g. assuming the data signalling is according to the

[0264] data block size, e.g. to demodulate and / or decode the data block. Receiving may be

[0265] based on, and / or according to, a resource allocation, which may be configured or sched- 505 uled to a transmitter by the receiver (e.g., if transmitted by a wireless device; a network

[0266] node may receive data signalling according to the resource allocation, which it may have indicated to the wireless device), or received from the transmitter (or the network; e.g.

[0267] if a wireless device has resources allocated for scheduled or configured data signalling it

[0268] should receive). 510

[0269] The size of data blocks and / or code blocks may be such that an integer number fits into

[0270] an interval between allocation units carrying DM-RS, e.g. without leaving an allocation

[0271] unit of interval without associated part of a data block (e.g., empty). Thus, resource use

[0272] may be optimised. Code block size (a code block may be considered a subblock of a data

[0273] block or code block bundle, or represent a data block only comprising the code block as 515 single code block) and / or data block size may be from a set of sizes, which may allow

[0274] such mapping and / or code block distribution.

[0275] It may be considered that a data block corresponds to a code block bundle (CBB). The

[0276] CBB may comprise one or more code blocks. It may be considered that different CBBs

[0277] have the same size; in some cases, different CBBs may have different sizes. The size of a 520 CBB may be represented or representable in number of code blocks and / or bits. Different

[0278] sizes may be due to different modulation used. Same-sized data blocks or code blocks

[0279] or CBBs in general (at least if the same modulation and / or MCS is used) may comprise and / or represent the same number of information bits (also referred to as payload or user

[0280] bits) and / or code rate. However, in some cases, e.g. if reference signalling is embedded 525 in time domain in a data block, same-sized code blocks and / or CBBs or data blocks may

[0281] have different number of information bits and / or code rate.

[0282] Alternatively, or additionally, the number of data blocks and / or size of one or more of

[0283] the data blocks (and / or of a code block or code block bundle) may be dependent on

[0284] a modulation and / or coding scheme (MCS) used for transmitting the data signalling, 530 in particular the data blocks. The modulation and / or coding scheme may in particular

[0285] refer to the modulation (e.g., QPSK, n-QAM) and / or number of constellation points per modulation symbol and / or the error coding used, in particular the error correction coding.

[0286] Parts of the same data block may be transmitted with the same modulation and / or coding

[0287] P113137WOD1 15 / 79scheme. Different data blocks may be transmitted with the same or different schemes, 535 in particular re: modulation and / or coding. Thus, optimised transmission and resource utilisation may be provided.

[0288] In general, the number of data blocks and / or the size of the one or more data blocks may

[0289] be from a set of numbers containing numbers dividing the number of allocation units of a

[0290] data transmission interval, e.g. without rest, and / or such that the number of allocation 540 units of the data transmission interval is an integer multiple (1 or more) of each of the numbers of the set (each of the numbers of the set may be an integer number; the numbers

[0291] may be different; the set may comprise one or more numbers). The largest number of the

[0292] set may be equal to the number of allocation units (SI) of the data transmission interval.

[0293] It may be considered that the reference signalling may be and / or comprise Demodulation 545 Reference signalling, DMRS, e.g. each instance associated to one data block. DMRS may

[0294] be considered associated to a data block if it allows and / or is intended to allow demodulation of the signalling associated to the data block. In some cases, reference signalling may alternatively, or additionally, comprise a second form of reference signalling, e.g. userspecific RS and / or Phase-Tracking (PT) Reference signalling, and / or time tracking (TT) 550 Reference signalling. In particular, a first reference allocation unit may be associated to DMRS, and a second or third may be associated to PT-RS. The second type of RS allows

[0295] great flexibility, and / or may facilitate phase correction and / or timing correction, e.g. to

[0296] handle large path delays.

[0297] In general, to each allocation unit carrying data signalling, there may be associated a 555 cyclic prefix (depending on waveform), which may lead in time domain.

[0298] DMRS on different reference allocation units may be based on the same or different sequences, and / or may have the same or different cyclic shift. If the same form of DMRS

[0299] is used, it may be easier to provide high signal resolution; different forms may help to overcome strongly fluctuating interferences. 560

[0300] It may be considered that different data blocks may be transmitted with the same modulation and coding scheme, e.g. in a data transmission interval. This simplifies reception,

[0301] as circuitry does not have to be adapted to handle shifting transmission parameters. However, in some cases, e.g. if the data blocks represent a mix of newly transmitted data and retransmissions, it may be useful to use different MCS for different data blocks and / or 565 code block bundles.

[0302] It may be considered that each data block (and / or code block and / or code block bundle)

[0303] may be associated to a different acknowledgement signalling process and / or different

[0304] P113137WO01 16 / 79processes, e.g. different ranges of processes. Different processes may be associated to different process IDs and / or data (sub-) streams and / or transmission layers and / or buffers 570 (e.g., for soft combining).

[0305] In general, it may be considered that a code block represents a part of a data block and / or

[0306] CBB. A part of a data block associated to an allocation unit may be a code block, or

[0307] a different part (e.g., smaller or larger than one code block, and / or comprising parts of

[0308] more than one code block). 575

[0309] Communication may be based on TDD. Communicating may in general comprise transmitting and / or receiving signalling, e.g. data signalling. Communicating utilising or using

[0310] data signalling may comprise transmitting or receiving data signalling, e.g. data signalling

[0311] being transmitted according to the code block distribution. A node being configured for

[0312] data signalling may be considered to be set up with, and / or provided with a configuration 580 or indication of a code block distribution, and / or provided with the code block distribution and / or associated mapping, and / or the associated resource structure / s, e.g. with control signalling, e.g. physical layer signalling or higher layer signalling, in particular

[0313] with scheduling assignment / s and / or grant / s and / or resource configuration using higher

[0314] layer signalling, e.g. RRC signalling configuring resources for data signalling (and / or in- 585 dicating the CB distribution, e.g. indicating a Code block bundle size, and / or CB and / or

[0315] BS as discussed herein). A node being configured for indication signalling may be considered to be set up with, and / or provided with a configuration or indication of the code

[0316] block distribution, and / or provided with the code block distribution and / or associated mapping, e.g. with control signalling, e.g. physical layer signalling or higher layer sig- 590 nailing. In general, a code block distribution may map all code blocks of a code block

[0317] bundle to the allocation units of a (e.g., the same, like the first or a second) signalling resource structure.

[0318] The transmitting radio node may in general comprise, and / or be adapted to utilise, processing circuitry and / or radio circuitry, in particular a transmitter and / or transceiver, to 595 process (e.g., trigger and / or schedule) and / or transmit data signalling and / or the data

[0319] block, e.g. utilising the multiple transmission sources. The transmitting radio node may

[0320] in particular be a wireless device or terminal or UE, or a network node, for example a base

[0321] station or an IAB or relay node. In general, the transmitting radio node may comprise and / or be adapted for transmission diversity, and / or may be connected or connectable 600 to, and / or comprise, antenna circuitry, and / or two or more independently operable or controllable antenna arrays or arrangements, and / or transmitter circuitries and / or antenna circuitries, and / or may be adapted to use (e.g., simultaneously) a plurality of transmission sources, e.g. antenna ports and / or antennas or antenna arrays or subarrays

[0322] P113137WO01 17 / 79or antenna arrangements (e.g., for transmitting data signalling and / or associated refer- 605 ence signalling). Transmitting may comprise controlling transmission using transmission sources, e.g. the antenna array / s. The transmitting radio node may comprise multiple components and / or transmitters and / or TRPs (and / or be connected or connectable thereto) and / or be adapted to control transmission from such. Any combination of units and / or devices able to control transmission on an air interface and / or in radio as described 610 herein may be considered a transmitting radio node.

[0323] The receiving radio node may comprise, and / or be adapted to utilise, processing circuitry

[0324] and / or radio circuitry, in particular a receiver and / or transmitter and / or transceiver, to

[0325] receive and / or process (e.g. receive and / or demodulate and / or decode and / or perform

[0326] blind detection and / or schedule or trigger such) data signalling. Receiving may comprise 615 scanning a frequency range (e.g., a carrier) for data signalling, e.g. at specific (e.g., predefined and / or configured) locations in time / frequency domain, which may be dependent

[0327] on the carrier and / or system bandwidth. Such location / s may correspond to one or more location or resource allocations configured or indicated or scheduled or allocated to the transmitting radio node, for reception of data signalling. Such resources may for example 620 be PDSCH resources (if the receiving radio node is a wireless device, for example), e.g. scheduled dynamically or configured, e.g. with DCI and / or RRC signalling, or PUSCH resources (for example, if the receiving radio node is a network node). The receiving radio

[0328] node may in particular be a network node or base station, or an IAB node or relay node.

[0329] However, in some cases, the receiving radio node may be implemented as a wireless device 625 or terminal or UE. The receiving radio node may comprise one or more independently operable or controllable receiving circuitries and / or antenna circuitries and / or may be adapted to receive data signalling from the plurality of transmission resources, e.g. simultaneously and / or to operate using two or more antenna ports simultaneously, and / or

[0330] may be connected and / or connectable and / or comprise multiple independently operable 630 or controllable antennas or antenna arrays or subarrays. Receiving the data block may comprise combining signalling received from the transmission sources to construct the

[0331] data block.

[0332] A data transmission interval may in general comprise and / or cover and / or consist of

[0333] an integer multiple of BS. The CB code blocks may be considered to represent and / or 635 implement a code block bundle. A code block distribution may be represented and / or indicated and / or configured by information indicating mapping code block / s to a signalling resource structure, e.g. in the abstract or a specific resource structure, e.g. the first signalling resource structure. The distribution may in particular be indicated or configured

[0334] with physical layer signalling and / or higher layer signalling, e.g. RRC or MAC signalling. 640

[0335] P113137WO01 18 / 79Receiving data signalling may comprise and / or be based on decoding and / or demodulating data signalling, e.g. based on a configuration and / or scheduling information. Data signalling may be configured and / or scheduled for transmission and / or reception, e.g. by

[0336] the network or a network node, for example with physical layer signalling and / or higher

[0337] layer signalling. For example, a network node as signalling radio node may configure 645 and / or schedule data signalling to be received by a wireless device, or as a receiving

[0338] node, it may schedule or configure data signalling to be transmitted by a wireless device.

[0339] Receiving may be based on the assumption that code blocks are mapped to allocation

[0340] units as described herein. Transmitting data signalling may be based on and / or comprise, mapping information or data or corresponding bits to code blocks and / or allocation units, 650 e.g. based on a modulation scheme and / or scheduling and / or operating conditions. A network node may be adapted to schedule and / or configure data signalling.

[0341] The data signalling may be signalling on a data channel, in particular a physical data channel like a PUSCH or PDSCH or PSSCH (depending, e.g., on the implementation

[0342] of the signalling radio node and / or the receiving radio node). The data signalling may 655 be beamformed. The data signalling may be at one occasion (e.g., one transmission of PUSCH or PDSCH). The data signalling may be uplink or downlink or sidelink signalling;

[0343] the type of communication (e.g., transmitting or receiving) performed by a specific node

[0344] in regard to the data signalling may be corresponding to the type or direction of signalling.

[0345] BS allocation units (of one data block and / or one occurrence of data signalling) may be 660 contiguous in time domain, e.g. such that each allocation unit of the BS allocation unit neighbors two other allocation units of the BS allocation, with the exception of border allocation units, which may only neighbor one allocation unit of the BS allocation units

[0346] (and border another allocation unit not carrying bits of the CB code blocks, assuming BS

[0347] is large enough. 665

[0348] CB code blocks being associated to BS allocation units may refer to the code block / s and / or associated error coding, and / or error encoded code blocks being contained in

[0349] the BS allocation units. BS may be 1 or larger than 1. CB may be 1 or larger than

[0350] 1. The value / s of CB and / or BS may differ between transmissions and / or code block

[0351] groups (each CB may belong to only one group). Thus, after CB code blocks have been 670 transmitted in BS allocation units, different values for CB and / or BS may be used. In general, CB and / or BS may be based on operating conditions and / or network load and / or

[0352] signal quality and / or signal strength (e.g., quality and / or strength based on measurement reports) and / or buffer status (e.g., of a buffer storing incoming user data).

[0353] It may be considered that a code block comprises, and / or is associated to error coding, e.g. 675 error detection coding (like parity coding and / or CRC) and / or error correction coding

[0354] P113137WO01 19 / 79(e.g., FEC, like polar coding and / or turbo coding and / or LDPC). The bits for error coding and / or the bits representing the error coded code block / s of the BS allocation units may

[0355] be mapped to the BS allocation units, representing the CB code blocks being associated

[0356] to the BS allocation units. 680

[0357] It may be considered that in some variants, one code block or data block may be contained

[0358] in one allocation unit (in particular, only one code block, possibly including error coding

[0359] or the error encoded representation), or one data block or code block may occupy multiple allocation units; for example, one data block or code block (in particular, only one code

[0360] block, plus possibly error coding or the error encoded representation) may fully occupy 685 the multiple allocation units, for example if one allocation unit is not sufficient. The data

[0361] block size may in general be determined to allow such mapping to one or more allocation

[0362] units.

[0363] It may be considered that to a code block or CBB, there is mapped (e.g., exactly) one

[0364] packet data unit from at least one higher layer, for example a MAC (Medium Access 690 Control) layer and / or an RLC (Radio Link Control) layer. Each packet data unit may comprise layer-specific header information. With this approach, parallel processing is facilitated even in the higher layers. In particular, a receiver may pass such structured information to higher layers, and / or a transmitter may pass information downwards from

[0365] higher layers to the physical layer. Code blocks may be mapped to allocation units on a 695 physical layer.

[0366] In some variants, the data signalling and / or a data block and / or CBB may comprise a plurality of code blocks, with independent error detection coding and / or error correction

[0367] coding for each code block. Thus, error coding may only pertain to one code block,

[0368] allow quick independent processing of code blocks. It may be considered that the data 700 signalling or data block comprises a plurality of code blocks, wherein no collective error detection coding and / or error correction coding is included in and / or associated to the

[0369] data signalling. The signalling may omit error coding covering more than one code block.

[0370] For example, transport block level error coding may be omitted. Thus, fully independent

[0371] or parallel processing is facilitated. A corresponding data block may be considered a code 705 block bundle.

[0372] There is also described a program product comprising instructions causing processing circuitry to control and / or perform a method as described herein. Moreover, a carrier medium arrangement carrying and / or storing a program product as described herein is considered. An information system comprising, and / or connected or connectable, to a 710 radio node is also disclosed.

[0373] P113137WO01 20 / 79The data signalling may be associated to a data channel, and / or a priority level. Different data signallings may be associated to different data channels, or different priority levels,

[0374] e.g. for URLLC or other high priority signalling.

[0375] Transmission parameters may comprise in particular frequency resources and / or start (in 715 time domain, e.g. in which allocation unit) and / or modulation and / or coding (in particular, modulation and coding scheme) and / or code rate and / or beam parameters, e.g. pertaining to the beam in which the data signalling is transmitted) and / or MIMO param-eter / s and / or parameter / s indicating an arrangement of code blocks of the data signalling, and / or information regarding reception, e.g. antenna and / or beams for reception, and / or 720 information indicative of a beam pair to use for transmission and / or reception.

[0376] An unspecified duration may indicate that the data signalling will be transmitted until

[0377] an unspecified end, such that a receiver may have to listen and / or monitor resources accordingly. The end may be unspecified when starting, and / or the resources (in particular

[0378] in time domain) to be monitored or used may be unspecified when starting or triggering 725 the data signalling transmission. The unspecified duration may be within a transmission

[0379] phase, e.g. a downlink transmission phase, for example in a TDD system. The transmission may utilise a single-carrier based waveform. The unspecified duration may extend at

[0380] least over a plurality of allocation units, in particular at least over 10, or at least 20, or

[0381] at least 50, or at least 100 allocation units, e.g. block symbols. The receiving radio node 730 may be expected to be ready to monitor for, and / or receive, data signalling and / or a stop

[0382] or end and / or interruption indication. The timing for transmission and reception may be

[0383] shifted relative to each other due to path traveling effects; however, the time structure

[0384] of signalling may be considered to be essentially the same for transmitter and receiver.

[0385] Data signalling may be scheduled or configured with unspecified duration, such that e.g. 735 numerous data blocks and / or reference signallings are transmitted as indicated.

[0386] It may be considered that the data signalling is transmitted using constant transmission parameters, e.g. constant over the data transmission time. Such parameters may

[0387] in particular indicate modulation and / or coding and / or modulation and coding scheme and / or transmission power and / or reference signalling density and / or bandwidth and / or 740 frequency resources (e.g., bandwidth part and / or carrier) and / or waveform. Thus, the receiving radio node does not have to change associated reception parameters and / or circuitry settings.

[0388] A code block may in general represent bits of information (e.g., user data and / or payload) and / or error coding, and / or may be represented by a corresponding bit sequence. A code 745 block (e.g., its bits or representation) may be mapped to one or more modulation symbols contained in the one or more allocation units (e.g., depending on modulation and / or

[0389] P113137WO01 21 / 79coding scheme and / or bandwidth and / or waveform). The allocation unit may in some cases contain reference signalling, e.g. phase tracking reference signalling, which may for example be included as a sequence, e.g. in a fixed and / or predefined and / or configured 750 or configurable location (e.g. in time domain) of the allocation unit. Control information

[0390] like header information and / or similar from higher layers may be represented by the information bits of the code block. In general, a code block may be padded (e.g. with

[0391] zeros or ones) to allow occupying an allocation unit, e.g. if the code block size otherwise

[0392] is too small to fully occupy one allocation unit. Alternatively, padding signalling may 755 be used, e.g. padding symbols associated to the allocation unit not completely filled by

[0393] a code block and / or its error coded representation. An error coded representation of a

[0394] code block may comprise bits representing the information of the code block and / or error detection coding and / or error correction coding; the information bits may be directly included, or transformed (e.g., when using polar coding for FEC). A code block bundle 760 (CBB) may comprise a plurality of code blocks; the code blocks in a CBB may be encoded separately, e.g. such that there is no common error correction coding covering the CBB.

[0395] A frequency domain interval and / or carrier may be associated to a specific wireless communication approach or network, e.g., a RAT; different intervals or carriers may be associated to different RANs and / or RATs. For example, the first frequency domain interval 765 may be associated to a 6G RAN or RAT, or to a 5G RAN or RAT, e.g., with extended bandwidth; narrower carriers may be associates to similar or same RAN / RAT, or to a different one. For example narrower carriers may be associated to 5G RAN or RAT.

[0396] A radio node, e.g. a transmitting or signalling radio node, and / or a receiving or feedback

[0397] radio node, may operate in TDD mode, e.g. switching between DL periods and UL 770 periods. A DL period may be a period in which the radio node operates using DL transmissions, an UL period may be a period in which the radio node operates using UL transmissions (e.g., a network node may transmit during DL, and receive during UL, and

[0398] vice versa for a wireless device). It may be considered that there is a TDD guard period between DL and UL periods and / or between UL and DL periods, which may comprise a 775 number of symbol time intervals, e.g. 10 or more symbols, or 12 or more symbols; there

[0399] may be the same duration for guard periods for DL / UL and UL / DL, or different ones.

[0400] The guard period may allow switching circuitry between the different communication directions and / or handling of interference (in particular considering that DL signalling

[0401] tends to much more powerful than (received) UL signalling). An antenna arrangement 780 may comprise one or more antenna elements and / or sub-arrays and / or panels; different antenna arrangements may comprise different antenna elements and / or sub-arrays and / or panels. Different antenna arrangements and / or panels and / or sub-arrays and / or elements

[0402] may be adapted to be controlled or controllable separately from each other. There may

[0403] P113137WO01 22 / 79be the same number of DL and UL periods and / or the same duration associated to DL 785 and UL (at least over a certain time interval, e.g. alternating such that one DL period is followed by one UL period, or vice versa, or different numbers or durations, e.g. (roughly)

[0404] 3:1 (e.g., 3 DL periods followed by a TDD guard period and 1 UL period), or (roughly)

[0405] 2:1, or even (roughly) 1:2 or 1:NU with NU 3 or larger, for UL heavy scenarios. UL

[0406] period durations may be the same as DL period durations, or different. The distribution 790 and / or duration of DL and UL periods may be referred to as TDD pattern; the TDD

[0407] pattern may be dynamically controllable (e.g., with DCI signalling), and / or configured

[0408] or configurable, e.g. with higher layer signalling like RRC signalling or RLC signalling, and / or may be semi-statically configurable or configured. The TDD pattern may describe

[0409] the smallest time domain distribution of DL period / s and / or UL period / s and / or TDD 795 guard period / s repeated over time, e.g. in one or more frames and / or subframes and / or

[0410] slots and / or a time duration covering multiple repetitions of the TDD pattern.

[0411] It may be considered that the radio node is adapted for utilising a number NP of antenna sub- arrays and / or panels, wherein NP may be an integer number of 4 or larger. An antenna sub-array may comprise a plurality of antenna elements, e.g. 4 or more, or 10 800 or more, or 50 or more, or 100 or more. An antenna sub-array, and / or the antenna elements associated thereto and / or comprised therein, may be associated and / or connected

[0412] or connectable to one and / or the same antenna circuitry, and / or be jointly controllable

[0413] for analog and / or digital beam-forming, and / or be operable for joint transmission or reception. A panel may comprise a support structure, e.g. plastics and / or metallic ma- 805 terial and / or wood, supporting one or more antenna sub-arrays, which additionally may support additional circuitry like antenna circuitry and / or interface circuitry. Each antenna sub-array may be associated for one communication direction (e.g., reception or transmission) and / or one functionality, e.g. communication. It may be considered that antenna elements of an antenna sub-array share the same polarisation, e.g. horizontal 810 or vertical. In some cases, NP may be an even number, wherein it may be considered

[0414] that NP / 2 antenna sub-arrays (and / or their antenna elements) may be associated to a

[0415] first polarisation (e.g., horizontal or vertical or left-circular or right-circular, or any other suitable polarisation) and the other NP / 2 antenna sub- arrays are associated to a second polarisation, which may be orthogonal to the first polarisation. For example, the first 815 polarisation may be horizontal with the second polarisation being vertical, or the first polarisation may be left-circular and the second polarisation may be right-circular. This

[0416] allows multiple beams to be operated, with good flexibility and / or large signalling capacity. In general, an antenna arrangement associated to a radio node may comprise one or

[0417] more antenna sub-arrays, in particular an even number of antenna sub-arrays. In general, 820 at different times, different antenna sub-arrays and / or panels may be used for different

[0418] P113137WO01 23 / 79functions, e.g. transmission or reception, and / or communication. The polarisation of an antenna element may be associated to a specific operation direction, e.g. for transmission

[0419] or reception. Depending on signalling direction (transmission or reception), polarisation

[0420] may be different. For example, an antenna sub-array may be associated to a first polari- 825 sation for transmission, and a second polarisation for reception, or vice versa. This may

[0421] be achieved, for example, by providing crossed linear antenna elements for the sub-arrays,

[0422] with associated connections / circuitry according to polarisation.

[0423] It may be considered that operating utilising signalling like communication signalling, and / or communicating utilising signalling like communication signalling, may comprise 830 transmitting the signalling, e.g. communication signalling, and / or receiving the signalling,

[0424] e.g. communication signalling. It may be considered that signalling like communication signalling is based on an OFDM wave-form, e.g. OFDM, or DFT-s-OFDM, or pulseshaped DFT-s-OFDM. Such a wave-form is particularly suitable for wireless communication at high frequencies and / or with high communication loads. A cyclic appendix may 835 generally be a cyclic prefix, or a cyclic suffix. The appendix may represent a repetition

[0425] of a part of signalling carried by a symbol at its start (suffix) or end (prefix), which may

[0426] be appended at the opposite of the symbol (end or start); e.g. a cyclic prefix may be considered a repetition of the signalling at the end of the symbol it pertains to. The communication signalling may be based on a waveform with cyclic appendix. A cyclic 840 appendix may be associated to a specific symbol, it may have a duration shorter than the symbol duration, e.g. 1 / 4 or less than 1 / 4 of the symbol duration, or 1 / 6 or less than

[0427] 1 / 6.

[0428] A radio node, like a transmitting radio node or receiving radio node, may be a wireless

[0429] device or user equipment or terminal. Alternatively, it may be a network node or sig- 845 nailing radio node. A radio node adapted for wireless communication may be a radio

[0430] node adapted for transmitting and / or receiving communication signalling. Communication signalling may be. and / or comprise, data signalling and / or control signalling and / or reference signalling, e.g. according to a wireless communication standard like a 3GPP standard or IEEE standard (e.g., of WIFI or WLAN). Operating utilising communication 850 signalling may comprise transmitting and / or receiving communication signalling. The

[0431] radio circuitry and / or processing circuitry and / or antenna circuitry of a radio node may

[0432] be adapted for handling communication signalling The radio node may be adapted for

[0433] full-duplex operation, and / or half-duplex operation. Full duplex may refer to transmitting and receiving at the same time, e.g. using the same or different circuitries, and / or 855 using different antenna sub-arrays or separately operable antenna sub-arrays or antenna elements. The communication signalling may be beam-formed.

[0434] P113137WO01 24 / 79A DFT-s-OFDM based wave-form may be a wave-form constructed by performing a DFT-spreading operation on modulation symbols mapped to a frequency interval (e.g., subcarriers), e.g. to provide a time- variable signal. A DFT-s-OFDM based wave-form may 860 also be referred to a SC-FDM wave-form. It may be considered to provide good PAPR characteristics, allowing optimised operation of power amplifiers, in particular for high frequencies. In general, the approaches described herein may also be applicable to SingleCarrier based wave-forms, e.g. FDE-based wave-forms. Communication, e.g. on data channel / s and / or control channel / s, may be based on, and / o utilise, a DFT-s-OFDM 865 based wave-form, or a Single-Carrier based wave-form.

[0435] Communication may in particular on multiple communication links and / or beams and / or

[0436] with multiple targets (e.g., TRPs or other forms of transmission sources also receiving) and / or multiple layers at the same time; different reference signallings for multiple transmission or reception may be based on different sequence roots and / or combs and / or cyclic 870 shifts. Thus, high throughput may be achieved, with low interference. In general, different reference signallings (e.g., of the same type) may be associated to different transmission

[0437] sources and / or beams and / or layers, in particular if transmitted simultaneously and / or overlapping in time (e.g., considering different timing advance values if transmitted in uplink). For example, there may be first reference signalling transmitted using a first 875 transmission source and / or first beam and / or first layer, and second reference signalling transmitted using a first transmission source and / or first beam and / or first layer.

[0438] There is also described a program product comprising instructions causing processing circuitry to control and / or perform a method as described herein. Moreover, a carrier medium arrangement carrying and / or storing a program product as described herein is 880 considered. An information system comprising, and / or connected or connectable, to a

[0439] radio node is also disclosed.

[0440] Brief description of the drawings

[0441] The drawings are provided to illustrate concepts and approaches described herein, and

[0442] are not intended to limit their scope. The drawings comprise: 885

[0443] Figure 1, showing an exemplary processing chain for transmission of signalling;

[0444] Figure 2, showing an exemplary interleaving or signalling scenario;

[0445] Figure 3 , showing an exemplary radio node like wireless device; and

[0446] Figure 4, showing an exemplary radio node like a network node.

[0447] P113137WO01 25 / 79Detailed description 890

[0448] Figure 1 shows an exemplary processing chain for transmission (a reception chain may be considered to be complementary). Data for a code block (e.g., information bits and / or payload) may be provided with a CRC, encoded, and be subject to one or more actions of interleaving like Pre-Cb interleaving and CBB interleaving. Scrambling and modulation

[0449] may be provided, as well as layer mapping (for multi-layer transmission) and precoding (if 895 applicable, e.g., in the uplink; precoding in this context may refer to SC-FDM precoding).

[0450] Modulation symbols may then be mapped to resource elements (RE) for transmission.

[0451] Such a chain may be utilised for transmission of data signalling.

[0452] Figure 2 shows an exemplary interleaving scenario, which may facilitate frequency diversity for split code blocks. In the example, code blocks CBO to CB3 are supposed to be 900 provided on a first allocation unit like a first symbol (this allocation unit may also carry

[0453] other CB, e.g., for another data block / not shown). An interleaver that may cover more

[0454] sub-carriers than available for transmission may be considered; the superfluous entries available for the interleaver may carry NULL. The not NULL-ed entries (block) of the interleaver may be associated to interleaving sub-patterns of a code block with a size 905 corresponding to NL*QM bits, with NL representing the number of layers and QM the number of bits representable by the modulation symbol to be used. Interleaving subpatterns of the code blocks may be mapped row- by- row into the interleaver (as input),

[0455] for code block after code block. For output, the entries may be read column- by-column,

[0456] which may provide a comb-like structure of interleaved combs for each code block; each 910 entry of the interleaver may be associated to one sub-carrier. The number of sub-carriers

[0457] may be the number available and / or scheduled for transmission. Each entry may be mapped to the next higher sub-carrier. The interleaver may be configured or configurable

[0458] to accommodate the largest number of sub-carriers that may be made available. In the scenario shown, CB3 may not fit completely into the interleaver, only a first portion is 915 mapped thereto. By mapping / inp utting row- by- row, but reading / outputting column- bycolumn, in general, interleaving sub-patterns are spread out in frequency domain, allowing frequency diversity and / or improved reliability.

[0459] The second portion of CB3 may be provided for the second allocation unit or second symbol that also should carry code blocks CB4 to CB8 (CB8 also partially). Interleaving 920 sub-patterns of the second portion of CB3 are not mapped to the leading entries of the interleaver, but to the end (essentially starting with the column after the last column still having an interleaving sub-pattern of CB3 in the last column for the first symbol). With

[0460] the reading out column- by-column (as generally indicated by the dashed arrow- lines), the interleaving sub-pattern of the second portion thus will be mapped to a second range 925

[0461] P113137WO01 26 / 79in frequency domain that is higher in frequency than the first range in which the first portion is transmitted.

[0462] The interleavers for the first and second allocation units may operate separately and / or in parallel; they may be considered as sub- interleavers. An interleaver or sub-interleaver may

[0463] have a number of rows and columns. Different representations of functionally identical 930 interleavers may be considered equivalent.

[0464] In some cases, one or more bit patterns and / or one or more sub-patterns may be padded

[0465] to provide a desired number of bits, e.g., providing the exact number of bits for an interleaving sub-pattern even if a code block size does not represent an integer multiple

[0466] of the size of such a sub-pattern. 935

[0467] Figure 3 schematically shows a radio node, in particular a wireless device or terminal 10

[0468] or a UE (User Equipment). Radio node 10 comprises processing circuitry (which may also

[0469] 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 940 particular as module in the controller. Radio node 10 also comprises radio circuitry

[0470] 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

[0471] or connectable to the processing circuitry. An antenna circuitry 24 of the radio node 10

[0472] is connected or connectable to the radio circuitry 22 to collect or send and / or amplify 945 signals. Radio circuitry 22 and the processing circuitry 20 controlling it are configured

[0473] for cellular communication with a network, e.g. a RAN as described herein, and / or for sidelink communication (which may be within coverage of the cellular network, or out

[0474] of coverage; and / or may be considered non-cellular communication and / or be associated

[0475] to a non-cellular wireless communication network). Radio node 10 may generally be 950 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, e.g. software modules. It may be considered that the radio

[0476] node 10 comprises, and / or is connected or connectable, to a power supply. A DFE may

[0477] be considered part of radio circuitry; an analogue frontend may be associated to radio 955 circuitry and / or antenna circuitry.

[0478] Figure 4 schematically shows a radio node 100, which may in particular be implemented

[0479] 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,

[0480] which may comprise a controller connected to a memory. Any module, e.g. transmitting 960 module and / or receiving module and / or configuring module of the node 100 may be im-

[0481] P113137WO01 27 / 79plemented 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 con- 965 nectable to radio circuitry 122 for signal reception or transmittance and / or amplification.

[0482] Node 100 may be adapted to carry out any of the methods for operating a radio node

[0483] or network node disclosed herein; in particular, it may comprise corresponding circuitry,

[0484] e.g. processing circuitry, and / or modules. The antenna circuitry 124 may be connected

[0485] to and / or comprise an antenna array. The node 100, respectively its circuitry, may be 970 adapted to perform any of the methods of operating a network node or a radio node as described herein; in particular, it may comprise corresponding circuitry, e.g. processing circuitry, and / or modules. The radio node 100 may generally comprise communication circuitry, e.g. for communication with another network node, like a radio node, and / or

[0486] with a core network and / or an internet or local net, in particular with an information sys- 975 tem, which may provide information and / or data to be transmitted to a user equipment.

[0487] A DFE may be considered part of radio circuitry; an analog frontend may be associated

[0488] to radio circuitry and / or antenna circuitry.

[0489] In general, the wireless device and / or network node may operate in, and / or the communication signalling may be in TDD operation. It should be noted that the transmission 980 of signalling from transmission sources may be synchronised and simultaneous; a shift in

[0490] time may occur due to different propagation times, e.g. due to different beams and / or

[0491] source locations. Communication signalling in general may represent and / or comprise

[0492] data signalling (e.g., on a physical data channel), and / or control signalling. Communication signalling may comprise, and / or have associated thereto, reference signalling, in 985 particular for demodulation of the communication signalling.

[0493] A data block may refer to a transport block, or a code block or a code block bundle. A

[0494] code block may comprise and / or represent a number of (information) bits representing information (e.g., data or control information), to which there may be associated, and / or

[0495] which may further include, bits for error detection coding, e.g. CRC. The bits for error 990 detection coding may be determined based on the (information) bits, and / or may be error detection bits for the (information) bits. A code block bundle may comprise one or more

[0496] code blocks; wherein each code block may have associated to it, and / or comprise, error correction bits. The error correction bits in a code block bundle may each pertain to an associated code block; error correction bits may be specific to only one code block, e.g. 995 determined based on bits of only one code block. Different bits and / or groups of bits

[0497] may be associated to different code blocks. Error correction bit / s associated to a code

[0498] block may be associated to a single code block; this may refer to the error correction bits

[0499] P113137WO01 28 / 79indicating correctness / incorrectness of the single code block, and / or calculated and / or determined based only on (information) bits of the single code block. Information bits 1000 may represent data and / or control information, e.g. associated to a data channel (data in-formation / bits) and / or control channel (control information / bits) code block bundle may

[0500] be a data block without error correction coding pertaining to more than one code block.

[0501] A transport block may comprise error detection coding pertaining to a plurality of code blocks, e.g. covering the code blocks it consists of. A transport block may comprise one 1005 or more code blocks. It may be considered that a data block may be associated to, and

[0502] or subject to, and / or correspond to, a, one and / or a single acknowledgement process, e.g.

[0503] a specific HARQ process, which may correspond to and / or be represented by a HARQ identifier. A code block may correspond to a sub-pattern of an acknowledgement information bit pattern. In some cases, a data block may correspond and / or pertain and / or be 1010 subject to a plurality of acknowledgement processes, e.g. if there is one acknowledgement process per code block of the data block.

[0504] A data block may comprise and / or represent information bits, which may be data bits

[0505] (e.,g., user data) and / or control information bits; the information bits may be associated

[0506] to one or more data or control channels, e.g. transport channels and / or logical channels, 1015 and / or may be mapped to a specific and / or single physical channel, in particular a physical

[0507] data channel, or in some cases, a physical control channel (in which case it may or may

[0508] not be associated to a higher layer channel like a transport channel or logical channel). A

[0509] data block may represent bits intended for transmission, e.g. encapsulating one or more

[0510] higher layer data packets, e.g. one or more MAC layer data packets, e.g. one or more 1020 PDUs (Protocol Data Unit) and / or SDUs (Service Data Unit); error correction bits, e.g.

[0511] CRC; may be added in physical layer processing. It may be considered that bits of a

[0512] data block are subject to physical layer processing like coding (e.g., forward error coding

[0513] and / or adding error correction coding) and / or rate matching and / or scrambling, and / or modulation. Modulation may correspond to mapping of bits of the processed data block 1025 to modulation symbols, e.g. according to a modulation scheme and / or to a modulation

[0514] space. The modulation symbols may be represented as a bit sequence until they are subject to analog conversion (or vice versa for reception).

[0515] A wireless device may in general comprise processing circuitry and / or radio circuitry, in particular a receiver and / or transceiver and / or transmitter, for performing measurement 1030 and / or to control beam switch and / or control beam-forming and / or receive and / or transmit signalling like communication signalling. The wireless device may in particular be implemented as terminal or a user equipment. However, in some cases, e.g. relay and / or

[0516] back-link and / or IAB scenarios, it may be implemented as network node or network radio

[0517] node. A network node may in general comprise processing circuitry and / or radio circuitry, 1035

[0518] P113137WO01 29 / 79in particular a receiver and / or transceiver and / or transmitter, for transmitting reference signalling and / or a beam switch indication and / or for beam switching and / or to control

[0519] beam switch and / or control beam-forming and / or receive and / or transmit signalling like communication signalling. The radio node may in particular be implemented as a network

[0520] node, e.g. a network radio node and / or base station or a relay node or IAB node. How- 1040 ever, in some cases, e.g. sidelink scenarios, the second radio node may be implemented

[0521] as a wireless device or terminal, e.g. a user equipment.

[0522] In general, an allocation unit or block symbol may represent and / or correspond to an extension in time domain, e.g. a time interval. An allocation unit or block symbol duration (the length of the time interval) may correspond to the duration of an OFDM 1045 symbol or a corresponding duration, and / or may be based and / or defined by a subcarrier spacing used (e.g., based on the numerology) or equivalent, and / or may correspond

[0523] to the duration of a modulation symbol (e.g., for OFDM or similar frequency domain multiplexed types of signalling). It may be considered that a block symbol comprises a plurality of modulation symbols, e.g. based on a sub-carrier spacing and / or numerology 1050 or equivalent, in particular for time domain multiplexed types (on the symbol level for

[0524] a single transmitter) of signalling like single-carrier based signalling, e.g. SC-FDE or

[0525] SC-FDMA (in particular, FDF-SC-FDMA or pulse-shaped SC-FDMA). The number of symbols may be based on and / or defined by the number of sub-carrier to be DFTS-spread

[0526] (for SC-FDMA) and / or be based on a number of FFT samples, e.g. for spreading and / or 1055 mapping, and / or equivalent, and / or may be predefined and / or configured or configurable.

[0527] A block symbol in this context may comprise and / or contain a plurality of individual modulation symbols, which may be for example 1000 or more, or 3000 or more, or 3300

[0528] or more. The number of modulation symbols in a block symbol may be based and / or be dependent on a bandwidth scheduled for transmission of signalling in the block symbol. A 1060 block symbol and / or a number of block symbols (an integer smaller than 20, e.g. equal to

[0529] or smaller than 14 or 7 or 4 or 2 or a flexible number) may be a unit (e.g., allocation unit)

[0530] used for scheduling and / or allocation of resources, in particular in time domain. To a block symbol (e.g., scheduled or allocated) and / or block symbol group and / or allocation unit,

[0531] there may be associated a frequency range and / or frequency domain allocation and / or 1065 bandwidth allocated for transmission.

[0532] An allocation unit, and / or a block symbol, may be associated to a specific (e.g., physical) channel and / or specific type of signalling, for example reference signalling. In some cases,

[0533] there may be a block symbol associated to a channel that also is associated to a form

[0534] of reference signalling and / or pilot signalling and / or tracking signalling associated to the 1070 channel, for example for timing purposes and / or decoding purposes (such signalling may comprise a low number of modulation symbols and / or resource elements of a block symbol,

[0535] P113137WO01 30 / 79e.g. less than 10% or less than 5% or less than 1% of the modulation symbols and / or resource elements in a block symbol). To a block symbol, there may be associated resource elements; a resource element may be represented in time / frequency domain, e.g. by the 1075 smallest frequency unit carrying or mapped to (e.g., a sub-carrier) in frequency domain

[0536] and the duration of a modulation symbol in time domain. A block symbol may comprise, and / or to a block symbol may be associated, a structure allowing and / or comprising

[0537] a number of modulation symbols, and / or association to one or more channels (and / or

[0538] the structure may dependent on the channel the block symbol is associated to and / or 1080 is allocated or used for), and / or reference signalling (e.g., as discussed above), and / or

[0539] one or more guard periods and / or transient periods, and / or one or more affixes (e.g.,

[0540] a prefix and / or suffix and / or one or more infixes (entered inside the block symbol)),

[0541] in particular a cyclic prefix and / or suffix and / or infix. A cyclic affix may represent

[0542] a repetition of signalling and / or modulation symbol / s used in the block symbol, with 1085 possible slight amendments to the signalling structure of the affix to provide a smooth

[0543] and / or continuous and / or differentiable connection between affix signalling and signalling

[0544] of modulation symbols associated to the content of the block symbol (e.g., channel and / or reference signalling structure). In some cases, in particular some OFDM-based waveforms, an affix may be included into a modulation symbol. In other cases, e.g. some 1090 single carrier-based wave-forms, an affix may be represented by a sequence of modulation symbols within the block symbol. It may be considered that in some cases a block symbol

[0545] is defined and / or used in the context of the associated structure.

[0546] Communicating may comprise transmitting or receiving. It may be considered that communicating like transmitting signalling is based on a SC-FDM based wave- form, and / or 1095 corresponds to a Frequency Domain Filtered (FDF) DFTS-OFDM wave-form. However,

[0547] the approaches may be applied to a Single Carrier based wave-form, e.g. a SC-FDM or

[0548] SC-FDE- wave-form, which may be pulse-shaped / FDF-based. It should be noted that SC-FDM may be considered DFT-spread OFDM, such that SC-FDM and DFTS-OFDM may

[0549] be used interchangeably. Alternatively, or additionally, the signalling (e.g., first signalling 1100 and / or second signalling) and / or beam / s (in particular, the first received beam and / or

[0550] second received beam) may be based on a wave-form with CP or comparable guard time.

[0551] The received beam and the transmission beam of the first beam pair may have the same (or similar) or different angular and / or spatial extensions; the received beam and the transmission beam of the second beam pair may have the same (or similar) or different angular 1105 and / or spatial extensions. It may be considered that the received beam and / or transmission beam of the first and / or second beam pair have angular extension of 20 degrees or

[0552] less, or 15 degrees or less, or 10 or 5 degrees or less, at least in one of horizontal or vertical direction, or both; different beams may have different angular extensions. An extended

[0553] P113137WO01 31 / 79guard interval or switching protection interval may have a duration corresponding to es- 1110 sentially or at least N CP (cyclic prefix) durations or equivalent duration, wherein N may

[0554] be 2, or 3 or 4. An equivalent to a CP duration may represent the CP duration associated

[0555] to signalling with CP (e.g., SC-FDM-based or OFDM-based) for a wave- form without CP

[0556] with the same or similar symbol time duration as the signalling with CP. Pulse-shaping (and / or performing FDF for) a modulation symbol and / or signalling, e.g. associated to 1115 a first sub-carrier or bandwidth, may comprise mapping the modulation symbol (and / or

[0557] the sample associated to it after FFT) to an associated second sub-carrier or part of the bandwidth, and / or applying a shaping operation regarding the power and / or amplitude and / or phase of the modulation symbol on the first sub-carrier and the second sub-carrier, wherein the shaping operation may be according to a shaping function. Pulse-shaping 1120 signalling may comprise pulse-shaping one or more symbols; pulse-shaped signalling may

[0558] in general comprise at least one pulse-shaped symbol. Pulse-shaping may be performed

[0559] based on a Nyquist-ffiter. It may be considered that pulse-shaping is performed based

[0560] on periodically extending a frequency distribution of modulation symbols (and / or associated samples after FFT) over a first number of sub-carrier to a larger, second number 1125 of sub-carriers, wherein a subset of the first number of sub-carriers from one end of the frequency distribution is appended at the other end of the first number of sub-carriers.

[0561] In some variants, communicating may be based on a numerology (which may, e.g., be represented by and / or correspond to and / or indicate a sub-carrier spacing and / or symbol

[0562] time length) and / or an SC-FDM based wave-form (including a FDF-DFTS-FDM based 1130 wave-form) or a single-carrier based wave-form. Whether to use pulse-shaping or FDF on

[0563] a SC-FDM or SC-based wave-form may depend on the modulation scheme (e.g., MCS)

[0564] used. Such wave- forms may utilise a cyclic prefix and / or benefit particularly from the described approaches. Communicating may comprise and / or be based on beamforming,

[0565] e.g. transmission beamforming and / or reception beamforming, respectively. It may be 1135 considered that a beam is produced by performing analog beamforming to provide the

[0566] beam, e.g. a beam corresponding to a reference beam. Thus, signalling may be adapted,

[0567] e.g. based on movement of the communication partner. A beam may for example be produced by performing analog beamforming to provide a beam corresponding to a reference

[0568] beam. This allows efficient postprocessing of a digitally formed beam, without requiring 1140 changes to a digital beamforming chain and / or without requiring changes to a standard defining beam forming precoders. In general, a beam may be produced by hybrid beamforming, and / or by digital beamforming, e.g. based on a precoder. This facilitates easy processing of beams, and / or limits the number of power amplifiers / ADC / DC A required

[0569] for antenna arrangements. It may be considered that a beam is produced by hybrid 1145 beamforming, e.g. by analog beamforming performed on a beam representation or beam

[0570] P113137WO01 32 / 79formed based on digital beamforming. Monitoring and / or performing cell search may be based on reception beamforming, e.g. analog or digital or hybrid reception beamforming.

[0571] The numerology may determine the length of a symbol time interval and / or the duration

[0572] of a cyclic prefix. The approaches described herein are particularly suitable to SC-FDM, 1150 to ensure orthogonality, in particular sub-carrier orthogonality, in corresponding systems,

[0573] but may be used for other wave-forms. Communicating may comprise utilising a waveform with cyclic prefix. The cyclic prefix may be based on a numerology, and may help keeping signalling orthogonal. Communicating may comprise, and / or be based on performing cell search, e.g. for a wireless device or terminal, or may comprise transmitting 1155 cell identifying signalling and / or a selection indication, based on which a radio node receiving the selection indication may select a signalling bandwidth from a set of signalling bandwidths for performing cell search.

[0574] A beam or beam pair may in general be targeted at one radio node, or a group of radio

[0575] nodes and / or an area including one or more radio nodes. In many cases, a beam or beam 1160 pair may be receiver-specific (e.g., UE-specffic), such that only one radio node is served

[0576] per beam / beam pair. A beam pair switch or switch of received beam (e.g., by using a different reception beam) and / or transmission beam may be performed at a border of a transmission timing structure, e.g. a slot border, or within a slot, for example between symbols. Some tuning of radio circuitry, e.g. for receiving and / or transmitting, may be 1165 performed. Beam pair switching may comprise switching from a second received beam

[0577] to a first received beam, and / or from a second transmission beam to a first transmission

[0578] beam. Switching may comprise inserting a guard period to cover retuning time; however, circuitry may be adapted to switch sufficiently quickly to essentially be instantaneous;

[0579] this may in particular be the case when digital reception beamforming is used to switch 1170 reception beams for switching received beams.

[0580] A reference beam (or reference signalling beam) may be a beam comprising reference signalling, based on which for example a of beam signalling characteristics may be determined, e.g. measured and / or estimated. A signalling beam may comprise signalling like control signalling and / or data signalling and / or reference signalling. A reference beam 1175 may be transmitted by a source or transmitting radio node, in which case one or more

[0581] beam signalling characteristics may be reported to it from a receiver, e.g. a wireless device. However, in some cases it may be received by the radio node from another radio

[0582] node or wireless device. In this case, one or more beam signalling characteristics may

[0583] be determined by the radio node. A signalling beam may be a transmission beam, or a 1180 reception beam. A set of signalling characteristics may comprise a plurality of subsets

[0584] of beam signalling characteristics, each subset pertaining to a different reference beam.

[0585] Thus, a reference beam may be associated to different beam signalling characteristics.

[0586] P113137WO01 33 / 79A beam signalling characteristic, respectively a set of such characteristics, may represent and / or indicate a signal strength and / or signal quality of a beam and / or a delay charac- 1185 teristic and / or be associated with received and / or measured signalling carried on a beam.

[0587] Beam signalling characteristics and / or delay characteristics may in particular pertain to, and / or indicate, a number and / or list and / or order of beams with best (e.g., lowest mean

[0588] delay and / or lowest spread / range) timing or delay spread, and / or of strongest and / or

[0589] best quality beams, e.g. with associated delay spread. A beam signalling characteristic 1190 may be based on measurement / s performed on reference signalling carried on the reference beam it pertains to. The measurement / s may be performed by the radio node, or another node or wireless device. The use of reference signalling allows improved accuracy

[0590] and / or gauging of the measurements. In some cases, a beam and / or beam pair may be represented by a beam identity indication, e.g. a beam or beam pair number. Such an in- 1195 dication may be represented by one or more signalling sequences (e.g., a specific reference signalling sequences or sequences), which may be transmitted on the beam and / or beam

[0591] pair, and / or a signalling characteristic and / or a resource / s used (e.g., time / frequency

[0592] and / or code) and / or a specific RNTI (e.g., used for scrambling a CRC for some messages

[0593] or transmissions) and / or by information provided in signalling, e.g. control signalling 1200 and / or system signalling, on the beam and / or beam pair, e.g. encoded and / or provided

[0594] in an information held or as information element in some form of message of signalling,

[0595] e.g. DCI and / or MAC and / or RRC signalling.

[0596] A reference beam may in general be one of a set of reference beams, the second set of reference beams being associated to the set of signalling beams. The sets being associated 1205 may refer to at least one beam of the first set being associated and / or corresponding to the

[0597] second set (or vice versa), e.g. being based on it, for example by having the same analog

[0598] or digital beamforming parameters and / or precoder and / or the same shape before analog beamforming, and / or being a modified form thereof, e.g. by performing additional analog beamforming. The set of signalling beams may be referred to as a first set of beams, a 1210 set of corresponding reference beams may be referred to as second set of beams.

[0599] In some variants, a reference beam and / or reference beams and / or reference signalling may correspond to and / or carry random access signalling, e.g. a random access preamble. Such

[0600] a reference beam or signalling may be transmitted by another radio node. The signalling

[0601] may indicate which beam is used for transmitting. Alternatively, the reference beams may 1215 be beams receiving the random access signalling. Random access signalling may be used

[0602] for initial connection to the radio node and / or a cell provided by the radio node, and / or for reconnection. Utilising random access signalling facilitates quick and early beam selection.

[0603] The random access signalling may be on a random access channel, e.g. based on broadcast information provided by the radio node (the radio node performing the beam selection), 1220

[0604] P113137WO01 34 / 79e.g. with synchronisation signalling (e.g., SSB block and / or associated thereto). The reference signalling may correspond to synchronisation signalling, e.g. transmitted by the

[0605] radio node in a plurality of beams. The characteristics may be reported on by a node receiving the synchronisation signalling, e.g. in a random access process, e.g. a Msg3

[0606] for contention resolution, which may be transmitted on a physical uplink shared channel 1225 based on a resource allocation provided by the radio node.

[0607] A delay characteristic (which may correspond to delay spread information) and / or a measurement report may represent and / or indicate at least one of mean delay, and / or

[0608] delay spread, and / or delay distribution, and / or delay spread distribution, and / or delay

[0609] spread range, and / or relative delay spread, and / or energy (or power) distribution, and / or 1230 impulse response to received signalling, and / or the power delay profile of the received signals, and / or power delay profile related parameters of the received signal. A mean

[0610] delay may represent the mean value and / or an averaged value of the delay spread, which

[0611] may be weighted or unweighted. A distribution may be distribution over time / delay, e.g.

[0612] of received power and / or energy of a signal. A range may indicate an interval of the delay 1235 spread distribution over time / delay, which may cover a predetermined percentage of the

[0613] delay spread respective received energy or power, e.g. 50% or more, 75% or more, 90% or

[0614] more, or 100%. A relative delay spread may indicate a relation to a threshold delay, e.g.

[0615] of the mean delay, and / or a shift relative to an expected and / or configured timing, e.g. a

[0616] timing at which the signalling would have been expected based on the scheduling, and / or 1240 a relation to a cyclic prefix duration (which may be considered on form of a threshold).

[0617] Energy distribution or power distribution may pertain to the energy or power received over

[0618] the time interval of the delay spread. A power delay profile may pertain to representations

[0619] of the received signals, or the received signals energy / power, across time / delay. Power

[0620] delay profile related parameters may pertain to metrics computed from the power delay 1245 profile. Different values and forms of delay spread information and / or report may be

[0621] used, allowing a wide range of capabilities. The kind of information represented by a measurement report may be predefined, or be configured or configurable, e.g. with a measurement configuration and / or reference signalling configuration, in particular with

[0622] higher layer signalling like RRC or MAC signalling and / or physical layer signalling like 1250 DCI signalling.

[0623] In general, different beam pair may differ in at least one beam; for example, a beam

[0624] pair using a first received beam and a first transmission beam may be considered to be different from a second beam pair using the first received beam and a second transmission

[0625] beam. A transmission beam using no precoding and / or beamforming, for example using 1255 the natural antenna profile, may be considered as a special form of transmission beam of

[0626] a transmission beam pair. A beam may be indicated to a radio node by a transmitter

[0627] P113137WO01 35 / 79with a beam indication and / or a configuration, which for example may indicate beam parameters and / or time / frequency resources associated to the beam and / or a transmission

[0628] mode and / or antenna profile and / or antenna port and / or precoder associated to the 1260 beam. Different beams may be provided with different content, for example different received beams may carry different signalling; however, there may be considered cases

[0629] in which different beams carry the same signalling, for example the same data signalling

[0630] and / or reference signalling. The beams may be transmitted by the same node and / or transmission point and / or antenna arrangement, or by different nodes and / or transmission 1265 points and / or antenna arrangements.

[0631] Communicating utilising a beam pair or a beam may comprise receiving signalling on a received beam (which may be a beam of a beam pair), and / or transmitting signalling on

[0632] a beam, e.g. a beam of a beam pair. The following terms are to be interpreted from

[0633] the point of view of the referred radio node: a received beam may be a beam carrying 1270 signalling received by the radio node (for reception, the radio node may use a reception

[0634] beam, e.g. directed to the received beam, or be non-beamformed). A transmission beam

[0635] may be a beam used by the radio node to transmit signalling. A beam pair may consist

[0636] of a received beam and a transmission beam. The transmission beam and the received

[0637] beam of a beam pair may be associated to each and / or correspond to each other, e.g. 1275 such that signalling on the received beam and signalling on a transmission beam travel essentially the same path (but in opposite directions), e.g. at least in a stationary or

[0638] almost stationary condition. It should be noted that the terms “first” and “second”

[0639] do not necessarily denote an order in time; a second signalling may be received and / or transmitted before, or in some cases simultaneous to, first signalling, or vice versa. The 1280 received beam and transmission beam of a beam pair may be on the same carrier or frequency range or bandwidth part, e.g. in a TDD operation; however, variants with

[0640] FDD may be considered as well. Different beam pairs may operate on the same frequency

[0641] ranges or carriers or bandwidth parts (e.g., such that transmission beams operate on

[0642] the same frequency range or carriers or bandwidth part, and received beams on the same 1285 frequency range or carriers or bandwidth part (the transmission beam and received beams

[0643] may be on the same or different ranges or carriers or BWPs). Communicating utilizing a

[0644] first beam pair and / or first beam may be based on, and / or comprise, switching from the

[0645] second beam pair or second beam to the first beam pair or first beam for communicating.

[0646] The switching may be controlled by the network, for example a network node (which may 1290 be the source or transmitter of the received beam of the first beam pair and / or second

[0647] beam pair, or be associated thereto, for example associated transmission points or nodes

[0648] in dual connectivity). Such controlling may comprise transmitting control signalling, e.g. physical layer signalling and / or higher layer signalling. In some cases, the switching may

[0649] P113137WO01 36 / 79be performed by the radio node without additional control signalling, for example based 1295 on measurements on signal quality and / or signal strength of beam pairs (e.g., of first and

[0650] second received beams), in particular the first beam pair and / or the second beam pair.

[0651] For example, it may be switched to the first beam pair (or first beam) if the signal quality

[0652] or signal strength measured on the second beam pair (or second beam) is considered to

[0653] be insufficient, and / or worse than corresponding measurements on the first beam pair 1300 indicate. Measurements performed on a beam pair (or beam) may in particular comprise measurements performed on a received beam of the beam pair. It may be considered that

[0654] the timing indication may be determined before switching from the second beam pair to

[0655] the first beam pair for communicating. Thus, the synchronization may be in place and / or

[0656] the timing indication may be available for synchronising) when starting communication 1305 utilizing the first beam pair or first beam. However, in some cases the timing indication

[0657] may be determined after switching to the first beam pair or first beam. This may be

[0658] in particular useful if first signalling is expected to be received after the switching only,

[0659] for example based on a periodicity or scheduled timing of suitable reference signalling

[0660] on the first beam pair, e.g. first received beam. In general, a reception beam of a node 1310 may be associated to and / or correspond to a transmission beam of the node, e.g. such

[0661] that the (spatial) angle of reception of the reception beam and the (spatial) angle of transmission of the transmission beam at least partially, or essentially or fully, overlap

[0662] and / or coincide, in particular for TDD operation and / or independent of frequency. Spatial correspondence between beams may be considered in some cases, e.g. such that a beam 1315 pair (e.g., transmission beam of a transmitting node and reception beam of a receiving

[0663] node) may be considered to comprise corresponding beams (e.g., the reception beam is suitable and / or the best beam to receive transmissions on the transmission beam, e.g.

[0664] based on a threshold signal quality and / or signal strength and / or measurements); to each

[0665] of such beams, there may be an associated or corresponding complementary beam of the 1320 respective node (e.g., to a transmission beam of a beam pair, there may be associated a reception beam of the transmitting node, and / or to the reception beam of a beam pair,

[0666] there may be associated a transmitting beam of the receiving node; if the beams (e.g.,

[0667] at least essentially or substantially) overlap (e.g., in spatial angle), in some cases a beam

[0668] pair may be considered to indicate four beams (or actually, two beam pairs). 1325

[0669] In some cases, to one or more beams or signals or signallings may be associated a Quasi-CoLocation (QCL) characteristic or set of characteristics, or QCL class (also referred to

[0670] as QCL type) or QCL identity; beams or signal or signallings sharing such may be considered to be Quasi-Colocated. Quasi-Colocated beams or signals or signallings may be considered (e.g., by a receiver) as the same beam or originating from the same transmit- 1330 ter or transmission source, at least in regard to the QCL characteristic or set or class or

[0671] P113137WO01 37 / 79identity, and / or to share the characteristic / s. QCL characteristics may pertain to propagation of signalling, and / or one or more delay characteristics, and / or pathloss, and / or

[0672] signal quality, and / or signal strength, and / or beam direction, and / or beam shape (in particular, angle or area, e.g. area of coverage), and / or Doppler shift, and / or Doppler 1335 spread, and / or delay spread, and / or time synchronisation, and / or frequency synchronisation, and / or one or more other parameters, e.g. pertaining to a propagation channel and / or spatial RX param eter / s (which may refer to reception beam and / or transmission

[0673] beam, e.g. shape or coverage or direction). A QCL characteristic may pertain to a specific channel (e.g., physical layer channel like a control channel or data channel) and / or 1340 reference signalling type and / or antenna port. Different QCL classes or types may pertain to different QCL characteristics or sets of characteristics; a QCL class may define and / or pertain to one or more criteria and / or thresholds and / or ranges for one or more

[0674] QCL characteristics beams have to fulfill to be considered Quasi-Colocated according to

[0675] this class; a QCL identity may refer to and / or represent all beams being quasi-colocated, 1345 according to a QCL class. Different classes may pertain to one or more of the same characteristics (e.g., different classes may have different criteria and / or thresholds and / or

[0676] ranges for one or more characteristics) and / or to different characteristics. A QCL indication may be seen as a form of beam indication, e.g. pertaining to all beams belonging

[0677] to one QCL class and / or QCL identity and / or quasi-colocated beams. A QCL identity 1350 may be indicated by a QCL indication. In some cases, a beam, and / or a beam indication,

[0678] may be considered to refer and / or represent a to a QCL identity, and / or to represent

[0679] quasi-colocated beams or signals or signallings.

[0680] Transmission on multiple layers (multi-layer transmission) may refer to transmission of communication signalling and / or reference signalling simultaneously in one or more beams 1355 and / or using a plurality of transmission sources, e.g. controlled by one network node

[0681] or one wireless device. The layers may refer to layers of transmission; a layer may be considered to represent one data or signalling stream. Different layers may carry different

[0682] data and / or data streams, e.g., to increase data throughput. In some cases, the same

[0683] data or data stream may be transported on different layers, e.g. to increase reliability. 1360 Multi-layer transmission may provide diversity, e.g. transmission diversity and / or spatial diversity. It may be considered that multi-layer transmission comprises 2, or more than

[0684] 2 layers; the number of layers of transmission may be represented by a rank or rank indication.

[0685] A transmission source may in particular comprise, and / or be represented by, and / or 1365 associated to, an antenna or group of antenna elements or antenna sub-array or antenna

[0686] array or transmission point or TRP or TP (Transmission Point) or access point. In some

[0687] cases, a transmission source may be represented or representable, and / or correspond

[0688] P113137WO01 38 / 79to, and / or associated to, an antenna port or layer of transmission, e.g. for multi-layer transmission. Different transmission sources may in particular comprise different and / or 1370 separately controllable antenna element / s or (sub-)arrays and / or be associated to different antenna ports. In particular, analog beamforming may be used, with separate analog control of the different transmission sources. An antenna port may indicate a transmission

[0689] source, and / or a one or more transmission parameter, in particular of reference signalling associated to the antenna port. In particular, transmission parameters pertaining to, 1375 and / or indicating a frequency domain distribution or mapping (e.g., which comb to use and / or which sub-carrier or frequency offset to use, or similar) of modulation symbols

[0690] of the reference signalling, and / or to which cyclic shift to use (e.g., to shift elements of

[0691] a modulation symbol sequence, or a root sequence, or a sequence based on or derived

[0692] from the root sequence) and / or to which cover code to use (e.g., (e.g., to shift elements 1380 of a modulation symbol sequence, or a root sequence, or a sequence based on or derived

[0693] from the root sequence). In some cases, a transmission source may represent a target for reception, e.g. if it is implemented as a TRP or AP (Access Point).

[0694] In some variants, reference signalling may be and / or comprise CSI-RS and / or PT-RS

[0695] and / or DMRS, e.g. transmitted by the network node. In other variants, the reference 1385 signalling may be transmitted by a UE, e.g. to a network node or other UE, in which

[0696] case it may comprise and / or be Sounding Reference signalling. Other, e.g. new, forms

[0697] of reference signalling may be considered and / or used. In general, a modulation symbol

[0698] of reference signalling respectively a resource element carrying it may be associated to a

[0699] cyclic prefix. 1390

[0700] Data signalling may be on a data channel, for example on a PDSCH or PSSCH, or on a dedicated data channel, e.g. for low latency and / or high reliability, e.g. a URLLC channel.

[0701] Control signalling may be on a control channel, for example on a common control channel

[0702] or a PDCCH or PSCCH, and / or comprise one or more DCI messages or SCI messages.

[0703] Reference signalling may be associated to control signalling and / or data signalling, e.g. 1395 DM-RS and / or PT-RS.

[0704] Reference signalling, for example, may comprise DM-RS and / or pilot signalling and / or discovery signalling and / or synchronisation signalling and / or sounding signalling and / or

[0705] phase tracking signalling and / or cell-specific reference signalling and / or user-specific signalling, in particular CSI-RS. Reference signalling in general may be signalling with one 1400 or more signalling characteristics, in particular transmission power and / or sequence of modulation symbols and / or resource distribution and / or phase distribution known to the receiver. Thus, the receiver can use the reference signalling as a reference and / or for training and / or for compensation. The receiver can be informed about the reference signalling

[0706] P113137WO01 39 / 79by the transmitter, e.g. being configured and / or signalling with control signalling, in par- 1405 ticular physical layer signalling and / or higher layer signalling (e.g., DCI and / or RRC signalling), and / or may determine the corresponding information itself, e.g. a network node configuring a UE to transmit reference signalling. Reference signalling may be signalling comprising one or more reference symbols and / or structures. Reference signalling may

[0707] be adapted for gauging and / or estimating and / or representing transmission conditions, 1410 e.g. channel conditions and / or transmission path conditions and / or channel (or signal or transmission) quality. It may be considered that the transmission characteristics (e.g.,

[0708] signal strength and / or form and / or modulation and / or timing) of reference signalling are available for both transmitter and receiver of the signalling (e.g., due to being predefined and / or configured or configurable and / or being communicated). Different types of 1415 reference signalling may be considered, e.g. pertaining to uplink, downlink or sidelink,

[0709] cell-specific (in particular, cell- wide, e.g., CRS) or device or user specific (addressed to

[0710] a specific target or user equipment, e.g., CSI-RS), demodulation-related (e.g., DMRS) and / or signal strength related, e.g. power-related or energy-related or amplitude-related

[0711] (e.g., SRS or pilot signalling) and / or phase-related, etc. 1420

[0712] References to specific resource structures like an allocation unit and / or block symbol and / or block symbol group and / or transmission timing structure and / or symbol and / or

[0713] slot and / or mini-slot and / or sub-carrier 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 1425 examples of a transmission timing structure are transmission time interval (TTI), 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, or more symbols, 1430 e.g. less symbols than symbols in a slot. A transmission timing structure may cover a

[0714] time interval of a specific length, which may be dependent on symbol time length and / or

[0715] cyclic prefix used. A transmission timing structure may pertain to, and / or cover, a specific

[0716] time interval in a time stream, e.g. synchronized for communication. Timing structures

[0717] used and / or scheduled for transmission, e.g. slot and / or mini-slots, may be scheduled in 1435 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

[0718] 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 trans- 1440 mission timing structure may have a duration (length in time) determined based on the

[0719] P113137WO01 40 / 79durations 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. The 1445 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

[0720] any symbol of the transmission timing structure, in particular one or more slots.

[0721] A transmission quality parameter may in general correspond to the number R of retransmissions and / or number T of total transmissions, and / or coding (e.g., number of coding 1450 bits, e.g. for error detection coding and / or error correction coding like FEC coding) and / or code rate and / or BLER and / or BER requirements and / or transmission power

[0722] level (e.g., minimum level and / or target level and / or base power level P0 and / or transmission power control command, TPC, step size) and / or signal quality, e.g. SNR and / or

[0723] SIR and / or SINR and / or power density and / or energy density. 1455

[0724] A signalling sequence or sequence (e.g. of an allocation unit or block symbol or symbol

[0725] time interval, and / or carried or transmitted on an allocation unit or block symbol or symbol time interval) may be based on a sequence root, e.g. a root sequence and / or a

[0726] root parameter and / or root index and / or seed. A sequence root in general may represent

[0727] or indicate a base for deriving or determining a signalling sequence; the root may be 1460 associated to, and / or represent a sequence directly, and / or indicate or represent a base sequence and / or seed. Examples of sequence roots may comprise a Zadoff Chu root sequence, a sequence seed, e.g. a seed for a Gold sequence, or a Golay complimentary sequence. A signalling sequence may be derived or derivable from, and / or be based on, a sequency root, e.g. based on a code, which may represent a shift or operation or processing 1465 on the root sequence or a sequence indicated by the sequence root, e.g. to provide the signalling sequence; the signalling sequence may be based on such shifted or processed or operated on root sequence. The code may in particular represent a cyclic shift and / or

[0728] phase shift and / or phase ramp (e.g., an amount for such). The code may assign one operation or shift for each allocation unit. 1470

[0729] In general, a signalling sequence associated to an allocation unit (and / or the allocation

[0730] units) associated to control signalling (and / or reference signalling) may be based on a

[0731] root sequence which may be a M-sequence or Zadoff-Chu sequence, or a Gold or Golay sequence, or another sequence with suitable characteristics regarding correlation and / or interference (e.g., self- interference and / or interference with other or neighboring transmit- 1475 ters). Different sequences may be used as root sequences for different signalling sequences,

[0732] or the same sequence may be used. If different sequences are used, they may be of the

[0733] P113137WO01 41 / 79same type (Gold, Golay, M- or Zadoff-Chu, for example). The (signalling and / or root) sequences may correspond to or be time-domain sequences, e.g. time domain Zadoff-Chu

[0734] and / or time-domain M sequences. 1480

[0735] In some cases, a shifted object like a signalling or signals or sequences or information

[0736] may be shifted, e.g. relative to a predecessor (e.g., one is subject to a shift, and the

[0737] shifted version is used), or relative to another (e.g., one associated to one signalling or allocation unit may be shifted to another associated to a second signalling or allocation

[0738] unit, both may be used). One possible way of shifting is operating a code on it, e.g. to 1485 multiply each element of a shifting object with a factor. A ramping (e.g. multiplying with

[0739] a monotonously increasing or periodic factor) may be considered an example of shifting.

[0740] Another is a cyclic shift in a domain or interval. A cyclic shift (or circular shift) may correspond to a rearrangement of the elements in the shifting object, corresponding to moving the final element or elements to the first position, while shifting all other entries 1490 to the next position, or by performing the inverse operation (such that the shifted object

[0741] as the result will have the same elements as the shifting object, in a shifted but similar order). Shifting in general may be specific to an interval in a domain, e.g. an allocation

[0742] unit in time domain, or a bandwidth in frequency domain. For example, it may be considered that signals or modulation symbols in an allocation unit are shifted, such that 1495 the order of the modulation symbols or signals is shifted in the allocation unit. In another example, allocation units may be shifted, e.g. in a larger time interval - this may leave

[0743] signals in the allocation units unshifted with reference to the individual allocation unit,

[0744] but may change the order of the allocation units. Domains for shifting may for example be

[0745] time domain and / or phase domain and / or frequency domain. Multiple shifts in the same 1500 domain or different domains, and / or the same interval or different intervals (differently

[0746] sized intervals, for example) may be performed.

[0747] Reference signalling may have a type. Types of reference signalling may include synchronisation signalling, and / or DM-RS (used to facilitate demodulation of associated data signalling and / or control signalling), and / or PT-RS (used to facilitate phase tracking of 1505 associated data signalling and / or control signalling, e.g. within a time interval or symbol

[0748] or allocation unit carrying such signalling), and / or CSI-RS (e.g., used for channel estimation and / or reporting). It may be considered that PT-RS are inserted into a bit sequence,

[0749] or a modulation symbol sequence, which may represent data. For example, PT-RS may

[0750] be mapped onto sub-carriers of a symbol also carrying data symbols. Accordingly, PT-RS 1510 insertion may be optimised for hardware implementations. In some cases, PT-RS may be modulated differently and / or independently of the modulation symbols representing data

[0751] (or data bits).

[0752] P113137WO01 42 / 79A comb structure, or shorter comb, may indicate a distribution, or periodic arrangement of reference signalling, in particular in frequency space, e.g. between an upper and lower 1515 frequency. A comb may pertain to one OFDMA symbol and / or SC-FDMA symbol and / or

[0753] one (the same) symbol time interval and / or one allocation unit. A comb may have width

[0754] or size N and / or may pertain to, and / or be associated to, specific signalling and / or a type

[0755] of signalling, e.g. a type of reference signalling. The width N may indicate how many

[0756] empty sub-carriers are between (e.g., non-neighbouring) sub-carriers carrying an element 1520 or signal or symbol of the signalling (e.g., this number may be N-l), or how many empty

[0757] sub-carriers and non-empty sub-carriers form a pattern that is repeated in frequency domain. In general, each comb may indicate that at least one empty sub-carrier is to be between non-empty sub-carriers. In this context, empty may refer to empty regarding

[0758] the pattern or distribution of the signalling associated to the comb (and non-empty may 1525 refer to a sub-carrier carrying an element or symbol of the associated signalling); in

[0759] some cases, other signallings (which may have a comb structure as well) may be carried

[0760] on empty sub-carriers, e.g. transmitted using other transmission sources and / or other devices, and / or mapped into the comb (e.g., for a DMRS comb, data signalling may be mapped on sub-carriers not carrying DMRS). 1530

[0761] A comb structure may generally describe a structure in which for every N-th (N may

[0762] be an integer) resource element and / or sub-carrier a reference signal or an element of a sequence of the reference signalling, and / or representing the reference signalling, and / or

[0763] on which the reference signalling is based, is mapped to, and / or represented by signalling

[0764] the resource element and / or sub-carrier, in particular an element (symbol) of a modulation 1535 symbol sequence, or an element of a sequence. N may be called the width of the comb.

[0765] Generally, the comb may indicate the periodicity of the pattern inside the frequency range

[0766] of the reference signalling. The pattern may in particular pertain to one reference signal and / or resource element or sub-carrier for transmitting a reference signal, such that the

[0767] comb may be considered to indicate that on every Nth resource element (in particular, 1540 only there) and / or sub-carrier there is to be a reference signal or element of an associated sequence, and / or how many resource elements and / or sub-carriers are between resource elements and / or sub-carriers with reference signals. However, there may be considered variants, in which the pattern represents more than one reference signals. The pattern

[0768] may also generally represent and / or indicate one or more empty signals and / or one or 1545 more data signals (respectively associated resource elements and / or sub-carriers). For

[0769] each comb or comb structure with a width or size of N, there may be N or f(N) different available individual combs. For example, for N=2, there may be two combs shifted in frequency space by one, or an odd number, of sub-carriers or PRBs (e.g., based on a frequency domain offset, or a sub-carrier offset). A comb structure or comb of width or 1550

[0770] P113137WO01 43 / 79size of N may be indicated as N-comb. Specific combs of this width may be numbered within N. For example, for a 2-comb, there may be a comb 1 (or Cl) and a comb 2

[0771] (or C2), which may be shifted relative to each other, e.g. to dovetail such that all subcarrier covered by both combs carry signalling (associated to Cl and C2 alternatingly in frequency domain). 1555

[0772] A comb may comprise two or more, for example at least three or at least four, repetitions of

[0773] the pattern. The comb may indicate a reference and / or indication, e.g. a resource element and / or subcarner, which may be related to the upper and / or lower boundary in frequency, regarding the arrangement and / or location in frequency of a first pattern, and / or the relative shift of the pattern and / or comb in frequency. Generally, a comb structure may 1560 cover at least part, and / or at least the majority, and / or essentially all or all resource elements and / or sub-carriers of the plurality of resource elements and / or sub-carriers, and / or the symbol. A comb structure may result from combining two comb structures,

[0774] which may in particular comb structures with pattern comprising only one reference

[0775] signal. A comb structure may be determined and / or amended before transmission, e.g. 1565 based on other reference signalling to be transmitted, e.g. on a different antenna port.

[0776] In this context, reference signals may be replaced by empty signals to avoid overlap

[0777] and / or interference. Generally, if the other reference signalling utilises a comb structure

[0778] as well, a different / new comb (as a combination of combs) may be considered to be determined, e.g. with less dense reference signal distribution and / or a different / wider 1570 pattern. Alternatively, or additionally, combs may be combined to increase the reference

[0779] signal density, e.g. by combining combs with different widths, and / or with shifted offsets.

[0780] Generally, a comb structure may represent and / or comprise and / or be comprised of any

[0781] of the combs / comb structures described herein.

[0782] A buffer state report (or buffer status report, BSR) may comprise information represent- 1575 ing the presence and / or size of data to be transmitted (e.g., available in one or more buffers, for example provided by higher layers). The size may be indicated explicitly, and / or indexed to range / s of sizes, and / or may pertain to one or more different channel / s and / or acknowledgement processes and / or higher layers and / or channel groups / s, e.g,

[0783] one or more logical channel / s and / or transport channel / s and / or groups thereof: The 1580 structure of a BSR may be predefined and / or configurable of configured, e.g. to override and / or amend a predefined structure, for example with higher layer signalling, e.g. RRC signalling. There may be different forms of BSR with different levels of resolution and / or information, e.g. a more detailed long BSR and a less detailed short BSR. A short BSR

[0784] may concatenate and / or combine information of a long BSR, e.g. providing sums for data 1585 available for one or more channels and / or or channels groups and / or buffers, which might

[0785] P113137WO01 44 / 79be represented individually in a long BSR; and / or may index a less-detailed range scheme for data available or buffered. A BSR may be used in lieu of a scheduling request, e.g.

[0786] by a network node scheduling or allocating (uplink) resources for the transmitting radio

[0787] node like a wireless device or UE or IAB node. 1590

[0788] 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

[0789] is considered a carrier medium arrangement carrying and / or storing a program product

[0790] as described herein. 1595

[0791] A carrier medium arrangement may comprise one or more carrier media. Generally, a

[0792] 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

[0793] 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 1600 guiding / transporting medium may be adapted to carry and / or carry and / or store signals,

[0794] 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,

[0795] may be adapted to guide such signals to carry them. A carrier medium, in particular a guiding / transporting medium, may comprise the electromagnetic held, e.g. radio waves 1605 or microwaves, and / or optically transmissive material, e.g. glass fiber, and / or cable. A

[0796] storage medium may comprise at least one of a memory, which may be volatile or nonvolatile, a buffer, a cache, an optical disc, magnetic memory, Hash memory, etc.

[0797] A system comprising one or more radio nodes as described herein, in particular a network

[0798] node and a user equipment, is described. The system may be a wireless communication 1610 system, and / or provide and / or represent a radio access network.

[0799] Moreover, there may be generally considered a method of operating an information system, the method comprising providing information. Alternatively, or additionally, an information system adapted for providing information may be considered. Providing information may comprise providing information for, and / or to, a target system, which 1615 may comprise and / or be implemented as radio access network and / or a radio node, in particular a network node or user equipment or terminal. Providing information may comprise transferring and / or streaming and / or sending and / or passing on the information, and / or offering the information for such and / or for download, and / or triggering such providing, e.g. by triggering a different system or node to stream and / or transfer and / or 1620 send and / or pass on the information. The information system may comprise, and / or be connected or connectable to, a target, for example via one or more intermediate systems,

[0800] P113137WO01 45 / 79e.g. a core network and / or internet and / or private or local network. Information may be provided utilising and / or via such intermediate system / s. Providing information may be

[0801] for radio transmission and / or for transmission via an air interface and / or utilising a RAN 1625 or radio node as described herein. Connecting the information system to a target, and / or providing information, may be based on a target indication, and / or adaptive to a target indication. A target indication may indicate the target, and / or one or more parameters of transmission pertaining to the target and / or the paths or connections over which the information is provided to the target. Such parameter / s may in particular pertain to the air 1630 interface and / or radio access network and / or radio node and / or network node. Example parameters may indicate for example type and / or nature of the target, and / or transmission capacity (e.g., data rate) and / or latency and / or reliability and / or cost, respectively

[0802] one or more estimates thereof. The target indication may be provided by the target, or determined by the information system, e.g. based on information received from the target 1635 and / or historical information, and / or be provided by a user, for example a user operating

[0803] the target or a device in communication with the target, e.g. via the RAN and / or air interface. For example, a user may indicate on a user equipment communicating with

[0804] the information system that information is to be provided via a RAN, e.g. by selecting

[0805] from a selection provided by the information system, for example on a user application 1640 or user interface, which may be a web interface. An information system may comprise

[0806] one or more information nodes. An information node may generally comprise processing circuitry and / or communication circuitry. In particular, an information system and / or an information node may be implemented as a computer and / or a computer arrangement,

[0807] e.g. a host computer or host computer arrangement and / or server or server arrangement. 1645 In some variants, an interaction server (e.g., web server) of the information system may provide a user interface, and based on user input may trigger transmitting and / or streaming information provision to the user (and / or the target) from another server, which may

[0808] be connected or connectable to the interaction server and / or be part of the information

[0809] system or be connected or connectable thereto. The information may be any kind of data, 1650 in particular data intended for a user of for use at a terminal, e.g. video data and / or audio

[0810] data and / or location data and / or interactive data and / or game-related data and / or environmental data and / or technical data and / or traffic data and / or vehicular data and / or circumstantial data and / or operational data. The information provided by the information system may be mapped to, and / or mappable to, and / or be intended for mapping to, 1655 communication or data signalling and / or one or more data channels as described herein

[0811] (which may be signalling or channel / s of an air interface and / or used within a RAN

[0812] and / or for radio transmission). It may be considered that the information is formatted

[0813] based on the target indication and / or target, e.g. regarding data amount and / or data

[0814] rate and / or data structure and / or timing, which in particular may be pertaining to a 1660

[0815] P113137WO01 46 / 79mapping to communication or data signalling and / or a data channel. Mapping information to data signalling and / or data channel / s may be considered to refer to using the signalling / channel / s to carry the data, e.g. on higher layers of communication, with the signalling / channel / s underlying the transmission. A target indication generally may comprise different components, which may have different sources, and / or which may indicate 1665 different characteristics of the target and / or communication path / s thereto. A format of information may be specifically selected, e.g. from a set of different formats, for information to be transmitted on an air interface and / or by a RAN as described herein. This may

[0816] be particularly pertinent since an air interface may be limited in terms of capacity and / or

[0817] of predictability, and / or potentially be cost sensitive. The format may be selected to be 1670 adapted to the transmission indication, which may in particular indicate that a RAN or

[0818] radio node as described herein is in the path (which may be the indicated and / or planned

[0819] and / or expected path) of information between the target and the information system. A (communication) path of information may represent the interface / s (e.g., air and / or cable interfaces) and / or the intermediate system / s (if any), between the information system 1675 and / or the node providing or transferring the information, and the target, over which the information is, or is to be, passed on. A path may be (at least partly) undetermined

[0820] when a target indication is provided, and / or the information is provided / transferred by

[0821] the information system, e.g. if an internet is involved, which may comprise multiple, dynamically chosen paths. Information and / or a format used for information may be 1680 packet-based, and / or be mapped, and / or be mappable and / or be intended for mapping,

[0822] to packets. Alternatively, or additionally, there may be considered a method for operating a target device comprising providing a target indicating to an information system.

[0823] More alternatively, or additionally, a target device may be considered, the target device

[0824] being adapted for providing a target indication to an information system. In another ap- 1685 proach, there may be considered a target indication tool adapted for, and / or comprising

[0825] an indication module for, providing a target indication to an information system. The

[0826] target device may generally be a target as described above. A target indication tool may comprise, and / or be implemented as, software and / or application or app, and / or web interface or user interface, and / or may comprise one or more modules for implementing 1690 actions performed and / or controlled by the tool. The tool and / or target device may be adapted for, and / or the method may comprise, receiving a user input, based on which a

[0827] target indicating may be determined and / or provided. Alternatively, or additionally, the

[0828] tool and / or target device may be adapted for, and / or the method may comprise, receiving information and / or communication signalling carrying information, and / or operating on, 1695 and / or presenting (e.g., on a screen and / or as audio or as other form of indication), information. The information may be based on received information and / or communication signalling carrying information. Presenting information may comprise processing received

[0829] P113137WO01 47 / 79information, e.g. decoding and / or transforming, in particular between different formats, and / or for hardware used for presenting. Operating on information may be independent of 1700 or without presenting, and / or proceed or succeed presenting, and / or may be without user interaction or even user reception, for example for automatic processes, or target devices without (e.g., regular) user interaction like MTC devices, of for automotive or transport

[0830] or industrial use. The information or communication signalling may be expected and / or received based on the target indication. Presenting and / or operating on information may 1705 generally comprise one or more processing steps, in particular decoding and / or executing and / or interpreting and / or transforming information. Operating on information may generally comprise relaying and / or transmitting the information, e.g. on an air interface,

[0831] which may include mapping the information onto signalling (such mapping may generally pertain to one or more layers, e.g. one or more layers of an air interface, e.g. RLC (Radio 1710 Link Control) layer and / or MAC layer and / or physical layer / s). The information may be imprinted (or mapped) on communication signalling based on the target indication, which

[0832] may make it particularly suitable for use in a RAN (e.g., for a target device like a network

[0833] node or in particular a UE or terminal). The tool may generally be adapted for use on a

[0834] target device, like a UE or terminal. Generally, the tool may provide multiple function- 1715 alities, e.g. for providing and / or selecting the target indication, and / or presenting, e.g.

[0835] video and / or audio, and / or operating on and / or storing received information. Providing

[0836] a target indication may comprise transmitting or transferring the indication as signalling, and / or carried on signalling, in a RAN, for example if the target device is a UE, or the

[0837] tool for a UE. It should be noted that such provided information may be transferred to 1720 the information system via one or more additionally communication interfaces and / or

[0838] paths and / or connections. The target indication may be a higher-layer indication and / or

[0839] the information provided by the information system may be higher-layer information, e.g. application layer or user-layer, in particular above radio layers like transport layer and physical layer. The target indication may be mapped on physical layer radio signalling, 1725 e.g. related to or on the user-plane, and / or the information may be mapped on physical

[0840] layer radio communication signalling, e.g. related to or on the user-plane (in particular,

[0841] in reverse communication directions). The described approaches allow a target indication

[0842] to be provided, facilitating information to be provided in a specific format particularly suitable and / or adapted to efficiently use an air interface. A user input may for example 1730 represent a selection from a plurality of possible transmission modes or formats, and / or

[0843] paths, e.g. in terms of data rate and / or packaging and / or size of information to be provided by the information system.

[0844] In general, a numerology and / or sub-carrier spacing may indicate the bandwidth (in frequency domain) of a sub-carrier of a carrier, and / or the number of sub-carriers in a 1735

[0845] P113137WO01 48 / 79carrier and / or the numbering of the sub-carriers in a carrier, and / or the symbol time length. Different numerologies may in particular be different in the bandwidth of a subcarrier. In some variants, all the sub-carriers in a carrier have the same bandwidth associated to them. The numerology and / or sub-carrier spacing may be different between carriers in particular regarding the sub-carrier bandwidth. A symbol time length, and / or 1740 a time length of a timing structure pertaining to a carrier may be dependent on the carrier frequency, and / or the sub-carrier spacing and / or the numerology. In particular, different numerologies may have different symbol time lengths, even on the same carrier.

[0846] Signalling may generally comprise one or more (e.g., modulation) symbols and / or signals and / or messages. A signal may comprise or represent one or more bits. An indication may 1745 represent signalling, and / or be implemented as a signal, or as a plurality of signals. One or

[0847] more signals may be included in and / or represented by a message, signalling, in particular control signalling, may comprise a plurality of signals and / or messages, which may be transmitted on different carriers and / or be associated to different signalling processes,

[0848] e.g. representing and / or pertaining to one or more such processes and / or corresponding 1750 information. An indication may comprise signalling, 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 signalling processes, e.g. representing

[0849] and / or pertaining to one or more such processes, signalling associated to a channel

[0850] may be transmitted such that represents signalling and / or information for that channel, 1755 and / or that the signalling is interpreted by the transmitter and / or receiver to belong to

[0851] that channel. Such signalling may generally comply with transmission parameters and / or format / s for the channel.

[0852] An antenna arrangement may comprise one or more antenna elements (radiating elements), which may be combined in antenna arrays. An antenna array or sub-array may 1760 comprise one antenna element, or a plurality of antenna elements, which may be arranged

[0853] e.g. two dimensionally (for example, a panel) or three dimensionally. It may be considered

[0854] that each antenna array or sub-array or element is separately controllable, respectively

[0855] that different antenna arrays are controllable separately from each other. A single antenna element / radiator may be considered the smallest example of a sub-array. Examples 1765 of antenna arrays comprise one or more multi-antenna panels or one or more individually controllable antenna elements. An antenna arrangement may comprise a plurality

[0856] of antenna arrays. It may be considered that an antenna arrangement is associated to

[0857] a (specific and / or single) radio node, e.g. a configuring or informing or scheduling radio

[0858] node, e.g. to be controlled or controllable by the radio node. An antenna arrangement 1770 associated to a UE or terminal may be smaller (e.g., in size and / or number of antenna elements or arrays) than the antenna arrangement associated to a network node. An-

[0859] P113137WO01 49 / 79tenna elements of an antenna arrangement may be configurable for different arrays, e.g. to change the beamforming characteristics. In particular, antenna arrays may be formed

[0860] by combining one or more independently or separately controllable antenna elements or 1775 sub-arrays. The beams may be provided by analog beamforming, or in some variants by

[0861] digital beamforming, or by hybrid beamforming combing analog and digital beamforming.

[0862] The informing radio nodes may be configured with the manner of beam transmission, e.g.

[0863] by transmitting a corresponding indicator or indication, for example as beam identify indication. However, there may be considered cases in which the informing radio node / s are 1780 not configured with such information, and / or operate transparently, not knowing the way

[0864] of beamforming used. An antenna arrangement may be considered separately controllable in regard to the phase and / or amplitude / power and / or gain of a signal feed to it for transmission, and / or separately controllable antenna arrangements may comprise an independent or separate transmit and / or receive unit and / or ADC (analog- Digit al- Converter, 1785 alternatively an ADC chain) or DCA (Digital-to-analog Converter, alternatively a DCA

[0865] chain) to convert digital control information into an analog antenna feed for the whole antenna arrangement (the ADC / DCA may be considered part of, and / or connected or connectable to, antenna circuitry) or vice versa. A scenario in which an ADC or DCA is controlled directly for beamforming may be considered an analog beamforming scenario; 1790 such controlling may be performed after encoding / decoding and7or after modulation symbols have been mapped to resource elements. This may be on the level of antenna arrangements using the same ADC / DCA, e.g. one antenna element or a group of antenna elements associated to the same ADC / DCA. Digital beamforming may correspond to a scenario in which processing for beamforming is provided before feeding signalling to the 1795 ADC / DCA, e.g. by using one or more precoder / s and / or by precoding information, for example before and / or when mapping modulation symbols to resource elements. Such a precoder for beamforming may provide weights, e.g. for amplitude and / or phase, and / or

[0866] may be based on a (precoder) codebook, e.g. selected from a codebook. A precoder may pertain to one beam or more beams, e.g. defining the beam or beams. The codebook 1800 may be configured or configurable, and / or be predefined. DFT beamforming may be considered a form of digital beamforming, wherein a DFT procedure is used to form one

[0867] or more beams. Hybrid forms of beamforming may be considered.

[0868] A beam may be defined by a spatial and / or angular and / or spatial angular distribution

[0869] of radiation and / or a spatial angle (also referred to as solid angle) or spatial (solid) angle 1805 distribution into which radiation is transmitted (for transmission beamforming) or from

[0870] which it is received (for reception beamforming). Reception beamforming may comprise

[0871] only accepting signals coming in from a reception beam (e.g., using analog beamforming

[0872] to not receive outside reception beam / s), and / or sorting out signals that do not come

[0873] P113137WO01 50 / 79in in a reception beam, e.g. in digital postprocessing, e.g. digital beamforming. A 1810 beam may have a solid angle equal to or smaller than 4*pi sr (4*pi correspond to a

[0874] beam covering all directions), in particular smaller than 2* pi, or pi, or pi / 2, or pi / 4 or

[0875] pi / 8 or pi / 16. In particular for high frequencies, smaller beams may be used. Different

[0876] beams may have different directions and / or sizes (e.g., solid angle and / or reach). A beam

[0877] may have a main direction, which may be defined by a main lobe (e.g., center of the 1815 main lobe, e.g. pertaining to signal strength and / or solid angle, which may be averaged

[0878] and / or weighted to determine the direction), and may have one or more sidelobes. A lobe

[0879] may generally be defined to have a continuous or contiguous distribution of energy and / or

[0880] power transmitted and / or received, e.g. bounded by one or more contiguous or contiguous regions of zero energy (or practically zero energy). A main lobe may comprise the lobe 1820 with the largest signal strength and / or energy and / or power content. However, sidelobes usually appear due to limitations of beamforming, some of which may carry signals with significant strength, and may cause multi-path effects. A sidelobe may generally have a different direction than a main lobe and / or other side lobes, however, due to reflections

[0881] a sidelobe still may contribute to transmitted and / or received energy or power. A beam 1825 may be swept and / or switched over time, e.g., such that its (main) direction is changed,

[0882] but its shape (angular / solid angle distribution) around the main direction is not changed,

[0883] e.g. from the transmitter’s views for a transmission beam, or the receiver’s view for a reception beam, respectively. Sweeping may correspond to continuous or near continuous

[0884] change of main direction (e.g., such that after each change, the main lobe from before the 1830 change covers at least partly the main lobe after the change, e.g. at least to 50 or 75 or

[0885] 90 percent). Switching may correspond to switching direction non-continuously, e.g. such

[0886] that after each change, the main lobe from before the change does not cover the main

[0887] lobe after the change, e.g. at most to 50 or 25 or 10 percent.

[0888] Signal strength may be a representation of signal power and / or signal energy, e.g. as 1835 seen from a transmitting node or a receiving node. A beam with larger strength at transmission (e.g., according to the beamforming used) than another beam does may

[0889] not necessarily have larger strength at the receiver, and vice versa, for example due to interference and / or obstruction and / or dispersion and / or absorption and / or reflection

[0890] and / or attrition or other effects influencing a beam or the signalling it carries. Signal 1840 quality may in general be a representation of how well a signal may be received over

[0891] noise and / or interference. A beam with better signal quality than another beam does

[0892] not necessarily have a larger beam strength than the other beam. Signal quality may be represented for example by SIR, SNR, SINR, BER, BLER, Energy per resource element

[0893] over noise / interference or another corresponding quality measure. Signal quality and / or 1845 signal strength may pertain to, and / or may be measured with respect to, a beam, and / or

[0894] P113137WO01 51 / 79specific signalling carried by the beam, e.g. reference signalling and / or a specific channel, e.g. a data channel or control channel. Signal strength may be represented by received

[0895] signal strength, and / or relative signal strength, e.g. in comparison to a reference signal (strength). 1850

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

[0897] Downlink signalling may in particular be OFDMA signalling. However, signalling like communication signalling is not limited thereto (Filter-Bank based signalling and / or

[0898] Single-Carrier based signalling, e.g. SC-FDE signalling, may be considered alternatives). 1855

[0899] A radio node may generally be considered a device or node adapted for wireless and / or

[0900] radio (and / or millimeter wave) frequency communication, and / or for communication utilising an air interface, e.g. according to a communication standard.

[0901] A radio node may be a network node, or a user equipment or terminal. A network node

[0902] may be any radio node of a wireless communication network, e.g. a base station and / or 1860 gNodeB (gNB) and / or eNodeB (eNB) and / or relay node and / or micro / nano / pico / femto

[0903] node and / or transmission point (TP) and / or access point (AP) and / or other node, in particular for a RAN or other wireless communication network as described herein.

[0904] The terms user equipment (UE) and terminal may be considered to be interchangeable

[0905] in the context of this disclosure. A wireless device, user equipment or terminal may rep- 1865 resent 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- 1870 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. A wireless device generally may comprise, and / or be implemented as, processing circuitry and / or radio circuitry, which may comprise one or more chips or sets of chips.

[0906] The circuitry and / or circuitries may be packaged, e.g. in a chip housing, and / or may have 1875 one or more physical interfaces to interact with other circuitry and / or for power supply.

[0907] Such a wireless device may be intended for use in a user equipment or terminal.

[0908] A radio node may generally comprise processing circuitry and / or radio circuitry. A radio

[0909] node, in particular a network node, may in some cases comprise cable circuitry and / or communication circuitry, with which it may be connected or connectable to another radio 1880 node and / or a core network.

[0910] P113137WO01 52 / 79Circuitry 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) 1885 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

[0911] 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 mem- 1890 ory, and / or EPROM or EEPROM (Erasable Programmable ROM or Electrically Erasable Programmable ROM).

[0912] Radio circuitry may comprise one or more transmitters and / or receivers and / or transceivers

[0913] (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 1895 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

[0914] one or more antennas and / or antenna arrays. An antenna array may comprise one or

[0915] more antennas, which may be arranged in a dimensional array, e.g. 2D or 3D array, and / or antenna panels. A remote radio head (RRH) may be considered as an example 1900 of an antenna array. However, in some variants, an RRH may be also be implemented

[0916] as a network node, depending on the kind of circuitry and / or functionality implemented therein.

[0917] Communication circuitry may comprise radio circuitry and / or cable circuitry. Communication circuitry generally may comprise one or more interfaces, which may be air inter- 1905 face / s and / or cable interface / s and / or optical interface / s, e.g. laser-based. Interface / s

[0918] may be in particular packet-based. Cable circuitry and / or a cable interfaces may comprise, and / or be connected or connectable to, one or more cables (e.g., optical fiber-based

[0919] and / or wire-based), which may be directly or indirectly (e.g., via one or more intermediate systems and / or interfaces) be connected or connectable to a target, e.g. controlled by 1910 communication circuitry and / or processing circuitry.

[0920] 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

[0921] 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 1915 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

[0922] P113137WO01 53 / 79execution may be performed on, and / or controlled by the associated circuitry).

[0923] A wireless communication network may be or comprise a radio access network and / or

[0924] a backhaul network (e.g. a relay or backhaul network or an IAB network), and / or a 1920 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,

[0925] e.g. according to NR or LTE, in particular LTE Evolution.

[0926] 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 net- 1925 work, 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

[0927] (New Radio), respectively successors thereof. A RAN may comprise one or more network nodes, and / or one or more terminals, and / or one or more radio nodes. A network

[0928] node may in particular be a radio node adapted for radio and / or wireless and / or cellular 1930 communication with one or more terminals. A terminal may be any device adapted for

[0929] 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

[0930] may be mobile, or in some cases stationary. A RAN or a wireless communication network 1935 may comprise at least one network node and a UE, or at least two radio nodes. There

[0931] may be generally considered a wireless communication network or system, e.g. a RAN or

[0932] RAN system, comprising at least one radio node, and / or at least one network node and

[0933] at least one terminal.

[0934] Transmitting in downlink may pertain to transmission from the network or network node 1940 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 1945 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

[0935] relay communication and / or network communication is implemented as a form of sidelink

[0936] or uplink communication or similar thereto. 1950

[0937] Control information or a control information message or corresponding signalling (control signalling) may be transmitted on a control channel, e.g. a physical control channel,

[0938] which may be a downlink channel or (or a sidelink channel in some cases, e.g. one UE

[0939] P113137WO01 54 / 79scheduling another UE). For example, control information / allocation information may be signaled by a network node on PDCCH (Physical Downlink Control Channel) and / or 1955 a PDSCH (Physical Downlink Shared Channel) and / or a HARQ-specihc channel. Acknowledgement signalling, e.g. as a form of control information or signalling like uplink control information / signalling, may be transmitted by a terminal on a PUCCH (Physical Uplink Control Channel) and / or PUSCH (Physical Uplink Shared Channel) and / or a

[0940] HARQ-specihc channel. Multiple channels may apply for multi-component / multi-carrier 1960 indication or signalling.

[0941] Transmitting acknowledgement signalling may in general be based on and / or in response

[0942] to subject transmission, and / or to control signalling scheduling subject transmission.

[0943] Such control signalling and / or subject signalling may be transmitted by a signalling radio node (which may be a network node, and / or a node associated to it, e.g. in a dual 1965 connectivity scenario. Subject transmission and / or subject signalling may be transmission or signalling to which ACK / NACK or acknowledgement information pertains, e.g. indicating correct or incorrect reception and / or decoding of the subject transmission or signalling. Subject signalling or transmission may in particular comprise and / or be represented by data signalling, e.g. on a PDSCH or PSSCH, or some forms of control signalling, 1970 e.g. on a PDCCH or PSSCH, for example for specific formats.

[0944] A signalling characteristic may be based on a type or format of a scheduling grant and / or scheduling assignment, and / or type of allocation, and / or timing of acknowledgement signalling and / or the scheduling grant and / or scheduling assignment, and / or resources associated to acknowledgement signalling and / or the scheduling grant and / or schedul- 1975 ing assignment. For example, if a specific format for a scheduling grant (scheduling

[0945] or allocating the allocated resources) or scheduling assignment (scheduling the subject transmission for acknowledgement signalling) is used or detected, the first or second communication resource may be used. Type of allocation may pertain to dynamic allocation

[0946] (e.g., using DCI / PDCCH) or semi-static allocation (e.g., for a configured grant). Timing 1980 of acknowledgement signalling may pertain to a slot and / or symbol / s the signalling is to

[0947] be transmitted. Resources used for acknowledgement signalling may pertain to the allocated resources. Timing and / or resources associated to a scheduling grant or assignment

[0948] may represent a search space or CORESET (a set of resources configured for reception of PDCCH transmissions) in which the grant or assignment is received. Thus, which trans- 1985 mission resource to be used may be based on implicit conditions, requiring low signalling overhead.

[0949] Scheduling may comprise indicating, e.g. with control signalling like DCI or SCI signalling

[0950] and / or signalling on a control channel like PDCCH or PSCCH, one or more scheduling

[0951] P113137WO01 55 / 79opportunities of a configuration intended to carry data signalling or subject signalling. 1990 The configuration may be represented or representable by, and / or correspond to, a table.

[0952] A scheduling assignment may for example point to an opportunity of the reception allocation configuration, e.g. indexing a table of scheduling opportunities. In some cases, a reception allocation configuration may comprise 15 or 16 scheduling opportunities. The configuration may in particular represent allocation in time. It may be considered that the 1995 reception allocation configuration pertains to data signalling, in particular on a physical

[0953] data channel like PDSCH or PSSCH. In general, the reception allocation configuration

[0954] may pertain to downlink signalling, or in some scenarios to sidelink signalling. Control signalling scheduling subject transmission like data signalling may point and / or index

[0955] and / or refer to and / or indicate a scheduling opportunity of the reception allocation con- 2000 figuration. It may be considered that the reception allocation configuration is configured

[0956] or configurable with higher-layer signalling, e.g. RRC or MAC layer signalling. The reception allocation configuration may be applied and / or applicable and / or valid for a plurality

[0957] of transmission timing intervals, e.g. such that for each interval, one or more opportunities may be indicated or allocated for data signalling. These approaches allow efficient 2005 and flexible scheduling, which may be semi-static, but may updated or reconfigured on

[0958] useful timescales in response to changes of operation conditions.

[0959] Control information, e.g., in a control information message, in this context may in particular be implemented as and / or represented by a scheduling assignment, which may indicate subject transmission for feedback (transmission of acknowledgement signalling), 2010 and / or reporting timing and / or frequency resources and / or code resources. Reporting

[0960] timing may indicate a timing for scheduled acknowledgement signalling, e.g. slot and / or symbol and / or resource set. Control information may be carried by control signalling.

[0961] Subject transmissions may comprise one or more individual transmissions. Scheduling assignments may comprise one or more scheduling assignments. It should generally be noted 2015 that in a distributed system, subject transmissions, configuration and / or scheduling may

[0962] be provided by different nodes or devices or transmission points. Different subject transmissions may be on the same carrier or different carriers (e.g., in a carrier aggregation), and / or same or different bandwidth parts, and / or on the same or different layers or beams,

[0963] e.g. in a MIMO scenario, and / or to same or different ports. Generally, subject transmis- 2020 sions may pertain to different HARQ or ARQ processes (or different sub-processes, e.g. in

[0964] MIMO with different beams / layers associated to the same process identifier, but different

[0965] sub-process-identifiers like swap bits). A scheduling assignment and / or a HARQ codebook may indicate a target HARQ structure. A target HARQ structure may for example indicate an intended HARQ response to a subject transmission, e.g. the number of bits 2025 and / or whether to provide code block group level response or not. However, it should be

[0966] P113137WO01 56 / 79noted that the actual structure used may differ from the target structure, e.g. due to the total size of target structures for a sub-pattern being larger than the predetermined size.

[0967] Transmitting acknowledgement signalling, also referred to as transmitting acknowledgement information or feedback information or simply as ARQ or HARQ feedback or feed- 2030 back or reporting feedback, may comprise, and / or be based on determining correct or incorrect reception of subject transmission / s, e.g. based on error coding and / or based on scheduling assignment / s scheduling the subject transmissions. Transmitting acknowledgement information may be based on, and / or comprise, a structure for acknowledgement information to transmit, e.g. the structure of one or more sub-patterns, e.g. based on 2035 which subject transmission is scheduled for an associated subdivision. Transmitting acknowledgement information may comprise transmitting corresponding signalling, e.g. at

[0968] one instance and / or in one message and / or one channel, in particular a physical channel,

[0969] which may be a control channel. In some cases, the channel may be a shared channel

[0970] or data channel, e.g. utilising rate-matching of the acknowledgment information. The 2040 acknowledgement information may generally pertain to a plurality of subject transmissions, which may be on different channels and / or carriers, and / or may comprise data signalling and / or control signalling. The acknowledgment information may be based on

[0971] a codebook, which may be based on one or more size indications and / or assignment indications (representing HARQ structures), which may be received with a plurality of 2045 control signallings and / or control messages, e.g. in the same or different transmission

[0972] timing structures, and / or in the same or different (target) sets of resources. Transmitting acknowledgement information may comprise determining the codebook, e.g. based on control information in one or more control information messages and / or a configuration.

[0973] A codebook may pertain to transmitting acknowledgement information at a single and / or 2050 specific instant, e.g. a single PUCCH or PUSCH transmission, and / or in one message

[0974] or with jointly encoded and / or modulated acknowledgement information. Generally, acknowledgment information may be transmitted together with other control information,

[0975] e.g. a scheduling request and / or measurement information.

[0976] Acknowledgement signalling may in some cases comprise, next to acknowledgement in- 2055 formation, other information, e.g. control information, in particular, uplink or sidelink control information, like a scheduling request and / or measurement information, or similar, and / or error detection and / or correction information, respectively associated bits.

[0977] The payload size of acknowledgement signalling may represent the number of bits of acknowledgement information, and / or in some cases the total number of bits carried by 2060 the acknowledgement signalling, and / or the number of resource elements needed. Acknowledgement signalling and / or information may pertain to ARQ and / or HARQ processes; an ARQ process may provide ACK / NACK (and perhaps additional feedback)

[0978] P113137WO01 57 / 79feedback, and decoding may be performed on each (re-)transmission separately, without soft-buffering / soft-combining intermediate data, whereas HARQ may comprise soft- 2065 buffering / soft-combining of intermediate data of decoding for one or more (re-)transmissions.

[0979] Subject transmission may be data signalling or control signalling. The transmission may

[0980] be on a shared or dedicated channel. Data signalling may be on a data channel, for example on a PDSCH or PSSCH, or on a dedicated data channel, e.g. for low latency and / or

[0981] high reliability, e.g. a URLLC channel. Control signalling may be on a control channel, 2070 for example on a common control channel or a PDCCH or PSCCH, and / or comprise one

[0982] or more DCI messages or SCI messages. In some cases, the subject transmission may comprise, or represent, reference signalling. For example, it may comprise DM-RS and / or pilot signalling and / or discovery signalling and / or sounding signalling and / or phase tracking signalling and / or cell-specific reference signalling and / or user-specific signalling, in par- 2075 ticular CSI-RS. A subject transmission may pertain to one scheduling assignment and / or

[0983] one acknowledgement signalling process (e.g., according to identifier or subidentifier), and / or one subdivision. In some cases, a subject transmission may cross the borders of subdivisions in time, e.g. due to being scheduled to start in one subdivision and extending

[0984] into another, or even crossing over more than one subdivision. In this case, it may be 2080 considered that the subject transmission is associated to the subdivision it ends in.

[0985] It may be considered that transmitting acknowledgement information, in particular of acknowledgement information, is based on determining whether the subject transmission / s

[0986] has or have been received correctly, e.g. based on error coding and / or reception quality.

[0987] Reception quality may for example be based on a determined signal quality. Acknowl- 2085 edgement information may generally be transmitted to a signalling radio node and / or

[0988] node arrangement and / or to a network and / or network node.

[0989] Acknowledgement information, or bit / s of a sub-pattern structure of such information

[0990] (e.g., an acknowledgement information structure, may represent and / or comprise one or

[0991] more bits, in particular a pattern of bits. Multiple bits pertaining to a data structure 2090 or substructure or message like a control message may be considered a sub-pattern. The structure or arrangement of acknowledgement information may indicate the order, and / or meaning, and / or mapping, and / or pattern of bits (or sub-patterns of bits) of the information. The structure or mapping may in particular indicate one or more data block structures, e.g. code blocks and / or code block groups and / or transport blocks and / or 2095 messages, e.g. command messages, the acknowledgement information pertains to, and / or

[0992] which bits or sub-pattern of bits are associated to which data block structure. In some

[0993] cases, the mapping may pertain to one or more acknowledgement signalling processes, e.g. processes with different identifiers, and / or one or more different data streams. The config-

[0994] P113137WO01 58 / 79uration or structure or codebook may indicate to which process / es and / or data stream / s 2100 the information pertains. Generally, the acknowledgement information may comprise

[0995] one or more sub-patterns, each of which may pertain to a data block structure, e.g. a

[0996] code block or code block group or transport block. A sub-pattern may be arranged to indicate acknowledgement or non-acknowledgement, or another retransmission state like

[0997] non-scheduling or non-reception, of the associated data block structure. It may be consid- 2105 ered that a sub-pattern comprises one bit, or in some cases more than one bit. It should

[0998] be noted that acknowledgement information may be subjected to significant processing

[0999] before being transmitted with acknowledgement signalling. Different configurations may indicate different sizes and / or mapping and / or structures and / or pattern.

[1000] An acknowledgment signalling process (providing acknowledgment information) may be 2110 a HARQ process, and / or be identified by a process identifier, e.g. a HARQ process identifier or sub-identifier. Acknowledgement signalling and / or associated acknowledgement information may be referred to as feedback or acknowledgement feedback. It should be

[1001] noted that data blocks or structures to which sub-patterns may pertain may be intended

[1002] to carry data (e.g., information and / or systemic and / or coding bits). However, depending 2115 on transmission conditions, such data may be received or not received (or not received correctly), which may be indicated correspondingly in the feedback. In some cases, a

[1003] sub-pattern of acknowledgement signalling may comprise padding bits, e.g. if the acknowledgement information for a data block requires fewer bits than indicated as size of

[1004] the sub-pattern. Such may for example happen if the size is indicated by a unit size larger 2120 than required for the feedback.

[1005] Acknowledgment information may generally indicate at least ACK or NACK, e.g. pertaining to an acknowledgment signalling process, or an element of a data block structure

[1006] like a data block, subblock group or subblock, or a message, in particular a control message. Generally, to an acknowledgment signalling process there may be associated one 2125 specific sub-pattern and / or a data block structure, for which acknowledgment information

[1007] may be provided. Acknowledgement information may comprise a plurality of pieces of information, represented in a plurality of ARQ and / or HARQ structures.

[1008] An acknowledgment signalling process may determine correct or incorrect reception, and / or corresponding acknowledgement information, of a data block like a transport 2130 block, and / or substructures thereof, based on coding bits associated to the data block, and / or based on coding bits associated to one or more data block and / or subblocks and / or subblock group / s. Acknowledgement information (determined by an acknowledgement signalling process) may pertain to the data block as a whole, and / or to one

[1009] or more subblocks or subblock groups. A code block may be considered an example of 2135

[1010] P113137WO01 59 / 79a subblock, whereas a code block group may be considered an example of a subblock group. Accordingly, the associated sub-pattern may comprise one or more bits indicating reception status or feedback of the data block, and / or one or more bits indicating reception status or feedback of one or more subblocks or subblock groups. Each sub-pattern

[1011] or bit of the sub-pattern may be associated and / or mapped to a specific data block or 2140 subblock or subblock group. In some variants, correct reception for a data block may be indicated if all subblocks or subblock groups are correctly identified. In such a case, the

[1012] sub-pattern may represent acknowledgement information for the data block as a whole, reducing overhead in comparison to provide acknowledgement information for the subblocks or subblock groups. The smallest structure (e.g. subblock / subblock group / data 2145 block) the sub-pattern provides acknowledgement information for and / or is associated to

[1013] may be considered its (highest) resolution. In some variants, a sub-pattern may provide acknowledgment information regarding several elements of a data block structure and / or

[1014] at different resolution, e.g. to allow more specific error detection. For example, even if a

[1015] sub-pattern indicates acknowledgment signalling pertaining to a data block as a whole, 2150 in some variants higher resolution (e.g., subblock or subblock group resolution) may be provided by the sub-pattern. A sub-pattern may generally comprise one or more bits indicating ACK / NACK for a data block, and / or one or more bits for indicating ACK / NACK

[1016] for a subblock or subblock group, or for more than one subblock or subblock group.

[1017] A subblock and / or subblock group may comprise information bits (representing the data 2155 to be transmitted, e.g. user data and / or downlink / sidelink data or uplink data). It may be considered that a data block and / or subblock and / or subblock group also comprises error

[1018] one or more error detection bits, which may pertain to, and / or be determined based on,

[1019] the information bits (for a subblock group, the error detection bit / s may be determined

[1020] based on the information bits and / or error detection bits and / or error correction bits of the 2160 subblock / s of the subblock group). A data block or substructure like subblock or subblock

[1021] group may comprise error correction bits, which may in particular be determined based

[1022] on the information bits and error detection bits of the block or substructure, e.g. utilising

[1023] an error correction coding scheme, in particular for forward error correction (FEC), e.g.

[1024] LDPC or polar coding and / or turbo coding. Generally, the error correction coding of a 2165 data block structure (and / or associated bits) may cover and / or pertain to information bits

[1025] and error detection bits of the structure. A subblock group may represent a combination of

[1026] one or more code blocks, respectively the corresponding bits. A data block may represent

[1027] a code block or code block group, or a combination of more than one code block groups.

[1028] A transport block may be split up in code blocks and / or code block groups, for example 2170 based on the bit size of the information bits of a higher layer data structure provided

[1029] for error coding and / or size requirements or preferences for error coding, in particular

[1030] P113137WO01 60 / 79error correction coding. Such a higher layer data structure is sometimes also referred to as transport block, which in this context represents information bits without the error

[1031] coding bits described herein, although higher layer error handling information may be 2175 included, e.g. for an internet protocol like TCP. However, such error handling information represents information bits in the context of this disclosure, as the acknowledgement signalling procedures described treat it accordingly.

[1032] In some variants, a subblock like a code block may comprise error correction bits, which

[1033] may be determined based on the information bit / s and / or error detection bit / s of the 2180 subblock. An error correction coding scheme may be used for determining the error correction bits, e.g. based on LDPC or polar coding or Reed-Mueller coding. In some cases,

[1034] a subblock or code block may be considered to be defined as a block or pattern of bits comprising information bits, error detection bit / s determined based on the information

[1035] bits, and error correction bit / s determined based on the information bits and / or error 2185 detection bit / s. It may be considered that in a subblock, e.g. code block, the information

[1036] bits (and possibly the error correction bit / s) are protected and / or covered by the error correction scheme or corresponding error correction bit / s. A code block group may comprise one or more code blocks. In some variants, no additional error detection bits and / or

[1037] error correction bits are applied, however, it may be considered to apply either or both. A 2190 transport block may comprise one or more code block groups. It may be considered that

[1038] no additional error detection bits and / or error correction bits are applied to a transport

[1039] block, however, it may be considered to apply either or both. In some specific variants,

[1040] the code block group / s comprise no additional layers of error detection or correction coding, and the transport block may comprise only additional error detection coding bits, 2195 but no additional error correction coding. This may particularly be true if the transport

[1041] block size is larger than the code block size and / or the maximum size for error correction coding. A sub-pattern of acknowledgement signalling (in particular indicating ACK or NACK) may pertain to a code block, e.g. indicating whether the code block has been correctly received. It may be considered that a sub-pattern pertains to a subgroup like 2200 a code block group or a data block like a transport block. In such cases, it may indicate

[1042] ACK, if all subblocks or code blocks of the group or data / transport block are received correctly (e.g. based on a logical AND operation), and NACK or another state of noncorrect reception if at least one subblock or code block has not been correctly received. It

[1043] should be noted that a code block may be considered to be correctly received not only if 2205 it actually has been correctly received, but also if it can be correctly reconstructed based

[1044] on soft-combining and / or the error correction coding.

[1045] A sub-pattern / HARQ structure may pertain to one acknowledgement signalling process and / or one carrier like a component carrier and / or data block structure or data block. It

[1046] P113137WO01 61 / 79may in particular be considered that one (e.g. specific and / or single) sub-pattern pertains, 2210 e.g. is mapped by the codebook, to one (e.g., specific and / or single) acknowledgement signalling process, e.g. a specific and / or single HARQ process. It may be considered

[1047] that in the bit pattern, sub-patterns are mapped to acknowledgement signalling processes and / or data blocks or data block structures on a one-to-one basis. In some variants, there

[1048] may be multiple sub-patterns (and / or associated acknowledgment signalling processes) 2215 associated to the same component carrier, e.g. if multiple data streams transmitted

[1049] on the carrier are subject to acknowledgement signalling processes. A sub-pattern may comprise one or more bits, the number of which may be considered to represent its size

[1050] or bit size. Different bit n-tupels (n being 1 or larger) of a sub-pattern may be associated

[1051] to different elements of a data block structure (e.g., data block or subblock or subblock 2220 group), and / or represent different resolutions. There may be considered variants in which

[1052] only one resolution is represented by a bit pattern, e.g. a data block. A bit n-tupel

[1053] may represent acknowledgement information (also referred to a feedback), in particular

[1054] ACK or NACK, and optionally, (if n^,l), may represent DTX / DRX or other reception

[1055] states. ACK / NACK may be represented by one bit, or by more than one bit, e.g. to 2225 improve disambiguity of bit sequences representing ACK or NACK, and / or to improve transmission reliability.

[1056] The acknowledgement information or feedback information may pertain to a plurality

[1057] of different transmissions, which may be associated to and / or represented by data block structures, respectively the associated data blocks or data signalling. The data block 2230 structures, and / or the corresponding blocks and / or signalling, may be scheduled for simultaneous transmission, e.g. for the same transmission timing structure, in particular

[1058] within the same slot or subframe, and / or on the same symbol / s. However, alternatives

[1059] with scheduling for non-simultaneous transmission may be considered. For example, the acknowledgment information may pertain to data blocks scheduled for different trans- 2235 mission timing structures, e.g. different slots (or mini-slots, or slots and mini-slots) or similar, which may correspondingly be received (or not or wrongly received). Scheduling signalling may generally comprise indicating resources, e.g. time and / or frequency resources, for example for receiving or transmitting the scheduled signalling.

[1060] Signalling may generally be considered to represent an electromagnetic wave structure 2240 (e.g., over a time interval and frequency interval), which is intended to convey information to at least one specific or generic (e.g., anyone who might pick up the signalling) target. A process of signalling may comprise transmitting the signalling. Transmitting signalling, in particular control signalling or communication signalling, e.g. comprising

[1061] or representing acknowledgement signalling and / or resource requesting information, may 2245 comprise encoding and / or modulating. Encoding and / or modulating may comprise error

[1062] P113137WO01 62 / 79detection coding and / or forward error correction encoding and / or scrambling. Receiving control signalling may comprise corresponding decoding and / or demodulation. Error detection coding may comprise, and / or be based on, parity or checksum approaches, e.g.

[1063] CRC (Cyclic Redundancy Check). Forward error correction coding may comprise and / or 2250 be based on for example turbo coding and / or Reed-Muller coding, and / or polar coding

[1064] and / or LDPC coding (Low Density Parity Check). The type of coding used may be based

[1065] on the channel (e.g., physical channel) the coded signal is associated to. A code rate may represent the ratio of the number of information bits before encoding to the number of encoded bits after encoding, considering that encoding adds coding bits for error detec- 2255 tion coding and forward error correction. Coded bits may refer to information bits (also

[1066] called systematic bits) plus coding bits.

[1067] Communication signalling may comprise, and / or represent, and / or be implemented as,

[1068] data signalling, and / or user plane signalling. Communication signalling may be associated

[1069] to a data channel, e.g. a physical downlink channel or physical uplink channel or physical 2260 sidelink channel, in particular a PDSCH (Physical Downlink Shared Channel) or PSSCH (Physical Sidelink Shared Channel). Generally, a data channel may be a shared channel

[1070] or a dedicated channel. Data signalling may be signalling associated to and / or on a data channel.

[1071] An indication generally may explicitly and / or implicitly indicate the information it rep- 2265 resents and / or indicates. Implicit indication may for example be based on position

[1072] and / or resource used for transmission. Explicit indication may for example be based

[1073] 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 signalling as described herein, based on the utilised resource sequence, 2270 implicitly indicates the control signalling type.

[1074] 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

[1075] time and a sub-carrier in frequency. A signal may be allocatable and / or allocated to a 2275 resource element. A sub-carrier 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

[1076] 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 sub-carrier spacing (and / or 2280 numerology) may be different between different symbols and / or sub-carriers, different resource elements may have different extension (length / width) in time and / or frequency

[1077] P113137WO01 63 / 79domain, in particular resource elements pertaining to different carriers.

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

[1079] A border symbol may generally represent a starting symbol or an ending symbol for transmitting and / or receiving. A starting symbol may in particular be a starting symbol

[1080] of uplink or sidelink signalling, for example control signalling or data signalling. Such signalling may be on a data channel or control channel, e.g. a physical channel, in 2290 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.

[1081] If the starting symbol is associated to control signalling (e.g., on a control channel), the control signalling may be in response to received signalling (in sidelink or downlink), e.g. representing acknowledgement signalling associated thereto, which may be HARQ or ARQ 2295 signalling. An ending symbol may represent an ending symbol (in time) of downlink or sidelink transmission or signalling, which may be intended or scheduled for the radio node

[1082] or user equipment. Such downlink signalling may in particular be data signalling, e.g.

[1083] on a physical downlink channel like a shared channel, e.g. a PDSCH (Physical Downlink

[1084] Shared Channel). A starting symbol may be determined based on, and / or in relation to, 2300 such an ending symbol.

[1085] Configuring a radio node, in particular a terminal or user equipment, may refer to the

[1086] radio node being adapted or caused or set and / or instructed 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 2305 case it may comprise transmitting configuration data to the radio node to be configured.

[1087] Such configuration data may represent the configuration to be configured and / or comprise

[1088] one or more instruction pertaining to a configuration, e.g. a configuration for transmitting

[1089] and / or receiving on allocated resources, in particular frequency resources. A radio node

[1090] may configure itself, e.g., based on configuration data received from a network or network 2310 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.

[1091] Configuration data may comprise and / or be represented by configuration information, and / or one or more corresponding indications and / or message / s

[1092] Generally, configuring may include determining configuration data representing the con- 2315 figuration and providing, e.g. transmitting, it to one or more other nodes (parallel and / or sequentially), which may transmit it further to the radio node (or another node, which

[1093] may be repeated until it reaches the wireless device). Alternatively, or additionally, con-

[1094] P113137WO01 64 / 79figuring 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 2320 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

[1095] 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.,

[1096] an X2 interface in the case of LTE or a corresponding interface for NR. Configuring a 2325 terminal may comprise scheduling downlink and / or uplink transmissions for the terminal,

[1097] e.g. downlink data and / or downlink control signalling and / or DCI and / or uplink control

[1098] or data or communication signalling, in particular acknowledgement signalling, and / or configuring resources and / or a resource pool therefor.

[1099] A resource structure may be considered to be neighboured in frequency domain by an- 2330 other 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 sub-carrier n, which

[1100] also represents the lower end of a bandwidth assigned to a sub-carrier n+1. A resource structure may be considered to be neighboured in time domain by another resource struc- 2335 ture, 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,

[1101] which also represents the beginning of a symbol time interval assigned to a symbol n+1.

[1102] Generally, a resource structure being neighboured by another resource structure in a 2340 domain may also be referred to as abutting and / or bordering the other resource structure

[1103] in the domain.

[1104] A resource structure may general represent a structure in time and / or frequency domain,

[1105] in particular representing a time interval and a frequency interval. A resource structure

[1106] may comprise and / or be comprised of resource elements, and / or the time interval of a 2345 resource structure may comprise and / or be comprised of symbol time interval / s, and / or

[1107] the frequency interval of a resource structure may comprise and / or be comprised of sub-carrier / s. A resource element may be considered an example for a resource structure, a

[1108] 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 2350 PUCCH, in particular resource structure smaller than a slot or PRB.

[1109] Examples of a resource structure in frequency domain comprise a bandwidth or band, or

[1110] a bandwidth part. A bandwidth part may be a part of a bandwidth available for a radio

[1111] node for communicating, e.g. due to circuitry and / or configuration and / or regulations

[1112] P113137WO01 65 / 79and / or a standard. A bandwidth part may be configured or configurable to a radio 2355 node. In some variants, a bandwidth part may be the part of a bandwidth used for communicating, e.g. transmitting and / or receiving, by a radio node. The bandwidth

[1113] part may be smaller than the bandwidth (which may be a device bandwidth defined by

[1114] the circuitry / configuration of a device, and / or a system bandwidth, e.g. available for a RAN). It may be considered that a bandwidth part comprises one or more resource blocks 2360 or resource block groups, in particular one or more PRBs or PRB groups. A bandwidth

[1115] part may pertain to, and / or comprise, one or more carriers.

[1116] 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 sub-carriers. A carrier may have assigned to it a central frequency 2365 or center frequency interval, e.g. represented by one or more sub-carriers (to each subcarrier there may be generally assigned a frequency bandwidth or interval). Different carriers may be non-overlapping, and / or may be neighbouring in frequency domain.

[1117] 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 2370 millimeter waves, in particular above one of the thresholds 10 GHz or 20 GHz or 50 GHz or

[1118] 52 GHz or 52.6 GHz or 60 GHz or 72 GHz or 100 GHz or 114 GHz. Such communication

[1119] may utilise one or more carriers, e.g. in FDD and / or carrier aggregation. Upper frequency boundaries may correspond to 300 GHz or 200 GHz or 120 GHz or any of the thresholds

[1120] larger than the one representing the lower frequency boundary. 2375

[1121] 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

[1122] carrier may comprise a carrier accessed based on an LBT procedure (which may be called

[1123] LBT carrier), e.g., an unlicensed carrier. It may be considered that the carrier is part of 2380 a carrier aggregate.

[1124] 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 2385 DL communication / transmission (called DL carrier). It may be considered that a cell comprises different numbers of UL carriers and DL carriers. 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.

[1125] P113137WO01 66 / 79A channel may generally be a logical, transport or physical channel. A channel may 2390 comprise and / or be arranged on one or more carriers, in particular a plurality of subcarriers. A channel carrying and / or for carrying control signalling / control information

[1126] may be considered a control channel, in particular if it is a physical layer channel and / or

[1127] if it carries control plane information. Analogously, a channel carrying and / or for carrying

[1128] data signalling / user information may be considered a data channel, in particular if it is 2395 a physical layer channel and / or if it carries user plane information. A channel may be defined for a specific communication direction, or for two complementary communication directions (e.g., UL and DL, or sidelink in two directions), in which case it may be considered to have two component channels, one for each direction. Examples of channels comprise a channel for low latency and / or high reliability transmission, in particular a 2400 channel for Ultra- Reliable Low Latency Communication (URLLC), which may be for control and / or data.

[1129] In general, a symbol may represent and / or be associated to a symbol time length, which

[1130] may be dependent on the carrier and / or sub-carrier spacing and / or numerology of the associated carrier. Accordingly, a symbol may be considered to indicate a time interval 2405 having a symbol time length in relation to frequency domain. A symbol time length

[1131] may be dependent on a carrier frequency and / or bandwidth and / or numerology and / or

[1132] sub-carrier spacing of, or associated to, a symbol. Accordingly, different symbols may

[1133] have different symbol time lengths. In particular, numerologies with different sub-carrier spacings may have different symbol time length. Generally, a symbol time length may be 2410 based on, and / or include, a guard time interval or cyclic extension, e.g. prefix or postfix.

[1134] 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

[1135] (UEs and / or terminals) via the communication channel, e.g. directly and / or without

[1136] being relayed via a network node. A sidelink may be established only and / or directly via 2415 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

[1137] that a network node provides some control functionality, e.g. by configuring resources, in 2420 particular one or more resource pool / s, for sidelink communication, and / or monitoring a sidelink, e.g. for charging purposes.

[1138] 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

[1139] of LTE. A sidelink may be implemented in the context of V2x communication (Vehicular 2425

[1140] P113137WO01 67 / 79communication), 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.

[1141] A sidelink communication channel (or structure) may comprise one or more (e.g., physical

[1142] or logical) channels, e.g. a PSCCH (Physical Sidelink Control CHannel, which may for 2430 example carry control information like an acknowledgement position indication, and / or

[1143] a PSSCH (Physical Sidelink Shared CHannel, which for example may carry data and / or acknowledgement signalling). It may be considered that a sidelink communication channel

[1144] (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 2435 license and / or standard. Participants may share a (physical) channel and / or resources,

[1145] in particular in frequency domain and / or related to a frequency resource like a carrier)

[1146] 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

[1147] to specific participants, so that for example only one participant transmits on a specific 2440 channel or on a specific resource or specific resources, e.g., in frequency domain and / or

[1148] related to one or more carriers or sub-carriers.

[1149] A sidelink may comply with, and / or be implemented according to, a specific standard,

[1150] e.g. an 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 2445 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

[1151] radio circuitry and / or processing circuitry, is adapted for utilising a sidelink, e.g. on one

[1152] 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 2450 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

[1153] be related to a network node and / or communication with such a node.

[1154] Communication or communicating may generally comprise transmitting and / or receiving signalling. Communication on a sidelink (or sidelink signalling) may comprise util- 2455 ising the sidelink for communication (respectively, for signalling). Sidelink transmission

[1155] 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

[1156] the air interface. Sidelink reception and / or receiving on a sidelink may be considered

[1157] to comprise reception utilising the sidelink, e.g. associated resources and / or transmis- 2460 sion formats and / or circuitry and / or the air interface. Sidelink control information (e.g.,

[1158] P113137WO01 68 / 79SCI) may generally be considered to comprise control information transmitted utilising a sidelink.

[1159] 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 2465 network node and a terminal or on a sidelink comprising a plurality of carriers for at least

[1160] one direction of transmission (e.g. DL and / or UL), as well as to the aggregate of carriers.

[1161] 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

[1162] as component carriers (CC). In such a link, data may be transmitted over more than one 2470 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),

[1163] over which control information may be transmitted, wherein the control information may

[1164] refer to the primary carrier and other carriers, which may be referred to as secondary 2475 carriers (or secondary component carrier, SCC). However, in some approaches, control information may be sent over more than one carrier of an aggregate, e.g. one or more

[1165] PCCs and one PCC and one or more SCCs.

[1166] A transmission may generally pertain to a specific channel and / or specific resources,

[1167] in particular with a starting symbol and ending symbol in time, covering the interval 2480 therebetween. A scheduled transmission may be a transmission scheduled and / or expected

[1168] 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

[1169] may not be received, or a scheduled uplink transmission may not be transmitted due to

[1170] power limitations, or other influences (e.g., a channel on an unlicensed carrier being 2485 occupied). A transmission may be scheduled for a transmission timing substructure (e.g.,

[1171] 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

[1172] in the transmission timing structure at which the transmission starts or ends.

[1173] Predefined in the context of this disclosure may refer to the related information being 2490 defined for example in a standard, and / or being available without specific configuration

[1174] 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 / conhgured, e.g. by the network or a network node.

[1175] A configuration or schedule, like a mini-slot configuration and / or structure configuration, 2495 may schedule transmissions, e.g. for the time / transmissions it is valid, and / or transmissions may be scheduled by separate signalling or separate configuration, e.g. separate RRC

[1176] P113137WO01 69 / 79signalling and / or downlink control information signalling. The transmission / s scheduled may represent signalling to be transmitted by the device for which it is scheduled, or signalling to be received by the device for which it is scheduled, depending on which side 2500 of a communication the device is. It should be noted that downlink control information

[1177] or specifically DCI signalling may be considered physical layer signalling, in contrast to

[1178] higher layer signalling like MAC (Medium Access Control) signalling or RRC layer signalling. The higher the layer of signalling is, the less frequent / the more time / resource consuming it may be considered, at least partially due to the information contained in such 2505 signalling having to be passed on through several layers, each layer requiring processing

[1179] and handling.

[1180] A scheduled transmission, and / or transmission timing structure like a mini-slot or slot,

[1181] may pertain to a specific channel, in particular a physical uplink shared channel, a physical

[1182] uplink control channel, or a physical downlink shared channel, e.g. PUSCH, PUCCH or 2510 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

[1183] such channel, cell and / or carrier aggregation. 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 2515 channel. For such channels, semi-persistent configuring may be particularly suitable.

[1184] Generally, a configuration may be a configuration indicating timing, and / or be represented

[1185] or configured with corresponding configuration data. A configuration may be embedded

[1186] 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. 2520

[1187] A control region of a transmission timing structure may be an interval in time and / or frequency domain for intended or scheduled or reserved for control signalling, in particular downlink control signalling, 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-specihc) dedicated 2525 signalling (which may be single-cast, for example addressed to or intended for a specific

[1188] UE), e.g. on a PDCCH, or RRC signalling, or on a multicast or broadcast channel.

[1189] 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. A control region may be associated, e.g. 2530 via configuration and / or determination, to one or more specific UEs and / or formats of PDCCH and / or DCI and / or identifiers, e.g. UE identifiers and / or RNTIs or carrier / cell identifiers, and / or be represented and / or associated to a CORESET and / or a search

[1190] P113137WO01 70 / 79space.

[1191] The duration of a symbol (symbol time length or interval) of the transmission timing 2535 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

[1192] to be used for the scheduled transmission.

[1193] System information signalling may comprise and / or represent signalling indicating one or

[1194] more system parameters, in particular timing and / or synchronisation, and / or numerol- 2540 ogy and / or a system identity (e.g. beam identity and / or cell ID and / or node ID and / or network ID). System information signalling may comprise broadcast signalling or multicast signalling; it may be beam-formed signalling, or non-beam-formed. In some cases,

[1195] system information signalling may comprise synchronisation signalling, e.g. PSS and / or

[1196] SSS, and / or reference signalling, e.g. DM-RS, and / or data signalling, e.g. on a broad- 2545 cast channel like PBCH, or on a data channel like PDSCH, e.g. suitable for broadcast

[1197] or multicast, or scrambled with an ID provided in earlier signalling or predefined in a standard. Such data signalling may comprise encoded information, e.g. with error detection coding and / or error correction coding. System information signalling may comprise

[1198] System Information, e.g. a Master Information Block (MIB) and / or one or more System 2550 Information Blocks (SIB). System information signalling may be carried on a SSB beam.

[1199] 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 2555 component or duration or length in time of the symbol, unless it is clear from the context

[1200] 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

[1201] be considered a superstructure of a slot), respectively their time domain component. A 2560 transmission timing structure may generally comprise a plurality of symbols defining the

[1202] 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)

[1203] may be defined by a succession of such transmission timing structures, which may for 2565 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

[1204] 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

[1205] P113137WO01 71 / 79control signalling is received, e.g. in relation to the timing grid. A transmission timing 2570 structure may in particular be a slot or subframe or in some cases, a mini-slot.

[1206] Feedback signalling may be considered a form or control signalling, e.g. uplink or sidelink control signalling, like UCI (Uplink Control Information) signalling or SCI (Sidelink Control Information) signalling. Feedback signalling may in particular comprise and / or represent acknowledgement signalling and / or acknowledgement information and / or measure- 2575 ment reporting.

[1207] Signalling utilising, and / or on and / or associated to, resources or a resource structure may

[1208] be signalling covering the resources or structure, signalling on the associated frequency / ies and / or in the associated time interval / s. It may be considered that a signalling resource structure comprises and / or encompasses one or more substructures, which may be as- 2580 sociated to one or more different channels and / or types of signalling and / or comprise

[1209] one or more holes (resource element / s not scheduled for transmissions or reception of transmissions). A resource substructure, e.g. a feedback resource structure, may generally be continuous in time and / or frequency, within the associated intervals. It may be considered that a substructure, in particular a feedback resource structure, represents a 2585 rectangle filled with one or more resource elements in time / frequency space. However,

[1210] in some cases, a resource structure or substructure, in particular a frequency resource

[1211] range, may represent a non-continuous pattern of resources in one or more domains, e.g.

[1212] time and / or frequency. The resource elements of a substructure may be scheduled for associated signalling. 2590

[1213] Example types of signalling comprise signalling of a specific communication direction, in particular, uplink signalling, downlink signalling, sidelink signalling, as well as reference signalling (e.g., SRS or CRS or CSI-RS), communication signalling, control signalling, and / or signalling associated to a specific channel like PUSCH, PDSCH, PUCCH, PDCCH, PSCCH, PSSCH, etc.). 2595

[1214] In the context of this disclosure, there may be distinguished between dynamically scheduled or aperiodic transmission and / or configuration, and semi-static or semi-persistent or periodic transmission and / or configuration. The term “dynamic” or similar terms may generally pertain to conhguration / transmission valid and / or scheduled and / or configured

[1215] for (relatively) short timescales and / or a (e.g., predefined and / or configured and / or lim- 2600 ited and / or definite) number of occurrences and / or transmission timing structures, e.g.

[1216] one or more transmission timing structures like slots or slot aggregations, and / or for one

[1217] or more (e.g., specific number) of transmission / occurrences. Dynamic configuration may

[1218] be based on low-level signalling, e.g. control signalling on the physical layer and / or MAC

[1219] layer, in particular in the form of DCI or SCI. Periodic / semi-static may pertain to longer 2605

[1220] P113137WO01 72 / 79timescales, e.g. several slots and / or more than one frame, and / or a non-defined number of occurrences, e.g., until a dynamic configuration contradicts, or until a new periodic configuration arrives. A periodic or semi-static configuration may be based on, and / or be configured with, higher-layer signalling, in particular RCL layer signalling and / or RRC signalling and / or MAC signalling. 2610

[1221] In this disclosure, for purposes of explanation and not limitation, specific details are set

[1222] forth (such as particular network functions, processes and signalling steps) in order to provide a thorough understanding of the technique presented herein. It will be apparent

[1223] to one skilled in the art that the present concepts and aspects may be practised in other variants and variants that depart from these specific details. 2615

[1224] For example, the concepts and variants are partially described in the context of Long

[1225] 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

[1226] and aspects in connection with additional or alternative mobile communication technologies such as the Global System for Mobile Communications (GSM) or IEEE standards as 2620 IEEE 802. Had or IEEE 802.11 ay. While described variants may pertain to certain Technical Specifications (TSs) of the Third Generation Partnership Project (3GPP), it will be appreciated that the present approaches, concepts and aspects could also be realized in connection with different Performance Management (PM) specifications.

[1227] Moreover, those skilled in the art will appreciate that the services, functions and steps 2625 explained herein may be implemented using software functioning in conjunction with a programmed microprocessor, or using an Application Specific Integrated Circuit (ASIC),

[1228] 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

[1229] are elucidated in the context of methods and devices, the concepts and aspects presented 2630 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.

[1230] It is believed that the advantages of the aspects and variants presented herein will be fully 2635 understood from the foregoing description, and it will be apparent that various changes

[1231] may be made in the form, constructions and arrangement of the exemplary aspects thereof without departing from the scope of the concepts and aspects described herein or without sacrificing all of its advantageous effects. The aspects presented herein can be varied in

[1232] many ways. 2640

[1233] P113137WO01 73 / 79Some useful abbreviations comprise

[1234] Abbreviation Explanation

[1235] ABF Analog beamformer, fanout to antenna+beamforming ACK / NACK Acknowledgment / Negative Acknowledgement Ant Antenna

[1236] ARQ Automatic Repeat reQuest

[1237] BB BaseBand

[1238] Beamindex IF beamindex interface

[1239] BER Bit Error Rate

[1240] BI Beam Index

[1241] BLER Block Error Rate

[1242] BPSK Binary Phase Shift Keying

[1243] BWP BandWidth Part

[1244] CAZAC Constant Amplitude Zero Cross Correlation

[1245] CB Code Block

[1246] CBB Code Block Bundle

[1247] CBG Code Block Group

[1248] CDM Code Division Multiplex

[1249] CM Cubic Metric

[1250] Comm RXBB communication receiver baseband

[1251] CORESET Control Resource Set

[1252] CP Cyclic Prefix

[1253] CP rem CP removal

[1254] CQI Channel Quality Information

[1255] CRC Cyclic Redundancy Check

[1256] CRS Common reference signal

[1257] CSI Channel State Information

[1258] CSI-RS Channel state information reference signal

[1259] DAI Downlink Assignment Indicator

[1260] DCI Downlink Control Information

[1261] DFE Digital Frontend

[1262] DFT Discrete Fourier Transform

[1263] DFTS-FDM DFT-spread-FDM

[1264] DM(-)RS Demodulation reference signal(ing)

[1265] eMBB enhanced Mobile BroadBand

[1266] FDD Frequency Division Duplex

[1267] FDE Frequency Domain Equalisation

[1268] P113137WO01 74 / 79FDF Frequency Domain Filtering

[1269] FDM Frequency Division Multiplex

[1270] FFT Fast Fourier Transform

[1271] FR1 Frequency Range 1, covering 410MHz to 7125MHz FR2 Frequency Range 2, covering 24250MHz to 52600 MHz GPIO General Purpose Input Output

[1272] HARQ Hybrid Automatic Repeat Request

[1273] IAB Integrated Access and Backhaul

[1274] IFFT Inverse Fast Fourier Transform

[1275] Im Imaginary part, e.g. for pi / 2*BPSK modulation

[1276] IR Impulse Response

[1277] ISI Inter Symbol Interference

[1278] JCAS Joint Communication and Sensing

[1279] MBB Mobile Broadband

[1280] MCS Modulation and Coding Scheme

[1281] MIMO Multiple-input-multiple-output

[1282] MRC Maximum-ratio combining

[1283] MRT Maximum-ratio transmission

[1284] MU-MIMO Multiuser multiple- input-multiple-output

[1285] OFDM / A Orthogonal Frequency Division Multiplex / Multiple Access PAPR Peak to Average Power Ratio

[1286] PDCCH Physical Downlink Control Channel

[1287] PDSCH Physical Downlink Shared Channel

[1288] PRACH Physical Random Access CHannel

[1289] PRB Physical Resource Block

[1290] PUCCH Physical Uplink Control Channel

[1291] PUSCH Physical Uplink Shared Channel

[1292] (P)SCCH (Physical) Sidelink Control Channel

[1293] PSS Primary Synchronisation Signal(ing)

[1294] PT-RS Phase Tracking Reference signalling

[1295] (P)SSCH (Physical) Sidelink Shared Channel

[1296] QAM Quadrature Amplitude Modulation

[1297] occ Orthogonal Cover Code

[1298] QPSK Quadrature Phase Shift Keying

[1299] PSD Power Spectral Density

[1300] RAN Radio Access Network

[1301] RAT Radio Access Technology

[1302] RB Resource Block

[1303] P113137WO01 75 / 79RE Resource Element

[1304] Re Real part (e.g., for pi / 2*BPSK) modulation

[1305] RF Radio Frequency

[1306] RNTI Radio Network Temporary Identifier

[1307] RRC Radio Resource Control

[1308] RX Receiver, Reception, Reception-related / side

[1309] SA Scheduling Assignment

[1310] SC-FDE Single Carrier Frequency Domain Equalisation

[1311] SC-FDM / A Single Carrier Frequency Division Multiplex / Multiple Access SCI Sidelink Control Information

[1312] SINR Signal-to-interference-plus-noise ratio

[1313] SIR Signal-to-interference ratio

[1314] SNR Sign al-to- noise-ratio

[1315] SPI Serial to Parallel Interface

[1316] SR Scheduling Request

[1317] SRS Sounding Reference Signal(ing)

[1318] sss Secondary Synchronisation Signal(ing)

[1319] SVD Singular- value decomposition

[1320] TB Transport Block

[1321] TDD Time Division Duplex

[1322] TDM Time Division Multiplex

[1323] T-RS Tracking Reference signalling or Timing Reference signalling TX Transmitter, Transmission, Transmission-related / side UCI Uplink Control Information

[1324] UDC Up-Down Converter, mixing from BBj-^RF

[1325] UE User Equipment

[1326] URLLC Ultra Low Latency High Reliability Communication

[1327] VL-MIMO Very- large multiple-input-multiple-output

[1328] WD Wireless Device

[1329] Wfg Waveform Generator

[1330] ZC Zadoff-Chu

[1331] ZF Zero Forcing

[1332] ZP Zero-Power, e.g. muted CSLRS symbol

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

[1334] P113137WO01 76 / 79

Claims

CLAIMS1. Method of operating a radio node in a wireless communication network, the method 2645 comprising communicating utilising data signalling, the data signalling comprising and / or representing a set of code blocks, each code block representing a bit pattern comprisingan integer number of bits, the data signalling spanning a set of allocation units in time domain, wherein at least one code block of the set of code blocks is split into a first portion associated to a first allocation unit of the set of allocation units, and into a second 2650 portion associated to a second allocation unit of the set of allocation units, wherein thefirst portion is in a first range in frequency domain, and the second portion is in a secondrange in frequency domain.

2. Radio node for a wireless communication network, the radio node being adapted for communicating utilising data signalling, the data signalling comprising and / or represent- 2655 ing a set of code blocks, each code block representing a bit pattern, the data signalling spanning a set of allocation units in time domain, wherein at least one code block of theset of code blocks is split into a first portion associated to a first allocation unit of the setof allocation units, and into a second portion associated to a second allocation unit of theset of allocation units, wherein the first portion is in a first range in frequency domain, 2660 and the second portion is in a second range in frequency domain.

3. Method or device according to one of the preceding claims, wherein the first rangedoes not overlap with the second range.

4. Method or device according to one of the preceding claims, wherein the first portionis mapped to the first range based on and / or by interleaving, and / or the second portion 2665 is mapped to the second range based on and / or by interleaving.

5. Method or device according to one of the preceding claims, wherein to each allocationunit, there is associated at least one code block.

6. Method or device according to one of the preceding claims, wherein the code blocks ofthe set of code blocks are associated to the same data block. 26707. Method or device according to one of the preceding claims, wherein the first allocationunit and the second allocation unit are neighbouring in time domain.

8. Method or device according to one of the preceding claims, wherein the first range and / or the second range comprise an integer number of sub-carriers, wherein sub-patternsof bits of a code block are associated to different sub-carriers. 2675P113137WO01 77 / 799. Method or device according to one of the preceding claims, wherein no more than two code blocks are split on the first allocation unit and / or the second allocation unit.

10. Method or device according to one of the preceding claims, wherein code blocks are interleaved per allocation unit and / or are interleaved in frequency domain.

11. Method or device according to one of the preceding claims, wherein each bit pattern 2680 of a code block comprises error detection bits.

12. Method or device according to one of the preceding claims, wherein bits of thecode blocks are interleaved in interleaving sub-patterns, each interleaving sub-pattern comprising an integer number NIS of bits.

13. Method or device according to one of the preceding claims , wherein the bits of the code 2685 blocks are interleaved based on a rectangular interleaver, and / or based on interleavingsub-patterns of different code blocks alternatingly.

14. Program product comprising instructions causing processing circuitry to control and / or perform a method according to one of claims 1, or one of 3 to 13.

15. Carrier medium arrangement carrying and / or storing a program product according 2690 to claim 14.P113137WO01 / Q

Images