Frequency domain resources for IAB

[0001] This application is a Submission Under 35 U.S.C. § 371 for U.S. National Stage Patent Application of International Application Number: PCT/SE2021/050025, filed Jan. 18, 2021 entitled “FREQUENCY DOMAIN RESOURCES FOR IAB,” the entirety of which is incorporated herein by reference.

[0002] This disclosure pertains to wireless communication technology, in particular in the context radio access technologies.

[0003] For radio access networks, radio nodes are connected to a core network, to allow communication between terminals in different cells provided by different radio nodes. The radio nodes are usually connected to the core network by wire or cable, in particular via optical fibre. However, it is not always practical or feasible to arrange such a land-bound connection. For such cases, there may be employed relay nodes or nodes for integrated access and backhaul (IAB). An IAB node may on the one hand provide radio access to terminals or user equipments (UEs), and on the other hand may communicated to a parent (IAB) node via radio technology, to be relayed or routed to a core network, e.g. via a donor node. Due to sharing time/frequency resources with terminals and other nodes, the use of IAB nodes requires new approaches of managing resources and node behaviour.

[0004] It is an object of the present disclosure to provide approaches facilitating improved IAB handling, in particular regarding frequency domain resources. The approaches allow efficient indication of the availability of soft frequency domain resources, with low signaling overhead and/or limited changes to legacy systems.

[0005] The approaches are particularly advantageously implemented in a 5^th Generation (5G) telecommunication network or 5G radio access technology or network (RAT/RAN), in particular according to 3GPP (3^rd Generation Partnership Project, a standardisation organization). A suitable RAN may in particular be a RAN according to NR, for example release 15 or later, or LTE Evolution.

[0006] There is disclosed a method of operating an IAB parent node for a wireless communication network. The method comprises transmitting, to an IAB child node, an indication of the availability of soft frequency resources.

[0007] Moreover, an IAB parent node for a wireless communication network is proposed. The IAB parent node is adapted for transmitting, to an IAB child node, an indication of the availability of soft frequency resources.

[0008] A method of operating an IAB child node for a wireless communication network is described. The method comprises communicating utilising soft frequency resources based on a received indication of the availability of the soft frequency resources.

[0009] An IAB child node for a wireless communication network is also considered. The IAB child node is adapted for communicating utilising soft frequency resources based on a received indication of the availability of the soft frequency resources.

[0010] The indication may be considered and/or be referred to as an availability indication. In general, the indication may be represented by one or more parameters or values or indexes and/or may be carried in one or more distinct signaling or messages, which may be on the same layer (e.g., physical layer, or higher layer), or on different layers (e.g., physical layer signaling like DCI signaling, which may point to a configuration provided with higher layer signaling, e.g. semi-static signaling like RRC signaling). The indication may be implemented according to any of approaches described herein, and/or any combination, in particular as discussed referring to the FIGS. 5 to 10.

[0011] Transmitting the indication may comprise transmitting signaling carrying and/or encoding and/o representing and/or containing and/or comprising the indication, e.g. in a DCI format, in particular a DCI format 2_5 or 2_1, or a variation thereof. Soft frequency resources may be resources in frequency space, e.g. in one or more frequency intervals. Different resources may pertain to different frequency intervals, the soft resources may be associated or allocated to, and/or configured for, the IAB child node. The resources may be configured to the child node, e.g. by the parent node and/or a donor node. Soft resources may be resources that are conditionally available to the child node (after allocation and/or configuration), e.g. based on the indication and/or one or more conditions, e.g. pertaining to operation of a MT function and/or DU function of the child node. The soft frequency resources (also referred to as soft resources for conciseness) may be transmission resources, and/or in some cases reception resources. The soft resources may be associated to one function of the IAB child node, e.g. DU function or MT function.

[0012] Communicating may generally comprise transmitting and/or receiving. Communicating based on the indication and/or utilising soft frequency resources may comprise communicating utilising the resources if they are available, e.g. for the associated function; if they are not available, they may be utilised for another function (e.g., DU instead of MT or vice versa), or not used by the child node.

[0013] The indication may generally indicate whether the soft frequency resources and, optionally, soft time resources, are available, and/or when and/or in which slot/s and/or symbols and/or over how many slots and/or symbols they are available.

[0014] It may be considered that the indication is represented by DCI signaling and/or higher layer signaling. This allows dynamic and/or semi-static indication of availability.

[0015] In general, the indication may comprise a DCI message that indexes and/or point to a configuration. The configuration may indicate combinations of available soft frequency resources, one of which may be pointed to by the DCI message. The configuration may be represented or representable by one table, or a set of tables, and/or may correspond to one or more availabilityCombinations and/or resourceAvailability or sets thereof, e.g., of a RRC information element or group of elements. The DCI may comprise one or more values or indexes or fields that may point to a specific availabilitycombination, e.g. for a specific frequency interval or multiple frequency intervals (e.g., in a group of intervals).

[0016] A IAB parent node, may comprise, and/or be adapted for utilising, processing circuitry and/or radio circuitry, in particular one or more transceivers and/or transmitters and/or receivers, for communicating and/or transmitting the indication, and/or for providing CU and/or DU and/or MT functionality and/or for providing one or more communication links, e.g. to one or more IAB child nodes and/or UEs. An IAB child node may comprise, and/or be adapted for utilising, processing circuitry and/or radio circuitry, in particular one or more receivers and/or transceivers and/or transmitters, for receiving the indication and/or communicating based on the indication, and/or for providing DU and/or MT functionality and/or for providing one or more communication links, e.g. to one or more IAB child nodes and/or UEs. A child IAB node may be connected or connectable to a first parent IAB node via a first backhaul link, and/or may perform random access to access the network node as parent node, and/or may be adapted to communicate with one or more child nodes and/or UEs.

[0017] A frequency interval may in particular be allocated or configured for a DU function of a IAB child node. The interval may be represented or representable in resource blocks or RB groups; intervals may be indicated to be available individually, or in groups (e.g. with a group ID). Which intervals are associated to a group may be configured or configurable, and/or predefined.

[0018] There is also considered a program product comprising instructions adapted for causing processing circuitry to control and/or perform a method as described herein. A carrier medium arrangement carrying and/or storing a program product disclosed herein is proposed.

[0019] A communication link may be a backhaul link and/or access link. A backhaul link, e.g. a first and/or second backhaul links may be in a set of parent backhaul links to a number of parent node larger than two. Any link-specific parameter mentioned may pertain to one of the link provides by a parent of the set. A backhaul link from a parent IAB node (also referred to as parent node) may be controlled regarding timing and/or synchronisation by the parent, e.g. via DCI signaling and/or SS/PBCH block signaling, in particular with signaling indicating timing advance and/or timing advance adjustment, and/or primary and/or secondary synchronisation signaling. Alternatively, or additionally, the backhaul link may be power-controlled by the parent node, e.g. via TPC commands in DCI. In general, the parent node may control physical layer aspect of communication with a child node (the IAB node) with suitable control signaling, e.g. DCI signaling. A backhaul link may generally be a wireless connection between network nodes (IAB nodes), over which signaling from a (wireless or radio) access link or another backhaul link may be carried or transported or routed, e.g. to another IAB node. In particular, signaling between a terminal not in direct radio access with a donor node may be carried over one or more backhaul links. The backhaul links may be in mm-wave ranges. It may be considered that backhaul link and access links are in different frequency ranges and/or carriers. For example, access links may be lower in frequency, e.g. below 6 GHz. Backhaul links may share a frequency range and/or carrier and/or carrier aggregation.

[0020] Providing a communication link may comprise providing a cell and/or uplink and/or downlink communication for the link, e.g. for access and/or backhaul. The IAB node may provide power control and/or timing and/or synchronisation for a child (e.g., terminal or IAB child node) on the communication link it provides. Providing a communication link may comprise transmitting and/or receiving signaling on the link, based on the communication timing. The timing for transmission and reception on the communication may be linked, e.g. based on distance to the communication partner and/or timing advance or timing advance adjustment for the communication partner (e.g., a terminal, if it is an access link, and an IAB node if it is a backhaul link). In general, the communication timing may be used for multiple communication links provided by the IAB node, e.g. an access link and/or one or more backhaul links. An access link may pertain to a cell, or more than one cell, provided by the IAB node, which may allow radio access for a plurality of terminals. A backhaul link may be device-specific, e.g. with strong beamforming to a stationary child node.

[0021] A donor node may generally be an IAB node with higher-layer control functionality, and/or an IAB node with a cable connection to a core network, e.g. via fibre or wire. The donor node may provide synchronisation via synchronisation signaling, e.g. SS/PBCH block signaling, synchronising its child nodes, which then provide similar synchronisation to their child nodes, etc. Each synchronisation step may be based on the parent synchronisation, such that in general, the whole IAB arrangement connected to one donor may be similarly synchronised. It should be noted that individual transmission and reception timing may be based on the synchronisation, but may be shifted, e.g. due to delay and/or signal travel time effects, which may be accommodated for e.g. via timing advance and/or timing advance adjustment functionality. Also, the synchronisation may be considered to pertain to the physical layer, e.g. in regard to the timing grid used. When specific signaling is transmitted on this grid may be determined on a higher layer, e.g. by a scheduler and/or the MAC or higher layer.

