Method and apparatus for resource allocation

By receiving resource configuration information from the parent node in the wireless communication system and flexibly allocating resource types, the problem of resource allocation of multi-hop relay nodes is solved, resource utilization efficiency and interference management are improved, and the needs of different duplex scenarios are adapted.

CN112771953BActive Publication Date: 2024-12-06NOKIA NETWORKS OY
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN201880098040.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-09-27
Publication Date
2024-12-06
Estimated Expiration
2038-09-27

AI Technical Summary

Technical Problem

In the integrated access and backhaul (IAB) architecture, it is difficult to effectively configure and control resource allocation between multi-hop relay nodes, resulting in low resource utilization efficiency and difficulty in interference management.

Method used

Flexible resource allocation and scheduling is achieved by receiving resource configuration information from the parent node or donor node, determining and allocating appropriate resource types for multiple links, including uplink and downlink access links, as well as uplink and downlink backhaul links, enabling flexible resource allocation and scheduling , ensure the scheduling and non-scheduling of resources between different links.

Benefits of technology

It improves resource utilization efficiency, reduces interference, supports multi-hop relay and flexible capacity allocation, enhances link direction alignment capabilities, and adapts to the needs of different duplex scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112771953B_ABST
    Figure CN112771953B_ABST
Patent Text Reader

Abstract

A method includes receiving a resource configuration from at least one of a parent node and a donor node. The resource configuration includes information defining at least one resource type for a plurality of links for at least one time and at least one resource. The method includes: allocating at least one resource for the at least one time to at least one link of the plurality of links according to the resource configuration, the at least one link being with one or more child nodes.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to a method, apparatus and computer program and particularly, but not exclusively, to a method and apparatus to be used in a network using integrated access and backhaul. Background Art

[0002] A communication system can be viewed as a facility for enabling a communication session between two or more entities (e.g., communication devices, base stations / access points / relay nodes, and / or other nodes) by providing a carrier between the various entities involved in the communication path. A communication system can be provided, for example, with the aid of a communication network and one or more compatible communication devices.

[0003] In a wireless communication system, at least a portion of a communication session between at least two stations occurs over a wireless link.

[0004] The communication device is equipped with appropriate signal receiving and sending means to achieve communication, such as access to a communication network or direct communication with other communication devices. The communication device can access a carrier provided by a station or access point and send and / or receive communications on the carrier.

[0005] A communication system and associated equipment may operate according to a given standard or specification, which sets out what the various entities associated with the system are allowed to do and how it should be achieved. The communication protocols and / or parameters that should be used for the connection are usually defined. Summary of the invention

[0006] According to one aspect, a method is provided, the method comprising: receiving a resource configuration from at least one of a parent node and a donor node, the resource configuration comprising information defining at least one resource type for multiple links for at least one time and at least one resource; and allocating the at least one resource for the at least one time to at least one link among the multiple links according to the resource configuration, the at least one link being connected to one or more child nodes.

[0007] The method may include determining, based on the received resource configuration, one or more schedulable resources for at least one link of the plurality of links for the at least one time and the at least one resource, the allocating using the determined schedulable resources.

[0008] The at least one resource may include at least one physical resource block.

[0009] At least one resource type may be flexibly allocable to any one of the plurality of said links.

[0010] The multiple links may include one or more of the following: an uplink backhaul link with the first subnode, a downlink backhaul link with the first subnode, an uplink access link with the second subnode, and a downlink access link with the second subnode.

[0011] At least one resource type may define an access link with the second sub-node and a backhaul link with the first sub-node for at least one time and at least one resource.

[0012] One or more of the following resource types can be defined by the information in the resource configuration: a first type for a downlink sub-access link with the second sub-node and a downlink return link with the first sub-node; a second type for an uplink sub-access link with the second sub-node and an uplink return link with the first sub-node; and a third flexible type that can be used for any link with the first and second sub-nodes.

[0013] The method may include discarding allocation of at least one time and at least one resource to a link with the parent node or the donor node, and using the at least one time and at least one resource for at least one link with at least one child node.

[0014] In at least one resource type, at least one time and at least one resource may be made non-schedulable for a child link but schedulable for a link with the parent node or the donor node.

[0015] One or more of the following resource types can be defined by the information in the resource configuration: a first parent or donor node link type for a downlink return link with a parent or donor node; a second parent or donor node link type for an uplink return link with a parent or donor node; and a third flexible parent or donor node link type that can be used for any link with a parent or donor node and a child node.

[0016] The method may include: receiving further configuration information indicating that a third flexible parent or donor node link type resource is reserved for a link with the parent or donor node; determining that at least one time and at least one resource are not allocable to any of the plurality of sub-links; and allocating at least one time and at least one resource to a link with the parent or donor node.

[0017] The further configuration information includes one or more of higher layer configuration and downlink control information.

[0018] At least one parent or donor node link may be time multiplexed with respect to at least one child link.

[0019] The at least one parent or donor node link and the at least one child link may be at least one of frequency division multiplexed and space division multiplexed with respect to each other.

[0020] The method may include: receiving further configuration information indicating that a third flexible parent or donor node link type resource is reserved for a link with the parent or donor node; and determining that the at least one time and the at least one resource are allocatable to a downlink sublink if the at least one time and the at least one resource are reserved for an uplink parent or donor node return trip, or determining that the at least one time and the at least one resource are allocatable to an uplink sublink if the at least one time and the at least one resource are reserved for a downlink parent or donor node return trip.

[0021] The resource types may include one or more resource types for a plurality of links, wherein at least one link is with a parent or donor node and at least one link is with a child node.

[0022] At least one link with a parent or donor node is one of an uplink and a downlink, and at least one link with a child node is one of an uplink and a downlink.

[0023] One or more of the following resource types are defined by the information in the resource configuration: a fourth type for an uplink parent or donor node return, and one or more of a downlink sub-access link with a second child node and a downlink return link with a first child node; and a fifth type for an uplink parent or donor node return, and one or more of an uplink sub-access link with a second child node and an uplink return link with a first child node.

[0024] One or more of the following resource types can be defined by the information in the resource configuration: a sixth type for an uplink parent or donor node backhaul, and one or more of an uplink sub-access link with the second child node and an uplink backhaul link with the first child node; a seventh type for a downlink parent or donor node backhaul, and one or more of an uplink sub-access link with the second child node and an uplink backhaul link with the first child node; an eighth type for an uplink parent or donor node backhaul and any links with the first and second child nodes; and a ninth type for a downlink parent or donor node backhaul and any links with the first and second child nodes.

[0025] The at least one time may include a plurality of time slots, and the resource type is one or more of time slot specific and symbol specific.

[0026] The resource configuration may be provided by at least one of: a cell specific higher layer configuration; a dedicated higher layer configuration; and a group common physical downlink control channel.

[0027] According to another aspect, a method is provided, the method comprising causing a resource configuration to be sent from a parent node or a donor node, the resource configuration comprising information defining at least one resource type for a plurality of links for at least one time and at least one resource.

[0028] According to another aspect, a device is provided, comprising a module for performing the following operations: receiving a resource configuration from at least one of a parent node and a donor node, the resource configuration comprising information defining at least one resource type for multiple links for at least one time and at least one resource; and allocating the at least one resource for the at least one time to at least one link among the multiple links based on the resource configuration, the at least one link being with one or more child nodes.

[0029] The module may be configured to determine, based on the received resource configuration, one or more schedulable resources for at least one link of the plurality of links for at least one time and at least one resource, the allocating using the determined schedulable resources.

[0030] The at least one resource may include at least one physical resource block.

[0031] At least one resource type may be flexibly allocable to any one of the plurality of said links.

[0032] The multiple links may include one or more of an uplink backhaul link with the first subnode, a downlink backhaul link with the first subnode, an uplink access link with the second subnode, and a downlink access link with the second subnode.

[0033] At least one resource type may define an access link with the second sub-node and a backhaul link with the first sub-node for at least one time and at least one resource.

[0034] One or more of the following resource types can be defined by the information in the resource configuration: a first type for a downlink sub-access link with the second sub-node and a downlink return link with the first sub-node; a second type for an uplink sub-access link with the second sub-node and an uplink return link with the first sub-node; and a third flexible type that can be used for any link with the first and second sub-nodes.

