Random access in wireless communication network

Abstract

The disclosure pertains to a method of operating a wireless device in a wireless communication network, the method comprising transmitting random access signalling at a transmission random access opportunity based on a first random access configuration indicating a set of first random access opportunities, and based on a second random access configuration indicating a set of second random access opportunities, wherein the transmission random access opportunity is a first random access opportunity or a second random access opportunity determined based on validating one or more of the first and / or second random access opportunities The disclosure also pertains to related devices and methods.

Description

[0001] Random access in wireless communication network

[0002] Technical field

[0003] This disclosure pertains to wireless communication, in particular to random access.

[0004] Background

[0005] For future wireless communication systems, the introduction of full duplex functionality is considered, wherein frequency spectrum, e.g., a carrier or bandwidth part, may be used 5 for transmission and reception at the same time, which may allow better use of available frequency resources, or allow optimising latency. However, introduction of full duplex brings additional challenges and issues that need to be addressed.

[0006] Summary

[0007] It is an object of this disclosure to provide approaches for improved random access, in 10 particular in the context of full duplex operation, e.g., on a carrier and / or bandwidth part, and / or in TDD. The approaches described may be utilised for one or more different frequencies ranges. For example, they may be implemented for frequency ranges (e.g., carrier bandwidth and / or system bandwidth) for communication signalling of 1 GHz or more, 2GHz or more, 5 GHz or more, or 6 GHz or more, or 10 GHz or more, and / or for 15 millimeter wave communication, in particular for radio carrier frequencies around and / or above 52.6 GHz, which may be considered high radio frequencies (high frequency) and / or millimetre waves. The carrier frequency / ies 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 20

[0008] 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 wide-band, e.g. with a carrier bandwidth (or bandwidth or carrier aggregation) of 400MHz or more, in 25 particular 1 GHz or more, or 2 GHz or more, or even larger, e.g. 6 GHz or more, or 8 GHz or more; the scheduled or allocated bandwidth may be the carrier bandwidth, or be smaller, e.g. depending on channel and / or procedure. In some cases, operation may be based on an OFDM wave- form or a SC-FDM wave- form (e.g., downlink and / or uplink), in particular a FDF-SC-FDM-based wave-form. However, operation based on a 30 single carrier wave-form, e.g. SC-FDE (which may be pulse-shaped or Frequency Domain Filtered, e.g. based on modulation scheme and / or MGS), may be considered for downlink and / or uplink. In general, different wave-forms may be used for different communication directions. Communicating using or utilising a carrier and / or beam may correspond to operating using or utilising the carrier and / or beam, and / or may comprise transmitting 35 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 960 kHz, or 1920 kHz, e.g. representing the bandwidth of a 40 subcarrier or equivalent.

[0009] The approaches are particularly advantageously implemented in a future 6th Generation (6G) telecommunication network or 6G radio access technology or network (RAT / RAN), in particular according to 3GPP (3rd Generation Partnership Project, a standardisation organization). A suitable RAN may in particular be a RAN according to NR, for example 45 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 wireless device in a wireless communication network. The method comprises transmitting random access signalling (RA signalling) at a transmission random access opportunity (transmission RO) based on a first ran- 50 dom access configuration (first RA configuration) indicating a set of first random access opportunities (first ROs), and based on a second random access configuration (second RA configuration) indicating a set of second random access opportunities (second ROs), wherein the transmission random access opportunity is a first random access opportunity or a second random access opportunity determined based on validating one or more of 55 the first and / or second random access opportunities.

[0011] Moreover, there is discussed a wireless device for a wireless communication network. The wireless device is adapted for transmitting random access signalling at a transmission random access opportunity based on a first random access configuration indicating a set of first random access opportunities, and based on a second random access configuration 60 indicating a set of second random access opportunities, wherein the transmission random access opportunity is a first random access opportunity or a second random access opportunity determined based on validating one or more of the first and / or second random access opportunities.

[0012] A method of operating a network node in a wireless communication network is also pro- 65 posed. The method comprises receiving, from a wireless device, random access signalling at a transmission random access opportunity according to a first random access configuration indicating a set of first random access opportunities, and according to a second random access configuration indicating a set of second random access opportunities, wherein the transmission random access opportunity is a first random access opportunity or a 70 second random access opportunity determined according to validating one or more of the first and / or second random access opportunities.

[0013] There is also described a network node for a wireless communication network. The network node is adapted for receiving, from a wireless device, random access signalling at a transmission random access opportunity according to a first random access configuration 75 indicating a set of first random access opportunities, and according to a second random access configuration indicating a set of second random access opportunities, wherein the transmission random access opportunity is a first random access opportunity or a second random access opportunity determined according to validating one or more of the first and / or second random access opportunities. 80

[0014] The network node may configure, and / or be adapted to configure, the wireless device with the first RA configuration and / or second RA configuration, e.g., with corresponding signalling. In general, the network node may be considered aware of the first RA configuration and / or the second RA configuration, e.g., due to information provided by another network node, and / or determining the conhguration / s itself, and / or due to oper- 85 ating based on a common predefinition (e.g., according to a standard of communication).

[0015] Receiving RA signalling at a transmission RO may comprise, and / or be based on monitoring resources of the RO for such signalling, and / or demodulating and / or decoding the signalling, and / or associating the signalling with a random access procedure and / or a UE, and / or one of the first and second configurations, e.g., according to one or more 90 validation rule / s. A second RA configuration may be based on, and / or comprised in, a SBFD configuration, or an UL subband configuration, which may configure SBFD-related parameters and / or operation for a wireless device or UE. The transmission random access opportunity may be a RO on which RA signalling is actually transmitted, and / or expected to be received and / or monitored for by the receiver / network node. Transmis- 95 sion on a second RO may correspond to transmission on a UL subband and / or in SBFD operation or mode.

[0016] Validating may be based on one or more validation rules, which may be indicated with the second RA configuration. The rule / s may be configured or configurable, and / or predefined. Thus, suitable validation behaviour may be provided with a desirable amount 100 of flexibility.

[0017] The transmission random access opportunity may be a first random access opportunity based on a fallback rule. Prioritising second ROs may be considered, e.g., such that a first RO is used after one or more valid second ROs have been used for unsuccessful random access procedure, and / or a significant number (e.g., X) of second ROs are determined to 105 be invalid. Validating may comprise and / or be based on determining a second random access opportunity to be valid if it does not collide with a first random access opportunity. Colliding may pertain to overlapping in time domain and / or frequency domain and / or format (e.g., it may be considered to collide if the formats are non-orthogonal, at least non-pseudo 110 orthogonal), and / or if the second RO starts or ends or is located in the same subslot or slot or subframe as the first RO.

[0018] In particular, validating may comprise determining a second random access opportunity to be valid if it does not collide with a first random access opportunity in time domain and / or frequency domain. 115

[0019] Transmitting may be in Subband Full Duplex, SBFD, operation, in particular in a SBFD slot and / or subframe and / or one or more SBFD symbols. The network node may receive the signalling in SBFD mode.

[0020] It may be considered that validating may comprise determining a second random access opportunity to be valid if it does not start and / or end and / or is not located in the 120 same slot and / or subframe and / or subslot and / or transmission timing structure as a first random access opportunity; this may be considered a form of collision-based validation.

[0021] The second random access configuration may pertain to Subband Full Duplex, SBFD, operation, e.g., indicating second ROs to be in SBFD slots and / or symbols and / or subframes. 125

[0022] It may be considered that the transmission random access opportunity may be a random access opportunity determined valid, e.g., based on one or more validation rules. One or more ROs, e.g., first and / or second ROs, may be determined invalid. Invalid ROs may be earlier in time domain that the transmission RO.

[0023] Transmitting random access signalling may be based on triggering of a random access 130 procedure, and / or it may be part of an random access procedure. The wireless device and / or network node may be adapted and / or configured for operation in TDD mode and / or SBFD mode. The network node may be adapted to configure the wireless device with the first RA configuration and / or the second RA configuration and / or may transmit correspoding signalling, and / or may configure the wireless device accordingly. In some 135 cases, the first RA configuration and / or second RA configuration may be pre-defined and / or configured and / or configurable. A set of first ROs may comprise one or more ROs.

[0024] A set of second ROs may comprise one or more ROs. One or more of the first ROs and second ROs may partially or completely overlap, e.g., in time domain and / or frequency domain. To each RO, there may be associated a format, e.g., according to the RA 140 configuration. Different formats may be associated to or by different RA configurations, even to overlapping ROs. The wireless device may be configured, and / or operate based on, a SBFD configuration, which may be configured or configurable to the WD (e.g., by the network or network node), and / or may be predefined. It may be considered that the ROs according to the RA configurations may be periodical or quasi-periodical, e.g., at 145 least for timescales longer than one or more radio frames or minutes, and / or describe a recurring pattern of ROs.

[0025] The random access signalling may be transmitted in a subband of a Downlink Subframe, e.g., in a SBFD mode.

[0026] A subband may be an UL subband. The signalling may pertain to signalling on one 150 carrier and / or bandwidth part; the subband may cover a part of the carrier. One or more DL subbands may be defined on the carrier for a DL slot. The wireless device may be adapted for operation in a TDD mode, which may indicate that it is capable to operate in such a mode. It may be configured or configurable for operation in a TDD mode based on a configuration, which for example may configure an UL / DL pattern of slots, and / or 155 one or more carrier or frequency ranges for TDD operation; the configuration may be cell-specific and / or UE-specific. The wireless device may be adapted and / or configured for operation in SBFD mode. For a wireless device, this may refer to the capability of being configured of transmitting in a DL slot and / or on an UL subband, and / or that the wireless device is adapted for cooperating with a network node operating in SBFD 160 mode; it does not necessarily indicate that the wireless device is capable of simultaneously transmit and receive on the same carrier (the carrier in which the UL subband is located), although in some variants, the wireless device may be adapted for such capability (capable of transmitting and receiving on the same carrier at the same time, albeit possibly on different subbands of the carrier). A TDD configuration may in particular be based 165 on broadband signalling received from a network or network node, e.g., synchronisation signalling like SSB signalling.

[0027] A subband may in general indicate a frequency range on a carrier, which may be smaller than the frequency range of the carrier and / or of a bandwidth part configured and / or operated on; for example, the subband may be 50% or less of the frequency range, or 1 / 3 or 170 less of the frequency range, or 1 / 4 or less of the frequency range. An UL subband may be embedded into the frequency range, e.g., such that a subband for DL is below the subband, and a subband for DL is above the subband in frequency domain. However, cases in which the UL subband is at the upper or lower edge of the frequency range may be considered.

[0028] This may for example facilitate aligning RO between slots in frequency domain, and / or 175 allow assigning different frequency ranges as subbands for different wireless devices. Performing a radom access procedure may comprise transmitting one or more random access message, e.g., in response to, and / or based on, receiving the random access signalling (from one or more wireless devices). The random access signalling (transmitted by the wireless device) may in particular be a msgl or msgA of a random access procedure. 180

[0029] In particular, performing the procedure may comprise transmitting a random access response or msg2 and / or msgB, and / or a msg2 and msg4, e.g., based on receiving a msg3 after transmitting a msg2.

[0030] In general, a configuration and / or configurations may be configured to the wireless device by the network and / or network node, e.g., with higher layer signalling like RRC signalling, 185 and / or MAC layer signalling. This may allow consistent setup of the wireless device.

[0031] The network node may generally be adapted for operating in SBFD mode. In particular, it may be adapted to simultaneously transmit signalling on a carrier (in DL), and to receive signalling on the same carrier (in UL); receiving and transmitting may be on different subbands of the carrier, e.g., receiving may be on an UL subband, and transmitting on a 190

[0032] DL subband.

[0033] The random access signalling may be transmitted over two, or more, ROs, which may be in different slots, e.g., in an UL slot and a DL slot (with UL subband). Splitting the signalling may be facilitated, e.g., allowing longer signalling to be provided. The signalling may have a first part, associated to a first RO and / or first slot, which may for 195 example be in an UL subband, and / or a first part of the signalling may be transmitted in the UL subband. The signalling may have a second part, which may be associated to a second RO and / or a second slot, which may be in a different slot (e.g., a subsequent and / or neighbouring in time domain slot), and / or the second part may be transmitted in a second slot (e.g., a subsequent and / or neighbouring in time domain slot). In some 200 cases, the first part may comprise and / or consist of signalling representing a preamble or part thereof, the second part may comprise and / or consist of signalling representing the preamble; in some cases, the second part may comprise (e.g., additionally to signalling representing a preamble), additional information and / or payload, e.g., if the random access signalling represents a msgA. In some cases, the signalling may be split into more 205 than two parts, e.g., split out over more than two slots and / or ROs. A first slot may be a

[0034] DL slot (with UL subband), and the second slot may be an UL slot; other scenarios may be considered, e.g., the reverse arrangement.

[0035] It may be considered that the random access signalling may comprise and / or represent a random access preamble; such a preamble may represent a sequence of signals / modulation 210 symbols for indicating random access initiation. A preamble may be from a set of preambles, which may be configured or configurable, and / or pre-defined; in some cases, a specific preamble may be configured to be used, e.g., from a set, in other cases, a preamble may be randomly or pseudo-randomly determined. The random access signalling may comprise additional information, e.g., an identity of the wireless device, and / or data for early 215 transmission, and / or information relating to random access or communication, like timing information, and / or UE capabilities. Additional information may be included into a PUSCH transmission, which may be associated to the preamble, e.g., time multiplexed and / or frequency multiplexed, and / or transmitted on the same occasion / s or opportunities. 220

[0036] In some cases, the random access signalling may cross a slot border. This allows spreading out the signalling over time. In general, the random access signalling may cover a plurality of symbols, e.g., 2 or more, or 4 or more, or 8 or more, or 12 or more, or 14 or more symbols. The signalling may start in a RO in a first or leading slot, and / or may be continued in a RO in the next or subsequent slot (the slot crossed into); there may be one or more of 225 such subsequent slots. In general, the random access signalling may be (e.g., exclusively) transmitted in ROs, and / or on resources associated to and / or allocated for ROs. The ROs may be continuous in time domain, or interrupted (e.g., with a gap in time domain between them). The ROs may at least partly, or completely overlap in frequency domain, and / or the signalling may be transmitted on the same frequency resources on different 230

[0037] ROs. The ROs may be configured to the wireless device, and / or may be associated to and / or be relative to synchronisation signalling occasions, e.g., resources on which SSB or synchronisation signalling is or may be transmitted and / or received.

[0038] It may be considered that the duration and / or extension in time domain of one or more second random access opportunities and / or of the second ROs is longer than that of one 235 or more first ROs, e.g., e.g., it may comprise ND more symbols, with ND being an integer of 1 or larger, or 2 or larger, or 4 or larger, or 7 or larger, or 14 or larger. This allows spreading out the signalling over a long time, which may improve the reception quality for the network node even in SBFD operation.

[0039] It may be considered that the random access signalling may longer than a slot duration 240

[0040] (in time domain). Thus, the total energy / power and / or signal quality may be improved, e.g., allowing improved random access, e.g., from a cell edge and / or from larger distances to the network node.

[0041] It may be considered that random access signalling may start in a DL slot and end in an

[0042] UL slot, or vice versa. This allows in particular adapting to UL-light TDD configurations 245

[0043] (in which there may be many more DL slots than UL slots).

[0044] In general, it may be considered that the random access signalling is transmitted on the same and / or aligned and / or associated frequency resources in different slots. Thus, tuning and / or internal interference may be minimised.

[0045] It may be considered that the random access signalling may be based on a distance and / or 250 path-loss and / or signal strength and / or signal quality determination. For example, which preamble to use, and / or transmission power, and / or signalling duration, and / or whether to cross a slot boundary may be based on such determination. The determination may be performed by the wireless device, e.g., based on measurements, which may be performed on pilot or reference signalling, e.g., synchronisation signalling like SSB signalling and / or 255

[0046] PSS and / or SSS, and / or CSI-RS signalling, and / or other signalling. For example, there may be a threshold for such a characteristic, based on which random access signalling is transmitted on a subband, or not, and / or based on which the preamble and / or format and / or duration is selected. In some cases, for low signal quality or high path-loss (e.g., based on measurements, and / or relative to an associated threshold), transmission on the 260 subband may be performed, e.g., to improve coverage.

[0047] In general, random access signalling may be transmitted on a random access occasion (RO) in the subband. A random access occasion may also be referred to as opportunity; it may indicate time and / or frequency resources on which random access signalling may be transmitted. Both a wireless device and a network node may be aware of such occasion / s, 265 e.g., based on a configuration and / or predefinition. In particular, the network node may configure the wireless device with one or more ROs in the subband, e.g., based on a UL subband configuration and / or UL subband PRACH or RACK configuration.

[0048] The configuration may implicitly and / or explicitly indicate one or more ROs; it may be considered that one or more of those may be invalid, e.g., based on additional criteria; 270 validity may be determined by the wirelss device (the network node may be adapted to monitor all occasions, for example, as different wireless devices may have different valid occasions). In general, a RO in an UL subband may be associated to, and / or mapped to, to one or more RO in an UL slot, and / or vice versa, e.g., based on a configuration, and / or predefined and / or configured or configurable. It may be considered that the starting RO 275 for random access signalling indicates and / or is mapped to and / or determined a further RO in another slot for continuation of the signalling, e.g., based on such a configuration and / or predefinition (this may be unambiguously defined).

