Reference signalling for wireless communication

Abstract

There is disclosed method of operating a receiver radio node (100) in a wireless communication network, the receiver radio node (100) being adapted for receiving signalling based on at least one Machine Learning, ML, model, the method comprising performing signalling operation based on received monitoring signalling. The disclosure also pertains to related devices and methods.

Description

[0001] Reference signalling for wireless communication

[0002] Technical field

[0003] This disclosure pertains to wireless communication technology, in particular in the context of managing wireless communication utilising artificial intelligence-related techniques.

[0004] Background

[0005] For future wireless communication systems, increased use of artificial intelligence is envisaged, e.g., for physical layer operation, or higher layer operation. Approaches to manage Al and / or Al controlled network operation are desirable.

[0006] Summary

[0007] It is an object of this disclosure to provide improved approaches of Al in the context of wireless communication.

[0008] The approaches are particularly suitable 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 millimeter waves. The carrier frequency / ies 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 71 GHz or 72GHz or above, and / or 100 GHz or above, and / or 140 GHz or above. The carrier frequency may in particular refer to a center frequency or maximum frequency of the carrier. The radio nodes and / or network described herein may operate in wideband, e.g. with a carrier bandwidth of 1 GHz or more, or 2 GHz or more, or even larger, e.g. up to 8 GHz; the scheduled or allocated bandwidth may be the carrier bandwidth, or be smaller, e.g. depending on channel and / or procedure. In some cases, operation may be based on an OFDM waveform or a SC-FDM waveform (e.g., downlink and / or uplink), in particular a FDF-SC-FDM-based waveform. However, operation based on a single carrier waveform, 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 waveforms 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 equivalent thereof, e.g., in comparison to an OFDM based system. A subcarrier spacing or equivalent frequency interval may for example correspond to 960kHZ, or 1920 kHz, e.g. representing the bandwidth of a subcarrier or equivalent.