[0022] The IAB node may be connected, or adapted to be connected or connectable, to a plurality N of parent nodes via associated backhaul links, e.g. with corresponding timings. Thus, complex IAB node arrangement with high levels of redundancy and/or high data throughput may be provided. The communication timing may in general be based on the number of parent nodes of the IAB node, and/or hop-count of a parent. The hop-number may indicate the number of backhaul links signaling has to go over from a terminal on an access link of the IAB node to the donor. Links with lower hop-count may be weighed higher than links with higher hop-count. For example, a weight may be dependent on 1/HC, with HC the hop-count of a link or associated to a parent. It should generally be considered that each parent may be associated to one backhaul link to the IAB node.

[0023] A program product comprising instructions adapted for causing processing circuitry to control and/or perform any method described herein may be considered. Also, there is described a carrier medium arrangement carrying and/or storing such a program product.

[0024] The approaches described herein allow use of a downlink timing considering influence from multiple parents, which is particularly suitable for a multi-parent IAB arrangement. In particular, the timing accommodates for different operational conditions on different links with different parents, and provides a stable environment, even if communication is relayed or routed over different links or paths at different times.

[0025] In the context of this disclosure, a backhaul link to a parent may be referred to as UL backhaul link, a backhaul link to a child may be referred to as DL backhaul link. For each backhaul link, there may be communication in both directions, from parent to child and reverse. Communication on a backhaul from child to parent may be considered UL communication, or UL component of the backhaul link, and from parent to child may be considered DL communication, or DL component of the backhaul link. Thus, for an IAB node with an UL backhaul link, UL communication goes from the IAB node to a parent node, and DL communication from parent to the IAB node, for this backhaul link. For a DL backhaul link, UL communication would go from the child to the IAB node, and DL communication from the IAB node to the child, for the backhaul link. An analogous terminology may be used for an access link, providing radio access to terminals. In some cases, the connection from a child to a parent may be referred to as northbound, the connection from a parent to a child as southbound.

[0026] An IAB node may be logically divided in a mobile terminal (MT) functional part and a network node (gN) functional part. A backhaul link may comprise corresponding parts. The MT part may provide communication with parent nodes based on and/or similar to UE-type radio access, and/or provide termination for associated interface/s and/or protocol layer/s. The network node part may provide communication with UEs and/or child nodes, and/or higher layer communication with other IAB nodes, and/or provide termination for associated interface/s and/or protocol layer/s. The network node part may be logically subdivided into a DU part and a CU part, which may be associated to different layers of the protocol stack. It may be considered that network node functionality and UE functionality are provided by different radio circuitries, which may be operable separately and/or independent of each other. AN IAB node, e.g. an IAB parent or child node, may be adapted for FDM operation, e.g. to allow operation on a set of frequency intervals.

[0027] In general, an IAB node may be expected to communicate in half-duplex mode. In half-duplex mode, it may either transmit or receive, e.g. for a given functional part or for all functional parts. For example, it may operate either as network node (gNB functionality) or as mobile terminal (UE functionality) at any given point in time. This significantly limits the amount of self-interference of a node, in particular in context of the significantly different capabilities and power characteristics between UEs and gNB, respectively associated functionality of IAB nodes. However, this leads to certain limitations on IAB nodes. For example, an IAB node has to provide types of broadcasts and/or reference signaling like synchronisation signaling (in particular SS/PBCH blocks), e.g. to enable random access for UEs. Transmission of such signaling usually is synchronised over networks and/or network nodes and usually occurs with a given synchronisation periodicity, e.g. one of 10 ms, 20 ms, 40 ms, 80 ms. An IAB node that transmits such signaling thus cannot receive the SS/PBCH blocks provided by other IAB nodes (e.g., parent node/s and/or potential parent node/s). To enable an IAB node to receive such signaling, additional SS/PBCH signaling may be scheduled (e.g., by a donor node and/or CU functionality) for IAB nodes, which may occur inside the intervals of the synchronisation periodicity intervals. This additional SS/PBCH signaling may be at timing occasions and/or patterns that are different for different IAB nodes. In particular, the additional signaling may be scheduled such that at certain occasions, an IAB node can receive the additional signaling from other IAB nodes, without having to transmit it itself.

[0028] The synchronisation signaling (e.g., SSB or SS/PBCH block) provided by IAB nodes in general may be the same (e.g., to provide cell extension) or different, e.g. if each IAB node has its own cell with its own cell ID (the cell ID may be encoded in the synchronisation signaling, e.g. PSS and/or SSS). The synchronisation signaling may in general comprise a master information block and/or one or more system information blocks, and/or indicate a cell ID like a physical cell ID and/or information about numerology and/or carrier and/or timing and/or bandwidth part (e.g., initial bandwidth part) and/or search space for control signaling (e.g., for receiving DCI indicating on which resources a PDSCH transmission carrying remaining minimum system information like system information blocks is transmitted) used, and/or indicate information regarding random access, e.g. random access occasions and/or random access preamble format/s. In general, the synchronisation signaling may comprise distinct parts, e.g. primary synchronisation signaling (PSS) and/or secondary synchronisation signaling (SSS) and/or broadcast information (PBCH) and/or demodulation reference signaling (DMRS). One or more random access parameters may be included in a system information block, in particular a SIB1 or SIB2 or MIB.

[0042] In the following, variants are described in the context of NR, however, the approaches may be implemented in different contexts.

[0043] Densification via the deployment of increasing base stations (be them macro or micro base stations) is one of the mechanisms that can be employed to satisfy the ever-increasing demand for more and more bandwidth/capacity in mobile networks. Due to the availability of more spectrum in the millimeter wave (mmw) band, deploying small cells that operate in this band is an attractive deployment option for these purposes. However, deploying fiber to the small cells, which is the usual way in which small cells are deployed, can end up being very expensive and impractical. Thus, employing a wireless link for connecting the small cells to the operator's network is a cheaper and practical alternative with more flexibility and shorter time-to-market. One such solution is an Integrated Access and Backhaul (IAB) network, where the operator can utilize part of the radio resources for the backhaul link.

[0044] In FIG. 1, an IAB deployment that supports multiple hops is presented. The IAB donor node (in short IAB donor) has a wired connection to the core network and the IAB nodes are wirelessly connected using NR to the IAB donor, either directly or indirectly via another IAB node. The connection between IAB donor/node and UEs is called access link, whereas the connection between two IAB nodes or between an IAB donor and an IAB node is called backhaul link.

[0045] Furthermore, as shown in FIG. 2, the adjacent upstream node which is closer to the IAB donor node of an IAB node is referred to as a parent node of the IAB node. The adjacent downstream node which is further away from the IAB donor node of an IAB node is referred to as a child node of the IAB node. The backhaul link between the parent node and the IAB node is referred to as parent (backhaul) link, whereas the backhaul link between the IAB node and the child node is referred to as child (backhaul) link.

[0046] FIG. 1 shows an exemplary setup of a backhaul arrangement. An IAB donor node (also referred to as donor) may be connected to a core network via a wireline connection (cable or fibre, e.g.). It provides radio access for terminals, and a wireless connection to another network node, an IAB node 1. The IAB node 1 also provides radio access for terminals (via an access link), and communicates to the donor via a wireless connection providing a backhaul link. Moreover, it provides a backhaul link to an IAB node 2. FIG. 1 thus shows a multi-hop arrangement, wherein communication via IAB node 2 passes via two backhaul links until it reaches the IAB donor. In general, an IAB node may be any node that is adapted for providing radio access to one or more terminals/UEs (via access links), and also may access and/or provide one or more backhaul links. A backhaul link may generally be provided to route and/or forward communication from or to a terminal to another IAB node, e.g. using radio signaling. Backhaul and access links may in general use the same or different resource structures. In particular, they may operate on the same carriers and/or carrier aggregations. The carriers used may in particular be mm-wave carriers, e.g. above 6 GHz or 20 GHz or 30 GHz in frequency. For each IAB node, each backhaul link terminated at an IAB node to be used to reach a donor may be counted as one hop. For example, an IAB node connected to a donor directly with a backhaul link would have a hop-count of 1, IAB node 2 in FIG. 1 has one of 2. For multiple-parent scenarios, different paths to a donor may have different hop-counts, or the same, depending on the arrangement.

[0047] FIG. 2 shows a different view of an IAB arrangement. From an IAB nodes point of view, it may be connected via a backhaul (BH) link to a parent node, which may be closer to the donor node (or be the donor node itself) in terms of backhaul links needed to reach the donor. Each backhaul link may comprise an UL component and DL component, which may for example be in TDD or FDD operation. In UL, communication may be transmitted in the direction of the donor. In DL, communication may be from the donor, e.g. to a terminal connected to the IAB node, or another IAB connected via another backhaul link. A device to which an IAB node provides radio access, either via an access link or backhaul link, may be considered a child node. An IAB node may in general process information received via an access link or backhaul link, e.g. to route its content to a target terminal or other IAB node or donor. It may be considered that an IAB node (e.g., as parent node) provides and determines control signaling on the access and/or backhaul links it provides. The control signaling may in particular be physical layer control signaling, e.g. DCI signaling, in particular for scheduling and/or power control and/or timing. Some IAB nodes, in particular a donor node, may be adapted to also provide higher-layer control, in particular RRC layer control.

