CN111901871A

CN111901871A - Resource allocation method, device, communication node and storage medium

Info

Publication number: CN111901871A
Application number: CN202010275711.5A
Authority: CN
Inventors: 苗婷; 邢卫民; 毕峰; 卢有雄; 刘文豪
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-04-09
Filing date: 2020-04-09
Publication date: 2020-11-06
Also published as: WO2021203873A1

Abstract

The application provides a resource allocation method, a device, a communication node and a storage medium, wherein the method comprises the following steps: acquiring at least one multiplexing resource configuration information, wherein the multiplexing resource configuration information is used for indicating the configuration of multiplexing resources; and carrying out data transmission based on the multiplexing resource configuration information.

Description

Resource allocation method, device, communication node and storage medium

Technical Field

The present application relates to the field of communications, and in particular, to a resource allocation method, apparatus, communication node, and storage medium.

Background

For the new generation mobile communication system, the node having the wired Backhaul link with the core network is an Integrated Access and Backhaul (IAB) donor. The node connected to the donor IAB (or upper IAB node) by radio is the IAB node, and there is no direct connection between the IAB node and the core network. The interaction between the IAB node and the core network needs to be performed through one or more times of forwarding, and finally, the interaction is realized by means of the IAB donor. Either the IAB donor or the IAB node supports access for the terminal.

The IAB node may multiplex the parent backhaul link and the child backhaul link (or the child access link) in time, frequency, or space domain. However, when data is transmitted simultaneously by using Frequency Division Multiplexing (FDM) or Space Division Multiplexing (SDM), the problem of resource allocation is an urgent technical problem to be solved.

Disclosure of Invention

In order to solve the above technical problem, the present application provides a resource allocation method, an apparatus, a communication node, and a storage medium.

In a first aspect, an embodiment of the present application provides a resource allocation method, applied to a first communication node, including:

acquiring at least one multiplexing resource configuration information, wherein the multiplexing resource configuration information is used for indicating the configuration of multiplexing resources;

and carrying out data transmission based on the multiplexing resource configuration information.

In a second aspect, an embodiment of the present application provides a resource allocation method, applied to a second communication node, including:

determining at least one multiplexing resource configuration information, wherein the multiplexing resource configuration information is used for indicating the configuration of multiplexing resources;

and sending the multiplexing resource configuration information.

In a third aspect, an embodiment of the present application provides a resource allocation apparatus, configured at a first communication node, including:

an obtaining module configured to obtain at least one multiplexing resource configuration information, where the multiplexing resource configuration information is used to indicate a configuration of multiplexing resources;

and the transmission module is configured to transmit data based on the multiplexing resource configuration information.

In a fourth aspect, an embodiment of the present application provides a resource allocation apparatus, configured at a second communication node, including:

a determining module configured to determine at least one multiplexing resource configuration information, the multiplexing resource configuration information being used to indicate a configuration of multiplexing resources;

and the sending module is configured to send the multiplexing resource configuration information.

In a fifth aspect, an embodiment of the present application provides a communication node, including:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement any one of the methods in the embodiments of the present application.

In a sixth aspect, the present application provides a storage medium storing a computer program, where the computer program is executed by a processor to implement any one of the methods in the embodiments of the present application.

With regard to the above embodiments and other aspects of the present application and implementations thereof, further description is provided in the accompanying drawings description, detailed description and claims.

Drawings

Fig. 1 is a schematic flowchart of a resource allocation method provided in the present application;

fig. 1a is a schematic relationship diagram of each node in an IAB network provided in the present application;

fig. 2 is a schematic flowchart of a resource allocation method provided in the present application;

fig. 2a is a schematic diagram of a time-frequency domain resource attribute configuration with a frequency unit being an RB according to the present application;

fig. 2b is a schematic diagram of a time-frequency domain resource attribute configuration with RBGs as a frequency unit according to the present application;

fig. 2c is a schematic diagram of the application for indicating the availability of soft frequency resources in a manner of RBG numbers and bitmaps when a frequency unit is an RBG;

fig. 3 is a schematic structural diagram of a resource allocation apparatus provided in the present application;

fig. 4 is a schematic structural diagram of a resource allocation apparatus provided in the present application;

fig. 5 is a schematic structural diagram of a communication node provided in the present application;

FIG. 6 is a schematic illustration of a transition position provided herein;

FIG. 7 is a schematic illustration of yet another alternate switching position provided herein;

fig. 8 is a schematic view of another alternate switching position provided by the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.

The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.

In an exemplary embodiment, fig. 1 is a flowchart illustrating a resource configuration method provided in the present application, where the method may be applied to a case of resource configuration. The method may be performed by a resource configuration arrangement as provided herein, which may be implemented by software and/or hardware, and integrated on the first communication node. The first communication node may be an IAB node or an IAB donor.

An IAB donor consists of a Centralized Unit (CU) and one or more Distributed Units (DU), and can obtain downlink data or send uplink data to a core network.

The IAB node has two functions: 1) a distributed unit DU function (i.e., a base station), that is, an IAB node provides a radio access function for a child node or a User Equipment (UE) like a base station; 2) Mobile-Termination (MT) functions (i.e., terminals), i.e., IAB nodes, are controlled and scheduled by a parent node (IAB node or IAB donor) like a UE.

Fig. 1a is a schematic relationship diagram of each node in an IAB network provided in the present application. Referring to fig. 1a, an IAB node is a current node as a reference, a node at the previous stage is called a parent node, and the parent node may be the IAB node or an IAB donor; the next-level node of the IAB node may be an IAB node (child node) or may be a UE. The link between the IAB node and the previous node is called a parent link, and the link between the IAB node and the next node (or UE) is called a child link. In one embodiment, the link between the IAB node and its Parent node is called a Parent Backhaul link (i.e., a Parent Backhaul link), and is divided into a downlink Parent Backhaul link (i.e., DL Parent Backhaul) and an uplink Parent Backhaul link (i.e., UL Parent Backhaul); a link between the IAB node and a next-level node (i.e., a Child Backhaul link) is called a Child Backhaul link, and is divided into a downlink Child Backhaul link (i.e., DL Child Backhaul) and an uplink Child Backhaul link (i.e., UL Child Backhaul); the link between the IAB node and the UE is called a Child access link (i.e., a Child access link), and is divided into a downlink Child access link (i.e., DL Child access) and an uplink Child access link (i.e., UL Child access).

The Multiplexing method adopted by the IAB node depends on the Multiplexing capability of the IAB node, and considering that when the IAB node adopts a Time Division Multiplexing (TDM) method, a parent backhaul link and a child backhaul link (or a child access link) cannot simultaneously perform data transmission, the utilization rate of spectrum resources is low, and transmission delay is large, so that Frequency Division Multiplexing (FDM) or Space Division Multiplexing (SDM) is important for improving the utilization rate of spectrum resources and reducing transmission delay, and the IAB node can simultaneously transmit data to the parent node and the child node (or a terminal) and also can simultaneously receive the data transmitted by the parent node and the child node (or the terminal) by adopting an FDM/SDM method, so as to improve the utilization rate of resources and reduce the transmission delay. In order to make the IAB node more effectively adopt the FDM/SDM mode to transmit signals simultaneously, the resource allocation problem in FDM/SDM needs to be considered.

In order to enable the IAB node to more effectively transmit signals simultaneously in the FDM/SDM manner, a resource allocation method is provided, and as shown in fig. 1, the resource allocation method provided by the present application includes S110 to S120.

S110, obtaining at least one multiplexing resource configuration information, wherein the multiplexing resource configuration information is used for indicating the configuration of multiplexing resources.

The multiplexing resources include, but are not limited to, frequency domain resources and time domain resources. The first communication node may receive at least one multiplexing resource configuration information sent by the second communication node for resource configuration.

One or more of frequency domain resource attribute configuration, frequency domain resource configuration, and time domain resource configuration may be implemented based on the multiplexing resource configuration information in this embodiment.

The first communication node may acquire at least one multiplexing resource configuration information transmitted by the CU, where the multiplexing resource configuration information may include frequency domain resource attribute configuration information.

The first communication node may also obtain at least one multiplexing resource configuration information of the parent node or the serving cell, where the multiplexing resource configuration information may include frequency domain resource configuration information.

Wherein the CU, the parent node, and the serving cell may be a second communication node.

The frequency domain resource attribute configuration information may be used to configure the frequency domain resource attribute of each frequency unit. The frequency domain resource attributes include one or more of: hard, soft and unusable. The frequency domain resource configuration information is used to indicate availability of frequency domain resources.

In this embodiment, the multiplexing resource configuration information may further include time domain resource configuration information. The time domain resource configuration information may be used to configure the availability of the time domain resources.

Wherein the availability includes at least one of: whether available may be multiplexed, not multiplexed or determined according to the usage of the MT of the first communication node.

Each multiplexing resource configuration information in the at least one multiplexing resource configuration information obtained by the present application may correspond to one cell, one carrier, or at least one resource type.

The first communication node in the present application may also report the expected multiplexing resource configuration information. Such as reporting the desired multiplexing resource configuration information to a parent node of the first communication node (or a serving cell of the MT of the first communication node). The reporting timing is not limited, and may be before, after, or when the at least one piece of multiplexing resource configuration information is acquired.

Reporting the expected multiplexing resource configuration information before acquiring at least one piece of multiplexing resource configuration information, so that the father node can determine the multiplexing resource configuration information sent to the first communication node. The parent node may determine a multiplexing resource configuration to send to the first communication node based on the desired multiplexing resource configuration information; it is also possible to directly determine the multiplexing resource configuration information sent to the first communication node.

And reporting the expected multiplexing resource configuration information after acquiring at least one piece of multiplexing resource configuration information, wherein the expected multiplexing resource configuration information can be used by the father node for determining the multiplexing resource configuration information next time. The desired multiplexing resource configuration information may be regarded as multiplexing resource configuration information that the first communication node desires the parent node to transmit.

The method may further include obtaining, from the CU, at least one multiplexing resource configuration information of a child node of the first communication node to determine, based on the multiplexing resource configuration information, frequency domain resources that may be used by the child link of the child node and/or to indicate availability of soft frequency domain resources of the child node.

It should be noted that, in the present application, specific contents of the multiplexing resource configuration information and the multiplexing resource configuration information of the first communication node may refer to corresponding contents of at least one multiplexing resource configuration information (i.e., the multiplexing resource configuration information of the first communication node) acquired by the first communication node, which are not described herein again.

And S120, carrying out data transmission based on the multiplexing resource configuration information.

After the at least one piece of multiplexing resource configuration information is acquired, the resource used for data transmission can be determined, and then data transmission is performed on the determined resource.