[0009] The approaches are particularly advantageously implemented in a future 6thGeneration (6G) telecommunication network or 6G radio access technology or network (RAT / RAN), in particular according to 3GPP (3rdGeneration 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.

[0010] There is disclosed a method of operating a receiver radio node in a wireless communication network. The receiver radio node is adapted for receiving signalling based on at least one Machine Learning, ML, model, the method comprising performing signalling operation based on received monitoring signalling.

[0011] Also, a receiver radio node for a wireless communication network is considered. The receiver radio node is adapted for receiving signalling based on at least one Machine Learning, ML, model, and further is adapted for performing signalling operation based on received monitoring signalling.

[0012] A radio node being adapted for receiving signalling based on at least one ML model may be considered to refer to the radio node being capable of activating and / or deactivating and / or switching to at least on ML model for at least one function and / or action during reception of signalling and / or as receiver component or function. For example, a ML model may be used for demapping and / or decoding and / or demodulation. Different models may be available for the same functionality, e.g., to be switched between, and / or to be run in parallel (e.g., for monitoring, such that a suitable model may be used for operation). The ML model may be pre-trained, and / or may be trainable. The ML model may be a DPoD model, and / or may be adapted for operating based on intentional signal distortion and / or PA non-linearity (which may be a form of DPoD). A receiver radio node may be adapted for operating in one or more modes, e.g., receiver modes; the modes may be operated in parallel (e.g., for monitoring), or individually; this may depend on hardware and / or software capability of the receiver.

[0013] A method of operating a transmitter radio node in a wireless communication network is proposed. The method comprises transmitting monitoring signalling based on a monitoring configuration.

[0014] Furthermore, a transmitter radio node for a wireless communication network is described. The transmitter radio node is adapted for transmitting monitoring signalling based on a monitoring configuration.

[0015] Approaches described herein may facilitate improved communication, with monitoring of ML model performance.

[0016] The monitoring signalling may be transmitted for monitoring at least one ML model, e.g., used for receiving the signalling, and / or used for transmitting the signalling. The monitoring configuration may pertain to at least on ML model; different configurations may be considered, wherein different monitoring configurations may be associated to, and / or pertain, to different models and / or modes. The monitoring signalling in particular may be radio signalling.

[0017] A monitoring configuration may in general be configured or configurable to a transmitter radio node by a receiver radio node, e.g., using configuration signalling, which may be higher layer signalling, e.g., RRC layer signalling and / or MAC layer signalling. Lower layer signalling, and / or physical layer signalling, e.g., DCI signalling, may be utilised to indicate and / or trigger use or activation of a configuration, and / or its deactivation. Configurations signalling and / or such lower layer signalling or physical layer signalling may be transmitted by the network, e.g., one or more network nodes

[0018] 105 and / or receivers.

[0019] Signalling operation may be performed based on monitoring the monitoring signalling and / or monitoring reception of the monitoring signalling. In particular, a model may be monitored. Monitoring may comprise performing measurements based on the no monitoring signalling and / or the ML model, and / or may comprise determining one or more KPIs and / or reception parameters. It may be considered that monitoring comprises comparing one or more parameters, e.g., with target values, and / or between different modes.

[0020] 115 Signalling operation may for example comprise switching a ML model, or activating or deactivating a ML model, and / or adapting transmission and / or reception and / or a receiver, and / or initiating re-training of the ML model.

[0021] A transmitter radio node may be also referred to as a transmitting radio node or as

[0022] 120 transmitter. It may for example be implemented as a wireless device or UE or terminal, or in some cases a network node or BS or gNB or similar. A receiver radio node may also be referred to as receiving radio node or receiver. It may for example be implemented as a network node or BS or gNB, or in some cases a wireless device (WD) or UE or terminal.

[0023] 125

[0024] A transmitting radio node may comprise, and / or be adapted to utilise, processing circuitry and / or radio circuitry, in particular a transmitter and / or transceiver, to process (e.g., trigger and / or schedule) and / or transmit control signalling and / or reference signalling. The transmitting radio node may in particular be a network node or base

[0025] 130 station, and / or a network radio node; it may be implemented as an IAB or relay node. However, in some cases, e.g. a sidelink scenario, it may be a wireless device. The receiving radio node may comprise, and / or be adapted to utilise, processing circuitry and / or radio circuitry, in particular a receiver and / or transmitter and / or transceiver, to receive and / or process (e.g. receive and / or demodulate and / or decode and / or perform

[0026] 135 blind detection and / or schedule or trigger such) reference signalling and / or control signalling. Receiving may comprise demodulating and / or decoding the signalling, e.g. based on associated reference signalling, in particular DMRS and / or tracking reference signalling, based on which timing and / or channel estimation may be performed. The receiving radio node may in particular be a wireless device like a terminal or UE. However, in some cases, e.g. IAB or relay scenarios or multiple-RAT scenarios, it may be network node or base station, and / or a network radio node, for example an IAB or relay node.

[0027] Monitoring signalling may be associated to a transmission beam and / or a beam pair, and / or may comprise (as signalling type) reference signalling and / or data signalling, and / or in some cases control signalling. A beam or beam pair and / or resources for monitoring signalling, and / or type of monitoring signalling may be indicated with the monitoring configuration.

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

[0029] Brief description of the drawings

[0030] The drawings are provided to illustrate concepts and approaches described herein, they are not intended to limit their scope. The drawings comprise:

[0031] Figure 1 , showing an exemplary neural network;

[0032] Figure 2, showing an exemplary approach for model lifecycle management;

[0033] Figure 3, showing an exemplary approach for using a model for radio node operation;

[0034] Figure 4, showing an exemplary approach of demapping and / or for a receiver;

[0035] Figure 5, showing an SNR vs BLER result for different operation policies; Figure 6, showing an exemplary DPoD model monitoring scenario;

[0036] Figure 7, showing an exemplary radio node like a terminal or UE, e.g., operating based on a model; and

[0037] Figure 8, showing another exemplary radio node like a network node, e.g., operating the model and / or monitoring operation according to the model.

[0038] Detailed description

[0039] The term “receiver” may be considered with broad meaning, e.g., to refer to an entity like a device and / or radio node and / or arrangement and / or circuitry and / or algorithm for receiving signalling, e.g., certain transmitted data, and / or for detecting and / or monitoring for and / or decoding and / or demodulating the signalling and / or transmitted data; signalling and / or transmitted data may be transmitted by a transmitter, which may be another entity like a device and / or radio node and / or arrangement and / or circuitry and / or algorithm for transmitting signalling, e.g., certain transmitted data. In general, a device or arrangement or node or entity may encompass both a transmitter and a receiver and / or corresponding functionality; in general, a transmitter of specific signalling and / or transmitted data may be considered to be a different entity of the receiver of such.

[0040] In some cases, a transmitter may be represented by, and / or be part of, and / or be associated to, a wireless device. A receiver may for example be represented by, and / or be part of, and / or be associated to, a network node. However, cases in which a transmitter corresponds to a network node, and / or a receiver corresponds to a wireless device may be considered.

[0041] Signalling or data may be transmitted for example over a wireless channel (e.g., in a wireless communication network), through an optical fiber, or through wired channel. A communication network may be and / or comprise a wireless communication network and / or radio access network, and / or a higher layer network, e.g., a core network, and / or an intermediate network and / or one or more associated network layers. A node or device may be associated to and / or part of such a network and / or layer.

[0042] Received data (e.g., signalling and / or transmitted data as received) may be subject to some distortions and / or conditions depending on the transmission medium and the hardware at transmitter and receiver. Receivers may experience conditions over time and / or frequency and / or space that are unknown and may be estimated to achieve optimal performance. These conditions can also vary, over e.g., time or frequency. Under each condition, the receiver can possibly operate in different ways to cope with underlying conditions. Some example conditions may comprise non-linearities of hardware at the transmitter and / or receiver, phase or frequency drifts and / or distortion, pathloss, temperature sensitivity of hardware, etc.

[0043] Machine learning (ML) or Machine learning algorithms may refer to, and / or be based on, and / or comprise techniques using a set of training data for one or more training model / s (or model in general) and / or using trained model / s for various applications, e.g., including one or more of inference, classification, prediction. Machine learning algorithms may be classified into online and offline algorithms, where offline algorithms may rely on pre-trained models, while online algorithms may train the model on the fly (and / or during operation), e.g., while receiving new data samples. An online approach may be based on a previous offline pre-training of a model. ML may be further classified according to be supervised, unsupervised and / or reinforcement learning; learning approaches may be combined, in particular for online learning, e.g., based on offline learning.

[0044] A ML, or a ML system and / or model and / or algorithm and / or technique, may be implemented in software and / or with data, and may alternatively referred to as ML model; in some cases, it may be implemented as and / or comprise hardware and / or firmware and / or associated components. A ML system may in general be adapted to obtain input, extract information based on the input and its training, and provide an output. ML, a ML system or model may be based on, and / or comprise a neural network, and / or may be based on a machine learning approach. The ML system may be based on a regressive or linear approach. In some cases, a deep learning system may be used as ML model. A model, ML or a ML system may be considered an (artificial) neural network, and / or may comprise one or more neural networks and / or one or more layers.

[0045] A neural network may generally be an artificial neural network; in some cases, it may be referred to a model, and / or represented by a model. A model or neural network may comprise multiple layers. The layers may be of different type; in particular, the neural network or model may comprise an input layer, for receiving data to be evaluated and / or as training data as input or base data, and an output layer, providing processed data as output and / or result. Between input layer and output layer, there may be one or more hidden layers, which may be interconnected to receive output of one layer as input, and / or to provide its output as input for another layer. The neural network may be linear, or non-linear. In some cases, the neural network may be recursive, e.g., such that the same layer (at least one layer) may be provided with output of a layer (e.g., itself, or a different layer) multiple times. A layer may operate based on matrix multiplication being applied on input. In some cases, a layer may operate based on convolution being applied on input. Base input may correspond to original data the network as a whole is intended to operate on to provide a result, which may be considered output of the last / output layer and / or the neural network as a whole. A neural network may be a convolutional neural network, e.g., comprising at least one convolutional layer. Inference may refer to the model providing prediction / s and / or conclusions based on new data, e.g., provided as input data to the (trained) model, e.g., during operation or application of the model.

[0046] An artificial neural network may represent a class of machine learning algorithms provide a capability to approximate a general function based on training data set / s, and may facilitate parallel processing, which make these techniques attractive candidates for implementation on emerging Al accelerator hardware. A neural network may be based on interconnected processing units called neurons as depicted in Figure 1 , where each neuron (shown as circular nodes, and arranged in layers) receives weighted version (indicated by the lines, weights indicated by wjn for input weight, w_out for output weight, w_hidden for weights of layer / s between input and output layers) of the other neuron’s outputs and compute the output based on a nonlinear transformation of the aggregated inputs using an activation function. Input data may represent input to the model and / or a layer, in particular an input layer. Output data may represent output of the network or a layer, in particular an output layer. Network data may represent the neural network (e.g., as software and / or with associated data / weights and / o connections and / or layers and / or nodes and / or neurons). Auxiliary data or intermediate data may comprise intermediate results, and / or additional information, in particular control information, e.g., pertaining to a target layer for output, and / or formatting of data, or similar.

[0047] AI / ML may be utilised for a wireless network or radio access network, e.g., an air interface like a NR Air Interface. Life cycle management (LCM) may be considered for such. AI / ML may be used for the physical layer of the wireless network, e.g., for design and / or operation of the physical layer and / or the radio access network.

[0048] A possible high-level description of model LCM for Al on PHY may include the stages and data / signal flows depicted in Figure 2. LCM may comprise setting up a model based on data, based on which a model may be trained. A trained (pre-trained) model may be deployed and / or applied and / or used, e.g., in the context of model inference. The deployed model may be monitored, e.g., for performance.

[0049] In particular, model performance monitoring (or short model monitoring) may be considered. Model performance monitoring may refer to, and / or comprise, and / or be based on, a procedure that monitors an inference performance of the AI / ML model.

[0050] In general, one or more of metrics / methods for AI / ML model monitoring in lifecycle management may be considered:

[0051] Monitoring based on inference accuracy, which may include metrics related to intermediate KPIs (KPI may in general refer to key performance indicator, e.g., predefined parameters of performance, which may be indicative of individual radio links or overall link performance, e.g., based on (weighed) average and / or combined parameter / s and / or parameter sets); and / or

[0052] Monitoring based on system performance, including metrics related to system performance KPIs;

[0053] Monitoring based on data distribution, which can further include one or more of Input-based monitoring, monitoring the input data, e.g., validity of the AI / ML input based on out-of-distribution detection, drift detection of input data, etc.; and / or

[0054] Output-based monitoring: e.g., drift detection of output data; and / or

[0055] Monitoring based on applicable conditions and / or parameters, e.g. pre-defined and / or preconfigurable conditions and / or operational conditions.

[0056] Some examples of KPI / monitored parameter / s may pertain to signal strength and / or signal quality and / or one or more signalling characteristics, e.g., BLER and / or BER, and / or SNR and / or SIR and / or SINR, etc.

[0057] AI / ML receiver methods may be considered. Machine learning methods and / or a model may be used at a receiver side, e.g., to optimize one or multiple functionalities at the receiver. For example, a machine learning receiver method based on neural network (NN) may be utilised optimize the demapper (a single functionality), e.g., to compensate for hardware impairments due to oscillator phase noise. This is exemplified in Figure 3, which shows various typical functionalities provided at a receiver, like FFT on received signalling, performing channel estimation (e.g., based on reference signalling received, performing phase noise (PN) compensation, channel combining and equalisation, DFT dispreading if applicable and demapping, which may be performed utilising a model / ML as described herein, e.g., as ML-based soft demapper. Demapping may refer to extracting bits from received symbols.

[0058] One example of a neural network receiver is illustrated in Figure 4. Soft symbol-by- symbol demapping may be performed, taking the real (I) and imaginary (Q) components of a complex baseband sample, context information and SNR estimate as inputs and generating soft bits LLR of a desired range as the output. Such a demapper may improve the performance of a system that is under the influence of RF impairments such as PA nonlinearity. Performance of this ML / AI-based method in comparison with a baseline method is illustrated in Figure 5.

[0059] Al-based digital post distortion (AI-DPoD) compensation may rely on a trainable or trained entity (or ML model) at the receiver side (e.g., gNB in uplink transmissions). The model can be implemented for example using neural network / s and / or may be pre-trained for the operation in the network. However, the performance of the model may degrade during the operation of the system. For example, due to the introduction of new types of UEs which have not been considered during the training of the model, or change of the conditions, e.g., on the hardware or the propagation environment, due to which the operation conditions may deviate from the conditions under which the model has been trained. This can lead to performance degradation in the system. An approach to systematically monitor the performance of the DPoD model and perform actions accordingly may be considered, especially considering the special nature of training a model to handle PA non-linear distortion.

[0060] Approaches for monitoring gNB ML model-based DPoD performance are considered, in particular when UEs are configured to transmit with reduced PA backoff and the ML model is used to compensate the additional TX distortion. This may facilitate UE PA type / mode and the gNB DPoD model remaining compatible, although UE PA design and operation details may be unknown to the gNB.

[0061] Model monitoring (may be performed before model activation, to determine whether to activate the model fora specific UE or all UEs e.g., monitoring without using a model for receiving, e.g., to provide a baseline for comparison of operation modes), e.g., to ensure that the UE PA design and operation mode is compatible with the DPoD model. It may also or alternatively be performed after model activation, to detect subsequent degradation or data drift. Drift may occur, e.g., due to change of operating conditions due to the variations in the temperature, which could change UE PA characteristics, or a change of the UE configurations that may not be transparent to the gNB such as activation / deactivation of DPD (Digital Pre-Distortion) or energy saving features such as PA envelope tracking.

[0062] Model monitoring may be continuous or performed at a set of time occasions, periodically or on-demand. The gNB may signal a monitoring configuration, and / or initiation and termination of monitoring, and / or trigger single-instance monitoring support from one or more UEs. The UEs may signal DPoD model monitoring support capability to the NW, e.g. with capability information, which may be transmitted in an RRC layer message.. In general, a transmitter like a UE or network node may be adapted to transmit signalling for model monitoring (monitoring signalling), which may comprise reference signalling and / or data (e.g., predefined data, and / or random data). In general, monitoring signalling may be transmitted based on a monitoring configuration. A monitoring configuration may indicate transmitting parameters specific to the monitoring signalling. Such parameter / s may pertain to the power amplifier, and / or transmission power level, and / or (power) distortion like digital pre-distortion, and / or power backoff, and / or non-linearity (or linearity) of power amplifier operation when transmitting, and / or transmission power time domain behaviour, and / or phase distortion, and / or phase non-linearity, and / or phase time domain behaviour, and / or deviation and / or derivate of one or more thereof. In some cases, the parameter / s may pertain to time domain behaviour or resources of the transmission, and / or repetition and / or periodicity (e.g., over one or more transmission time structures), and / or transmission duration (e.g., over one or more structures or interval or symbols durations), and / or location in time domain (e.g., specific transmission time structure and / or slot and / or subframe and / or symbol / s of transmission), and / or frequency domain behaviour and / or resources, e.g., carrier and / or resource blocks and / or frequency range, and / or deviation and / or derivate of one or more thereof. In some cases, the parameter / s may indicate a sequence or modulation sequence or symbol sequence (e.g., for reference signalling like SRS or DMRS) and / or sequence root, and / or a code rate or maximum code rate, or minimum code rate, and / or a modulation for transmission of the monitoring signalling, or a modulation set or code rate set, which may be used to provide time-variable behaviour for modulation and / or code rate. One or more transmission parameters may be different between different monitoring configurations, and / or for different monitoring signalling instances. Transmission parameters may comprise one or more radio front-end (FE) parameters, e.g., one or more of: MPR relaxation, PA backoff, EVM metric, etc. Alternatively, and / or additionally, transmission parameters may comprise monitoring signal parameters, and / or monitoring occasion parameters.

[0063] A transmitter may be configured or configurable with multiple (different) monitoring configurations. Monitoring signalling and / or an associated configuration may be intended for, and / or specific to, and / or facilitate monitoring of a model and / or evaluating model performance; the model may be a receiver model, which may be operable for receiving signalling from the transmitter and / or receiving monitoring signalling. Monitoring signalling and / or a monitoring configuration may correspond to parameters and / or be according to parameters corresponding to a specific operation mode of the transmitter and / or receiver, e.g. , using a model for controlling transmission and / or for controlling reception.

[0064] In general, a transmitter may operate based on a transmitter model, and / or a receiver may operate based on a receiver model.

[0065] One or more of the following monitoring approaches may be considered: a UE / transmitter may transmit data signalling like regular data; and / or a receiver / NW node may monitor resulting BLER and / or one or more other KPIs; and / or a transmitter / UE may transmit data signalling like regular data with predetermined (higher) PA distortion, lower code rate; and / or the receiver / gNB may monitor DPoD output metrics (e.g. soft bits); and / or a transmitter / UE may transmit data signalling like regular data with no MPR (e.g., in legacy mode); receiver / gNB may compare legacy RX performance with previous model performance; and / or a transmitter / UE may transmit a known test sequence; receiver / gNB may monitor DPoD output metrics; and / or receiver / gNB may operate legacy RX in parallel with the ML model, and may compare model output metric between receiving modes; and / or receiver / gNB may operate multiple models (in some cases, also nonmodel based / legacy receiver mode / s) in parallel, and / or may compare model output metric / s.

[0066] In general, one or more of the following aspects may be considered: a receiver / gNB may additionally monitor SNR statistics; and / or a transmitter / UE may be adapted to, and / or may report current PHR, MPR relaxation, PA backoff value, etc. (e.g., based on configuration provided by the receiver / gNB); and / or receiver / gNB may consider info on expected conditions associated with the training dataset; and / or monitoring can be detecting gradual degradation, while the model is still partially functional (using regular data as labels and observing DPoD output metrics).

[0067] In some cases, regular data and / or data signalling (of which regular data may be a form of) and / or test sequence and / or reference signalling (of which a test sequence may be a form of) may be utilised as monitoring signalling.

[0068] The receiver may be adapted for monitoring, and / or monitoring may be performed, on a representative UE subset and / or monitoring signalling from one or more transmitters, e.g., of the subset of UEs, connected to, and / or communicating with the receiver.

[0069] Signalling operation may be based on monitoring. Signalling operation may comprise reception / receiving of signalling, and / or adapting such, and / or operating in a receiver mode (also referred to as receiving mode or reception mode). A mode may indicate whether or not a model is used, and / or which model is used, for receiving and / or for the receiver. Different modes may differ in the model and / or whether a model is used, and / or regarding one or more parameters for the model / s. A receiver mode may indicate receiver without a ML model (also referred to as legacy). Different modes may indicate different parameters for a receiver without a ML model, and / or different approaches for such a receiver.

[0070] In some cases, signalling operation may comprise transmitting / transmission of signalling, and / or adapting such, and / or operating in a transmitter mode (also referred to as transmitting mode or transmission mode). A mode may indicate whether or not a model is used, and / or which model is used, for transmitting and / or for the transmitter. Different modes may differ in the model and / or whether a model is used, and / or regarding one or more parameters for the model / s. A transmitter mode may indicate a transmitter without a ML model (also referred to as legacy). Different modes may indicate different parameters for a transmitter without a ML model, and / or different approaches for such a transmitter.

[0071] In general, a model may be used for one or more functions and / or components for a transmitter or receiver, in particular one or more functions and / or components associated to the physical layer of a radio access network, e.g., for receiver and / or transmitter. Such a function may for example correspond to demapping for a receiver and / or mapping for a transmitter (mapping information bits to symbols and / or the inverse of demapping). It may be considered that a model may be used / activated and / or switch on or to comparatively quickly, such that a mode may change between symbols and / or slots and / or different modes may be used for communication with different UEs / transmitters. A receiver model and / or a transmitter model may be a DPoD model, in which DPoD is used for transmission and / or reception of signalling.

[0072] Signalling operation based on monitoring may comprise performing one or more actions or operations based on monitoring results, or in some cases, not performing one or more actions. Actions may comprise switching a model, and / or adapting a model, and / or adapting or setting one or more parameters for a model and / or receiver and / or transmitter, transmitting signalling. The transmitted signalling may indicate, e.g., to a transmitter, a monitoring result and / or one or more actions to perform, and / or a transmission configuration or reception configuration (e.g., reconfiguring, and / or indicating an already configured configuration to use), and / or to activate a model or to deactivate a model or which model to switch to (e.g., for transmitting). Alternatively, or additionally, it may indicate one or more transmission parameters for the transmitter to use, e.g., pertaining to PA backoff and / or MPR and / or MPR relaxation). Signalling operation may be based on and / or comprise evaluating monitoring and / or monitoring result / s.

[0073] Monitoring, and / or performing monitoring may comprise, and / or be based on, determining a monitoring result, and / or determining and / or evaluating one or more parameter / s and / or KPIs, which may pertain to reception, e.g., of monitoring signalling. The reception and / or monitoring may pertain to a receiver mode and / or transmitting mode (e.g., of the transmitter).

[0074] Depending on monitoring outcome or result, one or more of the following actions may be taken by the receiver and / or gNB, e.g., a signalling operation:

[0075] If the model is functioning well for all UEs, activate it or continue using it. If it is failing for some UEs, apply fallback (legacy DPoD or other radio front end (FE) solution and / or reduce MPR relaxation), and optionally request training data from these UEs, and / or continue using the model for other UEs;

[0076] If it is failing for most (and / or a pre-defined or specific number or ratio of) UEs, the receiver / gNB may apply one or more of the following: switch the DPoD function to another model; and / or falls back to legacy DPoD or another radio FE (Front-End) algorithm, and UE is configured to reduce or remove MPR relaxation or increase PA backoff (e.g., with transmitting signalling providing corresponding indications) trigger model retraining (and may initiate additional training data collection).

[0077] In general, there may be considered a method of operating a wireless device or transmitter, and / or there may be considered a wireless device or transmitter. The method may comprise, and / or the WD or transmitter may be adapted for: receiving from a receiver or network node or gNB a monitoring configuration like a DPoD model monitoring configuration, which may comprise one or more parameters, e.g., radio front end parameters, and / or monitoring signalling parameters, and / or monitoring occasion parameters (e.g., regarding time domain), and / or transmitting, e.g., to the gNB or receiver or network node, monitoring signalling according to or based on a model monitoring configuration, which may be the received and / or configured one. Transmitting may be based on an indication or trigger of monitoring initiation and / or monitoring termination (e.g., initiation / termination signaling may be separate from configuration signaling), which may for example be provided with control signalling, e.g., physical layer signalling, e.g., on PDCCH and / or DCI. The method may comprise, and / or the device may be adapted for (further) receiving, e.g., from the receiver / network node / gNB, upon terminating the monitoring transmission (monitoring signalling), an updated UL transmission configuration (e.g. increase backoff if the gNB DPoD model is deactivated), and / or transmitting based on such a configuration. In general, the method may comprise and / or the device may be updated for (further) signaling to the network node and / or receiver and / or gNB a capability of DPoD model monitoring support, e.g., with capability signalling. It may be considered that the configuration may indicate, and / or transmission of signalling is based on, transmission parameter / s, e.g., radio front end parameters which may comprise one or more of: MPR relaxation, PA backoff, EVM metric. Monitoring signal parameters may comprise one or more of: known data source, sequence generation seed, using user data, MCS applied to user data. Monitoring occasion parameters may comprise one or more of: periodic / one-time, duration, number of instances, period.

[0078] There may be considered a method of operating a receiver and / or network node and / or gnB, and / or there may be considered a receiver and / or network node and / or gNB. The method may be for, and / or the receiver or network node or gNB may be adapted for model monitoring and / or for DPoD model monitoring. The method may comprise, and / or the receiver or network node orgNB may be adapted for: transmitting to a transmitter or UE or WD a monitoring configuration like DPoD model monitoring configuration, which may comprise one or more of radio front end parameters, and / or monitoring signal parameters, and / or monitoring occasion parameters. The method may comprise, and / or the receiver and / or network node and / or gNB may be adapted for, receiving, e.g, from a transmitter and / or a WD or UE, monitoring signalling, which may be based on and / or according to the model monitoring configuration. The method may comprise, and / or the receiver and / or network node and / or gNB may be adapted for, monitoring reception based on the monitoring signalling, and / or performing a DPoD model monitoring based on the received monitoring signalling. Monitoring and / or performing the model monitoring may be considered based on and / or may be wrt. one or more UEs before activating the DPoD model, and / or if the monitoring result is favorable, and / or based on the monitoring, a first (LCM) action may be taken, e.g., activating the model for the one or more UEs (e.g., a receiver model for reception from the UEs, and / or indicating activation of a transmitter model on the UEs, using signalling). Monitoring and / or performing the model monitoring may be considered based on and / or wrt. one or more UEs after activating the (DPoD) model, and / or based on the result, and / or if the monitoring result is unfavorable, taking a second LCM action for the one or more UEs. The second LCM action may comprise falling back to legacy RX processing (receiver mode) and / or instructing or configuring the UE to use legacy TX procedures (using corresponding signalling). The second LCM action may comprise switching to another (DPoD) receiver model. The second LCM action may comprises initiating (e.g., DPoD) model retraining, e.g., retraining of the receiver model. This may include instructing one or more UEs accordingly, e.g., to provide training data. It may be considered that monitoring and / or performing the model monitoring may comprise one or more of: running legacy receiver algorithm in parallel with the model, e.g., a ML DPoD model, running multiple models, e.g., ML DPoD models in parallel, etc.

[0079] Approaches discussed herein facilitate that UE PA type / mode and the gNB DPoD model are compatible and remain compatible during operation, although UE PA design and operation details may be unknown to the gNB. This is achieved robustly and flexibly, with minimum additional test signal transmission and processing overhead. Approaches may be generalised to transmitters (of monitoring signalling) and receivers (of monitoring signalling), which may have different function in a network. For example, in some cases, a receiver may be a wireless device or UE, or both transmitter and receiver may be WDs, e.g., in a sidelink scenario.

[0080] There are described approaches and methods for model performance monitoring of AI / ML based DPoD at the receiver of a wireless transmission. In general, principle and methodology described may be applied to uplink, where transmitter is a device (referred to as UE in the discussion below), receiver is base station or network node (referred to as gNB in the discussion), downlink, where transmitter is a network node or gNB, receiver is a device, sidelink, where the transmitter and receiver are two peer UEs.

[0081] Without losing the generality, the disclosed methods are explained below using nonlimiting examples where AI / ML model based digital post distortion (DPoD) is applied at the gNB receiver for uplink transmission. It is understood by those skilled in the art that the disclosed methods can be applied to other setups as well.

[0082] For model monitoring of the DPoD model (or other receiver model) located at the network side, model monitoring occasions may be defined for validating the model performance. During the occasions, received samples / symbols / bits for which labels are available or can be generated may be used to evaluate / verify model performance via intermediate or performance metrics.

[0083] To support model monitoring, the UE additionally may report PHR (Power Headroom Report) to the network node, where the PHR contains fields related to relaxed MPR associated with transmitting the predefined bit sequence S. The UE may also report explicit currently applied PA backoff values.

[0084] The base station may trigger the model monitoring procedure before model activation or after model activation.

[0085] When triggering the model monitoring procedure before model activation, the base station may use this model monitoring procedure to verify that the AI / ML model can work well for the given UE. For instance, the AI / ML model may have trained for certain type of power amplifier (GaAs, GaN), certain power amplifier classes (e.g. class A, B, AB, ...), certain range of parameters of the power amplifier (e.g. bias voltage, operating temperature, ...), but not all the possible power amplifier types and parameter ranges possible. Additionally, the UE may activate certain features to that impact the effective linearity of the systems e.g., envelops tracking and / or digital pre distortion (DPD). Then it is necessary to verify that the given UE's power amplifier and the activated features are compatible with the AI / ML model at the base station side. For example, the base station AI / ML model may have been trained with the following PA types and parameter ranges:

[0086] (1) GaAs (gallium arsenide) PA designed for operation at around 2.1GHz;

[0087] (2) GaN (gallium nitride) PA designed for operation at around 2.1 GHz;

[0088] (3) GaN (gallium nitride) PA designed for operation at around 28 GHz;

[0089] If the UE's PA model is compatible with any of (1)-(3) above, then the base station AI / ML model is expected to perform well for DPoD. On the other hand, the AI / ML model may not work satisfactory if the UE's PA model is not compatible with any of (1)-(3) above, e.g., a CMOS PA designed for operation around 28 GHz.

[0090] In addition to the substrate technology and the frequency band, other PA design- related parameters affecting the resulting non-linearity may be used for model validity checking.

[0091] The model monitoring procedure may be used to verify model performance, given that UE power amplifier implementation is typically proprietary and not known to the network. If the model monitoring procedure indicates satisfactory performance, then the AI / ML model can be used to receive the given UE's UL transmission. Otherwise, the AI / ML model is not applicable, and legacy receiver or another model should be used instead.

[0092] When triggering the model monitoring procedure after model activation, the base station may use this model monitoring procedure to verify that the AI / ML model continues to work well for the given UE in the current operating scenario, or to identify performance degradation due to e.g. data drift when the input data is not representative of the previously used training data. In particular, the model monitoring procedure may be triggered when the NW identifies an unexpected performance degradation while the model is activated.

[0093] Based on the outcome of the model monitoring, one or more of the following scenarios can be considered:

[0094] • Scenario #1 : the model is working well for all UEs, then the model can be executed for all UEs with no further action.

[0095] • Scenario #2: the model is not working well for one UE or one group (subset) of UEs, but the model is fine for all other UEs. o The network signals the poorly performing UEs not to rely on DPoD and fall back to legacy behavior. The model is still executed for all other UEs. o The network signals the poorly performing UE(s) to transmit training data

[0096] (or use the data collected for model monitoring), and initiate model retraining to update the model.

[0097] • Scenario #3: the model is not working well for all UEs or for the majority of the UEs. o The network deactivates the DPoD feature, and signal to all UEs not to rely on DPoD and to fall back to the legacy behavior. o The network signal the UEs to transmit training data (or use the data collected for model monitoring), and initiate model retraining to update the model.

[0098] Signaling related to (DPoD) model monitoring may be considered. In one aspect, the UE signals to the NW DPoD model monitoring assistance capability (e.g. via RRC signaling in conjunction with initial connection establishment). In one aspect, the gNB signals to the UE DPoD model monitoring configuration (e.g via RRC). The configuration may include PA settings, monitoring data parameters, monitoring occasion parameters, monitoring initiation mode, etc., Multiple configurations with different parameter settings may be provided. In one aspect, the gNB signals DPoD model monitoring initiation (and optionally, the monitoring duration or the number and timing of occasions) and termination. Efficient signaling (e.g. via DCI) may be used, e.g one or few bits, to trigger one out of a set of pre-configured actions for UE. This ensures that the signaling overhead to support monitoring is not excessive. In one aspect, the activation is signaled to a representative subset of UEs in the cell, where the representation is in terms of all expected PA designs and operating modes, when checking model performance. Based on monitoring results, the gNB may signal (DPoD) model activation and / or related UE transmission configuration changes, e.g. MPR relaxation. In model activation, it may be activated for all UEs or for a subset of UEs while other UEs use legacy behavior. Similarly, the gNB may signal (DPoD) functionality deactivation and related UE transmission configuration changes, e.g. removing MPR relaxation, for UEs for which the DPoD model performance is inferior, or for all UEs if the functionality is deactivated for the entire cell. Example signalings for realizing (DPoD) monitoring are illustrated in Figure 6.

[0099] Model performance monitoring approaches may comprise and / or be based on one or more of the following: Approach / Method 1 : Trigger the UEs to transmit a known sequence periodically or on-demand. At the model monitoring occasions, the network node may trigger the UE to transmit a predefined pseudorandom bit sequence S on the uplink, optionally with a predetermined / configured PA settings (e.g. PHR, backoff). Since S is known to the network node a priori, S can serve as ground truth labels for calculating model performance metrics of the network side model. The transmitted data can be collected for model re-training as well. In Approach / Method 2, there may be no need to send known sequence. The UE may transmit information blocks (data blocks) on the uplink in the normal manner (e.g., regular data). As usual, the information blocks may be attached with CRC bits for error detection, and then encoded with channel coding techniques (e.g., LDPC codes) for error correction. At the receiver of the network node, the received signal may be processed with DPoD (e.g., to generate LLR values of the received bits), channel decoding (e.g., LDPC decoder to correct errors), and CRC decoding (to detect errors) to extract the information block. The network node may monitor the bit error rate (BER) or block error rate (BLER) of the received information block. If the monitored BER or BLER approximately or at maximally matches the target BER or target BLER set by the scheduler (e.g., target BLER=1e-2 for typical data transmission), then the network node may determine that the AI / ML model for DPoD is working properly. On the other hand, if the monitored BER or BLER is substantially higher than the target BER or target BLER set by the scheduler (e.g., monitored BLER is 1 e-1 while the target BLER is set as 1e-2), then the network node can indicate, e.g., sound an alarm, that the AI / ML model (e.g., for DPoD) may not be working well. In one variant of this approach, for monitoring while the received signal quality is still sufficient for successful decoding of, e.g., PUSCH, the decoded data may be used to generate the coded bit labels and the model output may be compared to the labels to estimate a performance metric. Alternatively, or additionally, the UE may transmit regular data with a predetermined (higher) PA distortion to be able to more critically test the model’s compensation ability, but a lower code rate is used to allow successful decoding and label generation. Using the labels, the gNB may monitor (e.g., DPoD) output metrics (e.g. soft bits). The monitoring may be performed over a (e.g., pre-determined and / or configured and / or sufficiently large) time window, in order to collect sufficiently reliable statistics for making model monitoring decisions. Approach / Method 3 may comprise running two or more Al models (each may have different complexity, where one of them may be a reference model, etc), e.g., in parallel to cross-checking. Among the models that have satisfactory performance, the one with the lowest complexity among models providing satisfactory performance may be activated. This may be up to base station implementation, and transparent to other nodes like UE. As a variant, a legacy receiver may be run in parallel to the Al model, using intermediate metrics (e.g. the mean and standard deviation of the magnitude of the soft values), or the collected statistics using CRC check (e.g. BLER) to assess / compare model output quality. If the legacy receiver outperforms the Al receiver, then the Al model may be deactivated and / or be retrained. Approach / Method 4 may comprise configuring the UE to periodically, or on demand, transmit its payload complying with Tx EVM requirements valid for conventional receivers. This may imply that the UE will increase its PA backoff and likely use a more robust modulation and coding scheme. This requirement may facilitate or ensure that the nonlinearities from the transmitter are small enough to allow the use of a conventional receiver. A potential problem associated with the use of conventional receivers to demodulate and decode non-linearly distorted signals is that the performance may collapse. This means that no codeword may be correctly decoded despite the received signal power being sufficiently above the noise floor to decode the codeword with a given probability. Using this approach / method, the network can compare the performance of a conventional receiver with historical data of the Al receiver performance. If these transmissions have a low duty cycle (e.g. 1- 5% of the total transmissions), the impact on throughput and / or UE energy performance is very small and the network may monitor the health of the link.

[0100] Other (DPoD) model monitoring aspects are considered. The gNB may additionally, or alternatively, monitor SNR or other link quality statistics, and may apply monitoring metrics or criteria applicable to the current SNR. A UE may additionally, or alternatively, report to the gNB its current PHR, MPR relaxation, PA backoff value, etc. and the model performance monitoring results may be assessed specifically for the reported TX parameters or PA type / operation. A gNB may consider additional info on expected conditions associated with the training dataset, and the model performance monitoring results may be compared specifically for the associated conditions. The monitoring approaches and / or mechanism can be used to detect gradual degradation while the model is still partially functional, e.g., using regular user data as labels and observing DPoD output metrics.

[0101] Monitoring may be be performed on a representative UE subset. From the full population of UEs in the cell, the gNB may pick a smaller subset UEs belonging to one type (e.g., PA type), run the monitoring procedure to check whether gNB side model. This may save signaling overhead and monitoring burden, as compared to perform the monitoring on all UEs' transmission.

[0102] Actions based on monitoring, e.g., DPoD model performance monitoring, may be considered. In one variant, the gNB may deactivate the DPoD feature and / or model, and may falls back to the legacy receiver. The gNB may notify the UE accordingly, or omit this. The UE may adapt transmission of signalling accordingly (e.g. adapt transmit power and / or the PA’s operating point, e.g. bias voltage), so that distortions at the transmitter are reduced to levels manageable by conventional receivers. The UE may be configured to comply with TxEVM requirements for conventional receivers. In a variant, the gNB may perform model switching. The model switching can be applied to adapt the complexity of the model with the level of distortions. For example, if the signal is distorted with severe distortion, then a more capable (more complex) AI / ML model may be deployed at the receiver (e.g., for DPoD). The BS may deploy more advanced models after testing them under the same conditions where the initial model failed. By having metadata about trained models, training conditions, and performance metrics, a gNB may dynamically deploy advanced models as needed. Each model may have an associated LUT (Look-Up Tables) that may define its performance under different conditions. These conditions may include normal scenarios and worst-case scenarios with various distortions level and imperfections. From, e.g., generalization tests across imperfections and non-linearities an average throughput for 256 QAM and 64QAM can be deduced and used as worst-case scenario KPIs.

[0103] In one gNB implementation, the model switch may be relatively static / long-term; dynamic update of NW-side model may be avoided due to long latency to load a model in practice; this may depend on capability of the receiver, e.g., to load and / or activate a model. In another implementation, the model switching may be dynamic, where multiple models have been loaded in memory and the model switch amounts to pointing to another memory region, this may depend on capability of the receiver, e.g., to load and / or activate a model.

[0104] Model retraining orfine-tuning scenarios are considered. In some cases, the gNB may, based on the monitoring result, initiate a re-training session, e.g., to correct or finetune the model, e.g., using the known data that has been sent for performance monitoring purpose, or signal the UE to transmit training data in the case that monitoring has not been performed based on transmitting known sequences (e.g. approach / method 2). Re-training may be based on and / or may use data collected across various PA operating conditions, e.g., received signals and corresponding transmit bits for different PA backoff values. The re-training may be performed for one or multiple transmit signal types, e.g., specific modulation order or a group of modulation orders depending on the performance of the existing model or DPoD model for each signal type. For example, if the existing model or DPoD model underperforms for 64QAM, then the re-training may be performed using a data set containing more data samples for 64QAM. This may facilitate allocating of training resources efficiently. According to one scenario, general performance-based retraining (for all UEs) may be considered. If the overall performance metrics (KPIs) fall below predefined thresholds (e.g., based on previous performance or LUT), there may be considered initiating a retraining or fine-tuning procedure for the general model. This may facilitate or ensure that the AI / ML model used at the receiver is optimized for current conditions for all UEs and achieve an acceptable performance. In another scenario, UE cluster-specific model may be considered. The receiver / BS may monitor the performance of individual UEs based on metrics (BLER, SNR, ...) used to identify specific UEs experiencing performance issues. Instead of relying on a single model for all UEs, multiple models for different UE categories, based on clustering techniques to group UEs with similar characteristics and create specific models for each cluster, may be used. The receiver / BS may request the specific UEs to send training data for this purpose. At the same time, UEs may be requested or signalling or instructed to fallback normal EVM level that the legacy receiver support or to reduce distortion to a certain level that can be managed by the switch model.

[0105] If the UEs encounters the same issue in another gNB or receiver, and a re-training plan has already been initiated in the previous gNB, the retaining initiation may be aggregated based on input from multiple cells. In one variant, a model training architecture may be used where a central node trains a single model for multiple gNBs that use the same type of hardware.

[0106] In general, a receiver may be represented by, and / or comprise, at least one receiver and / or transceiver circuitry and / or associated software and / or hardware and / or firmware and / or modules and / or components. A receiver may be a device adapted for receiving signalling, and may be included in a larger device with additional functionality, e.g., for transmitting and / or user functions and / or server functions. A receiver may be implemented as a receiving device, in particular a receiving radio node, which may for example be a network node, or a user equipment or terminal or wireless device. A receiver may encompass and / or provide one or more functions and / or associated modules and / or components, which may be involved in receiving functions. A receiver may be a receiver for receiving monitoring signalling. In general, a transmitter may be represented by, and / or comprise, at least one transmitter and / or transceiver circuitry and / or associated software and / or hardware and / or firmware and / or modules and / or components. A transmitter may be a device adapted for transmitting signalling, and may be included in a larger device with additional functionality, e.g., for receiving and / or user functions and / or server functions. A transmitter may be implemented as a transmitting device, in particular a transmitting radio node, which may for example be a network node, or a user equipment or terminal or wireless device. A transmitter may encompass and / or provide one or more functions and / or associated modules and / or components, which may be involved in transmitting functions. A transmitter may be a transmitter for transmitting monitoring signalling.

[0107] In some cases, the term receiver may refer to the receiver / transceiver circuitry and / or functions actually involved in reception of signalling, in others it may refer to the device / arrangement which comprises such circuitry and functions (e.g., radio node); unless it is clear from the context which interpretation is referred to, it should be assumed that both, or either, apply. In some cases, the term transmitter may refer to the transmitter / transceiver circuitry and / or functions actually involved in transmission of signalling, in others it may refer to the device / arrangement which comprises such circuitry and functions (e.g., radio node); unless it is clear from the context which interpretation is referred to, it should be assumed that both, or either, apply.

[0108] Figure 7 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 be referred to as control circuitry) 20, which may comprise a controller connected to a memory. Any module of the radio node 10, e.g. a communicating module or determining module, may be implemented in and / or executable by, the processing circuitry 20, in particular as module in the controller. Radio node 10 also comprises radio circuitry 22 providing receiving and transmitting or transceiving functionality (e.g., one or more transmitters and / or receivers and / or transceivers), the radio circuitry 22 being connected or connectable to the processing circuitry. An antenna circuitry 24 of the radio node 10 is connected or connectable to the radio circuitry 22 to collect or send and / or amplify signals. Radio circuitry 22 and the processing circuitry 20 controlling it are configured for cellular communication with a network, e.g. a RAN as described herein, and / or for sidelink communication (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 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.

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

[0110] In general, a block symbol may represent and / or correspond to an extension in time domain, e.g. a time interval. A block symbol duration (the length of the time interval) may correspond to the duration of an OFDM 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 comprises a plurality of modulation symbols, e.g. based on a subcarrier spacing and / or 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 mapping, and / or equivalent, and / or may be predefined and / or configured or configurable. A block symbol in this context may comprise and / or contain a plurality of individual modulation symbols, which may be for example 1000 or more, or 3000 or more, or 3300 or more. The number of modulation symbols in a block symbol may be based and / or be dependent on a bandwidth scheduled for transmission of signalling in the block symbol. A 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 or usable or intended e.g. 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 domain allocation and / or bandwidth allocated for transmission.

[0111] 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 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 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 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 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 waveforms, an affix may be included into a modulation symbol. In other cases, e.g. some single carrier-based waveforms, 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.

[0112] Communicating may comprise transmitting or receiving. It may be considered that communicating like transmitting signalling is based on a SC-FDM based waveform, and / or corresponds to a Frequency Domain Filtered (FDF) DFTS-OFDM waveform. However, the approaches may be applied to a Single Carrier based waveform, e.g. a SC-FDM or SC-FDE-waveform, 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 and / or second signalling) and / or beam / s (in particular, the first received beam and / or second received beam) may be based on a waveform 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 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 degrees 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 extended guard interval or switching protection interval may have a duration corresponding 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