[0048] In general, it may be assumed that an IAB node is aware of its children and parents (IAB children and parents). In particular, it may be aware of all IAB nodes reachable via a backhaul link it provides itself (e.g., children of children, or more distant children). It may be aware of higher-layer parents like grandparents, but in some cases not, as it may be adapted to follow control signaling by its direct parent. A parent of a parent may be considered a grandparent, a child of a child a grandchild, etc. A donor may be aware of all IAB nodes reachable via backhaul links provided by the donor, e.g. all children. This may be due to installation, or automatic communication between nodes when setting up.

[0049] It should be noted that for a child with multiple parents, not all backhaul links have to be used for communicating data (e.g., carrying data from or for a terminal), but a backhaul link may be kept in reserve, e.g. established and/or maintained and/or set to sleep or idle, temporarily. However, it may be considered that signaling for a terminal, or for different terminals, is distributed over time between different backhauls. The use of multiple parents may provide improved reliability and/or a possible fallback. In some cases, different backhaul links may be used for different channels and/or communications and/or terminals based on reliability or quality requirements, and/or latency requirements and/or service agreements. A connection via a backhaul link may be in RRC idle and/or in DRX and/or may be upheld by regularly providing reference signaling and/or control signaling, even if no data signaling or signaling for or from a terminal is to be carried on the backhaul link.

[0050] As one major difference of the IAB architecture compared to Rel-10 LTE relay (besides lower layer differences) is that the IAB architecture adopts the Central-Unit/Distributed-Unit (DU/DU) split of gNBs in which time-critical functionalities are realized in DU closer to the radio, whereas the less time-critical functionalities are pooled in the CU with the opportunity for centralization. Based on this architecture, an IAB-donor contains both CU and DU functions. In particular, it contains all CU functions of the IAB-nodes under the same IAB-donor. Each IAB-node then hosts the DU function(s) of a gNB. In order to be able to transmit/receive wireless signals to/from the upstream IAB-node or IAB-donor, each IAB-node has a mobile termination (MT), a logical unit providing a set of UE-like functions. Via the DU, the IAB-node establishes RLC-channels to UEs and/or to MTs of the connected IAB-node(s). Via the MT, the IAB-node establishes the backhaul radio interface towards the serving IAB-node or IAB-donor. FIG. 3 shows a reference diagram for a two-hop chain of IAB-nodes under an IAB-donor.

[0051] Wireless backhaul links are vulnerable to blockage, e.g., due to moving objects such as vehicles, due to seasonal changes (foliage), severe weather conditions (rain, snow or hail), or due to infrastructure changes (new buildings). Such vulnerability also applies to IAB-nodes. Also, traffic variations can create uneven load distribution on wireless backhaul links leading to local link or node congestion. In view of those concerns, the IAB topology supports redundant paths as another difference compared to the Rel-10 LTE relay.

[0052] The following topologies are considered in IAB as shown in FIG. 4:

[0053] Spanning tree (ST) and Directed acyclic graph (DAG). FIG. 4 specifically shows non-limiting examples for ST and DAG. The arrow indicates the directionality of the graph edge.

[0054] In general, one IAB node may have multiple child nodes and/or have multiple parent nodes. The multi-connectivity or route redundancy may be used for back-up purposes. It is also possible that redundant routes are used concurrently, e.g., to achieve load balancing, reliability, etc.

[0055] In case of in-band operation, the IAB-node is typically subject to the half-duplex constraint, e.g., an IAB-node can only be in either transmission or reception mode at a time. There is mainly considered the time-division multiplexing (TDM) case, where the MT and DU resources of the same IAB-node are separated in time. Based on this consideration, the following resource types are defined for IAB MT and DU, respectively.

[0056] From an IAB-node MT point-of-view, the following time-domain resources can be indicated for the parent link:

• • [0057] Downlink (DL) time resource
  • [0058] Uplink (UL) time resource
  • [0059] Flexible (F) time resource

[0060] From an IAB-node DU point-of-view, the child link has the following types of time resources:

• • [0061] DL time resource
  • [0062] UL time resource
  • [0063] F time resource
  • [0064] Not-available (NA) time resources (resources not to be used for communication on the DU child links)

[0065] Each of the downlink, uplink and flexible time-resource types of the DU child link can belong to one of two categories:

• • [0066] Hard (H): The corresponding time resource is always available for the DU child link
  • [0067] Soft (S): The availability of the corresponding time resource for the DU child link is explicitly and/or implicitly controlled by the parent node.

[0068] The IAB DU resources in time are configured per cell, and the H/S/NA attributes for the DU resource configuration are explicitly indicated per-resource type (D/U/F) in each slot. As a result, the semi-static time-domain resources of the DU part can be of seven types in total: Downlink-Hard (DL-H), Downlink-Soft (DL-S), Uplink-Hard (UL-H), Uplink-Soft (UL-S), Flexible-Hard (F-H), Flexible-Soft (F-S), and Not-Available (NA). The coordination relation between MT and DU resources are listed in Table 1.

[0069]

TABLE 1
Coordination between MT and DU resources of an IAB-node.
	MT configuration
	DL	UL	Flexible
DU	DL-H	DU: can transmit on	DU: can transmit on	DU: can transmit on
configuration		DL unconditionally;	DL unconditionally;	DL unconditionally;
		MT: not available.	MT: not available.	MT: not available.
	DL-S	DU: can transmit	DU: can transmit	DU: can transmit
		conditionally;	conditionally;	conditionally;
		MT: available on DL.	MT: available on UL.	MT: available on DL
				& UL.
	UL-H	DU: can schedule	DU: can schedule	DU: can schedule
		UL unconditionally;	UL unconditionally;	UL unconditionally;
		MT: not available.	MT: not available.	MT: not available.
	UL-S	DU: can schedule	DU: can schedule	DU: can schedule
		UL conditionally;	UL conditionally;	UL conditionally;
		MT: available on DL.	MT: available on UL.	MT: available on DL
				& UL.
	F-H	DU: can transmit on	DU: can transmit on	DU: can transmit on
		DL or schedule UL	DL or schedule UL	DL or schedule UL
		unconditionally;	unconditionally;	unconditionally;
		MT: not available.	MT: not available.	MT: not available.
	F-S	DU: can transmit on	DU: can transmit on	DU: can transmit on
		DL or schedule	DL or schedule	DL or schedule
		UL conditionally;	UL conditionally;	UL conditionally;
		MT: available on DL.	MT: available on UL.	MT: available on DL
				& UL.
	NA	DU: not available;	DU: not available;	DU: not available;
		MT: available on DL.	MT: available on UL.	MT: available on DL
				& UL.

[0070] Parent nodes may indicate the availability of the soft time-domain DU resource using implicit indication or explicit indication. The explicit indication, referred to as Availability Indication (AI), uses DCI Format 2_5 for dynamically indicating the availability of DU Soft resource in a slot.

---------------Extract from TS 38.213------------------

[0071] If an IAB-node is provided an AvailabiltyIndicator, the IAB-node is provided an AI-RNTI by ai-RNTI and a payload size of a DCI format 2_5 by dci-PayloadSize-AI. The IAB-node is also provided a search space set configuration, by SearchSpace, for monitoring PDCCH.

[0072] For each serving cell of an IAB-DU in a set of serving cells of the IAB-DU, the IAB-DU can be provided:

• • [0073] an identity of the IAB-DU serving cell by iabDuCell/d-AI
  • [0074] a location of an availability indicator (AI) index field in DCI format 2_5 by positionInDCl-AI
  • [0075] a set of availability combinations by availabilityCombinations, where each availability combination in the set of availability combinations includes
  • [0076] resourceAvailability indicating availability of soft symbols in one or more slots for the IAB-DU serving cell, and
  • [0077] a mapping for the soft symbol availability combinations provided by resourceAvailability to a corresponding AI index field value in DCI format 2_5 provided by availabilityCombinationId

[0078] The IAB-DU can assume a same SCS configuration for availabilityCombinations for a serving cell as an SCS configuration provided by IAB-DU-Resource-Configuration-TDD-Config for the serving cell.

[0079] An AI index field value in a DCI format 2_5 indicates to an IAB-DU a soft symbol availability in each slot for a number of slots starting from the earliest slot of the IAB-DU which overlaps in time with the slot of the IAB-MT where the IAB-MT detects the DCI format 2_5. The number of slots is equal to or larger than a PDCCH monitoring periodicity for DCI format 25 as provided by SearchSpace. The AI index field includes max{┌log₂(maxAIndnex+1)┐,1} bits where maxAIindex is the maximum of the values provided by corresponding availabiltyCombinationId. An availability for a soft symbol in a slot is identified by a corresponding value resourceAvailability as provided in Table 14-3.

[0080]

TABLE 14-3
Mapping between values of resourceAvailability elements
and types of soft symbol availability in a slot
Value	Indication
0	No indication of availability for soft symbols
1	DL soft symbols are indicated available
	No indication of availability for UL and Flexible soft
	symbols
2	UL soft symbols are indicated available
	No indication of availability for DL and Flexible soft
	symbols
3	DL and UL soft symbols are indicated available
	No indication of availability for Flexible soft symbols
4	Flexible soft symbols are indicated available
	No indication of availability for DL and UL soft symbols
5	DL and Flexible soft symbols are indicated available
	No indication of availability for UL soft symbols
6	UL and Flexible soft symbols are indicated available
	No indication of availability for DL soft symbols
7	DL, UL, and Flexible soft symbols are indicated
	available