[0049] It may be considered that the random access signalling may be interrupted, e.g., for a pause or gap (in time domain). For example, it may be interrupted for a guard interval 280 when switching from DL to UL or vice versa, and / or for a time until an associated RO in the next slot (the slot crossed into) starts. This allows spreading out the signalling, while considering provided gaps. In some cases, the interrupting may comprise transmitting zeroed symbols, which may allow maintaining the phase over the pause. In some cases, it may comprise turning off and / or setting to sleep the transmitter / transceiver, e.g., if the 285 gap is comparatively long.

[0050] In some cases, the random access signalling may be based on a configuration like an UL subband configuration and / or UL subband PRACH configuration and / or a PRACH configuration. The configuration / s may be provided individually, or separately, e.g., with different signalling like broadcast signalling and dedicated signalling. This may facilitate 290

[0051] UE-specific setups. Different parameters may be provided with different configurations; in some cases, a more specialised and / or dedicated and / or additional configuration may override and / or complement a more general or earlier configuration.

[0052] It may be considered that the random access signalling is based on a dedicated configuration and / or based on or in accordance with capability information. Capability infor- 295 mation may be provided to the network node by the wireless device, e.g., with higher layer signalling; in this case, it may be considered that the random access signalling may be transmitted after initial access, e.g., for synchronisation or other purposes. A dedicated configuration may in general be UE-specific. However, it may be considered that configuration pertaining to SBFD operation and / or UL subband random access sig- 300 nailing may be provided with broadcast signalling, e.g., in system information, e.g., in a PDSCH received before initial access is performed. This may allow early utilisation of the approaches described herein.

[0053] A radio node, e.g. a transmitting or signalling radio node, and / or a receiving or feedback radio node, may operate in TDD mode, e.g. switching between DL periods and UL 305 periods. A DL period may be a period in which the radio node operates using DL transmissions, an UL period may be a period in which the radio node operates using UL transmissions (e.g., a network node may transmit during DL, and receive during UL, and vice versa for a wireless device). It may be considered that there is a TDD guard period between DL and UL periods and / or between UL and DL periods, which may comprise a 310 number of symbol time intervals, e.g. 10 or more symbols, or 12 or more symbols; there may be the same duration for guard periods for DL / UL and UL / DL, or different ones.

[0054] The guard period may allow switching circuitry between the different communication directions and / or handling of interference (in particular considering that DL signalling tends to much more powerful than (received) UL signalling). An antenna arrangement 315 may comprise one or more antenna elements and / or sub-arrays and / or panels; different antenna arrangements may comprise different antenna elements and / or sub-arrays and / or panels. Different antenna arrangements and / or panels and / or sub-arrays and / or elements may be adapted to be controlled or controllable separately from each other. There may be the same number of DL and UL periods and / or the same duration associated to DL 320 and UL (at least over a certain time interval, e.g. alternating such that one DL period is followed by one UL period, or vice versa, or different numbers or durations, e.g. (roughly) 3:1 (e.g., 3 DL periods followed by a TDD guard period and 1 UL period), or (roughly) 2:1, or even (roughly) 1:2 or 1:NU with NU 3 or larger, for UL heavy scenarios. UL period durations may be the same as DL period durations, or different. The distribution 325 and / or duration of DL and UL periods may be referred to as TDD pattern; the TDD pattern may be dynamically controllable (e.g., with DCI signalling), and / or configured or configurable, e.g. with higher layer signalling like RRC signalling or RLC signalling, and / or may be semi-statically configurable or configured. The TDD pattern may describe the smallest time domain distribution of DL period / s and / or UL period / s and / or TDD 330 guard period / s repeated over time, e.g. in one or more frames and / or subframes and / or slots and / or a time duration covering multiple repetitions of the TDD pattern.

[0055] It may be considered that the radio node is adapted for utilising a number NP of antenna sub- arrays and / or panels, wherein NP may be an integer number of 4 or larger. An antenna sub-array may comprise a plurality of antenna elements, e.g. 4 or more, or 10 335 or more, or 50 or more, or 100 or more. An antenna sub-array, and / or the antenna elements associated thereto and / or comprised therein, may be associated and / or connected or connectable to one and / or the same antenna circuitry, and / or be jointly controllable for analog and / or digital beam-forming, and / or be operable for joint transmission or reception. A panel may comprise a support structure, e.g. plastics and / or metallic ma- 340 terial and / or wood, supporting one or more antenna sub-arrays, which additionally may support additional circuitry like antenna circuitry and / or interface circuitry. Each antenna sub-array may be associated for one communication direction (e.g., reception or transmission) and / or one functionality, e.g. communication. It may be considered that antenna elements of an antenna sub-array share the same polarisation, e.g. horizontal 345 or vertical. In some cases, NP may be an even number, wherein it may be considered that NP / 2 antenna sub-arrays (and / or their antenna elements) may be associated to a first polarisation (e.g., horizontal or vertical or left-circular or right-circular, or any other suitable polarisation) and the other NP / 2 antenna sub-arrays are associated to a second polarisation, which may be orthogonal to the first polarisation. For example, the first 350 polarisation may be horizontal with the second polarisation being vertical, or the first polarisation may be left-circular and the second polarisation may be right-circular. This allows multiple beams to be operated, with good flexibility and / or large signalling capacity. In general, an antenna arrangement associated to a radio node may comprise one or more antenna sub-arrays, in particular an even number of antenna sub-arrays. In general, 355 at different times, different antenna sub-arrays and / or panels may be used for different functions, e.g. transmission or reception, and / or communication. The polarisation of an antenna element may be associated to a specific operation direction, e.g. for transmission or reception. Depending on signalling direction (transmission or reception), polarisation may be different. For example, an antenna sub-array may be associated to a first polari- 360 sation for transmission, and a second polarisation for reception, or vice versa. This may be achieved, for example, by providing crossed linear antenna elements for the sub-arrays, with associated connections / circuitry according to polarisation.

[0056] A transmitter may generally represent a device adapted for transmission, but it also may be adapted for reception, and / or represent a TRP or radio node or antenna arrangement. 365

[0057] In some cases, a transmitter or TRP may be controlled by a radio node, e.g. a network node or transmitting radio node; such a node may control one or more transmitters, e.g. a first transmitter and second transmitter.

[0058] It may be considered that operating utilising signalling like communication signalling, and / or communicating utilising signalling like communication signalling, may comprise 370 transmitting the signalling, e.g. communication signalling, and / or receiving the signalling, e.g. communication signalling. It may be considered that signalling like communication signalling is based on an OFDM wave-form, e.g. OFDM, or DFT-s-OFDM, or pulseshaped DFT-s-OFDM. Such a wave-form is particularly suitable for wireless communication at high frequencies and / or with high communication loads. A cyclic appendix may 375 generally be a cyclic prefix, or a cyclic suffix. The appendix may represent a repetition of a part of signalling carried by a symbol at its start (suffix) or end (prefix), which may be appended at the opposite of the symbol (end or start); e.g. a cyclic prefix may be considered a repetition of the signalling at the end of the symbol it pertains to. The communication signalling may be based on a waveform with cyclic appendix. A cyclic 380 appendix may be associated to a specific symbol, it may have a duration shorter than the symbol duration, e.g. 1 / 4 or less than 1 / 4 of the symbol duration, or 1 / 6 or less than 1 / 6.

[0059] A radio node, like a transmitting radio node or receiving radio node, may be a wireless device or user equipment or terminal. Alternatively, it may be a network node or sig- 385 nailing radio node. A radio node adapted for wireless communication may be a radio node adapted for transmitting and / or receiving communication signalling. Communication signalling may be. and / or comprise, data signalling and / or control signalling and / or reference signalling, e.g. according to a wireless communication standard like a 3GPP standard or IEEE standard (e.g., of WIFI or WLAN). Operating utilising communication 390 signalling may comprise transmitting and / or receiving communication signalling. The radio circuitry and / or processing circuitry and / or antenna circuitry of a radio node may be adapted for handling communication signalling The radio node may be adapted for full-duplex operation, and / or half-duplex operation. Full duplex may refer to transmitting and receiving at the same time, e.g. using the same or different circuitries, and / or 395 using different antenna sub-arrays or separately operable antenna sub-arrays or antenna elements. The communication signalling may be beam-formed.

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

[0061] Communication may in particular on multiple communication links and / or beams and / or with multiple targets (e.g., TRPs or other forms of transmission sources also receiving) and / or multiple layers at the same time; different reference signallings for multiple transmission or reception may be based on different sequence roots and / or combs and / or cyclic 410 shifts. Thus, high throughput may be achieved, with low interference. In general, different reference signallings (e.g., of the same type) may be associated to different transmission sources and / or beams and / or layers, in particular if transmitted simultaneously and / or overlapping in time (e.g., considering different timing advance values if transmitted in uplink). For example, there may be first reference signalling transmitted using a first 415 transmission source and / or first beam and / or first layer, and second reference signalling transmitted using a first transmission source and / or first beam and / or first layer.

[0062] Paging may in general represent a procedure in which a wireless device known to, and / or registered with, a network is in a quiet modus, e.g., with RRC connection and / or in idle mode, but data for the wireless device is available (e.g., due to an incoming call). 420

[0063] The network then may send a paging message, which may indicate to the wireless device that it should connect to the network, e.g. go into RRC connection and / or to perform a random access procedure. Paging messages may be sent a specific paging occasions; the occasions may be configured to wireless devices, such that for example not all wireless devices have to monitor all paging occasions. A paging message may trigger a random 425 access procedure.

[0064] There is also described a program product comprising instructions adapted for causing, and / oir 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 430 connected or connectable, to a radio node is also disclosed.

[0065] Brief description of the drawings

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

[0067] Figure 1, showing an exemplary illustration of FDD and TDD; 435

[0068] Figure 2, showing an exemplary TDD pattern;

[0069] Figure 3, showing an exemplary TDD scenario;

[0070] Figure 4, showing another exemplary TDD scenario with subband full duplex operation;

[0071] Figure 5, showing exemplary SBFD scenarios;

[0072] Figure 6, showing an exemplary RA configuration scenario; 440

[0073] Figure 7, showing an exemplary RA scenario;

[0074] Figure 8, showing an exemplary Information Element;

[0075] Figure 9, showing exemplary held descriptions;

[0076] Figure 10, showing an exemplary signalling scenario;

[0077] Figure 11, showing an exemplary signalling scenario; 445

[0078] Figure 12, showing an exemplary signalling scenario;

[0079] Figure 13, showing an exemplary signalling scenario;

[0080] Figure 14, showing an exemplary signalling scenario;

[0081] Figure 15, showing an exemplary signalling scenario;

[0082] Figure 16, showing an exemplary signalling scenario; 450

[0083] Figure 17, showing an exemplary signalling scenario;

[0084] Figure 18, showing an exemplary signalling scenario;

[0085] Figure 19, showing an exemplary signalling scenario; Figure 20, showing an exemplary signalling scenario;

[0086] Figure 21, showing an exemplary signalling scenario; 455

[0087] Figure 22 , showing an exemplary radio node like a wireless device; and

[0088] Figure 23, showing an exemplary radio node like a network node.

[0089] Detailed description

[0090] In the following, reference is being made to a random access procedure, and / or associated messages. However, the approaches described may be applicable in other contexts, e.g. 460 exchange of messages in high-speed scenarios (e.g., with drones and / or trains and / or vehicles) and / or loT (Internet-of-Things) scenarios and / or for transmission on different carriers and / or different beams, and may for example be applicable for control signalling and / or data signalling also outside of a random access procedure. A UE may be seen as an exemplary receiving radio node or wireless device. The random access may be in a 465

[0091] 3GPP-based system, e.g., NR, or a 6G system, or in another system, e.g., based on WiFi and / or WLAN.

[0092] Random access (RA) may be performed by a wireless device, e.g., to access a cell and / or to start communication and / or to synchronise to a network, in particular for uplink synchronisation, and / or for handover or other purposes. A receiving radio node like a 470 wireless device or UE may be considered to be adapted to perform random access, e.g. to perform one or more actions like transmissions and / or reception associated to a random access procedure on the device side; a transmitting radio node like a network node may be considered to be adapted to perform random access, e.g. to perform one or more actions like transmissions and / or reception associated to a random access procedure on 475 the network side. A UE or wireless device may be considered an example of a receiving radio node, and the terms may be interchanged. A network node or gNodeB may be considered an example of a transmitting radio node and the terms may be interchanged.

[0093] In general, a wireless device may receive synchronisation signalling transmitted from the network (e.g., a signalling radio node), e.g. a transmitted SS / PBCH beam SSBO, 480

[0094] SSB1,. . . . Reception of the SS / PBCH beam SSBO, . . . may be with a reception beam, which may for example be associated to a random access transmission beam PRACH beam 0, 1, . . . for the wireless device, and / or to the SS / PBCH transmission beam (associated in this context may indicate the inverse / reverse beam, and / or a beam in a specific reception direction). A reception beam may be associated to a SS / PBCH transmission 485 beam, or to a group of such, e.g. comprising two or more SS / PBCH transmission beams, e.g. corresponding to a reception beam like a PRACH Rx beam having twice the width of a SSB beam. The wireless device may determine the best received SS / PBCH transmission, e.g. based on reception within a FFT window to sample the signalling, and transmit a random access preamble in response to indicate it wants to perform random 490 access. A random access preamble may also be referred to as message 1 or Msgl; it may be represented by a sequence of symbols to be transmitted, e.g. selected from a set (or two sets or more sets) of preambles available (e.g., according to configuration and / or indicated by the SS / PBCH received); the selection may be randomised, or in some cases, indicated by the network node, for example configuring a specific set and / or 495 preamble to the wireless device. The Msgl or preamble may be transmitted in a random access resource (also referred to as random access occasion), which may be indicated by and / or dependent on the SS / PBCH received, and / or be associated to the specific set of preambles the preamble is selected from. It may be considered that the RA preamble is transmitted using a subcarrier spacing or numerology different from the one used for 500 communication; the SCS for RA may be for example be 960 kHz, wherein the communication SCS may be 1920 kHz. The transmission of the RA preamble may comprise a number of repetitions of the preamble and / or a cyclic prefix. When a preamble sequence arrives at the network node, may depend on the distance between the wireless device and the receiving network node. The RA preamble transmission may be received with 505

[0095] SSB reception beams, to e.g. determine the best reception. The received SSB may in general be used for cell identification and synchronisation by the wireless device. However, for transmissions to the network node (UL), timing might be off due to signalling travelling time; the wireless device may generally acquire a timing advance (TA) value for

[0096] UL transmissions, which may be provided by the network node. The maximum delay of 510

[0097] RA preamble reception may be indicative of a cell size or communication radius, which may be related to a maximum allowed TA. After receiving the preamble, a network node may transmit a random access response (RAR) or message 2 (Msg2), which may provide a timing advance value (TAI) and schedule resources for uplink transmission, e.g. on a

[0098] PUSCH, using a message 3 (Msg3). The Msg3 may be transmitted using the provided 515 timing advance value (TAI) and / or according to the communication SCS, which may in general shift the transmission to an earlier point in time in relation to the downlink timing to accommodate the signal travelling time for UL transmission (e.g., so that the network may receive synchronised signalling). Msg3 may be a contention resolution request, e.g. containing details of the identity of the wireless device to enable to network to 520 unambiguously identify wireless devices to finish random access. A Msg4 transmitted by the network node may resolve the contention and / or provide setup for communication, e.g. to perform an RRC setup procedure. In general, multiple wireless device may try to access the network at the same time, e.g. using the same preamble or same set of preambles and / or the same random access resources. The contention resolution may fa- 525 cilitate resolving issues arising with multiple random access attempts. If a wireless device does not receive a RAR, it may retransmit the RA preamble with increased power, e.g. using power ramping, until it receives a response and / or a maximum transmission power has been reached. In general, random access messages transmitted by a network node or signalling radio node (e.g., Msg2, Msg4) may be transmitted on a data channel, e.g. 530

[0099] PDSCH or PSSCH; such transmission may be scheduled with a control channel message and / or on a PDCCH or PSCCH, e.g. a DCI format message or SCI format message. The control channel message may be associated to a search space or CORESET, which may be configured or configurable with higher layer signalling, e.g. with PBCH signalling and / or RRC layer signalling, e.g. in a SS / PBCH transmission and / or a data channel 535 transmission, e.g. on PDSCH (e.g., for specific configuration or as System Information multicast or broadcast, e.g. associated to PBCH signalling). In an alternative approach, instead of Msgl and 3, a single message may be transmitted, e.g. a message A or MsgA.

[0100] MsgA may comprise a preamble part and / or a part with coded data, similar to a PUSCH transmission. In response to a MsgA, there may be transmitted a MsgB, e.g. instead of 540 a Msg2 and Msg4. MsgB may be similar to a PDSCH transmission. This may be part of a 2-step RA procedure. For some uses cases, e.g. synchronisation, it may be sufficient to exchange Msgl and Msg2 in a shortened 4-step procedure. A MsgB, and / or Msg2 or Msg4 may comprise one or more message parts, e.g. a scheduling assignment (e.g., DCI and / or PDCCH) and / or a scheduled data channel transmission. A MsgB or Msg2 may 545 in general schedule a transmission by the receiving radio node or UE. A random access message like msgl or msA may have a specific format (e.g., according to preamble-size or modulation or simular). In general, the physical channel involved with random access may be referred to a PRACH (Physical Random Access CHannel); associated (physical layer) parameters may be considered PRACH parameters. For many purposes, the terms 550

[0101] RACH and PRACH may be considered synonymous. In the context of this discussion a preamble may be referred to interchangeably as RA preamble or PRACH preamble or RACH preamble.

[0102] Random access may in general be performed based on system information, which may be provided in different information blocks. For example, basic system information may 555 be included in a MiB, which may be provided via PBCH transmission, in a SSB and / or together with synchronisation signalling like PSS and SSS. Additional essential system information may be provided in System Information Blocks (SiBs); of particular importance may be a SiBl, which may provide system information essential to operate, in particular to perform random access. SiBl may be provided with data signalling, e.g., 560 broadcast by PDSCH, which may be scheduled by a broadcast PDCCH or DCI message; such broadcast may be periodically; a search space for the DCI / PDCCH message may be indicated in the SSB and / or PBCH. Broadcast in this context may refer to being decodable by any receiver without additional configuration, e.g., having a CRC scrambled with a commonly known and / or pre-defined RNTI (e.g., defined in the standard). Additional 565 system information (e.g., SiB2 or more, referred to as SiBn; n may be larger than 1) may be provided in PDSCH, e.g., in a separate PDSCH transmission, which may be scheduled by DCI message and / or on PDCCH. This may be the same PDSCH providing SiBl, or a different transmission. SIBn may be broadcast, or single-cast and / or dedicated signalling, e.g., in response to a request transmitted by the wireless device / UE, for example a msgl, 570 msg3 or msgA during random access; this concept may be referred to as OnDemand, e.g., OnDemand request or OnDemand procedure or OnDemand signalling.

[0103] Some approaches to utilise radio resources (in particular, time and frequency domain resources) comprise FDD and TDD. Transmission and reception from a node, e.g. a terminal in a cellular system, can be multiplexed in the frequency domain or in the 575 time domain (or combinations thereof). Frequency Division Duplex (FDD) is illustrated to the left in Figure 1, and implies that downlink and uplink transmission take place in different, sufficiently separated (e.g., to avoid crosstalk / interference), frequency bands.

[0104] Time Division Duplex (TDD), as illustrated to the right in Figure 1, implies that downlink and uplink transmission take place in different, non-overlapping time slots. Thus, TDD 580 can operate in unpaired spectrum, whereas FDD requires paired spectrum. Frequency spectrum referred to in this context may be a carrier; thus unpaired spectrum may be on one carrier, paired spectrum may pertain to two carriers.

[0105] Typically, the structure of the transmitted signal in a communication system is organized in the form of a frame structure. In more detail, the following two information elements 585

[0106] (IES) may be defined in current specifications (other approaches may be considered, e.g. in non-3GPP systems, or future specifications). The TDD pattern may be configured with at least the first IE, and optionally the 2nd IE: TDD-DL-UL-ConhgCommon (cell-specific);

[0107] TDD-DL-UL-ConhgDedicated (UE-specffic). The first IE is cell specific (common to all

[0108] UEs) and is provided by broadcast signalling (e.g., with system information). It provides 590 the number of slots in the TDD pattern via a reference subcarrier spacing and a periodicity such that the S-slot pattern repeats every S slots. This IE allows for very flexible configuration of the pattern characterized as follows: A number of full downlink slots at the beginning of the pattern configured by the parameter nDownlinkSlots; A number of full uplink slots at the end of the pattern configured by the parameter nUplinkSlots; 595

[0109] A number of downlink (’D’) symbols following the full downlink slots configured by the parameter nDownlinkSymbols; A number of uplink (’U’) symbols preceding the full downlink slots configured by the parameter nUplinkSlots. If there is a gap between the last downlink symbol and the first uplink symbol, then all symbols in the gap are charac- terized as flexible (’F’). A symbol classified as ’F’ can be used for downlink or uplink. 600

[0110] A UE determines the direction in one of the following two ways: Detecting a DCI that schedules / triggers a DL signal / channel, e.g., PDSCH, CSI-RS or schedules / triggers an UL signal / channel, e.g. PUSCH, SRS, etc; or by dedicated (UE-specific) signalling of the IE TDD-DL-UL-ConfigDedicated. This parameter overrides some or all of the ’F’ symbols in the pattern, thus providing a semi-static indication of whether a symbol is 605 classified as ’D’ or ’U’. Optionally, a 2nd pattern that is concatenated to the first pattern can be configured as above. If a 2nd pattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 ms.

[0111] Figure 2 shows an exemplary TDD DL / UL pattern configured by TDD-DL-UL-ConfigCommon.

[0112] It consists of 3 full ’D’ slots, 1 full ’U’ slot, with a mixed slot in between consisting of 4 610

[0113] ’D’ symbols and 3 ’U’ symbols. The remaining 7 symbols in the mixed slot are classified as ’F.’

[0114] If a UE is not configured with TDD-DL-UL-ConfigDedicated, then the pattern at the top of the diagram is what it assumes. As stated above, the network can make use of the ’F’ symbols flexibly, by scheduling / triggering either an uplink or a downlink signal / channel 615 in a UE specific manner. This allows for very dynamic behavior: the direction is not known to the UE a priori; rather, the direction becomes known once the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.

[0115] In contrast, the DL / UL direction for some or all of the ’F’ symbols in a particular slot can be provided to the UE in a semi-static manner by RRC configuring the UE with TDD- 620

[0116] DL-UL-ConfigDedicated. The lower part of Figure 2 shows 3 exemplary configurations for overriding ’F’ symbols in Slot 3. If the IE indicates ’allDownlink’ or ’allUplink’ for a particular slot (or slots), then all ’F’ symbols in the slot are converted to either ’D’ or ’U,’ respectively. If the IE indicates ’explicit,’ then a number of symbols at the beginning of the slot and / or a number of symbols at the end of the slot are indicated as ’D’ and ’U,’ 625 respectively. In the example below, the first 7 and the last 5 are indicated as ’D’ and ’U’, which converts some of the ’F’ symbols (but not all in this example) to ’D’ and ’U.’

[0117] Figure 2 thus shows exemplary an TDD DL / UL pattern consisting of S = 5 slots. TDD- DL-UL-ConfigCommon configures the cell-specific pattern, and TDD-DL-UL-ConfigDedicated (if provided) UE-specifically configures the direction for some or all of the ’F’ symbols 630 in the cell-specific pattern. The UE-specific IE TDD-DL-UL-ConfigDedicated can only override (i.e., specify ’D’ or ’U’) for symbols that are configured as ’F’ by the cell-specific IE TDD-DL-UL-ConfigCommon. In other words, a UE does not expect to have a ’D’ symbol converted to ’U’ or vice versa. As described in the last section, in a conventional TDD system, entire carrier BW or all 635 carriers in the same frequency band need to be utilizing the same DL transmission or UL reception directions. This is further illustrated in Figure 3.

[0118] A subband full duplex (SBFD) system may be considered, e.g., in the context of TDD. In such a system, a portion of a carrier like a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the left-hand 640 side of Figure 4. That is, unlike a conventional TDD system as shown on the left-hand side of Figure 3, where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in the left-hand side of

[0119] Figure 4. Similarly, instead of utilizing all carriers for the same DL or UL directions in 645 a conventional TDD system as shown in the right-hand side of Figure 3, some carriers in the SBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of Figure 4.

[0120] It may be considered that only a network node operates in SBFD, e.g. a network node like a gNBs may transmit DL and receive UL simultaneously. An individual UE in some 650 variants may be scheduled in only one direction (DL or UL) at a time.

[0121] It may be considered to provide a configuration of one or more OFDM symbols of a slot with two or more ”RB sets” where each RB set corresponds to a frequency domain subband and has a defined transmission direction (’D’ or ’U’). The RB sets may have gaps between them that serve as guardbands where neither DL or UL transmission occurs. 655

[0122] Figure 5 shows two exemplary RB set configurations, one with D - U - D configuration and the other with U - D - U configuration. The RB sets are configured (e.g., to a wireless device), e.g., by introduction of new RRC parameter (s) or enhancement of an existing RRC parameter, e.g., TDD-UL-DL-ConhgDedicated. In either case, the parameters) may signal the size and frequency domain location of the RB sets as well as which 660 symbols / slots in the TDD UL / DL pattern are configured with RB sets. Figure 5 specifically shows thus configured exemplary configurations of 3 RB sets in an SBFD symbol configured as (a) D - U - D (to the left), and (b) as U - D - U (on the right). Rel-18 PRACH Configuration