The resource allocation method provided by the application comprises the steps of firstly, obtaining at least one multiplexing resource allocation message, wherein the multiplexing resource allocation message is used for indicating the allocation of multiplexing resources; and then, based on the multiplexing resource configuration information, carrying out data transmission. The method effectively solves the problem of resource configuration and improves the resource utilization rate.

On the basis of the above-described embodiment, a modified embodiment of the above-described embodiment is proposed, and it is to be noted herein that, in order to make the description brief, only the differences from the above-described embodiment are described in the modified embodiment.

In one embodiment, the method further comprises one or more of:

reporting expected multiplexing resource configuration information;

obtaining at least one multiplexing resource configuration information of a child node of the first communication node.

In one embodiment, the multiplexing resource configuration information includes one or more of: a reference subcarrier spacing; frequency domain resource attribute configuration information; time domain resource configuration information; or, the multiplexing resource configuration information includes one or more of the following: a reference subcarrier spacing; frequency domain resource configuration information; time domain resource configuration information.

In one embodiment, the frequency domain resource attribute configuration information is used to configure the frequency domain resource attribute for each frequency unit.

The frequency unit comprises any one of the following: a resource block; a group of resource blocks; a sub-band; a sub-band group; a subcarrier; a subcarrier group; the number of the frequency resource groups is a result of dividing the bandwidth by m and rounded up, wherein m is an integer greater than or equal to 1, the size of each frequency resource group is m resource blocks under the condition that the result of dividing the bandwidth by m is an integer, the size of one frequency resource group is the bandwidth mod m under the condition that the result of dividing the bandwidth by m is not an integer, the sizes of the other frequency resource groups are m, and mod is modular operation.

In one embodiment, the frequency domain resource attributes include one or more of: hard; soft; is not available.

In one embodiment, in a case that a frequency domain resource is configured to be hard, a sublink of a node corresponding to the frequency domain resource may use the frequency domain resource;

in the case that a frequency domain resource is configured to be soft, whether a sublink of a node corresponding to the frequency domain resource can be indicated by a parent node or a serving cell of the node using the frequency domain resource;

and under the condition that the frequency domain resources are configured to be unavailable, the sublink of the node corresponding to the frequency domain resources cannot use the frequency domain resources.

In the case where the frequency domain resource is configured to be soft, the frequency domain resource may be considered to be sharable, and the parent node or the serving cell may determine, according to actual conditions, the availability of the sublinks of the nodes corresponding to the frequency domain resource for the frequency domain resource.

In one embodiment, where the frequency domain resources are configured to be soft, one of:

indicating the availability of each frequency unit of the frequency domain resource through a bitmap, wherein each bit in the bitmap corresponds to one frequency unit, and the size of the bitmap is a fixed value, or has a corresponding relation with a bandwidth corresponding to a reference subcarrier interval, or is the total number of frequency units or soft frequency units contained in the bandwidth corresponding to the reference subcarrier interval;

indicating availability of each frequency cell of the frequency domain resource by indicating a location of an available frequency cell;

indicating availability of each frequency unit of the frequency domain resources by an index indicating available frequency units, the frequency units not indicated being unavailable or available being determined in dependence on usage of mobile terminal resources of the first communication node;

indicating availability of each frequency cell of the frequency domain resources by an index indicating unavailable frequency cells, the availability or availability of non-indicated frequency cells being determined in dependence on usage of mobile terminal resources of the first communication node.

The availability of each frequency unit of the soft frequency domain resources is indicated by a bitmap. When the bit number of the bitmap is greater than the total number of soft frequency units contained in the bandwidth corresponding to the reference subcarrier interval, the bit corresponding to only the soft frequency unit in the bitmap is valid, and the rest bits are invalid, or the availability of each frequency unit of the soft frequency domain resource is indicated by using a part of the bitmap (for example, the first X bits, where X is the total number of soft frequency units contained in the bandwidth corresponding to the reference subcarrier interval).

The index of the frequency unit can uniquely identify the frequency unit, for example, by numbering the soft frequency resource according to the frequency unit, or numbering the bandwidth corresponding to the soft frequency resource according to the frequency unit, and using the numbering as the index of the frequency unit.

In the case where availability is determined in accordance with resource usage by the first correspondent node mobile terminal, the determination may be based on the conflict of frequency units with the mobile terminal's usage of resources. Conflicts include conflicts and non-conflicts.

In one embodiment, the frequency domain resource configuration information indicates available frequency domain resources by one of:

each bit in the bitmap corresponds to a frequency unit, and the size of the bitmap is a fixed value or the total number of frequency units contained in a bandwidth corresponding to a reference subcarrier interval;

the location of available frequency units;

indices of available frequency units.

In one embodiment, the frequency unit comprises any one of: a resource block; a group of resource blocks; a sub-band; a sub-band group; a subcarrier; a subcarrier group; the method comprises the steps that frequency resource groups are obtained by rounding up the result of dividing a bandwidth by m, the m is an integer larger than or equal to 1, the size of each frequency resource group is m resource blocks under the condition that the result of dividing the bandwidth by m is an integer, the size of one frequency resource group is a bandwidth modm under the condition that the result of dividing the bandwidth by m is not an integer, the sizes of the other frequency resource groups are m, and mod is modular operation.

In one embodiment, the frequency domain resource attribute configuration information or the frequency domain resource configuration information is valid in a case where the parent link and the child link of the node employ frequency division multiplexing; alternatively, the first and second electrodes may be,

the frequency domain resource attribute configuration information or the frequency domain resource configuration information is effective under the condition that the parent link and the sublinks of the nodes adopt frequency division multiplexing and space division multiplexing; alternatively, the first and second electrodes may be,

the frequency domain resource attribute configuration information or the frequency domain resource configuration information is effective in the case that the parent link and the child link of the node adopt all multiplexing modes.

In one embodiment, the time domain resource configuration information includes one or more of: multiplexing a resource cycle; multiplexing a resource time slot set; multiplexing the resource symbols; and (4) multiplexing mode.

The multiplexing resource period may be regarded as a period of multiplexing resources. The present embodiment determines availability on a periodic basis.

The set of multiplexed resource slots may indicate slots that are reusable within a multiplexed resource period. The multiplexing resource symbol may indicate the reusability of symbols in a multiplexing slot within a multiplexing resource period; or the reusability of symbols within a multiplexing resource period. Reusability includes at least one of: can be reused, not be reused or indicate whether to be reused according to the rest information. The remaining information is not limited herein.

In one embodiment, the set of multiplexed resource slots is indicated by one of: a bit in the bitmap corresponds to a time slot in a multiplexing resource period, and the bit value of the bitmap is used for indicating whether the corresponding time slot is a multiplexing resource or not; multiplexing the index of the time slot in the resource period; multiplexing a starting time slot index and a multiplexing time slot number which can be multiplexed in a resource period; a start slot index and an end slot index that are multiplexed within the resource period.

The start slot index may be considered as an index of the start slot. The termination slot index may be regarded as an index of the termination slot.

In one embodiment, a multiplexing resource symbol indicates the reusability of a symbol in a reusable slot in a set of multiplexing resource slots; or multiplexing the reusability of symbols in the resource period.

In one embodiment, the multiplexing resource symbols are configured by one of: multiplexing symbols are configured for each time slot independently; and the reusable symbols are uniformly configured for all time slots.

In one embodiment, symbols not included in the multiplexed resource symbols are not multiplexed; or the reusability of symbols not included in the multiplexed resource symbols is determined according to the resource usage of the mobile terminal of the first communication node.

In one embodiment, the time domain resource configuration information includes one or more sub-time domain resource configuration information, which includes one or more of: multiplexing a resource cycle; multiplexing the resource offset; multiplexing a resource duration; and (4) multiplexing mode.

The multiplexing resource offset may represent a starting position of the multiplexing resource within the multiplexing period.

In one embodiment, the unit of the multiplexing resource offset or the multiplexing resource duration is one of: a subframe; a time slot; orthogonal frequency division multiplexing symbols.

In one embodiment, the multiplexing mode includes one or more of: frequency division multiplexing; and (4) space division multiplexing.

In one embodiment, the time domain resource configuration information configures the time domain resources by one of:

providing a set of first slot multiplexing resource combinations through first indication information, wherein each first slot multiplexing resource combination indicates the reusability of each slot in a plurality of continuous slots, each first slot multiplexing resource combination is identified through a different first combination index, the first combination index is indicated through second indication information, the first combination index indicated by the second indication information indicates the reusability of each slot in L1 continuous slots from the slot in which the second indication information is received, and L1 is the number of slots corresponding to the first slot multiplexing resource combination identified by the first combination index;

providing a set of second slot multiplexing resource combinations through third indication information, wherein each second slot multiplexing resource combination indicates the reusability of symbols in each of a plurality of consecutive slots, each second slot multiplexing resource combination is identified by a different second combination index, a second combination index is indicated through fourth indication information, the second combination index indicated by the fourth indication information is used for indicating the reusability of each of L2 consecutive slots starting from a slot in which the fourth indication information is received, and L2 is the number of slots corresponding to the second slot multiplexing resource combination identified by the second combination index;

the reusability of the corresponding slot resource is indicated by the reusability of the signal or the channel.

The first indication information and the third indication information may be Radio Resource Control (RRC) signaling or Medium Access Control Element (MAC CE). The second indication information and the fourth indication information may be Physical Downlink Control Channels (PDCCHs).

The terms "first" and "second" and the like in the present application are used only for distinguishing the corresponding contents. Illustratively, the first slot multiplexing resource combination and the second slot multiplexing resource combination are used only to distinguish different slot multiplexing resource combinations. The "plurality" of the plurality of consecutive time slots indicated by the first time slot multiplexing resource combination is not limited, and one skilled in the art can set at least one time slot for the first time slot multiplexing resource according to actual situations. The "plurality" of the plurality of slots indicated by the second slot multiplexing resource combination is also not limited.

The reusability of the time slot resources can be indicated through different types of signals or channels. All slot resources occupied as in the indicated signal may or may not be multiplexed.

In one embodiment, each multiplexing resource configuration information corresponds to one cell, one carrier, or at least one resource type.

In one embodiment, the frequency domain resource configuration information is used to indicate one of: frequency resources available to a mobile terminal of the first communication node; frequency resources available to the distributed elements of the first communication node.

In one embodiment, the time domain resource configuration information is used to indicate one of: a time domain resource reusable by a mobile terminal of the first communication node; time domain resources that are reusable by the distributed elements of the first communication node.

In an exemplary embodiment, the present application provides a resource allocation method, and fig. 2 is a flowchart illustrating the resource allocation method provided in the present application, where the method may be applied to a case of resource allocation. The method may be performed by a resource configuration arrangement as provided herein, which may be implemented by software and/or hardware and integrated on the second communication node. The second communication node may be a CU or DU or donor IAB or IAB node or any node supporting relay functionality. The above embodiments are not exhaustive, and are not repeated here.