[0081] If a PDCCH monitoring periodicity for DCI format 2_5 is smaller than a duration of an availability combination of soft symbols over a number of slots that the IAB-MT obtains at a PDCCH monitoring occasion for DCI format 2_5 by a corresponding AI index field value, and the IAB-MT detects more than one DCI formats 2_5 indicating an availability combination of soft symbols in a slot, the IAB-MT expects that each of the more than one DCI formats 2_5 indicates a same value for the availability combination of the soft symbols in the slot.

----------------End extract from TS 38.213---------------

----------------Extract from TS 38.331-----------------

AvailabilityIndicator information element

[0082]

	-- ASN1START
	-- TAG-AVAILABILITYINDICATOR-START
	AvailabilityIndicator-r16 ::= SEQUENCE {
	ai-RNTI-r16 AI-RNTI-r16
	dci-PayloadSizeAI-r16 INTEGER (1..maxAI-DCI-PayloadSize-r16),
	availableCombToAddModList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16))
	OF AvailabilityCombinationsPerCell-r16 OPTIONAL, -- Need N
	availableCombToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16))
	OF AvailabilityCombinationsPerCellIndex-r16 OPTIONAL, -- Need N
	...
	}
	AI-RNTI-r16 ::= RNTI-Value
	-- TAG-AVAILABILITYINDICATOR-STOP
	-- ASN1STOP

AvailabilityCombinationsPerCell information element

[0083]