[0035] The module may be used to discard allocation of at least one time and at least one resource to a link with the parent node or the donor node and use the at least one time and at least one resource for at least one link with at least one child node.

[0036] In at least one resource type, at least one time and at least one resource may be made non-schedulable for a child link but schedulable for a link with the parent node or the donor node.

[0037] One or more of the following resource types can be defined by the information in the resource configuration: a first parent or donor node link type for a downlink return link with a parent or donor node; a second parent or donor node link type for an uplink return link with a parent or donor node; and a third flexible parent or donor node link type that can be used for any link with a parent or donor node and a child node.

[0038] The module can be used to: receive further configuration information indicating that a third flexible parent or donor node link type resource is reserved for a link with the parent or donor node; determine that at least one time and at least one resource are not allocable to any of the multiple sub-links; and allocate at least one time and at least one resource to a link with the parent or donor node.

[0039] The further configuration information includes one or more of higher layer configuration and downlink control information.

[0040] At least one parent or donor node link may be time multiplexed with respect to at least one child link.

[0041] The at least one parent or donor node link and the at least one child link may be at least one of frequency division multiplexed and space division multiplexed with respect to each other.

[0042] The module can be used to: receive further configuration information indicating that a third flexible parent or donor node link type resource is reserved for a link with the parent or donor node; and if at least one time and at least one resource are reserved for an uplink parent or donor node return trip, determine that the at least one time and at least one resource are allocatable to a downlink sublink, or if at least one time and at least one resource are reserved for a downlink parent or donor node return trip, determine that the at least one time and at least one resource are allocatable to an uplink sublink.

[0043] The resource types may include one or more resource types for a plurality of links, wherein at least one link is with a parent or donor node and at least one link is with a child node.

[0044] At least one link with a parent or donor node is one of an uplink and a downlink, and at least one link with a child node is one of an uplink and a downlink.

[0045] One or more of the following resource types are defined by the information in the resource configuration: a fourth type for an uplink parent or donor node return, and one or more of a downlink sub-access link with a second child node and a downlink return link with a first child node; and a fifth type for an uplink parent or donor node return, and one or more of an uplink sub-access link with a second child node and an uplink return link with a first child node.

[0046] One or more of the following resource types can be defined by the information in the resource configuration: a sixth type for an uplink parent or donor node backhaul, and one or more of an uplink sub-access link with the second child node and an uplink backhaul link with the first child node; a seventh type for a downlink parent or donor node backhaul, and one or more of an uplink sub-access link with the second child node and an uplink backhaul link with the first child node; an eighth type for an uplink parent or donor node backhaul and any links with the first and second child nodes; and a ninth type for a downlink parent or donor node backhaul and any links with the first and second child nodes.

[0047] The at least one time may include a plurality of time slots, and the resource type is one or more of time slot specific and symbol specific.

[0048] The resource configuration may be provided by at least one of: a cell specific higher layer configuration; a dedicated higher layer configuration; and a group common physical downlink control channel.

[0049] According to another aspect, an apparatus is provided that includes means for causing a resource configuration to be sent from a parent or donor node, the resource configuration including information defining at least one resource type for a plurality of links for at least one time and at least one resource.

[0050] According to one aspect, a device is provided, comprising at least one processor and at least one memory, the at least one memory storing computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, enable the device to at least: receive a resource configuration from at least one of a parent node and a donor node, the resource configuration comprising information defining at least one resource type for a plurality of links for at least one time and at least one resource; and, based on the resource configuration, allocate the at least one resource for the at least one time to at least one link among the plurality of links, the at least one link being with one or more child nodes.

[0051] At least one memory and computer code may be configured to, together with at least one processor, cause the apparatus to at least: determine, based on the received resource configuration, one or more schedulable resources for at least one link among the plurality of links for at least one time and at least one resource, the allocation using the determined schedulable resources.

[0052] The at least one resource may include at least one physical resource block.

[0053] At least one resource type may be flexibly allocable to any one of the plurality of said links.

[0054] The multiple links may include one or more of an uplink backhaul link with the first subnode, a downlink backhaul link with the first subnode, an uplink access link with the second subnode, and a downlink access link with the second subnode.

[0055] At least one resource type may define an access link with the second sub-node and a backhaul link with the first sub-node for at least one time and at least one resource.

[0056] One or more of the following resource types can be defined by the information in the resource configuration: a first type for a downlink sub-access link with the second sub-node and a downlink return link with the first sub-node; a second type for an uplink sub-access link with the second sub-node and an uplink return link with the first sub-node; and a third flexible type that can be used for any link with the first and second sub-nodes.

[0057] At least one memory and computer code may be configured to, together with at least one processor, cause the apparatus to at least: discard allocation of at least one time and at least one resource to a link with the parent node or the donor node, and use the at least one time and at least one resource for at least one link with at least one child node.

[0058] In at least one resource type, at least one time and at least one resource may be made non-schedulable for a child link but schedulable for a link with the parent node or the donor node.

[0059] One or more of the following resource types can be defined by the information in the resource configuration: a first parent or donor node link type for a downlink return link with a parent or donor node; a second parent or donor node link type for an uplink return link with a parent or donor node; and a third flexible parent or donor node link type that can be used for any link with a parent or donor node and a child node.

[0060] At least one memory and computer code may be configured to, together with at least one processor, cause the apparatus to at least: receive further configuration information indicating that a third flexible parent or donor node link type resource is reserved for a link with a parent or donor node; determine that at least one time and at least one resource are not allocable to any of a plurality of said child links; and allocate at least one time and at least one resource to a link with said parent or donor node.

[0061] The further configuration information includes one or more of higher layer configuration and downlink control information.

[0062] At least one parent or donor node link may be time multiplexed with respect to at least one child link.

[0063] The at least one parent or donor node link and the at least one child link may be at least one of frequency division multiplexed and space division multiplexed with respect to each other.

[0064] At least one memory and computer code may be configured to, together with at least one processor, cause the apparatus to at least: receive further configuration information indicating that a third flexible parent or donor node link type resource is reserved for a link with the parent or donor node; and determine that at least one time and at least one resource are allocatable to a downlink sublink if at least one time and at least one resource are reserved for an uplink parent or donor node return trip, or determine that at least one time and at least one resource are allocatable to an uplink sublink if at least one time and at least one resource are reserved for a downlink parent or donor node return trip.

[0065] The resource types may include one or more resource types for a plurality of links, wherein at least one link is with the parent or donor node and at least one link is with a child node.

[0066] At least one link with a parent or donor node is one of an uplink and a downlink, and at least one link with a child node is one of an uplink and a downlink.

[0067] One or more of the following resource types are defined by the information in the resource configuration: a fourth type for an uplink parent or donor node return, and one or more of a downlink sub-access link with a second child node and a downlink return link with a first child node; and a fifth type for an uplink parent or donor node return, and one or more of an uplink sub-access link with a second child node and an uplink return link with a first child node.

[0068] One or more of the following resource types can be defined by the information in the resource configuration: a sixth type for an uplink parent or donor node backhaul, and one or more of an uplink sub-access link with the second child node and an uplink backhaul link with the first child node; a seventh type for a downlink parent or donor node backhaul, and one or more of an uplink sub-access link with the second child node and an uplink backhaul link with the first child node; an eighth type for an uplink parent or donor node backhaul and any links with the first and second child nodes; and a ninth type for a downlink parent or donor node backhaul and any links with the first and second child nodes.

[0069] The at least one time may include a plurality of time slots, and the resource type is one or more of time slot specific and symbol specific.

[0070] The resource configuration may be provided by at least one of: a cell specific higher layer configuration; a dedicated higher layer configuration; and a group common physical downlink control channel.

[0071] According to one aspect, a device is provided, comprising at least one processor and at least one memory, the at least one memory storing computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, enable the device to at least: cause a resource configuration to be sent from a parent node or a donor node, the resource configuration comprising information defining at least one resource type for multiple links for at least one time and at least one resource.

[0072] In another aspect, a computer program embodied on a non-transitory computer readable storage medium is provided, the computer program comprising program code for providing any of the above methods.