As shown in fig. 2, a resource allocation method provided in the present application includes the following steps:

s210, determining at least one multiplexing resource configuration information, wherein the multiplexing resource configuration information is used for indicating the configuration of multiplexing resources.

This step may determine at least one multiplexing resource configuration information of the first communication node based on the desired multiplexing resource configuration information sent by the first communication node; at least one multiplexing resource configuration information of the first communication node may also be determined directly.

This step may determine multiplexing resource configuration information based on availability and reusability of the resource by the first communication node, as so limited.

In one embodiment, the second communication node may be a CU, and the multiplexing resource configuration information may include frequency domain resource attribute configuration information. The second communication node may also be a DU or a parent node of the first communication node, and the multiplexing resource configuration information may include frequency domain resource configuration information. The multiplexing resource configuration information may further include time domain resource configuration information.

For example, in the case of configuring the frequency domain resource attribute information, the content included in the frequency domain resource attribute information may be determined based on whether the sublink of the node corresponding to the frequency domain resource may use the frequency domain resource; the content included in the frequency domain resource attribute information may also be determined based on whether the child link and the parent link of the node corresponding to the frequency domain resource may share the frequency domain resource.

S220, sending the multiplexing resource configuration information.

After determining the multiplexing resource configuration information, this step may send the determined multiplexing resource configuration information to the first communication node, so that the first communication node determines the resource used for data transmission.

The resource allocation method provided by the application comprises the steps of firstly determining at least one piece of multiplexing resource allocation information, wherein the multiplexing resource allocation information is used for indicating the allocation of multiplexing resources; and then transmitting the multiplexing resource configuration information. The method effectively solves the problem of resource configuration and improves the resource utilization rate.

In one embodiment, the method further comprises: one or more of:

receiving expected multiplexing resource configuration information sent by a first communication node;

at least one multiplexing resource configuration information of a child node of the first communication node is determined and transmitted.

In one embodiment, determining multiplexing resource configuration information includes one or more of:

configuring the frequency domain resource attribute of the frequency domain resource which can be used by the sublink of the node corresponding to the frequency domain resource to be hard;

configuring the frequency domain resource attribute of the frequency domain resource which can be shared by the sublink and the parent link of the node corresponding to the frequency domain resource to be soft;

and configuring the frequency domain resource attribute of the frequency domain resource which cannot be used by the sublink of the node corresponding to the frequency domain resource to be unavailable.

In one embodiment, for frequency resources configured to be soft, availability is indicated by one of:

when the bit number of the bitmap is larger than the total number of soft frequency units contained in the bandwidth corresponding to the reference subcarrier interval, only the bit corresponding to the soft frequency unit in the bitmap is valid, and the rest bits are invalid; or a portion of a bitmap (e.g., the first X bits, where X is the total number of soft frequency units contained in the bandwidth corresponding to the reference subcarrier spacing) indicates the availability of each frequency unit of the soft frequency-domain resources.

the location of available frequency units;

indices of available frequency units.

The present application is described exemplarily below:

new Radio (NR) allows for more flexible networking than 2-Generation wireless telephone technology (2G), third Generation mobile communication technology (3rd-Generation, 3G), fourth Generation communication technology (4rd-Generation, 4G) systems and the existence of new types of network nodes. Currently, a new type of node, i.e., an IAB node, which integrates a backhaul link and a normal NR access link, can provide coverage and a networking mode more flexible than that of a single cellular coverage, and will be an important component in a future mobile communication network.

First embodiment, the CU in this example provides the properties of frequency domain hard, soft, and unavailable.

A first node, namely a first communication node, receives resource configuration information; the resource configuration information includes at least one of: a multiplexing resource configuration set of the first node, i.e. at least one multiplexing resource configuration information, a multiplexing resource configuration set of child nodes of the first node. Each multiplexing resource configuration corresponds to a cell, a carrier, or at least one resource type, and the multiplexing resource configuration includes at least one of the following: referring to the subcarrier spacing, the frequency domain resource attribute configuration (i.e., frequency domain resource attribute information), and the time domain resource configuration (i.e., time domain resource configuration information). The frequency domain resource attribute configuration is used for configuring the frequency domain resource attribute of each frequency unit.

The frequency domain resource attribute includes at least one of: hard, soft, unusable.

In one embodiment, when a frequency domain resource of a node is configured to be hard, then the frequency domain resource may be used by the sublinks of the node.

In one embodiment, when a frequency domain resource of a node is configured to be soft, then whether a sublink of the node can be explicitly or implicitly indicated by its parent node using the frequency domain resource.

In one embodiment, when a frequency domain resource of a node is configured to be unavailable, then the frequency domain resource may not be used by the sublink of the node.

The node may be the first node or a child node of the first node.

In one embodiment, the soft frequency domain resources may indicate their availability by: indicating whether each frequency unit of the soft frequency resource is available or not by using a bitmap, wherein each bit corresponds to one frequency unit, the size of the bitmap is the total number of the frequency units or the soft frequency units contained in the bandwidth corresponding to the reference subcarrier interval or is a fixed value, and the availability of the corresponding frequency units is represented by using a bit value; or, indicating the location of available frequency bins; or, a set of available frequency unit indices is indicated.

The frequency unit is any one of the following items: resource blocks, resource block groups, subbands, subband groups, subcarriers, subcarrier groups, frequency resource groups (e.g., the number of frequency resource groups is the bandwidth divided by m and rounded, or the maximum number of frequency resource groups is c, and the actual number is the minimum of bandwidths N and c, i.e., min { N, c }); wherein m or c is an integer of 1 or more.

In one embodiment, the validity of the frequency domain resource attribute configuration is one of: it is effective only when FDM multiplexing is adopted for the parent link and the child link; it is only effective when FDM and SDM are employed for the parent link and the child link; all multiplexing is available for the parent and child links.

In one embodiment, the time domain resource configuration includes at least one of: multiplexing resource period, multiplexing resource time slot set, multiplexing resource symbol in each multiplexing resource time slot and multiplexing mode indication.

In one embodiment, the time domain resource configuration comprises at least one sub-time domain resource configuration, wherein the sub-time domain resource configuration comprises at least one of: multiplexing resource period, multiplexing resource offset, multiplexing resource duration and multiplexing mode indication.

The multiplexing mode indication is used for indicating the multiplexing mode adopted by the multiplexing resource. Wherein the multiplexing mode comprises at least one of the following modes: FDM, SDM.

The second node, i.e. the second communication node, sends the resource configuration information. In this embodiment, the first node may be an IAB node and the second node may be a CU.

Example 1, this example shows a way to configure frequency domain resource attributes of an IAB node (i.e. IAB node) DU:

in this example, the frequency domain resource attribute of the IAB node DU is configured by the CU.

In one embodiment, a CU configures a frequency domain resource attribute for each carrier of each cell of an IAB node DU. For example, for a cell of an IAB node DU, it is assumed that the cell employs Time Division Duplex (TDD), a carrier is configured, and a CU configures a frequency domain resource attribute for the carrier. If the cell is also configured with a Supplemental Uplink (SUL) carrier, the CU also configures a frequency domain resource attribute for the SUL carrier. For another example, for a cell of an IAB node DU, it is assumed that the cell employs Frequency Division Duplex (FDD), and a CU configures Frequency domain resource attributes for an UL carrier and a DL carrier of the cell respectively.

In one embodiment, a CU configures a frequency domain resource attribute for each carrier, for example, if an IAB node DU configures one carrier, then configures one frequency domain resource attribute for the carrier, all cells using the carrier have the same frequency domain resource attribute, and if the IAB node DU configures multiple carriers, then configures one frequency domain resource attribute for each carrier.

In one embodiment, a CU configures a frequency domain resource attribute per time resource type for each carrier. For example, different time resource types (i.e., resource types, such as uplink, downlink, and flexible) correspond to different frequency domain resource attributes, and for one TDD carrier, the frequency domain resource attributes are respectively configured for downlink resources, uplink resources, and flexible resources; or configuring a frequency domain resource attribute for the downlink resource and the flexible resource, and configuring a frequency domain resource attribute for the uplink resource; or configuring a frequency domain resource attribute for the uplink resource and the flexible resource and configuring a frequency domain resource attribute for the downlink resource.

For a carrier of an IAB node DU, the bandwidth corresponding to the reference subcarrier spacing is N Resource Blocks (RBs), and the frequency domain Resource attribute of the carrier may be configured as follows: for a frequency bin, its properties may be one of: hard, soft, unusable. Wherein, the frequency unit includes but is not limited to any one of the following items: resource Block, Resource Block Group (RBG), subband Group, subcarrier Group, frequency Resource Group.

When the frequency domain resources are configured to be hard, then the IAB node DU (or a sublink of the IAB node) may use the frequency domain resources.

When the frequency domain resource is configured to be soft, then whether an IAB node DU (or a sublink of the IAB node) can be explicitly or implicitly indicated by its parent node using the frequency domain resource.

When a frequency domain resource is configured to be unavailable, then the IAB node DU (or a sublink of the IAB node) cannot use the frequency domain resource.

Fig. 2a is a schematic diagram of a time-frequency domain resource attribute configuration of a frequency unit that is an RB provided by the present application, and fig. 2b is a schematic diagram of a time-frequency domain resource attribute configuration of a frequency unit that is an RBG provided by the present application. Fig. 2a shows the frequency domain resource allocation when the frequency unit is RB. Fig. 2b shows the frequency domain resource allocation when the frequency unit is RBG. Assuming that the RBG size is k RBs, the total number of RBGs is ceil (N/k), where ceil () represents a rounding-up. If N/k is an integer, all RBG sizes are k RBs; if N/k is not an integer, the last or first RBG is N mod k RBs, and the remaining RBGs are k, where mod represents the modulo operation, e.g., the last RBG in FIG. 2b contains 3 RBs.

When the frequency unit is a sub-band, the number and size of the sub-band are determined in a manner similar to that of the RBG, and the RBG is replaced by the sub-band.

When the frequency unit is a subband group, the number and size of the subband group are determined in a manner similar to that of the RBG, and the RB/RBG is replaced by the subband/subband group.

The schematic diagrams of the time-frequency domain resource attribute configuration with the frequency unit being the subcarrier and the subcarrier group are respectively similar to fig. 1-1 and fig. 1-2, and the RB/RBG is replaced by the subcarrier/subcarrier group, the total number of subcarriers is 12N, and the calculation methods of the number and the size of the subcarrier group are also similar.

In one embodiment, the CU provides one of: RBG size, subband size, m.

In one embodiment, the number of frequency resource groups is ceil (N/m), where m is an integer greater than or equal to 1, if N/m is an integer, each frequency resource group has a size of m RBs, if N/m is not an integer, one of the frequency resource groups (e.g., the last or first frequency resource group) has a size of N mod m RBs, and the remaining frequency resource groups have sizes of m RBs.