[0123] An exemplary PRACH configuration according to existing (Rel-17) specifications is de- 665 scribed here. The example is for frequency range 1 (FR1) for unpaired spectrum (TDD), and uses PRACH configuration index 118 from the existing (Rel-17) 38.211 specification as shown in Figure 6.

[0124] Figure 7 illustrates an example PRACH configuration (e.g., as indicated with the config- uration of Figure 6), assuming the PRACH SCS is 30 kHz. The value x = 1 in Table 670

[0125] 6.3.3.2-3 (see Figure 6) means that the PRACH configuration period is 2 radio frames (20 ms), and the value y = 1 means that the RACH occasions (ROs) occur in the 2nd frame of this period. Within this frame, the ROs occur in subframes 2, 3, 4, 7, 8, and 9. With 30 kHz SCS, there are two slots per subframe. Since the number of PRACH slots within a subframe is equal to 1 for this example, the 2nd slot of the subframe contains the ROs 675 according to current specifications. This means that the ROs are contained in slots 5,6,9,

[0126] 14, 17, and 19. In this example PRACH format A3 (6 symbol duration) is used, hence there are two back-to-back ROs per slot starting at symbol 0 of the slot.

[0127] For an example, it may be assumed that the cell-specific (common) TDD UL / DL pattern is

[0128] D-D-D-D-U, which is also shown in Figure 7. In the existing 38.213 spec, the UE assumes 680 that a RACH occasion is valid if it is within UL symbols according to the following text extract:

[0129] [38.213 Section 8.1] For unpaired spectrum,

[0130] • if a UE is not provided tdd-UL-DL-ConhgurationCommon, a PRACH occasion in a PRACH slot is valid if it does not precede a SS / PBCH block in the PRACH slot 685 and starts at least N_gap symbols after a last SS / PBCH block reception symbol, where N_gap is provided in Table 8.1-2 and, if channelAccessMode = ’’semiStatic” is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit [15, TS 37.213].

[0131] 690

[0132] • the candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or in Serving- CellConhgCommon , as described in clause 4.1 If a UE is provided tdd-UL-DL- ConhgurationCommon, a PRACH occasion in a PRACH slot is valid if

[0133] 695

[0134] • it is within UL symbols, or

[0135] • it does not precede a SS / PBCH block in the PRACH slot and starts at least

[0136] N_gap symbols after a last downlink symbol and at least N_gap symbols after a last SS / PBCH block symbol, where N_gap is provided in Table 8.1-2, and if channelAc- 700 cessMode = ’’semiStatic” is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where there shall not be any transmissions, as described in [15, TS 37.213] • the candidate SS / PBCH block index of the SS / PBCH block corresponds to the 705

[0137] SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or in ServingCell- ConhgCommon, as described in clause 4.1.

[0138] With the D-D-D-D-U pattern, it turns out that only slots 9 and 19 contain valid ROs.

[0139] The ROs in slots in 5, 7, 15, and 17 are invalidated, as indicated by the X’s in Figure 7. 710

[0140] In the current 38.331 spec, ROs are configured in the frequency domain via two parameters: msgl-FDM, which indicates the number of ROs in the frequency domain (1, 2, 4, or 8) within an OFDM symbol, and msgl-FrequencyStart which indicates the lowest indexed RB in the active BWP of the first RO in the frequency domain. A corresponding

[0141] IE is shown in Figure 8, Figure 9 shows associated held descriptions. 715

[0142] A subband (also referred to as UL subband) may in general be configured as an UL subband in a DL slot. There may be one or more subbands; at least one DL subband may be present in a DL slot. A subband / UL subband may be configured by a network node, e.g. with a subband or UL subband configuration. The subband may be configured with a starting time, and / or ending time (e.g., with a starting symbol and / or ending 720 symbol or corresponding resource element / s), and / or with a lowest frequency (e.g., a PRB or resource element or subcarrier), and7or highest frequency (e.g., a PRB or resource element or subcarrier). The subband may be valid for the whole duration of a slot, or for a limited time within the slot. In general, the subband / UL subband configuration may be in addition to, and / or based on, to a TDD configuration or UL / DL slot configuration; it 725 may override and / or complement such a configuration. A RO may be indicated in relation to parameters identifying the subband, e.g., starting time / symbol and / or ending time symbol, and / or starting / lowest PRB or frequency or subcarrier, and / or ending / highest PRB or frequency or subcarrier. In general, the frequeny range covered by a subband / UL subband may be continuous in frequency domain; a subband may be continuous in time 730 domain during its time of validity.

[0143] For typical legacy TDD DL / UL configurations with a DDDDU slot format, legacy operation is restricted to using short PRACH formats, shorter than one (UL) slot. That limits the effective cell coverage and cell range that is possible to achieve. With SBFD capable devices and networks, PRACH is no longer limited to UL slots. Approaches for efficiently 735 configuring SBFD PRACH in relation to legacy PRACH are considered, e.g., such that longer formats, and correspondingly longer transmission durations, are feasible.

[0144] There may be considered a method in a wireless network device (UE) for transmitting a PRACH preamble in an UL subband to a wireless network node. The device may determine an UL subband RACH occasion (RO) associated with an UL slot (legacy) RO, 740 together with a PRACH format and PRACH preamble that is associated with the UL subband RO. The determined PRACH preamble may be transmitted at the determined UL subband RO.

[0145] There may be considered a method of operation a wireless device, and / or a wireless device adapted accordingly may be considered (as well as complementary method of op- 745 erating a network node, or a network node adapted accordingly). One or more of the following features may be considered for any one of the methods or devices (wireless device and / or network node) may be considered. The method may pertain to an SBFD configured network device (e.g., UE). The method may be for, and / or comprise transmitting a PRACH preamble in an UL subband to a SBFD configured network node. The 750 method may comprise determining, and / or transmitting may be based on, a PRACH format and / or preamble associated with a UL subband RO (which may be determined, e.g., based on, and / or in accordance with, a configuration; it should be noted that an

[0146] UL subband RO may be in a DL slot); and / or the method may comprise determining, and / or transmitting may be based on, an UL subband RO associated with an UL slot 755

[0147] (legacy) RO; and / or transmitting may comprise transmitting at least a first part of the determined PRACH preamble at the determined UL subband RO. A second part of the preamble may be transmitted in UL slot RO. Alternatively, or additionally, wherein the method may comprise and / or the wireless device may be adapted to , e.g., prior to determining the RO, receiving one or more of, and / or wherein transmitting may be based on 760 one or more of a PRACH configuration, and / or an UL subband configuration; and / or an

[0148] UL subband PRACH configuration. Alternatively, or additionally, the transmitting may comprise, and / or the method may comprise, and / or the wireless device may be adapted for, pausing transmission at a configured guard / flexible symbol, and / or transmitting the remaining part of the determined PRACH preamble (e.g., in the UL slot). Alternatively, 765 or additionally, the transmission of a second part may start at the symbol subsequent to the guard / flexible symbol, or the UL slot RO (determined to be associated to the UL subband RO).

[0149] In general, a UL subband PRACH configuration (based on which transmitting may be performed, and / or which may be configured to the wireless device by the network node) 770 may include one or more of a PRACH format; more PRACH config information (e.g., that may differ to legacy); a time offset (e.g., from a beginning time, or an ending time, of a subband); a frequency offset (e.g, from a lowest frequency of the subband, or a highest frequency of the subband); A PRACH duration; A PRACH interrupt; A shift or reverse of the SSB index to which the UL subband RO is associated in relation to the UL slot 775

[0150] RO; A PRACH table configuration index, where 0 or more columns may be ignored (e.g. subframe number ignored, while all intra-slot-related columns adhered to).

[0151] It may be considered that an association of the UL subband RO with the UL slot RO may be, and / or may be based on one or more of or at least one of: An offset in time;

[0152] An offset in frequency; A PRACH interrupt. It may be considered the time offset may 780 be determined from a (e.g., received or configured) UL subband configuration, and / or a (received or configured) UL subband PRACH configuration. The time offset may be determined such that for a given PRACH format or preamble, the UL subband RO may have the same end symbol as the UL slot RO. The RO and / or transmitting may be interrupted by one or more of DL-to-UL guard symbols; UL symbols prior to the UL slot 785

[0153] RO; A PRACH interrupt configuration. In some variants, the UL subband RO may be considered valid if one or more of the following applies: Regardless of if the UL slot is valid; If also the UL slot RO is valid; the UL subband RO time-frequency resource is located within an UL subband.

[0154] Efficient configuration of SBFD PRACH may be provided, which may allows for using 790 longer PRACH formats and consequently longer transmission durations. As a result, devices in worse coverage and / or at longer ranges can be detected and connected to the network. Particularly, configuring PRACH to span both UL subband / s and UL slots, both the long format, from spanning multiple slots, and good detection performance, from the higher SINR in UL slots, can be achieved. Alternatively, more ROs will allow for shorter 795

[0155] PRACH latencies and higher PRACH capacity, useful in industrial applications.

[0156] A method of operating a wireless device in a wireless communication network, and / or a wireless device or apparatus for a wireless communication network may be considered. The wireless device may be configured, and / or be adapted for being configured, for SBFD operation, and / or for transmitting a random access preamble like a PRACH preamble in at 800 least an UL subband to a network node (e.g., gNB), which may support SBFD operation.

[0157] A configuration, like a PRACH configuration or RA configuration, e.g., a provided UL subband PRACH configuration, may include, e.g., one or more of:

[0158] • An indication of a relative time and / or frequency location (offset) of the UL subband PRACH in relation to the provided legacy PRACH RO. The time offset may 805 be indicated, e.g., in symbols and / or slots and / or subframes and the frequency offset may be indicated in, e.g., subcarriers, PRBs or RB sets. Additionally, and / or alternatively, the time offset may relate to the UL subband RO’s location in relation to the start of the UL subband or the start of the slot / symbol / sub frame in which the UL subband starts or similar. Correspondingly, the frequency offset may relate 810 to the UL subband RO’s location in relation to the start of the UL subband. Figure 14 illustrates some of the described time and frequency offsets.