[0073] In another aspect, there is provided a computer program product for use with a computer, comprising software code portions for performing the steps of any of the aforementioned methods when said product is run.

[0074] A computer program may be provided, which comprises program code means suitable for executing the method. The computer program may be stored and / or embodied in other ways by means of a carrier medium.

[0075] Many different embodiments have been described above. It should be understood that further embodiments may be provided by combining any two or more of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] Some embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0077] Figure 1A schematic diagram showing an exemplary communication system including a plurality of base stations and a plurality of communication devices is shown;

[0078] Figure 2 A schematic diagram of an example mobile communication device is shown;

[0079] Figure 3 A schematic diagram of an example control device is shown;

[0080] Figure 4 An example backhaul link configuration is shown;

[0081] Figure 5 A first example of an integrated access and backhaul (IAB) architecture is shown;

[0082] Figure 6 A second example of an integrated access and backhaul architecture is shown;

[0083] Figure 7 shows the link between the IAB node and the communication device;

[0084] Figure 8 A first example of a combination of resource types for an IAB node is shown;

[0085] Fig. 9 shows a combination of resource types for a time division multiplexing scenario;

[0086] Fig.10 The resource type combination for frequency division / space division multiplexing scenario is shown;

[0087] Fig.11 shows the resource type combination for a full-duplex scenario;

[0088] Fig.12 A flow chart of a method according to some embodiments is shown. DETAILED DESCRIPTION

[0089] Before explaining the examples in detail, refer to Figure 1 to Figure 2 Some general principles of wireless communication systems and mobile communication devices are briefly explained to help understand the underlying technology of the described examples.

[0090] In such Figure 1In the wireless communication system 100 shown, wireless access is provided to mobile communication devices or user equipment (UE) 102, 104, 105 via at least one access point or similar wireless transmission and / or reception node or point. An access point or base station is called a Node B or generally referred to as a NB (e.g. eNB in ​​LTE and gNB in ​​5G NR). The base station is typically controlled by at least one appropriate controller device to enable its operation and management of mobile communication devices communicating with the base station. The controller device may be located in a radio access network (e.g. the wireless communication system 100) or a core network (CN) (not shown) and may be implemented as a central device or its functionality may be distributed over several devices. The controller device may be part of a base station and / or provided by a separate entity (such as a radio network controller). In Figure 1 In FIG. 1 , control means 108 and 109 are shown to control the respective macro level base stations 106 and 107. In some systems, the control means may additionally or alternatively be provided in a radio network controller.

[0091] exist Figure 1 In FIG. 1 , base stations 106 and 107 are shown as being connected to a wider communications network 113 via a gateway 112. A further gateway function may be provided to connect to another network.

[0092] Smaller base stations (or relay nodes or RNs) 116, 118 and 120 may also be connected to the network 113, for example, by separate gateway functions and / or via a controller of a macro level station. In the case of a multi-hop scenario, a relay node may be considered to contain certain communication equipment functions that facilitate backhaul connections with a donor gNB (DgNB) or a serving relay node. The communication equipment functions may be limited to those functions that handle radio links. This function may be referred to as a mobile terminal (MT) function. In addition, a relay node may be considered to contain gNB functions that facilitate access link connections with communication devices within the relay node cell and backhaul connections for relay nodes served by the current relay node (when the relay node operates as a serving relay node in a multi-hop scenario).

[0093] An example of a wireless communication system is an architecture standardized by the Third Generation Partnership Project (3GPP). One is generally referred to as the 5G NR (New Radio) standard. It should be understood that although some embodiments may be described in the context of the 5G standard, other embodiments may be used in the context of any other suitable standard.

[0094] 5G NR networks may be able to allow network deployment with relatively low manual and relatively high automated self-configuration. In some cases, coverage may be problematic. This may be a problem, for example, on higher frequency bands. In some embodiments, the system may be such that coverage extensions may be provided. In some embodiments, these coverage extensions may be provided with little or no network (re)planning. In some embodiments, this may be achieved in a relatively fast and / or cost-effective manner.

[0095] In current 5G proposals, the ability to implement wireless backhaul for access point sites that do not have a fixed (e.g., wired and / or fiber) connection to the network has been specified. Using radio connections for backhaul can eliminate the need to wire at least some or even all of the access point sites of the radio network (which can be very dense). This can reduce initial deployment costs.

[0096] It has been proposed that the same carrier be used for both the backhaul BH (also called the parent BH link) and the access link (also called the child link) that shares the same radio resources and radio transceiver. This is called self-backhaul. In 3GPP, this is sometimes referred to as integrated access and backhaul (IAB). The frequency bands that can be applied to IAB are those with sufficient capacity (i.e., sufficiently large carrier bandwidth). These carriers can be on the millimeter wave bands and are typically TDD (time division duplex) bands. When using the TDD band, IAB needs to consider the half-duplex constraint, i.e., it is not possible to send and receive at the same time. This is to avoid excessive interference between the transmitter and the receiver. There can be two half-duplex scenarios: 1) half-duplex with TDM between access and BH, and 2) half-duplex with FDM / SDM between access and backhaul. Depending on the capabilities of the IAB nodes, full-duplex methods can be supported alternatively or additionally.

[0097] IAB or self-backhaul may need to support multi-hop relay. In some embodiments, IAB may support the use of one or more relay nodes. Multi-hop relay may be a case where an IAB node can provide a wireless BH link to a next-hop IAB node. The serving node that provides the BH connection is called a parent node, where the node may be a donor node (with a wired network connection) or another IAB node. The served IAB node is called a child node.

[0098] Different options for the IAB architecture have been proposed.

[0099] In this regard, reference Figure 5, which shows a high-level architecture for L2 relay with a distributed base station (i.e. gNB) architecture. The donor node (IAB donor) hosts the centralized unit (CU) for all IAB nodes, i.e., it runs RRC (Radio Resource Control), higher L2 (PDCP-Packet Data Convergence Protocol) and control functions for the subtending IAB topology. The distributed unit (DU) resides at the IAB node hosting the lower L2 protocol layers (Radio Link Control (RLC), Media Access Control (MAC)) and physical (PHY) layers. With this architecture, radio resource usage can be centrally coordinated by the CU of the IAB donor. Each IAB node has the MT functionality discussed previously.

[0100] NGC is the 5G (Next Generation) Core to which the RAN nodes are connected via the NG interface. F1 is the interface between CU and DU. F1 is a standardized interface for wired CU-DU interface, while F1* may include some IAB specific enhancements due to wireless connections.

[0101] Figure 6 Another IAB architecture option using connection services for BH is shown. In this case, the IAB nodes including the donor IAB node host the entire gNB functionality with a complete protocol stack including RRC (Radio Resource Control). The IAB node hosts the MT functionality. In this case, the radio resource coordination can be distributed or the donor can act as a central coordinator of the IAB nodes. Figure 6 In the IAB, the user plane function (UPF) is a gateway function (which is a CN function), but can be included in the IAB node to establish a protocol data unit (PDU) session between the serving node and the served node MT to carry backhaul data. This is an alternative architecture to implement IAB operation. Bearers are provided between the MT of one node and the gNB or another node.

[0102] The partitioning for centralized units (CU) and distributed units (DU) may be used to partition the gNB functionality between the IAB donor and the IAB nodes. In this case, the backhaul connection also carries the gNB internal interface. It should be understood that some embodiments may be used with any of these architectures or any other suitable architecture.

[0103] In the following, a higher hop may be understood as communication from a device and another device to a donor access node, such as a communication hop between a relay node and a donor access node, and a lower hop may be understood as communication from a device and another device to a user equipment, such as a communication hop between a relay node acting as a service relay node and another relay node.

[0104] Base stations 116, 118 and 120 may be pico or femto level base stations, etc. In this example, base station 118 is connected via gateway 111, and base station 120 is connected via controller device 108. Base station 116 may be connected via base station 107, which will be described in further detail below. In some embodiments, smaller base stations may not be provided.

[0105] In some embodiments, frequency bands on the order of millimeter waves may be used. Alternatively or additionally, lower frequency bands may be supported.