[0113] 985 signalling with CP (e.g., SC-FDM-based or OFDM-based) for a waveform 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. 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 subcarrier or part of

[0114] 990 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. Pulse-shaping signalling may comprise pulse-shaping one or more symbols; pulse-shaped signalling may in general comprise at least one pulse-shaped symbol.

[0115] 995 Pulse-shaping may be performed based on a Nyquist-filter. It may be considered that pulse-shaping is performed based on periodically extending a frequency distribution of modulation symbols (and / or associated samples after FFT) over a first number of subcarrier to a larger, second number of subcarriers, wherein a subset of the first number of subcarriers from one end of the frequency distribution is appended at the

[0116] 1000 other end of the first number of subcarriers.

[0117] 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 time length) and / or an SC-FDM based waveform (including a FDF-DFTS-FDM

[0118] 1005 based waveform) or a single-carrier based waveform. Whether to use pulse-shaping or FDF on a SC-FDM or SC-based waveform may depend on the modulation scheme (e.g., MCS) used. Such waveforms may utilise a cyclic prefix and / or benefit particularly from the described approaches. Communicating may comprise and / or be based on beamforming, e.g. transmission beamforming and / or reception beamforming,

[0119] 1010 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 produced by performing analog beamforming to provide a beam corresponding to a reference beam. This allows efficient 1015 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 beamforming, and / or by digital beamforming, e.g. based on a precoder. This facilitates easy processing of beams, and / or limits the number of power amplifiers / ADC / DCA required