[0159] • A PRACH format, allowing for, e.g., a different PRACH preamble with different properties, e.g., different CP length and / or different duration and / or subcarrier 815 spacing. A legacy PRACH configuration may define multiple ROs, and / or in one variant, the offset may only applied to a subset of ROs (e.g., one, and / or the first) in a slot / subframe. Thus, there may be cases with only a subset of ROs in the UL subband even if there are more ROs in the UL slot. This option may be especially useful if the configured preamble format differs from the legacy preamble format and 820 thus the number of ROs per PRACH slot / subframe differs. A different offset may be applied to each RO. A subset of the offsets (e.g. only the first RO’s offset), may be signalled / configured / predefined as described herein; remaining offsets may have their offsets automatically derived based on the subset of offsets such that there is no overlap among the resulting ROs in the UL subband. 825

[0160] • A preamble duration, which may indicate a different length of the PRACH preamble compared to its specified duration, e.g., extending over the duration of a RO and / or slot (an extended duration may for example be achieved by repeating signalling of the preamble). 830

[0161] • An indication of a PRACH interrupt, e.g., breaking the contiguous PRACH preamble into two non-contiguous parts, which may be interrupted by a DL / UL switch guard interval.

[0162] 835

[0163] • An indication of a shift or a reversal in the order of a configured or specified SSB-to- RO mapping between the legacy RO and the UL subband RO, e.g., that in case two SSBs are transmitted by the node, a legacy RO mapping to SSB 0 will be associated with a UL subband RO mapping to SSB 1 and vice versa.

[0164] 840

[0165] • A PRACH table configuration index may be provided, where 0 or more columns may be ignored. In on variant, the subframe Held may be ignored, but intra-slot related columns (e.g., “starting symbol”, “number of PRACH slots within a subframe” , “number of time-domain PRACH occasions within a PRACH slot”) may be considered. In one variant, the system frame number (SFN) related fields may be ig- 845 nored; the SFNs where the legacy ROs occur may determine in which SFN the ROs occur. In one variant, the SFN related fields may be considered. In one variant, all fields except the preamble format field may be ignored. The time domain positions of the ROs may be determined based on the legacy ROs and the configured offset(s).

[0166] 850

[0167] In general, a wireless device or UE may be configured or configurable (e.g., by a network node) with a first RA configuration and a second RA configuration (which may be configured with the same or different signalling occurrences and / or with the same or different messages (e.g., RRCReconfiguration and / or RRCSetup). The first RA configuration may indicate and / or configure one or more (first) ROs. The second RA configuration may 855 indicate and / or configure one or more (second) ROs. First ROs may be associated to the first RA configuration, second ROs may be associated to the second RA configuration.

[0168] A first RO may overlap and / or collide with a second RO, e.g., partially or completely, for example in time domain and / or frequency domain, and / or one or more aspects of RA format (e.g., duration and / or length in symbols and / or set of sequences and / or set 860 of sequence roots available). A second RA configuration may in particular pertain to SBFD operation and / or may be provided or configured based on capability information transmitted and / or provided to a network or network node by the wireless device. A RA configuration, in particular a second RA configuration, may indicate one or more rules for validating a RO, e.g., a second RO. A rule may pertain to a first RA configu- 865 ration, and / or first RO, and / or comparison therewith, for example based on overlapping resources in time domain and / or frequency domain; in some cases, a rule may be based on a TDD pattern and / or slot configuration or symbol configuration (e.g., whether a slot is an UL slot and / or comprises UL symbols). A first RA configuration may be provided with broadcast signalling, e.g., with RRC layer signalling and / or signalling on a broad- 870 cast channel like PBCH and / or PDSCH, and / or utilising one or more system information blocks (e.g., SIBn), and / or may be cell-specific. The second RA configuration may be provided with dedicated signalling, e.g., based on capability information pertaining to a specific UE, and / or may be UE-specific; a second RA configuration may for example be provided in a RRCreconfiguration message, or a RRCSetup message. However, in some 875 cases, the second RA configuration may be provided with broadcast signalling as well (e.g., a SIB), and / or the first RA configuration may be provided with dedicated signalling, in particular during a reconfiguration or setup.

[0169] A PRACH interrupt may be related to, e.g., DL-to-UL guard symbols, and / or UL symbols prior to the legacy RO; and / or an UL subband PRACH interrupt configuration. In 880 general, an interrupt and / or PRACH interrupt may indicate and / or specify and / or configure transmission of the preamble, and / or the UL subband RO, and / or the resources or RO for the transmission, to be split into two non-contiguous parts, a first part starting at the start of the RO and a second part starting after the PRACH interrupt, e.g., after the DL-to-UL guard symbols or at the start of the legacy RO to which the UL subband RO is 885 associated. The PRACH interrupt may further be specified or configured how to handle the interrupt, e.g., should the device continue to transmit, or be assumed to continuing to transmit, during the interrupt, or the device should pause its transmission and continue after the guard band. In one variant, the pausing of the PRACH preamble transmission, may involve keeping the transmitter on, but puncturing the preamble transmission during 890 the pause. Puncturing can be done by replacing the samples during the pause with zeros. This has the advantage that the phase of the transmission may be maintained after the pause. In one variant, the UE may signal a capability if it can maintain the phase during the pause or not.

[0170] The validation or validity of the UL subband RO may depend on one or more of the 895 following parameters or conditions: Regardless of if the legacy UL slot or legacy RO is valid or not; Only if the legacy RO is valid; the UL subband RO time-frequency resource is located within an UL subband, either fully or at least the RO part prior to an interrupt.

[0171] In general, validation and / or validating may refer to, and / or comprise, and / or be based on, determining, e.g., as determining validity and / or that a RO is valid, whether a config- 900 ured and / or indicated RO may be used for, and / or intended for use, and / or is available or allowed for use, for transmission, e.g., of random access signalling and / or a RA preamble.

[0172] Validation may be based on configured and / or pre-defined rules, which may indicate when a RO is to be validated on invalidated (also referred to as non- validated). An invalidated RO may be determined to not be usable for a transmission, and / or may not be used for 905 transmission, e.g., skipped (such that one of the next in time domain, or the next in time domain of validated ROs may be used for transmission. Validation may be performed individually, e.g. for each RO, e.g., in time domain for the next RO until a RO is validated, and / or transmission is performed, for a set of more than one RO, e.g., over a time interval, which for example may be a time interval covering one or more subframe and / or one or 910 more TDD patterns, and / or one or more DL slots. Validating may comprise determining the validity of a RO and / or that a RO is valid, or the invalidity of the RO, and / or that the RO is invalid.

[0173] For a cell configured with SBFD operation, in order to serve both RACH accesses initiated by a legacy UEs (or UEs not operating SBFD) and RACH access initiated by a UEs 915 operating SBFD, one option is that the cell or network node may provide UEs with two PRACH configurations, e.g., legacy one and an additional one for SBFD operation. In some cases, these two configurations may indicate ROs that overlap, e.g., in time domain and / or frequency domain. This may be undesirable for several reasons, for example if the PRACH preambles used in the first and second RO have different formats, they 920 may be non-orthogonal, and thus maz stronglz interfere with each other. If the formats are the same, the base station may not be able to determine if a PRACH transmission originated from a UE that used the first or second configuration. An approach or method to selectively invalidate ROs indicated by the second configuration is proposed, which may ameliorate such issues. 925

[0174] For SBFD, one option is that the UE is provided with two PRACH configurations, the legacy one and an additional one for SBFD operation. A method is disclosed for determining which ROs in the additional PRACH configuration that are valid. In some embodiments, this determination depends on the ROs in the first PRACH configuration.

[0175] For example, an RO indicated by the second configuration, is invalid if it overlaps with 930 an RO indicated by the first configuration.

[0176] There is generally discussed a method in a wireless device, and / or for operating a wireless device, e.g., for and / or comprising transmitting random access signalling like a preamble like a PRACH preamble, e.g., to a network node (the network node may be capable of subband full duplex communication) The method may comprise any of the method fea- 935 tures described herein and / or one or more of: receiving a SBFD configuration; and / or receiving a first [e.g., legacy] RA or PRACH configuration indicating one or more first ROs, and / or receiving a second [e.g., SBFD] RA or PRACH configuration indicating one or more second ROs; and / or determining if or whether a one or more second RO is valid; and / or transmitting a PRACH preamble in one of the valid second ROs and / or transmit- 940 ting random access signalling like a RA preamble on a validated RO (e.g., from a second configuration). It may be considered that the determining maz comprise considering a second RO to be valid if it starts in a SBFD symbol. In some variants, the determining may comprise considering a second RO to be valid if it does not collide and / or overlap

[0177] (e.g., partially or completely, in time domain and / or frequency domain and / or preamble 945 format) with a first RO. It may be considered that colliding or overlapping may comprise that the first and second RO collides in time. In some cases, colliding may comprise that the first and second RO collide in time and / or frequency. It may be considered that colliding in time may comprise that a second RO at least partly overlaps with a time interval starting T1 seconds before the first RO starts and ends T2 seconds after the first RO ends 950

[0178] (T1 and / or T2 may be a fraction or multiple of 1). Colliding in time may comprise and / or represent that a second RO is located in the same slot and / or subslot and / or subframe as a first RO. Colliding in time may comprise and / or represent that a second RO starts in the same subslot and / or slot and / or subframe as a first RO. Colliding in frequency may comprise and / or consist of and / or represent a frequency range (e.g., subcarriers or PRBs) 955 of the second RO at least partly overlapping with the frequency range of the first RO. The second RA or PRACH configuration may include an indication whether a collision with the first ROs should be considered or not (e.g., as a rule for validating). A second RO, that would be validated according to a general / legacy RO validation rule (applicable to a first RO), may be invalidated according to an explicit rule for the second RA or PRACH 960 configuration. A validation rule may be and / or comprise and / or represent that a RO in a slot like a PRACH slot is valid if it is within UL symbols (e.g., UL slot or Special slot with UL symbols).

[0179] Avoiding overlapping ROs from two PRACH configurations in case different PRACH preamble formats are used for the two ROs may help avoiding that they interfere with 965 each other (e.g., due to non-orthogonality of the preambles). If the formats are the same, approaches discussed herein may facilitate the network node or base station to determine if a PRACH transmission originated from a UE that used the first or second configuration.

[0180] Throughout the disclosure several figures are used. In general, these figures assume 30kHz subcarrier spacing, thus one subframe (SF) contains two slots. Downlink slots / signalling / resource 970 is marked DL and / or light; and a slot / resource / signalling marked dark indicate UL. ROs are marked with light, e.g., embedded in dark when located in UL. A cross may indicate that an RO is invalidated. The horizontal direction represents time in slots and subframes (SF). The vertical direction represents the two PRACH configurations and with each configuration the vertical direction illustrates the frequency dimension in subbands. A UE 975 may be considered an example of a wireless device, and UE features may be applicable to a wireless device as well. In the figures, ignoring ROs, a slot or symbol with three same-colored blocks (representing subbands) may be considered a non-SBFD slot (as all subbands go into the same direction), and / or a slot or symbol with different colors for the subbands may be considered an SBFD slot or symbol. 980

[0181] For a system or device or node or cell configured with and / or adapted for SBFD operation, the cell (and / or network and / or network node) may provide two RACH configurations (e.g., a first RA configuration and a second RA configuration) to UEs, e.g., via signalling alternatives including at least system information, dedicated RRC signalling. In some cases, only the first R A c onhguration (a nd / or ot her co nhguration not cov ered by the 985 second RA configuration) m ay b e c onhgured fo r UE s wh ich ar e no t ca pable of SBFD operation, e.g., legacy UEs, or UEs not supporting SBFD operation; while another RACH configuration ( second R A c onfiguration) may additionally be co nfigured for UEs which support SBFD operation, e.g., based on capability information provided for, and / or by, and / or pertaining to, the UE or wireless device. A UE supporting SBFD operation, upon 990 and / or in the context and / or in preparation of, triggering of a RACH procedure, may determine PRACH resources (including PRACH preamble and / or RACH occasions).

[0182] The UE may receive a subband full duplex configuration. The fullduplex configuration may comprise and / or indicate at least time and frequency locations of the UL and DL subbands. 995

[0183] The UE may receive a first (legacy) PRACH or RA configuration. This PRACH or RA configuration may also used by UEs not capable of SBFD operation.

[0184] THe UE may perform determination / selection / validation of a RACK configuration and / or ROs in case of multiple RACK configurations. It may be considered that a UE receives a second (SBFD) PRACH or RA configuration. The second PRACH configuration may 1000 be a complete independent configuration, or it can be a delta configuration in relation to the first configuration (e.g., refer to the first RA configuration). A delta configuration may covers / comprises or indicate changes / variations of parameters comparing to the reference configuration, i.e., the first RA configuration; an absent parameter in the delta configuration may indicate that the parameter applies the same setting as the reference 1005 configuration.

[0185] The UE may choose or select and / or configure itself with the second PRACH configuration according to its capability, e.g., if the UE supports SBFD operation.

[0186] It may be considered that the UE may choose and / or apply and / or configure itself with the two PRACH configurations (first and second RA configuration) in a combinational 1010 fashion; in this case, the second PRACH configuration may be not applicable by the UE.

[0187] Determination of RACH resources may be performed by the UE. The UE may obtain a PRACH preamble (which can be obtained in a contention- free manner, i.e., dedicated preamble or contention-based manner) according to the selected RACH conhguration(s).

[0188] The UE may select one or multiple RACH occasions (ROs) (e.g., following the legacy 1015 procedure as captured in clause 5.1.2 of TS 38.321 V 18.0.0) according to the selected RACH conhguration(s). The UE may determine which ROs are valied, e.g., which initially selected ROs are valid , for example according to specific rules introduced for SBFD operation and / or as provided with the second RA configuration. Such determining may be performed on and / or limited to one or more ROs, and / or to one or more ROs of the 1020 second RA configuration.

[0189] The UE may transmit random access signalling like a PRACH preamble in one or more of the valid ROs indicated by the second configuration.

[0190] Validation may be performed based on one or more rules, e.g., configured (possibly with the second RA configuration) and / or pre-defined rule / s. 1025

[0191] Validation based on an SBFD- and / or UL / DL configuration may be considered. Validation for example may be based on an RO starting in an SBFD symbol. ROs indicated by the selected RACK configuration (e.g., the second PRACH configuration) may be considered valid if they start in a symbol configured for SBFD operation. That may be a symbol in which both DL and UL operation is allowed (in particular, for 1030 the network node; in many cases, a UE may be limited to either, in particular UL in this case; however, the approaches here may be applied to a sufficiently capable UE with SBFD utilising UL and DL simultaneously as well). Figure 10 shows an exemplary general signalling scenario with SBFD and two non-specific RA configurations. In the following, exemplary validation rules are described. Validation may be based on one or more of 1035 these rules (e.g., in a combination of rules).

[0192] In Figure 11 an example approaches of validating second ROs is shown. In this example, the ROs indicated by the second PRACH configuration are validated only if they start in a SBFD symbol. That is, the ROs starting in a non-SBFD symbol may be invalidated.

[0193] In Figure 12 another example of validating second ROs is shown. In this example, the 1040

[0194] RO in SF7 (subframe 7 as arbitrary time interval) indicated by the second PRACH configuration is invalid because it doesn’t start in a SBFD symbol. In this variant, the fact that one of them extend into a non-SBFD symbol (see SF9) does not affect the validation of this RO.

[0195] Validation based on a RO being fully contained in SBFD symbols may be considered. In 1045 this alternative and / or additional variant, ROs indicated by the second PRACH configuration are only valid if they are completely contained in SBFD symbols. That is, a second RO may be invalidated if at least a part of the RO extends into a symbol or slot without a SBFD conhguration / setup.

[0196] Figure 13 illustrates an example where the last (in time) 7 ROs indicated by the second 1050

[0197] PRACH configuration in SF9 are invalidated, because they are not fully contained in symbols with a SBFD configuration.

[0198] Alternatively, or additionally, validation may be based on overlap with UL symbols. On or more ROs indicated by the second PRACH configuration (in general referred to as second ROs) may be determined or considered invalid if at least a part of a RO extends 1055 into an UL symbol. Note that they may extend into a flexible symbol without SBFD configuration and be considered valid. Figure 14 illustrates an example where the last (in time) 6 ROs indicated by the second PRACH configuration in SF9 are invalidated, because they overlap with UL symbols.

[0199] Validation based on ROs indicated by the first PRACH configuration may be consid- 1060 ered. In this variant rule, the ROs indicated by the second PRACH configuration may be determined valid if they do not collide with an RO indicated by the first PRACH configuration.

[0200] For example, validation may be based on start of first and second ROs in the same slot or subslot. ROs indicated by the second PRACH configuration may be determined valid 1065 if they don’t start in the same slot or subslot as an RO indicated by the first PRACH configuration. Figure 15 illustrates this variant. In this case, the ROs indicated by the second PRACH configuration are determined valid because they don’t start in the same slots as the ROs indicated by the first PRACH configuration.

[0201] In Figure 16 another exemplary validation is shown. In this example, the ROs indicted 1070 by the second configuration are validated if they don’t start in the same slot as an RO indicated by the first PRACH configuration. For example, the RO in the first slot of subframe 7 (SF7) is valid even if it doesn’t start in a SBFD symbol (although an additional rule requiring start in a SBFD symbol or slot may be utilised, then it would be invalid).

[0202] Validation based on ROs starting in same subframe may be considered. ROs indicated by 1075 the second PRACH configuration may be determined valid if they don’t start in the same subframe as an RO indicated by the first PRACH configuration. In Figure 17, another exemplary validation is shown. In this example, the ROs indicted by the second configuration are validated (determined to be valid) if they don’t start in the same subframe as an RO indicated by the first PRACH configuration. For example, the RO in the first slot 1080 of subframe 7 (SF7) is valid even if it doesn’t start in a SBFD symbol, and the first RO in SF9 is invalid or invalidated because it starts in the same subframe as an RO indicated by the first PRACH configuration.

[0203] In Figure 18, another exemplary validation is shown. In this example the ROs indicted by the second configuration are validated if they don’t start in the same subframe as 1085 an RO indicated by the first PRACH configuration. For example, the RO in SF9 is invalidated because it starts in the same subframe as an RO indicated by the first PRACH configuration. It should be noted that in general, second ROs may extend in duration over a slot border, shown as uninterrupted block as in Figure 18.

[0204] A validation rule based on collision in time domain (e.g., with margin) may be considered. 1090

[0205] For example, ROs indicated by the second PRACH configuration in this case may be considered invalidated if they overlap in time with an RO indicated by the first PRACH configuration. Overlap in time may refer to overlap is on symbol or OFDM symbol level, or some margin can be added (e.g., one or more gap symbols, and / or a gap interval), so that ROs just before and / or just after (based on the margin) may also be invalidated. In 1095 general, validation may be based on same-sized (in duration or length or time domain) or different-sized margins (intervals or gap intervals) before and after a first RO. The margin can for example be N^X-TX) X TCbefore the RO indicated by the first PRACH configuration and / or N TX-RX) x Tcafter the RO indicated by the first PRACH configuration, where N^x-Tx^ , NTX_RX) and Tcmay be defined as in 3GPP document TS 38.211. 1100