-- ASN1START
-- TAG-AVAILABILITYCOMBINATIONSPERCELL-START
AvailabilityCombinationsPerCell-r16 ::= SEQUENCE {
availabilityCombinationsPerCellIndex-r16 AvailabilityCombinationsPerCellIndex-
r16,
iab-DU-CellIdentity-r16 CellIdentity,
positionInDCI-AI-r16	INTEGER(0..maxAI-DCI-PayloadSize-r16-1)
OPTIONAL, -- Need M
availabilityCombinations-r16	SEQUENCE (SIZE
(1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombination-r16,
...
}
AvailabilityCombinationsPerCellIndex-r16 ::= INTEGER(0..maxNrofDUCells-r16)
AvailabilityCombination-r16 ::=	SEQUENCE {
availabilityCombinationId-r16	AvailabilityCombinationId-r16,
resourceAvailability-r16	SEQUENCE (SIZE
(1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7)
}
AvailabilityCombinationId-r16 ::=	INTEGER
(0..maxNrofAvailabilityCombinationsPerSet-r16-1)
-- TAG-AVAILABILITYCOMBINATIONSPERCELL-STOP
-- ASN1STOP

--------------End extract from TS 38.331---------------

[0084] FIG. 5 illustrates the signaling design for the DCI format 2_5. For each serving cell, the IAB-DU is provided with a cell identity (cell-ID), information about the location of AI information (position of information) in a DCI 2_5 and a set of availability combinations. Each availability combination contains a sequence (resourceAvailability) of elements indicating the availability of soft symbols in one or more slots for the IAB-DU serving cell and an identity number (availabilityCombinationId) to map between symbol availability combinations provided by resourceAvailability and information provided via DCI 2_5 (the indices in DCI 2_5). The provisioning to the IAB-node of the combination of the cell-ID, location information and the set of availability combinations is by using an RRC information element

[0085] Furthermore, an IAB-DU function may correspond to multiple cells, including cells operating on different carrier frequencies. Similarly, an IAB-MT function may correspond to multiple carrier frequencies. This can either be implemented by one IAB-MT unit operating on multiple carrier frequencies or be implemented by multiple IAB-MT units, each operating on different carrier frequencies. The H/S/NA attributes for the per-cell DU resource configuration should take into account the associated IAB-MT carrier frequency(ies).

[0086] Parent nodes may indicate the availability of the soft time-domain DU resource via implicit indication and explicit indication. The explicit indication, referred to as Availability Indication (AI), uses DCI Format 2_5 for dynamically indicating the availability of the IAB-DU soft resource in a slot. It is proposed introducing frequency-domain H/S/NA to allow for greater flexibility, reduced cross-link interference (CLI) and reduced latency. Approaches are described for an IAB parent node to indicate the availability of the soft frequency-domain resource utilization to an IAB-node and/or availability of hard frequency-domain resource utilization. Use of soft frequency-domain resources at an IAB-node is facilitated, to provide efficient frequency multiplexing between IAB-MT and collocated IAB-DU. Dynamic and/or flexible signaling is proposed, with low signaling overhead.

[0087] For an IAB-node capable of frequency-domain multiplexing (FDM), the IAB-MT and IAB-DU can use time-domain resources simultaneously, but may need coordination on the usage of the frequency-domain resources. A FDM-capable IAB-node may be configured or provided with frequency-domain H/S/NA. IAB-MT and IAB-DU may be provided with different priorities regarding different frequency-domain resources, which introduces higher scheduling flexibility to the IAB network. The specific way of a frequency domain configuration in terms of H/S/NA, including how the configured resource should be treated at an IAB-node may for example consider that the frequency-domain resource configuration should have the granularity of resource block groups (RBGs). In the described exemplary scenarios, it may be assumed that RBGs are used as the parameter controlling the frequency range (e.g., as allocation units), but other parameters indicating a frequency range are not precluded, e.g., PRB or BWP.

[0088] The soft DU frequency resource can be available for example due to

• • [0089] the IAB-DU operation (transmission/reception) is prioritized; and/or
  • [0090] the IAB-MT does not need the resource in question

[0091] Dynamic indication approaches may be considered. For example, a parent IAB node may provide the dynamic availability indication to the IAB node via some Layer-1 signaling.

[0092] In particular, enhancement of DCI format 2_5 may be considered.

[0093] For example, a DU-RBG ID may be introduced. The legacy DCI format 2_5 is used to indicate availability to time-domain IAB-DU soft resource. An AI index field value in a DCI format 2_5 may indicate to an IAB-DU a soft symbol availability for a sequence of slots over the whole bandwidth of the serving cell. Availability of soft symbols in one or more slots is identified by a corresponding resourceAvailability, a sequence of availability information elements; each element in resourceAvailability can take 8 values.

[0094] When transmission/reception resources of a cell can be further partitioned into multiple RBGs, there can be multiple frequency-domain soft resources RBGs associated to the same slot. In this case, multiple DCI format 2_5 can be configured, where each one corresponds to one IAB-DU RBG, with an associated DU-RBG identifier, sometimes referred to as DU-RBG-ID in the following. It should be noted that the DU-RBG size (in number of RBs included in each group) can be the different from the size of an RBG used for scheduling in a BWP on the access link, in particular, it may be larger. However, in some cases, the RBG sizes may coincide. Different DU-RBG-IDs may be associated to different frequency domain parts or subdivisions of the bandwidth; each RBG and associated ID may correspond to a particular separately allocated or allocatable frequency interval and/or may be associated to a H or S or NA in frequency domain.

[0095] In one variant, the DU-RBG-ID may be provided in addition to the cell-ID. In this case, the described availability combination table (availabilityCombinations) can be reused. In the described provisioning of availabilityCombinations, the location information is only associated to the cell-ID. In the enhanced way of provisioning availabilityCombinations, the location information is associated to both the cell-ID and DU-RBG-ID. The DCI 2_5 payload provides availability information for a certain number of slots; by adding a DU-RBG-ID, the required signalling payload size of a DCI providing information for slots and DU-RBG-ID is multiplied by the number of considered DU-RBG-IDs. The maximum DCI payload size can be enlarged, and/or a DCI format, e.g. based on 2_5, may be provided including one or more fields or indexes indicating one or more DU-RBG-IDs. FIG. 6 gives an example of such enhancement of availability indication to include frequency domain soft resource RBGs by using DU-RBG-ID (the greyed column in the figure), where the legacy availabilityCombinations is provided for each DU-RBG of a serving cell.

[0096] FIG. 6 specifically shows an example of enhanced availability indication to include frequency domain resource RBGs by providing a availabilityCombinations to each DU-RBG of a serving cell. The DU-RBG-ID could be provided in addition to Cell-ID via RRC signaling, e.g. when configuring ResourceAvailability and/or availabilityCombinations.

[0097] In another variant, the DU-RBG-ID can be included in a modified availability combination table (availabilityCombinations). In this case, the DCI location information may be only associated to the cell-ID. FIG. 7 gives an example of the modification of the availability combination table (availabilityCombinations) to include frequency domain soft resource RBGs using DU-RBG-ID. The example assumes that the first DU-RBG (DU-RBG-ID=0) is provided with an availabilityCombinations of 3 availability combinations; the second DU-RBG (DU-RBG-ID=1) is proved with an availabilityCombinations of 2 availability combinations; the third DU-RBG (DU-RBG-ID=2) is provided with an availabilityCombinations of 1 availability combination or more. The greyed column in the figure shows the relation to the previous availabilityCombinationId.

[0098] Different to the example in FIG. 6, time and frequency domain references (e.g. position in DCI and RBG-ID) about resources does not need to be explicitly provided in a DCI as information about RBG-IDs is included in the table, thus potentially requiring less payload in a new or modified DCI 2_5. Also, since the principle structure of a new DCI that also carries RBG-ID information can rely on an DCI 2_5 structure (e.g., such that only the size of a DCI 2_5 could be adjusted). This may significantly reduce specification and implementation complexity. FIG. 7 specifically shows an example of enhancement on the availability combination table (availabilityCombinations) to include DU-RBG-ID for the frequency domain resource availability indication. The greyed column in the figure shows the relation to the legacy availabilityCombinationId (which is not a part of the enhanced availabilityCombinations).

[0099] In general, the availabilitycombinations and/or the combination table may be configured to the child IAB, e.g. with higher layer signaling. The DCI may point to an entry to the table (e.g., with one index or parameter), or may point to a table of a set of tables, and to an entry of the pointed table (e.g., using two indices or parameters, each for one pointing). In the first case, the table may contain entries pertaining to different DU-RBGs or DU-RBG-ID (and/or different frequency intervals); in the latter case, each table may pertain to one frequency interval, DU-RBG or ID, and at least some tables of the set may pertain to different frequency intervals, DU-RBGs or IDs

[0100] Alternatively, or additionally, using DU-RBG-group ID may be considered. In this variant, the frequency domain availability indication may be provided for a configurable group or groups of IAB-DU RBGs. Besides the availabilityCombinationId, each set of resourceAvailability may have an associated group identifier, referred to as DU-RBG-group-ID. In this case, each availability combination can be provided to a group of IAB-DU RBGs; the DU-RBG-IDs belonging to a specific DU-RBG-group-ID need only be provided at initialization (e.g., configuration), more infrequently or if the DU-RBG-IDs belonging to a specific DU-RBG-group-ID changes. This can reduce overhead in dynamic signaling of availability information, such as in DCI transmissions. In one variant, the DU-RBG-group-ID may be provided in addition to the cell-ID in the DCI. Thus, previous availabilityCombinations may be reused. In this way of provisioning availabilityCombinations, the location information is associated to both the cell-ID and DU-RBG-group-ID. With the group-ID, RBG-IDs may have not to be addressed individually, lowering potential signaling overhead. FIG. 8 gives an example of such enhancement of the availability indication to include frequency domain soft resource RBGs by using DU-RBG-group-ID. The example assumes that the first DU-RBG group (DU-RBU-group-ID=0) contains two DU-RBGs (DU-RBG-ID=0 and 1); and the second DU-RBG group (DU-RBU-group-ID=1) contains three DU-RBGs (DU-RBG-ID=2,3,4). availabilityCombinations as described herein may be provided for each DU-RBG group of a serving cell. FIG. 8 specifically shows an example for frequency domain resource availability indication by associating a availabilityCombinations to configurable groups of IAB-DU RBGs. The DU-RBG-group-ID can be provided in addition to the Cell-ID via the RRC signaling when configuring the availabilityCombinations and/or ResourceAvailability—

[0101] In another variant, the DU-RBG-group-ID may be included in a modified configuration of availabilityCombinations. Thereby, the DCI location information may be associated to the cell-ID (it may be modified as described with respect to FIG. 6, pointing to RBG-group-IDs instead of individual RBG-IDs. FIG. 9 gives an example of the modification of the availabilityCombinations to include frequency domain soft resource RBGs using DU-RBG-group-ID. The example assumes that the first DU-RBG group (DU-RBG-group-ID=0), consisting of two RBGs (DU-RBG-ID=0,1), is provided with an availabilityCombinations of 2 availability combinations; the second DU-RBG group (DU-RBG-group-ID=1), consisting of 3 RBGs (DU-RBG-ID=2,3,4) is provided with an availabilityCombinations of 1 or more availability combination. The greyed column in the figure shows the relation to the legacy availabilityCombinationId (and is not a part of the enhanced availabilityCombinations).

[0102] The mapping between DU-RBG-group-ID and DU-RBG-IDs can be provide in a separate information, in which case the third column (DU-RBG-ID) in FIG. 9 may be redundant and may be left out. In an alternative, the mapping information between availabilityCombinationId (according to FIG. 9) and DU-RBG-IDs can be provided as part of availabilityCombinations (according to FIG. 9), in which case the second column (DU-RBG-group-ID) may be redundant and may be left out. FIG. 9 specifically shows an example of enhancement of the availability combination table to include DU-RBG-group-ID. The greyed column in the figure shows the relation to the legacy availabilityCombinationId (and is not a part of the enhanced availabilityCombinations).

[0103] Alternatively, or additionally, a frequency domain resource availability element may be considered, e.g. in a DCI message, which may be represented in a new DCI format. In one variant, a new DCI format can be used to indicate the availability for a group of IAB-DU RBGs with a corresponding frequency domain resource availability element, which can for example take values as:

[0104]

Value	Indication
0	No indication of availability for soft RBGs
1	DL soft RBGs are indicated available
	No indication of availability for UL and Flexible soft
	RBGs
2	UL soft RBGs are indicated available
	No indication of availability for DL and Flexible soft
	RBGs
3	DL and UL soft RBGs are indicated available
	No indication of availability for Flexible soft RBGs
4	Flexible soft RBGs are indicated available
	No indication of availability for DL and UL soft RBGs
5	DL and Flexible soft RBGs are indicated available
	No indication of availability for UL soft RBGs
6	UL and Flexible soft RBGs are indicated available
	No indication of availability for DL soft RBGs
7	DL, UL, and Flexible soft RBGs are indicated available

[0105] The frequency domain resource availability element may be implemented as and/or represented by a bit field in the DCI, e.g. having a size of 3 bits. For each of the DU-RBG-IDs or DU-RBG-group-IDs (if used), and/or frequency intervals or groups of intervals, there may be provided its own element in the DCI.

[0106] In this case, resource availability may be configured for multiple consecutive slots, e.g. indicated by only one element. The starting slot and the ending slot between which the DCI is applied may be provided via the RRC signaling and/or Layer-1 signaling, e.g. together with the cell ID and the DU-RBG-ID or the DU-RBG-group-ID. In general, providing some information or parameter or value may comprise indicating the value.

[0107] FIG. 10 shows an example in which the frequency domain resource availability element is provided to configurable groups of IAB-DU RBGs over multiple slots. The example assumes the first DU-RBG group (DU-RBG-group-ID=0) contains 3 DU-RBGs (DU-RBG-ID=0,1,2); the second DU-RBG group (DU-RBG-group-ID=1) contains 2 DU-RBGs (DU-RBG-ID=3,4); and the third DU-RBG group (DU-RBG-group-ID=2) contains 1 DU-RBG (DU-RBG-ID=5). The reference to slots may be in order and/or according to a number or set of numbers of slots and/or an indicated range, to generally provide a mapping to the slots.

[0108] FIG. 10 specifically shows an example of a mapping between the frequency domain resource availability element for a group of IAB-DU RBGs over one N time slots. In another variant, the information of how many slots (and/or for which slots) a certain frequency domain resource availability element is valid may be preconfigured by, e.g., including/connecting it to a certain DU-RBG-group-ID, e.g. with the configuration. In this case, the signaling of a DU-RBG-group-ID may imply a time validity; thus, the starting slot and the ending slot of time validity do not need to be explicitly provided in the DCI. In another variant, the frequency domain resource availability indication or element may take less than 8 values, e.g. to reduce the signaling overhead. Which states of H/S/NA are available for such an element (e.g., having only 4 values, e.g. to save a bit) may be configured or configurable, and/or predefined.

[0109] In some variants, a preemption-like indication may be considered. DCI format 2_1 is a typical pre-emption indication, which is used to indicate to a certain device that some of its resources have been pre-empted and are used for other purposes. It contains a bitmap representing OFDM symbols in time and full/half bandwidth part. In the bitmap, 1 denotes the pre-empted resources. Similar structure can be used to indicate to the IAB-MT that certain frequency/time-domain resources (e.g., RBGs associated to one slot) are “pre-empted” by the IAB-DU Soft resources. In another variant, the pre-emption-like indication can be used to indicate to the IAB-DU that certain frequency/time domain resource are “pre-empted” by the IAB-MT.

[0110] The described dynamic approaches (e.g., using a DCI) may be considered to refer and/or point and/or index a configuration (e.g., of the combinations), which may be provided semi-statically. The DCI may in general be provided by a IAB parent node and/or DU function; the configuration may be provided by the IAB parent node and/or an IAB donor and/or DU or CU function.

[0111] Alternatively, or additionally, semi-static approaches may be considered, which may independent of dynamic signaling using DCI. A centralized network function unit (e.g., IAB-donor-CU) may be responsible for semi-static resource configuration of the IAB DU resource in terms of H/S/NA. The centralized network function unit may have a good overview of the interference condition of the network, as it is responsible for interference measurement configuration and reporting. Therefore, the centralized network function unit may provide availability information to the IAB node, or the parent node based on the measured interference condition of the network. The centralized network function may, for example, (optionally) determine the availability of soft resource RBGs, e.g. based on measured interference condition and/or channel estimates, the traffic condition, etc. In one example, the frequency resource might not be available (as configured by the centralized function CU) to certain IAB-DU or IAB-MT in certain direction like (DL/UL). The centralized function may (optionally) send the availability information to the IAB-node, e.g. via the F1 interface; and/or (optionally) send the availability information to the IAB parent node via for example the F1 interface. A IAB child not may (optionally) receive the availability information from the IAB parent node via for example the F1 interface

[0112] It may be considered that the soft frequency domain resource/s is configured per IAB-MT and IAB-DU pair, e.g. in terms of configurable groups of RBGs. Accordingly, the frequency domain availability indication may be provided per IAB-MT and IAB-DU pair in terms of configurable groups of RBGs.

[0113] In one variant, the soft frequency domain DU resource may by default Available. In another variant, the soft frequency domain DU resource may by default Not Available. In another variant, the S-IA (Soft-indicated-available) frequency domain resource may imply availability of the corresponding time domain resource. It may be considered that the maximum number of the elements in a set of resourceAvailability can be more than 256, allowing good flexibility for frequency intervals, e.g. associated to DU-RBG-ID or DU-RBG-Group-IDs.

[0114] In general, each frequency interval for which resource availability, e.g. soft availability, may be configured or indicated, there may be associated an address or ID, which may be configured or configurable, or predefined. A frequency interval may correspond to a (P)RB, or (P)RB group (RBG), or integer multiples thereof, or a BWP, or a part thereof. It some cases, different frequency intervals (at least such associated to the same cell or IAB node) may be non-overlapping.

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

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

[0117] An IAB node may in general be adapted for providing radio access to one or more terminals or UEs, and to communicate via a backhaul link with another IAB node, e.g. by providing the backhaul link, or by using it as a child node. A donor node may be considered a form of IAB node. From an IAB node's of view, UL communication may be communication via a backhaul link provided by a parent node, which may comprise UL and DL components itself, from and to the IAB node. DL communication may be communication via a backhaul link provided by the IAB node itself, or an access link provided by the IAB node, The IAB node may be a radio node, which may comprise radio circuitry and/or processing circuitry and/or antenna circuitry and/or an antenna arrangement and/or other circuitry, as described for radio nodes in general. In particular, it may comprise circuitry corresponding to terminal functionality (also referred to as MT), and second circuitry corresponding to IAB control functionality (also referred to as DU). An IAB node that is a donor node may in some variants comprise circuitry corresponding to higher layer functionality, which may be also referred to as CU functionality. An IAB node may be adapted to carry out and/or control any of the methods described herein.

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

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

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

[0121] A system comprising one or more radio nodes as described herein, in particular a network node and a user equipment, is described. The system may be a wireless communication system, and/or provide and/or represent a radio access network.

[0122] Moreover, there may be generally considered a method of operating an information system, the method comprising providing information. Alternatively, or additionally, an information system adapted for providing information may be considered. Providing information may comprise providing information for, and/or to, a target system, which may comprise and/or be implemented as radio access network and/or a radio node, in particular a network node or user equipment or terminal. Providing information may comprise transferring and/or streaming and/or sending and/or passing on the information, and/or offering the information for such and/or for download, and/or triggering such providing, e.g. by triggering a different system or node to stream and/or transfer and/or send and/or pass on the information. The information system may comprise, and/or be connected or connectable to, a target, for example via one or more intermediate systems, e.g. a core network and/or internet and/or private or local network. Information may be provided utilising and/or via such intermediate system/s. Providing information may be for radio transmission and/or for transmission via an air interface and/or utilising a RAN or radio node as described herein. Connecting the information system to a target, and/or providing information, may be based on a target indication, and/or adaptive to a target indication. A target indication may indicate the target, and/or one or more parameters of transmission pertaining to the target and/or the paths or connections over which the information is provided to the target. Such parameter/s may in particular pertain to the air 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 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 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, e.g. a host computer or host computer arrangement and/or server or server arrangement. In some variants, an interaction server (e.g., web server) of the information system may provide a user interface, and based on user input may trigger transmitting and/or streaming information provision to the user (and/or the target) from another server, which may be connected or connectable to the interaction server and/or be part of the information system or be connected or connectable thereto. The information may be any kind of data, in particular data intended for a user of for use at a terminal, e.g. video data and/or audio data and/or location data and/or interactive data and/or game-related data and/or environmental data and/or technical data and/or traffic data and/or vehicular data and/or circumstantial data and/or operational data. The information provided by the information system may be mapped to, and/or mappable to, and/or be intended for mapping to, communication or data signaling and/or one or more data channels as described herein (which may be signaling or channel/s of an air interface and/or used within a RAN and/or for radio transmission). It may be considered that the information is formatted based on the target indication and/or target, e.g. regarding data amount and/or data rate and/or data structure and/or timing, which in particular may be pertaining to a mapping to communication or data signaling and/or a data channels. Mapping information to data signaling and/or data channel/s may be considered to refer to using the signaling/channel/s to carry the data, e.g. on higher layers of communication, with the signaling/channel/s underlying the transmission. A target indication generally may comprise different components, which may have different sources, and/or which may indicate different characteristics of the target and/or communication path/s thereto. A format of information may be specifically selected, e.g. from a set of different formats, for information to be transmitted on an air interface and/or by a RAN as described herein. This may be particularly pertinent since an air interface may be limited in terms of capacity and/or of predictability, and/or potentially be cost sensitive. The format may be selected to be adapted to the transmission indication, which may in particular indicate that a RAN or radio node as described herein is in the path (which may be the indicated and/or planned and/or expected path) of information between the target and the information system. A (communication) path of information may represent the interface/s (e.g., air and/or cable interfaces) and/or the intermediate system/s (if any), between the information system and/or the node providing or transferring the information, and the target, over which the information is, or is to be, passed on. A path may be (at least partly) undetermined when a target indication is provided, and/or the information is provided/transferred by the information system, e.g. if an internet is involved, which may comprise multiple, dynamically chosen paths. Information and/or a format used for information may be packet-based, and/or be mapped, and/or be mappable and/or be intended for mapping, to packets. Alternatively, or additionally, there may be considered a method for operating a target device comprising providing a target indicating to an information system. More alternatively, or additionally, a target device may be considered, the target device being adapted for providing a target indication to an information system. In another approach, there may be considered a target indication tool adapted for, and/or comprising an indication module for, providing a target indication to an information system. The target device may generally be a target as described above. A target indication tool may comprise, and/or be implemented as, software and/or application or app, and/or web interface or user interface, and/or may comprise one or more modules for implementing actions performed and/or controlled by the tool. The tool and/or target device may be adapted for, and/or the method may comprise, receiving a user input, based on which a target indicating may be determined and/or provided. Alternatively, or additionally, the tool and/or target device may be adapted for, and/or the method may comprise, receiving information and/or communication signaling 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 signaling carrying information. Presenting information may comprise processing received information, e.g. decoding and/or transforming, in particular between different formats, and/or for hardware used for presenting. Operating on information may be independent of 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 signaling may be expected and/or received based on the target indication. Presenting and/or operating on information may generally comprise one or more processing steps, in particular decoding and/or executing and/or interpreting and/or transforming information. Operating on information may generally comprise relaying and/or transmitting the information, e.g. on an air interface, which may include mapping the information onto signaling (such mapping may generally pertain to one or more layers, e.g. one or more layers of an air interface, e.g. RLC (Radio Link Control) layer and/or MAC layer and/or physical layer/s). The information may be imprinted (or mapped) on communication signaling based on the target indication, which may make it particularly suitable for use in a RAN (e.g., for a target device like a network node or in particular a UE or terminal). The tool may generally be adapted for use on a target device, like a UE or terminal. Generally, the tool may provide multiple 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 signaling, and/or carried on signaling, in a RAN, for example if the target device is a UE, or the tool for a UE. It should be noted that such provided information may be transferred to the information system via one or more additionally communication interfaces and/or paths and/or connections. The target indication may be a higher-layer indication and/or the information provided by the information system may be higher-layer information, e.g. application layer or user-layer, in particular above radio layers like transport layer and physical layer. The target indication may be mapped on physical layer radio signaling, e.g. related to or on the user-plane, and/or the information may be mapped on physical layer radio communication signaling, e.g. related to or on the user-plane (in particular, in reverse communication directions). The described approaches allow a target indication to be provided, facilitating information to be provided in a specific format particularly suitable and/or adapted to efficiently use an air interface. A user input may for example 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.

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

[0124] Signaling may generally comprise one or more symbols and/or signals and/or messages. A signal may comprise or represent one or more bits. An indication may represent signaling, and/or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and/or represented by a message. Signaling, in particular control signaling, may comprise a plurality of signals and/or messages, which may be transmitted on different carriers and/or be associated to different signaling processes, e.g. representing and/or pertaining to one or more such processes and/or corresponding information. An indication may comprise signaling, and/or a plurality of signals and/or messages and/or may be comprised therein, which may be transmitted on different carriers and/or be associated to different acknowledgement signaling processes, e.g. representing and/or pertaining to one or more such processes. Signaling associated to a channel may be transmitted such that represents signaling and/or information for that channel, and/or that the signaling is interpreted by the transmitter and/or receiver to belong to that channel. Such signaling may generally comply with transmission parameters and/or format/s for the channel.

[0125] Reference signaling may be signaling comprising one or more reference symbols and/or structures. Reference signaling 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 signaling are available for both transmitter and receiver of the signaling (e.g., due to being predefined and/or configured or configurable and/or being communicated). Different types of reference signaling may be considered, e.g. pertaining to uplink, downlink or sidelink, cell-specific (in particular, cell-wide, e.g., CRS) or device or user specific (addressed to a specific target or user equipment, e.g., CSI-RS), demodulation-related (e.g., DMRS) and/or signal strength related, e.g. power-related or energy-related or amplitude-related (e.g., SRS or pilot signaling) and/or phase-related, etc.

[0126] An antenna arrangement may comprise one or more antenna elements (radiating elements), which may be combined in antenna arrays. An antenna array or subarray may comprise one antenna element, or a plurality of antenna elements, which may be arranged e.g. two dimensionally (for example, a panel) or three dimensionally. It may be considered that each antenna array or subarray or element is separately controllable, respectively that different antenna arrays are controllable separately from each other. A single antenna element/radiator may be considered the smallest example of a subarray. Examples of antenna arrays comprise one or more 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 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 by combining one or more independently or separately controllable antenna elements or subarrays. The beams may be provided by analog beamforming, or in some variants by digital beamforming, or by hybrid beamforming combing analog and digital beamforming. The informing radio nodes may be configured with the manner of beam transmission, e.g. by transmitting a corresponding indicator or indication, for example as beam identify indication. However, there may be considered cases in which the informing radio node/s are not configured with such information, and/or operate transparently, not knowing the way of beamforming used. An antenna arrangement may be considered separately controllable in regard to the phase and/or amplitude/power and/or gain of a signal feed to it for transmission, and/or separately controllable antenna arrangements may comprise an independent or separate transmit and/or receive unit and/or ADC (Analog-Digital-Converter, alternatively an ADC chain) or DCA (Digital-to-Analog Converter, alternatively a DCA chain) to convert digital control information into an analog antenna feed for the whole antenna arrangement (the ADC/DCA may be considered part of, and/or connected or connectable to, antenna circuitry) or vice versa. A scenario in which an ADC or DCA is controlled directly for beamforming may be considered an analog beamforming scenario; such controlling may be performed after encoding/decoding and or after modulation symbols have been mapped to resource elements. This may be on the level of antenna arrangements using the same ADC/DCA, e.g. one antenna element or a group of antenna elements associated to the same ADC/DCA. Digital beamforming may correspond to a scenario in which processing for beamforming is provided before feeding signaling 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 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.

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

[0128] 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 and/or attrition or other effects influencing a beam or the signaling 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 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 signaling carried by the beam, e.g. reference signaling and/or a specific channel, e.g. a data channel or control channel. Signal strength may be represented by received signal strength, and/or relative signal strength, e.g. in comparison to a reference signal (strength).

[0129] Uplink or sidelink signaling may be OFDMA (Orthogonal Frequency Division Multiple Access) or SC-FDMA (Single Carrier Frequency Division Multiple Access) signaling. Downlink signaling may in particular be OFDMA signaling. However, signaling is not limited thereto (Filter-Bank based signaling may be considered one alternative).

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

[0131] A radio node may be a network node, or a user equipment or terminal. A network node may be any radio node of a wireless communication network, e.g. a base station and/or gNodeB (gNB) and/or eNodeB (eNB) and/or relay node or IAB 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 as described herein.

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

[0133] A radio node may generally comprise processing circuitry and/or radio circuitry. A radio node, in particular a network node, may in some cases comprise cable circuitry and/or communication circuitry, with which it may be connected or connectable to another radio node and/or a core network.

[0134] Circuitry may comprise integrated circuitry. Processing circuitry may comprise one or more processors and/or controllers (e.g., microcontrollers), and/or ASICs (Application Specific Integrated Circuitry) and/or FPGAs (Field Programmable Gate Array), or similar. It may be considered that processing circuitry comprises, and/or is (operatively) connected or connectable to one or more memories or memory arrangements. A memory arrangement may comprise one or more memories. A memory may be adapted to store digital information. Examples for memories comprise volatile and non-volatile memory, and/or Random Access Memory (RAM), and/or Read-Only-Memory (ROM), and/or magnetic and/or optical memory, and/or flash memory, and/or hard disk memory, and/or EPROM or EEPROM (Erasable Programmable ROM or Electrically Erasable Programmable ROM).

[0135] Radio circuitry may comprise one or more transmitters and/or receivers and/or transceivers (a transceiver may operate or be operable as transmitter and receiver, and/or may comprise joint or separated circuitry for receiving and transmitting, e.g. in one package or housing), and/or may comprise one or more amplifiers and/or oscillators and/or filters, and/or may comprise, and/or be connected or connectable to antenna circuitry and/or one or more antennas and/or antenna arrays. An antenna array may comprise one or more antennas, which may be arranged in a dimensional array, e.g. 2D or 3D array, and/or antenna panels. A remote radio head (RRH) may be considered as an example of an antenna array. However, in some variants, a RRH may be also be implemented as a network node, depending on the kind of circuitry and/or functionality implemented therein.

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

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

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

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

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

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

[0142] Signaling 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 signaling) target. A process of signaling may comprise transmitting the signaling. Transmitting signaling, in particular control signaling or communication signaling, e.g. comprising or representing acknowledgement signaling and/or resource requesting information, may comprise encoding and/or modulating. Encoding and/or modulating may comprise error detection coding and/or forward error correction encoding and/or scrambling. Receiving control signaling may comprise corresponding decoding and/or demodulation. Error detection coding may comprise, and/or be based on, parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check). Forward error correction coding may comprise and/or be based on for example turbo coding and/or Reed-Muller coding, and/or polar coding and/or LDPC coding (Low Density Parity Check). The type of coding used may be based on the channel (e.g., physical channel) the coded signal is associated to. A code rate may represent the ratio of the number of information bits before encoding to the number of encoded bits after encoding, considering that encoding adds coding bits for error detection coding and forward error correction. Coded bits may refer to information bits (also called systematic bits) plus coding bits.

[0143] Communication signaling may comprise, and/or represent, and/or be implemented as, data signaling, and/or user plane signaling. Communication signaling may be associated to a data channel, e.g. a physical downlink channel or physical uplink channel or physical sidelink channel, in particular a PDSCH (Physical Downlink Shared Channel) or PSSCH (Physical Sidelink Shared Channel). Generally, a data channel may be a shared channel or a dedicated channel. Data signaling may be signaling associated to and/or on a data channel.

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

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

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

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

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

[0149] 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 configuration data and/or data pertaining to configuration data, e.g., from another node like a network node, which may be a higher-level node of the network, and/or transmitting received configuration data to the radio node. Accordingly, determining a configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities, which may be able to communicate via a suitable interface, e.g., an X2 interface in the case of LTE or a corresponding interface for NR. Configuring a terminal may comprise scheduling downlink and/or uplink transmissions for the terminal, e.g. downlink data and/or downlink control signaling and/or DCI and/or uplink control or data or communication signaling, in particular acknowledgement signaling, and/or configuring resources and/or a resource pool therefor.

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

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

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

[0153] Examples of a resource structure in frequency domain comprise a bandwidth or band, or a bandwidth part. A bandwidth part may be a part of a bandwidth available for a radio node for communicating, e.g. due to circuitry and/or configuration and/or regulations and/or a standard. A bandwidth part may be configured or configurable to a radio node. In some variants, a bandwidth part may be the part of a bandwidth used for communicating, e.g. transmitting and/or receiving, by a radio node. The bandwidth part may be smaller than the bandwidth (which may be a device bandwidth defined by the circuitry/configuration of a device, and/or a system bandwidth, e.g. available for a RAN). It may be considered that a bandwidth part comprises one or more resource blocks 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.

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

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

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

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

[0158] A channel may generally be a logical, transport or physical channel. A channel may comprise and/or be arranged on one or more carriers, in particular a plurality of subcarriers. A channel carrying and/or for carrying control signaling/control information may be considered a control channel, in particular if it is a physical layer channel and/or if it carries control plane information. Analogously, a channel carrying and/or for carrying data signaling/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 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.

[0159] In general, a symbol may represent and/or be associated to a symbol time length, which may be dependent on the carrier and/or subcarrier spacing and/or numerology of the associated carrier. Accordingly, a symbol may be considered to indicate a time interval having a symbol time length in relation to frequency domain. A symbol time length may be dependent on a carrier frequency and/or bandwidth and/or numerology and/or subcarrier spacing of, or associated to, a symbol. Accordingly, different symbols may have different symbol time lengths. In particular, numerologies with different subcarrier spacings may have different symbol time length. Generally, a symbol time length may be based on, and/or include, a guard time interval or cyclic extension, e.g. prefix or postfix.

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

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

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

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

[0164] 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 signaling or separate configuration, e.g. separate RRC signaling and/or downlink control information signaling. The transmission/s scheduled may represent signaling to be transmitted by the device for which it is scheduled, or signaling 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 signaling may be considered physical layer signaling, in contrast to higher layer signaling like MAC (Medium Access Control) signaling or RRC layer signaling. The higher the layer of signaling is, the less frequent/the more time/resource consuming it may be considered, at least partially due to the information contained in such signaling having to be passed on through several layers, each layer requiring processing and handling.

[0165] A scheduled transmission, and/or transmission timing structure like a mini-slot or slot, may pertain to a specific channel, in particular a physical uplink shared channel, a physical uplink control channel, or a physical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and/or may pertain to a specific cell and/or carrier aggregation. A 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 physical channel, for example a physical uplink shared channel or physical downlink shared channel. For such channels, semi-persistent configuring may be particularly suitable.

[0166] 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 indicate and/or schedule resources, in particular semi-persistently and/or semi-statically.

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

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

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

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

[0171] A transmission timing structure may comprise a plurality of symbols, and/or define an interval comprising several symbols (respectively their associated time intervals). In the context of this disclosure, it should be noted that a reference to a symbol for ease of reference may be interpreted to refer to the time domain projection or time interval or time component or duration or length in time of the symbol, unless it is clear from the context that the frequency domain component also has to be considered. Examples of transmission timing structures include slot, subframe, mini-slot (which also may be considered a substructure of a slot), slot aggregation (which may comprise a plurality of slots and may be considered a superstructure of a slot), respectively their time domain component. A transmission timing structure may generally comprise a plurality of symbols defining the time domain extension (e.g., interval or length or duration) of the transmission timing structure, and arranged neighboring to each other in a numbered sequence. A timing structure (which may also be considered or implemented as synchronisation structure) may be defined by a succession of such transmission timing structures, which may for example define a timing grid with symbols representing the smallest grid structures. A transmission timing structure, and/or a border symbol or a scheduled transmission may be determined or scheduled in relation to such a timing grid. A transmission timing structure of reception may be the transmission timing structure in which the scheduling control signaling is received, e.g. in relation to the timing grid. A transmission timing structure may in particular be a slot or subframe or in some cases, a mini-slot.

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

[0173] Signaling utilising, and/or on and/or associated to, resources or a resource structure may be signaling covering the resources or structure, signaling on the associated frequency/ies and/or in the associated time interval/s. It may be considered that a signaling resource structure comprises and/or encompasses one or more substructures, which may be associated to one or more different channels and/or types of signaling 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 generally be continuous in time and/or frequency, within the associated intervals. It may be considered that a substructure, in particular a feedback resource structure, represents a rectangle filled with one or more resource elements in time/frequency space. However, in some cases, a resource structure or substructure, in particular a frequency resource range, may represent a non-continuous pattern of resources in one or more domains, e.g. time and/or frequency. The resource elements of a substructure may be scheduled for associated signaling.

[0174] It should generally be noted that the number of bits or a bit rate associated to specific signaling that can be carried on a resource element may be based on a modulation and coding scheme (MCS). Thus, bits or a bit rate may be seen as a form of resources representing a resource structure or range in frequency and/or time, e.g. depending on MCS. The MCS may be configured or configurable, e.g. by control signaling, e.g. DCI or MAC (Medium Access Control) or RRC (Radio Resource Control) signaling.

[0175] A resource structure in frequency domain (which may be referred to as frequency interval and/or range) may be represented by a subcarrier grouping. A subcarrier grouping may comprise one or more subcarriers, each of which may represent a specific frequency interval, and/or bandwidth. The bandwidth of a subcarrier, the length of the interval in frequency domain, may be determined by the subcarrier spacing and/or numerology. The subcarriers may be arranged such that each subcarrier neighbours at least one other subcarrier of the grouping in frequency space (for grouping sizes larger than 1). The subcarriers of a grouping may be associated to the same carrier, e.g. configurably or configured of predefined. A physical resource block may be considered representative of a grouping (in frequency domain). A subcarrier grouping may be considered to be associated to a specific channel and/or type of signaling, it transmission for such channel or signaling is scheduled and/or transmitted and/or intended and/or configured for at least one, or a plurality, or all subcarriers in the grouping. Such association may be time-dependent, e.g. configured or configurable or predefined, and/or dynamic or semi-static. The association may be different for different devices, e.g. configured or configurable or predefined, and/or dynamic or semi-static. Patterns of subcarrier groupings may be considered, which may comprise one or more subcarrier groupings (which may be associated to same or different signalings/channels), and/or one or more groupings without associated signaling (e.g., as seen from a specific device). An example of a pattern is a comb, for which between pairs of groupings associated to the same signaling/channel there are arranged one or more groupings associated to one or more different channels and/or signaling types, and/or one or more groupings without associated channel/signaling).

[0176] In the context of this disclosure, there may be distinguished between dynamically scheduled or aperiodic transmission and/or configuration, and semi-static or semi-persistent or periodic transmission and/or configuration. The term “dynamic” or similar terms may generally pertain to configuration/transmission valid and/or scheduled and/or configured for (relatively) short timescales and/or a (e.g., predefined and/or configured and/or limited and/or definite) number of occurrences and/or transmission timing structures, e.g. one or more transmission timing structures like slots or slot aggregations, and/or for one or more (e.g., specific number) of transmission/occurrences. Dynamic configuration may be based on low-level signaling, e.g. control signaling 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 configured with, higher-layer signaling, in particular RCL layer signaling and/or RRC signaling and/or MAC signaling.

[0177] Example types of signaling comprise signaling of a specific communication direction, in particular, uplink signaling, downlink signaling, sidelink signaling, as well as reference signaling (e.g., SRS or CRS or CSI-RS), communication signaling, control signaling, and/or signaling associated to a specific channel like PUSCH, PDSCH, PUCCH, PDCCH, PSCCH, PSSCH, etc.).

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

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

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

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