[0120] 1020 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

[0121] 1025 and / or the duration 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 waveforms. Communicating may comprise utilising a waveform with cyclic prefix. The cyclic prefix may be based on a numerology, and may help keeping signalling orthogonal. Communicating may

[0122] 1030 comprise, and / or be based on performing 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 receiving the selection indication may select a signalling bandwidth from a set of signalling bandwidths for performing cell search.

[0123] 1035 A beam or beam pair may in general be targeted at one radio node, or a group of radio 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

[0124] 1040 a border of a transmission timing structure, e.g. a slot border, or within a slot, for example between symbols Some tuning of radio circuitry, e.g. for receiving and / or transmitting, may be 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

[0125] 1045 to cover retuning time; however, circuitry may be adapted to switch sufficiently quickly to essentially be instantaneous; this may in particular be the case when digital reception beamforming is used to switch reception beams for switching received beams. 1050 A reference beam may be a beam comprising reference signalling, based on which for example a of beam signalling characteristics may be determined, e.g. measured and / or estimated. A signalling beam may comprise signalling like control signalling and / or data signalling and / or reference signalling. A reference beam may be transmitted by a source or transmitting radio node, in which case one or more beam

[0126] 1055 signalling characteristics may be reported to it from a receiver, e.g. a wireless device. However, in some cases it may be received by the radio node from another radio node or wireless device. In this case, one or more beam signalling characteristics may 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

[0127] 1060 of beam signalling characteristics, each subset pertaining to a different reference beam. Thus, a reference beam may be associated to different beam signalling characteristics.

[0128] A beam signalling characteristic, respectively a set of such characteristics, may

[0129] 1065 represent and / or indicate a signal strength and / or signal quality of a beam and / or a delay characteristic 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,

[0130] 1070 and / or of strongest and / or 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 reference beam it pertains to. The measurement / s may be performed by the radio node, or another node or wireless device. The use of reference signalling allows improved accuracy and / or gauging of the measurements.

[0131] 1075 In some cases, a beam and / or beam pair may be represented by a beam identity indication, e.g. a beam or beam pair number. Such an indication 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)

[0132] 1080 and / or a specific RNTI (e.g., used for scrambling a CRC for some messages 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.

[0133] 1085

[0134] A reference beam may in general be one of a set of reference beams, the second set of reference beams being associated to the set of signalling beams. The sets being associated 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

[0135] 1090 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 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.

[0136] 1095

[0137] 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 may indicate which beam is used for transmitting.

[0138] 1100 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

[0139] 1105 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

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

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

[0142] 1115 delay spread, and / or delay distribution, and / or delay spread distribution, and / or delay 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

[0143] 1120 spread, which may be weighted or unweighted. A distribution may be distribution over time / delay, e.g. 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

[0144] 1125 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 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

[0145] 1130 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 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

[0146] 1135 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 higher layer signalling like RRC or MAC signalling and / or physical layer signalling like DCI signalling.

[0147] 1140 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 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

[0148] 1145 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 mode and / or antenna profile and / or antenna port and / or precoder associated to the beam. Different beams may be provided with different

[0149] 1150 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 transmission point and / or antenna arrangement, or by different nodes and / or transmission points and / or antenna arrangements.

[0150] 1155

[0151] 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 the point of view of the referred radio node: a received beam may be a beam carrying

[0152] 1160 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 beam of a beam pair may be associated to each and / or

[0153] 1165 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 transmitted before, or in some cases simultaneous

[0154] 1170 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 the same frequency range or carriers or

[0155] 1175 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. The switching

[0156] 1180 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 1185 may 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)