[0206] Another option is that that margin is equal to Ngapas defined in 38.213.

[0207] Figure 19 illustrates an example where no margin is used and thus the last three (in time) ROs indicated by the second PRACH configuration are invalidated because they overlap in time with the ROs indicated by the first PRACH configuration.

[0208] Figure 20 illustrates an example where a margin is used, and the last four (in time) ROs 1105 indicated by the second PRACH configuration are invalidated because they overlap in time with the ROs plus margin indicated by the first PRACH configuration.

[0209] A validation rule based on collision in time and / or frequency may be considered. In addition, or alternatively, to the time domain, the frequency domain may also be considered.

[0210] For example, ROs indicated by the second PRACH configuration may be invalidated if 1110 they overlap in time (occasion) and frequency (occasion) with one or more ROs according to the first RACH configuration. The frequency overlap can be on resource block or subcarrier level. It can also involve a margin on both sides of an RO indicated by the first PRACH configuration, wherein the same margin or a different margin may be applied to the lower frequency end and the higher frequency end (note that this may refer to physical 1115 frequency resources or to virtual physical frequency resources, e.g. before an intermediate frequency resource mapping).

[0211] Figure 21 illustrates an example where three ROs indicated by the second PRACH configuration are invalidated because they overlap both in time and frequency with ROs indicated by the first PRACH configuration. 1120

[0212] It may be considered that pre-defined and / or configured (e.g., with the first RA configuration) validation rules are disregarded and / or not applied to the second (SBFD) PRACH configuration and / or second ROs. A second RA configuration may indicate and / or override one or more validation rules that may be applicable and / or configured and / or pre-defined, e.g., for a first RA configuration and / or first ROs. In one example, a 1125 second RO that would be validated according to a legacy or a general validation rule that is applicable to a first RO, may be invalidated. For this case, the second RO would be invalidated based on an explicit invalidation rule, being an exception to the legacy or general validation rule that would otherwise render the RO valid (or vice versa, determining a second RO valid even if according to a rule applicable to a first RO it would be invalid). 1130 According to a variant, a validation rule to be invalidated / overridden / disregarded may correspond to or represent that an RO in a PRACH slot is valid if it is within UL symbols. That is, the second RO may only be valid if at least partly located in SBFD symbols.

[0213] It may be considered that a UE may access a cell configured with at least two RACK configurations, wherein at least RACK configuration serves and / or configures non-SBFD op- 1135 eration (e.g., first RA configuration), and at least one RACK configuration serves and / or configures SBFD operation (second RA configuration). The UE (e.g., if supporting SBFD operation) upon triggering of a RACK procedure, may first select ROs according to the second RACK configuration (SBFD) to transmit the selected PRACH preamble (as described in the above embodiments). The UE may determine, e.g., according to a fallback 1140 rule, to fallback to ROs according to the first RACH configuration (serving non SBFD operation) when one or more of the below conditions (fallback rule / s) is met: after N transmissions / transmissions of PRACH preambles (e.g., retransmissions), e.g. if the UE cannot complete the RACH procedure successfully; and / or after M ms (M being an integer or rational or real number, which may be smaller or larger than 1) since the RACH 1145 procedure is triggered and / or first transmission of a preamble, e.g., start or end of such transmission), if the UE cannot complete the RACH procedure successfully; and / or X ROs since or after RACH procedure is triggered are invalid, if or such that the UE cannot complete the RACH procedure successfully (X may be an integer larger than 1, e.g., 2 or larger, or 5 or larger, or 8 or larger); the invalid ROs may be consecutive in time, or one 1150 or more valid ROs may be interspersed.

[0214] Figure 22 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 1155 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 1160 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 1165 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. A DFE may be 1170 considered part of radio circuitry; an analog frontend may be associated to radio circuitry and / or antenna circuitry.

[0215] Figure 23 schematically shows 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, 1175 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 1180 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.

[0216] 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 1185 to and / or comprise an antenna array. The node 100, respectively its circuitry, may be adapted to perform any of the methods of operating a network node or a radio node as described herein; in particular, it may comprise corresponding circuitry, e.g. processing 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 1190 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.

[0217] A DFE may be considered part of radio circuitry; an analog frontend may be associated to radio circuitry and / or antenna circuitry.

[0218] In general, the wireless device and / or network node may operate in, and / or the commu- 1195 nication signalling may be in TDD operation. It should be noted that the transmission of signalling from transmission sources may be synchronised and simultaneous; a shift in time may occur due to different propagation times, e.g. due to different beams and / or source locations.

[0219] A data block may refer to a transport block, or a code block or a code block bundle. A 1200 code block may comprise and / or represent a number of (information) bits representing information (e.g., data or control information), to which there may be associated, and / or which may further include, bits for error detection coding, e.g. CRC. The bits for error detection coding may be determined based on the (information) bits, and / or may be error detection bits for the (information) bits. A code block bundle may comprise one or more 1205 code blocks; wherein each code block may have associated to it, and / or comprise, error correction bits. The error correction bits in a code block bundle may each pertain to an associated code block; error correction bits may be specific to only one code block, e.g. determined based on bits of only one code block. Different bits and / or groups of bits may be associated to different code blocks. Error correction bit / s associated to a code 1210 block may be associated to a single code block; this may refer to the error correction bits indicating correctness / incorrectness of the single code block, and / or calculated and / or determined based only on (information) bits of the single code block. Information bits may represent data and / or control information, e.g. associated to a data channel (data in- formation / bits) and / or control channel (control information / bits) code block bundle may 1215 be a data block without error correction coding pertaining to more than one code block.

[0220] A transport block may comprise error detection coding pertaining to a plurality of code blocks, e.g. covering the code blocks it consists of. A transport block may comprise one or more code blocks. It may be considered that a data block may be associated to, and or subject to, and / or correspond to, a, one and / or a single acknowledgement process, e.g. 1220 a specific HARQ process, which may correspond to and / or be represented by a HARQ identifier. A code block may correspond to a subpattern of an acknowledgement information bit pattern. In some cases, a data block may correspond and / or pertain and / or be subject to a plurality of acknowledgement processes, e.g. if there is one acknowledgement process per code block of the data block. 1225

[0221] A data block may comprise and / or represent information bits, which may be data bits (e.,g., user data) and / or control information bits; the information bits may be associated to one or more data or control channels, e.g. transport channels and / or logical channels, and / or may be mapped to a specific and / or single physical channel, in particular a physical data channel, or in some cases, a physical control channel (in which case it may or may 1230 not be associated to a higher layer channel like a transport channel or logical channel). A data block may represent bits intended for transmission, e.g. encapsulating one or more higher layer data packets, e.g. one or more MAC layer data packets, e.g. one or more PDUs (Protocol Data Unit) and / or SDUs (Service Data Unit); error correction bits, e.g.

[0222] CRC; may be added in physical layer processing. It may be considered that bits of a 1235 data block are subject to physical layer processing like coding (e.g., forward error coding and / or adding error correction coding) and / or rate matching and / or scrambling, and / or modulation. Modulation may correspond to mapping of bits of the processed data block to modulation symbols, e.g. according to a modulation scheme and / or to a modulation space. The modulation symbols may be represented as a bit sequence until they are 1240 subject to analog conversion (or vice versa for reception).

[0223] A wireless device may in general comprise processing circuitry and / or radio circuitry, in particular a receiver and / or transceiver and / or transmitter, for performing measurement and / or to control beam switch and / or control beam-forming and / or receive and / or transmit signalling like communication signalling. The wireless device may in particular be 1245 implemented as terminal or a user equipment. However, in some cases, e.g. relay and / or back-link and / or IAB scenarios, it may be implemented as network node or network radio node. A network node may in general comprise processing circuitry and / or radio circuitry, in particular a receiver and / or transceiver and / or transmitter, for transmitting reference signalling and / or a beam switch indication and / or for beam switching and / or to control 1250 beam switch and / or control beam-forming and / or receive and / or transmit signalling like communication signalling. The radio node may in particular be implemented as a network node, e.g. a network radio node and / or base station or a relay node or IAB node. However, in some cases, e.g. sidelink scenarios, the second radio node may be implemented as a wireless device or terminal, e.g. a user equipment. 1255

[0224] Performing a measurement may in general comprise taking a plurality of measurement samples. As such, performing a measurement and performing measurements may be considered equivalent, unless explicitly explained otherwise (e.g., when referring to measurement at a specific occasion as opposed to measurements at a plurality of occasions).

[0225] Monitoring for a message or signalling may in general comprise utilising receiving circuitry 1260 at resources corresponding to the resource monitored (e.g., time and / or frequency domain, accomodating for path delay effects if applicable) to determine presence or absence of the message, and / or to receive and / or demodulate and / or decode the message, and / or to perform measurements on the signalling.

[0226] In general, an allocation unit or block symbol may represent and / or correspond to an ex- 1265 tension in time domain, e.g. a time interval. An allocation unit or block symbol duration (the length of the time interval) may correspond to the duration of an OFDM 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 1270 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 1275 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 1280 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 for scheduling and / or allocation of resources, in particular in time domain. To a block 1285 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.

[0227] 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, 1290 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 1295 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 1300 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)), 1305 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 1310 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 wave-forms, an affix may be represented by a sequence of modulation symbols within the block symbol. It may be considered that in some cases a block symbol is defined and / or used in the context of the associated structure. 1315

[0228] Communicating may comprise transmitting or receiving. It may be considered that communicating like transmitting signalling is based on a SC-FDM based wave- form, and / or corresponds to a Frequency Domain Filtered (FDF) DFTS-OFDM wave-form. However, the approaches may be applied to a Single Carrier based wave-form, e.g. a SC-FDM or SC-FDE- wave-form, which may be pulse-shaped / FDF-based. It should be noted that SC- 1320 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 wave-form with CP or comparable guard time.

[0229] The received beam and the transmission beam of the first beam pair may have the same 1325

[0230] (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 1330 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 signalling with CP (e.g., SC-FDM-based or OFDM-based) for a wave-form 1335 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 the bandwidth, and / or applying a shaping operation regarding the power 1340 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. Pulse-shaping may be performed based on a Nyquist-hlter. It may be considered that pulse-shaping is per- 1345 formed 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 other end of the first number of subcarriers.

[0231] In some variants, communicating may be based on a numerology (which may, e.g., be 1350 represented by and / or correspond to and / or indicate a subcarrier spacing and / or symbol time length) and / or an SC-FDM based wave-form (including a FDF-DFTS-FDM based wave-form) or a single-carrier based wave-form. Whether to use pulse-shaping or FDF on a SC-FDM or SC-based wave-form may depend on the modulation scheme (e.g., MCS) used. Such wave- forms may utilise a cyclic prefix and / or benefit particularly from the 1355 described approaches. Communicating may comprise and / or be based on beamforming, e.g. transmission beamforming and / or reception beamforming, respectively. It may be considered that a beam is produced by performing analog beamforming to provide the beam, e.g. a beam corresponding to a reference beam. Thus, signalling may be adapted, e.g. based on movement of the communication partner. A beam may for example be pro- 1360 duced by performing analog beamforming to provide a beam corresponding to a reference beam. This allows efficient postprocessing of a digitally formed beam, without requiring changes to a digital beamforming chain and / or without requiring changes to a standard defining beam forming precoders. In general, a beam may be produced by hybrid beamforming, and / or by digital beamforming, e.g. based on a precoder. This facilitates easy 1365 processing of beams, and / or limits the number of power amplifiers / ADC / DC A required 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. 1370

[0232] The numerology may determine the length of a symbol time interval 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 wave-forms. Communicating may comprise utilising a waveform with cyclic prefix. The cyclic prefix may be based on a numerology, and may help 1375 keeping signalling orthogonal. Communicating may comprise, and / or be based on performing cell search, e.g. for a wireless device or terminal, or may comprise transmitting 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. 1380

[0233] 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-specffic), such that only one radio node is served per beam / beam pair. A beam pair switch or switch of received beam (e.g., by using a different reception beam) and / or transmission beam may be performed at a border of a 1385 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 to cover retuning time; however, 1390 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.

[0234] A reference beam (or reference signalling beam) may be a beam comprising reference signalling, based on which for example a of beam signalling characteristics may be deter- 1395 mined, 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 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 1400 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 of beam signalling characteristics, each subset pertaining to a different reference beam.

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

[0236] A beam signalling characteristic, respectively a set of such characteristics, may represent and / or indicate a signal strength and / or signal quality of a beam and / or a delay 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 1410 delay and / or lowest spread / range) timing or delay spread, 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 1415 and / or gauging of the measurements. In some cases, a beam and / or beam pair may be represented by a beam identity indication, e.g. a beam or beam pair number. Such an 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 1420 and / or code) 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 held or as information element in some form of message of signalling, e.g. DCI and / or MAC and / or RRC signalling. 1425

[0237] 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 by having the same analog or digital beamforming parameters and / or precoder and / or the same shape before analog 1430 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.

[0238] 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 1435 a reference beam or signalling may be transmitted by another radio node. The signalling may indicate which beam is used for transmitting. Alternatively, the reference beams may be beams receiving the random access signalling. Random access signalling may be used for initial connection to the radio node and / or a cell provided by the radio node, and / or for reconnection. Utilising random access signalling facilitates quick and early beam selection. 1440

[0239] The random access signalling may be on a random access channel, e.g. based on broadcast information provided by the radio node (the radio node performing the beam selection), 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 1445 receiving the synchronisation signalling, e.g. in a random access process, e.g. a Msg3 for contention resolution, which may be transmitted on a physical uplink shared channel based on a resource allocation provided by the radio node.

[0240] 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 1450 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 spread, which 1455 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 indicate a relation to a threshold delay, e.g. 1460 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 of the delay spread. A power delay proftie may pertain to representations 1465 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 a measurement report may be predefined, or be configured or configurable, e.g. with a 1470 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.

[0241] 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 1475 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 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 1480 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 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 1485 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.

[0242] 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 1490 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 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 1495 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 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” 1500 do not necessarily denote an order in time; a second signalling may be received and / or transmitted before, or in some cases simultaneous to, first signalling, or vice versa. The 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