[0106] In some embodiments, a RF beamforming architecture may be used at one or both of the gNB / IAB node and the communication device.

[0107] Some embodiments may primarily use TDD. Alternatively or additionally, FDD scenarios may be supported.

[0108] In some embodiments, self-backhaul may be primarily used. However, in some embodiments, out-of-band relaying may also be supported.

[0109] Now refer to Figure 2 Describing possible communication devices in more detail, Figure 2 A schematic partial cutaway view of a communication device 200 is shown. Such communication devices are generally referred to as user equipment (UE) or terminals. Suitable communication devices may be provided by any device capable of sending and receiving radio signals. Non-limiting examples include mobile stations (MS) or mobile devices such as mobile phones or so-called "smart phones", computers equipped with wireless interface cards or other wireless interface facilities (e.g., USB dongles), personal data assistants (PDAs) or tablets equipped with wireless communication capabilities, machine type devices, or any combination of these devices, etc.

[0110] The communication device 200 may receive signals via an air interface or radio interface 207 via appropriate means for receiving, and may transmit signals via appropriate means for transmitting radio signals. Figure 2 In the mobile device, the transceiver arrangement is schematically represented by block 206. The transceiver arrangement 206 may be provided, for example, by a radio part and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0111] The communication device is typically equipped with at least one data processing entity 201, at least one memory 202 and possibly other components 203 for use in the software and hardware assisted execution of the tasks it is designed to perform, including control of access and communication with access systems and other communication devices. The data processing, storage and other related control means may be provided on appropriate circuit boards and / or in a chipset. This feature is indicated by reference numeral 204.

[0112] The user may control the operation of the device by means of a suitable user interface such as keypad 205, voice commands, touch sensitive screen or pad, combinations thereof, etc. In some embodiments, this may be optional.

[0113] A display 208, speaker and microphone may also be provided. Again, this may be optional.

[0114] The communication devices 102, 104, 105 may access the communication system based on various access technologies. In some embodiments, the relay operation may be transparent to the UE.

[0115] exist Figure 3 An example control device is shown in FIG. Figure 3 An example of a control device provided in a base station, an IAB node, or an access point or a relay node is shown. The control device 300 includes at least one memory 301, at least one data processing unit 302, 303 and an input / output interface 304. The control device can be coupled to a receiver and a transmitter via the interface. The receiver and / or the transmitter can be implemented as a radio front end or a remote radio head. For example, the control device 300 or the processor 302 / 303 can be configured to execute appropriate software code to provide control functions.

[0116] One aspect of 5G New Radio (NR) is the physical layer design and related NR functionality for enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC). NR under this work item (NR Phase I) should consider frequency ranges up to 52.6 GHz. It is expected that NR work will continue after Phase I with various enhancements, also including frequency ranges greater than or less than 52.6 GHz. 5G NR should be able to allow network deployment with minimal manual and as automated self-configuration as possible. Especially in higher frequency bands, coverage can be an issue, and NR requires specific capabilities to enable easy coverage extension in a fast and cost-effective manner with minimal / no requirements for network (re)planning.

[0117] Therefore, NR (and mainly for these reasons) requires support for self-backhauling, where the same carrier is used for the backhaul connection and the access link to achieve in-band backhaul operation. Specific relay nodes can be used to provide wireless backhaul connections to base stations (rather than having a wired connection), and the base stations have a fixed connection to the network backhaul. The serving base station (or other network node that controls resource usage depending on the IAB architecture) can then fully control the use of radio resources, considering both the access and backhaul links.

[0118] The self-backhaul scenarios considered include both frequency division duplex (FDD) and time division duplex (TDD). TDD operates on an unpaired spectrum. The typical assumption for relay operation is that the IAB node cannot transmit and receive simultaneously in at least the same direction. This is called the half-duplex constraint.