[0157] 1190 is considered to 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

[0158] 1195 synchronization may be in place 8and / or 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

[0159] 1200 or scheduled timing of suitable reference signalling on the first beam pair, e.g. first received beam.

[0160] In some variants, reference signalling may be and / or comprise CSI-RS, e.g. transmitted by the network node. In other variants, the reference signalling may be

[0161] 1205 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 cyclic prefix.

[0162] 1210

[0163] Data signalling may be on a data channel, for example on a PDSCH or PSSCH or PUSCH, 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 or PUCCH, and / or comprise one

[0164] 1215 or more DCI messages or SCI messages. 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

[0165] 1220 and / or phase tracking signalling and / or cell-specific reference signalling and / or userspecific signalling, 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

[0166] 1225 as a reference and / or for training and / or for compensation. The receiver can be informed about the reference signalling by the transmitter, e.g. being configured and / or signalling with control signalling, in particular physical layer signalling and / or higher layer signalling (e.g., DCI and / or RRC signalling), and / or may determine the corresponding information itself, e.g. a network node configuring a UE to transmit

[0167] 1230 reference signalling. Reference signalling may be signalling comprising one or more reference symbols and / or structures. Reference signalling may 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

[0168] 1235 form and / or modulation and / or timing) of reference signalling are available for both transmitter and receiver of the signalling (e.g., due to being predefined and / or configured or configurable and / or being communicated). Different types of reference signalling may be considered, e.g. pertaining to uplink, downlink or sidelink, cellspecific (in particular, cell-wide, e.g., CRS) or device or user specific (addressed to a

[0169] 1240 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 (e.g., SRS or pilot signalling) and / or phase-related, etc.

[0170] References to specific resource structures like an allocation unit and / or block symbol

[0171] 1245 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 numerology, which may be predefined and / or configured or configurable. A transmission timing structure may represent a time interval, which may cover one or more symbols. Some examples of a transmission timing structure are transmission

[0172] 1250 time interval (TTI), subframe, slot and mini-slot. A slot may comprise a predetermined, e.g. predefined and / or configured or configurable, number of symbols, e.g. 6 or 7, or 12 or 14. A mini-slot may comprise a number of symbols (which may in particular be configurable or configured) smaller than the number of symbols of a slot, in particular 1 , 2, 3 or 4, or more symbols, e.g. less symbols than symbols in a slot. A transmission

[0173] 1255 timing structure may cover a time interval of a specific length, which may be dependent on symbol time length and / or cyclic prefix used. A transmission timing structure may pertain to, and / or cover, a specific time interval in a time stream, e.g. synchronized for communication. Timing structures used and / or scheduled for transmission, e.g. slot and / or mini-slots, may be scheduled in relation to, and / or synchronized to, a timing

[0174] 1260 structure provided and / or defined by other transmission timing structures. Such transmission timing structures may define a timing grid, e.g., with symbol time intervals within individual structures representing the smallest timing units. Such a timing grid may for example be defined by slots or subframes (wherein in some cases, subframes may be considered specific variants of slots). A transmission timing structure may

[0175] 1265 have a duration (length in time) determined based on the durations of its symbols, possibly in addition to cyclic prefix / es used. The symbols of a transmission timing structure may have the same duration, or may in some variants have different duration. The number of symbols in a transmission timing structure may be predefined and / or configured or configurable, and / or be dependent on numerology. The timing of a mini¬

[0176] 1270 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.

[0177] A transmission quality parameter may in general correspond to the number R of

[0178] 1275 retransmissions 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 PO and / or transmission power control command, TPC, step size) and / or signal quality, e.g. SNR

[0179] 1280 and / or SIR and / or SINR and / or power density and / or energy density. A transmission quality parameter may be considered an example of a KPI.

[0180] There is generally considered a program product comprising instructions adapted for causing processing and / or control circuitry to carry out and / or control any method

[0181] 1285 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.

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

[0183] 1290 carrier medium may be accessible and / or readable and / or receivable by processing or control circuitry. Storing data and / or a program product and / or code may be seen as part of carrying data and / or a program product and / or code. A carrier medium generally may comprise a guiding / transporting medium and / or a storage medium. A guiding / transporting medium may be adapted to carry and / or carry and / or store

[0184] 1295 signals, in particular electromagnetic signals and / or electrical signals and / or magnetic signals and / or optical signals. A carrier medium, in particular a guiding / transporting medium, may be adapted to guide such signals to carry them. A carrier medium, in particular a guiding / transporting medium, may comprise the electromagnetic field, e.g. radio waves or microwaves, and / or optically transmissive material, e.g. glass fiber,

[0185] 1300 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.

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

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

[0188] Moreover, there may be generally considered a method of operating an information system, the method comprising providing information. Alternatively, or additionally, an

[0189] 1310 information system adapted for providing information may be considered. Providing information may comprise providing information for, and / or to, a target system, which 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

[0190] 1315 information, and / or offering the information for such and / or for download, and / or triggering such providing, e.g. by triggering a different system or node to stream and / or transfer and / or 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 1320 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 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

[0191] 1325 target, and / or one or more parameters of transmission pertaining to the target and / or the paths or connections over which the information is provided to the target. Such parameter / s may in particular pertain to the air interface and / or radio access network and / or radio node and / or network node. Example parameters may indicate for example type and / or nature of the target, and / or transmission capacity (e.g., data rate)

[0192] 1330 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 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

[0193] 1335 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 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

[0194] 1340 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. In some variants, an interaction server (e.g., web server) of the information system may provide a user interface, and based on user

[0195] 1345 input may trigger transmitting and / or streaming 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, in particular data intended for a user of for use at a terminal, e.g. video data and / or audio data and / or

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

[0197] 1355 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 mapping to communication or data signalling and / or a data channel.

[0198] 1360 Mapping information to data signalling and / or data channel / s may be considered to refer to using the signalling / channel / s to carry the data, e.g. on higher layers of communication, with the signalling / channel / s underlying the transmission. A target indication generally may comprise different components, which may have different sources, and / or which may indicate different characteristics of the target and / or

[0199] 1365 communication path / s thereto. A format of information may be specifically selected, e.g. from a set of different formats, for information to be transmitted on an air interface and / or by a RAN as described herein. This may 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 adapted to the transmission

[0200] 1370 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 cable interfaces) and / or the intermediate system / s (if any), between the information system and / or the

[0201] 1375 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

[0202] 1380 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 operating 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.

[0203] 1385 In another approach, 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

[0204] 1390 or more modules for implementing 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

[0205] 1395 signalling carrying information, and / or operating on, and / or presenting (e.g., on a screen and / or as audio or as other form of indication), information. The information may be based on received information and / or communication signalling carrying information. Presenting information may comprise processing received information, e.g. decoding and / or transforming, in particular between different formats, and / or for

[0206] 1400 hardware used for presenting. Operating on information may be independent of 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

[0207] 1405 expected and / or received based on the target indication. Presenting and / or operating on information may generally comprise one or more processing steps, in particular decoding and / or executing and / or interpreting and / or transforming information. Operating on information may generally comprise relaying and / or transmitting the information, e.g. on an air interface, which may include mapping the information onto

[0208] 1410 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 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

[0209] 1415 terminal). The tool may generally be adapted for use on a target device, like a UE or terminal. Generally, the tool may provide multiple functionalities, 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

[0210] 1420 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 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.

[0211] 1425 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, 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

[0212] 1430 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 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.

[0213] 1435

[0214] In general, a numerology and / or subcarrier spacing may indicate the bandwidth (in frequency domain) of a subcarrier of a carrier, and / or the number of subcarriers in a carrier and / or the numbering of the subcarriers in a carrier, and / or the symbol time length. Different numerologies may in particular be different in the bandwidth of a

[0215] 1440 subcarrier. In some variants, all the subcarriers in a carrier have the same bandwidth associated to them. The numerology and / or subcarrier spacing may be different between carriers in particular regarding the subcarrier bandwidth. A symbol time length, and / or a time length of a timing structure pertaining to a carrier may be dependent on the carrier frequency, and / or the subcarrier spacing and / or the

[0216] 1445 numerology. In particular, different numerologies may have different symbol time lengths, even on the same carrier.

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

[0218] 1450 indication may 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

[0219] 1455 such processes and / or corresponding 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

[0220] 1460 that represents signalling and / or information for that channel, 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.

[0221] 1465 An antenna arrangement may comprise one or more antenna elements (radiating elements), which may be combined in antenna arrays. An antenna array or subarray may 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 subarray or element is separately

[0222] 1470 controllable, respectively that different antenna arrays are controllable separately from each other. A single antenna element / radiator may be considered the smallest example of a subarray. Examples of antenna arrays comprise one or more multiantenna panels or one or more individually controllable antenna elements. An antenna arrangement may comprise a plurality of antenna arrays. It may be considered that an

[0223] 1475 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 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. Antenna elements of an antenna

[0224] 1480 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 subarrays. 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

[0225] 1485 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 indication. However, there may be considered cases in which the informing radio node / s are not configured with such information, and / or operate transparently, not knowing the way of beamforming used. An antenna arrangement may be considered 1490 separately controllable in regard to the phase and / or amplitude / power and / or gain of a signal feed to it for transmission, and / or separately controllable antenna arrangements may comprise an independent or separate transmit and / or receive unit and / or ADC (Analog-Digital-Converter, alternatively an ADC chain) or DCA (Digital-to- Analog Converter, alternatively a DCA chain) to convert digital control information into

[0226] 1495 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; such controlling may be performed after encoding / decoding and7or after modulation symbols have been mapped to

[0227] 1500 resource elements. This may be on the level of antenna arrangements using the same ADC / DCA, e.g. one antenna element or a group of antenna elements associated to the same ADC / DCA. Digital beamforming may correspond to a scenario in which processing for beamforming is provided before feeding signalling to the ADC / DCA, e.g. by using one or more precoder / s and / or by precoding information, for example

[0228] 1505 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 may be configured or configurable, and / or be predefined. DFT

[0229] 1510 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.

[0230] A beam may be defined by a spatial and / or angular and / or spatial angular distribution

[0231] 1515 of radiation and / or a spatial angle (also referred to as solid angle) or spatial (solid) angle 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

[0232] 1520 do not come in in a reception beam, e.g. in digital postprocessing, e.g. digital beamforming. A 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

[0233] 1525 and / or reach). A beam may have a main direction, which may be defined by a main lobe (e.g., center of the 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.

[0234] 1530 bounded by one or more contiguous or contiguous regions of zero energy (or practically zero energy). A main lobe may comprise the lobe 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

[0235] 1535 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 may be swept and / or switched overtime, 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

[0236] 1540 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 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

[0237] 1545 change does not cover the main lobe after the change, e.g. at most to 50 or 25 or 10 percent.

[0238] Signal strength may be a representation of signal power and / or signal energy, e.g. as seen from a transmitting node or a receiving node. A beam with larger strength at

[0239] 1550 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 quality may in general be a representation of how well a signal may be received over

[0240] 1555 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 signal strength may pertain to, and / or may be measured with respect to,

[0241] 1560 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).

[0242] 1565 Uplink or sidelink signalling may be OFDMA (Orthogonal Frequency Division Multiple Access) or SC-FDMA (Single Carrier Frequency Division Multiple Access) signalling. Downlink signalling may in particular be OFDMA signalling. However, signalling is not limited thereto (Filter-Bank based signalling and / or Single-Carrier based signalling, e.g. SC-FDE signalling, may be considered alternatives).

[0243] 1570

[0244] 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 utilising an air interface, e.g. according to a communication standard.

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

[0246] 1580 described herein.

[0247] 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 represent an end device for communication utilising the wireless communication

[0248] 1585 network, and / or be implemented as a user equipment according to a standard. Examples of user equipments may comprise a phone like a smartphone, a personal communication device, a mobile phone or terminal, a computer, in particular laptop, a sensor or machine with radio capability (and / or adapted for the air interface), in particular for MTC (Machine-Type-Communication, sometimes also referred to M2M,

[0249] 1590 Machine-To-Machine), or a vehicle adapted for wireless communication. A user equipment or terminal may be mobile or stationary. A wireless device generally may comprise, and / or be implemented as, processing circuitry and / or radio circuitry, which may comprise one or more chips or sets of chips. The circuitry and / or circuitries may be packaged, e.g. in a chip housing, and / or may have one or more physical interfaces

[0250] 1595 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.

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

[0252] 1600 communication circuitry, with which it may be connected or connectable to another radio node and / or a core network.