In one embodiment, the maximum number of frequency resource groups is c. The number of the actual frequency resource groups is the minimum value x of the bandwidth N and the maximum number c of the frequency resource groups, i.e. x ═ min { N, c }, if x ═ N, the frequency resource groups are resource blocks RB, if x ═ c and N/x are integers, each frequency resource group size is N/x RBs, if x ═ c and N/x are not integers, the size of N mod x frequency resource groups is ceil (N/x) RBs, and the size of the rest frequency resource groups is floor (N/x) RBs. Where ceil () and floor () represent rounded up and rounded down, respectively.

The methods for determining the size and number of frequency units in the following examples are also similar and will not be described in detail.

Wherein, the reference subcarrier spacing is configured by the CU, or determined by default.

For example, the default may be: the maximum subcarrier interval in a plurality of subcarrier intervals corresponding to the carrier is used as a reference subcarrier interval; or, the minimum subcarrier interval among a plurality of subcarrier intervals corresponding to the carriers is used as a reference subcarrier interval; or, determining the reference subcarrier spacing according to the frequency range of the carrier, for example, different frequency ranges correspond to different reference subcarrier spacings, the carrier belongs to the frequency range 1(FR1), and the reference subcarrier spacing is 60 kHz; the carrier belongs to frequency range 2 and the reference subcarrier spacing is 120 kHz.

In one embodiment, the frequency domain resource attribute configuration of the IAB node is only effective when FDM multiplexing is adopted for the sub-link and the parent link of the IAB node.

In one embodiment, the frequency domain resource attribute configuration of the IAB node is effective for both the child link and the parent link of the IAB node to adopt FDM and SDM multiplexing.

In one embodiment, if the cell-level (i.e., cell-specific) Signal or Channel of the IAB node is, for example, a Synchronization Signal Block (SSB), a Physical Random Access Channel (PRACH), an SIB1 in a System Information Block (SIB), etc. On a frequency bin, the frequency bin can be considered a hard frequency bin.

Example 2, this example shows a manner of indicating the availability of soft frequency domain resources of an IAB node DU, where the availability of soft frequency domain resources of an IAB node DU cell is indicated by a parent node of the IAB node (or a serving cell of the IAB node MT). The indication mode is one of the following modes:

mode 1: all frequency domain resources configured to be soft are numbered according to frequency units, for example, according to the ascending order or descending order of frequency, and the availability of each frequency unit is indicated in a bitmap (i.e., bitmap) manner, where the size of bitmap is the total number of soft frequency units contained in the bandwidth corresponding to the reference subcarrier interval.

Fig. 2c is a schematic diagram of soft frequency resource RBG number and bitmap indication of soft frequency resource availability when a frequency unit is an RBG according to the present application, where, referring to fig. 2c, a bit value of 1 indicates that a corresponding soft frequency unit is available, a bit value of 0 indicates that the corresponding soft frequency unit is unavailable, M is the total number of RBGs, and X is the total number of soft RBGs.

Mode 2: the availability of each frequency unit is indicated in a bitmap mode by numbering the bandwidths corresponding to the reference subcarrier intervals according to the frequency units, for example, numbering the bandwidths according to the ascending order or the descending order of the frequency, the size of the bitmap is the total number of the frequency units contained in the bandwidths corresponding to the reference subcarrier intervals, and the availability of the corresponding frequency units is represented by bit values. In one embodiment, the bitmap is valid only for soft frequency resources and not for other resources.

Mode 3: numbering the bandwidths corresponding to the reference subcarrier intervals according to frequency units, for example, numbering according to an ascending order or a descending order of frequency, indicating available frequency unit indexes, and making the soft frequency units which are not indicated unavailable; or indicating an unavailable frequency element index and soft frequency elements not indicated as available.

Mode 4: the bandwidth corresponding to the reference subcarrier spacing is numbered in frequency units, for example, in ascending or descending frequency order, to indicate available frequency unit indexes, and the availability of soft frequency units which are not indicated is determined according to the usage of the IAB node MT. For example, an IAB node DU may be determined based on whether the frequency unit is in conflict with an IAB node MT. If not, it is available, otherwise it is not available. Or indicating an unavailable frequency element index, the availability of the soft frequency element not indicated is determined according to the usage of the IAB node MT.

Mode 5: the availability of X soft frequency units is indicated by X bits (e.g., least significant X bits, or most significant X bits) in the bitmap. The size of the bitmap is the total number of frequency units included in the bandwidth corresponding to the reference subcarrier interval, or is a fixed value (e.g., 275), or has a corresponding relationship with the bandwidth corresponding to the reference subcarrier interval, and X is the total number of soft frequency units included in the bandwidth corresponding to the reference subcarrier interval, or the total number of frequency units included in the bandwidth corresponding to the reference subcarrier interval.

Mode 6: indicating the location of available frequency bins. For example, the number of start frequency units and frequency units available to the IAB node DU is indicated by a Resource Indication Value (RIV) within a bandwidth corresponding to the reference subcarrier spacing, or the start frequency units and end frequency units available to the IAB node DU are indicated (i.e., the start frequency units and end frequency units and all soft frequency units therebetween are available). In one embodiment, the indication is valid only for soft frequency resources and not for other resources.

Mode 7: indicating the location of available frequency bins. For example, all frequency domain resources configured to be soft are numbered in frequency units, and the starting frequency unit and the number of frequency units available to the IAB node DU are indicated by a resource indication value, or the starting frequency unit and the ending frequency unit available to the IAB node DU are indicated (i.e., the starting frequency unit and the ending frequency unit and all soft frequency units therebetween are available).

In one embodiment, the availability of soft frequency cells is indicated by different bit values. For example, a bit value of 1 indicates available and a bit value of 0 indicates unavailable.

In one embodiment, the availability of soft frequency cells is indicated by different bit values. For example, a bit value of 1 indicates availability, and a bit value of 0 indicates availability of the frequency unit may be determined according to usage of the IAB node MT, e.g., an IAB node DU is determined according to whether the frequency unit is in conflict with the IAB node MT when the frequency unit is used, and if not, the frequency unit is available, otherwise the frequency unit is not available.

Wherein, the frequency unit includes but is not limited to one of the following: RB, RBG, subband group, subcarrier group, frequency resource group (e.g., the number of frequency resource groups is the bandwidth divided by m and rounded, or the maximum number of frequency resource groups is c, the actual number is the minimum of bandwidths N and c, i.e., min { N, c }).

In one embodiment, the CU provides one of: RBG size, subband size, m, c.

Example 3, this example shows a semi-static, time domain resource configuration per slot and per symbol:

this example gives a way to configure the time domain resources of an IAB node DU.

The CU provides time domain resource configuration for each cell or each carrier or at least one time resource type of the IAB node DU.

In one embodiment, a CU provides a time domain resource configuration for each cell of an IAB node DU, e.g., all carriers of a cell use the same time domain resource configuration.

In one embodiment, the CU provides a time domain resource configuration for each carrier of each cell of the IAB node DU, for example, for one cell of the IAB node DU, assuming that the cell employs time division duplexing, one carrier is configured, and the CU provides the time domain resource configuration for the carrier. For another example, assuming that the cell employs frequency division duplexing, a CU provides time domain resource allocation for the UL carrier and the DL carrier of the cell, respectively.

In one embodiment, a CU provides a time domain resource configuration for each carrier. For example, if an IAB node DU configures one carrier, a time domain resource configuration is provided for the carrier, all cells using the carrier have the same time domain resource configuration, and if the IAB node DU configures multiple carriers, a time domain resource configuration is provided for each carrier.

In one embodiment, a CU provides a time domain resource configuration per time resource type for each carrier. For example, different time resource types correspond to different time domain resource configurations. For a TDD carrier, respectively providing time domain resource allocation for downlink resources, uplink resources and flexible resources; or providing a time domain resource configuration for the downlink resource and the flexible resource and providing a time domain resource configuration for the uplink resource; or providing a time domain resource configuration for the uplink resource and the flexible resource and providing a time domain resource configuration for the downlink resource.

Wherein, the time domain resource configuration comprises at least one of the following: multiplexing resource period, multiplexing resource time slot set, multiplexing resource symbol and multiplexing mode indication.

The set of multiplexing resource slots may be configured by any of the following:

mode 1: the slot set is indicated in a bitmap (bitmap) manner. One bit corresponds to one time slot in the multiplexing resource cycle, and the bit value is used for indicating whether the corresponding time slot is the multiplexing resource, for example, if the bit value is 1, the time slot is the multiplexing resource, otherwise, the time slot is not the multiplexing resource;

mode 2: an index set indicating a reusable slot within a multiplexing resource period.

Mode 3: indicating the index of the start slot that can be multiplexed within the period of multiplexing resources and the number of slots that can be multiplexed.

Mode 4: indicating the start slot index and the end slot index that are multiplexed within the multiplexing resource period (i.e., the slots corresponding to the start slot index and the end slot index and all slot indices therebetween are available).

In one embodiment, the set of multiplexing resource slots is valid only for the corresponding type of time resource, e.g. for the time domain resource configuration provided for the downlink resource and the flexible resource, only for the downlink resource and the flexible resource, i.e. for the uplink resource, the available slots indicated by the set of multiplexing resource slots configuration are ignored.

The multiplexing resource symbol configuration may provide reusability of symbols in a multiplexing slot in a multiplexing resource slot set, and may also provide reusability of symbols in a multiplexing resource period, where the multiplexing resource symbol may be configured in any one of the following manners:

mode 1: a reusable symbol is separately configured for each slot. For example, indicating reusability of a symbol in a slot according to the resource type of the symbol configures any one of a specific set of configurations:

mode 2: and the reusable symbols are uniformly configured for all time slots. For example, the reusability of a symbol can be indicated for any one of a particular set of configurations based on the resource type of the symbol.

The resource types include: uplink (UL), Downlink (DL), and Flexible (F).

The specific configuration set is composed of at least one of the following configurations: all symbols (i.e., All symbols) may be multiplexed, Only downlink symbols (i.e., Only DL symbols) may be multiplexed, Only uplink symbols (i.e., Only UL symbols) may be multiplexed, Only flexible symbols (i.e., Only flexible symbols) may be multiplexed, Only downlink and flexible symbols (i.e., Only DL and flexible symbols) may be multiplexed, Only uplink and flexible symbols (i.e., Only UL and flexible symbols) may be multiplexed, Only downlink and uplink symbols (i.e., Only DL and flexible symbols) may be multiplexed, and All symbols (i.e., All symbols) may not be multiplexed.

In one embodiment, symbols that are not indicated as being reusable for a particular configuration set are not reusable.