[0119] refer to Figure 4 , which shows an example of a three-hop scenario. The example shows a gNB (or donor gNB or donor or IAB donor) 107, a first relay node (RN) 116a, a second relay node (RN) 116b, a third relay node (RN) 116c, a first communication device 105, a second communication device 105a, a third communication device 105b, and a fourth communication device 105c. In this scenario, there are access links between the nodes and the communication devices, which can be, for example, a first uplink / downlink access link 401 between the gNB 107 and the first communication device 105, a second uplink / downlink access link 401a between the first RN 116a and the second communication device 105a, a third uplink / downlink access link 401b between the second RN 116b and the third communication device 105b, and a third uplink / downlink access link 401c between the third RN 116c and the fourth communication device 105c. Figure 4 A backhaul link or a link between access points / relay nodes is shown. Figure 4 The figure shows a first-hop return link (BH Hop#1) 403a between the first RN 116a and the gNB 107, a second-hop return link (BH Hop#2) 403b between the second RN 116b and the first RN 116a, and a third-hop return link (BH Hop#3) 403c between the third RN 116c and the second RN 116b.

[0120] It should be understood that in other embodiments, there may be more or less than Figure 4 The number of hops shown in .

[0121] Some embodiments may involve resource allocation on BH and / or access connections. Some embodiments may consider multi-hop relays in IAB deployments. Some embodiments may provide robust operation while providing flexibility to adapt to capacity requirements on both BH links and access links.

[0122] Figure 7The basic connection between the IAB node and the access UE is shown. The IAB node has a child node and a parent or donor node. The IAB node has an uplink (UL) parent BH and a downlink (DL) parent BH with the parent or donor node. The IAB node has a UL access link and a DL access link with a communication device that can be regarded as a child device. The IAB node has a DL child BH and a UL child BH with the child node. Therefore, the child node is two hops away from the donor or parent node.

[0123] Some embodiments may address the issue of how to configure and control the use of each link. Some embodiments may configure and control the use of the links in such a way that there is no ambiguity at the IAB node as to whether DL / UL (downlink / uplink) scheduling on the IAB sublink is supported at a given time and at a given resource (e.g., physical resource block).

[0124] In some embodiments, the allocation may provide flexibility in allocating capacity. For example, when the traffic load varies on one or more of the access and BH connections, the allocation may be made as needed.

[0125] Some embodiments may facilitate interference management between nodes. For example, link direction alignment between nodes may be supported.

[0126] Some embodiments may use half-duplex operation with one or more of time domain multiplexing (TDM), frequency domain multiplexing (FDM), and space domain multiplexing (SDM). In some embodiments, half-duplex operation with TDM is used in combination with one or more of FDM and SDM. This can provide good resource utilization.

[0127] Some embodiments may use full-duplex operation of IAB nodes.

[0128] Some embodiments may be such that they may be used with legacy communications equipment configured to operate with legacy standards.

[0129] It should be noted that in other embodiments, one or more changes may be made to a communication device to allow the communication device to operate in accordance with some embodiments.

[0130] Some embodiments may define schedulable resources for IAB sublinks. In some embodiments, predefined resource type combinations are defined. The combination may be between a parent link and a sublink. This may be defined according to an IAB duplex scheme. The duplex scheme may be one or more of a TDM half-duplex scheme, an FDM / SDM half-duplex scheme, a full-duplex scheme, and / or any other suitable scheme. Rules may be defined for different links, such as priority rules.

[0131] Figure 8A table showing an example of resource type combinations for an IAB node. An IAB node is Figure 7 It is a node with a parent and a child. The child can be a communication device or another relay node. Figure 7 The following links are shown: DL Sub-BH, UL Sub-BH, DL Access (Sub), UL Access (Sub).

[0132] It should be understood that one or more additional resource type combinations may be provided in other embodiments. Alternatively or additionally, one or more resource type combinations may be omitted.

[0133] Each column of the table shows a resource type combination for an IAB node.

[0134] Based on this, the IAB node can determine which resources / resource types are available for sub-link scheduling (which is according to the responsibility of the IAB node). A blank entry indicates that the resource type is not active in the corresponding link (at a certain time, in a certain PRB physical resource block).

[0135] Different types support different IAB capabilities and different interference scenarios. To this end, some embodiments provide a plurality of different combinations. Different resource types can be allocated to different time domain resources (such as time slots / symbols).

[0136] The IAB node can use this information as a boundary condition to schedule the IAB sub-links (which is according to the responsibility of the IAB node).

[0137] Some embodiments may maintain the overall control and interference management at the upper node (parent node or IAB donor).However, some embodiments provide sufficient flexibility for the IAB nodes to perform scheduling.

[0138] Therefore, the resource type combination is used to determine the schedulable resources for the IAB sublink. The IAB node will use the resource type combination to define how to perform the actual scheduling. The IAB node may receive the resource type combination from the RRC or lower layer control via one or more of the following:

[0139] Cell-specific higher-layer signaling;

[0140] Dedicated higher layer signaling; and

[0141] A group common PDCCH (physical downlink control channel) indicating a slot format index for one or more time slots. This can be using downlink control information (DCI) format 2_0 or any other suitable format. An IAB node may receive multiple resource configurations for a resource. Different signaling options may have predefined priorities and rules for managing conflict situations. For example, dedicated high-level signaling may be able to cover flexible resources for cell-specific high-level signaling. Dynamic DL control signaling such as GC-PDCCH (DCI 2_0) or dedicated DCI may be able to cover flexible resources for cell-specific high-level signaling or dedicated high-level signaling. Dedicated DCI may be able to cover resource configurations defined by other signaling types.

[0142] The high-level (semi-static) coordination scheme may depend on one or more of the architecture and protocol choices:

[0143] The L2 architecture may operate according to centralized coordination. In the case of centralized coordination, the IAB donor may configure resource usage for multiple hops.

[0144] The L3 architecture may operate according to distributed coordination, where the parent IAB node is responsible for semi-static coordination. Information may be exchanged between IAB nodes to enhance resource utilization and control, taking into account resource allocation among neighboring nodes.

[0145] The parent IAB node may be responsible for DL / UL scheduling for the parent BH link.The parent IAB node may be responsible for dynamic resource coordination between the parent BH link and the child link.

[0146] exist Figure 8 In the example shown, the table shows types A to C and types 1 to 9. For each type, the table shows the operation of the parent BH link, the child BH link, and the child access link.

[0147] The resource type combination may be determined in a slot-specific or symbol-specific manner.

[0148] Types A through C are currently proposed resource types. Some embodiments may provide that the IAB node applies additional or alternative rules on how to operate with these resource types.

[0149] Types A, B and C may be, for example, as proposed in NR Rel-15. Type A means that the IAB node uses specific resources for the parent downlink (PDL) backhaul, type B means that the IAB node uses specific resources for the parent uplink (PUL), and type C is F (flexible), meaning that the IAB node uses specific resources for the parent BH, child BH and / or child access link. In NR Rel-15, signaling indicates whether the resources are D (PDL) and U (PUL) or F (flexible), which indicates resources potentially available for IAB DL sublinks.

[0150] Resource types A and B determine resources that are exclusive to the parent BH link. For these resource types, the parent BH link has priority. When operating according to these resource types, the IAB node may not schedule any signal in the IAB child link, which results in transmission or reception at the child link of the IAB node. These resources are used for IAB operation under TDM half-duplex constraints. When the IAB node is serving the parent BH, it cannot serve the child link.

[0151] Type A and Type B do not support simultaneous operation of sub-links and BH links.

[0152] The parent node may indicate D / F / U in the signaling. Link direction alignment between parent and child IAB nodes may not be supported by resource types A to C alone. The parent node may only indicate D / F / U, requiring some additional signaling / resource types in some cases. An example of an existing proposed link direction alignment problem is that when the parent node serves its access link communication device on the DL (but has no DL parent BH), the parent node cannot configure the IAB resource usage in a way that the IAB node will only use flexible resources for DL ​​traffic. (The DL in the access link of the parent node and the UL in the access link of the IAB node may be subject to cross-link interference). It should be noted that in some embodiments, link direction alignment may be supported.

[0153] When operating only according to resource type AC, the cell common signals in the IAB cell operate in flexible resources. When following the NR Rel-15 rules defined for flexible resources, the IAB node has synchronization signal blocks (SSBs), physical random access channels (PRACHs), and control resource set CORSET#0 configured for the IAB cell only when no periodic signals have been configured for PDL and PUL. The parent node can block SSB / PRACH / CORESET#0 through DCI.

[0154] Based on Rel-15 rules, flexible resources are coupled between the IAB parent link and the IAB child link. These rules need to be considered, for example, when configuring periodic signals and physical downlink control channel (PDCCH) monitoring. This can be on both the parent node and the child node. It should be understood that the current rules do not consider different duplex scenarios.

[0155] The timeslot configuration (based on resource types A to C) may be used to determine the schedulable resources for the IAB node at least in the case of TDM between the parent BH link and the child link. This may be used as a starting point for the IAB node scenario as well. In some embodiments, signaling principles such as a hierarchical structure (with TDD-UL-DL-ConfigurationCommon, TDD-UL-DL-ConfigurationDedicated, DCI format 2_0), adaptation period, granularity, etc. may be used.

[0156] Some embodiments may also use the signaling principles used for NR Rel-15 slot format indication (hierarchy, adaptation period, granularity, etc.) for IAB scenarios. In other embodiments, these signaling principles may not be used.

[0157] The current method has not been designed for IAB node scenarios, and there are some problems that may need to be solved. For example, Rel-15 signaling does not support link direction alignment (or other interference coordination) between different links. This means that additional signaling will be needed on NRRel-15. The time slot configuration based on Rel-15 includes the coupling between the parent BH link and the sub-link. According to the Rel-15 rules, the parent BH link can always have the highest priority. The parent node may suffer from scheduler restrictions (for example, to ensure that the periodic signal and PDCCH monitoring opportunities for the IAB node are outside the flexible resources). The IAB node may be difficult to configure the resources for the cell common signal SSB, PRACH and CORESET#0 (in some embodiments, these are provided in the flexible resources). The dynamic capacity allocation between access and BH may worsen the situation. Some embodiments can solve this problem.

[0158] Some embodiments may address the need to have a common framework cover different duplexing schemes (TDM / FDM / SDM, full duplex). It should be understood that in other embodiments, the framework may cover only one or some of the different duplexing schemes discussed.

[0159] Type C can be considered as a default resource type combination for an IAB node and means that the IAB node will flexibly use specific resources. Flexible F resource types can be used to facilitate dynamic BH / access capacity allocation. Type C can be flexible between parent DL BH, parent UL BH, and IAB sublinks. For flexible resources, a parent BH link can take precedence over an IAB sublink.

[0160] The rules defined for flexible resources may be used as a basis for determining whether the IAB has a valid resource allocation for the parent BH link. In some embodiments, the rules may be based on the rules defined in TS 38.213. For example, the rules may define that a flexible symbol may be used as a schedulable resource for an IAB child link if one or more of the following apply:

[0161] DCI 2_0 (if configured / detected) does not indicate that variable symbols are used as DL or UL (i.e., for the parent BH link);

[0162] During the variable symbol period, the IAB node has not received (in the DL parent BH link) an indication (DCI or higher layer configuration) regarding reception of PDCCH, Physical Downlink Shared Channel (PDSCH) or Channel State Information Reference Signal (CSI-RS); and

[0163] During the variable symbols, the IAB node has not received (in the UL parent BH link) an indication (DCI or higher layer configuration) about sending the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH) or Sounding Reference Signal (SRS).

[0164] In the case of half-duplex based on TDM between the access link and the BH link, if the IAB node has a valid resource allocation or PDCCH monitoring opportunity for the parent BH link based on the second configuration (DCI and / or high-layer signaling), it will define that type C resources are not available for the IAB sub-link. If not, type C resources are available for the IAB sub-link. (The first resource configuration may include one or more of the following: default configuration (all resources are flexible); cell-specific high-layer configuration; and dedicated high-layer configuration).

[0165] In the case of half-duplex based on SDM or FDM between the access link and the BH link, if the IAB node has a valid resource allocation for the parent DL BH link based on the second configuration (DCI and / or high-layer signaling or PDCCH monitoring opportunity), it will define the resource as a flexible resource available for the IAB sub-UL. If the IAB node has a valid resource allocation for the parent UL BH link based on the second configuration (DCI and / or high-layer signaling), it will define the resource as a flexible resource available for the IAB sub-DL.