[0253] Circuitry may comprise integrated circuitry. Processing circuitry may comprise one or more processors and / or controllers (e.g., microcontrollers), and / or ASICs (Application

[0254] 1605 Specific Integrated Circuitry) and / or FPGAs (Field Programmable Gate Array), or similar. It may be considered that processing circuitry comprises, and / or is (operatively) connected or connectable to one or more memories or memory arrangements. A memory arrangement may comprise one or more memories. A memory may be adapted to store digital information. Examples for memories comprise

[0255] 1610 volatile and non-volatile memory, and / or Random Access Memory (RAM), and / or Read-Only-Memory (ROM), and / or magnetic and / or optical memory, and / or flash memory, and / or hard disk memory, and / or EPROM or EEPROM (Erasable Programmable ROM or Electrically Erasable Programmable ROM).

[0256] 1615 Radio circuitry may comprise one or more transmitters and / or receivers and / or transceivers (a transceiver may operate or be operable as transmitter and receiver, and / or may comprise joint or separated circuitry for receiving and transmitting, e.g. in one package or housing), and / or may comprise one or more amplifiers and / or oscillators and / or filters, and / or may comprise, and / or be connected or connectable to

[0257] 1620 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 of an antenna array. However, in some variants, an RRH may be also be implemented as a network node, depending on the kind of

[0258] 1625 circuitry and / or functionality implemented therein. Communication circuitry may comprise radio circuitry and / or cable circuitry. Communication circuitry generally may comprise one or more interfaces, which may be air interface / s and / or cable interface / s and / or optical interface / s, e.g. laser-based.

[0259] 1630 Interface / s may be in particular packet-based. Cable circuitry and / or a cable interfaces may comprise, and / or be connected or connectable to, one or more cables (e.g., optical fiber-based and / or wire-based), which may be directly or indirectly (e.g., via one or more intermediate systems and / or interfaces) be connected or connectable to a target, e.g. controlled by communication circuitry and / or processing circuitry.

[0260] 1635

[0261] Any one or all of the modules disclosed herein may be implemented in software and / or firmware and / or hardware. Different modules may be associated to different components of a radio node, e.g. different circuitries or different parts of a circuitry. It may be considered that a module is distributed over different components and / or

[0262] 1640 circuitries. A program product as described herein may comprise the modules related to a device on which the program product is intended (e.g., a user equipment or network node) to be executed (the execution may be performed on, and / or controlled by the associated circuitry).

[0263] 1645 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 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.

[0264] 1650

[0265] A wireless communication network may be and / or comprise a Radio Access Network (RAN), which may be and / or comprise any kind of cellular and / or wireless radio network, which may be connected or connectable to a core network. The approaches described herein are particularly suitable for a 5G network, e.g. LTE Evolution and / or

[0266] 1655 NR (New Radio), respectively successors thereof. A RAN may comprise one or more network nodes, and / or one or more terminals, and / or one or more radio nodes. A network node may in particular be a radio node adapted for radio and / or wireless and / or cellular communication with one or more terminals. A terminal may be any device adapted for radio and / or wireless and / or cellular communication with or within 1660 a RAN, e.g. a user equipment (UE) or mobile phone or smartphone or computing device or vehicular communication device or device for machine-type-communication (MTC), etc. A terminal may be mobile, or in some cases stationary. A RAN or a wireless communication network may comprise at least one network node and a UE, or at least two radio nodes. There may be generally considered a wireless

[0267] 1665 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.

[0268] Transmitting in downlink may pertain to transmission from the network or network node to the terminal. Transmitting in uplink may pertain to transmission from the terminal to

[0269] 1670 the network or network node. Transmitting in sidelink may pertain to (direct) transmission from one terminal to another. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered communication directions. In some variants, uplink and downlink may also be used to described wireless communication between network nodes, e.g. forwireless backhaul and / or relay communication and / or

[0270] 1675 (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.

[0271] 1680 Control information or a control information message or corresponding signalling (control signalling) may be transmitted on a control channel, e.g. a physical control channel, which may be a downlink channel or (or a sidelink channel in some cases, e.g. one UE scheduling another UE). For example, control information / allocation information may be signaled by a network node on PDCCH (Physical Downlink Control

[0272] 1685 Channel) and / or a PDSCH (Physical Downlink Shared Channel) and / or a HARQ- specific channel. Acknowledgement signalling, e.g. as a form of control information or signalling like uplink control information / signalling, may be transmitted by a terminal on a PUCCH (Physical Uplink Control Channel) and / or PUSCH (Physical Uplink Shared Channel) and / or a HARQ-specific channel. Multiple channels may apply for

[0273] 1690 multi-component / multi-carrier indication or signalling.

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

[0275] 1695 a signalling radio node (which may be a network node, and / or a node associated to it, e.g. in a dual connectivity scenario. Subject transmission and / or subject signalling may be transmission or signalling to which ACK / NACK or acknowledgement information pertains, e.g. indicating correct or incorrect reception and / or decoding of the subject transmission or signalling. Subject signalling or transmission may in particular

[0276] 1700 comprise and / or be represented by data signalling, e.g. on a PDSCH or PSSCH, or some forms of control signalling, e.g. on a PDCCH or PSSCH, for example for specific formats.

[0277] A signalling characteristic may be based on a type or format of a scheduling grant

[0278] 1705 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 scheduling assignment. For example, if a specific format for a scheduling grant (scheduling or allocating the allocated resources) or scheduling

[0279] 1710 assignment (scheduling the subject transmission for acknowledgement signalling) is used or detected, the first or second communication resource may be used. Type of allocation may pertain to dynamic allocation (e.g., using DCI / PDCCH) or semi-static allocation (e.g., for a configured grant). Timing of acknowledgement signalling may pertain to a slot and / or symbol / s the signalling is to be transmitted. Resources used

[0280] 1715 for acknowledgement signalling may pertain to the allocated 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 transmission resource to be used may be based on implicit conditions, requiring low signalling

[0281] 1720 overhead.

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

[0283] 1725 signalling. 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 allocation configuration, e.g. indexing a table of scheduling opportunities. In some cases, a reception allocation configuration may comprise 15 or 16 scheduling opportunities. The configuration may in particular represent allocation

[0284] 1730 in time. It may be considered that the 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

[0285] 1735 a scheduling opportunity of the reception allocation configuration. 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 reception 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

[0286] 1740 opportunities may be indicated or allocated for data signalling. These approaches allow efficient and flexible scheduling, which may be semi-static, but may updated or reconfigured on useful timescales in response to changes of operation conditions.

[0287] Control information, e.g., in a control information message, in this context may in

[0288] 1745 particular be implemented as and / or represented by a scheduling assignment, which may indicate subject transmission for feedback (transmission of acknowledgement signalling), 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

[0289] 1750 signalling.

[0290] Subject transmissions may comprise one or more individual transmissions. Scheduling assignments may comprise one or more scheduling assignments. It should generally be noted that in a distributed system, subject transmissions, configuration

[0291] 1755 and / or scheduling may be provided by different nodes or devices or transmission points. Different subject transmissions may be on the same carrier or different carriers (e.g., in a carrier aggregation), and / or same or different bandwidth parts, and / or on the same or different layers or beams, e.g. in a Ml MO scenario, and / or to same or different ports. Generally, subject transmissions may pertain to different HARQ or ARQ

[0292] 1760 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 codebook may indicate a target HARQ structure. A target HARQ structure may for example indicate an intended HARQ response to a subject transmission, e.g. the number of bits and / or whether to

[0293] 1765 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.

[0294] Transmitting acknowledgement signalling, also referred to as transmitting

[0295] 1770 acknowledgement information or feedback information or simply as ARQ or HARQ feedback or feedback or reporting feedback, may comprise, and / or be based on determining correct or incorrect reception of subject transmission / s, e.g. based on error coding and / or based on scheduling assignment / s scheduling the subject transmissions. Transmitting acknowledgement information may be based on, and / or

[0296] 1775 comprise, a structure for acknowledgement information to transmit, e.g. the structure of one or more subpatterns, e.g. based on which subject transmission is scheduled for an associated subdivision. Transmitting acknowledgement 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.

[0297] 1780 In some cases, the channel may be a shared channel or data channel, e.g. utilising rate-matching of the acknowledgment information. The acknowledgement information may generally pertain to a plurality of subject transmissions, which may be on different channels and / or carriers, and / or may comprise data signalling and / or control signalling. The acknowledgment information may be based on a codebook, which may

[0298] 1785 be based on one or more size indications and / or assignment indications (representing HARQ structures), which may be received with a plurality of 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

[0299] 1790 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 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, acknowledgment information may be transmitted together with other control

[0300] 1795 information, e.g. a scheduling request and / or measurement information. Acknowledgement signalling may in some cases comprise, next to acknowledgement information, other information, e.g. control information, in particular, uplink or sidelink control information, like a scheduling request and / or measurement information, or

[0301] 1800 similar, and / or error detection and / or correction information, respectively associated bits. The payload size of acknowledgement signalling may represent the number of bits of acknowledgement information, and / or in some cases the total number of bits carried by the acknowledgement signalling, and / or the number of resource elements needed. Acknowledgement signalling and / or information may pertain to ARQ and / or

[0302] 1805 HARQ processes; an ARQ process may provide ACK / NACK (and perhaps additional feedback) feedback, and decoding may be performed on each (re-)transmission separately, without soft-buffering / soft-combining intermediate data, whereas HARQ may comprise soft-buffering / soft-combining of intermediate data of decoding for one or more (re-)transmissions.

[0303] 1810

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

[0305] 1815 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. In some cases, the subject transmission may comprise, or represent, reference signalling. For example, it may comprise DM-RS and / or pilot signalling and / or discovery signalling and / or sounding signalling and / or phase tracking signalling and / or cell-specific reference

[0306] 1820 signalling and / or user-specific signalling, in particular 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

[0307] 1825 crossing over more than one subdivision. In this case, it may be considered that the subject transmission is associated to the subdivision it ends in.

[0308] It may be considered that transmitting acknowledgement information, in particular of acknowledgement information, is based on determining whether the subject 1830 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. Acknowledgement information may generally be transmitted to a signalling radio node and / or node arrangement and / or to a network and / or network node.

[0309] 1835 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 or substructure or message like a control message may be considered a subpattern. The structure or arrangement of acknowledgement information may indicate the order,

[0310] 1840 and / or meaning, and / or mapping, and / or pattern of bits (or subpatterns of bits) of the information. The structure or mapping may in particular indicate one or more data block structures, e.g. code blocks and / or code block groups and / or transport blocks and / or messages, e.g. command messages, the acknowledgement information pertains to, and / or which bits or subpattern of bits are associated to which data block

[0311] 1845 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 configuration or structure or codebook may indicate to which process / es and / or data stream / s the information pertains. Generally, the acknowledgement information may comprise one or more subpatterns, each of which

[0312] 1850 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 nonacknowledgement, or another retransmission state like non-scheduling or nonreception, of the associated data block structure. It may be considered that a subpattern comprises one bit, or in some cases more than one bit. It should be noted

[0313] 1855 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.

[0314] An acknowledgment signalling process (providing acknowledgment information) may

[0315] 1860 be a HARQ process, and / or be identified by a process identifier, e.g. a HARQ process identifier or subidentifier. 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

[0316] 1865 bits). However, depending 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 acknowledgement information for a data block requires fewer bits than indicated as size of the subpattern. Such may for example happen if the size

[0317] 1870 is indicated by a unit size larger than required for the feedback.

[0318] Acknowledgment information may generally indicate at least ACK or NACK, e.g. pertaining to an acknowledgment signalling process, or an element of a data block structure like a data block, subblock group or subblock, or a message, in particular a

[0319] 1875 control message. Generally, to an acknowledgment signalling process there may be associated one 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.

[0320] 1880

[0321] An acknowledgment signalling process may determine correct or incorrect reception, and / or corresponding acknowledgement information, of a data block like a transport 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

[0322] 1885 and / or subblock group / s. Acknowledgement information (determined by an acknowledgement signalling process) may pertain to the data block as a whole, and / or to one or more subblocks or subblock groups. A code block may be considered an example of a subblock, whereas a code block group may be considered an example of a subblock group. Accordingly, the associated subpattern may comprise one or

[0323] 1890 more bits indicating reception status or feedback of the data block, and / or one or more bits indicating reception status or feedback of one or more subblocks or subblock groups. Each subpattern or bit of the subpattern may be associated and / or mapped to a specific data block or subblock or subblock group. In some variants, correct reception for a data block may be indicated if all subblocks or subblock groups are

[0324] 1895 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 subblocks or subblock groups. The smallest structure (e.g. subblock / subblock group / data block) the subpattern provides acknowledgement information for and / or is associated to may be considered its

[0325] 1900 (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, in some variants higher resolution (e.g., subblock or subblock group resolution) may

[0326] 1905 be provided by the subpattern. A subpattern may generally comprise one or more bits indicating 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.

[0327] 1910 A subblock and / or subblock group may comprise information bits (representing the data 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

[0328] 1915 bit / s may be determined based on the information bits and / or error detection bits and / or error correction bits of the 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

[0329] 1920 particular for forward error correction (FEC), e.g. LDPC or polar coding and / or turbo coding. Generally, the error correction coding of a 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

[0330] 1925 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 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

[0331] 1930 transport block, which in this context represents information bits without the error coding bits described herein, although higher layer error handling information may be 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.

[0332] 1935

[0333] 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 subblock. An error correction coding scheme may be used for determining the error correction bits, e.g. based on LDPC or polar coding or Reed-Mueller coding. In

[0334] 1940 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 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

[0335] 1945 covered by the error correction scheme or corresponding error correction bit / s. A code block group may comprise one or more code blocks. In some variants, no additional error detection bits and / or error correction bits are applied, however, it may be considered to apply either or both. A transport block may comprise one or more code block groups. It may be considered that no additional error detection bits and / or error

[0336] 1950 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 coding, and the transport block may comprise only additional error detection coding bits, but no additional error correction coding. This may particularly be true if the transport block size is larger than the code

[0337] 1955 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 code block group or a data block like a transport block. In such cases, it may indicate ACK, if all subblocks

[0338] 1960 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 it actually has been correctly received, but also if it can be correctly reconstructed based on soft-

[0339] 1965 combining and / or the error correction coding. Asubpattern / 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

[0340] 1970 pertains, 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

[0341] 1975 associated acknowledgment signalling processes) 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

[0342] 1980 of a data block structure (e.g., data block or subblock or subblock 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.

[0343] 1985 ACK / NACK may be represented by one bit, or by more than one bit, e.g. to improve disambiguity of bit sequences representing ACK or NACK, and / or to improve transmission reliability.

[0344] The acknowledgement information or feedback information may pertain to a plurality

[0345] 1990 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 structures, and / or the corresponding blocks and / or signalling, may be scheduled for simultaneous transmission, e.g. for the same transmission timing structure, in particular within the same slot or subframe, and / or on the same symbol / s. However,

[0346] 1995 alternatives with scheduling for non-simultaneous transmission may be considered. For example, the acknowledgment information may pertain to data blocks scheduled for different transmission timing structures, e.g. different slots (or mini-slots, or slots and mini-slots) or similar, which may correspondingly be received (or not or wrongly received). Scheduling signalling may generally comprise indicating resources, e.g. 2000 time and / or frequency resources, for example for receiving or transmitting the scheduled signalling.

[0347] Signalling may generally be considered to represent an electromagnetic wave structure (e.g., over a time interval and frequency interval), which is intended to convey

[0348] 2005 information to at least one specific or generic (e.g., anyone who might pick up the signalling) target. A process of signalling may comprise transmitting the signalling. Transmitting signalling, in particular control signalling or communication signalling, e.g. comprising or representing acknowledgement signalling and / or resource requesting information, may comprise encoding and / or modulating. Encoding and / or

[0349] 2010 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 detection coding may comprise, and / or be based on, parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check). Forward error correction coding may comprise and / or be based on for example turbo coding

[0350] 2015 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 detection coding and

[0351] 2020 forward error correction. Coded bits may refer to information bits (also called systematic bits) plus coding bits.

[0352] Communication signalling may comprise, and / or represent, and / or be implemented as, data signalling, and / or user plane signalling. Communication signalling may be

[0353] 2025 associated to a data channel, e.g. a physical downlink channel or physical uplink channel or physical 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.

[0354] 2030

[0355] An indication generally may explicitly and / or implicitly indicate the information it represents and / or indicates. Implicit indication may for example be based on position and / or resource used for transmission. Explicit indication may for example be based on a parametrisation with one or more parameters, and / or one or more index or

[0356] 2035 indices, and / or one or more bit patterns representing the information. It may in particular be considered that control signalling as described herein, based on the utilised resource sequence, implicitly indicates the control signalling type.

[0357] A resource element may generally describe the smallest individually usable and / or

[0358] 2040 encodable and / or decodable and / or modulatable and / or demodulatable timefrequency resource, and / or may describe a time-frequency resource covering a symbol time length in time and a subcarrier in frequency. A signal may be allocatable and / or allocated to a resource element. A subcarrier may be a subband of a carrier, e.g. as defined by a standard. A carrier may define a frequency and / or frequency band

[0359] 2045 for transmission and / or reception. In some variants, a signal (jointly encoded / modulated) may cover more than one resource elements. A resource element may generally be as defined by a corresponding standard, e.g. NR or LTE. As symbol time length and / or subcarrier spacing (and / or numerology) may be different between different symbols and / or subcarriers, different resource elements may have

[0360] 2050 different extension (length / width) in time and / or frequency domain, in particular resource elements pertaining to different carriers.

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

[0362] 2055 transmitted and / or received, and / or be intended for transmission and / or reception.

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

[0364] 2060 signalling may be on a data channel or control channel, e.g. a physical channel, in particular a physical uplink shared channel (like PUSCH) or a sidelink data or shared channel, or a physical uplink control channel (like PUCCH) or a sidelink control channel. If the starting symbol is associated to control signalling (e.g., on a control channel), the control signalling may be in response to received signalling (in sidelink

[0365] 2065 or downlink), e.g. representing acknowledgement signalling associated thereto, which may be HARQ or ARQ 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,

[0366] 2070 e.g. a PDSCH (Physical Downlink Shared Channel). A starting symbol may be determined based on, and / or in relation to, such an ending symbol.

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

[0368] 2075 the configuration. Configuring may be done by another device, e.g., a network node (for example, a radio node of the network like a base station or eNodeB) or network, in which case it may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and / or comprise one or more instruction pertaining to a configuration, e.g. a

[0369] 2080 configuration for transmitting and / or receiving on allocated resources, in particular frequency resources. A radio node may configure itself, e.g., based on configuration data received from a network or network node. A network node may utilise, and / or be adapted to utilise, its circuitry / ies for configuring. Allocation information may be considered a form of configuration data. Configuration data may comprise and / or be

[0370] 2085 represented by configuration information, and / or one or more corresponding indications and / or message / s

[0371] Generally, configuring may include determining configuration data representing the configuration and providing, e.g. transmitting, it to one or more other nodes (parallel

[0372] 2090 and / or sequentially), which may transmit it further to the radio node (or another node, which may be repeated until it reaches the wireless device). Alternatively, or additionally, configuring a radio node, e.g., by a network node or other device, may include receiving configuration data and / or data pertaining to configuration data, e.g., from another node like a network node, which may be a higher-level node of the

[0373] 2095 network, and / or transmitting received configuration data to the radio node. Accordingly, determining a configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities, which may be able to communicate via a suitable interface, e.g., an X2 interface in the case of LTE or a corresponding interface for NR. Configuring a terminal may comprise scheduling

[0374] 2100 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.

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

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

[0377] 2115 a symbol time interval assigned to a symbol n+1.

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

[0379] 2120

[0380] A resource structure may general represent a structure in time and / or frequency domain, in particular representing a time interval and a frequency interval. A resource structure may comprise and / or be comprised of resource elements, and / or the time interval of a resource structure may comprise and / or be comprised of symbol time

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

[0382] 2130 than a slot or PRB.

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

[0384] 2135 regulations and / or a standard. A bandwidth part may be configured or configurable to a radio 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

[0385] 2140 RAN). It may be considered that a bandwidth part comprises one or more resource blocks 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.

[0386] A carrier may generally represent a frequency range or band and / or pertain to a

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

[0388] 2150 frequency domain.

[0389] 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 millimeter waves, in particular above one of the thresholds 10 GHz or 20

[0390] 2155 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.

[0391] 2160

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

[0393] 2165 may be called LBT carrier), e.g., an unlicensed carrier. It may be considered that the carrier is part of a carrier aggregate.

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