In one embodiment, symbols that are not indicated as reusable for a particular configuration set are determined whether or not reusable based on resource usage by the IAB node MT.

Each configuration in a specific configuration set corresponds to an index, and the index is indicated to indicate which resource type symbol is a reusable symbol.

In one embodiment, for providing the time domain resource configuration by time resource type, it is not necessary to provide a multiplexed resource symbol configuration.

The multiplexing mode indication is used for indicating the multiplexing mode adopted by the multiplexing resource. Wherein, the multiplexing mode comprises at least one of the following modes: FDM, SDM.

The time domain resource configuration is used for configuring time domain resources which can potentially be sent or received simultaneously when the sub-link and the parent link of the IAB node adopt an FDM or SDM mode.

Example 4, this example shows a semi-static, time domain resource configuration of period + offset (i.e., offset) + duration (i.e., duration):

In one embodiment, a CU provides a time domain resource configuration for each carrier of each cell of an IAB node DU.

In one embodiment, a CU provides a time domain resource configuration for each carrier.

In one embodiment, a CU provides a time domain resource configuration for each carrier according to a time resource type, for example, different time resource types correspond to different time domain resource configurations.

The specific example of the above-mentioned options is similar to example 3 in embodiment one, and is not described here again.

In one embodiment, the time domain resource configuration comprises at least one sub-time domain resource configuration.

Wherein, the sub-time domain resource configuration comprises at least one of the following: multiplexing resource period, multiplexing resource offset, multiplexing resource duration and multiplexing mode indication.

In one embodiment, the multiplexing resource offset represents a starting position of the multiplexing resource within the multiplexing resource period;

in one embodiment, the unit of the multiplexing resource offset is any one of: a subframe, a slot, an Orthogonal Frequency Division Multiplexing (OFDM) symbol.

In one embodiment, the unit of the reuse resource duration is any one of: subframe, slot, OFDM symbol.

In one embodiment, for each cell or carrier or resource type of an IAB node DU, the reuse resource is a union of the resources provided by all the sub-time domain resource configurations of the cell.

For example, according to the sub-time domain resource configuration parameter, the wireless frame n where the resource is located is multiplexed_fAnd a starting time slot

Satisfy the requirement of

Wherein

The number of slots per radio frame when configured to μ for the subcarrier spacing,

configuring the time slot number, o, in a muTime radio frame for a subcarrier spacing_sFor multiplexing resource offsets, k_sIs the reuse resource period. That is, the multiplexing resource is a radio frame n_fTo Chinese

Successive T's as starting time slots_sAnd a time slot. T is_sIs multiplexing the resource duration.

In this example, the unit of the multiplexing resource period and the multiplexing resource offset is a time slot when the subcarrier spacing is configured as μ, and if the unit is not a time slot, the unit can be converted into a time slot when the subcarrier spacing is configured as μ.

In the above example, the unit of multiplexing resource offset is a time slot, and similar formulas can be used for other units, and the unit of configuring each parameter for the sub-time domain resource is converted into a uniform unit, and the number of time slots of each radio frame is

And also into uniform units.

In the second embodiment, the parent node in this embodiment provides the resource configuration to the IAB node, and the parent node in this embodiment is the third node.

The father node of the IAB node provides multiplexing resource configuration for the IAB node MT or DU:

in the frequency domain: 1) indicated with a bitmap within a transmission Bandwidth or Bandwidth Part (BWP); 2) Indicated by RIV within the transmission bandwidth or BWP.

In the time domain, the reusable resource configuration may adopt: slot granularity, slot + symbol granularity, or configured by signal or channel type.

The first node receives at least one multiplexing resource configuration; the multiplexing resource is configured to be at least one of: reference subcarrier spacing, frequency domain resource allocation and time domain resource allocation.

In one embodiment, the frequency domain resource configuration may indicate available frequency resources by: indicating available frequency units by using a bitmap (bitmap), wherein each bit corresponds to one frequency unit, the size of the bitmap is the total number of the frequency units contained in the bandwidth corresponding to the reference subcarrier interval, and the availability of the corresponding frequency units is represented by using a bit value; or, a set of frequency unit indices available in the frequency resource is indicated.

The frequency unit is any one of the following items: resource block, resource block group, sub-band group, sub-carrier group, and frequency resource with bandwidth/m as one group; wherein m is an integer greater than or equal to 1;

the frequency domain resource configuration is for one of: indicating frequency resources available to the MT of the first node; or, indicating frequency resources available to the DU of the first node;

the time domain resource configuration is for one of: indicating a time domain resource that the MT of the first node can multiplex; or indicating a time domain resource that the DU of the first node can reuse;

the at least one multiplexing resource configuration may be transmitted through RRC signaling or MAC CE.

Example 1, this example indicates the frequency resources available to the IAB node MT:

in one embodiment, the serving cell of the IAB node MT (or the parent node of the IAB node) provides a frequency domain resource configuration for each carrier of the IAB node MT.

In one embodiment, the serving cell of the IAB node MT provides a frequency domain resource configuration per time resource type for each carrier. For example, different time resource types correspond to different frequency domain resource configurations. The specific example is similar to example 1 in embodiment one, and is not described again here.

Wherein, the frequency domain resource configuration is used for indicating the frequency resources available for the IAB node MT.

The serving cell of the IAB node MT (or the parent node of the IAB node) indicates the frequency resources available to the IAB node MT by one of the following:

mode 1: the available frequency units are indicated by a bitmap (bitmap), wherein each bit corresponds to one frequency unit, the size of the bitmap is the bandwidth corresponding to the reference subcarrier interval or the total number of frequency units contained in the BWP, and the availability of the corresponding frequency units is indicated by a bit value, for example, a bit value of 1 indicates that the corresponding frequency units are available, and a bit value of 0 indicates that the corresponding frequency units are not available.

Mode 2: indicating the frequency unit locations available for IAB node MT. For example, a bandwidth corresponding to a reference subcarrier spacing or a starting frequency unit and a frequency unit number available for the IABnode MT within the BWP are indicated, e.g., by a resource indication value; or indicate the start frequency unit and the end frequency unit available to the IAB node MT.

Mode 3: indicating a set of available frequency unit indices within a bandwidth corresponding to the reference subcarrier spacing.

Mode 4: the availability of frequency bins is indicated by X bits (e.g., least significant X bits, or most significant X bits) in the bitmap correspondence. Wherein, the size of bitmap is a fixed value, X is the total number of frequency units included in the Bandwidth corresponding to the reference subcarrier interval, or the total number of frequency units included in the Bandwidth Part (BWP) corresponding to the reference subcarrier interval.

Wherein the fixed value can be predefined or has a corresponding relation with the bandwidth corresponding to the reference subcarrier interval.

Wherein, the frequency unit includes but is not limited to one of the following: RB, RBG, subband group, subcarrier group, bandwidth/m is a frequency resource of a group; wherein m is an integer of 1 or more.

In one embodiment, the parent node provides one of: RBG size, subband size, m.

In one embodiment, the configuration related to the frequency resources with a set bandwidth/m is similar to the above example, and is not described here again.

In one embodiment, the reference subcarrier spacing is configured by the parent node, or determined by default.

The default mode is the same as the default mode for determining the subcarrier spacing in example 1 of the first embodiment, and is not described here again.

Example 2, this example indicates the frequency resources available for an IAB node DU:

in one embodiment, the serving cell of the IAB node MT (or the parent node of the IAB node) provides the frequency domain resource configuration for each carrier of the IAB node du.

In one embodiment, a frequency domain resource configuration is provided for each carrier of each cell of an IAB node DU.

In one embodiment, a frequency domain resource configuration is provided for each carrier of an IAB node DU.

In one embodiment, the frequency domain resource configuration is provided per time resource type for each carrier of the IAB node DU.

Wherein, the frequency domain resource configuration is used for indicating the frequency resources available for the IAB node DU.

The specific examples of the above options are similar to example 1 in embodiment one, and are not described here again.

The available frequency resources are configured in a similar manner to the frequency resources available for indicating the IAB node MT, and are not described herein again.

Example 3, this example shows a dynamic time domain resource configuration:

the serving cell of the IAB node MT (or the parent node of the IAB node) provides the IAB node MT with a time domain resource configuration.

In one embodiment, the IAB node MT is provided with a time domain resource configuration for each serving cell.

In one embodiment, the IAB node MT is provided with a time domain resource configuration for each carrier of each serving cell.

In one embodiment, for each carrier, the IAB node MT is provided with a time domain resource configuration in terms of time resource type. For example, for one TDD carrier, time domain resource configurations are provided for downlink resources, uplink resources, and flexible resources, respectively; or a time domain resource configuration is provided for the downlink resource and the flexible resource, and a time domain resource configuration is provided for the uplink resource; or a time domain resource configuration is provided for the uplink resource and the flexible resource, and a time domain resource configuration is provided for the downlink resource.

The time domain resource configuration mode is any one of the following modes:

mode 1 (slot granularity): a set of time domain multiplexing resource combinations is provided by RRC signaling or MAC CE, wherein each combination is used for indicating whether each time slot in a plurality of continuous time slots is reusable or not, and each combination is uniquely identified by a combination index. The combination index is indicated by the PDCCH, and the combination index in the PDCCH indicates whether each of a plurality of consecutive slots is reusable from the slot in which the PDCCH is received by the IAB node MT.

Mode 2 (slot + symbol granularity): a set of time domain multiplexing resource combinations is provided by RRC signaling or MAC CE, wherein each combination is used for indicating the reusability of symbols in each of a plurality of continuous time slots, and each combination is uniquely identified by a combination index. The combination index is indicated by the PDCCH, and indicates the reusability of symbols in each of a plurality of consecutive slots from the slot in which the PDCCH is received from the IAB node MT. Wherein the reusability of the symbols in each slot is any one configuration in a specific configuration set.

The specific configuration set is composed of at least one of the following configurations: all symbols are reusable, only downlink symbols are reusable, only uplink symbols are reusable, only null symbols are reusable, only downlink and flexible symbols are reusable, only uplink and flexible symbols are reusable, only downlink and uplink symbols are reusable, and all symbols are not reusable.

In one embodiment, for each configuration of a particular set of configurations, the symbols that are not indicated are not reusable.

In one embodiment, for each configuration of a particular set of configurations, the non-indicated symbol determines whether it is reusable based on the resource usage of the IABnode MT.

Mode 3: indicating whether different types of signals or channels are reusable, respectively, e.g., using RRC signaling or MAC CE to indicate a set of reusable signals or channels. In an embodiment, for a Physical Downlink Shared Channel (PDSCH)/Physical Uplink Shared Channel (PUSCH) scheduled by a PDCCH, 1bit in a Downlink Control Information (DCI) indicates whether a resource corresponding to the PDSCH/PUSCH can be multiplexed with a sub-link of an IAB node. In one embodiment, the configuration may override the configuration provided by RRC signaling or MAC CE.