[0166] In the case of full duplex based on SDM / FDM between the access link and the BH link, for type C resources, the IAB node has complete freedom in selecting resources for the IAB sublink. The parent node can use dynamic signaling (e.g., DCI 2_0) to change the type C resources to other resource types (e.g., type A, B, any one of types 1-9). This may require defining a slot format type corresponding to one or more (but not all) of types 1-9. The flexible resources (based on the first configuration) can be covered by the DCI indicated by DCI 2_0 (dynamic DCI).

[0167] The parent node can use dynamic signaling (e.g., DCI 2_0) to dynamically change the type C resource to other resource types (e.g., type A, B, type 1-9). This can facilitate dynamic capacity adaptation between the parent BH link and the child link, but it may require defining a slot format type (one or more of the reserved slot format indications SFI 56-254 can be used for this).

[0168] Types 1 to 3 are TDM-based half-duplex resources.

[0169] In some embodiments, resource types 1-3 may be considered as exclusive resources of the IAB sub-node based on TDM between the access link and the BH link.

[0170] In some embodiments, resource types A and B may take precedence over resource types 1-3. For example, if a resource is configured as resource type A or B, the IAB node may ignore DCI 2_0 that attempts to configure those resources as type 1-3.

[0171] In some embodiments, resource types 1-3 may take precedence over flexible resources (type C). When the IAB node has determined schedulable resources for the IAB sublink for at least one time instant and at least one physical resource block (PRB), the IAB node shall ignore (or discard) all UL / DL resource allocations and PDCCH monitoring opportunities corresponding to the parent BH link and the at least one time instant.

[0172] In some embodiments, common channels for the IAB sublink (eg, SSB, CORESET#0, and PRACH) may be allocated to resource types 1 and 2.

[0173] Type 1 means that the IAB node can use specific resources for sub-DL BH and sub-DL access.

[0174] Type 2 means that the IAB node can use specific resources for sub-UL BH and sub-UL access.

[0175] Type 3 means that the IAB can flexibly use specific resources for sub-BHs and accesses.

[0176] Types 4 and 5 are half-duplex based on SDM and / or FDM.

[0177] In the case of FDM and SDM between the access link and the BH link, resource types 4 and 5 may provide resources for the IAB sub-link. It should be understood that, alternatively or additionally, the parent node may dynamically allocate resource types A, B, C and / or types 1-3 for an IAB node supporting FDM / SDM between the access link and the BH link.

[0178] Type 4 means that the IAB node can use specific resources for sub-UL BH and sub-UL access as well as parent DL BH.

[0179] Type 5 means that the IAB node can use specific resources for child DL BH, child DL access and parent UL BH.

[0180] Types 6 to 9 are full-duplex resources.

[0181] Type 6 indicates that the IAB node can use DL BH for parent, child DL BH and child DL access.

[0182] Type 7 means that the IAB node can use specific resources for child UL BH, child UL access and parent UL BH.

[0183] Type 8 means that the IAB node can flexibly use specific resources for parent DL BH, child BH, and child access.

[0184] Type 9 means that the IAB node can flexibly use specific resources for parent UL BH, child BH, and child access.

[0185] The IAB node may not be allowed to use resource types 1-9 for link types other than the associated link options. In the case where the IAB node supports full-duplex operation between access links and BH links, resource types 6 to 9 may provide resources for IAB sub-links.

[0186] The IAB node may receive resource configuration from the parent node. This may be the case, for example, in the case of an L3 architecture. Depending on the IAB architecture, the RRC (for high-level signaling to configure resource usage) resides at the donor CU, as in the case of an IAB architecture using a split gNB architecture (such as Figure 5 or Figure 6 The same as shown). Information about the radio resource configuration of each IAB node in the subtended IAB topology may be located in a centralized node / function. Some embodiments may also be applicable in this case. Using an IAB architecture without CU / DU separation, the resource allocation provided by some embodiments may be applied hop by hop, where the parent node sets the basis for resource availability for the child nodes. The same principle can be repeated in a multi-hop scenario where the upstream node (i.e., the parent node) has priority for resources, taking into account the restrictions set by the grandparent node.

[0187] In some embodiments, the 5G network may support multi-hop wireless self-backhaul. Figure 4 An exemplary multi-hop resource allocation for a half-duplex IAB scenario with TDM between the parent BH link and the child link is shown. Some embodiments may assume a semi-static resource pool configuration and an even allocation between BH DL, BH UL, Access DL, and Access UL time slots. This example only includes up to three hops, but it can be easily extended to additional hops. It can be noted that in this example scenario (half-duplex, Access or TDM between BHs), Hop (k) and Hop (k+2) always serve the same link (BH DL, BH UL, Access DL, or Access UL).

[0188] In some embodiments, the IAB node reports duplex capabilities after initial access so that the parent node can configure resource type combinations accordingly.

[0189] In some embodiments, all IAB nodes may support resource types A, B, C, and types 1-3.

[0190] In some embodiments, an IAB node supporting half-duplex based on FDM and / or SDM may also support resource types 4 and 5.

[0191] In some embodiments, an IAB node capable of full-duplex operation may support all resource types.

[0192] refer to Fig. 9 , showing some resource type combinations that can be used in TDM scenarios.

[0193] Type 1 is used for DL ​​sub-access. This can be for DL ​​sub-access or DL ​​sub-BH.

[0194] Type 2 is used for UL sub-access. This can be for UL sub-access or UL sub-BH.

[0195] Type 3 is used for flexible sub-access. This can be for flexible sub-access or flexible sub-BH. IAB nodes can use these resources as DL sub-access or UL sub-access with full flexibility.

[0196] BH and access link can be time-division multiplexed with each other. Each resource type combination can contain two sub-types: access only, and BH only. In this example, type 1a can be used for sub-DL BH, and type 1b can be used for sub-access DL.

[0197] Type 2a may be used for sub-UL BH, and type 2b represents sub-UL BH.

[0198] Type 3a can be flexibly used for sub-BH (for UL or DL), and type 3b can be flexibly used for sub-access (for UL or DL).

[0199] refer to Fig.10 , shows some resource type combinations that can be used in FDM / SDM scenarios:

[0200] Type 4 means that the IAB node will use specific resources for child UL BH, child UL access and parent DL BH.

[0201] Type 4a may be used for IAB nodes that are used for both parent DL BH and child UL BH.

[0202] Type 4b is used for IAB nodes that receive both parent DL BH and child UL accesses.

[0203] Type 5 means that the IAB node will use specific resources for child DL BH, child DL access, and parent UL BH.

[0204] Type 5a is used for IAB nodes for both parent UL BH and child DL BH.

[0205] Type 5b is used for IAB nodes for both parent UL BH and child DL access.

[0206] refer to Fig.11 , showing a combination of resource types that may be used for resources available for a full-duplex scenario (IAB nodes transmitting and receiving simultaneously).

[0207] Type 6 indicates that the IAB node can use DL BH for parent, child DL BH and child DL access.

[0208] In the time division multiplexing option, type 6a is used for parent DL BH and child DL BH. Type 6b is used for parent DL BH and child DL access.

[0209] Type 7 means that the IAB node will use specific resources for child UL BH, child UL access, and parent UL BH.

[0210] In the time division multiplexing option, type 7a is used for parent UL BH and child UL BH. Type 7b is used for parent UL BH and child UL access.

[0211] Type 8 means that the IAB node will flexibly use specific resources for parent DL BH, child BH and child access.

[0212] In the time division multiplexing option, type 8a is used for parent DL BH and flexibly used for child BH. Type 8b is used for parent DL BH and flexibly used for child access.

[0213] Type 9 means that the IAB node will flexibly use specific resources for parent UL BH, child BH and child access. In the time division multiplexing option, type 9a is used for parent UL BH and flexibly for child BH. Type 9b is used for parent UL BH and flexibly for child access.

[0214] Now refer to Fig.12 Methods of some embodiments are described.

[0215] In step S1, a resource configuration is received at an IAB node from a parent node. The resource configuration defines a resource type combination for at least one time instant and at least one PRB. The resource type combination may include: Figure 8 Any one or more of the resource types shown.

[0216] In step S2, the IAB node or a control device in the node is configured to determine, based on the received resource configuration, schedulable resources for a sublink for at least one time instant and at least one PRB.

[0217] In step S3, resource allocation is performed for at least one sub-node link using the determined schedulable resources. The sub-node may be another IAB or a communication device.

[0218] It should be understood that the naming of the types is merely exemplary and different embodiments may have different naming.

[0219] The number of types is merely exemplary, and different embodiments may have different numbers of types.

[0220] Some embodiments may provide for explicit determination of the rules for use and how radio resources are used at each IAB node.

[0221] Some embodiments may support various implementation options for IAB nodes.

[0222] Some embodiments may be compatible with NR Rel-15. In some embodiments, a communication device or UE may operate with Rel-15 rules, and an IAB node may operate as described in one or more of the described embodiments. The cell common configuration may be common to the access UE and the IAB node. The dedicated UE specific configuration may be different for the access UE and the IAB node. DCI 2_0 may be different for the access UE and the IAB node.

[0223] Some embodiments may enable resource allocation to adapt to changing traffic and radio conditions over multiple hops of self-backhaul.

[0224] Some embodiments may be used with so-called normal slot types. Alternatively or additionally, some embodiments may be used with so-called mini-slots such as provided in NR.

[0225] Some embodiments may be applicable to any IAB architecture option with centralized control or distributed control and gNB architecture.

[0226] Some embodiments may be straightforward to implement, since dynamic BH and / or access adaptation are not mandatory for the network.Using the current rules currently proposed, the use of flexible resources and a corresponding framework is required, which may be relatively complex in some cases.

[0227] Some embodiments may provide robust operation of cell common channels operating in an IAB sublink. This may be advantageous if these channels defining the cell can always be sent. This may be in contrast to current proposals where it may be that an IAB node is serving a parent BH when it should be sending / receiving common channels via an access link.

[0228] Some embodiments may provide a general framework that supports one or more different duplexing schemes. In some embodiments, the same framework may support all different duplexing schemes.

[0229] It should be understood that each block in the flowcharts of the drawings and any combination thereof may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuits.

[0230] It should be noted that although embodiments have been described with respect to one example of a 5G network, similar principles may apply to other examples of networks. It should be noted that other embodiments may be based on standards other than the 3GPP standard. Therefore, although certain embodiments are described above by way of example with reference to certain example architectures for wireless networks, technologies, and standards, the embodiments may be applicable to any other suitable form of communication system other than the communication system shown and described herein.

[0231] It is also noted herein that while the above describes exemplifying embodiments, there are numerous variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0232] It should be understood that these devices may include or be coupled to other units or modules, such as a radio part or radio head for transmission and / or reception. Although these devices have been described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0233] In general, various embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but the invention is not limited thereto. Although various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other graphical representation, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0234] Embodiments of the present invention may be implemented by computer software executable by a data processor of a mobile device (e.g., in a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products) including software routines, applets and / or macros may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is run. One or more computer executable components may be at least one software code or a portion thereof.