[0182] Some useful abbreviations comprise

[0183]

	Abbreviation	Explanation
	BAP	Backhaul adaptation protocol
	BH	Backhaul
	CU	Central Unit
	DAG	Directed Acyclic Graph
	DL	Downlink
	DL-H	Downlink-Hard
	DL-S	Downlink-Soft
	DU	Distributed Unit
	F1	Interface between a gNB-CU and a gNB-DU
	FDM	Frequency Division Multiplexing
	F-H	Flexible-Hard
	FP	Frequency part
	F-S	Flexible-Soft
	gNB	Base station with NR air interface for
		communication with UEs
	IAB	Integrated Access and Backhaul
	MAC	Medium access control
	MCG	Master cell group
	MT	Mobile Termination
	NA	Not-Available
	NG	Interface between an gNB and 5GC
	NR	New Radio
	PDCP	Packet Data Convergence Protocol
	RB	Resource block
	RLC	Radio Link Control
	RRC	Radio Resource Control
	Rx or RX	Receive
	SDM	Space Division Multiplexing
	ST	Spanning Tree
	TDD	Time Division Duplex
	TDM	Time Division Multiplexing
	Tx or TX	Transmit
	UE	User Equipment
	UL	Uplink
	UL-H	Uplink-Hard
	UL-S	Uplink-Soft
	ACK/NACK	Acknowledgment/Negative Acknowledgement
	ARQ	Automatic Repeat reQuest
	BER	Bit Error Rate
	BLER	Block Error Rate
	BPSK	Binary Phase Shift Keying
	BWP	BandWidth Part
	CAZAC	Constant Amplitude Zero Cross Correlation
	CB	Code Block
	CBG	Code Block Group
	CDM	Code Division Multiplex
	CM	Cubic Metric
	CORESET	Control Resource Set
	CQI	Channel Quality Information
	CRC	Cyclic Redundancy Check
	CRS	Common reference signal
	CSI	Channel State Information
	CSI-RS	Channel state information reference signal/ing
	DAI	Downlink Assignment Indicator
	DCI	Downlink Control Information
	DFT	Discrete Fourier Transform
	DFTS-FDM	DFT-spread-FDM
	DM(-)RS	Demodulation reference signal(ing)
	eMBB	enhanced Mobile BroadBand
	FDD	Frequency Division Duplex
	FDE	Frequency Domain Equalisation
	FDF	Frequency Domain Filtering
	FDM	Frequency Division Multiplex
	HARQ	Hybrid Automatic Repeat Request
	IAB	Integrated Access and Backhaul
	IFFT	Inverse Fast Fourier Transform
	IR	Impulse Response
	ISI	Inter Symbol Interference
	MBB	Mobile Broadband
	MCS	Modulation and Coding Scheme
	MIMO	Multiple-input-multiple-output
	MRC	Maximum-ratio combining
	MRT	Maximum-ratio transmission
	MU-MIMO	Multiuser multiple-input-multiple-output
	OFDM/A	Orthogonal Frequency Division
		Multiplex/Multiple Access
	PAPR	Peak to Average Power Ratio
	PDCCH	Physical Downlink Control Channel
	PDSCH	Physical Downlink Shared Channel
	PRACH	Physical Random Access CHannel
	PRB	Physical Resource Block
	PUCCH	Physical Uplink Control Channel
	PUSCH	Physical Uplink Shared Channel
	(P)SCCH	(Physical) Sidelink Control Channel
	PSS	Primary Synchronisation Signal(ing)
	(P)SSCH	(Physical) Sidelink Shared Channel
	QAM	Quadrature Amplitude Modulation
	OCC	Orthogonal Cover Code
	QPSK	Quadrature Phase Shift Keying
	PSD	Power Spectral Density
	RAN	Radio Access Network
	RAT	Radio Access Technology
	RB	Resource Block
	RNTI	Radio Network Temporary Identifier
	RRC	Radio Resource Control
	RX	Receiver, Reception, Reception-related/side
	SA	Scheduling Assignment
	SC-FDE	Single Carrier Frequency Domain Equalisation
	SC-FDM/A	Single Carrier Frequency Division
		Multiplex/Multiple Access
	SCI	Sidelink Control Information
	SINR	Signal-to-interference-plus-noise ratio
	SIR	Signal-to-interference ratio
	SNR	Signal-to-noise-ratio
	SR	Scheduling Request
	SRS	Sounding Reference Signal(ing)
	SSS	Secondary Synchronisation Signal(ing)
	SVD	Singular-value decomposition
	TB	Transport Block
	TDD	Time Division Duplex
	TDM	Time Division Multiplex
	TX	Transmitter, Transmission,
		Transmission-related/side
	UCI	Uplink Control Information
	UE	User Equipment
	URLLC	Ultra Low Latency High Reliability
		Communication
	VL-MIMO	Very-large multiple-input-multiple-output
	ZF	Zero Forcing
	ZP	Zero-Power, e.g. muted CSI-RS symbol

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