[0243] FDD may be considered as well. Different beam pairs may operate on the same frequency 1505 ranges or carriers or bandwidth parts (e.g., such that transmission beams operate on the same frequency range or carriers or bandwidth part, and received beams on the same frequency range or carriers or bandwidth part (the transmission beam and received beams may be on the same or different ranges or carriers or BWPs). Communicating utilizing a first beam pair and / or first beam may be based on, and / or comprise, switching from the 1510 second beam pair or second beam to the first beam pair or first beam for communicating. The switching may be controlled by the network, for example a network node (which may be the source or transmitter of the received beam of the first beam pair and / or second beam pair, or be associated thereto, for example associated transmission points or nodes in dual connectivity). Such controlling may comprise transmitting control signalling, e.g. 1515 physical layer signalling and / or higher layer signalling. In some cases, the switching 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.

[0244] For example, it may be switched to the first beam pair (or first beam) if the signal quality 1520 or signal strength measured on the second beam pair (or second beam) 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 1525 the first beam pair for communicating. Thus, the synchronization may be in place and / 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, 1530 for example based on a periodicity or scheduled timing of suitable reference signalling on the first beam pair, e.g. first received beam. In general, a reception beam of a node may be associated to and / or correspond to a transmission beam of the node, e.g. such that the (spatial) angle of reception of the reception beam and the (spatial) angle of transmission of the transmission beam at least partially, or essentially or fully, overlap 1535 and / or coincide, in particular for TDD operation and / or independent of frequency. Spatial correspondence between beams may be considered in some cases, e.g. such that a beam pair (e.g., transmission beam of a transmitting node and reception beam of a receiving node) may be considered to comprise corresponding beams (e.g., the reception beam is suitable and / or the best beam to receive transmissions on the transmission beam, e.g. 1540 based on a threshold signal quality and / or signal strength and / or measurements); to each of such beams, there may be an associated or corresponding complementary beam of the respective node (e.g., to a transmission beam of a beam pair, there may be associated a reception beam of the transmitting node, and / or to the reception beam of a beam pair, there may be associated a transmitting beam of the receiving node; if the beams (e.g., 1545 at least essentially or substantially) overlap (e.g., in spatial angle), in some cases a beam pair may be considered to indicate four beams (or actually, two beam pairs).

[0245] In some cases, to one or more beams or signals or signallings may be associated a Quasi- CoLocation (QCL) characteristic or set of characteristics, or QCL class (also referred to as QCL type) or QCL identity; beams or signal or signallings sharing such may be con- 1550 sidered to be Quasi-Colocated. Quasi-Colocated beams or signals or signallings may be considered (e.g., by a receiver) as the same beam or originating from the same transmitter or transmission source, at least in regard to the QCL characteristic or set or class or identity, and / or to share the characteristic / s. QCL characteristics may pertain to propagation of signalling, and / or one or more delay characteristics, and / or pathloss, and / or 1555 signal quality, and / or signal strength, and / or beam direction, and / or beam shape (in particular, angle or area, e.g. area of coverage), and / or Doppler shift, and / or Doppler spread, and / or delay spread, and / or time synchronisation, and / or frequency synchronisation, and / or one or more other parameters, e.g. pertaining to a propagation channel and / or spatial RX parameter / s (which may refer to reception beam and / or transmission 1560 beam, e.g. shape or coverage or direction). A QCL characteristic may pertain to a specific channel (e.g., physical layer channel like a control channel or data channel) and / or reference signalling type and / or antenna port. Different QCL classes or types may pertain to different QCL characteristics or sets of characteristics; a QCL class may define and / or pertain to one or more criteria and / or thresholds and / or ranges for one or more 1565

[0246] QCL characteristics beams have to fulfill to be considered Quasi-Colocated according to this class; a QCL identity may refer to and / or represent all beams being quasi-colocated, according to a QCL class. Different classes may pertain to one or more of the same characteristics (e.g., different classes may have different criteria and / or thresholds and / or ranges for one or more characteristics) and / or to different characteristics. A QCL indi- 1570 cation may be seen as a form of beam indication, e.g. pertaining to all beams belonging to one QCL class and / or QCL identity and / or quasi-colocated beams. A QCL identity may be indicated by a QCL indication. In some cases, a beam, and / or a beam indication, may be considered to refer and / or represent a to a QCL identity, and / or to represent quasi-colocated beams or signals or signallings. 1575

[0247] Transmission on multiple layers (multi-layer transmission) may refer to transmission of communication signalling and / or reference signalling simultaneously in one or more beams and / or using a plurality of transmission sources, e.g. controlled by one network node or one wireless device. The layers may refer to layers of transmission; a layer may be considered to represent one data or signalling stream. Different layers may carry different 1580 data and / or data streams, e.g., to increase data throughput. In some cases, the same data or data stream may be transported on different layers, e.g. to increase reliability.

[0248] Multi-layer transmission may provide diversity, e.g. transmission diversity and / or spatial diversity. It may be considered that multi-layer transmission comprises 2, or more than 2 layers; the number of layers of transmission may be represented by a rank or rank 1585 indication.

[0249] A transmission source may in particular comprise, and / or be represented by, and / or associated to, an antenna or group of antenna elements or antenna sub-array or antenna array or transmission point or TRP or TP (Transmission Point) or access point. In some cases, a transmission source may be represented or representable, and / or correspond 1590 to, and / or associated to, an antenna port or layer of transmission, e.g. for multi-layer transmission. Different transmission sources may in particular comprise different and / or separately controllable antenna element / s or (sub-)arrays and / or be associated to different antenna ports. In particular, analog beamforming may be used, with separate analog control of the different transmission sources. An antenna port may indicate a transmission 1595 source, and / or a one or more transmission parameter, in particular of reference signalling associated to the antenna port. In particular, transmission parameters pertaining to, and / or indicating a frequency domain distribution or mapping (e.g., which comb to use and / or which subcarrier or frequency offset to use, or similar) of modulation symbols of the reference signalling, and / or to which cyclic shift to use (e.g., to shift elements of a 1600 modulation symbol sequence, or a root sequence, or a sequence based on or derived from the root sequence) and / or to which cover code to use (e.g., (e.g., to shift elements of a modulation symbol sequence, or a root sequence, or a sequence based on or derived from the root sequence). In some cases, a transmission source may represent a target for reception, e.g. if it is implemented as a TRP or AP (Access Point). 1605

[0250] In some variants, reference signalling may be and / or comprise CSLRS and / or PT-RS and / or DMRS, e.g. transmitted by the network node. In other variants, the reference signalling may be transmitted by a UE, e.g. to a network node or other UE, in which case it may comprise and / or be Sounding Reference signalling. Other, e.g. new, forms of reference signalling may be considered and / or used. In general, a modulation symbol 1610 of reference signalling respectively a resource element carrying it may be associated to a cyclic prefix.

[0251] Data signalling may be on a data channel, for example on a PDSCH or PSSCH, or on a dedicated data channel, e.g. for low latency and / or high reliability, e.g. a URLLC channel. Control signalling may be on a control channel, for example on a common control channel 1615 or a PDCCH or PSCCH, and / or comprise one or more DCI messages or SCI messages.

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

[0253] Reference signalling, for example, may comprise DM-RS and / or pilot signalling and / or discovery signalling and / or synchronisation signalling and / or sounding signalling and / or 1620 phase tracking signalling and / or cell-specific reference signalling and / or user-specific signalling, in particular CSI-RS. Reference signalling in general may be signalling with one or more signalling characteristics, in particular transmission power and / or sequence of modulation symbols and / or resource distribution and / or phase distribution known to the receiver. Thus, the receiver can use the reference signalling as a reference and / or for train- 1625 ing 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 reference signalling. Reference signalling may be signalling 1630 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 form and / or modulation and / or timing) of reference signalling are 1635 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, cell-specific (in particular, cell- wide, e.g., CRS) or device or user specific (addressed to a specific target or user equipment, e.g., CSI-RS), demodulation-related (e.g., DMRS) 1640 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.

[0254] References to specific resource structures like an allocation unit and / or block symbol and / or block symbol group and / or transmission timing structure and / or symbol and / or slot and / or mini-slot and / or subcarrier and / or carrier may pertain to a specific numerol- 1645 ogy, 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 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 1650 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 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 1655 time interval in a time stream, e.g. synchronized for communication. Timing structures used and / or scheduled for transmission, e.g. slot and / or mini-slots, may be scheduled in relation to, and / or synchronized to, a timing structure provided and / or defined by other transmission timing structures. Such transmission timing structures may define a timing grid, e.g., with symbol time intervals within individual structures representing the small- 1660 est timing units. Such a timing grid may for example be defined by slots or subframes (wherein in some cases, subframes may be considered specific variants of slots). A transmission timing structure may have a duration (length in time) determined based on the durations of its symbols, possibly in addition to cyclic prefix / es used. The symbols of a transmission timing structure may have the same duration, or may in some variants have 1665 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-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. 1670

[0255] A transmission quality parameter may in general correspond to the number R of retransmissions and / or number T of total transmissions, and / or coding (e.g., number of coding bits, e.g. for error detection coding and / or error correction coding like FEC coding) and / or code rate and / or BLER and / or BER requirements and / or transmission power level (e.g., minimum level and / or target level and / or base power level P0 and / or trans- 1675 mission power control command, TPC, step size) and / or signal quality, e.g. SNR and / or SIR and / or SINR and / or power density and / or energy density.

[0256] A signalling sequence or sequence (e.g. of an allocation unit or block symbol or symbol time interval, and / or carried or transmitted on an allocation unit or block symbol or symbol time interval) may be based on a sequence root, e.g. a root sequence and / or a 1680 root parameter and / or root index and / or seed. A sequence root in general may represent or indicate a base for deriving or determining a signalling sequence; the root may be associated to, and / or represent a sequence directly, and / or indicate or represent a base sequence and / or seed. Examples of sequence roots may comprise a Zadoff Chu root sequence, a sequence seed, e.g. a seed for a Gold sequence, or a Golay complimentary 1685 sequence. A signalling sequence may be derived or derivable from, and / or be based on, a sequency root, e.g. based on a code, which may represent a shift or operation or processing on the root sequence or a sequence indicated by the sequence root, e.g. to provide the signalling sequence; the signalling sequence may be based on such shifted or processed or operated on root sequence. The code may in particular represent a cyclic shift and / or 1690 phase shift and / or phase ramp (e.g., an amount for such). The code may assign one operation or shift for each allocation unit.

[0257] In general, a signalling sequence associated to an allocation unit (and / or the allocation units) associated to control signalling (and / or reference signalling) may be based on a root sequence which may be a M-sequence or Zadoff-Chu sequence, or a Gold or Golay 1695 sequence, or another sequence with suitable characteristics regarding correlation and / or interference (e.g., self- interference and / or interference with other or neighboring transmitters). Different sequences may be used as root sequences for different signalling sequences, or the same sequence may be used. If different sequences are used, they may be of the same type (Gold, Golay, M- or Zadoff-Chu, for example). The (signalling and / or root) 1700 sequences may correspond to or be time-domain sequences, e.g. time domain Zadoff-Chu and / or time-domain M sequences.

[0258] In some cases, a shifted object like a signalling or signals or sequences or information may be shifted, e.g. relative to a predecessor (e.g., one is subject to a shift, and the shifted version is used), or relative to another (e.g., one associated to one signalling or 1705 allocation unit may be shifted to another associated to a second signalling or allocation unit, both may be used). One possible way of shifting is operating a code on it, e.g. to multiply each element of a shifting object with a factor. A ramping (e.g. multiplying with a monotonously increasing or periodic factor) may be considered an example of shifting.

[0259] Another is a cyclic shift in a domain or interval. A cyclic shift (or circular shift) may 1710 correspond to a rearrangement of the elements in the shifting object, corresponding to moving the final element or elements to the first position, while shifting all other entries to the next position, or by performing the inverse operation (such that the shifted object as the result will have the same elements as the shifting object, in a shifted but similar order). Shifting in general may be specific to an interval in a domain, e.g. an allocation 1715 unit in time domain, or a bandwidth in frequency domain. For example, it may be considered that signals or modulation symbols in an allocation unit are shifted, such that the order of the modulation symbols or signals is shifted in the allocation unit. In another example, allocation units may be shifted, e.g. in a larger time interval - this may leave signals in the allocation units unshifted with reference to the individual allocation unit, 1720 but may change the order of the allocation units. Domains for shifting may for example be time domain and / or phase domain and / or frequency domain. Multiple shifts in the same domain or different domains, and / or the same interval or different intervals (differently sized intervals, for example) may be performed.

[0260] Reference signalling may have a type. Types of reference signalling may include synchro- 1725 nisation signalling, and / or DM-RS (used to facilitate demodulation of associated data signalling and / or control signalling), and / or PT-RS (used to facilitate phase tracking of associated data signalling and / or control signalling, e.g. within a time interval or symbol or allocation unit carrying such signalling), and / or CSI-RS (e.g., used for channel estimation and / or reporting). It may be considered that PT-RS are inserted into a bit sequence, 1730 or a modulation symbol sequence, which may represent data. For example, PT-RS may be mapped onto subcarriers of a symbol also carrying data symbols. Accordingly, PT-RS insertion may be optimised for hardware implementations. In some cases, PT-RS may be modulated differently and / or independently of the modulation symbols representing data (or data bits). 1735

[0261] A comb structure, or shorter comb, may indicate a distribution, or periodic arrangement of reference signalling, in particular in frequency space, e.g. between an upper and lower frequency. A comb may pertain to one OFDMA symbol and / or SC-FDMA symbol and / or one (the same) symbol time interval and / or one allocation unit. A comb may have width or size N and / or may pertain to, and / or be associated to, specific signalling and / or a 1740 type of signalling, e.g. a type of reference signalling. The width N may indicate how many empty subcarriers are between (e.g., non-neighbouring) subcarriers carrying an element or signal or symbol of the signalling (e.g., this number may be N-l), or how many empty subcarriers and non-empty subcarriers form a pattern that is repeated in frequency domain. In general, each comb may indicate that at least one empty subcarrier is to be 1745 between non-empty subcarriers. In this context, empty may refer to empty regarding the pattern or distribution of the signalling associated to the comb (and non-empty may refer to a subcarrier carrying an element or symbol of the associated signalling); in some cases, other signallings (which may have a comb structure as well) may be carried on empty subcarriers, e.g. transmitted using other transmission sources and / or other devices, 1750 and / or mapped into the comb (e.g., for a DMRS comb, data signalling may be mapped on subcarriers not carrying DMRS).

[0262] A comb structure may generally describe a structure in which for every N-th (N may be an integer) resource element and / or subcarrier a reference signal or an element of a sequence of the reference signalling, and / or representing the reference signalling, and / or 1755 on which the reference signalling is based, is mapped to, and / or represented by signalling the resource element and / or subcarrier, in particular an element (symbol) of a modulation symbol sequence, or an element of a sequence. N may be called the width of the comb.

[0263] Generally, the comb may indicate the periodicity of the pattern inside the frequency range of the reference signalling. The pattern may in particular pertain to one reference signal 1760 and / or resource element or subcarrier for transmitting a reference signal, such that the comb may be considered to indicate that on every Nth resource element (in particular, only there) and / or subcarrier there is to be a reference signal or element of an associated sequence, and / or how many resource elements and / or subcarriers are between resource elements and / or subcarriers with reference signals. However, there may be considered 1765 variants, in which the pattern represents more than one reference signals. The pattern may also generally represent and / or indicate one or more empty signals and / or one or more data signals (respectively associated resource elements and / or subcarriers). For each comb or comb structure with a width or size of N, there may be N or f(N) different available individual combs. For example, for N=2, there may be two combs shifted in frequency 1770 space by one, or an odd number, of subcarriers or PRBs (e.g., based on a frequency domain offset, or a subcarrier offset). A comb structure or comb of width or size of N may be indicated as N-comb. Specific combs of this width may be numbered within N.

[0264] For example, for a 2-comb, there may be a comb 1 (or Cl) and a comb 2 (or C2), which may be shifted relative to each other, e.g. to dovetail such that all subcarrier covered by 1775 both combs carry signalling (associated to Cl and C2 alternatingly in frequency domain).

[0265] A comb may comprise two or more, for example at least three or at least four, repetitions of the pattern. The comb may indicate a reference and / or indication, e.g. a resource element and / or subcarner, which may be related to the upper and / or lower boundary in frequency, regarding the arrangement and / or location in frequency of a first pattern, 1780 and / or the relative shift of the pattern and / or comb in frequency. Generally, a comb structure may cover at least part, and / or at least the majority, and / or essentially all or all resource elements and / or subcarriers of the plurality of resource elements and / or subcarriers, and / or the symbol. A comb structure may result from combining two comb structures, which may in particular comb structures with pattern comprising only one 1785 reference signal. A comb structure may be determined and / or amended before transmission, e.g. based on other reference signalling to be transmitted, e.g. on a different antenna port. In this context, reference signals may be replaced by empty signals to avoid overlap and / or interference. Generally, if the other reference signalling utilises a comb structure as well, a different / new comb (as a combination of combs) may be considered to 1790 be determined, e.g. with less dense reference signal distribution and / or a different / wider pattern. Alternatively, or additionally, combs may be combined to increase the reference signal density, e.g. by combining combs with different widths, and / or with shifted offsets.

[0266] Generally, a comb structure may represent and / or comprise and / or be comprised of any of the combs / comb structures described herein. 1795

[0267] A buffer state report (or buffer status report, BSR) may comprise information representing the presence and / or size of data to be transmitted (e.g., available in one or more buffers, for example provided by higher layers). The size may be indicated explicitly, and / or indexed to range / s of sizes, and / or may pertain to one or more different channel / s and / or acknowledgement processes and / or higher layers and / or channel groups / s, e.g, 1800 one or more logical channel / s and / or transport channel / s and / or groups thereof: The structure of a BSR may be predefined and / or configurable of configured, e.g. to override and / or amend a predefined structure, for example with higher layer signalling, e.g. RRC signalling. There may be different forms of BSR with different levels of resolution and / or information, e.g. a more detailed long BSR and a less detailed short BSR. A short BSR 1805 may concatenate and / or combine information of a long BSR, e.g. providing sums for data available for one or more channels and / or or channels groups and / or buffers, which might be represented individually in a long BSR; and / or may index a less-detailed range scheme for data available or buffered. A BSR may be used in lieu of a scheduling request, e.g. by a network node scheduling or allocating (uplink) resources for the transmitting radio 1810 node like a wireless device or UE or IAB node.

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

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

[0270] A system comprising one or more radio nodes as described herein, in particular a network 1830 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.

[0271] Moreover, there may be generally considered a method of operating an information system, the method comprising providing information. Alternatively, or additionally, an information system adapted for providing information may be considered. Providing in- 1835 formation 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 information, and / or offering the information for such and / or for download, and / or triggering such 1840 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 network. Information may be provided utilising and / or via such intermediate system / s. Providing information may be 1845 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 target, and / or one or more parameters of transmission pertaining to the target and / or the paths or connections over which the in- 1850 formation 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) 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 1855 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 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 1860 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 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, 1865 e.g. a host computer or host computer arrangement and / or server or server arrangement.

[0272] In some variants, an interaction server (e.g., web server) of the information system may provide a user interface, and based on user input may trigger transmitting and / or streaming information provision to the user (and / or the target) from another server, which may be connected or connectable to the interaction server and / or be part of the information 1870 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 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 informa- 1875 tion 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 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 1880 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. 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 com- 1885 prise different components, which may have different sources, and / or which may indicate different characteristics of the target and / or communication path / s thereto. A format of information may be specifically selected, e.g. from a set of different formats, for information to be transmitted on an air interface and / or by a RAN as described herein. This may be particularly pertinent since an air interface may be limited in terms of capacity and / or 1890 of predictability, and / or potentially be cost sensitive. The format may be selected to be adapted to the transmission indication, which may in particular indicate that a RAN or radio node as described herein is in the path (which may be the indicated and / or planned and / or expected path) of information between the target and the information system. A (communication) path of information may represent the interface / s (e.g., air and / or ca- 1895 ble interfaces) and / or the intermediate system / s (if any), between the information system and / or the node providing or transferring the information, and the target, over which the information is, or is to be, passed on. A path may be (at least partly) undetermined when a target indication is provided, and / or the information is provided / transferred by the information system, e.g. if an internet is involved, which may comprise multiple, 1900 dynamically chosen paths. Information and / or a format used for information may be 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.

[0273] More alternatively, or additionally, a target device may be considered, the target device 1905 being adapted for providing a target indication to an information system. 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 1910 interface or user interface, and / or may comprise one 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 1915 information and / or communication 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, 1920 and / or for 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 expected and / or 1925 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 signalling (such mapping may generally 1930 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 terminal). The tool may generally be adapted for use on a 1935 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 on signalling, in a RAN, for example if the target device is a UE, or the 1940 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. application layer or user-layer, in particular above radio layers like transport layer and 1945 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 indication to be provided, facilitating information to be provided in a specific format particularly 1950 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.

[0274] In general, a numerology and / or subcarrier spacing may indicate the bandwidth (in fre- 1955 quency 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 subcarrier.

[0275] 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 1960 in particular regarding the subcarrier bandwidth. A symbol time length, and / or a time length of a timing structure pertaining to a carrier may be dependent on the carrier frequency, and / or the subcarrier spacing and / or the numerology. In particular, different numerologies may have different symbol time lengths, even on the same carrier.

[0276] Signalling may generally comprise one or more (e.g., modulation) symbols and / or signals 1965 and / or messages. A signal may comprise or represent one or more bits. An 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, 1970 e.g. representing and / or pertaining to one or more 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 1975 may be transmitted such 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.

[0277] An antenna arrangement may comprise one or more antenna elements (radiating ele- 1980 ments), which may be combined in antenna arrays. An antenna array or sub-array 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 sub-array or element is separately controllable, respectively that different antenna arrays are controllable separately from each other. A single an- 1985 tenna element / radiator may be considered the smallest example of a sub-array. Examples of antenna arrays comprise one or more multi-antenna panels or one or more individually controllable antenna elements. An antenna arrangement may comprise a plurality of antenna arrays. It may be considered that an antenna arrangement is associated to a (specific and / or single) radio node, e.g. a configuring or informing or scheduling radio 1990 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 arrangement may be configurable for different arrays, e.g. to change the beamforming characteristics. In particular, antenna arrays may be formed 1995 by combining one or more independently or separately controllable antenna elements or sub-arrays. The beams may be provided by analog beamforming, or in some variants by digital beamforming, or by hybrid beamforming combing analog and digital beamforming.

[0278] The informing radio nodes may be configured with the manner of beam transmission, e.g. by transmitting a corresponding indicator or indication, for example as beam identify in- 2000 dication. 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 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 inde- 2005 pendent 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 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 2010 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 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 2015 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 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 2020 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 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.

[0279] A beam may be defined by a spatial and / or angular and / or spatial angular distribution 2025 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 do not come 2030 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 and / or reach). A beam 2035 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. bounded by one or more contiguous or contiguous 2040 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 direction than a main lobe and / or other side lobes, however, due to reflections 2045 a sidelobe still may contribute to transmitted and / or received energy or power. A beam may be swept and / or switched over time, e.g., such that its (main) direction is changed, but its shape (angular / solid angle distribution) around the main direction is not changed, e.g. from the transmitter’s views for a transmission beam, or the receiver’s view for a reception beam, respectively. Sweeping may correspond to continuous or near continuous 2050 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 change does not cover the main lobe after the change, e.g. at most to 50 or 25 or 10 percent. 2055

[0280] 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 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 2060 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 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 2065 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, 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 2070

[0281] (strength).

[0282] 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 like communication signalling is not limited thereto (Filter-Bank based signalling and / or 2075

[0283] Single-Carrier based signalling, e.g. SC-FDE signalling, may be considered alternatives).

[0284] 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.

[0285] A radio node may be a network node, or a user equipment or terminal. A network node 2080 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 described herein.

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

[0287] The circuitry and / or circuitries may be packaged, e.g. in a chip housing, and / or may have one or more physical interfaces to interact with other circuitry and / or for power supply.

[0288] Such a wireless device may be intended for use in a user equipment or terminal.

[0289] 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 2100 communication circuitry, with which it may be connected or connectable to another radio node and / or a core network.

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

[0291] Specific Integrated Circuitry) and / or FPGAs (Field Programmable Gate Array), or sim- 2105 ilar. It may be considered that processing circuitry comprises, and / or is (operatively) connected or connectable to one or more memories or memory arrangements. A memory arrangement may comprise one or more memories. A memory may be adapted to store digital information. Examples for memories comprise volatile and non-volatile memory, and / or Random Access Memory (RAM), and / or Read-Only-Memory (ROM), 2110 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).