[0235] Further, in this regard, it should be noted that any block of the logic flow as in the figure may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disk, and optical media such as DVD and its data variants CD.

[0236] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology (e.g., semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory). The data processor may be of any type suitable for the local technical environment and may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a gate level circuit, and a processor based on a multi-core processor architecture, as non-limiting examples.

[0237] Embodiments of the present invention may be practiced in various components such as integrated circuit modules. The design of integrated circuits is essentially a highly automated process. Complex and powerful software tools are available to convert a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0238] The foregoing description provides a complete and informative description of exemplary embodiments of the present invention by way of exemplary and non-limiting examples. However, various modifications and adaptations will become apparent to those skilled in the relevant art in view of the foregoing description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications to the teachings of the present invention will still fall within the scope of the present invention. Indeed, there are further embodiments comprising a combination of one or more embodiments with any other embodiments previously discussed.

Claims

1. A method for resource allocation, comprising: receiving a resource configuration from at least one of a parent node or a donor node, the resource configuration comprising information defining at least one resource type for a plurality of links for at least one time and at least one resource; receiving further configuration information indicating that flexible parent node link type resources are reserved for a link with the parent node or donor node; as well as allocating one or more resources of the at least one resource type for the at least one time to at least one link of the plurality of links based on the information defining the at least one resource type for the plurality of links for the at least one time and the at least one resource and the further configuration information, the at least one link being with one or more child nodes; The allocation includes at least one of the following: determining that at least one time and at least one resource are not allocable to any of the plurality of sub-links, and operating according to the further configuration information; or If at least one time and at least one resource are reserved for the uplink parent node backhaul, determining that the at least one time and at least one resource are allocable to the downlink sublink, or If at least one time and at least one resource are reserved for the downlink parent node backhaul, it is determined that the at least one time and the at least one resource are allocatable to the uplink sublink.

2. The method according to claim 1, wherein: The method includes determining, based on the received resource configuration, one or more schedulable resources for the at least one link of the plurality of links for the at least one time and the at least one resource, the allocating using the determined schedulable resources.

3. The method according to claim 1, wherein: The at least one resource comprises at least one physical resource block.

4. The method according to any one of claims 1 to 3, wherein: At least one resource type is flexibly assignable to any one of the plurality of links.

5. The method according to any one of claims 1 to 3, wherein: The multiple links include one or more of the following: an uplink backhaul link with the first subnode, a downlink backhaul link with the first subnode, an uplink access link with the second subnode, and a downlink access link with the second subnode.

6. The method according to claim 5, wherein: At least one resource type defines an access link with the second sub-node and a backhaul link with the first sub-node for at least one time and at least one resource.

7. The method according to claim 5, wherein: One or more of the following resource types are defined by the information in the resource configuration: a first type for a downlink sub-access link with the second sub-node and a downlink backhaul link with the first sub-node; a second type for an uplink sub-access link with the second sub-node and an uplink backhaul link with the first sub-node; as well as A third flexible type may be used for any of said links with the first sub-node and the second sub-node.

8. The method according to any one of claims 1 to 3, further comprising: Allocation of the at least one time and the at least one resource to the link with the parent node is discarded, and the at least one time and the at least one resource are used for at least one link with at least one child node.

9. The method according to any one of claims 1 to 3, wherein: At least one resource type is such that at least one time and at least one resource are non-schedulable for the child link and schedulable for the link with the parent node.

10. The method according to any one of claims 1 to 3, wherein: One or more of the following resource types are defined by the information in the resource configuration: a first parent node link type for a downlink backhaul link with the parent node; a second parent node link type for an uplink backhaul link with the parent node; and A flexible parent node link type may be used for any of said links with said parent node and said child nodes.

11. The method according to any one of claims 1 to 3, wherein: At least one parent node link is time multiplexed with respect to at least one child link.

12. The method according to any one of claims 1 to 3, wherein: At least one parent node link and at least one child link are at least one of the following relative to each other: frequency division multiplexing, or space division multiplexing.

13. The method according to any one of claims 1 to 3, wherein: The resource types include one or more resource types for a plurality of links, wherein at least one link is with the parent node and at least one link is with a child node.

14. The method according to claim 13, wherein: At least one link with the parent node is one of an uplink and a downlink, and at least one link with the child node is one of an uplink and a downlink.

15. The method according to claim 10, wherein: One or more of the following resource types are defined by the information in the resource configuration: a fourth type for the uplink parent node backhaul and one or more of: a downlink child access link with the second child node, and a downlink backhaul link with the first child node; as well as A fifth type is used for the uplink parent node backhaul and one or more of: an uplink child access link with the second child node, and an uplink backhaul link with the first child node.

16. The method according to claim 10, wherein: One or more of the following resource types are defined by the information in the resource configuration: a sixth type for the uplink parent node backhaul and one or more of: an uplink child access link with the second child node, and an uplink backhaul link with the first child node; a seventh type for the downlink parent node backhaul and one or more of: an uplink child access link with the second child node, and an uplink backhaul link with the first child node; an eighth type for said uplink parent node backhaul and any said links with said first child node and said second child node; as well as A ninth type for the downlink parent node backhaul and any of the links with the first child node and the second child node.