Example 4, this example shows a dynamic time domain resource configuration:

the IAB node DU assumes that all time domain resources are reusable resources except for the configured time domain unavailable resources.

Example 5, this example shows a semi-static time domain resource configuration:

the parent node of the IAB node may also provide time domain resource configuration for the IAB node MT by using methods similar to those in examples 3 and 4 in embodiment one, and replace the CU with the parent node of the IAB node and replace the IAB node DU with the IAB node MT, which is not described herein again.

Example 6, this example shows a time domain resource configuration:

the parent node of the IAB node provides at least one time domain resource configuration for the IAB node DU, where the time domain resource configuration is used to indicate a time domain resource that the IAB node DU can reuse, that is, the time domain resource configuration is provided for each cell of the IAB node DU or each carrier of each cell or each carrier or at least one type of time resource, that is, the time domain resource that can be used for the parent link and the child link of the IAB node to transmit or receive simultaneously is provided.

The indication manner is similar to that of examples 3 and 5 of the second embodiment, and is not described here again, and the differences are only: examples 3 and 5 are indicated by serving cell or carrier of the IAB node MT, i.e. time domain resources for indicating that one serving cell or carrier of the IAB node MT is transmitted or received simultaneously with one or more cells of the IAB node DU; and example 6 is indicated by the cell or carrier of the IAB node DU, i.e. the time domain resources used to indicate that one cell or carrier of the IAB node DU is transmitting or receiving simultaneously with one or more serving cells of the IAB node MT.

In a third embodiment, this embodiment shows that the IAB node reports resource configuration to the parent node:

the first node reports the resource configuration information; the resource allocation information provides a multiplexing resource allocation of each cell or carrier of the first node or at least one time resource type, where the multiplexing resource allocation includes at least one of: reference subcarrier spacing, frequency domain resource allocation and time domain resource allocation.

In one embodiment, the frequency domain resource configuration may indicate available frequency resources by: indicating available frequency units by using a bitmap (bitmap), wherein each bit corresponds to one frequency unit, the size of the bitmap is the total number of the frequency units contained in the bandwidth corresponding to the reference subcarrier interval, and the availability of the corresponding frequency units is represented by using a bit value; or, the location of the available frequency units is indicated, or, the set of available frequency unit indices within the bandwidth corresponding to the reference subcarrier spacing is indicated.

The frequency unit is any one of the following items: resource block, resource block group, sub-band group, sub-carrier group, and frequency resource with bandwidth/m as one group; wherein m is an integer of 1 or more.

The time domain resource configuration is for one of: indicating a time domain resource that each cell or carrier of the first node can reuse;

the multiplexing resource configuration may be transmitted through RRC signaling or MAC CE.

Example 1, this example indicates the frequency resources available for an IAB node DU:

and the frequency domain resource of the IAB node DU is reported by the IAB node and is configured to a father node of the IAB node (or a service cell of the IAB node MT).

In one embodiment, the frequency domain resource configuration of each carrier of each cell of the IAB node DU is reported.

In one embodiment, the frequency domain resource configuration of each carrier of the IAB node DU is reported.

In one embodiment, for each carrier, the frequency domain resource configuration of the IAB node DU is reported according to the time resource type.

In one embodiment, the frequency domain resource configuration indicates the frequency resources available for the IAB node DU.

The IAB node indicates the frequency domain resource configuration by one of the following ways:

mode 1: the available frequency units are indicated by a bitmap (bitmap), wherein each bit corresponds to one frequency unit, the size of the bitmap is the total number of frequency units contained in the bandwidth corresponding to the reference subcarrier interval, the availability of the corresponding frequency units is indicated by a bit value, for example, a bit value of 1 indicates that the corresponding frequency units are available, and a bit value of 0 indicates that the corresponding frequency units are unavailable.

Mode 2: indicating the available frequency cell locations. For example, a starting frequency unit and a frequency unit number available for the IABnode DU within a bandwidth corresponding to the reference subcarrier spacing are indicated, e.g., by a resource indication value; or indicate available start frequency units and end frequency units.

Mode 3: indicating a set of frequency unit indices available within a bandwidth corresponding to the reference subcarrier spacing.

Mode 4: the availability of frequency bins is indicated by X bits (e.g., least significant X bits, or most significant X bits) in the bitmap correspondence. The size of bitmap is a fixed value, and X is the total number of frequency units included in the bandwidth corresponding to the reference subcarrier interval.

In one embodiment, the IAB node reports one of the following: RBG size, subband size, m.

Example 2, this example shows a semi-static time domain resource configuration:

and the IAB node reports the time domain resource of the IAB node DU to a father node (or a service cell of the IAB node MT) of the IAB node.

In one embodiment, the IAB node DU reports the time domain resource configuration of each carrier of each cell. For example, assuming that a cell employs time division duplex and a carrier is configured, the time domain resource configuration of the carrier is reported. For another example, assuming that the cell employs frequency division duplex, the time domain resource configuration of the UL carrier and the DL carrier of the cell is reported.

In one embodiment, the IAB node DU reports the time domain resource configuration of each carrier, for example, if the IAB node DU configures one carrier, the time domain resource configuration of the carrier is reported, and all cells using the carrier have the same time domain resource configuration. And if the IAB node DU is configured with a plurality of carriers, reporting the time domain resource configuration of each carrier.

In one embodiment, the IAB node DU reports the time domain resource configuration for each carrier according to the time resource type. For example, different time resource types correspond to different time domain resource configurations.

The time domain resource configuration is similar to examples 3 and 4 in the first embodiment, and is not described again here.

In one embodiment, in all the embodiments and examples described above, for each cell of an IAB node DU, the time domain resource provided by the time domain resource configuration is a potentially reusable resource, that is, for each cell of the IAB node DU, whether the configured time domain resource can be used for simultaneous transmission or simultaneous reception of a child link and a parent link, depending on the transmission directions of the child link and the parent link, which are different in the transmission directions on the time resource (for example, one is uplink and the other is downlink), the IAB node may transmit or receive simultaneously on the child link and the parent link, and if the transmission directions of the child link and the parent link are the same (for example, both are uplink or both are downlink), the half-duplex IAB node cannot transmit or receive simultaneously on the child link and the parent link. For example, for a sublink and a parent link, the time resource is an uplink resource and a downlink resource, respectively, and the IAB node may receive the time resource on the sublink and the parent link at the same time; for another example, for the child link and the parent link, the time resource is a downlink resource and an uplink resource, respectively, and the IAB node may transmit on the child link and the parent link at the same time.

In one embodiment, in all of the above embodiments and examples, the second node (e.g. CU) or the third node (e.g. parent node of the IAB node) needs to know the frequency location of the bandwidth corresponding to the reference subcarrier spacing of the IAB node. That is, the IAB node reports a start Frequency or a termination Frequency or a center Frequency of a bandwidth corresponding to the reference subcarrier interval (for example, the start Frequency or the termination Frequency or the center Frequency may be indicated in any manner of reporting a Frequency difference with the point a, or reporting an Absolute Radio Frequency Channel Number (ARFCN) to at least one of the second node and the third node. Where point a is a common reference point of the resource grid.

In one embodiment, in all embodiments and examples described above, the frequency domain resource configuration and the time domain resource configuration may employ different reference subcarrier spacings. For example, the frequency domain resource configuration employs a reference subcarrier spacing of 1, and the time domain resource configuration employs a reference subcarrier spacing of 2.

In one embodiment, a CU or a parent node provides a first reference subcarrier spacing employed by a frequency domain resource attribute configuration or a frequency domain resource configuration;

in one embodiment, the CU or the parent node provides a second reference subcarrier spacing employed by the time domain resource configuration;

in one embodiment, the IAB node reports a third reference subcarrier interval adopted by the frequency domain resource configuration;

in one embodiment, the IAB node reports a fourth reference subcarrier interval used for time domain resource configuration.

The reference subcarrier spacing includes one or more of: a first reference subcarrier spacing; a second reference subcarrier spacing; a third reference subcarrier spacing; a fourth reference subcarrier spacing.

In one embodiment, in all the embodiments and examples described above, the time domain resource configuration is Not valid for the time domain unavailable resource (i.e. Not Available (NA) resource) of the first node.

In one embodiment, in all the above embodiments and examples, the default multiplexing resource can be used for FDM and SDM if no multiplexing mode indication is provided.

In an exemplary embodiment, the present application provides a resource allocation apparatus, and fig. 3 is a schematic structural diagram of a resource allocation apparatus provided in the present application, the apparatus is configured at a first communication node, as shown in fig. 3, the apparatus includes: an obtaining module 31, configured to obtain at least one multiplexing resource configuration information, where the multiplexing resource configuration information is used to indicate a configuration of multiplexing resources; and the transmission module 32 is configured to transmit data based on the multiplexing resource configuration information.

The resource configuration apparatus provided in this embodiment is used to implement the resource configuration method in the embodiment shown in fig. 1, and the implementation principle and technical effect of the resource configuration apparatus provided in this embodiment are similar to those of the resource configuration method in the embodiment shown in fig. 1, and are not described here again.

In one embodiment, the apparatus further comprises a communication module configured to one or more of:

reporting expected multiplexing resource configuration information;

the location of available frequency units;

indices of available frequency units.

In one embodiment, symbols not included in the multiplexed resource symbols are not multiplexed; or the reusability of symbols not included in the multiplexed resource symbols is determined according to the usage of the mobile terminal resources of the first communication node.

In an exemplary embodiment, the present application provides a resource allocation apparatus, and fig. 4 is a schematic structural diagram of a resource allocation apparatus provided in the present application, the apparatus being configured at a second communication node, and the apparatus including: a determining module 41 configured to determine at least one multiplexing resource configuration information, where the multiplexing resource configuration information is used to indicate a configuration of multiplexing resources; a sending module 42, configured to send the multiplexing resource configuration information.

The resource configuration apparatus provided in this embodiment is used to implement the resource configuration method in the embodiment shown in fig. 2, and the implementation principle and technical effect of the resource configuration apparatus provided in this embodiment are similar to those of the resource configuration method in the embodiment shown in fig. 2, and are not described here again.

In one embodiment, the apparatus further comprises a transmission module configured to: including one or more of:

In one embodiment, the determination module 41 is configured to: including one or more of:

the location of available frequency units;

indices of available frequency units.

In an exemplary implementation manner, an embodiment of the present application further provides a communication node, and fig. 5 is a schematic structural diagram of a communication node provided in the present application. As shown in fig. 5, the communication node provided by the present application includes one or more processors 51 and a storage device 52; the processor 51 in the communication node may be one or more, and fig. 5 illustrates one processor 51 as an example; storage 52 is used to store one or more programs; the one or more programs are executed by the one or more processors 51, so that the one or more processors 51 implement the resource configuration method as described in the embodiment of the present application.

In the case where the communication node is a first communication node, the one or more processors 51 implement the resource allocation method as described in fig. 1 herein. In the case where the communication node is a second communication node, the one or more processors 51 implement the resource allocation method as described in fig. 2 herein.

The communication node further comprises: a communication device 53, an input device 54 and an output device 55.

The processor 51, the storage means 52, the communication means 53, the input means 54 and the output means 55 in the communication node may be connected by a bus or other means, which is exemplified in fig. 5.

The input device 54 may be used to receive entered numeric or character information and to generate key signal inputs relating to user settings and function control of the communication node. The output device 55 may include a display device such as a display screen.

The communication means 53 may comprise a receiver and a transmitter. The communication device 53 is configured to perform information transceiving communication according to the control of the processor 51. The information includes, but is not limited to, multiplexing resource configuration information.

The storage device 52, which is a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the resource configuration method shown in fig. 1 (for example, the obtaining module 31 and the transmitting module 32 in the resource configuration device); also shown in fig. 2 of the present application are program instructions/modules (e.g., the determining module 41 and the sending module 42 in the resource configuration apparatus) corresponding to the resource configuration method. The storage device 52 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the communication node, and the like. Further, the storage 52 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the storage 52 may further include memory located remotely from the processor 51, which may be connected to the communication node over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The embodiment of the present application further provides a storage medium, where a computer program is stored, and when the computer program is executed by a processor, the resource configuration method described in any one of the embodiments of the present application is implemented. As applied to a resource configuration method of a first communication node and a resource configuration method of a second communication node, wherein the method applied to the first communication node comprises: acquiring at least one multiplexing resource configuration information, wherein the multiplexing resource configuration information is used for indicating the configuration of multiplexing resources;

The resource allocation method applied to the second communication node comprises the following steps: determining at least one multiplexing resource configuration information, wherein the multiplexing resource configuration information is used for indicating the configuration of multiplexing resources;

and sending the multiplexing resource configuration information.

The computer storage media of the embodiments of the present application may take any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM), a flash Memory, an optical fiber, a portable CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. A computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take a variety of forms, including, but not limited to: an electromagnetic signal, an optical signal, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, Radio Frequency (RF), etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The above description is only exemplary embodiments of the present application, and is not intended to limit the scope of the present application.