[0292] Radio circuitry may comprise one or more transmitters and / or receivers and / or transceivers

[0293] (a transceiver may operate or be operable as transmitter and receiver, and / or may com- 2115 prise joint or separated circuitry for receiving and transmitting, e.g. in one package or housing), and / or may comprise one or more amplifiers and / or oscillators and / or filters, and / or may comprise, and / or be connected or connectable to antenna circuitry and / or one or more antennas 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, 2120 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 circuitry and / or functionality implemented therein.

[0294] Communication circuitry may comprise radio circuitry and / or cable circuitry. Commu- 2125 nication circuitry generally may comprise one or more interfaces, which may be air inter- face / s and / or cable interface / s and / or optical interface / s, e.g. laser-based. Interface / s may be in particular packet-based. Cable circuitry and / or a cable interfaces may 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 intermedi- 2130 ate systems and / or interfaces) be connected or connectable to a target, e.g. controlled by communication circuitry and / or processing circuitry.

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

[0296] A wireless communication network may be or comprise a radio access network and / or 2140 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.

[0297] A wireless communication network may be and / or comprise a Radio Access Network 2145

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

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

[0300] 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 2175 signaled by a network node on PDCCH (Physical Downlink Control Channel) and / or a PDSCH (Physical Downlink Shared Channel) and / or a HARQ-specihc channel. Acknowledgement signalling, e.g. as a form of control information or signalling like uplink control information / signalling, may be transmitted by a terminal on a PUCCH (Physical

[0301] Uplink Control Channel) and / or PUSCH (Physical Uplink Shared Channel) and / or a 2180 HARQ-specihc channel. Multiple channels may apply for multi-component / multi-carrier indication or signalling.

[0302] Transmitting acknowledgement signalling may in general be based on and / or in response to subject transmission, and / or to control signalling scheduling subject transmission.

[0303] Such control signalling and / or subject signalling may be transmitted by a signalling ra- 2185 dio 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 comprise and / or be repre- 2190 sented 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.

[0304] A signalling characteristic may be based on a type or format of a scheduling grant and / or scheduling assignment, and / or type of allocation, and / or timing of acknowledgement signalling and / or the scheduling grant and / or scheduling assignment, and / or resources 2195 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 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 2200