[0395] 2175 communication / transmission and DL communication / transmission, e.g., in TDD- based approaches.

[0396] A channel may generally be a logical, transport or physical channel. A channel may comprise and / or be arranged on one or more carriers, in particular a plurality of

[0397] 2180 subcarriers. A channel carrying and / or for carrying control signalling / control information may be considered 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 signalling / user information may be considered a data channel, in particular if it is a physical layer channel and / or if it carries user plane

[0398] 2185 information. A channel may be defined for a specific communication direction, or for two complementary communication directions (e.g., UL and DL, or sidelink in two directions), in which case it may be considered to have two component channels, one for each direction. Examples of channels comprise a channel for low latency and / or high reliability transmission, in particular a channel for Ultra-Reliable Low

[0399] 2190 Latency Communication (URLLC), which may be for control and / or data.

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

[0401] 2195 interval having a symbol time length in relation to frequency domain. A symbol time length may be dependent on a carrier frequency and / or bandwidth and / or numerology and / or subcarrier spacing of, or associated to, a symbol. Accordingly, different symbols may have different symbol time lengths. In particular, numerologies with different subcarrier spacings may have different symbol time length. Generally, a

[0402] 2200 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) between two UEs and / or terminals, in which data is transmitted between the

[0403] 2205 participants (UEs and / or terminals) via the communication channel, e.g. directly and / or without being relayed via a network node. A sidelink may be established only and / or directly via air interface / s of the participant, which may be directly linked via the sidelink communication channel. In some variants, sidelink communication may be performed without interaction by a network node, e.g. on fixedly defined resources

[0404] 2210 and / or on resources negotiated between the participants. Alternatively, or additionally, it may be considered that a network node provides some control functionality, e.g. by configuring resources, in particular one or more resource pool / s, for sidelink communication, and / or monitoring a sidelink, e.g. for charging purposes.

[0405] 2215 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-lnfrastructure) and / or V2P (Vehicle-to-Person). Any device

[0406] 2220 adapted for sidelink communication may be considered a user equipment or terminal.

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

[0408] 2225 indication, and / or a PSSCH (Physical Sidelink Shared CHannel, which for example may carry data and / or acknowledgement signalling). It may be considered that a sidelink communication channel (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

[0409] 2230 may share a (physical) channel and / or resources, in particular in frequency domain and / or related to a frequency resource like a carrier) of a sidelink, such that two or more participants transmit thereon, e.g. simultaneously, and / or time-shifted, and / or there may be associated specific channels and / or resources to specific participants, so that for example only one participant transmits on a specific channel or on a

[0410] 2235 specific resource or specific resources, e.g., in frequency domain and / or related to one or more carriers or subcarriers. 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

[0411] 2240 Duplex) and / or FDD (Frequency Division Duplex) technology, e.g. as configured by a network node, and / or preconfigured and / or negotiated between the participants. A user equipment may be considered to be adapted for sidelink communication if it, and / or its radio circuitry and / or processing circuitry, is adapted for utilising a sidelink, e.g. on one or more frequency ranges and / or carriers and / or in one or more formats,

[0412] 2245 in particular according to a specific standard. It may be generally considered that a Radio Access Network is defined by two participants of a sidelink communication. Alternatively, or additionally, a Radio Access Network may be represented, and / or defined with, and / or be related to a network node and / or communication with such a node.

[0413] 2250

[0414] Communication or communicating may generally comprise transmitting and / or receiving signalling. Communication on a sidelink (or sidelink signalling) may comprise utilising the sidelink for communication (respectively, for signalling). Sidelink transmission and / or transmitting on a sidelink may be considered to

[0415] 2255 comprise transmission utilising the sidelink, e.g. associated resources and / or transmission formats and / or circuitry and / or the air interface. Sidelink reception and / or receiving on a sidelink may be considered to comprise reception utilising the sidelink, e.g. associated resources and / or transmission formats and / or circuitry and / or the air interface. Sidelink control information (e.g., SCI) may generally be

[0416] 2260 considered to comprise control information transmitted utilising a sidelink.

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

[0418] 2265 carriers for at least one direction of transmission (e.g. DL and / or UL), as well as to the aggregate of carriers. A corresponding communication link may be referred to as carrier aggregated communication link or CA communication link; carriers in a carrier aggregate may be referred to as component carriers (CC). In such a link, data may be transmitted over more than one of the carriers and / or all the carriers of the carrier

[0419] 2270 aggregation (the aggregate of carriers). A carrier aggregation may comprise one (or more) dedicated control carriers and / or primary carriers (which may e.g. be referred to as primary component carrier or PCC), over which control information may be transmitted, wherein the control information may refer to the primary carrier and other carriers, which may be referred to as secondary carriers (or secondary component

[0420] 2275 carrier, SCC). However, in some approaches, control information may be sent over more than one carrier of an aggregate, e.g. one or more PCCs and one PCC and one or more SCCs.

[0421] A transmission may generally pertain to a specific channel and / or specific resources,

[0422] 2280 in particular with a starting symbol and ending symbol in time, covering the interval therebetween. A scheduled transmission may be a transmission scheduled and / or expected and / or for which resources are scheduled or provided or reserved. However, not every scheduled transmission has to be realized. For example, a scheduled downlink transmission may not be received, or a scheduled uplink transmission may

[0423] 2285 not be transmitted due to power limitations, or other influences (e.g., a channel on an unlicensed carrier being occupied). A transmission may be scheduled for a transmission timing substructure (e.g., a mini-slot, and / or covering only a part of a transmission timing structure) within a transmission timing structure like a slot. A border symbol may be indicative of a symbol in the transmission timing structure at

[0424] 2290 which the transmission starts or ends.

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

[0426] 2295 being configured. Configured or configurable may be considered to pertain to the corresponding information being set / configured, e.g. by the network or a network node.