In general, the various embodiments of the application may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.

Embodiments of the application may be implemented by a data processor of a mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

Any logic flow block diagrams in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on a memory. The Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random Access Memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disc (CD)), etc. The computer readable medium may include a non-transitory storage medium. The data processor may be of any type suitable to the local technical environment, such as but not limited to general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Programmable logic devices (FGPAs), and processors based on a multi-core processor architecture.

When FDM/SDM is multiplexed between an IAB node MT and a DU, the application also provides a conversion position determining method, which comprises the following steps:

in the case of simultaneous transmission of parent and child links of an IAB node, the transition locations of the mobile terminals and distributed units of the IAB node are determined based on the first or last symbol.

In one embodiment, the transition locations of the mobile terminals and the distributed elements of the IAB node are determined based on the first or last symbol, including one of:

under the condition that an IAB node receives on a parent link and a sub-link simultaneously, the conversion position from an IAB node mobile terminal to a distributed unit is the end position of the last uplink symbol of the uplink resource on the hard resource of the IAB node distributed unit;

under the condition that an IAB node receives on a parent link and a sub-link simultaneously, the conversion position from an IAB node mobile terminal to a distributed unit is the end position of the first symbol after the last uplink symbol of the uplink resource on the hard resource of the IAB node distributed unit;

under the condition that the IAB node simultaneously sends the information on the parent link and the child link, the conversion position from the IAB node mobile terminal to the distributed unit is the end position of the last downlink symbol of the downlink resource on the hard resource of the IAB node distributed unit;

under the condition that an IAB node simultaneously sends on a parent link and a sub-link, the conversion position from the IAB node mobile terminal to a distributed unit is the end position of the first symbol after the last downlink symbol of the downlink resource on the hard resource of the IAB node distributed unit;

under the condition that an IAB node receives on a parent link and a sub-link simultaneously, the conversion position from the IAB node distributed unit to a mobile terminal is the starting position of the first uplink symbol of the uplink resource on the hard resource of the IAB node distributed unit;

under the condition that an IAB node receives on a parent link and a sub-link simultaneously, the conversion position from the IAB node distributed unit to a mobile terminal is the starting position of a first symbol before a first uplink symbol of an uplink resource on a hard resource of the IAB node distributed unit;

under the condition that the IAB node simultaneously transmits on a parent link and a sub-link, the conversion position from the IAB node distributed unit to the mobile terminal is the starting position of the first downlink symbol of the downlink resource on the hard resource of the IAB node distributed unit;

under the condition that the IAB node simultaneously transmits on the parent link and the sub-link, the conversion position from the IAB node distributed unit to the mobile terminal is the starting position of the first symbol before the first downlink symbol of the downlink resource on the hard resource of the IAB node distributed unit.

When the IAB node MT and the DU are subjected to FDM/SDM multiplexing, and the IAB node MT/DU is a flexible symbol at a conversion position, the application also provides a method for determining the protection symbol, which comprises the following steps:

in the case where at least one of the mobile terminal and the distributed unit of the IAB node at the switch location is a flexible symbol, the number of guard symbols is one of: a default value; a configurable value; a value determined according to the type of conversion.

In one embodiment, in the case that the distributed unit of the IAB node at the switch position is a flexible symbol, the number of the protection symbols is the minimum value or the maximum value of the number of the protection symbols corresponding to the switch type when the distributed unit of the IAB node at the switch position is downlink transmission and uplink transmission;

under the condition that at least one of a distributed unit and a mobile terminal of the IAB node at the conversion position is a flexible symbol, the number of the protection symbols is the minimum value or the maximum value of the number of the protection symbols corresponding to the conversion type of the IAB node;

under the condition that the mobile terminal of the IAB node at the conversion position is a flexible symbol, the number of the protection symbols is the minimum value or the maximum value of the number of the protection symbols corresponding to the conversion type when the mobile terminal of the IAB node at the conversion position is downlink transmission and uplink transmission;

and under the condition that at least one of the distributed unit and the mobile terminal of the IAB node at the switching position is a flexible symbol, the number of the protection symbols is the minimum value or the maximum value of the number of the protection symbols of the switching type corresponding to the same switching direction.

Example four

This embodiment shows the determination of the transfer switch position and the number of switch symbols between the MT and the DU.

The IAB node has dual identities of a terminal (MT) and a base station (DU), and different identities have respective transceiving timings, which causes the MT and the DU of the IAB node to use different symbols in the time domain, but may overlap in the time domain, and particularly under the half-duplex limitation, a transceiving switching time or a transceiving switching time may be required between the MT and the DU of the IAB node, which may cause the resources used by the MT and the DU of the IAB node to collide.

In the related art, there are 8 possible conversion types between the IAB node MT and the DU, including 4 conversion types of MT to DU (MT transmit, Tx)/Receive (Receive, Rx) to DU Tx/Rx, i.e., MT Tx to DU Tx, MT Tx to DU Rx, MT Rx to DU Tx, and DU to MT, and 4 conversion types of DU to MT (DU Tx/Rx to MT Tx/Rx, i.e., DU to MT, Tx to MT Rx, DU Rx to MT Tx, and DU Rx to MT Rx), the IAB node provides its parent node (or the serving cell of the IAB node MT) with the number of symbols (i.e., the number of guard symbols) that the parent node is expected to not use at each conversion location, and the parent node provides the IAB node with the number of guard symbols it can provide at each conversion location. To ensure that the parent and child link resources of the IABnode do not conflict, the IAB node and its parent node need to have the same understanding of the switch location and the switch type.

For an IAB node DU, its time resources include 7 types: hard (i.e., Hard) DL, F, UL, Soft (i.e., Soft) DL, Soft F, Soft UL, unavailable. Among them, on hard resources (including DL, UL, F), the DU can directly schedule its sublinks regardless of the resource allocation of the MT. The NA resource is a DU unavailable resource for which the availability of Soft resources (including DL, UL, F) can be determined by parent node indication or MT usage. In addition, the cell-level signal or channel of the IAB node DU may be transmitted on the NA resource or the soft resource (for example, the PDCCH for transmitting the synchronization channel block and SIB1, the PRACH reception, and the like), and in this case, the NA resource or the soft resource for transmitting the cell-level signal or channel is equivalent to a hard resource (for simplicity of description, referred to as an equivalent hard resource).

Example 1

For the IAB node supporting FDM/SDM, under the condition that the transmission direction meets the condition, the IAB node can be simultaneously transmitted on the parent link and the child link or simultaneously received on the parent link and the child link. That is, on the Hard resource of the IAB node DU cell, the parent node of the IAB node can schedule the IAB node MT (corresponding to the parent link). Therefore, in the Hard resource of the IAB node DU cell, when the IAB node simultaneously receives or transmits in the parent link and the child link, when the transmission direction of the child link of the IAB node DU is switched, the transmission switching between the IAB node MT and the IAB node DU also occurs. To ensure that the IAB node and the parent node understand the translation location consistently, the translation location may be determined as follows.

For the case that the IAB node receives on the parent link and the child link simultaneously, the possible conversion positions from the IAB node MT to the IAB node DU are: the ending position of the last UL symbol of the UL resource of the IAB node DU on the Hard resource of the IAB node DU cell; or, the end position of the first symbol after the last UL symbol of the UL resource of the IAB node DU on the Hard resource of the IAB node DU cell.

Fig. 6 is a schematic diagram of a switching position provided in the present application. Referring to fig. 6, the transition location may be an end location of the last UL symbol of the UL resource of the IAB node DU on the Hard resource of the IAB node DU cell.

For the case that the IAB node simultaneously transmits on the parent link and the child link, the possible conversion bits from the IAB node MT to the IAB node DU are: the ending position of the last DL symbol of the DL resource of the IAB node DU on the Hard resource of the IAB node DU cell; or, the ending position of the first symbol after the last DL symbol of the DL resource of the IAB node DU on the Hard resource of the IAB node DU cell.

Fig. 7 is a schematic view of yet another alternative switching position provided by the present application. Referring to fig. 7, the transition location may be an end location of the last DL symbol of the DL resource of the IAB node DU on the Hard resource of the IAB node DU cell.

For the case that the IAB node receives on the parent link and the child link simultaneously, the possible conversion positions from the IAB node DU to the IAB node MT are: starting position of the first UL symbol of the UL resource of the IAB node DU on the Hard resource of the IAB node DU cell; or, the starting position of the first symbol before the first UL symbol of the UL resource of the IAB node DU on the Hard resource of the IAB node DU cell.