17. The method according to any one of claims 1 to 3, wherein: The at least one time includes a plurality of time slots, and the resource type is one or more of time slot specific and symbol specific.

18. The method according to any one of claims 1 to 3, wherein: The resource configuration is provided by at least one of: a cell specific higher layer configuration; a dedicated higher layer configuration; or a group common physical downlink control channel.

19. A method for resource allocation, comprising: causing a resource configuration to be sent from a parent node or a donor node to a child node of the parent node or the donor node, the resource configuration comprising information defining at least one resource type for a plurality of links for at least one time and at least one resource; causing further configuration information to be sent from the parent node or donor node to the child node of the parent node or donor node, wherein the further configuration information indicates that flexible parent node link type resources are reserved for a link with the parent node or donor node, wherein the information and the further configuration information enable the child node to allocate one or more resources of the at least one resource type for the at least one time to at least one link of the plurality of links with one or more child nodes of the child node; The allocation includes at least one of the following: determining that at least one time and at least one resource are not allocable to any of the plurality of sub-links, and operating according to the further configuration information; or If at least one time and at least one resource are reserved for the uplink parent node backhaul, determining that the at least one time and at least one resource are allocable to the downlink sublink, or If at least one time and at least one resource are reserved for the downlink parent node backhaul, it is determined that the at least one time and the at least one resource are allocatable to the uplink sublink.

20. The method according to claim 19, wherein: The resource configuration is sent from the parent or donor node to at least one integrated access and backhaul node.

21. An apparatus for resource allocation, comprising at least one processor and at least one memory, the at least one memory storing computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to at least: receiving a resource configuration from at least one of a parent node or a donor node, the resource configuration comprising information defining at least one resource type for a plurality of links for at least one time and at least one resource; receiving further configuration information indicating that flexible parent node link type resources are reserved for a link with the parent node or donor node; and allocating one or more resources of the at least one resource type for the at least one time to at least one link of the plurality of links based on the information defining the at least one resource type for the plurality of links for the at least one time and the at least one resource and the further configuration information, the at least one link being with one or more child nodes; in, The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to distribute by at least one of: determining that at least one time and at least one resource are not allocable to any of the plurality of sub-links, and operating according to the further configuration information; or If at least one time and at least one resource are reserved for the uplink parent node backhaul, determining that the at least one time and at least one resource are allocable to the downlink sublink, or If at least one time and at least one resource are reserved for the downlink parent node backhaul, it is determined that the at least one time and the at least one resource are allocatable to the uplink sublink.

22. The device according to claim 21, wherein The at least one memory and the computer program code are further configured to cause the apparatus to at least: determine, based on the received resource configuration, one or more schedulable resources for the at least one link among the plurality of links for the at least one time and the at least one resource, the allocating using the determined schedulable resources.

23. The device according to claim 21, wherein The at least one resource comprises at least one physical resource block.

24. The device according to any one of claims 21 to 23, wherein: At least one resource type is flexibly assignable to any one of the plurality of links.

25. The device according to any one of claims 21 to 23, wherein The multiple links include one or more of the following: an uplink backhaul link with the first subnode, a downlink backhaul link with the first subnode, an uplink access link with the second subnode, and a downlink access link with the second subnode.

26. The device according to claim 25, wherein At least one resource type defines an access link with the second sub-node and a backhaul link with the first sub-node for at least one time and at least one resource.

27. The device according to claim 25, wherein: One or more of the following resource types are defined by the information in the resource configuration: a first type for a downlink sub-access link with the second sub-node and a downlink backhaul link with the first sub-node; a second type for an uplink sub-access link with the second sub-node and an uplink backhaul link with the first sub-node; as well as A third flexible type may be used for any of said links with the first sub-node and the second sub-node.

28. The device according to any one of claims 21 to 23, wherein: The at least one memory and the computer program code are further configured to cause the apparatus to at least: discard allocation of the at least one time and at least one resource to the link with the parent node, and use the at least one time and at least one resource for at least one link with at least one child node.

29. The device according to any one of claims 21 to 23, wherein: At least one resource type is such that at least one time and at least one resource are non-schedulable for the child link and schedulable for the link with the parent node.

30. The device according to any one of claims 21 to 23, wherein: One or more of the following resource types are defined by the information in the resource configuration: a first parent node link type for a downlink backhaul link with the parent node; a second parent node link type for an uplink backhaul link with the parent node; and A flexible parent node link type may be used for any of said links with said parent node and said child nodes.

31. The device according to any one of claims 21 to 23, wherein: At least one parent node link is time multiplexed with respect to at least one child link.

32. The device according to any one of claims 21 to 23, wherein: At least one parent node link and at least one child link are at least one of the following relative to each other: frequency division multiplexing, or space division multiplexing.

33. The device according to any one of claims 21 to 23, wherein: The resource types include one or more resource types for a plurality of links, wherein at least one link is with the parent node and at least one link is with a child node.

34. The device according to claim 33, wherein At least one link with the parent node is one of an uplink and a downlink, and at least one link with the child node is one of an uplink and a downlink.

35. The device according to claim 30, wherein: One or more of the following resource types are defined by the information in the resource configuration: a fourth type for the uplink parent node backhaul and one or more of: a downlink child access link with the second child node, and a downlink backhaul link with the first child node; as well as A fifth type is used for the uplink parent node backhaul and one or more of: an uplink child access link with the second child node, and an uplink backhaul link with the first child node.

36. The device according to claim 30, wherein: One or more of the following resource types are defined by the information in the resource configuration: a sixth type for the uplink parent node backhaul and one or more of: an uplink child access link with the second child node, and an uplink backhaul link with the first child node; a seventh type for the downlink parent node backhaul and one or more of: an uplink child access link with the second child node, and an uplink backhaul link with the first child node; an eighth type for said uplink parent node backhaul and any said links with said first child node and said second child node; as well as A ninth type for the downlink parent node backhaul and any of the links with the first child node and the second child node.

37. The device according to any one of claims 21 to 23, wherein: The at least one time includes a plurality of time slots, and the resource type is one or more of time slot specific and symbol specific.

38. The device according to any one of claims 21 to 23, wherein: The resource configuration is provided by at least one of: a cell specific higher layer configuration; a dedicated higher layer configuration; or a group common physical downlink control channel.

39. An apparatus for resource allocation, comprising at least one processor and at least one memory, the at least one memory storing computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus to at least: causing a resource configuration to be sent to a child node of the apparatus, the resource configuration comprising information defining at least one resource type for a plurality of links for at least one time and at least one resource; causing further configuration information to be sent to said child nodes of said device, wherein the further configuration information indicates that flexible parent node link type resources are reserved for a link with the device, wherein the information and the further configuration information enable the child node to allocate one or more resources of the at least one resource type for the at least one time to at least one link of the plurality of links, the at least one link being with one or more children of the child node of the device; The allocation includes at least one of the following: determining that at least one time and at least one resource are not allocable to any of the plurality of sub-links, and operating according to the further configuration information; or If at least one time and at least one resource are reserved for the uplink parent node backhaul, determining that the at least one time and at least one resource are allocable to the downlink sublink, or If at least one time and at least one resource are reserved for the downlink parent node backhaul, it is determined that the at least one time and the at least one resource are allocatable to the uplink sublink.

40. The device according to claim 39, wherein The resource configuration is sent to at least one integrated access and backhaul node.

41. A non-transitory computer readable medium encoding instructions which, when executed in hardware, perform the method of any one of claims 1 to 20.

42. An apparatus for resource allocation, comprising means for performing the method of any one of claims 1 to 18.

43. An apparatus for resource allocation, comprising means for performing the method of any one of claims 19 to 20.

Citation Information

Patent Citations

  • Method of uplink control channel allocation for a relay backhaul link

    CN103109472A

  • Allocation of communication resources for control signals in the uplink

    CN104041163A

  • Method and apparatus of transmitting and receiving backhaul downlink control information in wireless communication system

    US20120069790A1

  • Allocating backhaul resources

    US20130034043A1

  • Dynamic resource allocation in wireless network

    US20180042031A1