[0427] A configuration or schedule, like a mini-slot configuration and / or structure

[0428] 2300 configuration, may schedule transmissions, e.g. for the time / transmissions it is valid, and / or transmissions may be scheduled by separate signalling or separate configuration, e.g. separate RRC 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 2305 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 higher layer signalling like MAC (Medium Access Control) signalling or RRC layer signalling. The higher the layer of signalling is, the less frequent / the more time / resource consuming it may be

[0429] 2310 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.

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

[0431] 2315 physical uplink control channel, or a physical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and / or may pertain to a specific cell and / or carrier aggregation. A corresponding configuration, e.g. scheduling configuration or symbol configuration may pertain to such channel, cell and / or carrier aggregation. It may be considered that the scheduled transmission represents transmission on a physical channel, in

[0432] 2320 particular a shared physical channel, for example a physical uplink shared channel or physical downlink shared channel. For such channels, semi-persistent configuring may be particularly suitable.

[0433] Generally, a configuration may be a configuration indicating timing, and / or be

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

[0435] 2330 A control region of a transmission timing structure may be an interval in time and / or frequency domain for intended or scheduled or reserved for control signalling, in particular downlink control signalling, and / or for a specific control channel, e.g. a physical downlink control channel like PDCCH. The interval may comprise, and / or consist of, a number of symbols in time, which may be configured or configurable, e.g.

[0436] 2335 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. 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

[0437] 2340 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 identifiers, and / or be represented and / or associated to a CORESET and / or a search space. A search space may comprise and / or be associated to a control region or CORESET and / or time

[0438] 2345 and / or frequency resources, which may be configured and / or indicated for reception of control information and / or signalling on a (e.g., physical) control channel like PDCCH or PSCCH. To a search space, additional parameters and / or conditions may be provided and / or associated, e.g. defining and / or configuring and / or indicating and / or specifying control signalling or control information to search for and / or monitor

[0439] 2350 in the search space, and / or associated control region or CORESET or resources. For example, one or more signalling characteristics of such control signalling and / or control information may be provided, e.g. signalling format and / or possible position within the resources and / or repetition and / or coding and / or priority between different types or formats and / or hashing function.

[0440] 2355

[0441] 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 numerology and / or carrier may be configurable. The numerology may be the numerology to be used for the scheduled transmission.

[0442] 2360

[0443] A transmission timing structure may comprise a plurality of symbols, and / or define an interval comprising several symbols (respectively their associated time intervals). In the context of this disclosure, it should be noted that a reference to a symbol for ease of reference may be interpreted to refer to the time domain projection or time interval

[0444] 2365 or time component or duration or length in time of the symbol, unless it is clear from the context that the frequency domain component also has to be considered. Examples of transmission timing structures include slot, subframe, mini-slot (which also may be considered a substructure of a slot), slot aggregation (which may comprise a plurality of slots and may be considered a superstructure of a slot),

[0445] 2370 respectively their time domain component. A transmission timing structure may generally comprise a plurality of symbols defining the time domain extension (e.g., interval or length or duration) of the transmission timing structure, and arranged neighboring to each other in a numbered sequence. A timing structure (which may also be considered or implemented as synchronisation structure) may be defined by

[0446] 2375 a succession of such transmission timing structures, which may for example define a timing grid with symbols representing the smallest grid structures. A transmission timing structure, and / or a border symbol or a scheduled transmission may be determined or scheduled in relation to such a timing grid. A transmission timing structure of reception may be the transmission timing structure in which the scheduling

[0447] 2380 control signalling is received, e.g. in relation to the timing grid. A transmission timing structure may in particular be a slot or subframe or in some cases, a mini-slot.

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

[0449] 2385 (Sidelink Control Information) signalling. Feedback signalling may in particular comprise and / or represent acknowledgement signalling and / or acknowledgement information and / or measurement reporting.

[0450] Signalling utilising, and / or on and / or associated to, resources or a resource structure

[0451] 2390 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 associated to one or more different channels and / or types of signalling and / or comprise one or more holes (resource element / s not

[0452] 2395 scheduled for transmissions or reception of transmissions). A resource substructure, e.g. a feedback resource structure, may generally be continuous in time and / or frequency, within the associated intervals. It may be considered that a substructure, in particular a feedback resource structure, represents a rectangle filled with one or more resource elements in time / frequency space. However, in some cases, a

[0453] 2400 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.

[0454] 2405 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.).

[0455] 2410

[0456] In the context of this disclosure, there may be distinguished between dynamically scheduled or aperiodic transmission and / or configuration, and semi-static or semi- persistent or periodic transmission and / or configuration. The term “dynamic” or similar terms may generally pertain to configuration / transmission valid and / or scheduled

[0457] 2415 and / or configured for (relatively) short timescales and / or a (e.g., predefined and / or configured and / or limited 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

[0458] 2420 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 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

[0459] 2425 be configured with, higher-layer signalling, in particular RCL layer signalling and / or RRC signalling and / or MAC signalling.

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

[0461] 2430 to provide a thorough understanding of the technique presented herein. It will be apparent to one skilled in the art that the present concepts and aspects may be practiced in other variants and variants that depart from these specific details.

[0462] For example, the concepts and variants are partially described in the context of Long

[0463] 2435 Term Evolution (LTE) or LTE-Advanced (LTE-A) or New Radio mobile or wireless communications technologies; however, this does not rule out the use of the present concepts and aspects in connection with additional or alternative mobile communication technologies such as the Global System for Mobile Communications (GSM) or IEEE standards as IEEE 802.11 ad or IEEE 802.11 ay. While described

[0464] 2440 variants may pertain to certain Technical Specifications (TSs) of the Third Generation Partnership Project (3GPP), it will be appreciated that the present approaches, concepts and aspects could also be realized in connection with different Performance Management (PM) specifications.

[0465] 2445 Moreover, those skilled in the art will appreciate that the services, functions and steps explained herein may be implemented using software functioning in conjunction with a programmed microprocessor, or using an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA) or general purpose computer. It will also be appreciated that while the variants

[0466] 2450 described herein are elucidated in the context of methods and devices, the concepts and aspects presented herein may also be embodied in a program product as well as in a system comprising control circuitry, e.g. a computer processor and a memory coupled to the processor, wherein the memory is encoded with one or more programs or program products that execute the services, functions and steps disclosed herein.

[0467] 2455

[0468] It is believed that the advantages of the aspects and variants presented herein will be fully 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

[0469] 2460 described herein or without sacrificing all of its advantageous effects. The aspects presented herein can be varied in many ways.

[0470] Some useful abbreviations comprise

[0471] 2465 Abbreviation Explanation

[0472] ACK / NACK Acknowledgment / Negative Acknowledgement

[0473] Al Artificial Intelligence

[0474] ARQ Automatic Repeat reQuest

[0475] BER Bit Error Rate

[0476] 2470 BLER Block Error Rate

[0477] BPSK Binary Phase Shift Keying

[0478] BWP Bandwidth Part

[0479] CAZAC Constant Amplitude Zero Cross Correlation

[0480] CB Code Block 2475 CBG Code Block Group

[0481] CCE Control Channel Element

[0482] CDM Code Division Multiplex

[0483] CM Cubic Metric

[0484] CORESET Control Resource Set

[0485] 2480 CQI Channel Quality Information

[0486] CRB Common Resource Block

[0487] CRC Cyclic Redundancy Check

[0488] CRS Common reference signal

[0489] CSI Channel State Information

[0490] 2485 CSI-RS Channel state information reference signal

[0491] DAI Downlink Assignment Indicator

[0492] DCI Downlink Control Information

[0493] DFT Discrete Fourier Transform

[0494] DFTS-FDM DFT-spread-FDM

[0495] 2490 DM(-)RS Demodulation reference signal(ing) eMBB enhanced Mobile BroadBand

[0496] EVM Error Vector Magnitude

[0497] FDD Frequency Division Duplex

[0498] FDE Frequency Domain Equalisation

[0499] 2495 FDF Frequency Domain Filtering

[0500] FDM Frequency Division Multiplex

[0501] FE (radio) Front End

[0502] FR1 Frequency Range 1 (for NR)

[0503] FR2 Frequency Range 2 (for NR)

[0504] 2500 GCS Golay Complementary Sequence(s)

[0505] HARQ Hybrid Automatic Repeat Request

[0506] IAB Integrated Access and Backhaul

[0507] IE Information Element

[0508] IFFT Inverse Fast Fourier Transform

[0509] 2505 IR Impulse Response

[0510] ISI Inter Symbol Interference

[0511] MBB Mobile Broadband

[0512] MCS Modulation and Coding Scheme Ml MO Multiple-input-multiple-output

[0513] 2510 ML Machine Learning

[0514] MPR Maximum Power Reduction

[0515] MRC Maximum-ratio combining

[0516] MRT Maximum-ratio transmission

[0517] MU-MIMO Multiuser multiple-input-multiple-output

[0518] 2515 NN Neural Network

[0519] OFDM / A Orthogonal Frequency Division Multiplex / Multiple Access PA Power Amplifier

[0520] PAPR Peak to Average Power Ratio

[0521] PBCH Physical Broadcast CHannel

[0522] 2520 PDCCH Physical Downlink Control Channel

[0523] PDSCH Physical Downlink Shared Channel

[0524] PRACH Physical Random Access CHannel

[0525] PRB Physical Resource Block

[0526] PUCCH Physical Uplink Control Channel

[0527] 2525 PUSCH Physical Uplink Shared Channel

[0528] PSD Power Spectral Density

[0529] (P)SCCH (Physical) Sidelink Control Channel

[0530] PSS Primary Synchronisation Signal(ing)

[0531] (P)SSCH (Physical) Sidelink Shared Channel

[0532] 2530 PT(-)RS Phase-Tracking RS

[0533] QAM Quadrature Amplitude Modulation

[0534] OCC Orthogonal Cover Code

[0535] QPSK Quadrature Phase Shift Keying

[0536] PSD Power Spectral Density

[0537] 2535 RAN Radio Access Network

[0538] RAT Radio Access Technology

[0539] RB Resource Block

[0540] REG Resource Element Group

[0541] RNTI Radio Network Temporary Identifier

[0542] 2540 RRC Radio Resource Control

[0543] RS Reference Signal(ing)

[0544] RX Receiver, Reception, Reception-related / side SA Scheduling Assignment

[0545] SC-FDE Single Carrier Frequency Domain Equalisation

[0546] 2545 SC-FDM / A Single Carrier Frequency Division Multiplex / Multiple Access

[0547] SCI Sidelink Control Information

[0548] SIB System Information Block

[0549] SI NR Signal-to-interference-plus-noise ratio

[0550] SIR Signal-to-interference ratio

[0551] 2550 SNR Signal-to-noise-ratio

[0552] SR Scheduling Request

[0553] SRS Sounding Reference Signal(ing)

[0554] SSS Secondary Synchronisation Signal(ing)

[0555] SVD Singular-value decomposition

[0556] 2555 TB Transport Block

[0557] TDD Time Division Duplex

[0558] TDM Time Division Multiplex

[0559] TX Transmitter, Transmission, Transmission-related / side

[0560] UCI Uplink Control Information

[0561] 2560 UE User Equipment

[0562] URLLC Ultra Low Latency High Reliability Communication

[0563] VL-MIMO Very-large multiple-input-multiple-output

[0564] VRB Virtual Resource Block

[0565] ZF Zero Forcing

[0566] 2565 ZP Zero-Power, e.g. muted CSI-RS symbol

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

Claims

Claims2570 1. Method of operating a receiver radio node (100) in a wireless communication network, the receiver radio node (100) being adapted for receiving signalling based on at least one Machine Learning, ML, model, the method comprising performing signalling operation based on received monitoring signalling.2575 2. Receiver radio node (100) for a wireless communication network, the receiver radio node (100) being adapted for receiving signalling based on at least one Machine Learning, ML, model, and further being adapted for performing signalling operation based on received monitoring signalling.2580 3. Method of operating a transmitter radio node (10) in a wireless communication network, the method comprising transmitting monitoring signalling based on a monitoring configuration.

4. Transmitter radio node (10) for a wireless communication network, the transmitter2585 radio node (10) being adapted for transmitting monitoring signalling based on a monitoring configuration.

5. Method or device according to one of the preceding claims, wherein the monitoring signalling is transmitted for monitoring the at least one ML model, and / or wherein the2590 monitoring configuration pertains to at least on ML model.

6. Method or device according to one of the preceding claims, wherein the monitoring configuration is configured to a transmitter radio node (10) by a receiver radio node (100).25957. Method or device according to one of the preceding claims, wherein signalling operation is performed based on monitoring the monitoring signalling and / or monitoring reception of the monitoring signalling.2600 8. Method or device according to one of the preceding claims, wherein signalling operation comprise switching a ML model, or activating or deactivating a ML model,and / or adapting transmission and / or reception and / or a receiver, and / or initiating retraining of the ML model.2605 9. Program product comprising instructions causing processing circuitry to control and / or perform a method according to one of claims 1 , 3, or 5 to 8.

10. Carrier medium arrangement carrying and / or storing a program product according to claim 9.

Images