Fig. 8 is a schematic diagram of another switching position provided by the present application, and referring to fig. 8, the switching position may be: the starting position of the first UL symbol of the UL resource of the IAB node DU on the Hard resource of the IAB node DU cell.

For the case that the IAB node is simultaneously transmitted on the parent link and the child link, possible conversion positions from the IAB node DU to the IAB node MT are: starting position of first DL symbol of DL resource of IAB node DU on hard resource of IAB node DU cell; or, the starting position of the first symbol is before the first DL symbol of the DL resource of the IAB node DU on the Hard resource of the IAB node DU cell.

Example 2

For flexible symbols where the cell of an IAB node DU is configured at the transition location, the parent node of the IAB node may not be able to determine the transmission direction (Rx or Tx) of the IAB node DU, and therefore, how to determine the number of guard symbols provided by the parent node in this case needs to be considered.

In one embodiment, a method of determining the number of protection symbols provided by a parent node comprises:

the method comprises the following steps: and when the IAB node DU at the conversion position is a flexible symbol, determining the number of the protection symbols as the minimum value or the maximum value of the numbers of the protection symbols corresponding to two conversions when the IAB node DU at the conversion position is UL and DL. In one embodiment, taking MT to DU conversion and minimum value as an example, assuming that the IAB node MT is DL, the number of guard symbols corresponding to MT DL Rx to DU DL Tx conversion is X1, and the number of guard symbols corresponding to MT DL Rx to DU UL Rx conversion is X2 at the conversion position, the number of guard symbols corresponding to MT DL Rx to DU flex conversion is determined to be min { X1, X2}, i.e., the minimum value of X1 and X2.

The method 2 comprises the following steps: when the IAB node DU is a flexible symbol at the switch location, the number of guard symbols is determined to be a configurable value, or a default value. For example, when the IAB node DU is a flexible symbol at the switch location, the IAB node assumes that the number of guard symbols provided by the parent node is 0.

The method 3 comprises the following steps: and when the IAB node DU is a flexible symbol at the conversion position, determining the number of the protection symbols as the minimum value or the maximum value of the number of the protection symbols corresponding to the 8 conversions of the IAB node. For example, assuming that the number of protection symbols corresponding to 8 conversions is Y1., Y8, the IAB node assumes min { Y1., Y8} of the number of protection symbols corresponding to MT-DU flexibility.

The method 4 comprises the following steps: and when the IAB node MT is the flexible symbol at the conversion position, determining the number of the protection symbols as the minimum value or the maximum value of the numbers of the protection symbols corresponding to the UL and the DL when the IAB node MT is at the conversion position.

The method 5 comprises the following steps: when the IAB node MT is a flexible symbol at the switch location, the number of guard symbols is determined to be a configurable value, or a default value.

The method 6 comprises the following steps: and when the IAB node MT is the flexible symbol at the conversion position, determining the number of the protection symbols as the minimum value or the maximum value of the number of the protection symbols corresponding to the 8 conversions of the IAB node.

The method 7 comprises the following steps: and when at least one of the IAB node MT and the IAB node DU is a flexible symbol at the conversion position, determining the number of the protection symbols to be the minimum value or the maximum value of the number of the protection symbols corresponding to the 8 conversions of the IAB node.

The method 8 comprises the following steps: when at least one of the IAB node MT and the IAB node DU is a flexible symbol at the switch location, the number of guard symbols is determined to be a configurable value, or a default value.

The method 9: and when at least one of the IAB node MT and the IAB node DU is a flexible symbol at the conversion position, determining the number of the protection symbols to be the minimum value or the maximum value of the number of the protection symbols of 4 conversions corresponding to the same conversion direction. For example, the IABnode assumes that the number of protection symbols flexibly corresponding to MT DL Rx to DU is the minimum value of the number of protection symbols corresponding to 4 kinds of conversions from MT to DU.

Mode 10: when the parent node does not provide the number of guard symbols corresponding to the translation between the MT and DU of the IAB node, the IAB node assumes the number of guard symbols corresponding to the translation to be a default value. In one embodiment, the conversion is at least one of: MT DL to DU DL, MT DL to DU UL, MT DL to DU Flexible, MT UL to DU DL, MT UL to DU UL, MT UL to DU DL Flexible, MT to DU UL Flexible, DU DL to MT DL, DU DL to MTUL, DU DL to MT Flexible, DU UL to MT DL, DU UL to MT UL, DU UL to MT Flexible, DU DL to MT DL, DU UL to MT UL, DU UL to MT Flexible, DU to MT UL, DU to DU UL, DU to MT Flexible.

Mode 11: when carriers of a plurality of serving cells of an IAB node MT belong to the same frequency band or overlap, the IAB node expects the serving cells to provide the same number of guard symbols.

Mode 12: in the case where at least one of the IAB node MT and the DU is a flexible symbol at the conversion location, the DU assumes that the parent node determines the number of guard symbols in accordance with the DL symbol of the DU at the conversion location; alternatively, the DU assumes a resource usage determined by the hard DL.

In one embodiment, a guard symbol refers to a symbol that the IAB node MT cannot use.

In one embodiment, the default value is 0.

In one embodiment, the default value is a predefined positive integer.

The above methods may be combined without conflict.

It should be noted that in this embodiment and all examples, the hard resource, the soft resource, and the NA resource all refer to the time domain resource of the DU of the IABnode. Hard resources include configured Hard resources as well as equivalent Hard resources (e.g., in the case of cell-specific signals transmitted on soft or NA resources, the soft or NA resources are equivalent Hard resources).

It is noted that in the above embodiments and examples, in the definition of the transition type between the IAB node MT and the DU, MT DL is equivalent to MT Rx, MT UL is equivalent to MT Tx, DU DL is equivalent to DU Tx, and DU UL is equivalent to DU Rx.

It should be noted that, in all the above embodiments and examples, the IAB node is only an example, and the above scheme is also applicable to other nodes, for example, any type of wireless communication device such as a relay node, a base station, and the like, and the corresponding scheme can be obtained by replacing the IAB node with a corresponding device.

The foregoing has provided by way of exemplary and non-limiting examples a detailed description of exemplary embodiments of the present application. Various modifications and adaptations to the foregoing embodiments may become apparent to those skilled in the relevant arts in view of the drawings and the following claims without departing from the scope of the invention. Accordingly, the proper scope of the application is to be determined according to the claims.

Claims

1. A resource allocation method applied to a first communication node, comprising:

2. The method of claim 1, further comprising one or more of:

reporting expected multiplexing resource configuration information;

3. The method according to claim 1 or 2, wherein the multiplexing resource configuration information comprises one or more of: a reference subcarrier spacing; frequency domain resource attribute configuration information; time domain resource configuration information; or, the multiplexing resource configuration information includes one or more of the following: a reference subcarrier spacing; frequency domain resource configuration information; time domain resource configuration information.

4. The method of claim 3, wherein the frequency domain resource attribute configuration information is used to configure the frequency domain resource attribute of each frequency unit.

5. The method of claim 4, wherein the frequency domain resource attributes comprise one or more of: hard; soft; is not available.

6. The method of claim 5,

in the case that the frequency domain resources are configured to be hard, the sub-link of the node corresponding to the frequency domain resources may use the frequency domain resources;

7. The method of claim 5, wherein in the case that the frequency domain resources are configured to be soft, the method comprises one of:

8. The method of claim 3, wherein the frequency domain resource configuration information indicates available frequency domain resources by one of:

the location of available frequency units;

indices of available frequency units.

9. The method of claim 8, wherein the frequency unit comprises any one of: a resource block; a group of resource blocks; a sub-band; a sub-band group; a subcarrier; a subcarrier group; the number of the frequency resource groups is a result of dividing the bandwidth by m and rounded up, wherein m is an integer greater than or equal to 1, the size of each frequency resource group is m resource blocks under the condition that the result of dividing the bandwidth by m is an integer, the size of one frequency resource group is the bandwidth mod m under the condition that the result of dividing the bandwidth by m is not an integer, the sizes of the other frequency resource groups are m, and mod is modular operation.

10. The method of claim 3,

the frequency domain resource attribute configuration information or the frequency domain resource configuration information is effective under the condition that the parent link and the sublinks of the nodes adopt frequency division multiplexing; alternatively, the first and second electrodes may be,

11. The method of claim 3, wherein the time domain resource configuration information comprises one or more of: multiplexing a resource cycle; multiplexing a resource time slot set; multiplexing the resource symbols; and (4) multiplexing mode.

12. The method of claim 11, wherein the set of multiplexed resource time slots is indicated by one of: a bit in the bitmap corresponds to a time slot in a multiplexing resource period, and the bit value of the bitmap is used for indicating whether the corresponding time slot is a multiplexing resource or not; multiplexing the index of the time slot in the resource period; multiplexing a starting time slot index and a multiplexing time slot number which can be multiplexed in a resource period; a start slot index and an end slot index that are multiplexed within the resource period.

13. The method of claim 11, wherein a multiplexing resource symbol indicates reusability of symbols in a multiplexing slot in a set of multiplexing resource slots; or multiplexing the reusability of symbols in the resource period.

14. The method of claim 11, wherein the multiplexing resource symbols are configured by one of: multiplexing symbols are configured for each time slot independently; and the reusable symbols are uniformly configured for all time slots.

15. The method of claim 11, wherein symbols not included in multiplexed resource symbols are not multiplexed; or the reusability of symbols not included in the multiplexed resource symbols is determined according to the usage of the mobile terminal resources of the first communication node.

16. The method of claim 3, wherein the time domain resource configuration information comprises one or more sub-time domain resource configuration information, and wherein the sub-time domain resource configuration information comprises one or more of the following: multiplexing a resource cycle; multiplexing the resource offset; multiplexing a resource duration; and (4) multiplexing mode.

17. The method of claim 3, wherein the time domain resource configuration information configures the time domain resources by one of:

18. The method of claim 1 or 2, wherein each multiplexing resource configuration information corresponds to one cell, one carrier, or at least one resource type.

19. The method of claim 3, wherein the frequency domain resource configuration information is used to indicate one of: frequency resources available to a mobile terminal of the first communication node; frequency resources available to the distributed elements of the first communication node.

20. The method of claim 3, wherein the time domain resource configuration information is used to indicate one of: a time domain resource reusable by a mobile terminal of the first communication node; time domain resources that are reusable by the distributed elements of the first communication node.

21. A resource allocation method applied to a second communication node is characterized by comprising the following steps:

and sending the multiplexing resource configuration information.

22. A resource allocation apparatus, configured at a first communication node, comprising:

23. A resource allocation apparatus, configured at a second communication node, comprising:

24. A communications node, comprising:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-21.

25. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1-21.