[0305] (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 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 2205 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 overhead.

[0306] 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 2210 opportunities of a configuration intended to carry data signalling or subject signalling.

[0307] 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 2215 configuration may in particular represent allocation 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 2220 and / or refer to and / or indicate 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 opportu- 2225 nities 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.

[0308] Control information, e.g., in a control information message, in this context may in particular be implemented as and / or represented by a scheduling assignment, which may 2230 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 signalling.

[0309] Subject transmissions may comprise one or more individual transmissions. Scheduling as- 2235 signments may comprise one or more scheduling assignments. It should generally be noted that in a distributed system, subject transmissions, configuration 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, 2240 e.g. in a MIMO scenario, and / or to same or different ports. Generally, subject transmissions may pertain to different HARQ or ARQ processes (or different sub-processes, e.g. in MIMO with different beams / layers associated to the same process identifier, but different sub-process-identifiers like swap bits). A scheduling assignment and / or a HARQ codebook may indicate a target HARQ structure. A target HARQ structure may for example 2245 indicate an intended HARQ response to a subject transmission, e.g. the number of bits and / or whether to provide code block group level response or not. However, it should be noted that the actual structure used may differ from the target structure, e.g. due to the total size of target structures for a subpattern being larger than the predetermined size.

[0310] Transmitting acknowledgement signalling, also referred to as transmitting acknowledge- 2250 ment 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 comprise, a structure for acknowledgement 2255 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. In some cases, the channel may be a shared channel 2260 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 be based on one or more size indications and / or assignment 2265 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 information in one or more control information messages and / or a configuration. 2270

[0311] 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 information, e.g. a scheduling request and / or measurement information. 2275

[0312] 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 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 ac- 2280 knowledgement 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 HARQ processes; an ARQ process may provide ACK / NACK (and perhaps additional feedback) feedback, and decoding may be performed on each (re-)transmission separately, with- 2285 out 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.

[0313] 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 2290 high reliability, e.g. a URLLC channel. Control signalling may be on a control channel, for example on a common control channel or a PDCCH or PSCCH, and / or comprise one or more DCI messages or SCI messages. 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 2295 signalling and / or cell-specific reference 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 2300 into another, or even 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.

[0314] It may be considered that transmitting acknowledgement information, in particular of acknowledgement information, is based on determining whether the subject transmission / s has or have been received correctly, e.g. based on error coding and / or reception quality. 2305

[0315] 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.

[0316] 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 2310 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, 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 2315 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 structure. In some cases, the mapping may pertain to one or more acknowledgement signalling processes, e.g. processes with different identifiers, and / or one or more different data streams. The config- 2320 uration 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 may pertain to a data block structure, e.g. a code block or code block group or transport block. A subpattern may be arranged to indicate acknowledgement or non-acknowledgement, or another retransmission state like 2325 non-scheduling or non-reception, 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 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. 2330

[0317] An acknowledgment signalling process (providing acknowledgment information) may be a HARQ process, and / or be identified by a process identifier, e.g. a HARQ process identifier or sub-identifier. Acknowledgement signalling and / or associated acknowledgement information may be referred to as feedback or acknowledgement feedback. It should be noted that data blocks or structures to which subpatterns may pertain may be intended 2335 to carry data (e.g., information and / or systemic and / or coding 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 2340 the subpattern. Such may for example happen if the size 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 control mes- 2345 sage. 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.

[0319] An acknowledgment signalling process may determine correct or incorrect reception, 2350 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 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 2355 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 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 2360 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 correctly identified. In such a case, the subpattern may represent acknowledgement information for the data block as a whole, reducing overhead in comparison to provide acknowledgement information for the sub- 2365 blocks 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 (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 2370 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 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. 2375

[0320] 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 bit / s may be determined 2380 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 particular for forward error correction (FEC), e.g. 2385

[0321] 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 or code block group, or a combination of more than one code block groups. 2390

[0322] 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 transport block, which in this context represents information bits without the error 2395 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.

[0323] In some variants, a subblock like a code block may comprise error correction bits, which 2400 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 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 2405 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 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 2410 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 correction bits are applied to a transport block, however, it may be considered to apply either or both. In some specific variants, the code block group / s comprise no additional layers of error detection or correction cod- 2415 ing, 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 block size and / or the maximum size for error correction coding. A subpattern of acknowledgement signalling (in particular indicating ACK or

[0324] NACK) may pertain to a code block, e.g. indicating whether the code block has been 2420 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 or code blocks of the group or data / transport block are received correctly (e.g. based on a logical AND operation), and NACK or another state of noncorrect reception if at least one subblock or code block has not been correctly received. It 2425 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-combining and / or the error correction coding.

[0325] A subpattern / HARQ structure may pertain to one acknowledgement signalling process and / or one carrier like a component carrier and / or data block structure or data block. It 2430 may in particular be considered that one (e.g. specific and / or single) subpattern 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 2435 may be multiple subpatterns (and / or 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 2440 to different elements 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

[0326] ACK or NACK, and optionally, (if n^,l), may represent DTX / DRX or other reception 2445 states. 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.

[0327] The acknowledgement information or feedback information may pertain to a plurality of different transmissions, which may be associated to and / or represented by data block 2450 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, alternatives with scheduling for non-simultaneous transmission may be considered. For example, the 2455 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. time and / or frequency resources, for example for receiving or transmitting the scheduled signalling. 2460 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 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 2465 or representing acknowledgement signalling and / or resource requesting information, may comprise encoding and / or modulating. Encoding and / or modulating may comprise error detection coding and / or forward error correction encoding and / or scrambling. Receiving control signalling may comprise corresponding decoding and / or demodulation. Error detection coding may comprise, and / or be based on, parity or checksum approaches, e.g. 2470

[0328] CRC (Cyclic Redundancy Check). Forward error correction coding may comprise and / or be based on for example turbo coding and / or Reed-Muller coding, and / or polar coding and / or LDPC coding (Low Density Parity Check). The type of coding used may be based on the channel (e.g., physical channel) the coded signal is associated to. A code rate may represent the ratio of the number of information bits before encoding to the number of 2475 encoded bits after encoding, considering that encoding adds coding bits for error detection coding and forward error correction. Coded bits may refer to information bits (also called systematic bits) plus coding bits.

[0329] Communication signalling may comprise, and / or represent, and / or be implemented as, data signalling, and / or user plane signalling. Communication signalling may be associated 2480 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. 2485

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

[0331] A resource element may generally describe the smallest individually usable and / or encodable and / or decodable and / or modulatable and / or demodulatable time- frequency resource, and / or may describe a time-frequency resource covering a symbol time length in 2495 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 b and for transmission and / or reception. In some variants, a signal (jointly encoded / modulated) may cover more than one resource elements. A resource element may generally be as defined by a correspond- 2500 ing standard, e.g. NR or LTE. As symbol time length and / or subcarrier spacing (and / or numerology) may be different between different symbols and / or subcarriers, different resource elements may have different extension ( length / width) i n t ime a nd / or frequency domain, in particular resource elements pertaining to different carriers.

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

[0333] 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 2510 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.

[0334] If the starting symbol is associated to control signalling (e.g., on a control channel), the control signalling may be in response to received signalling (in sidelink or downlink), e.g. 2515 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, e.g. a PDSCH (Physical Downlink 2520 Shared Channel). A starting symbol may be determined based on, and / or in relation to, such an ending symbol.

[0335] Configuring a radio node, in particular a terminal or user equipment, may refer to the radio node being adapted or caused or set and / or instructed to operate according to the configuration. Configuring may be done by another device, e.g., a network node (for 2525 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.

[0336] Such configuration data may represent the configuration to be configured and / or comprise one or more instruction pertaining to a configuration, e.g. a configuration for transmitting and / or receiving on allocated resources, in particular frequency resources. A radio node 2530 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 represented by configuration information, and / or one or more corresponding indications and / or message / s 2535

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

[0338] A resource structure may be considered to be neighboured in frequency domain by another resource structure, if they share a common border frequency, e.g. one as an upper frequency border and the other as a lower frequency border. Such a border may for example be represented by the upper end of a bandwidth assigned to a subcarrier n, which also represents the lower end of a bandwidth assigned to a subcarrier n+1. A resource 2555 structure may be considered to be neighboured in time domain by another resource structure, if they share a common border time, e.g. one as an upper (or right in the figures) border and the other as a lower (or left in the figures) border. Such a border may for example be represented by the end of the symbol time interval assigned to a symbol n, which also represents the beginning of a symbol time interval assigned to a symbol n+1. 2560 Generally, a resource structure being neighboured by another resource structure in a domain may also be referred to as abutting and / or bordering the other resource structure in the domain.

[0339] 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 2565 may comprise and / or be comprised of resource elements, and / or the time interval of a resource structure may comprise and / or be comprised of symbol time interval / s, and / or the frequency interval of a resource structure may comprise and / or be comprised of sub- carrier / s. A resource element may be considered an example for a resource structure, a slot or mini-slot or a Physical Resource Block (PRB) or parts thereof may be considered 2570 others. A resource structure may be associated to a specific channel, e.g. a PUSCH or PUCCH, in particular resource structure smaller than a slot or PRB.

[0340] Examples of a resource structure in frequency domain comprise a bandwidth or band, or a bandwidth part. A bandwidth part may be a part of a bandwidth available for a radio node for communicating, e.g. due to circuitry and / or configuration and / or regulations 2575 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 / conhguration of a device, and / or a system bandwidth, e.g. available for a 2580

[0341] 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.

[0342] A carrier may generally represent a frequency range or band and / or pertain to a central frequency and an associated frequency interval. It may be considered that a carrier com- 2585 prises 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 neighbouring in frequency domain.

[0343] It should be noted that the term “radio” in this disclosure may be considered to pertain to 2590 wireless communication in general, and may also include wireless communication utilising millimeter waves, in particular above one of the thresholds 10 GHz or 20 GHz or 50 GHz or 52 GHz or 52.6 GHz or 60 GHz or 72 GHz or 100 GHz or 114 GHz. Such communication may utilise one or more carriers, e.g. in FDD and / or carrier aggregation. Upper frequency boundaries may correspond to 300 GHz or 200 GHz or 120 GHz or any of the thresholds 2595 larger than the one representing the lower frequency boundary. A radio node, in particular a network node or a terminal, may generally be any device adapted for transmitting and / or receiving radio and / or wireless signals and / or data, in particular communication data, in particular on at least one carrier. The at least one carrier may comprise a carrier accessed based on an LBT procedure (which may be called 2600

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

[0345] Receiving or transmitting on a cell or carrier may refer to receiving or transmitting utilizing a frequency (band) or spectrum associated to the cell or carrier. A cell may generally comprise and / or be defined by or for one or more carriers, in particular at least one car- 2605 rier 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 communication / transmission and DL communication / transmission, e.g., in TDD-based approaches. 2610

[0346] A channel may generally be a logical, transport or physical channel. A channel may comprise and / or be arranged on one or more carriers, in particular a plurality of subcarriers. A channel carrying and / or for carrying control 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 sig- 2615 nailing / user information may be considered a data channel, in particular if it is a physical layer channel and / or if it carries user plane information. A channel may be defined for a specific communication direction, or for two complementary communication directions (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 2620 channel for low latency and / or high reliability transmission, in particular a channel for Ultra- Reliable Low Latency Communication (URLLC), which may be for control and / or data.

[0347] 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 2625 associated carrier. Accordingly, a symbol may be considered to indicate a time interval having a symbol time length in relation to frequency domain. A symbol time length may be dependent on a carrier frequency and / or bandwidth and / or numerology and / or subcarrier spacing of, or associated to, a symbol. Accordingly, different symbols may have different symbol time lengths. In particular, numerologies with different subcarrier 2630 spacings may have different symbol time length. Generally, a symbol time length may be based on, and / or include, a guard time interval or cyclic extension, e.g. prefix or postfix. A sidelink may generally represent a communication channel (or channel structure) between two UEs and / or terminals, in which data is transmitted between the participants (UEs and / or terminals) via the communication channel, e.g. directly and / or without 2635 being relayed via a network node. A sidelink may be established only and / or directly via air interface / s of the participant, which may be directly linked via the sidelink communication channel. In some variants, sidelink communication may be performed without interaction by a network node, e.g. on fixedly defined resources and / or on resources negotiated between the participants. Alternatively, or additionally, it may be considered 2640 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.

[0348] 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 2645 of LTE. A sidelink may be implemented in the context of V2x communication (Vehicular communication), e.g. V2V (Vehicle-to- Vehicle), V2I (Vehicle-to-Infrastructure) and / or V2P (Vehicle-to- Person). Any device adapted for sidelink communication may be considered a user equipment or terminal.

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

[0350] 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 2665

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

[0352] Communication or communicating may generally comprise transmitting and / or receiv- 2675 ing 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 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 2680 to comprise reception utilising the sidelink, e.g. associated resources and / or transmission formats and / or circuitry and / or the air interface. Sidelink control information (e.g., SCI) may generally be considered to comprise control information transmitted utilising a sidelink.

[0353] Generally, carrier aggregation (CA) may refer to the concept of a radio connection and / or 2685 communication link between a wireless and / or cellular communication network and / or network node and a terminal or on a sidelink comprising a plurality of carriers for at least one direction of transmission (e.g. DL and / or UL), as well as to the aggregate of carriers.

[0354] 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 2690 as component carriers (CC). In such a link, data may be transmitted over more than one of the carriers and / or all the carriers of the carrier aggregation (the aggregate of carriers). A carrier aggregation may comprise one (or more) dedicated control carriers and / or primary carriers (which may e.g. be referred to as primary component carrier or PCC), over which control information may be transmitted, wherein the control information may 2695 refer to the primary carrier and other carriers, which may be referred to as secondary carriers (or secondary component carrier, SCC). However, in some approaches, control information may be sent over more than one carrier of an aggregate, e.g. one or more PCCs and one PCC and one or more SCCs.

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

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

[0357] A configuration or schedule, like a mini-slot configuration and / or structure configuration, may schedule transmissions, e.g. for the time / transmissions it is valid, and / or 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 2720 signalling to be received by the device for which it is scheduled, depending on which side of a communication the device is. It should be noted that downlink control information or specifically DCI signalling may be considered physical layer signalling, in contrast to 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 2725 consuming it may be considered, at least partially due to the information contained in such signalling having to be passed on through several layers, each layer requiring processing and handling.

[0358] A scheduled transmission, and / or transmission timing structure like a mini-slot or slot, may pertain to a specific channel, in particular a physical uplink shared channel, a physical 2730 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 particular a shared phys- 2735 ical channel, for example a physical uplink shared channel or physical downlink shared channel. For such channels, semi-persistent configuring may be particularly suitable.

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

[0360] 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 2745 symbols in time, which may be configured or configurable, e.g. by (UE-specific) dedicated signalling (which may be single-cast, for example addressed to or intended for a specific UE), e.g. on a PDCCH, or RRC signalling, or on a multicast or broadcast channel.

[0361] 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 2750 configured to be after the control region in time. A control region may be associated, e.g. via configuration and / or determination, to one or more specific UEs and / or formats of PDCCH and / or DCI and / or identifiers, e.g. UE identifiers and / or RNTIs or carrier / cell identifiers, and / or be represented and / or associated to a CORESET and / or a search space. 2755

[0362] 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.

[0363] System information signalling may comprise and / or represent signalling indicating one or 2760 more system parameters, in particular timing and / or synchronisation, and / or numerology and / or a system identity (e.g. beam identity and / or cell ID and / or node ID and / or network ID). System information signalling may comprise broadcast signalling or multicast signalling; it may be beam-formed signalling, or non-beam-formed. In some cases, system information signalling may comprise synchronisation signalling, e.g. PSS and / or 2765

[0364] SSS, and / or reference signalling, e.g. DM-RS, and / or data signalling, e.g. on a broadcast channel like PBCH, or on a data channel like PDSCH, e.g. suitable for broadcast or multicast, or scrambled with an ID provided in earlier signalling or predefined in a standard. Such data signalling may comprise encoded information, e.g. with error detection coding and / or error correction coding. System information signalling may comprise 2770

[0365] System Information, e.g. a Master Information Block (MIB) and / or one or more System Information Blocks (SIB). System information signalling may be carried on a SSB beam; in some cases, different parts of system information may be transmitted in different signallings. For example, a MIB may be transmitted with signalling on a broadcast channel like PBCH and / or with synchronisation signalling (like a SSB), while a SIB1 or other 2775 SIBn may be transmitted on a data channel, e.g. a PDSCH, which may be scheduled with a corresponding control channel message like a DCI (such transmission may may singlecast, multi-cast / groupcast, or broadcast).

[0366] 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 2780 context of this disclosure, it should be noted that a reference to a symbol for ease of reference may be interpreted to refer to the time domain projection or time interval or time component or duration or length in time of the symbol, unless it is clear from the context that the frequency domain component also has to be considered. Examples of transmission timing structures include slot, subframe, mini-slot (which also may be considered a 2785 substructure of a slot), slot aggregation (which may comprise a plurality of slots and may be considered a superstructure of a slot), respectively their time domain component. A 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 2790 structure (which may also be considered or implemented as synchronisation structure) may be defined by a succession of such transmission timing structures, which may for example define a timing grid with symbols representing the smallest grid structures. A transmission timing structure, and / or a border symbol or a scheduled transmission may be determined or scheduled in relation to such a timing grid. A transmission timing 2795 structure of reception may be the transmission timing structure in which the scheduling control signalling is received, e.g. in relation to the timing grid. A transmission timing structure may in particular be a slot or subframe or in some cases, a mini-slot.

[0367] Feedback signalling may be considered a form or control signalling, e.g. uplink or sidelink control signalling, like UCI (Uplink Control Information) signalling or SCI (Sidelink Con- 2800 trol Information) signalling. Feedback signalling may in particular comprise and / or represent acknowledgement signalling and / or acknowledgement information and / or measurement reporting.

[0368] Signalling utilising, and / or on and / or associated to, resources or a resource structure may be signalling covering the resources or structure, signalling on the associated frequency / ies 2805 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 scheduled for transmissions or reception of transmissions). A resource substructure, e.g. a feedback resource structure, may gener- 2810 ally be continuous in time and / or frequency, within the associated intervals. It may be considered that a substructure, in particular a feedback resource structure, represents a rectangle filled with one or more resource elements in time / frequency space. However, in some cases, a resource structure or substructure, in particular a frequency resource range, may represent a non-continuous pattern of resources in one or more domains, e.g. 2815 time and / or frequency. The resource elements of a substructure may be scheduled for associated signalling.

[0369] 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, 2820 and / or signalling associated to a specific channel like PUSCH, PDSCH, PUCCH, PDCCH, PSCCH, PSSCH, etc.).

[0370] 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 2825 generally pertain to configuration / transmission valid and / or scheduled and / or configured for (relatively) short timescales and / or a (e.g., predefined and / or configured and / or 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 2830 be based on low-level signalling, e.g. control signalling on the physical layer and / or MAC layer, in particular in the form of DCI or SCI. Periodic / semi-static may pertain to longer timescales, e.g. several slots and / or more than one frame, and / or a non-defined number of occurrences, e.g., until a dynamic configuration contradicts, or until a new periodic configuration arrives. A periodic or semi-static configuration may be based on, and / or be 2835 configured with, higher-layer signalling, in particular RCL layer signalling and / or RRC signalling and / or MAC signalling.

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

[0372] For example, the concepts and variants are partially described in the context of Long Term Evolution (LTE) or LTE- Advanced (LTE-A) or New Radio mobile or wireless communications technologies; however, this does not rule out the use of the present concepts 2845 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. Had or IEEE 802.11 ay. While described variants may pertain to certain Tech- nical Specifications (TSs) of the Third Generation Partnership Project (3GPP), it will be appreciated that the present approaches, concepts and aspects could also be realized in 2850 connection with different Performance Management (PM) specifications.

[0373] 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 2855 purpose computer. It will also be appreciated that while the variants described herein are elucidated in the context of methods and devices, the concepts and aspects presented herein may also be embodied in a program product as well as in a system comprising control circuitry, e.g. a computer processor and a memory coupled to the processor, wherein the memory is encoded with one or more programs or program products that 2860 execute the services, functions and steps disclosed herein.

[0374] 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 described herein or without 2865 sacrificing all of its advantageous effects. The aspects presented herein can be varied in many ways.

[0375] Some useful abbreviations comprise

[0376] Abbreviation Explanation

[0377] ABF Analog beamformer, fanout to antenna+beamforming

[0378] ACK / NACK Acknowledgment / Negative Acknowledgement

[0379] Ant Antenna

[0380] ARQ Automatic Repeat reQuest

[0381] BB BaseBand

[0382] Beamindex IF beamindex interface

[0383] BER Bit Error Rate

[0384] BI Beam Index

[0385] BLER Block Error Rate

[0386] BPSK Binary Phase Shift Keying

[0387] BWP BandWidth Part

[0388] CAZAC Constant Amplitude Zero Cross Correlation

[0389] CB Code Block

[0390] CBB Code Block Bundle

[0391] CBG Code Block Group

[0392] CDM Code Division Multiplex

[0393] CE Control Element, in particular for the MAC layer

[0394] CM Cubic Metric

[0395] Comm RXBB communication receiver baseband

[0396] CORESET Control Resource Set

[0397] CP Cyclic Prefix

[0398] CP rem CP removal

[0399] CQI Channel Quality Information

[0400] CRC Cyclic Redundancy Check

[0401] CRS Common reference signal

[0402] CSI Channel State Information

[0403] CSI-RS Channel state information reference signal

[0404] DAI Downlink Assignment Indicator

[0405] DCI Downlink Control Information

[0406] DFE Digital Frontend

[0407] DFT Discrete Fourier Transform

[0408] DFTS-FDM DFT-spread-FDM

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

[0410] FDD Frequency Division Duplex FDE Frequency Domain Equalisation FDF Frequency Domain Filtering FDM Frequency Division Multiplex FFT Fast Fourier Transform GPIO General Purpose Input Output HARQ Hybrid Automatic Repeat Request IAB Integrated Access and Backhaul IE Information Element, in particular for RRC layer IFFT Inverse Fast Fourier Transform Im Imaginary part, e.g. for pi / 2*BPSK modulation IR Impulse Response ISI Inter Symbol Interference JCAS Joint Communication and Sensing MBB Mobile Broadband MGS Modulation and Coding Scheme MIMO Multiple-input-multiple-output MRC Maximum-ratio combining MRT Maximum-ratio transmission MU-MIMO Multiuser multiple- input-multiple-output

[0411] OFDM / A Orthogonal Frequency Division Multiplex / Multiple Access PAPR Peak to Average Power Ratio PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PRACH Physical Random Access CHannel PRB Physical Resource Block PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel (P)SCCH (Physical) Sidelink Control Channel PSS Primary Synchronisation Signal(ing) PT-RS Phase Tracking Reference signalling (P)SSCH (Physical) Sidelink Shared Channel QAM Quadrature Amplitude Modulation OGG Orthogonal Cover Code QPSK Quadrature Phase Shift Keying PCI Physical Cell Identity PSD Power Spectral Density RAN Radio Access Network RAT Radio Access Technology RB Resource Block

[0412] RE Resource Element

[0413] Re Real part (e.g., for pi / 2*BPSK) modulation

[0414] RF Radio Frequency

[0415] RNTI Radio Network Temporary Identifier

[0416] RO Random Access Occasion or Opportunity; e.g., time / frequency resources indicated fo RA preamble transmission

[0417] RRC Radio Resource Control

[0418] RX Receiver, Reception, Reception-related / side

[0419] SA Scheduling Assignment

[0420] SBFD Subband Full Duplex

[0421] SC-FDE Single Carrier Frequency Domain Equalisation

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

[0423] SCI Sidelink Control Information scs Subcarrier Spacing

[0424] SDT Small Data Transmission

[0425] SINR Signal-to-interference-plus-noise ratio

[0426] SIR Signal-to-interference ratio

[0427] SNR Signal-to-noise-ratio

[0428] SPI Serial to Parallel Interface

[0429] SR Scheduling Request

[0430] SRS Sounding Reference Signal(ing) sss Secondary Synchronisation Signal(ing)

[0431] SVD Singular- value decomposition

[0432] TB Transport Block

[0433] TDD Time Division Duplex

[0434] TDM Time Division Multiplex

[0435] T-RS Tracking Reference signalling or Timing Reference signalling

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

[0437] UCI Uplink Control Information

[0438] UDC Up-Down Converter, mixing from BBj-^RF

[0439] UE User Equipment

[0440] URLLC Ultra Low Latency High Reliability Communication VL-MIMO Very- large multiple-input-multiple-output WD Wireless Device Wfg Waveform Generator ZC Zadoff-Chu ZF Zero Forcing ZP Zero-Power, e.g. muted CSI-RS symbol

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

Claims

CLAIMS1. Method of operating a wireless device in a wireless communication network, the method comprising transmitting random access signalling at a transmission random access opportunity based on a first random access configuration indicating a set of first random access opportunities, and based on a second random access configuration indicating a set of sec- 2875 ond random access opportunities, wherein the transmission random access opportunity is a first random access opportunity or a second random access opportunity determined based on validating one or more of the first and / or second random access opportunities.

2. Wireless device for a wireless communication network, the wireless device being adapted for transmitting random access signalling at a transmission random access opportunity 2880 based on a first random access configuration indicating a set of first random access opportunities, and based on a second random access configuration indicating a set of second random access opportunities, wherein the transmission random access opportunity is a first random access opportunity or a second random access opportunity determined based on validating one or more of the first and / or second random access opportunities. 28853. Method of operating a network node in a wireless communication network, the method comprising receiving, from a wireless device, random access signalling at a transmission random access opportunity according to a first random access configuration indicating a set of first random access opportunities, and according to a second random access configuration indicating a set of second random access opportunities, wherein the transmission 2890 random access opportunity is a first random access opportunity or a second random access opportunity determined according to validating one or more of the first and / or second random access opportunities.

4. Network node for a wireless communication network, the network node being adapted for receiving, from a wireless device, random access signalling at a transmission random 2895 access opportunity according to a first random access configuration indicating a set of first random access opportunities, and according to a second random access configuration indicating a set of second random access opportunities, wherein the transmission random access opportunity is a first random access opportunity or a second random access opportunity determined according to validating one or more of the first and / or second random 2900 access opportunities.

5. Method or device according to one of the preceding claims, wherein validating is based on one or more validation rules, which may be indicated with the second RA configuration.

6. Method or device according to one of the preceding claims, wherein the transmissionrandom access opportunity is a first random access opportunity based on a fallback rule. 29057. Method or device according to one of the preceding claims, wherein validating comprises determining a second random access opportunity to be valid if it does not collide with a first random access opportunity.

8. Method or device according to one of the preceding claims, wherein validating comprises determining a second random access opportunity to be valid if it does not collide with a 2910 first random access opportunity in time domain and / or frequency domain.

9. Method or device according to one of the preceding claims, wherein transmitting is in Subband Full Duplex, SBFD, operation, in particular in a SBFD slot and / or subframe and / or one or more SBFD symbols.

10. Method or device according to one of the preceding claims, wherein validating com- 2915 prises determining a second random access opportunity to be valid if it does not start and / or end and / or is not located in the same slot and / or subframe and / or subslot and / or transmission timing structure as a first random access opportunity.

11. Method or device according to one of the preceding claims, wherein the second random access configuration pertains to Subband Full Duplex, SBFD, operation. 292012. Method or device according to one of the preceding claims, wherein the transmission random access opportunity is a random access opportunity determined valid.

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

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

Images