WO2025080172A1

WO2025080172A1 - Data block handling for wireless communication

Info

Publication number: WO2025080172A1
Application number: PCT/SE2023/051011
Authority: WO
Inventors: Robert Baldemair; Qiang Zhang; Thomas Magnusson; Anders Elgcrona
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-10-10
Filing date: 2023-10-10
Publication date: 2025-04-17
Anticipated expiration: 2026-04-10

Abstract

There is disclosed a method of operating a radio node in a wireless communication net- work, the method comprising processing at least one data block for communication sig- nalling, the at least one data block being processed based on mapping bit sequences of input data into different memory spaces of the radio node (10, 100), wherein each bit sequence has a size of NST, wherein into each memory space, one or more bit sequences are mapped, wherein the at least one data block represents and/or comprises an integer number NDB of bits, wherein NDB = I × NST, wherein I is an integer of 1 or larger, and NST is an integer number of bits comprised in a unit of digital information The disclosure also pertains to related devices and methods.

Description

DATA BLOCK HANDLING FOR WIRELESS COMMUNICATION Technical field This disclosure pertains to wireless communication, in particular for high frequencies. Background For future wireless communication systems, large data rates are going to be transmitted. This may put large data loads on circuitry, which may drive costs and/or inefficiencies in 5 processing and/or radio circuitry and/or interfaces carrying data between circuitries. Summary It is an object of this disclosure to provide approaches of handling data blocks for wireless communication, in particular for physical layer processing. The approaches described may be utilised for one or more different frequencies ranges. For example, they may be 10 implemented for frequency ranges (e.g., carrier bandwidth and/or system bandwidth) for communication signalling of 1 GHz or more, 2GHz or more, 5 GHz or more, or 6 GHz or more, or 10 GHz or more, and/or for millimeter wave communication, in particular for radio carrier frequencies around and/or above 52.6 GHz, which may be considered high radio frequencies (high frequency) and/or millimetre waves. The carrier frequency/ies 15 may be between 52.6 and 140 GHz, e.g. with a lower border between 52.6, 55, 60, 71 GHz and/or a higher border between 71, 72, 90, 114, 140 GHz or higher, in particular between 55 and 90 GHz, 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 20 center frequency or maximum frequency of the carrier. The radio nodes and/or network described herein may operate in wide-band, e.g. with a carrier bandwidth (or bandwidth or carrier aggregation) of 400MHz or more, in particular 1 GHz or more, or 2 GHz or more, or even larger, e.g. 6 GHz or more, or 8 GHz or more; the scheduled or allocated bandwidth may be the carrier bandwidth, or be smaller, e.g. depending on channel and/or 25 procedure. In some cases, operation may be based on an OFDM wave-form or a SC-FDM wave-form (e.g., downlink and/or uplink), in particular a FDF-SC-FDM-based wave- form. However, operation based on a single carrier wave-form, e.g. SC-FDE (which may be pulse-shaped or Frequency Domain Filtered, e.g. based on modulation scheme and/or MCS), may be considered for downlink and/or uplink. In general, different wave-forms 30 may be used for different communication directions. Communicating using or utilising a carrier and/or beam may correspond to operating using or utilising the carrier and/or beam, and/or may 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 subcarrier spacing and/or duration of an allocation unit and/or an 35 equivalent thereof, e.g., in comparison to an OFDM based system. A subcarrier spacing or equivalent frequency interval may for example correspond to 960 kHz, or 1920 kHz, e.g. representing the bandwidth of a subcarrier or equivalent. The approaches are particularly advantageously implemented in a future 6th Generation (6G) telecommunication network or 6G radio access technology or network (RAT/RAN), 40 in particular according to 3GPP (3rd Generation Partnership Project, a standardisation organization). A suitable RAN may in particular be a RAN according to NR, for example release 18 or later, or LTE Evolution. However, the approaches may also be used with other RAT, for example future 5.5G systems or IEEE based systems. There is disclosed a (first) method of operating a radio node in a wireless communication 45 network. The method comprises communicating based on communication signalling, the communication signalling comprising at least one data block. The at least one data block represents and/or comprises and/or has an integer number NDB of bits, wherein NDB = I × NST . I is an integer of 1 or larger, and NST is an integer number of bits comprised in a unit of digital information. 50 Alternatively, or additionally, a (second) method of operating a radio node in a wire- less communication network is considered; the (second) method may comprise the (first) method. The (second) method comprises processing at least one data block for communi- cation signalling, the data block being processed based on mapping bit sequences of input data into different memory spaces of the radio node. Each bit sequence has a size of NST, 55 wherein into each memory space, one or more bit sequences are mapped, wherein the at least one data block represents and/or comprises and/or has an integer number NDB of bits, wherein NDB = I × NST . I is an integer of 1 or larger, and NST is an integer number of bits comprised in a unit of digital information. Moreover, a (first) radio node for a wireless communication network is described. The ra- 60 dio node is adapted for communicating based on communication signalling, the communi- cation signalling comprising at least one data block. The at least one data block represents and/or comprises and/or has an integer number NDB of bits, wherein NDB = I×NST . I is an integer of 1 or larger, and NST is an integer number of bits comprised in a unit of digital information. 65 Alternatively, or additionally, a (second) radio node for a wireless communication network is considered. The (second) radio node may be implemented as, and/or comprise the functionality and/or features), of the first radio node. The second radio node may be adapted for processing at least one data block for communication signalling, the data block being processed based on mapping bit sequences of a data block into different 70 memory spaces of the radio node. Each bit sequence has a size of NST, wherein into each memory space, one or more bit sequences are mapped, wherein the at least one data block represents and/or comprises and/or has an integer number NDB of bits, wherein NDB = I × NST . I is an integer of 1 or larger, and NST is an integer number of bits comprised in a unit of digital information. 75 Approaches described herein facilitate parallel processing on the physical layer, e.g., avoid- ing locking memory spaces. NST consecutive bits may in general be considered a bit sequence. The data block may comprise an integer number of sequential bit sequences. In general, communicating based on communication signalling may be based on, and/or comprise processing at least on 80 data block. Communicating may comprise transmitting the communication signalling, or receiving the communication signalling. Communicating may be based on scheduling, e.g., transmitting scheduling information to a receiver (e.g., UE), or receiving scheduling information, e.g., from a radio node like a network node, which may also transmit the communication signalling (when scheduled for reception by the receiver of the schedul- 85 ing information), or intend to receive the communication signalling (when scheduled for transmission by the receiver of the scheduling information). Scheduling information may indicate and/or allocate resources for transmission and/or reception, and/or may indi- cate a MCS of the communication signalling, and/or a data block size (and/or multi- ple sizes, e.g., of different structure scalings, and/or different data blocks of the same 90 structure scaling). Scheduling information may be provided and/or transmitted dynam- ically, and/or semi-statically, and/or with higher-layer signalling, and/or physical layer signalling. Scheduling information may be considered control signalling, in particular it may comprise physical layer control signalling. In some cases, scheduling information may represent data bits of a data block. Scheduling information, in particular indicated 95 resources and/or allocated resources, may be based on, and/or restricted by, and/or be in accordance with NDB. Communication signalling may comprise data signalling, e.g., on a data channel like a physical data channel and/or a dedicated channel or shared channel or broadcast channel, for example PDSCH, or PUSCH, or PBCH. In some cases, communication signalling may 100 comprise control signalling, e.g., on a physical control channel, or a data channel, e.g., as UCI on PUSCH, or on a PUCCH or PDCCH or PDSCH. It may be considered that communication signalling may comprise, and/or be associated to, and/or embed, reference signalling, e.g., DM-RS and/or PT-RS. Such reference signalling may be signalling that does not carry any of the coded bits and/or data block/s. 105 It may be considered that the NDB bits are rate-matched, and/or may include padding bits (e.g., to fill up to a suitable number). This may provide a suitable size, without increasing processing needed for increased rate-matching. It may be considered that NST may correspond to the number of bits in a byte or word or doubleword or longword, and/or the unit of digital information may correspond to a 110 byte or word or doubleword or longword. Thus, a standardized unit may be used. A byte may have 8 bits, which may be a standard shared unit between different platforms. It may be considered that NST may be one of 8, 16, 32, 64. These are commonly used sizes for memory spaces, and allow easy utilisation in standard processing circuitry. In some variants, I may be 1 or 2. This may normalise NST to a commonly used size of 115 memory spaces. In general, NDB may be dependent on a modulation, and/or dependent on a modulation and coding scheme, MCS. This may allow flexible adaptation to MCS. However, in some cases, an approach independent on modulation may be considered. NDB may be consid- ered dependent on modulation is it is dependent on a Q_m and/or modulation order. It 120 may be considered independent of modulation, if it is independent of modulation order Q_m, e.g., the same for all modulation orders of a set of plurality of modulation orders, which may comprise the available modulation orders, e.g., according to capability and/or configuration. Alternatively, or additionally, NDB may be based on a number of layers, e.g., a number of layers (e.g., N) used for transmission of the data block and/or communi- 125 cation signalling. In some cases, NDB may be dependent on N ×Q_m (e.g., dependent on modulation), or N ×Q (e.g., independent of modulation). In particular, it may represent and/or be based on a lcm (lowest common multiple) of one of such and a multiple of NST. It may be considered that the bits of a data block comprise information bits (also referred to as data bits) and coding bits. The coding bits may comprise error detection bits (e.g., 130 for CRC), and/or error correction bits, e.g., for forward error correction, and/or based on turbo coding or polar coding or Muller-Reed coding. This may allow suitable error rate, e.g., in terms of reliability and/or BLER. A data block may in general represent rate-matched and/or coded information. Accord- ingly, error detection and/or correction may be facilitate, and/or suitable NDB may be 135 supported. It may be considered that the communication signalling may comprise and/or represent data signalling, and/or represent and/or comprise user data and/or higher-layer data or information (e.g., from a layer above physical layer). Approaches herein may be partic- ularly suitable for such data, which may comprise one or more code blocks and/or data 140 blocks (e.g., as opposed to usually smaller control information). The communication signalling may comprise multiple data blocks, wherein different data blocks of the multiple data blocks may comprise and/or have and/or represent different sizes and/or number of bits (having different NDB according to the criteria discusses herein). Alternatively, or additionally, different data blocks may comprise and/or have 145 and/or represent the same size and/or number of bits and/or the same NDB). The com- munication signalling may correspond to one transmission or occurrence, for example on a channel like PUSCH or PDSCH or PSSCH or PSCCH or PDCCH or PUCCH or PBCH. In some cases, the communication signalling may correspond to transmission in one transmission timing structure and/or in one time interval, e.g., one subframe and/or 150 slot and/or an integer number of symbols or block symbols; the communication signalling may cover the time interval and/or each symbol of the time interval may carry a part of the communication signalling. In some variant, one data block and/or code block of the communication signalling may be mapped to one symbol; each symbol may carry one data block and/or code block. This may allow parallel processing of signalling received 155 at different symbols. It may be considered that communicating may be based on mapping the NDB bits into separate memory spaces of the radio node, e.g., such that each memory space may con- tain at least on unit of digital information. Separate memory spaces may be separately addressable, and/or non-overlapping, and/or may be associated to different processes, 160 and/or cores, and/or processing threads, and/or branches. Optimised parallelisation may be provided. The at least one data block, and/or each of the data blocks of communication signalling, may represent a transport block, or code block, or code block bundle, or code block group. Data block may have a structure scaling, e.g., a code block may be the smallest 165 scale, a code block group may comprise one or more CB (larger scale), and/or a CBB or transport block may comprise one or more CBGs and/or CBs, and/or a transport block may comprise one or more CBBs. Characteristics of a smaller scale may transfer to a larger scale, e.g., such that a NDB of a larger scale shows the NBD may be from a set of numbers, the set comprising or consisting of a plurality of 170 numbers that are integer multiples of NST (with different integer multiples). The integer may in general be 1 or larger. Thus, a well-defined set of numbers may be utilisable. Communication signalling may in general comprise a series of sequential data blocks (e.g., one or more), and/or may be in sidelink or uplink or downlink; scheduling may be cor- responding. The communication signalling may be scheduled, e.g., with scheduling infor- 175 mation; a radio node may be adapted to transmit and/or receive scheduling information, and/or to receive and/or transmit based on, and/or according to, scheduling information. In general, processing may comprise modulation of the data block, e.g., based on the mapping , or the mapping may be based on demodulation of the data block. This may comprise reading information from memory spaces (e.g., for modulation), or writing into 180 memory spaces, e.g. after demodulation and/or for decoding. In particular reception of communication signalling having the described structure may be parallelised easily. In some cases, processing may comprise descrambling and/or delayering, and/or combing bits to a data stream, e.g., for reception of the communication signalling. It may be considered that processing may comprise scrambling and/or mapping to layers, and/or 185 separating bit sequences, e.g., for transmission of the communication signalling. It may be considered that the bit sequences (e.g., of the data block, and/or of each data block) are sequential in the data block. This may enable easy handling and/or processing of the bits. It may generally be considered that, based on the mapping, no memory space comprises 190 bits from more than one data block, and/or more than one bit sequence. A 1-to-1 mapping of bit sequences to memory spaces may be provided. In general, a memory space, and/or each of the memory spaces, may correspond to one memory address, and/or memory cell, and/or may accommodate exactly the one or more bit sequences mapped to it, and/or may correspond in size to the size of the unit of digital 195 information, e.g. having the size of a bit sequence mapped to it. Different memory spaces may have the same size. A memory space may be in RAM, or register, or stack of, and/or associated to, processing circuitry. Parallel processing using different memory spaces may be performed, e.g., as part of processing. In general, parallel processes may use the same size of memory spaces, or different sizes; if different sizes are used, the larger size/s may 200 be integer multiples of the smallest size used. In general, a memory space may have a size of a multiple integer of NST. The radio node may operate in TDD mode, e.g. switching between DL periods and UL 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 205 transmissions (e.g., a network node may transmit during DL, and receive during UL, and 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 number of symbol time intervals, e.g. 10 or more symbols, or 12 or more symbols; there may be the same duration for guard periods for DL/UL and UL/DL, or different ones. 210 The guard period may allow switching circuitry between the different communication directions and/or handling of interference (in particular considering that DL signalling tends to much more powerful than (received) UL signalling). An antenna arrangement 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 215 panels. Different antenna arrangements and/or panels and/or sub-arrays and/or elements may be adapted to be controlled or controllable separately from each other. There may be the same number of DL and UL periods and/or the same duration associated to DL 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) 220 3:1 (e.g., 3 DL periods followed by a TDD guard period and 1 UL period), or (roughly) 2:1, or even (roughly) 1:2 or 1:NU with NU 3 or larger, for UL heavy scenarios. UL period durations may be the same as DL period durations, or different. The distribution and/or duration of DL and UL periods may be referred to as TDD pattern; the TDD pattern may be dynamically controllable (e.g., with DCI signalling), and/or configured 225 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 the smallest time domain distribution of DL period/s and/or UL period/s and/or TDD guard period/s repeated over time, e.g. in one or more frames and/or subframes and/or slots and/or a time duration covering multiple repetitions of the TDD pattern. 230 It may be considered that the radio node is adapted for utilising a number NP of an- tenna 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 or more, or 50 or more, or 100 or more. An antenna sub-array, and/or the antenna ele- ments associated thereto and/or comprised therein, may be associated and/or connected 235 or connectable to one and/or the same antenna circuitry, and/or be jointly controllable 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- 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 an- 240 tenna 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 or vertical. In some cases, NP may be an even number, wherein it may be considered that NP/2 antenna sub-arrays (and/or their antenna elements) may be associated to a 245 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 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 250 allows multiple beams to be operated, with good flexibility and/or large signalling capac- ity. In general, an antenna arrangement associated to a radio node may comprise one or more antenna sub-arrays, in particular an even number of antenna sub-arrays. In general, at different times, different antenna sub-arrays and/or panels may be used for different functions, e.g. transmission or reception, and/or communication. The polarisation of an 255 antenna element may be associated to a specific operation direction, e.g. for transmission or reception. Depending on signalling direction (transmission or reception), polarisation may be different. For example, an antenna sub-array may be associated to a first polari- sation for transmission, and a second polarisation for reception, or vice versa. This may be achieved, for example, by providing crossed linear antenna elements for the sub-arrays, 260 with associated connections/circuitry according to polarisation. It may be considered that operating utilising communication signalling, and/or communi- cating utilising communication signalling, may comprise transmitting the communication signalling and/or receiving the communication signalling. It may be considered that the communication signalling is based on an OFDM wave- 265 form, e.g. OFDM, or DFT-s-OFDM, or pulse-shaped 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 generally be a cyclic prefix, or a cyclic suffix. The appendix may represent a repetition of a part of signalling carried by a symbol at its start (suffix) or end (prefix), which may be appended at the opposite of the symbol 270 (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 appendix may be associated to a specific symbol, it may have a duration shorter than the symbol duration, e.g. less than 1/4 of the symbol duration, or less than 1/6. 275 The radio node may be a wireless device or user equipment or terminal. Alternatively, it may be a network node or signalling radio node. A radio node adapted for wireless com- munication may be a radio 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 280 standard like a 3GPP standard or IEEE standard. Operating utilising communication signalling may comprise transmitting and/or receiving communication signalling. The radio circuitry and/or processing circuitry and/or antenna circuitry of a radio node may be adapted for handling communication signalling The radio node may be adapted for full-duplex operation, and/or half-duplex operation. Full duplex may refer to transmit- 285 ting and receiving at the same time, e.g. using the same or different circuitries, and/or using different antenna sub-arrays or separately operable antenna sub-arrays or antenna elements. The communication signalling may be beam-formed. A 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., sub- 290 carriers), e.g. to provide a time-variable signal. A DFT-s-OFDM based wave-form may 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 Single- Carrier based wave-forms, e.g. FDE-based wave-forms. Communication, e.g. on data 295 channel/s and/or control channel/s, may be based on, and/o utilise, a DFT-s-OFDM based wave-form, or a Single-Carrier based wave-form. Communication may in particular on multiple communication links and/or beams and/or 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 trans- 300 mission or reception may be based on different sequence roots and/or combs and/or cyclic 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 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 305 uplink). For example, there may be first reference signalling transmitted using a first 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. There is also described a program product comprising instructions causing processing circuitry to control and/or perform a method as described herein, e.g., when executed by 310 a radio node and/or processing circuitry (e.g., of the radio node). The instructions may be executable by processing circuitry, and/or computer-executable. 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 radio node is also disclosed. 315 Brief description of the drawings The drawings are provided to illustrate concepts and approaches described herein, and are not intended to limit their scope. The drawings comprise: Figure 1, showing an exemplary radio node, e.g., a wireless device; and Figure 2, showing an exemplary radio node, e.g., a network node. 320 Detailed description In wireless communication, there is usually performed physical layer processing of infor- mation and/or data. Bits representing the data may be encoded (e.g., utilising error coding), and then modulated for transmission. The size of data blocks may be depen- dent on a MCS and/or coding and/or modulation to be used, and/or available resources. 325 Rate-matching may be used to adapted the coding bits to the size. A data block transmit- ted may be considered to comprise bits representing data and/or information (e.g., from higher layers, e.g., as control and/or user data, or physical layer data), and/or error cod- ing bits, e.g. for error detection coding, and/or error correction coding. Rate-matching may in particular pertain to the number of error correction coding bits used. The total 330 number of bits of a data block may be referred to as coded bits. Data bits or information bits may be considered bits not including the coding bits (in particular, physical layer coding bits; data may in some cases include coding bits for higher layers). With increased data rates, in many cases, parallel processing of data may become increas- ingly beneficial. This may lead to lower power consumption of circuitry in comparison to 335 using serial processing with high processor frequency, which may produce a large amount of waste heat. Herein, approaches improving data handling, e.g., for facilitating such parallel processing, are discussed. In the following, L may represent NDB, and/or these expressions may be used interchangeably. ceil() indicates the ceiling function, floor() the floor function. It may be noted that some characteristics of data substructures (e.g., CB), 340 may transfer to larger structures, e.g., CBB or transport block. Thus, different structure scales for a data block may be considered (e.g., such that features may be applicable to a data block like a code block, or CBG, or CBB, or transport block, or to all of them in a nestled structure. In NR, coded bits may be rate matched so that a code block can be split across the 345 assigned number of layers. To this end, the number of coded bits NDB of a code block is an integer multiple of N×Q_m (N×Q_m bits fit onto N layers with Q_m bits per modulation symbol). For parallelizing code block processing, it may be considered using a number of coded bits of an integer multiple of a unit of digital information, e.g. like a byte, which may be an 350 octet (8bit), or word (e.g., 2 byte, e.g., 16 bit), double word (which may be 4 byte and/or 32 bit, or long word, etc. This may enable unit-wise (e.g., byte/word/double-word -wise) memory access without the need for locking functionality. Code block sizes not being multiple of byte/word/double-word may require locking func- tionality when byte/word/doubleword-wise memory access is used, otherwise two pro- 355 cesses (for two code words) may need access the same byte/word/doubleword in memory overwriting data of the other process. It may be considered (e.g., in the context of NR), that a transport block or CBB may comprise C₁ CBs of size E₁ = N ×Q_m× floor(G/(N ×Q_m×C)), and/or C₂ CBs of size E₂ = N×Q_m×ceil(G/(N×Q_m×C)). There may hold C₂ = mod(G/(N×Q_m), C), C₁ = 360 C − C₂. C may be the number of CBs in the CBB or transport block, G may be the number of coded bits in the CBB, Q_m may be the number of bits per modulation symbol, e.g., according to a modulation scheme. Using N ×Q_m may facilitate that the number of generated modulation symbols can be mapped across N layers. The number of coded bits (NDB or L) may a multiple of NST, e.g., 8 or 16 or 32 and/or of 365 size of a unit of digital information. This may be independent of the modulation and/or Q_m. In some cases, it may be particularly relevant for modulations with a number of bits not being the size of the digital information unit, or an integer multiple thereof, e.g., for one or more of Q_m = 1, 2, 4, 6, 10, 12, etc.. In general, Q_M may indicate the order of the modulation scheme, e.g., the number of bits representable by one point in the phase space 370 and/or value space available for the modulation. To enable that the code block or data block can be evenly split across N layers using modulation symbols with Q_m bits, it may be considered that the number of coded bits is both a multiple (integer of 1 or larger) of the unit size (e.g., 8/16/32) and N ×Q_m. In some variants, the number NDB may be dependent on Q_m. The number of bits ³⁷⁵ after rate matching (physical layer bits) bits of a code block (or more generally, a data block) may be determined to be a multiple (e.g., integer multiple of 1 or larger) of L = lcm(N ×Q_m, NST ) (NST may be 8, other multiples, e.g. 16, 32 may be considered). lcm denotes the least common multiple. It may be considered that resource scheduled for the communication signalling, and/or 380 data block, may be based on and/or be corresponding to, and/or according to, NST. For example, it may be desired that an integer number of L-bit blocks fits into the assigned number of scheduled resources. Scheduling and/or resource allocation may be accordingly, e.g., with scheduling restriction. For the number of resources N_res, e.g., resource elements or resource blocks, it may be considered a restriction that N_res×Q_m/L must be integer. 385 In an example, there may be considered N_res = N_prb× 12×N ×K (e.g., for NR). In this example, there may be N_prb RBs, N layers, K symbols (in time domain allocation), MCS with Q_m bits scheduled, all scheduled resources may be considered to be used for code blocks; additional resources may be scheduled, e.g., for reference signalling like DM-RS and/or CSI-RS. 390 For a NR setup or a similar setup (e.g., 12 subcarriers per RB, BPSK/QPSK/16QAM, 64QAM, 256QAM MCS) with two or more layers, this may be fulfilled. In a more specific example, there may be considered, for data signalling, e.g., a data block like a transport block or CBB: L = lcm(N ×Q_m, 8), C₁ CBs of size E₁ = L× floor(G/(L×C)); C₂ CBs of size E₂ = L× ceil(G/(L×C). There may hold C₂ = mod(G/L,C), and C₁ = C −C₂; 395 C is the number of CBs in the CBB or data block or transport block, G is the number of coded bits in the transport block or CBB or data block, Q_m represents the number of bits per modulation symbol. L = lcm(N × Q_m, 8) may facilitate that the Number of generated modulation symbols can be mapped across N layers, and/or that the Number of coded bits is a multiple of 8 bits. Instead of 8, another suitable number representative 400 of the size of the unit of digital information may be used. In some variants, the number of bits NDB may be Q_m independent. The number of coded bits of a code block or transport block or data block or CBB may be determined to be a multiple of L = lcm(lcm(N × Q, 8)), with lcm denoting the least common multiple, and Q being a vector containing all modulation schemes (for example, the order, e.g. 405 Q=[1,2,4,6,8] for modulation schemes [(pi/2) BPSK, QPSK, 16QAM, 64QAM, 256QAM]. The inner lcm function calculates the lcm of each vector element (first input argument) and 8 (or more generally, NST), and returns a vector. The outer lcm function calculates the lcm across vector elements of its input argument. This can lead to rather large L values. To ensure that an integer number of L-bit blocks fits into the assigned number 410 of scheduled resources, scheduling restrictions might be needed, for example, such that N_res ×Q_m/L may be restricted to be integer. For example, there may be considered a case with N_res = N_prb × 12 × N × K in NR (N_prb RBs, 12 subcarriers/REs per resource block, N layers, K symbols, MCS with Q_m bits scheduled, all scheduled resources used for code blocks and/or data blocks and/or 415 transport blocks, and/or CBBs; in some cases, additional resources may be scheduled, e.g., for reference signalling. In one example, there may be C₁ CBs of size E₁ = L × floor(G/(L×C)), C₂ CBs of size E₂ = L×ceil(G/(L×C)) with C₂ = mod(G/L,C), C₁ = C − C₂. C may be the number of CBs in the CBB/transport block, G the number of coded bits in the CBB/transport block, Q_m is the number of bits per modulation symbol 420 (order of modulation). L = lcm(lcm(N×Q, 8)) may ensure that the number of generated modulation symbols can be mapped across N layers, irrespective of Q_m (as long as Q_m is one of the supported ones). The number of coded bits is multiple of 8 bits. Figure 1 schematically shows a radio node, in particular a wireless device or terminal 10 or a UE (User Equipment). Radio node 10 comprises processing circuitry (which may also 425 be referred to as control circuitry) 20, which may comprise a controller connected to a memory. Any module of the radio node 10, e.g. a communicating module or determining module, may be implemented in and/or executable by, the processing circuitry 20, in particular as module in the controller. Radio node 10 also comprises radio circuitry 22 providing receiving and transmitting or transceiving functionality (e.g., one or more 430 transmitters and/or receivers and/or transceivers), the radio circuitry 22 being connected or connectable to the processing circuitry. An antenna circuitry 24 of the radio node 10 is connected or connectable to the radio circuitry 22 to collect or send and/or amplify signals. Radio circuitry 22 and the processing circuitry 20 controlling it are configured for cellular communication with a network, e.g. a RAN as described herein, and/or for 435 sidelink communication (which may be within coverage of the cellular network, or out of coverage; and/or may be considered non-cellular communication and/or be associated to a non-cellular wireless communication network). Radio node 10 may generally be adapted to carry out any of the methods of operating a radio node like terminal or UE disclosed herein; in particular, it may comprise corresponding circuitry, e.g. processing 440 circuitry, and/or modules, e.g. software modules. It may be considered that the radio node 10 comprises, and/or is connected or connectable, to a power supply. A DFE may be considered part of radio circuitry; an analog frontend may be associated to radio circuitry and/or antenna circuitry. Figure 2 schematically shows a radio node 100, which may in particular be implemented 445 as a network node 100, for example an eNB or gNB or similar for NR. Radio node 100 comprises processing circuitry (which may also be referred to as control circuitry) 120, which may comprise a controller connected to a memory. Any module, e.g. transmitting module and/or receiving module and/or configuring module of the node 100 may be im- plemented in and/or executable by the processing circuitry 120. The processing circuitry 450 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- nectable to radio circuitry 122 for signal reception or transmittance and/or amplification. Node 100 may be adapted to carry out any of the methods for operating a radio node 455 or network node disclosed herein; in particular, it may comprise corresponding circuitry, e.g. processing circuitry, and/or modules. The antenna circuitry 124 may be connected to and/or comprise an antenna array. The node 100, respectively its circuitry, may be adapted to perform any of the methods of operating a network node or a radio node as described herein; in particular, it may comprise corresponding circuitry, e.g. processing 460 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 with a core network and/or an internet or local net, in particular with an information sys- tem, which may provide information and/or data to be transmitted to a user equipment. A DFE may be considered part of radio circuitry; an analog frontend may be associated 465 to radio circuitry and/or antenna circuitry. In general, the wireless device and/or network node may operate in, and/or the commu- nication signalling may be in TDD operation. It should be noted that the transmission of signalling from transmission sources may be synchronised and simultaneous; a shift in time may occur due to different propagation times, e.g. due to different beams and/or 470 source locations. A data block may refer to a transport block, or a code block or a code block bundle. A 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 which may further include, bits for error detection coding, e.g. CRC. The bits for error 475 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 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. 480 determined based on bits of only one code block. Different bits and/or groups of bits may be associated to different code blocks. Error correction bit/s associated to a code block may be associated to a single code block; this may refer to the error correction bits indicating 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 485 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 be a data block without error correction coding pertaining to more than one code block. 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 490 or more code blocks. It may be considered that a data block may be associated to, and or subject to, and/or correspond to, a, one and/or a single acknowledgement process, e.g. a specific HARQ process, which may correspond to and/or be represented by a HARQ identifier. A code block may correspond to a subpattern of an acknowledgement informa- tion bit pattern. In some cases, a data block may correspond and/or pertain and/or be 495 subject to a plurality of acknowledgement processes, e.g. if there is one acknowledgement process per code block of the data block. A data block may comprise and/or represent information bits, which may be data bits (e.,g., user data) and/or control information bits; the information bits may be associated to one or more data or control channels, e.g. transport channels and/or logical channels, 500 and/or may be mapped to a specific and/or single physical channel, in particular a physical data channel, or in some cases, a physical control channel (in which case it may or may not be associated to a higher layer channel like a transport channel or logical channel). A data block may represent bits intended for transmission, e.g. encapsulating one or more higher layer data packets, e.g. one or more MAC layer data packets, e.g. one or more 505 PDUs (Protocol Data Unit) and/or SDUs (Service Data Unit); error correction bits, e.g. CRC; may be added in physical layer processing. It may be considered that bits of a data block are subject to physical layer processing like coding (e.g., forward error coding 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 510 to modulation symbols, e.g. according to a modulation scheme and/or to a modulation space. The modulation symbols may be represented as a bit sequence until they are subject to analog conversion (or vice versa for reception). 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 515 and/or to control beam switch and/or control beam-forming and/or receive and/or trans- mit 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 back-link and/or IAB scenarios, it may be implemented as network node or network radio node. A network node may in general comprise processing circuitry and/or radio circuitry, 520 in 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 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 node, e.g. a network radio node and/or base station or a relay node or IAB node. How- 525 ever, in some cases, e.g. sidelink scenarios, the second radio node may be implemented as a wireless device or terminal, e.g. a user equipment. In general, an allocation unit or block symbol may represent and/or correspond to an extension in time domain, e.g. a time interval. A block symbol duration or allocation unit duration (the length of the time interval) may correspond to the duration of an OFDM 530 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 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 or allocation unit may comprise a plurality of modulation symbols, e.g. based on a subcarrier spacing and/or 535 numerology or equivalent, in particular for time domain multiplexed types (on the symbol level for a single transmitter) of signalling like single-carrier based signalling, e.g. SC-FDE or 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 subcarrier to be DFTS-spread (for SC-FDMA) and/or be based on a number of FFT samples, e.g. for spreading and/or 540 mapping, and/or equivalent, and/or may be predefined and/or configured or configurable. A block symbol or allocation unit 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 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 545 the block symbol. A block symbol and/or a number of block symbols (an integer smaller than 20, e.g. equal to or smaller than 14 or 7 or 4 or 2 or a flexible number) may be a unit (e.g., allocation unit) 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, there may be associated a frequency range and/or frequency 550 domain allocation and/or bandwidth allocated for transmission. 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, there may be a block symbol associated to a channel that also is associated to a form of reference signalling and/or pilot signalling and/or tracking signalling associated to the 555 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, e.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 560 smallest frequency unit carrying or mapped to (e.g., a subcarrier) in frequency domain 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 a number of modulation symbols, and/or association to one or more channels (and/or the structure may dependent on the channel the block symbol is associated to and/or 565 is allocated or used for), and/or reference signalling (e.g., as discussed above), and/or one or more guard periods and/or transient periods, and/or one or more affixes (e.g., a prefix and/or suffix and/or one or more infixes (entered inside the block symbol)), in particular a cyclic prefix and/or suffix and/or infix. A cyclic affix may represent a repetition of signalling and/or modulation symbol/s used in the block symbol, with 570 possible slight amendments to the signalling structure of the affix to provide a smooth and/or continuous and/or differentiable connection between affix signalling and signalling 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 wave- forms, an affix may be included into a modulation symbol. In other cases, e.g. some 575 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 is defined and/or used in the context of the associated structure. Communicating may comprise transmitting or receiving. It may be considered that com- municating like transmitting signalling is based on a SC-FDM based wave-form, and/or 580 corresponds to a Frequency Domain Filtered (FDF) DFTS-OFDM wave-form. However, the approaches may be applied to a Single Carrier based wave-form, e.g. a SC-FDM or 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 be used interchangeably. Alternatively, or additionally, the signalling (e.g., first signalling 585 and/or second signalling) and/or beam/s (in particular, the first received beam and/or second received beam) may be based on a wave-form with CP or comparable guard time. 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 590 angular 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 de- grees or 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 ex- tended guard interval or switching protection interval may have a duration corresponding 595 to essentially or at least N CP (cyclic prefix) durations or equivalent duration, wherein N may be 2, or 3 or 4. An equivalent to a CP duration may represent the CP duration associated to signalling with CP (e.g., SC-FDM-based or OFDM-based) for a wave-form without CP 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. 600 associated to a first subcarrier or bandwidth, may comprise mapping the modulation symbol (and/or the sample associated to it after FFT) to an associated second subcar- rier 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 subcarrier and the second subcarrier, wherein the shaping operation may be according to a shaping function. 605 Pulse-shaping signalling may comprise pulse-shaping one or more symbols; pulse-shaped signalling may in general comprise at least one pulse-shaped symbol. Pulse-shaping may be performed based on a Nyquist-filter. It may be considered that pulse-shaping is per- formed based on periodically extending a frequency distribution of modulation symbols (and/or associated samples after FFT) over a first number of subcarriers to a larger, 610 second number of subcarriers, wherein a subset of the first number of subcarriers from one end of the frequency distribution is appended at the other end of the first number of subcarriers. 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 subcarrier spacing and/or symbol 615 time length) and/or an SC-FDM based wave-form (including a FDF-DFTS-FDM based wave-form) or a single-carrier based wave-form. Whether to use pulse-shaping or FDF on a SC-FDM or SC-based wave-form may depend on the modulation scheme (e.g., MCS) 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, 620 e.g. transmission beamforming and/or reception beamforming, respectively. It may be considered that a beam is produced by performing analog beamforming to provide the beam, e.g. a beam corresponding to a reference beam. Thus, signalling may be adapted, e.g. based on movement of the communication partner. A beam may for example be pro- duced by performing analog beamforming to provide a beam corresponding to a reference 625 beam. This allows efficient postprocessing of a digitally formed beam, without requiring 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 beam- forming, 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/DCA required 630 for antenna arrangements. It may be considered that a beam is produced by hybrid beamforming, e.g. by analog beamforming performed on a beam representation or beam formed 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. The numerology may determine the length of a symbol time interval and/or the duration 635 of a cyclic prefix. The approaches described herein are particularly suitable to SC-FDM, to ensure orthogonality, in particular subcarrier orthogonality, in corresponding systems, but may be used for other wave-forms. Communicating may comprise utilising a wave- form 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 per- 640 forming cell search, e.g. for a wireless device or terminal, or may comprise transmitting cell identifying signalling and/or a selection indication, based on which a radio node re- ceiving the selection indication may select a signalling bandwidth from a set of signalling bandwidths for performing cell search. A beam or beam pair may in general be targeted at one radio node, or a group of radio 645 nodes and/or an area including one or more radio nodes. In many cases, a beam or beam pair may be receiver-specific (e.g., UE-specific), such that only one radio node is served 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 650 symbols. Some tuning of radio circuitry, e.g. for receiving and/or transmitting, may be performed. Beam pair switching may comprise switching from a second received beam to a first received beam, and/or from a second transmission beam to a first transmission 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; 655 this may in particular be the case when digital reception beamforming is used to switch reception beams for switching received beams. 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 deter- mined, e.g. measured and/or estimated. A signalling beam may comprise signalling like 660 control signalling and/or data signalling and/or reference signalling. A reference beam may be transmitted by a source or transmitting radio node, in which case one or more beam signalling characteristics may be reported to it from a receiver, e.g. a wireless de- vice. However, in some cases it may be received by the radio node from another radio node or wireless device. In this case, one or more beam signalling characteristics may 665 be determined by the radio node. A signalling beam may be a transmission beam, or a reception beam. A set of signalling characteristics may comprise a plurality of subsets of beam signalling characteristics, each subset pertaining to a different reference beam. Thus, a reference beam may be associated to different beam signalling characteristics. A beam signalling characteristic, respectively a set of such characteristics, may represent 670 and/or indicate a signal strength and/or signal quality of a beam and/or a delay charac- teristic and/or be associated with received and/or measured signalling carried on a beam. 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 delay and/or lowest spread/range) timing or delay spread, and/or of strongest and/or 675 best quality beams, e.g. with associated delay spread. A beam signalling characteristic may be based on measurement/s performed on reference signalling carried on the refer- ence 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 and/or gauging of the measurements. In some cases, a beam and/or beam pair may be 680 represented by a beam identity indication, e.g. a beam or beam pair number. Such an in- 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 pair, and/or a signalling characteristic and/or a resource/s used (e.g., time/frequency and/or code) and/or a specific RNTI (e.g., used for scrambling a CRC for some messages 685 or transmissions) and/or by information provided in signalling, e.g. control signalling and/or system signalling, on the beam and/or beam pair, e.g. encoded and/or provided in an information field or as information element in some form of message of signalling, e.g. DCI and/or MAC and/or RRC signalling. A reference beam may in general be one of a set of reference beams, the second set of 690 reference beams being associated to the set of signalling beams. The sets being associated may refer to at least one beam of the first set being associated and/or corresponding to the second set (or vice versa), e.g. being based on it, for example by having the same analog 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 695 beamforming. The set of signalling beams may be referred to as a first set of beams, a set of corresponding reference beams may be referred to as second set of beams. 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 a reference beam or signalling may be transmitted by another radio node. The signalling 700 may indicate which beam is used for transmitting. Alternatively, the reference beams may be beams receiving the random access signalling. Random access signalling may be used 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. The random access signalling may be on a random access channel, e.g. based on broadcast 705 information provided by the radio node (the radio node performing the beam selection), e.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 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 710 for contention resolution, which may be transmitted on a physical uplink shared channel based on a resource allocation provided by the radio node. 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 delay spread, and/or delay distribution, and/or delay spread distribution, and/or delay 715 spread range, and/or relative delay spread, and/or energy (or power) distribution, and/or 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 delay may represent the mean value and/or an averaged value of the delay spread, which may be weighted or unweighted. A distribution may be distribution over time/delay, e.g. 720 of received power and/or energy of a signal. A range may indicate an interval of the delay spread distribution over time/delay, which may cover a predetermined percentage of the delay spread respective received energy or power, e.g. 50% or more, 75% or more, 90% or more, or 100%. A relative delay spread may indicate a relation to a threshold delay, e.g. of the mean delay, and/or a shift relative to an expected and/or configured timing, e.g. a 725 timing at which the signalling would have been expected based on the scheduling, and/or a relation to a cyclic prefix duration (which may be considered on form of a threshold). Energy distribution or power distribution may pertain to the energy or power received over the time interval of the delay spread. A power delay profile may pertain to representations of the received signals, or the received signals energy/power, across time/delay. Power 730 delay profile related parameters may pertain to metrics computed from the power delay profile. Different values and forms of delay spread information and/or report may be 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 735 higher layer signalling like RRC or MAC signalling and/or physical layer signalling like DCI signalling. In general, different beam pair may differ in at least one beam; for example, a beam 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 740 beam. A transmission beam using no precoding and/or beamforming, for example using the natural antenna profile, may be considered as a special form of transmission beam of a transmission beam pair. A beam may be indicated to a radio node by a transmitter with 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 745 mode and/or antenna profile and/or antenna port and/or precoder associated to the beam. Different beams may be provided with different content, for example different received beams may carry different signalling; however, there may be considered cases in which different beams carry the same signalling, for example the same data signalling and/or reference signalling. The beams may be transmitted by the same node and/or 750 transmission point and/or antenna arrangement, or by different nodes and/or transmission points and/or antenna arrangements. 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 a beam, e.g. a beam of a beam pair. The following terms are to be interpreted from 755 the point of view of the referred radio node: a received beam may be a beam carrying signalling received by the radio node (for reception, the radio node may use a reception beam, e.g. directed to the received beam, or be non-beamformed). A transmission beam may be a beam used by the radio node to transmit signalling. A beam pair may consist of a received beam and a transmission beam. The transmission beam and the received 760 beam of a beam pair may be associated to each and/or correspond to each other, e.g. 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 almost stationary condition. It should be noted that the terms “first” and “second” do not necessarily denote an order in time; a second signalling may be received and/or 765 transmitted before, or in some cases simultaneous to, first signalling, or vice versa. The 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 FDD may be considered as well. Different beam pairs may operate on the same frequency ranges or carriers or bandwidth parts (e.g., such that transmission beams operate on 770 the same frequency range or carriers or bandwidth part, and received beams on the same frequency range or carriers or bandwidth part (the transmission beam and received beams may be on the same or different ranges or carriers or BWPs). Communicating utilizing a first beam pair and/or first beam may be based on, and/or comprise, switching from the second beam pair or second beam to the first beam pair or first beam for communicating. 775 The switching may be controlled by the network, for example a network node (which may be the source or transmitter of the received beam of the first beam pair and/or second beam pair, or be associated thereto, for example associated transmission points or nodes 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 780 be performed by the radio node without additional control signalling, for example based on measurements on signal quality and/or signal strength of beam pairs (e.g., of first and second received beams), in particular the first beam pair and/or the second beam pair. For example, it may be switched to the first beam pair (or first beam) if the signal quality or signal strength measured on the second beam pair (or second beam) is considered to 785 be insufficient, and/or worse than corresponding measurements on the first beam pair 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 the timing indication may be determined before switching from the second beam pair to the first beam pair for communicating. Thus, the synchronization may be in place and/or 790 the timing indication may be available for synchronising) when starting communication utilizing the first beam pair or first beam. However, in some cases the timing indication may be determined after switching to the first beam pair or first beam. This may be in particular useful if first signalling is expected to be received after the switching only, for example based on a periodicity or scheduled timing of suitable reference signalling 795 on the first beam pair, e.g. first received beam. In general, a reception beam of a node may be associated to and/or correspond to a transmission beam of the node, e.g. such 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 and/or coincide, in particular for TDD operation and/or independent of frequency. Spatial 800 correspondence between beams may be considered in some cases, e.g. such that a beam pair (e.g., transmission beam of a transmitting node and reception beam of a receiving 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. based on a threshold signal quality and/or signal strength and/or measurements); to each 805 of such beams, there may be an associated or corresponding complementary beam of the 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, there may be associated a transmitting beam of the receiving node; if the beams (e.g., at least essentially or substantially) overlap (e.g., in spatial angle), in some cases a beam 810 pair may be considered to indicate four beams (or actually, two beam pairs). 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 as QCL type) or QCL identity; beams or signal or signallings sharing such may be con- sidered to be Quasi-Colocated. Quasi-Colocated beams or signals or signallings may be 815 considered (e.g., by a receiver) as the same beam or originating from the same transmit- ter or transmission source, at least in regard to the QCL characteristic or set or class or identity, and/or to share the characteristic/s. QCL characteristics may pertain to prop- agation of signalling, and/or one or more delay characteristics, and/or pathloss, and/or signal quality, and/or signal strength, and/or beam direction, and/or beam shape (in 820 particular, angle or area, e.g. area of coverage), and/or Doppler shift, and/or Doppler spread, and/or delay spread, and/or time synchronisation, and/or frequency synchroni- sation, and/or one or more other parameters, e.g. pertaining to a propagation channel and/or spatial RX parameter/s (which may refer to reception beam and/or transmission beam, e.g. shape or coverage or direction). A QCL characteristic may pertain to a spe- 825 cific channel (e.g., physical layer channel like a control channel or data channel) and/or reference signalling type and/or antenna port. Different QCL classes or types may per- tain 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 QCL characteristics beams have to fulfill to be considered Quasi-Colocated according to 830 this class; a QCL identity may refer to and/or represent all beams being quasi-colocated, 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 ranges for one or more characteristics) and/or to different characteristics. A QCL indi- cation may be seen as a form of beam indication, e.g. pertaining to all beams belonging 835 to one QCL class and/or QCL identity and/or quasi-colocated beams. A QCL identity may be indicated by a QCL indication. In some cases, a beam, and/or a beam indication, may be considered to refer and/or represent a to a QCL identity, and/or to represent quasi-colocated beams or signals or signallings. Transmission on multiple layers (multi-layer transmission) may refer to transmission of 840 communication signalling and/or reference signalling simultaneously in one or more beams and/or using a plurality of transmission sources, e.g. controlled by one network node 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 data and/or data streams, e.g., to increase data throughput. In some cases, the same 845 data or data stream may be transported on different layers, e.g. to increase reliability. 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 2 layers; the number of layers of transmission may be represented by a rank or rank indication. 850 A transmission source may in particular comprise, and/or be represented by, and/or associated to, an antenna or group of antenna elements or antenna sub-array or antenna array or transmission point or TRP or TP (Transmission Point) or access point. In some cases, a transmission source may be represented or representable, and/or correspond to, and/or associated to, an antenna port or layer of transmission, e.g. for multi-layer 855 transmission. Different transmission sources may in particular comprise different and/or 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 source, and/or a one or more transmission parameter, in particular of reference signalling 860 associated to the antenna port. In particular, transmission parameters pertaining to, and/or indicating a frequency domain distribution or mapping (e.g., which comb to use and/or which subcarrier or frequency offset to use, or similar) of modulation symbols of the reference signalling, and/or to which cyclic shift to use (e.g., to shift elements of a modulation symbol sequence, or a root sequence, or a sequence based on or derived from 865 the root sequence) and/or to which cover code to use (e.g., (e.g., to shift elements of a modulation symbol sequence, or a root sequence, or a sequence based on or derived 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). In some variants, reference signalling may be and/or comprise CSI-RS and/or PT-RS 870 and/or DMRS, e.g. transmitted by the network node. In other variants, the reference signalling may be transmitted by a UE, e.g. to a network node or other UE, in which case it may comprise and/or be Sounding Reference signalling. Other, e.g. new, forms of reference signalling may be considered and/or used. In general, a modulation symbol of reference signalling respectively a resource element carrying it may be associated to a 875 cyclic prefix. 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. Control signalling may be on a control channel, for example on a common control channel or a PDCCH or PSCCH, and/or comprise one or more DCI messages or SCI messages. 880 Reference signalling may be associated to control signalling and/or data signalling, e.g. DM-RS and/or PT-RS. 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 phase tracking signalling and/or cell-specific reference signalling and/or user-specific sig- 885 nalling, in particular CSI-RS. Reference signalling in general may be signalling with one 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 train- ing and/or for compensation. The receiver can be informed about the reference signalling 890 by the transmitter, e.g. being configured and/or signalling with control signalling, in par- ticular physical layer signalling and/or higher layer signalling (e.g., DCI and/or RRC sig- nalling), 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 895 be adapted for gauging and/or estimating and/or representing transmission conditions, 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., 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 prede- 900 fined and/or configured or configurable and/or being communicated). Different types of reference signalling may be considered, e.g. pertaining to uplink, downlink or sidelink, cell-specific (in particular, cell-wide, e.g., CRS) or device or user specific (addressed to 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 905 (e.g., SRS or pilot signalling) and/or phase-related, etc. 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 slot and/or mini-slot and/or subcarrier and/or carrier may pertain to a specific numerol- ogy, which may be predefined and/or configured or configurable. A transmission timing 910 structure may represent a time interval, which may cover one or more symbols. Some examples of a transmission timing structure are transmission time interval (TTI), sub- frame, 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) 915 smaller than the number of symbols of a slot, in particular 1, 2, 3 or 4, or more symbols, e.g. less symbols than symbols in a slot. A transmission timing structure may cover a time interval of a specific length, which may be dependent on symbol time length and/or cyclic prefix used. A transmission timing structure may pertain to, and/or cover, a specific time interval in a time stream, e.g. synchronized for communication. Timing structures 920 used and/or scheduled for transmission, e.g. slot and/or mini-slots, may be scheduled in relation to, and/or synchronized to, a timing structure provided and/or defined by other transmission timing structures. Such transmission timing structures may define a timing grid, e.g., with symbol time intervals within individual structures representing the small- est timing units. Such a timing grid may for example be defined by slots or subframes 925 (wherein in some cases, subframes may be considered specific variants of slots). A trans- mission timing structure may have a duration (length in time) determined based on the durations of its symbols, possibly in addition to cyclic prefix/es used. The symbols of a transmission timing structure may have the same duration, or may in some variants have different duration. The number of symbols in a transmission timing structure may be 930 predefined and/or configured or configurable, and/or be dependent on numerology. The timing of a mini-slot may generally be configured or configurable, in particular by the network and/or a network node. The timing may be configurable to start and/or end at any symbol of the transmission timing structure, in particular one or more slots. A transmission quality parameter may in general correspond to the number R of retrans- 935 missions and/or number T of total transmissions, and/or coding (e.g., number of coding 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 level (e.g., minimum level and/or target level and/or base power level P0 and/or trans- mission power control command, TPC, step size) and/or signal quality, e.g. SNR and/or 940 SIR and/or SINR and/or power density and/or energy density. A signalling sequence (e.g. of an allocation unit and/or block symbol and/or symbol time interval, and/or carried on an allocation unit and/or block symbol and/or symbol time interval, or more than one), may be based on a sequence root, e.g. a root sequence and/or a root parameter and/or root index and/or seed. A sequence root in general may 945 represent or indicate a base for deriving or determining a signalling sequence; the root may be 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, 950 a sequency root, e. g. based on a code, which may represent a shift or operation or processing 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 phase shift and/or phase ramp (e.g., an amount for such). The code may 955 assign one operation or shift for each allocation unit. In general, a signalling sequence associated to an allocation unit (and/or the allocation units) associated to control signalling (and/or reference signalling) may be based on a 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 960 interference (e.g., self-interference and/or interference with other or neighboring transmit- ters). Different sequences may be used as root sequences for different signalling sequences, or the same sequence may be used. If different sequences are used, they may be of the same 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 965 and/or time-domain M sequences. In some cases, a shifted object like a signalling or signals or sequences or information may be shifted, e.g. relative to a predecessor (e.g., one is subject to a shift, and the 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 970 unit, both may be used). One possible way of shifting is operating a code on it, e.g. to multiply each element of a shifting object with a factor. A ramping (e.g. multiplying with a monotonously increasing or periodic factor) may be considered an example of shifting. 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 975 moving the final element or elements to the first position, while shifting all other entries to the next position, or by performing the inverse operation (such that the shifted object 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 unit in time domain, or a bandwidth in frequency domain. For example, it may be 980 considered that signals or modulation symbols in an allocation unit are shifted, such that 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 signals in the allocation units unshifted with reference to the individual allocation unit, but may change the order of the allocation units. Domains for shifting may for example be 985 time domain and/or phase domain and/or frequency domain. Multiple shifts in the same domain or different domains, and/or the same interval or different intervals (differently sized intervals, for example) may be performed. Reference signalling may have a type. Types of reference signalling may include synchro- nisation signalling, and/or DM-RS (used to facilitate demodulation of associated data 990 signalling and/or control signalling), and/or PT-RS (used to facilitate phase tracking of associated data signalling and/or control signalling, e.g. within a time interval or symbol or allocation unit carrying such signalling), and/or CSI-RS (e.g., used for channel estima- tion and/or reporting). It may be considered that PT-RS are inserted into a bit sequence, or a modulation symbol sequence, which may represent data. For example, PT-RS may 995 be mapped onto subcarriers of a symbol also carrying data symbols. Accordingly, PT-RS 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 (or data bits). A comb structure, or shorter comb, may indicate a distribution, or periodic arrangement 1000 of reference signalling, in particular in frequency space, e.g. between an upper and lower frequency. A comb may pertain to one OFDMA symbol and/or SC-FDMA symbol and/or one (the same) symbol time interval and/or one allocation unit. A comb may have width or size N and/or may pertain to, and/or be associated to, specific signalling and/or a type of signalling, e.g. a type of reference signalling. The width N may indicate how 1005 many empty subcarriers are between (e.g., non-neighbouring) subcarriers carrying an element or signal or symbol of the signalling (e.g., this number may be N-1), or how many empty subcarriers and non-empty subcarriers form a pattern that is repeated in frequency domain. In general, each comb may indicate that at least one empty subcarrier is to be between non-empty subcarriers. In this context, empty may refer to empty regarding 1010 the pattern or distribution of the signalling associated to the comb (and non-empty may refer to a subcarrier carrying an element or symbol of the associated signalling); in some cases, other signallings (which may have a comb structure as well) may be carried on empty subcarriers, 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 1015 on subcarriers not carrying DMRS). A comb structure may generally describe a structure in which for every N-th (N may be an integer) resource element and/or subcarrier a reference signal or an element of a sequence of the reference signalling, and/or representing the reference signalling, and/or on which the reference signalling is based, is mapped to, and/or represented by signalling 1020 the resource element and/or subcarrier, in particular an element (symbol) of a modulation symbol sequence, or an element of a sequence. N may be called the width of the comb. Generally, the comb may indicate the periodicity of the pattern inside the frequency range of the reference signalling. The pattern may in particular pertain to one reference signal and/or resource element or subcarrier for transmitting a reference signal, such that the 1025 comb may be considered to indicate that on every Nth resource element (in particular, only there) and/or subcarrier there is to be a reference signal or element of an associated sequence, and/or how many resource elements and/or subcarriers are between resource elements and/or subcarriers with reference signals. However, there may be considered variants, in which the pattern represents more than one reference signals. The pattern 1030 may also generally represent and/or indicate one or more empty signals and/or one or more data signals (respectively associated resource elements and/or subcarriers). For 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 subcarriers or PRBs (e.g., based on a frequency 1035 domain offset, or a subcarrier offset). A comb structure or comb of width or size 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 C1) and a comb 2 (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 C1 and C2 alternatingly in frequency domain). 1040 A comb may comprise two or more, for example at least three or at least four, repetitions of 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 1045 structure may cover at least part, and/or at least the majority, and/or essentially all or all resource elements and/or subcarriers of the plurality of resource elements and/or subcarriers, and/or the symbol. A comb structure may result from combining two comb structures, which may in particular comb structures with pattern comprising only one reference signal. A comb structure may be determined and/or amended before trans- 1050 mission, e.g. based on other reference signalling to be transmitted, e.g. on a different antenna port. In this context, reference signals may be replaced by empty signals to avoid overlap and/or interference. Generally, if the other reference signalling utilises a comb structure 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 1055 pattern. Alternatively, or additionally, combs may be combined to increase the reference signal density, e.g. by combining combs with different widths, and/or with shifted offsets. Generally, a comb structure may represent and/or comprise and/or be comprised of any of the combs/comb structures described herein. A buffer state report (or buffer status report, BSR) may comprise information represent- 1060 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, one or more logical channel/s and/or transport channel/s and/or groups thereof: The 1065 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 may concatenate and/or combine information of a long BSR, e.g. providing sums for data 1070 available for one or more channels and/or or channels groups and/or buffers, which might be 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. by a network node scheduling or allocating (uplink) resources for the transmitting radio node like a wireless device or UE or IAB node. 1075 There is generally considered a program product comprising instructions adapted for caus- ing processing and/or control circuitry to carry out and/or control any method described herein, in particular when executed on the processing and/or control circuitry. Also, there is considered a carrier medium arrangement carrying and/or storing a program product as described herein. 1080 A carrier medium arrangement may comprise one or more carrier media. Generally, a carrier medium may be accessible and/or readable and/or receivable by processing or control circuitry. Storing data and/or a program product and/or code may be seen as part of carrying data and/or a program product and/or code. A carrier medium generally may comprise a guiding/transporting medium and/or a storage medium. A 1085 guiding/transporting medium may be adapted to carry and/or carry and/or store signals, in particular electromagnetic signals and/or electrical signals and/or magnetic signals and/or optical signals. A carrier medium, in particular a guiding/transporting medium, may be adapted to guide such signals to carry them. A carrier medium, in particular a guiding/transporting medium, may comprise the electromagnetic field, e.g. radio waves 1090 or microwaves, and/or optically transmissive material, e.g. glass fiber, and/or cable. A storage medium may comprise at least one of a memory, which may be volatile or non- volatile, a buffer, a cache, an optical disc, magnetic memory, flash memory, etc. A system comprising one or more radio nodes as described herein, in particular a network node and a user equipment, is described. The system may be a wireless communication 1095 system, and/or provide and/or represent a radio access network. Moreover, there may be generally considered a method of operating an information sys- tem, the method comprising providing information. Alternatively, or additionally, an information system adapted for providing information may be considered. Providing in- formation may comprise providing information for, and/or to, a target system, which 1100 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 informa- tion, 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 1105 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, e.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 for radio transmission and/or for transmission via an air interface and/or utilising a RAN 1110 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 in- formation is provided to the target. Such parameter/s may in particular pertain to the air 1115 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 transmis- sion capacity (e.g., data rate) and/or latency and/or reliability and/or cost, respectively 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 1120 and/or historical information, and/or be provided by a user, for example a user operating 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 the information system that information is to be provided via a RAN, e.g. by selecting from a selection provided by the information system, for example on a user application 1125 or user interface, which may be a web interface. An information system may comprise 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, e.g. a host computer or host computer arrangement and/or server or server arrangement. 1130 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 stream- ing information provision to the user (and/or the target) from another server, which may be connected or connectable to the interaction server and/or be part of the information system or be connected or connectable thereto. The information may be any kind of data, 1135 in particular data intended for a user of for use at a terminal, e.g. video data and/or audio data and/or location data and/or interactive data and/or game-related data and/or en- vironmental 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 informa- tion system may be mapped to, and/or mappable to, and/or be intended for mapping to, 1140 communication or data signalling and/or one or more data channels as described herein (which may be signalling or channel/s of an air interface and/or used within a RAN and/or for radio transmission). It may be considered that the information is formatted based on the target indication and/or target, e.g. regarding data amount and/or data rate and/or data structure and/or timing, which in particular may be pertaining to a 1145 mapping to communication or data signalling and/or a data channel. Mapping informa- tion 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 com- prise different components, which may have different sources, and/or which may indicate 1150 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 informa- tion to be transmitted on an air interface and/or by a RAN as described herein. This may be particularly pertinent since an air interface may be limited in terms of capacity and/or of predictability, and/or potentially be cost sensitive. The format may be selected to be 1155 adapted to the transmission indication, which may in particular indicate that a RAN or radio node as described herein is in the path (which may be the indicated and/or planned 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 ca- ble interfaces) and/or the intermediate system/s (if any), between the information system 1160 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 when a target indication is provided, and/or the information is provided/transferred by 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 1165 packet-based, and/or be mapped, and/or be mappable and/or be intended for mapping, to packets. Alternatively, or additionally, there may be considered a method for oper- ating a target device comprising providing a target indicating to an information system. More alternatively, or additionally, a target device may be considered, the target device being adapted for providing a target indication to an information system. In another ap- 1170 proach, there may be considered a target indication tool adapted for, and/or comprising an indication module for, providing a target indication to an information system. The 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 1175 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 target indicating may be determined and/or provided. Alternatively, or additionally, the 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, 1180 and/or presenting (e.g., on a screen and/or as audio or as other form of indication), infor- mation. The information may be based on received information and/or communication signalling carrying information. Presenting information may comprise processing received information, 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 1185 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 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 1190 generally comprise one or more processing steps, in particular decoding and/or execut- ing 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, 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 1195 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 may make it particularly suitable for use in a RAN (e.g., for a target device like a network node or in particular a UE or terminal). The tool may generally be adapted for use on a target device, like a UE or terminal. Generally, the tool may provide multiple function- 1200 alities, e.g. for providing and/or selecting the target indication, and/or presenting, e.g. video and/or audio, and/or operating on and/or storing received information. Providing 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 tool for a UE. It should be noted that such provided information may be transferred to 1205 the information system via one or more additionally communication interfaces and/or paths and/or connections. The target indication may be a higher-layer indication and/or 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, 1210 e.g. related to or on the user-plane, and/or the information may be mapped on physical layer radio communication signalling, e.g. related to or on the user-plane (in particular, in reverse communication directions). The described approaches allow a target indication 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 1215 represent a selection from a plurality of possible transmission modes or formats, and/or paths, e.g. in terms of data rate and/or packaging and/or size of information to be provided by the information system. In general, a numerology and/or subcarrier spacing may indicate the bandwidth (in fre- quency domain) of a subcarrier of a carrier, and/or the number of subcarriers in a carrier 1220 and/or the numbering of the subcarriers 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 subcarriers in a carrier have the same bandwidth associated to them. The numerology and/or subcarrier spacing may be different between carriers in particular regarding the subcarrier bandwidth. A symbol time length, and/or a time 1225 length of a timing structure pertaining to a carrier may be dependent on the carrier fre- quency, and/or the subcarrier spacing and/or the numerology. In particular, different numerologies may have different symbol time lengths, even on the same carrier. 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 1230 represent signalling, and/or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and/or represented by a message. 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, e.g. representing and/or pertaining to one or more such processes and/or corresponding 1235 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 and/or pertaining to one or more such processes. Signalling associated to a channel may be transmitted such that represents signalling and/or information for that channel, 1240 and/or that the signalling is interpreted by the transmitter and/or receiver to belong to that channel. Such signalling may generally comply with transmission parameters and/or format/s for the channel. An antenna arrangement may comprise one or more antenna elements (radiating ele- ments), which may be combined in antenna arrays. An antenna array or sub-array may 1245 comprise one antenna element, or a plurality of antenna elements, which may be arranged e.g. two dimensionally (for example, a panel) or three dimensionally. It may be considered that each antenna array or sub-array or element is separately controllable, respectively that different antenna arrays are controllable separately from each other. A single an- tenna element/radiator may be considered the smallest example of a sub-array. Examples 1250 of antenna arrays comprise one or more multi-antenna panels or one or more individu- ally controllable antenna elements. An antenna arrangement may comprise a plurality of antenna arrays. It may be considered that an antenna arrangement is associated to a (specific and/or single) radio node, e.g. a configuring or informing or scheduling radio node, e.g. to be controlled or controllable by the radio node. An antenna arrangement 1255 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- tenna 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 by combining one or more independently or separately controllable antenna elements or 1260 sub-arrays. The beams may be provided by analog beamforming, or in some variants by digital beamforming, or by hybrid beamforming combing analog and digital beamforming. The informing radio nodes may be configured with the manner of beam transmission, e.g. by transmitting a corresponding indicator or indication, for example as beam identify in- dication. However, there may be considered cases in which the informing radio node/s are 1265 not configured with such information, and/or operate transparently, not knowing the way of beamforming used. An antenna arrangement may be considered separately control- lable 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 inde- pendent or separate transmit and/or receive unit and/or ADC (analog-Digital-Converter, 1270 alternatively an ADC chain) or DCA (Digital-to-analog Converter, alternatively a DCA 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; 1275 such controlling may be performed after encoding/decoding and7or after modulation sym- bols have been mapped to resource elements. This may be on the level of antenna ar- rangements 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 1280 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 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 1285 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 or more beams. Hybrid forms of beamforming may be considered. A beam may be defined by a spatial and/or angular and/or spatial angular distribution of radiation and/or a spatial angle (also referred to as solid angle) or spatial (solid) angle 1290 distribution into which radiation is transmitted (for transmission beamforming) or from which it is received (for reception beamforming). Reception beamforming may comprise only accepting signals coming in from a reception beam (e.g., using analog beamforming to not receive outside reception beam/s), and/or sorting out signals that do not come in in a reception beam, e.g. in digital postprocessing, e.g. digital beamforming. A 1295 beam may have a solid angle equal to or smaller than 4*pi sr (4*pi correspond to a beam covering all directions), in particular smaller than 2* pi, or pi, or pi/2, or pi/4 or pi/8 or pi/16. In particular for high frequencies, smaller beams may be used. Different beams may have different directions and/or sizes (e.g., solid angle and/or reach). A beam may have a main direction, which may be defined by a main lobe (e.g., center of the 1300 main lobe, e.g. pertaining to signal strength and/or solid angle, which may be averaged and/or weighted to determine the direction), and may have one or more sidelobes. A lobe may generally be defined to have a continuous or contiguous distribution of energy and/or 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 1305 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 a sidelobe still may contribute to transmitted and/or received energy or power. A beam 1310 may be swept and/or switched over time, e.g., such that its (main) direction is changed, but its shape (angular/solid angle distribution) around the main direction is not changed, 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 change of main direction (e.g., such that after each change, the main lobe from before the 1315 change covers at least partly the main lobe after the change, e.g. at least to 50 or 75 or 90 percent). Switching may correspond to switching direction non-continuously, e.g. such that after each change, the main lobe from before the change does not cover the main lobe after the change, e.g. at most to 50 or 25 or 10 percent. Signal strength may be a representation of signal power and/or signal energy, e.g. as 1320 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 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 and/or attrition or other effects influencing a beam or the signalling it carries. Signal 1325 quality may in general be a representation of how well a signal may be received over noise and/or interference. A beam with better signal quality than another beam does 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 over noise/interference or another corresponding quality measure. Signal quality and/or 1330 signal strength may pertain to, and/or may be measured with respect to, a beam, and/or specific 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 signal strength, and/or relative signal strength, e.g. in comparison to a reference signal (strength). 1335 Uplink or sidelink signalling may be OFDMA (Orthogonal Frequency Division Multi- ple Access) or SC-FDMA (Single Carrier Frequency Division Multiple Access) signalling. Downlink signalling may in particular be OFDMA signalling. However, signalling like communication signalling is not limited thereto (Filter-Bank based signalling and/or Single-Carrier based signalling, e.g. SC-FDE signalling, may be considered alternatives). 1340 A radio node may generally be considered a device or node adapted for wireless and/or radio (and/or millimeter wave) frequency communication, and/or for communication util- ising an air interface, e.g. according to a communication standard. A radio node may be a network node, or a user equipment or terminal. A network node may be any radio node of a wireless communication network, e.g. a base station and/or 1345 gNodeB (gNB) and/or eNodeB (eNB) and/or relay node and/or micro/nano/pico/femto 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. The terms user equipment (UE) and terminal may be considered to be interchangeable in the context of this disclosure. A wireless device, user equipment or terminal may rep- 1350 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- 1355 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 sta- tionary. 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. The circuitry and/or circuitries may be packaged, e.g. in a chip housing, and/or may have 1360 one or more physical interfaces to interact with other circuitry and/or for power supply. Such a wireless device may be intended for use in a user equipment or terminal. A radio node may generally comprise processing circuitry and/or radio circuitry. A radio 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 1365 node and/or a core network. Circuitry may comprise integrated circuitry. Processing circuitry may comprise one or more processors and/or controllers (e.g., microcontrollers), and/or ASICs (Application Specific Integrated Circuitry) and/or FPGAs (Field Programmable Gate Array), or sim- ilar. It may be considered that processing circuitry comprises, and/or is (operatively) 1370 connected or connectable to one or more memories or memory arrangements. A mem- ory arrangement may comprise one or more memories. A memory may be adapted to store digital information. Examples for memories comprise volatile and non-volatile memory, and/or Random Access Memory (RAM), and/or Read-Only-Memory (ROM), and/or magnetic and/or optical memory, and/or flash memory, and/or hard disk mem- 1375 ory, and/or EPROM or EEPROM (Erasable Programmable ROM or Electrically Erasable Programmable ROM). Radio circuitry may comprise one or more transmitters and/or receivers and/or transceivers (a transceiver may operate or be operable as transmitter and receiver, and/or may com- prise joint or separated circuitry for receiving and transmitting, e.g. in one package or 1380 housing), and/or may comprise one or more amplifiers and/or oscillators and/or filters, and/or may comprise, and/or be connected or connectable to antenna circuitry and/or one or more antennas and/or antenna arrays. An antenna array may comprise one or 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 1385 of an antenna array. However, in some variants, an RRH may be also be implemented as a network node, depending on the kind of circuitry and/or functionality implemented therein. Communication circuitry may comprise radio circuitry and/or cable circuitry. Commu- nication circuitry generally may comprise one or more interfaces, which may be air inter- 1390 face/s and/or cable interface/s and/or optical interface/s, e.g. laser-based. Interface/s may be in particular packet-based. Cable circuitry and/or a cable interfaces may com- prise, and/or be connected or connectable to, one or more cables (e.g., optical fiber-based and/or wire-based), which may be directly or indirectly (e.g., via one or more intermedi- ate systems and/or interfaces) be connected or connectable to a target, e.g. controlled by 1395 communication circuitry and/or processing circuitry. Any one or all of the modules disclosed herein may be implemented in software and/or firmware and/or hardware. Different modules may be associated to different components of a radio node, e.g. different circuitries or different parts of a circuitry. It may be consid- ered that a module is distributed over different components and/or circuitries. A program 1400 product as described herein may comprise the modules related to a device on which the program product is intended (e.g., a user equipment or network node) to be executed (the execution may be performed on, and/or controlled by the associated circuitry). A wireless communication network may be or comprise a radio access network and/or a backhaul network (e.g. a relay or backhaul network or an IAB network), and/or a 1405 Radio Access Network (RAN) in particular according to a communication standard. A communication standard may in particular a standard according to 3GPP and/or 5G, e.g. according to NR or LTE, in particular LTE Evolution. 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- 1410 work, which may be connected or connectable to a core network. The approaches de- scribed herein are particularly suitable for a 5G network, e.g. LTE Evolution and/or NR (New Radio), respectively successors thereof. A RAN may comprise one or more net- work nodes, and/or one or more terminals, and/or one or more radio nodes. A network node may in particular be a radio node adapted for radio and/or wireless and/or cellular 1415 communication with one or more terminals. A terminal may be any device adapted for radio and/or wireless and/or cellular communication with or within a RAN, e.g. a user equipment (UE) or mobile phone or smartphone or computing device or vehicular com- munication device or device for machine-type-communication (MTC), etc. A terminal may be mobile, or in some cases stationary. A RAN or a wireless communication network 1420 may comprise at least one network node and a UE, or at least two radio nodes. There may be generally considered a wireless communication network or system, e.g. a RAN or RAN system, comprising at least one radio node, and/or at least one network node and at least one terminal. Transmitting in downlink may pertain to transmission from the network or network node 1425 to the terminal. Transmitting in uplink may pertain to transmission from the termi- nal 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 vari- ants, uplink and downlink may also be used to described wireless communication between 1430 network nodes, e.g. for wireless backhaul and/or relay communication and/or (wireless) network communication for example between base stations or similar network nodes, in particular communication terminating at such. It may be considered that backhaul and/or relay communication and/or network communication is implemented as a form of sidelink or uplink communication or similar thereto. 1435 Control information or a control information message or corresponding signalling (con- trol signalling) may be transmitted on a control channel, e.g. a physical control channel, which may be a downlink channel or (or a sidelink channel in some cases, e.g. one UE scheduling another UE). For example, control information/allocation information may be signalled by a network node on PDCCH (Physical Downlink Control Channel) and/or 1440 a PDSCH (Physical Downlink Shared Channel) and/or a HARQ-specific channel. Ac- knowledgement 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 HARQ-specific channel. Multiple channels may apply for multi-component/multi-carrier 1445 indication or signalling. Transmitting acknowledgement signalling may in general be based on and/or in response to subject transmission, and/or to control signalling scheduling subject transmission. Such control signalling and/or subject signalling may be transmitted by a signalling ra- dio node (which may be a network node, and/or a node associated to it, e.g. in a dual 1450 connectivity scenario. Subject transmission and/or subject signalling may be transmis- sion 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 repre- sented by data signalling, e.g. on a PDSCH or PSSCH, or some forms of control signalling, 1455 e.g. on a PDCCH or PSSCH, for example for specific formats. 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- 1460 ing assignment. For example, if a specific format for a scheduling grant (scheduling or allocating the allocated resources) or scheduling assignment (scheduling the subject transmission for acknowledgement signalling) is used or detected, the first or second com- munication resource may be used. Type of allocation may pertain to dynamic allocation (e.g., using DCI/PDCCH) or semi-static allocation (e.g., for a configured grant). Timing 1465 of acknowledgement signalling may pertain to a slot and/or symbol/s the signalling is to be transmitted. Resources used for acknowledgement signalling may pertain to the allo- cated resources. Timing and/or resources associated to a scheduling grant or assignment 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- 1470 mission resource to be used may be based on implicit conditions, requiring low signalling overhead. Scheduling may comprise indicating, e.g. with control signalling like DCI or SCI signalling and/or signalling on a control channel like PDCCH or PSCCH, one or more scheduling opportunities of a configuration intended to carry data signalling or subject signalling. 1475 The configuration may be represented or representable by, and/or correspond to, a table. A scheduling assignment may for example point to an opportunity of the reception allo- cation 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 1480 reception allocation configuration pertains to data signalling, in particular on a physical data channel like PDSCH or PSSCH. In general, the reception allocation configuration 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 and/or refer to and/or indicate a scheduling opportunity of the reception allocation con- 1485 figuration. It may be considered that the reception allocation configuration is configured or configurable with higher-layer signalling, e.g. RRC or MAC layer signalling. The recep- tion allocation configuration may be applied and/or applicable and/or valid for a plurality of transmission timing intervals, e.g. such that for each interval, one or more opportu- nities may be indicated or allocated for data signalling. These approaches allow efficient 1490 and flexible scheduling, which may be semi-static, but may updated or reconfigured on useful timescales in response to changes of operation conditions. Control information, e.g., in a control information message, in this context may in par- ticular be implemented as and/or represented by a scheduling assignment, which may indicate subject transmission for feedback (transmission of acknowledgement signalling), 1495 and/or reporting timing and/or frequency resources and/or code resources. Reporting 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. Subject transmissions may comprise one or more individual transmissions. Scheduling as- signments may comprise one or more scheduling assignments. It should generally be noted 1500 that in a distributed system, subject transmissions, configuration and/or scheduling may be provided by different nodes or devices or transmission points. Different subject trans- missions 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, e.g. in a MIMO scenario, and/or to same or different ports. Generally, subject transmis- 1505 sions may pertain to different HARQ or ARQ processes (or different sub-processes, e.g. in MIMO with different beams/layers associated to the same process identifier, but different sub-process-identifiers like swap bits). A scheduling assignment and/or a HARQ code- book 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 1510 and/or whether to provide code block group level response or not. However, it should be noted that the actual structure used may differ from the target structure, e.g. due to the total size of target structures for a subpattern being larger than the predetermined size. Transmitting acknowledgement signalling, also referred to as transmitting acknowledge- ment information or feedback information or simply as ARQ or HARQ feedback or feed- 1515 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 acknowledge- ment information may be based on, and/or comprise, a structure for acknowledgement information to transmit, e.g. the structure of one or more subpatterns, e.g. based on 1520 which subject transmission is scheduled for an associated subdivision. Transmitting ac- knowledgement information may comprise transmitting corresponding signalling, e.g. at one instance and/or in one message and/or one channel, in particular a physical channel, which may be a control channel. In some cases, the channel may be a shared channel or data channel, e.g. utilising rate-matching of the acknowledgment information. The 1525 acknowledgement information may generally pertain to a plurality of subject transmis- sions, 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 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 1530 control signallings and/or control messages, e.g. in the same or different transmission 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. A codebook may pertain to transmitting acknowledgement information at a single and/or 1535 specific instant, e.g. a single PUCCH or PUSCH transmission, and/or in one message or with jointly encoded and/or modulated acknowledgement information. Generally, ac- knowledgment information may be transmitted together with other control information, e.g. a scheduling request and/or measurement information. Acknowledgement signalling may in some cases comprise, next to acknowledgement in- 1540 formation, other information, e.g. control information, in particular, uplink or sidelink control information, like a scheduling request and/or measurement information, or sim- ilar, and/or error detection and/or correction information, respectively associated bits. The payload size of acknowledgement signalling may represent the number of bits of ac- knowledgement information, and/or in some cases the total number of bits carried by 1545 the acknowledgement signalling, and/or the number of resource elements needed. Ac- knowledgement signalling and/or information may pertain to ARQ and/or HARQ pro- cesses; an ARQ process may provide ACK/NACK (and perhaps additional feedback) feedback, and decoding may be performed on each (re-)transmission separately, with- out soft-buffering/soft-combining intermediate data, whereas HARQ may comprise soft- 1550 buffering/soft-combining of intermediate data of decoding for one or more (re-)transmissions. Subject transmission may be data signalling or control signalling. The transmission may be on a shared or dedicated channel. Data signalling may be on a data channel, for exam- ple 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. Control signalling may be on a control channel, 1555 for example on a common control channel or a PDCCH or PSCCH, and/or comprise one or more DCI messages or SCI messages. In some cases, the subject transmission may com- prise, 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- 1560 ticular CSI-RS. A subject transmission may pertain to one scheduling assignment and/or 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 into another, or even crossing over more than one subdivision. In this case, it may be 1565 considered that the subject transmission is associated to the subdivision it ends in. It may be considered that transmitting acknowledgement information, in particular of ac- knowledgement information, is based on determining whether the subject transmission/s has or have been received correctly, e.g. based on error coding and/or reception quality. Reception quality may for example be based on a determined signal quality. Acknowl- 1570 edgement information may generally be transmitted to a signalling radio node and/or node arrangement and/or to a network and/or network node. Acknowledgement information, or bit/s of a subpattern structure of such information (e.g., an acknowledgement information structure, may represent and/or comprise one or more bits, in particular a pattern of bits. Multiple bits pertaining to a data structure 1575 or substructure or message like a control message may be considered a subpattern. The structure or arrangement of acknowledgement information may indicate the order, and/or meaning, and/or mapping, and/or pattern of bits (or subpatterns of bits) of the infor- mation. 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 1580 messages, e.g. command messages, the acknowledgement information pertains to, and/or which bits or subpattern of bits are associated to which data block structure. In some 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- uration or structure or codebook may indicate to which process/es and/or data stream/s 1585 the information pertains. Generally, the acknowledgement information may comprise one or more subpatterns, each of which may pertain to a data block structure, e.g. a code block or code block group or transport block. A subpattern may be arranged to indicate acknowledgement or non-acknowledgement, or another retransmission state like non-scheduling or non-reception, of the associated data block structure. It may be con- 1590 sidered that a subpattern comprises one bit, or in some cases more than one bit. It should be noted that acknowledgement information may be subjected to significant processing before being transmitted with acknowledgement signalling. Different configurations may indicate different sizes and/or mapping and/or structures and/or pattern. An acknowledgment signalling process (providing acknowledgment information) may be 1595 a HARQ process, and/or be identified by a process identifier, e.g. a HARQ process iden- tifier or sub-identifier. Acknowledgement signalling and/or associated acknowledgement information may be referred to as feedback or acknowledgement feedback. It should be noted that data blocks or structures to which subpatterns may pertain may be intended to carry data (e.g., information and/or systemic and/or coding bits). However, depending 1600 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 subpattern of acknowledgement signalling may comprise padding bits, e.g. if the ac- knowledgement information for a data block requires fewer bits than indicated as size of the subpattern. Such may for example happen if the size is indicated by a unit size larger 1605 than required for the feedback. Acknowledgment information may generally indicate at least ACK or NACK, e.g. per- taining to an acknowledgment signalling process, or an element of a data block structure like a data block, subblock group or subblock, or a message, in particular a control mes- sage. Generally, to an acknowledgment signalling process there may be associated one 1610 specific subpattern and/or a data block structure, for which acknowledgment information may be provided. Acknowledgement information may comprise a plurality of pieces of information, represented in a plurality of ARQ and/or HARQ structures. An acknowledgment signalling process may determine correct or incorrect reception, and/or corresponding acknowledgement information, of a data block like a transport 1615 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 acknowl- edgement signalling process) may pertain to the data block as a whole, and/or to one or more subblocks or subblock groups. A code block may be considered an example of 1620 a subblock, whereas a code block group may be considered an example of a subblock group. Accordingly, the associated subpattern may comprise one or more bits indicating reception status or feedback of the data block, and/or one or more bits indicating recep- tion status or feedback of one or more subblocks or subblock groups. Each subpattern or bit of the subpattern may be associated and/or mapped to a specific data block or 1625 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 subpattern may represent acknowledgement information for the data block as a whole, reducing overhead in comparison to provide acknowledgement information for the sub- blocks or subblock groups. The smallest structure (e.g. subblock/subblock group/data 1630 block) the subpattern provides acknowledgement information for and/or is associated to may be considered its (highest) resolution. In some variants, a subpattern may provide acknowledgment information regarding several elements of a data block structure and/or at different resolution, e.g. to allow more specific error detection. For example, even if a subpattern indicates acknowledgment signalling pertaining to a data block as a whole, 1635 in some variants higher resolution (e.g., subblock or subblock group resolution) may be provided by the subpattern. A subpattern may generally comprise one or more bits indi- cating ACK/NACK for a data block, and/or one or more bits for indicating ACK/NACK for a subblock or subblock group, or for more than one subblock or subblock group. A subblock and/or subblock group may comprise information bits (representing the data 1640 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 one or more error detection bits, which may pertain to, and/or be determined based on, the information bits (for a subblock group, the error detection bit/s may be determined based on the information bits and/or error detection bits and/or error correction bits of the 1645 subblock/s of the subblock group). A data block or substructure like subblock or subblock group may comprise error correction bits, which may in particular be determined based on the information bits and error detection bits of the block or substructure, e.g. utilising an error correction coding scheme, in particular for forward error correction (FEC), e.g. LDPC or polar coding and/or turbo coding. Generally, the error correction coding of a 1650 data block structure (and/or associated bits) may cover and/or pertain to information bits and error detection bits of the structure. A subblock group may represent a combination of one or more code blocks, respectively the corresponding bits. A data block may represent a code block or code block group, or a combination of more than one code block groups. A transport block may be split up in code blocks and/or code block groups, for example 1655 based on the bit size of the information bits of a higher layer data structure provided for error coding and/or size requirements or preferences for error coding, in particular error 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 coding bits described herein, although higher layer error handling information may be 1660 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. In some variants, a subblock like a code block may comprise error correction bits, which may be determined based on the information bit/s and/or error detection bit/s of the 1665 subblock. An error correction coding scheme may be used for determining the error cor- rection bits, e.g. based on LDPC or polar coding or Reed-Mueller coding. In some cases, 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 bits, and error correction bit/s determined based on the information bits and/or error 1670 detection bit/s. It may be considered that in a subblock, e.g. code block, the information 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 com- prise one or more code blocks. In some variants, no additional error detection bits and/or error correction bits are applied, however, it may be considered to apply either or both. A 1675 transport block may comprise one or more code block groups. It may be considered that no additional error detection bits and/or error correction bits are applied to a transport block, however, it may be considered to apply either or both. In some specific variants, the code block group/s comprise no additional layers of error detection or correction cod- ing, and the transport block may comprise only additional error detection coding bits, 1680 but no additional error correction coding. This may particularly be true if the transport block size is larger than the code block size and/or the maximum size for error correction coding. A subpattern 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 subpattern pertains to a subgroup like a 1685 code block group or a data block like a transport block. In such cases, it may indicate 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 non- correct reception if at least one subblock or code block has not been correctly received. It should be noted that a code block may be considered to be correctly received not only if 1690 it actually has been correctly received, but also if it can be correctly reconstructed based on soft-combining and/or the error correction coding. A subpattern/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 may in particular be considered that one (e.g. specific and/or single) subpattern pertains, 1695 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 that in the bit pattern, subpatterns are mapped to acknowledgement signalling processes and/or data blocks or data block structures on a one-to-one basis. In some variants, there may be multiple subpatterns (and/or associated acknowledgment signalling processes) 1700 associated to the same component carrier, e.g. if multiple data streams transmitted on the carrier are subject to acknowledgement signalling processes. A subpattern may comprise one or more bits, the number of which may be considered to represent its size or bit size. Different bit n-tupels (n being 1 or larger) of a subpattern may be associated to different elements of a data block structure (e.g., data block or subblock or subblock 1705 group), and/or represent different resolutions. There may be considered variants in which only one resolution is represented by a bit pattern, e.g. a data block. A bit n-tupel may represent acknowledgement information (also referred to a feedback), in particular ACK or NACK, and optionally, (if n¿1), may represent DTX/DRX or other reception states. ACK/NACK may be represented by one bit, or by more than one bit, e.g. to 1710 improve disambiguity of bit sequences representing ACK or NACK, and/or to improve transmission reliability. The acknowledgement information or feedback information may pertain to a plurality 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 1715 structures, and/or the corresponding blocks and/or signalling, may be scheduled for si- multaneous transmission, e.g. for the same transmission timing structure, in particular within the same slot or subframe, and/or on the same symbol/s. However, alternatives with scheduling for non-simultaneous transmission may be considered. For example, the acknowledgment information may pertain to data blocks scheduled for different trans- 1720 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). Schedul- ing signalling may generally comprise indicating resources, e.g. time and/or frequency resources, for example for receiving or transmitting the scheduled signalling. signalling may generally be considered to represent an electromagnetic wave structure 1725 (e.g., over a time interval and frequency interval), which is intended to convey informa- tion 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 or representing acknowledgement signalling and/or resource requesting information, may 1730 comprise encoding and/or modulating. Encoding and/or modulating may comprise error detection coding and/or forward error correction encoding and/or scrambling. Receiving control signalling may comprise corresponding decoding and/or demodulation. Error de- tection coding may comprise, and/or be based on, parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check). Forward error correction coding may comprise and/or 1735 be based on for example turbo coding and/or Reed-Muller coding, and/or polar coding and/or LDPC coding (Low Density Parity Check). The type of coding used may be based on the channel (e.g., physical channel) the coded signal is associated to. 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- 1740 tion coding and forward error correction. Coded bits may refer to information bits (also called systematic bits) plus coding bits. Communication signalling may comprise, and/or represent, and/or be implemented as, data signalling, and/or user plane signalling. Communication signalling may be associated to a data channel, e.g. a physical downlink channel or physical uplink channel or physical 1745 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 or a dedicated channel. Data signalling may be signalling associated to and/or on a data channel. An indication generally may explicitly and/or implicitly indicate the information it rep- 1750 resents and/or indicates. Implicit indication may for example be based on position and/or resource used for transmission. Explicit indication may for example be based on a parametrisation with one or more parameters, and/or one or more index or indices, and/or one or more bit patterns representing the information. It may in particular be con- sidered that control signalling as described herein, based on the utilised resource sequence, 1755 implicitly indicates the control signalling type. A resource element may generally describe the smallest individually usable and/or en- codable and/or decodable and/or modulatable and/or demodulatable time-frequency re- source, and/or may describe a time-frequency resource covering a symbol time length in time and a subcarrier in frequency. A signal may be allocatable and/or allocated to a 1760 resource element. A subcarrier may be a subband of a carrier, e.g. as defined by a stan- dard. A carrier may define a frequency and/or frequency band for transmission and/or reception. In some variants, a signal (jointly encoded/modulated) may cover more than one resource elements. A resource element may generally be as defined by a correspond- ing standard, e.g. NR or LTE. As symbol time length and/or subcarrier spacing (and/or 1765 numerology) may be different between different symbols and/or subcarriers, different re- source elements may have different extension (length/width) in time and/or frequency domain, in particular resource elements pertaining to different carriers. 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- 1770 mitted and/or received, and/or be intended for transmission and/or reception. 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 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 1775 particular a physical uplink shared channel (like PUSCH) or a sidelink data or shared channel, or a physical uplink control channel (like PUCCH) or a sidelink control channel. If the starting symbol is associated to control 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 1780 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 or user equipment. Such downlink signalling may in particular be data signalling, e.g. on a physical downlink channel like a shared channel, e.g. a PDSCH (Physical Downlink Shared Channel). A starting symbol may be determined based on, and/or in relation to, 1785 such an ending symbol. Configuring a radio node, in particular a terminal or user equipment, may refer to the 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 1790 case it may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and/or comprise one or more instruction pertaining to a configuration, e.g. a configuration for transmitting and/or receiving on allocated resources, in particular frequency resources. A radio node may configure itself, e.g., based on configuration data received from a network or network 1795 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. Configuration data may comprise and/or be represented by configuration information, and/or one or more corresponding indications and/or message/s Generally, configuring may include determining configuration data representing the con- 1800 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 may be repeated until it reaches the wireless device). Alternatively, or additionally, con- figuring 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 1805 like a network node, which may be a higher-level node of the network, and/or transmitting received configuration data to the radio node. Accordingly, determining a configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities, which may be able to communicate via a suitable interface, e.g., an X2 interface in the case of LTE or a corresponding interface for NR. Configuring a 1810 terminal may comprise scheduling downlink and/or uplink transmissions for the terminal, e.g. downlink data and/or downlink control signalling and/or DCI and/or uplink control or data or communication signalling, in particular acknowledgement signalling, and/or configuring resources and/or a resource pool therefor. A resource structure may be considered to be neighboured in frequency domain by an- 1815 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 ex- ample be represented by the upper end of a bandwidth assigned to a subcarrier n, which also represents the lower end of a bandwidth assigned to a subcarrier n+1. A resource structure may be considered to be neighboured in time domain by another resource struc- 1820 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, which also represents the beginning of a symbol time interval assigned to a symbol n+1. Generally, a resource structure being neighboured by another resource structure in a 1825 domain may also be referred to as abutting and/or bordering the other resource structure in the domain. A resource structure may general represent a structure in time and/or frequency domain, in particular representing a time interval and a frequency interval. A resource structure may comprise and/or be comprised of resource elements, and/or the time interval of a 1830 resource structure may comprise and/or be comprised of symbol time interval/s, and/or the frequency interval of a resource structure may comprise and/or be comprised of sub- carrier/s. A resource element may be considered an example for a resource structure, a slot or mini-slot or a Physical Resource Block (PRB) or parts thereof may be considered others. A resource structure may be associated to a specific channel, e.g. a PUSCH or 1835 PUCCH, in particular resource structure smaller than a slot or PRB. Examples of a resource structure in frequency domain comprise a bandwidth or band, or a bandwidth part. A bandwidth part may be a part of a bandwidth available for a radio node for communicating, e.g. due to circuitry and/or configuration and/or regulations and/or a standard. A bandwidth part may be configured or configurable to a radio 1840 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 part may be smaller than the bandwidth (which may be a device bandwidth defined by 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 1845 or resource block groups, in particular one or more PRBs or PRB groups. A bandwidth part may pertain to, and/or comprise, one or more carriers. 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 com- prises a plurality of subcarriers. A carrier may have assigned to it a central frequency or 1850 center frequency interval, e.g. represented by one or more subcarriers (to each subcarrier there may be generally assigned a frequency bandwidth or interval). Different carriers may be non-overlapping, and/or may be neighbouring in frequency domain. 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 1855 millimeter waves, in particular above one of the thresholds 10 GHz or 20 GHz or 50 GHz or 52 GHz or 52.6 GHz or 60 GHz or 72 GHz or 100 GHz or 114 GHz. Such communication 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 larger than the one representing the lower frequency boundary. 1860 A radio node, in particular a network node or a terminal, may generally be any device adapted for transmitting and/or receiving radio and/or wireless signals and/or data, in particular communication data, in particular on at least one carrier. The at least one carrier may comprise a carrier accessed based on an LBT procedure (which may be called LBT carrier), e.g., an unlicensed carrier. It may be considered that the carrier is part of 1865 a carrier aggregate. Receiving or transmitting on a cell or carrier may refer to receiving or transmitting utiliz- ing 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 car- rier for UL communication/transmission (called UL carrier) and at least one carrier for 1870 DL communication/transmission (called DL carrier). It may be considered that a cell comprises different numbers of UL carriers and DL carriers. Alternatively, or addition- ally, a cell may comprise at least one carrier for UL communication/transmission and DL communication/transmission, e.g., in TDD-based approaches. System information signalling may comprise and/or represent signalling indicating one or 1875 more system parameters, in particular timing and/or synchronisation, and/or numerol- 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 multi- cast signalling; it may be beam-formed signalling, or non-beam-formed. In some cases, system information signalling may comprise synchronisation signalling, e.g. PSS and/or 1880 SSS, and/or reference signalling, e.g. DM-RS, and/or data signalling, e.g. on a broad- cast channel like PBCH, or on a data channel like PDSCH, e.g. suitable for broadcast 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 detec- tion coding and/or error correction coding. System information signalling may comprise 1885 System Information, e.g. a Master Information Block (MIB) and/or one or more System Information Blocks (SIB). A channel may generally be a logical, transport or physical channel. A channel may com- prise 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 may be con- 1890 sidered a control channel, in particular if it is a physical layer channel and/or if it carries control plane information. Analogously, a channel carrying and/or for carrying data sig- nalling/user information may be considered a data channel, in particular if it is 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 1895 (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 channel for Ultra-Reliable Low Latency Communication (URLLC), which may be for control and/or data. 1900 In general, a symbol may represent and/or be associated to a symbol time length, which may be dependent on the carrier and/or subcarrier spacing and/or numerology of the associated carrier. Accordingly, a symbol may be considered to indicate a time interval having a symbol time length in relation to frequency domain. A symbol time length may be dependent on a carrier frequency and/or bandwidth and/or numerology and/or 1905 subcarrier spacing of, or associated to, a symbol. Accordingly, different symbols may have different symbol time lengths. In particular, numerologies with different subcarrier spacings may have different symbol time length. Generally, a symbol time length may be based on, and/or include, a guard time interval or cyclic extension, e.g. prefix or postfix. A sidelink may generally represent a communication channel (or channel structure) be- 1910 tween two UEs and/or terminals, in which data is transmitted between the participants (UEs and/or terminals) via the communication channel, e.g. directly and/or without being relayed via a network node. A sidelink may be established only and/or directly via air interface/s of the participant, which may be directly linked via the sidelink commu- nication channel. In some variants, sidelink communication may be performed without 1915 interaction by a network node, e.g. on fixedly defined resources and/or on resources ne- gotiated between the participants. Alternatively, or additionally, it may be considered that a network node provides some control functionality, e.g. by configuring resources, in particular one or more resource pool/s, for sidelink communication, and/or monitoring a sidelink, e.g. for charging purposes. 1920 Sidelink communication may also be referred to as device-to-device (D2D) communication, and/or in some cases as ProSe (Proximity Services) communication, e.g. in the context of LTE. A sidelink may be implemented in the context of V2x communication (Vehicular communication), e.g. V2V (Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure) and/or V2P (Vehicle-to-Person). Any device adapted for sidelink communication may be consid- 1925 ered a user equipment or terminal. A sidelink communication channel (or structure) may comprise one or more (e.g., physical or logical) channels, e.g. a PSCCH (Physical Sidelink Control CHannel, which may for example carry control information like an acknowledgement position indication, and/or a PSSCH (Physical Sidelink Shared CHannel, which for example may carry data and/or 1930 acknowledgement signalling). It may be considered that a sidelink communication channel (or structure) pertains to and/or used one or more carrier/s and/or frequency range/s associated to, and/or being used by, cellular communication, e.g. according to a specific license and/or standard. Participants may share a (physical) channel and/or resources, in particular in frequency domain and/or related to a frequency resource like a carrier) 1935 of a sidelink, such that two or more participants transmit thereon, e.g. simultaneously, and/or time-shifted, and/or there may be associated specific channels and/or resources to specific participants, so that for example only one participant transmits on a specific channel or on a specific resource or specific resources, e.g., in frequency domain and/or related to one or more carriers or subcarriers. 1940 A sidelink may comply with, and/or be implemented according to, a specific standard, 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 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 1945 radio circuitry and/or processing circuitry, is adapted for utilising a sidelink, e.g. on one or more frequency ranges and/or carriers and/or in one or more formats, in particular according to a specific standard. It may be generally considered that a Radio Access Network is defined by two participants of a sidelink communication. Alternatively, or additionally, a Radio Access Network may be represented, and/or defined with, and/or 1950 be related to a network node and/or communication with such a node. Communication or communicating may generally comprise transmitting and/or receiv- ing signalling. Communication on a sidelink (or sidelink signalling) may comprise util- ising the sidelink for communication (respectively, for signalling). Sidelink transmission and/or transmitting on a sidelink may be considered to comprise transmission utilising the 1955 sidelink, e.g. associated resources and/or transmission formats and/or circuitry and/or the air interface. Sidelink reception and/or receiving on a sidelink may be considered to comprise reception utilising the sidelink, e.g. associated resources and/or transmis- sion formats and/or circuitry and/or the air interface. Sidelink control information (e.g., SCI) may generally be considered to comprise control information transmitted utilising a 1960 sidelink. Generally, carrier aggregation (CA) may refer to the concept of a radio connection and/or communication link between a wireless and/or cellular communication network and/or network node and a terminal or on a sidelink comprising a plurality of carriers for at least one direction of transmission (e.g. DL and/or UL), as well as to the aggregate of carriers. 1965 A corresponding communication link may be referred to as carrier aggregated communi- cation link or CA communication link; carriers in a carrier aggregate may be referred to as component carriers (CC). In such a link, data may be transmitted over more than one of the carriers and/or all the carriers of the carrier aggregation (the aggregate of carri- ers). A carrier aggregation may comprise one (or more) dedicated control carriers and/or 1970 primary carriers (which may e.g. be referred to as primary component carrier or PCC), over which control information may be transmitted, wherein the control information may refer to the primary carrier and other carriers, which may be referred to as secondary carriers (or secondary component carrier, SCC). However, in some approaches, control information may be sent over more than one carrier of an aggregate, e.g. one or more 1975 PCCs and one PCC and one or more SCCs. A transmission may generally pertain to a specific channel and/or specific resources, in particular with a starting symbol and ending symbol in time, covering the interval therebetween. A scheduled transmission may be a transmission scheduled and/or expected and/or for which resources are scheduled or provided or reserved. However, not every 1980 scheduled transmission has to be realized. For example, a scheduled downlink transmission may not be received, or a scheduled uplink transmission may not be transmitted due to power limitations, or other influences (e.g., a channel on an unlicensed carrier being occupied). A transmission may be scheduled for a transmission timing substructure (e.g., a mini-slot, and/or covering only a part of a transmission timing structure) within a 1985 transmission timing structure like a slot. A border symbol may be indicative of a symbol in the transmission timing structure at which the transmission starts or ends. Predefined in the context of this disclosure may refer to the related information being defined for example in a standard, and/or being available without specific configuration from a network or network node, e.g. stored in memory, for example independent of being 1990 configured. Configured or configurable may be considered to pertain to the corresponding information being set/configured, e.g. by the network or a network node. A configuration or schedule, like a mini-slot configuration and/or structure configuration, may schedule transmissions, e.g. for the time/transmissions it is valid, and/or transmis- sions may be scheduled by separate signalling or separate configuration, e.g. separate RRC 1995 signalling 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 of a communication the device is. It should be noted that downlink control information or specifically DCI signalling may be considered physical layer signalling, in contrast to 2000 higher layer signalling like MAC (Medium Access Control) signalling or RRC layer sig- nalling. 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 signalling having to be passed on through several layers, each layer requiring processing and handling. 2005 A scheduled transmission, and/or transmission timing structure like a mini-slot or slot, may pertain to a specific channel, in particular a physical uplink shared channel, a physical uplink control channel, or a physical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and/or may pertain to a specific cell and/or carrier aggregation. A correspond- ing configuration, e.g. scheduling configuration or symbol configuration may pertain to 2010 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 phys- ical channel, for example a physical uplink shared channel or physical downlink shared channel. For such channels, semi-persistent configuring may be particularly suitable. Generally, a configuration may be a configuration indicating timing, and/or be represented 2015 or configured with corresponding configuration data. A configuration may be embedded in, and/or comprised in, a message or configuration or corresponding data, which may indicate and/or schedule resources, in particular semi-persistently and/or semi-statically. 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 2020 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-specific) dedicated signalling (which may be single-cast, for example addressed to or intended for a specific UE), e.g. on a PDCCH, or RRC signalling, or on a multicast or broadcast channel. 2025 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. 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 2030 identifiers, and/or be represented and/or associated to a CORESET and/or a search space. The duration of a symbol (symbol time length or interval) of the transmission timing structure may generally be dependent on a numerology and/or carrier, wherein the nu- merology and/or carrier may be configurable. The numerology may be the numerology 2035 to be used for the scheduled transmission. 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 ref- erence may be interpreted to refer to the time domain projection or time interval or time 2040 component or duration or length in time of the symbol, unless it is clear from the context that the frequency domain component also has to be considered. Examples of transmis- sion timing structures include slot, subframe, mini-slot (which also may be considered a substructure of a slot), slot aggregation (which may comprise a plurality of slots and may be considered a superstructure of a slot), respectively their time domain component. A 2045 transmission timing structure may generally comprise a plurality of symbols defining the time domain extension (e.g., interval or length or duration) of the transmission timing structure, and arranged neighbouring to each other in a numbered sequence. A timing structure (which may also be considered or implemented as synchronisation structure) may be defined by a succession of such transmission timing structures, which may for 2050 example define a timing grid with symbols representing the smallest grid structures. A transmission timing structure, and/or a border symbol or a scheduled transmission may be determined or scheduled in relation to such a timing grid. A transmission timing structure of reception may be the transmission timing structure in which the scheduling control signalling is received, e.g. in relation to the timing grid. A transmission timing 2055 structure may in particular be a slot or subframe or in some cases, a mini-slot. 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 Con- trol Information) signalling. Feedback signalling may in particular comprise and/or rep- resent acknowledgement signalling and/or acknowledgement information and/or measure- 2060 ment reporting. Signalling utilising, and/or on and/or associated to, resources or a resource structure may 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- 2065 sociated to one or more different channels and/or types of signalling and/or comprise 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 gener- ally 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 2070 rectangle filled with one or more resource elements in time/frequency space. However, in some cases, a resource structure or substructure, in particular a frequency resource range, may represent a non-continuous pattern of resources in one or more domains, e.g. time and/or frequency. The resource elements of a substructure may be scheduled for associated signalling. 2075 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.). 2080 In the context of this disclosure, there may be distinguished between dynamically sched- uled 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 configuration/transmission valid and/or scheduled and/or configured for (relatively) short timescales and/or a (e.g., predefined and/or configured and/or lim- 2085 ited and/or definite) number of occurrences and/or transmission timing structures, e.g. one or more transmission timing structures like slots or slot aggregations, and/or for one or more (e.g., specific number) of transmission/occurrences. Dynamic configuration may be based on low-level signalling, e.g. control signalling on the physical layer and/or MAC layer, in particular in the form of DCI or SCI. Periodic/semi-static may pertain to longer 2090 timescales, 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. 2095 In this disclosure, for purposes of explanation and not limitation, specific details are set 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 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. 2100 For example, the concepts and variants are partially described in the context of Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or New Radio mobile or wireless com- munications technologies; however, this does not rule out the use of the present concepts and aspects in connection with additional or alternative mobile communication technolo- gies such as the Global System for Mobile Communications (GSM) or IEEE standards as 2105 IEEE 802.11ad or IEEE 802.11 ay. While described variants may pertain to certain Tech- nical 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. Moreover, those skilled in the art will appreciate that the services, functions and steps 2110 explained herein may be implemented using software functioning in conjunction with a programmed microprocessor, or using an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA) or general purpose computer. It will also be appreciated that while the variants described herein are elucidated in the context of methods and devices, the concepts and aspects presented 2115 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. It is believed that the advantages of the aspects and variants presented herein will be fully 2120 understood from the foregoing description, and it will be apparent that various changes 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 many ways. 2125

Some useful abbreviations comprise Abbreviation Explanation ABF Analog beamformer, fanout to antenna+beamforming ACK/NACK Acknowledgment/Negative Acknowledgement Ant Antenna ARQ Automatic Repeat reQuest BB BaseBand Beamindex IF beamindex interface BER Bit Error Rate BI Beam Index BLER Block Error Rate BPSK Binary Phase Shift Keying BWP BandWidth Part CAZAC Constant Amplitude Zero Cross Correlation CB Code Block CBB Code Block Bundle CBG Code Block Group CDM Code Division Multiplex CM Cubic Metric Comm RXBB communication receiver baseband CORESET Control Resource Set CP Cyclic Prefix CP rem CP removal CQI Channel Quality Information CRC Cyclic Redundancy Check CRS Common reference signal CSI Channel State Information CSI-RS Channel state information reference signal DAI Downlink Assignment Indicator DCI Downlink Control Information DFE Digital Frontend DFT Discrete Fourier Transform DFTS-FDM DFT-spread-FDM DM(-)RS Demodulation reference signal(ing) eMBB enhanced Mobile BroadBand FDD Frequency Division Duplex FDE Frequency Domain Equalisation FDF Frequency Domain Filtering FDM Frequency Division Multiplex FFT Fast Fourier Transform GPIO General Purpose Input Output HARQ Hybrid Automatic Repeat Request IAB Integrated Access and Backhaul IFFT Inverse Fast Fourier Transform Im Imaginary part, e.g. for pi/2*BPSK modulation IR Impulse Response ISI Inter Symbol Interference JCAS Joint Communication and Sensing MBB Mobile Broadband MCS Modulation and Coding Scheme MIMO Multiple-input-multiple-output MRC Maximum-ratio combining MRT Maximum-ratio transmission MU-MIMO Multiuser multiple-input-multiple-output OFDM/A Orthogonal Frequency Division Multiplex/Multiple Access PAPR Peak to Average Power Ratio PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PRACH Physical Random Access CHannel PRB Physical Resource Block PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel (P)SCCH (Physical) Sidelink Control Channel PSS Primary Synchronisation Signal(ing) PT-RS Phase Tracking Reference signalling (P)SSCH (Physical) Sidelink Shared Channel QAM Quadrature Amplitude Modulation OCC Orthogonal Cover Code QPSK Quadrature Phase Shift Keying PSD Power Spectral Density RAN Radio Access Network RAT Radio Access Technology RB Resource Block RE Resource Element Re Real part (e.g., for pi/2*BPSK) modulation RF Radio Frequency RNTI Radio Network Temporary Identifier RRC Radio Resource Control RX Receiver, Reception, Reception-related/side SA Scheduling Assignment SC-FDE Single Carrier Frequency Domain Equalisation SC-FDM/A Single Carrier Frequency Division Multiplex/Multiple Access SCI Sidelink Control Information SINR Signal-to-interference-plus-noise ratio SIR Signal-to-interference ratio SNR Signal-to-noise-ratio SPI Serial to Parallel Interface SR Scheduling Request SRS Sounding Reference Signal(ing) SSS Secondary Synchronisation Signal(ing) SVD Singular-value decomposition TB Transport Block TDD Time Division Duplex TDM Time Division Multiplex T-RS Tracking Reference signalling or Timing Reference signalling TX Transmitter, Transmission, Transmission-related/side UCI Uplink Control Information UDC Up-Down Converter, mixing from BB¡-¿RF UE User Equipment URLLC Ultra Low Latency High Reliability Communication VL-MIMO Very-large multiple-input-multiple-output WD Wireless Device Wfg Waveform Generator ZC Zadoff-Chu ZF Zero Forcing ZP Zero-Power, e.g. muted CSI-RS symbol Abbreviations may be considered to follow 3GPP usage if applicable.

Claims

CLAIMS 1. Method of operating a radio node (10, 100) in a wireless communication network, the 2130 method comprising processing at least one data block for communication signalling, the at least one data block being processed based on mapping bit sequences of input data into different memory spaces of the radio node (10, 100), wherein each bit sequence has a size of NST, wherein into each memory space, one or more bit sequences are mapped, wherein the at least one data block represents and/or comprises an integer number NDB 2135 of bits, wherein NDB = I ×NST , wherein I is an integer of 1 or larger, and NST is an integer number of bits comprised in a unit of digital information.

2. Radio node (10, 100) for a wireless communication network, the radio node being adapted for processing at least one data block for communication signalling, the data block being processed based on mapping bit sequences of a data block into different 2140 memory spaces of the radio node (10, 100), wherein each bit sequence has a size of NST, wherein into each memory space, one or more bit sequences are mapped, wherein the at least one data block represents and/or comprises an integer number NDB of bits, wherein NDB = I ×NST , wherein I is an integer of 1 or larger, and NST is an integer number of bits comprised in a unit of digital information. 2145

3. Method or device according to one of the preceding claims, wherein processing com- prises modulation of the data block, e.g., based on the mapping, or the mapping is based on demodulation of the data block.

4. Method or device according to one of the preceding claims, wherein the bit sequences are sequential in the data block. 2150

5. Method or device according to one of the preceding claims, wherein, based on the mapping, no memory space comprises bits from more than one data block and/or bit sequence.

6. Method or device according to one of the preceding claims, wherein the memory space corresponds to one memory address, and/or memory cell, and/or accommodates exactly 2155 the one or more bit sequences mapped to it, and/or corresponds in size to the size of the unit of digital information.

7. Method or device according to one of the preceding claims, wherein the bits of a data block comprise information bits and coding bits.

8. Method or device according to one of the preceding claims, wherein a data block 2160 represents rate-matched and/or coded information.

9. Method or device according to one of the preceding claims, wherein the communication signalling comprises and/or represents data signalling.

10. Method or device according to one of the preceding claims, wherein the communication signalling comprises multiple data blocks, wherein different datablocks of the multiple data 2165 blocks may comprise different number of bits.

11. Method or device according to one of the preceding claims, wherein communicating is based on mapping the NDB bits into separate memory spaces of the radio node, such that each memory space contains at least on unit of digital information.

12. Method or device according to one of the preceding claims, wherein the at least one 2170 data block represents a transport block, or code block, or code block bundle.

13. Method or device according to one of the preceding claims, wherein NBD is from a set of numbers, the set comprising a plurality of numbers that are integer multiples of NST.

14. Program product comprising instructions causing processing circuitry to control 2175 and/or perform a method according to one of claims 1, or 3 to 13.

15. Carrier medium arrangement carrying and/or storing a program product according to claim 14.