CN116458252A

CN116458252A - Node scheduling method and device

Info

Publication number: CN116458252A
Application number: CN202080107041.4A
Authority: CN
Inventors: 卓义斌; 朱元萍; 刘菁; 史玉龙
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-12-22
Filing date: 2020-12-22
Publication date: 2023-07-18
Also published as: WO2022133714A1

Abstract

The embodiment of the application discloses a node scheduling method and device. In the method, a distribution unit DU included in a first node receives first indication information from a CU included in an access backhaul integrated IAB host, wherein the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and a second node, so that the DU included in the first node performs downlink scheduling on the one or more BH RLCs according to the scheduling parameters of the one or more BH RLCs. The embodiment of the application ensures the transmission resources of the BH RLC CH of each bearer non-GBRQoS flow, and is beneficial to ensuring the fair scheduling among the data radio bearers DRB of each terminal device aggregated on the BH RLC CH.

Description

Node scheduling method and device

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a node scheduling method and apparatus.

Background

The fifth Generation mobile communication (5 th-Generation, 5G) puts more stringent demands on various performance indexes of the network than the fourth Generation mobile communication (4 th-Generation, 4G). For example, larger capacity index, wider coverage, ultra-high reliability, ultra-low latency, etc. In order to meet the 5G ultra-high capacity requirement, a mode of networking by adopting high-frequency small stations is becoming popular. However, the high-frequency carrier has poor propagation characteristics, serious shielding attenuation and poor coverage range, and a large number of small stations are required to be densely deployed. And the cost for providing optical fiber return for a large number of densely deployed small stations is high, the construction difficulty is high, and an economic and convenient return scheme is needed. Therefore, to solve the above-mentioned problem, an access backhaul integrated (integrated access and backhaul, IAB) technology is proposed, in which an Access Link (AL) and a Backhaul Link (BL) are both wireless transmission schemes, so that the deployment of optical fibers can be avoided.

The links between different IAB nodes, the links between an IAB node and an IAB-node (IAB-node) host are referred to as backhaul links, and are used to backhaul uplink data of a terminal device (UE) to a centralized unit (IAB donor centralized unit, IAB-node-CU) included in the IAB node or downlink data of an IAB-node-CU to the UE. On the backhaul link, there are one or more backhaul radio link control channels (backhaul radio link control channel, BH RLC CH) for transmitting the above data.

For a plurality of BH RLC CHs carrying non-guaranteed bit rate (non-guaranteed bit rate, non-GBR) quality of service (quality of service, qoS) flows, if data radio bearers (data radio bearer, DRBs) of one UE are aggregated on each BH RLC CH, then each BH RLC CH is fairly scheduled; if different numbers of DRBs of UEs are aggregated on each BH RLC CH and the same number of transmission resources are allocated to the multiple BH RLC CHs, the DRBs of some UEs will be treated unfairly in the BH RLC CH with the greater number of DRBs of the aggregated UEs. For example, for two BH RLC CHs, one BH RLC CH aggregates DRBs of 2 UEs and the other BH RLC CH aggregates DRBs of 10 UEs, if an IAB host includes a distribution unit (IAB donor distributed unit, IAB-donor-DU) that allocates the same number of transmission resources for the two BH RLC CHs at the time of scheduling, performance of DRBs of some UEs may be affected among the BH RLC CHs that aggregate DRBs of 10 UEs.

Disclosure of Invention

The application provides a node scheduling method and device, which can ensure fair scheduling among data radio bearers of aggregated terminal equipment on a BH RLC CH carrying non-GBR QoS flows.

In a first aspect, the present application provides a node scheduling method. In the method, a distribution unit DU included in a first node receives first indication information from a CU included in an access backhaul integrated IAB host, wherein the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and a second node, so that the DU included in the first node performs downlink scheduling on the one or more BH RLCs according to the scheduling parameters of the one or more BH RLCs.

Wherein the scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of one or more BH RLC CHs. The one or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The first node is an IAB host or IAB node and the second node is any one of one or more child nodes of the first node.

As can be seen, in the embodiment of the present application, downlink scheduling is performed on the one or more BH RLC CHs according to the bit rate and/or the scheduling level on the one or more BH RLC CHs, so that transmission resources of the BH RLC CHs carrying non-GBRQoS flows are guaranteed, and further fair scheduling among data radio bearers DRBs of each terminal device aggregated on the BH RLC CHs is guaranteed.

In one implementation manner, in one or more BH RLC CHs, the scheduling parameter of the first BH RLC CH is determined according to the number of DRBs of the terminal device aggregated on the first BH RLC CH, or is determined according to the QoS parameter of a QoS flow on the first BH RLC CH, where the QoS flow is a QoS flow corresponding to the DRBs of the terminal device aggregated on the first BH RLC CH, and the first BH RLC CH is any one of the one or more BH RLC CHs.

In this implementation manner, the scheduling parameters of the BH RLC CH are related to the DRBs of each terminal device aggregated by the BH RLC CH, so that the problem that the DRBs of part of the aggregated terminal devices are not scheduled when the DU included in the first node performs downlink scheduling is avoided, and fair scheduling between the DRBs of each aggregated terminal device on the BH RLC CH carrying the non-GBR QoS flow is realized.

In one implementation, one or more BH RLC CHs may also be BH RLC CHs carrying GBR QoS flows. That is, the first indication information may indicate a scheduling parameter of a BH RLC CH carrying a non-GBR QoS flow and a scheduling parameter of a BH RLC CH carrying a GBR QoS flow. It can be seen that this implementation may jointly indicate the BH RLC CH carrying the non-GBR QoS flow and the BH RLC CH carrying the GBR QoS flow.

In one implementation, the scheduling parameter includes a bit rate, and the DU included in the first node performs downlink scheduling on one or more BH RLC CHs according to the bit rate of the one or more BH RLC CHs, including: the first node includes a DU for scheduling downlink transmission resources for one or more BH RLC CHs according to a ratio between bit rates of the one or more BH RLC CHs.

The implementation is beneficial to reasonably scheduling downlink transmission resources for one or more BH RLC CH of DRB aggregated with different terminal devices. That is, the downlink transmission resource scheduling manner can ensure that DRBs of one or more terminal devices aggregated on the BH RLC CH carrying the non-GBRQoS flow can be scheduled.

In another implementation manner, the scheduling parameters include a scheduling level, and the DU included in the first node performs downlink scheduling on one or more BH RLC CHs according to the scheduling level of the one or more BH RLC CHs, where the method includes: and carrying out downlink scheduling on the one or more BH RLC CH according to the scheduling sequence corresponding to the scheduling level of the one or more BH RLC CH. The implementation method can ensure that the BH RLC CH with high scheduling level is scheduled first, thereby being beneficial to ensuring that DRB of terminal equipment aggregated on the BH RLC CH with high scheduling level can be scheduled.

In a second aspect, the present application further provides a node scheduling method, where the node scheduling method in the aspect corresponds to the node scheduling method in the first aspect, and the node scheduling method in the aspect is described from a CU side included in an access backhaul integrated IAB host. In the method, a centralized unit CU included in an access backhaul integrated IAB host determines first indication information and sends the first indication information to a DU included in a first node.

The first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and the second node. The scheduling parameters include at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of one or more bhrlc CHs. One or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The first node is an IAB host or IAB node and the second node is any one of one or more child nodes of the first node.

In this embodiment, the CU included in the IAB host indicates, to the DU included in the first node, a bit rate and/or a scheduling level of one or more BH RLC CHs between the first node and the second node, so that the DU of the first node is beneficial to downlink scheduling of the one or more BH RLC CHs according to the bit rate and/or the scheduling level of the one or more BH RLC CHs, and further is beneficial to ensuring fair scheduling between data radio bearers DRBs of each terminal device aggregated on the BH RLC CHs.

In one implementation, the scheduling parameter of the first BH RLC CH of the one or more BH RLC CHs is determined according to the number of data radio bearers DRBs of the terminal device aggregated on the first BH RLC CH, or according to the QoS parameter of the QoS flow on the first BH RLC CH, where the QoS flow is a QoS flow corresponding to the DRBs of the terminal device aggregated on the first BH RLC CH. The first BH RLC CH is any one of one or more BH RLC CHs.

In a third aspect, the present application provides a node scheduling method. The node scheduling method of this aspect is described for uplink transmission and is described from the side of the DU included in the first node. In the method, a distribution unit DU included in a first node receives first indication information from a CU included in an access backhaul integrated IAB, wherein the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and a second node, so that the DU included in the first node performs uplink scheduling on the second node according to the scheduling parameters of the one or more BH RLCs.

Wherein the scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of one or more BH RLC CHs. The one or more bhrlc CHs are bhrlc CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The first node is an IAB host or IAB node and the second node is any one of one or more child nodes of the first node.

It can be seen that, in the embodiment of the present application, the DU included in the first node performs uplink scheduling on the second node according to the bit rate and/or the scheduling level on the one or more BH RLC CHs, so as to ensure the transmission resource of the second node, and further facilitate ensuring fair scheduling between the one or more BH RLC CHs.

In one implementation, the DU included in the first node sends second indication information to the mobile terminal MT included in the second node; the second indication information is used for indicating a first priority bit rate and a first priority of one or more logical channels; 1. one or more logical channels are in one-to-one correspondence with one or more BH RLC CHs; the first priority bit rate and the first priority are for an MT included in the second node to perform a logical channel priority LCP procedure.

That is, the DU of the first node indicates the first priority bit rate and the first priority of the one or more logical channels used for performing the logical channel priority LCP procedure to the MT included in the second node, which is beneficial to ensuring that when the MT included in the second node performs uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logical channels, data radio bearers DRBs of terminal devices aggregated on the BH RLC CHs are all scheduled, that is, ensuring fair scheduling between DRBs of terminal devices aggregated on the BH RLC CHs.

In one implementation, the scheduling parameter of the first BH RLC CH of the one or more BH RLC CHs is determined according to the number of data radio bearers of the terminal device aggregated on the first BH RLC CH, or is determined according to the QoS parameter of the QoS flow on the first BH RLC CH, where the QoS flow is a QoS flow corresponding to the data radio bearers of the terminal device aggregated on the first BH RLC CH. The first BH RLC CH is any one of one or more BH RLC CHs.

In this implementation manner, the scheduling parameters of the BH RLC CH are related to the DRBs of each terminal device aggregated by the BH RLC CH, so that the problem that the BH RLC CH carrying non-GBR QoS flows is not scheduled when the DU included in the first node performs uplink scheduling on the second node is avoided, and fair scheduling among the BH RLC CHs is realized.

In one implementation, one or more BH RLC CHs are also BH RLC CHs carrying GBR QoS flows. That is, the first indication information may indicate a scheduling parameter of a BH RLC CH carrying a non-GBR QoS flow and a scheduling parameter of a BH RLC CH carrying a GBR QoS flow. It can be seen that the implementation can jointly indicate the bhrlc CH carrying the non-GBR QoS flow and the bhrlc CH carrying the GBR QoS flow.

In one implementation, the first priority bit rate and the first priority are determined based on scheduling parameters. That is, in this implementation, the first priority bit rate and the value of the first priority are also related to DRBs of the terminal device aggregated on the BH RLC CH, so that it is beneficial to ensure fair scheduling between DRBs of the terminal device aggregated on the BH RLC CH when the MT included in the second node performs uplink scheduling on one or more BH RLC CHs.

In one implementation, the scheduling parameter includes a bit rate, and the DU included in the first node performs uplink scheduling on the second node according to the bit rate of one or more BH RLC CHs between the first node and the second node, including: and scheduling uplink transmission resources for the second node and a third node according to a ratio of a sum of bit rates of one or more BH RLC CHs between the first node and the second node to a sum of bit rates of one or more BH RLC CHs between the first node and the third node, the third node being a node different from the second node among child nodes of the first node.

The implementation manner is beneficial to reasonably scheduling the uplink transmission resources for the second node and the third node. That is, the uplink transmission resource scheduling manner can ensure that one or more bhrlc CHs carrying non-GBRQoS flows between the first node and the second node and between the first node and the third node can be scheduled.

In another implementation manner, the scheduling parameters include a scheduling level, and the DU included in the first node performs uplink scheduling on the second node according to the scheduling level of one or more BH RLC CHs between the first node and the second node, where the uplink scheduling includes: and carrying out uplink scheduling on the second node and the third node according to the scheduling sequence corresponding to the scheduling level of one or more BH RLC CH between the first node and the second node and the scheduling sequence corresponding to the scheduling level of one or more BH RLC CH between the first node and the third node, wherein the third node is a node different from the second node in the child nodes of the first node. The realization method can ensure that the sub-node corresponding to the BH RLC CH with high scheduling level is scheduled first, thereby being beneficial to the BH RLC CH between the first node and the sub-node to be scheduled.

In a fourth aspect, the present application further provides a node scheduling method, where the node scheduling method in the aspect corresponds to the node scheduling method in the third aspect, and the node scheduling method in the aspect is set forth from an MT side included in the second node. In the method, a mobile terminal MT included in a second node receives second indication information from a distribution unit DU included in a first node, wherein the second indication information is used for indicating first priority bit rates and first priorities of one or more logic channels, then the MT included in the second node performs logic channel priority LCP flow according to the first priority bit rates and the first priorities of the one or more logic channels, and performs uplink scheduling on one or more BH RLCs corresponding to the one or more logic channels.

Wherein the one or more logical channels are in one-to-one correspondence with one or more BH RLC CHs between the first node and the second node. One or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The second node is any one of one or more child nodes of the first node.

As can be seen, in the embodiment of the present application, the logic channel priority LCP flow is performed according to the first priority bit rate and the first priority of one or more logic channels, and uplink scheduling is performed on one or more BH RLC CHs corresponding to one or more logic channels, so that fair scheduling among data radio bearers DRBs of each terminal device aggregated on the BH RLC CHs can be ensured.

In one implementation, the one or more BH RLC CHs may also be BH RLC CHs carrying GBR QoS flows, i.e. the second indication information may also indicate a first priority bit rate and a first priority of the BH RLC CHs carrying GBR QoS flows. It can be seen that the implementation can jointly indicate the bhrlc CH carrying the non-GBR QoS flow and the bhrlc CH carrying the GBR QoS flow.

In one implementation, the MT included in the second node performs a logical channel priority LCP procedure according to a first priority bit rate and a first priority of one or more logical channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logical channels, including: receiving third indication information from the central unit CU comprised by the IAB host, the third indication information being used for indicating a scaling factor of a priority bit rate and a scaling factor of a priority of the one or more logical channels; then determining a second priority bit rate for the one or more logical channels based on the first priority bit rate and a scaling factor for the priority bit rate, and determining a second priority for the one or more logical channels based on the first priority and the scaling factor for the priority; and finally, carrying out logic channel priority LCP flow according to the second priority bit rate and the second priority of one or more logic channels, and carrying out uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels.

In this implementation, the CU included in the IAB host may indicate to the MT included in the second node a scaling factor for a priority bit rate and a scaling factor for a priority of the one or more logical channels, such that the MT included in the second node may determine a second priority bit rate and a second priority for the one or more logical channels for LCP flows based on the first priority bit rate, the first priority, and the scaling factors for the priority bit rate and the priority, respectively.

In one implementation, the MT included in the second node performs a logical channel priority LCP procedure according to a first priority bit rate and a first priority of one or more logical channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logical channels, including: receiving fourth indication information from a central unit CU included in the IAB host, the fourth indication information being used to indicate a third priority bit rate and a third priority of the one or more logical channels; and then, carrying out logic channel priority LCP flow according to the third priority bit rate and the third priority of the one or more logic channels, and carrying out uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels. That is, in this implementation, the third priority bit rate and the third priority for the LCP flow by the MT included in the second node are indicated by the CU included in the IAB host.

In one implementation, the MT included in the second node performs a logical channel priority LCP procedure according to a first priority bit rate and a first priority of one or more logical channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logical channels, including: and carrying out logic channel priority LCP flow according to the first priority bit rate and the first priority of one or more logic channels by utilizing the uplink transmission resource authorized by the DU included by the first node, and carrying out uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels.

In this implementation manner, the uplink transmission resources authorized by the DU included in the first node for the MT included in the second node are determined according to the bit rate and/or the scheduling level of one or more BH RLC CHs between the first node and the second node, so that it is beneficial to ensure that the one or more BH RLC CHs can be scheduled.

In a fifth aspect, the present application further provides a node scheduling method, where the node scheduling method in the aspect corresponds to the node scheduling method in the third aspect or the fourth aspect, and the node scheduling method in the aspect is described from a CU side included in an access backhaul integrated IAB host. In the method, a centralized unit CU included in an access backhaul integrated IAB host determines first indication information and sends the first indication information to a CU included in a first node.

The first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and the second node. The scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of the plurality of second BH RLC CHs. One or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The first node is an IAB host or IAB node and the second node is any one of one or more child nodes of the first node.

It can be seen that the CU included in the IAB host indicates, to the DU included in the first node, a bit rate and/or a scheduling level of one or more BH RLC CHs carrying non-GBR QoS flows between the first node and the second node, so that the DU included in the first node is beneficial to uplink scheduling of the second node according to the bit rate and/or the scheduling level of the one or more BH RLC CHs, and is beneficial to ensuring fair scheduling between the one or more BH RLC CHs between the first node and the second node.

In one implementation manner, the scheduling parameter of a first BH RLC CH of the one or more BH RLC CHs is determined according to the number of data radio bearers of the terminal device aggregated on the first BH RLC CH, or is determined according to the QoS parameter of a QoS flow on the first BH RLC CH, where the QoS flow is a QoS flow corresponding to the data radio bearers of the terminal device aggregated on the first BH RLC CH; the first BH RLC CH is any one of a plurality of BH RLC CHs.

In one implementation, the one or more first BH RLC CHs are also BH RLC CHs carrying GBR QoS flows. That is, the first indication information may indicate a scheduling parameter of a BH RLC CH carrying a non-GBR QoS flow and a scheduling parameter of a BH RLC CH carrying a GBR QoS flow. It can be seen that the implementation can jointly indicate the bhrlc CH carrying the non-GBR QoS flow and the bhrlc CH carrying the GBR QoS flow.

In one implementation manner, the CU included in the IAB host may further send third indication information to the mobile terminal MT included in the second node; the third indication information is used for indicating the scaling factors of the priority bit rate and the scaling factors of the priority of one or more logic channels; one or more logical channels are in one-to-one correspondence with one or more BH RLC CHs.

In another implementation, the CU included in the IAB host may further send fourth indication information to the second node, where the fourth indication information is used to indicate a third priority bit rate and a third priority of one or more logical channels, and the third priority bit rate and the third priority are used by the second node to perform a logical channel priority LCP procedure.

In a sixth aspect, the present application also provides a communication device. The communication device has a function of implementing part or all of the DU included in the first node in the first aspect, or the communication device has a function of implementing part or all of the CU included in the IAB host in the second aspect, or the communication device has a function of implementing part or all of the DU included in the first node in the third aspect, or the communication device has a function of implementing part or all of the MT included in the second node in the fourth aspect, or the communication device has a function of implementing part or all of the CU included in the IAB host in the fifth aspect. For example, the function of the communication device may be provided in some or all of the embodiments of the DU included in the first node in the present application, or may be provided to implement any of the embodiments in the present application alone. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

In one possible design, the communication device may include a processing unit and a communication unit in a structure, where the processing unit is configured to support the communication device to perform the corresponding functions in the method. The communication unit is used for supporting communication between the communication device and other communication devices. The communication device may further comprise a memory unit for coupling with the processing unit and the communication unit, which holds the necessary program instructions and data of the communication device.

In one implementation, the communication device includes:

the communication unit is used for receiving first indication information from the CU included in the access backhaul integrated IAB host, wherein the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between a first node and a second node, and the first node is the IAB host or the IAB node;

and the processing unit is also used for carrying out downlink scheduling on the one or more BH RLC CH according to the scheduling parameters of the one or more BH RLC CH.

Wherein the scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of one or more BH RLC CHs. One or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The first node is an IAB host or IAB node and the second node is any one of the one or more child nodes of the first node.

In addition, in this aspect, other optional embodiments of the communication device may be referred to in the relevant content of the first aspect, which is not described in detail herein.

In one embodiment of the method of the present invention, the communication device includes:

a processing unit, configured to determine first indication information, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels bhrlc CH between a first node and a second node;

And a communication unit configured to send the first indication information to a DU included in the first node.

In addition, in this aspect, other optional embodiments of the communication device may be referred to in the related content of the second aspect, which is not described in detail herein.

In one implementation, the communication device includes:

the communication unit is used for receiving first indication information from the CU included in the access backhaul integrated IAB, wherein the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between a first node and a second node, and the first node is an IAB host or an IAB node;

and the processing unit is used for carrying out uplink scheduling on the second node according to the scheduling parameters of the one or more BH RLC CH.

Wherein the scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of one or more BH RLC CHs. The one or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The second node is any one of one or more child nodes of the first node.

In addition, in this aspect, other optional embodiments of the communication device may be referred to in the related content of the third aspect, which is not described in detail herein.

In one implementation, the communication device includes:

a communication unit configured to receive second indication information from a distribution unit DU included in a first node, the second indication information being configured to indicate a first priority bit rate and a first priority of one or more logical channels, the first node being an IAB host or an IAB node, the second node being any one of one or more child nodes of the first node;

and the processing unit is used for carrying out logic channel priority LCP flow according to the first priority bit rate and the first priority of one or more logic channels and carrying out uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels.

Wherein, one or more logical channels are in one-to-one correspondence with one or more BH RLC CHs, which are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows.

In addition, in this aspect, other optional embodiments of the communication device may be referred to in the related content of the fourth aspect, which is not described in detail herein.

In one implementation, the communication device includes:

Wherein the scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of one or more BH RLC CHs. One or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The first node is an IAB host or IAB node and the second node is any one of one or more child nodes of the first node.

In addition, in this aspect, other optional embodiments of the communication device may refer to the related matters of the fifth aspect, which are not described in detail herein.

As an example, the communication unit may be a transceiver or an interface, the storage unit may be a memory, and the processing unit may be a processor.

In one implementation, the communication device includes:

a transceiver configured to receive first indication information from a CU included in an access backhaul integrated IAB host, where the first indication information is configured to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CHs between a first node and a second node, and the first node is an IAB host or an IAB node;

And the processor is used for carrying out downlink scheduling on the one or more BH RLC CH according to the scheduling parameters of the one or more BH RLC CH.

In another implementation, the communication device includes:

a processor, configured to determine first indication information, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels bhrlc CH between a first node and a second node;

and a transceiver for transmitting the first indication information to a DU included in the first node.

In yet another implementation, the communication device includes:

a transceiver, configured to receive first indication information from a CU included in an access backhaul integrated IAB, where the first indication information is configured to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CHs between a first node and a second node, and the first node is an IAB host or an IAB node;

and the processor is used for carrying out uplink scheduling on the second node according to the scheduling parameters of the one or more BH RLC CH.

Wherein the scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of one or more BH RLC CHs. One or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The second node is any one of one or more child nodes of the first node.

In yet another implementation, the communication device includes:

A transceiver for receiving second indication information from a distribution unit DU included in a first node, the second indication information being for indicating a first priority bit rate and a first priority of one or more logical channels, the first node being an IAB host or an IAB node, the second node being any one of one or more child nodes of the first node;

and the processor is used for carrying out logic channel priority LCP flow according to the first priority bit rate and the first priority of one or more logic channels and carrying out uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels.

In yet another implementation, the communication device includes:

In an implementation, a processor may be used to perform, for example but not limited to, baseband related processing, and a transceiver may be used to perform, for example but not limited to, radio frequency transceiving. The above devices may be provided on separate chips, or may be provided at least partially or entirely on the same chip. For example, the processor may be further divided into an analog baseband processor and a digital baseband processor. Wherein the analog baseband processor may be integrated on the same chip as the transceiver and the digital baseband processor may be provided on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, the digital baseband processor may be integrated on the same chip as a variety of application processors (e.g., without limitation, graphics processors, multimedia processors, etc.). Such chips may be referred to as System on chips (System on chips). Whether the individual devices are independently disposed on different chips or integrally disposed on one or more chips is often dependent on the needs of the product design. The implementation form of the device is not limited in the embodiment of the application.

In a seventh aspect, the present application also provides a processor configured to perform the above-described methods. In performing these methods, the process of transmitting the above information and receiving the above information in the above methods may be understood as a process of outputting the above information by a processor and a process of receiving the above information inputted by the processor. When outputting the information, the processor outputs the information to the transceiver for transmission by the transceiver. This information, after being output by the processor, may also require additional processing before reaching the transceiver. Similarly, when the processor receives the input of the information, the transceiver receives the information and inputs it to the processor. Further, after the transceiver receives the information, the information may need to be further processed before being input to the processor.

Based on the above principle, for example, the transmission of the first indication information mentioned in the foregoing method may be understood as the transmission of the output first indication information by the processor.

With respect to operations such as transmitting, sending, and receiving, etc., that are referred to by a processor, unless otherwise specified, or if not contradicted by actual or inherent logic in the relevant description, the operations such as outputting and receiving, inputting, etc., by the processor are more generally understood as being operations such as transmitting, sending, and receiving, rather than directly by radio frequency circuitry and antennas.

In implementation, the processor may be a processor dedicated to performing the methods, or may be a processor that executes computer instructions in a memory to perform the methods, e.g., a general purpose processor. The Memory may be a non-transitory (non-transitory) Memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of the Memory and the manner of providing the Memory and the processor are not limited in this embodiment of the present application.

In an eighth aspect, the present application also provides a communication system, which includes at least one core network device, at least one radio access network device, at least one wireless backhaul device, and at least one terminal device of the above aspects. In another possible design, the system may further include other devices that interact with the above devices in the solution provided in the present application.

In a ninth aspect, the present application provides a computer readable storage medium storing computer software instructions which, when executed by a communications device, implement the method of the first aspect.

In a tenth aspect, the present application provides a computer readable storage medium storing computer software instructions which, when executed by a communications device, implement the method of the second aspect.

In an eleventh aspect, the present application provides a computer readable storage medium storing computer software instructions which, when executed by a communications device, implement the method of the third aspect.

In a twelfth aspect, the present application provides a computer readable storage medium storing computer software instructions which, when executed by a communications device, implement the method of the fourth aspect.

In a thirteenth aspect, the present application provides a computer readable storage medium storing computer software instructions which, when executed by a communications device, implement the method of the fifth aspect.

In a fourteenth aspect, the present application also provides a computer program product comprising instructions which, when run on a communication device, cause the communication device to perform the method of the first aspect described above.

In a fifteenth aspect, the present application also provides a computer program product comprising instructions which, when run on a communications apparatus, cause the communications apparatus to perform the method of the second aspect described above.

In a sixteenth aspect, the present application also provides a computer program product comprising instructions which, when run on a communication device, cause the communication device to perform the method of the third aspect described above.

In a seventeenth aspect, the present application also provides a computer program product comprising instructions which, when run on a communication device, cause the communication device to perform the method of the fourth aspect described above.

In an eighteenth aspect, the present application also provides a computer program product comprising instructions which, when run on a communication device, cause the communication device to perform the method of the fifth aspect described above.

In a nineteenth aspect, the present application provides a chip system comprising a processor and an interface for obtaining a program or instructions, the processor for invoking the program or instructions to implement or support a DU comprised by a first node to implement the functionality involved in the first aspect, e.g. to determine or process at least one of data and information involved in the above-mentioned method. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In a twentieth aspect, the present application provides a chip system comprising a processor and an interface for retrieving a program or instruction, the processor for invoking the program or instruction to implement or support a CU comprised by an IAB host to implement the functionality involved in the second aspect, e.g. to determine or process at least one of data and information involved in the above-described method. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In a twenty-first aspect, the present application provides a chip system comprising a processor and an interface for retrieving a program or instructions, the processor for invoking the program or instructions to implement or support a DU comprised by a first node to implement the functionality involved in the third aspect, e.g. to determine or process at least one of data and information involved in the above-mentioned method. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In a twenty-second aspect, the present application provides a chip system comprising a processor and an interface for acquiring a program or instruction, the processor for invoking the program or instruction to implement or support the MT included in the second node to implement the functionality involved in the fourth aspect, e.g. to determine or process at least one of data and information involved in the above-described method. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In a twenty-third aspect, the present application provides a chip system comprising a processor and an interface for retrieving a program or instructions, the processor for invoking the program or instructions to implement or support a CU comprised by an IAB host to implement the functionality involved in the fifth aspect, e.g. to determine or process at least one of data and information involved in the above-described method. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of an IAB network according to an embodiment of the present application;

fig. 3 is a schematic diagram of an IAB network user plane protocol stack according to an embodiment of the present application;

fig. 4 is a schematic diagram of an IAB network control plane protocol stack according to an embodiment of the present application;

fig. 5 is a schematic flow chart of a node scheduling method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of another IAB network provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of yet another IAB network provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of yet another IAB network provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of yet another IAB network provided in an embodiment of the present application;

fig. 10 is a flowchart of another node scheduling method according to an embodiment of the present application;

FIG. 11 is a flowchart of yet another node scheduling method according to an embodiment of the present disclosure;

fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

Specific embodiments of the present application are described in further detail below with reference to the accompanying drawings.

First, in order to better understand the node scheduling method disclosed in the embodiments of the present application, a communication system to which the embodiments of the present application are applicable will be described.

The technical scheme of the embodiment of the application can be applied to various communication systems. For example, the global system for mobile communications, the long term evolution (Long Term Evolution, LTE) frequency division duplex system, the LTE time division duplex system, the universal mobile telecommunications system, the fourth Generation mobile telecommunications technology (4 th-Generation, 4G) system, the fifth Generation mobile telecommunications technology (5 th-Generation, 5G) system, and with the continuous development of the telecommunications technology, the technical solutions of the embodiments of the present application may also be used for the subsequently evolved telecommunications system, such as the sixth Generation mobile telecommunications technology (6 th-Generation, 6G) system, and so on.

Referring to fig. 1, fig. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application. The communication system may comprise a core network device 101, a radio access network device 102, a wireless backhaul device 103, and at least one terminal device (e.g., terminal device 1041 and terminal device 1041 in fig. 1). The terminal device is connected to the wireless backhaul device 103 in a wireless manner and to the radio access network device 102 via one or more wireless backhaul devices 103. Alternatively, part of the terminal devices may be directly connected to the radio access network device 102 in a wireless manner. The radio access network device 102 is connected to the core network device 101 by wireless or wired means. The core network device 101 and the radio access network device 102 may be separate physical devices, may be devices in which the functions of the core network device 101 and the logical functions of the radio access network device 102 are integrated on the same physical device, or may be devices in which the functions of a part of the core network device 101 and the functions of a part of the radio access network device 102 are integrated on one physical device. The terminal device may be fixed in position or may be movable.

The number of the core network devices, the wireless access network devices, the wireless backhaul devices and the terminal devices included in the communication system is not limited, and the actual application may include two or more core network devices, two or more wireless access network devices, two or more wireless backhaul devices and two or more terminal devices.

In the embodiment of the present application, the radio access network device is an access device that a terminal device or a wireless backhaul device accesses to the mobile communication system in a wireless manner, and may be a base station NodeB, an evolved base station eNodeB, a base station gNB in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc., where specific technologies and specific device configurations adopted by the radio access network device are not limited.

In some deployments, the gNB may include a Centralized Unit (CU) and a Distributed Unit (DU). The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (medium access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer eventually becomes information of the PHY layer or is converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by DUs or by DUs and AAUs. It is understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into network devices in an access network (radio access network, RAN), or may be divided into network devices in a Core Network (CN), which is not limited in this application.

The Terminal device may also be referred to as a Terminal, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc. The terminal device may be a mobile phone, a tablet (Pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (self-driving), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), or the like.

The wireless backhaul device may provide backhaul services to its child nodes. Specifically, it may be a relay node in the LTE system, an IAB node in the 5G system, or other devices capable of providing a wireless relay function.

The wireless access network device, the wireless backhaul device, and the terminal device may be deployed on land, including indoor or outdoor, handheld, or vehicle-mounted; the device can be deployed on the water surface; but also on aerial planes, balloons and satellites. The embodiment of the application does not limit the application scenes of the wireless access network device, the wireless backhaul device and the terminal device.

In the embodiment of the application, the wireless links between the devices can communicate through the licensed spectrum (licensed spectrum), can also communicate through the unlicensed spectrum (unlicensed spectrum), and can also communicate through the licensed spectrum and the unlicensed spectrum at the same time. The wireless links between the devices may communicate over a frequency spectrum of 6 gigahertz (GHz) or less, may communicate over a frequency spectrum of 6GHz or more, and may communicate using both a frequency spectrum of 6GHz or less and a frequency spectrum of 6GHz or more. The spectrum resources used by the wireless link are not limited in the embodiments of the present application.

The radio access network device in the embodiment of the present application takes an access backhaul integrated host (integrated access and backhaul donor, IAB-donor) as an example, the radio backhaul device takes an IAB node as an example, and the terminal device takes a mobile phone as an example.

In order to facilitate an understanding of the embodiments disclosed herein, the following two descriptions are provided.

(1) In the embodiments disclosed in the present application, the scenario is described by taking the scenario of an NR network in a wireless communication network as an example, and it should be noted that the schemes in the embodiments disclosed in the present application may also be applied to other wireless communication networks, and the corresponding names may also be replaced by names of corresponding functions in other wireless communication networks.

(2) Embodiments of the present disclosure will present various aspects, embodiments, or features of the present disclosure around a system comprising a plurality of devices, components, modules, etc. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, combinations of these schemes may also be used.

Next, related concepts related to the embodiments of the present application will be briefly described.

1. IAB host, IAB node and IAB network

IAB host: the IAB host may be an access network element with a complete base station function, or may be an access network element with a separated form of a Centralized Unit (CU) and a Distributed Unit (DU). The IAB Donor in the embodiments of the present application may also be referred to as a host node (Donor node) or a host base station (DgNB, donor gnob).

The IAB host may be connected to a core network (e.g., 5G core network, 5 GC) network element serving the UE and provide radio backhaul functionality for the IAB node. The IAB host may include a centralized unit simply referred to as a donor CU, or a CU. The distribution unit comprised by the IAB host may be referred to simply as a donor DU. The donor CU may be in a form in which a Control Plane (CP) and a User Plane (UP) are separated. For example, a CU may be composed of one CU-CP and one or more CU-UPs.

IAB node: is a Relay Node (RN) in the IAB network, or called a wireless backhaul node, a wireless backhaul device. The IAB node may provide wireless access services for the UE and traffic data for the UE may be transmitted by the IAB node to the IAB host over a wireless backhaul link.

The IAB node may be composed of a mobile terminal (mobile termination, MT) part and a Distributed Unit (DU) part. Wherein, when the IAB node faces to the father node, the IAB node can be regarded as a role of user equipment (MT); when an IAB is directed to its child node (which may be another IAB node, or UE), it may be seen as a network device providing backhaul services to the child node, i.e. as a role of DU.

IAB network: is a network supporting multi-hop and multi-connection networking. In an IAB network, there may be multiple transmission paths between the UE and the IAB host. On one transmission path, a plurality of nodes may be included. For example: UE, one or more IAB nodes, and IAB node (if the IAB node is a form of CU and DU separated, it further includes a DU included in the IAB host and a CU included in the IAB host). Each IAB node treats the neighboring node for which backhaul service is provided as a parent node, and accordingly, each IAB node may be treated as a child node of its parent node.

For example, as shown in fig. 2, the parent node of IAB node 1 is IAB donor, IAB node 1 is also the parent nodes of IAB node 2 and IAB node 3, IAB node 2 and IAB node 3 are both the parent nodes of IAB node4, and the parent node of IAB node 5 is IAB node 3. The uplink data of the UE may be transmitted to the IAB node via one or more IAB nodes and then sent by the IAB node to a mobile gateway device (e.g. a user plane function UPF in a 5G core network). And the downlink data of the UE is received from the mobile gateway equipment by the IAB node and then is sent to the UE through the IAB node. There are two paths available for data transmission between UE #1 and IAB node, path 1: path 2:there are three paths available for data transmission between UE #2 and IAB node, path 3: path 4: path 5:

2. backhaul adaptation protocol, F1 interface

Backhaul adaptation protocol (backhaul adaptation protocol, BAP): a new protocol layer is introduced in the wireless backhaul link, and the BAP is located above the radio link control (radio link control, RLC) layer, and can be used to implement functions such as routing data on the wireless backhaul link, and bearer mapping.

F1 interface: an interface is established between the DU included in the IAB node and the IAB host (or the CU included in the IAB host). The F1 interface may also be referred to as an F1 interface, which may be collectively referred to as an F1 interface in the embodiments of the present application, but the naming of the interface is not limited.

The F1 interface supports user plane protocols (F1-U/F1 x-U) and control plane protocols (F1-C/F1 x-C). Wherein, as shown in fig. 3, the user plane protocol of the F1 interface includes one or more of the following protocol layers: a general packet radio service (general packet radio service, GPRS) tunneling protocol user plane (GPRS tunnelling protocol user plane, GTP-U), user datagram protocol (user datagram protocol, UDP), internet protocol (internet protocol, IP), and like protocol layers; as shown in fig. 4, the control plane protocol of the F1 interface includes one or more of the following: f1 application protocol (F1 application protocol, F1 AP), stream control transmission protocol (stream control transport protocol, SCTP), IP, etc.

Through the control plane of the F1 interface, interface management can be performed between the IAB node and the IAB host, the IAB host manages DUs included in the IAB node, and the IAB host performs UE context-related configuration and the like. Through the user plane of the F1 interface, the functions of user plane data transmission, downlink transmission state feedback and the like can be executed between the IAB node and the IAB host.

3. Logical channel priority (logical channel prioritization, LCP) flow

When the terminal equipment obtains the scheduling opportunity authorized by the network equipment, namely, the uplink transmission resource authorized by the network equipment is obtained, the priority order of scheduling each logic channel can be determined according to the condition of each uplink logic channel. Wherein the priority of the control logical channel is higher than the priority of the data logical channel, and the priority of the common control channel (common control channel, CCCH) is highest. The priority between the data logical channels is then dependent on the QoS parameters of the corresponding quality of service (quality of service, qoS) flows of the data radio bearers (data radio bearer, DRBs) aggregated over the logical channels.

If the terminal device allocates physical layer transmission opportunities for radio bearers on multiple logical channels at the medium access control (media access control, MAC) layer only by means of priority, the following new problems arise: the logical channel with the highest priority is always served by the MAC layer first, i.e. the MAC layer first puts the data in the logical channel with the highest priority into the MAC protocol data unit (MAC protocol data unit, MAC PDU) and then processes the second logical channel with the highest priority until the MAC PDU is filled.

In many cases, however, the transmission channel capacity allocated by the network device to the terminal device in one transmission time interval (transmission time interval, TTI) is limited, and the MAC PDU cannot hold all the data provided by the logical channels. The data provided by the low priority logical channels has to wait for the next transmission opportunity. In the next TTI, the high-priority logical channel is still served first, and if the data amount provided by the high-priority logical channel is large, the data provided by the low-priority logical channel may wait for a long time and even cannot be served forever.

To avoid the problem that the low priority logical channels cannot always be served, the network device configures a priority bit rate (prioritized bit rate, PBR) in kB/s for each uplink logical channel of the terminal device. The MAC layer scheduler of the terminal device limits the transmission rate of each logical channel to below the respective PBR. That is, if the data transmission rate of a certain high priority logical channel exceeds the PBR of the present logical channel, the MAC layer scheduler may instead serve a logical channel with a low priority and a transmission rate not reaching the PBR even though the high priority logical channel still has data to be transmitted.

Currently, a scheduler realizes the guarantee that the transmission rate of each logic channel is below PBR through a Token Bucket (Token Bucket) algorithm. Token Bucket algorithms are a commonly used rate limiting method that can be visually compared to the operation of a Bucket (Bucket) containing "tokens". A Token is a pass that transmits data, and a Token indicates that one unit of data (typically in bytes) can be passed. Tokens are placed into the bucket at a pre-agreed rate (i.e., PBR), and the data producer (i.e., logical channel) first takes tokens from the bucket, and how many tokens to take, and how much data to send. After the logic channel transmits data, the token in the bucket is correspondingly reduced, so that the speed of taking the token by the logic channel (namely, the data transmission rate) does not exceed the speed of putting the token in (namely, the PBR), thereby achieving the aim of limiting the data transmission rate.

The network device may configure the priorities, PBR and bucket size durations (bucket size duration, BSD) for the respective logical channels through RRC dedicated signaling (field LogicalChannelConfig). The token bucket size for each logical channel is PBR x BSD. For each TTI, for the token bucket of logical channel j, the newly added token amount is pbr×tti, and the total token amount is denoted B. When allocating resources, the scheduler of the terminal equipment considers the logical channels with tokens (B > 0) in the bucket, and puts the data of the logical channels into the MAC PDU from high to low according to the order of the logical channels until the MAC PDU is full. If the MAC PDU is not yet full, the terminal device re-allocates resources for each logical channel in the priority order of each logical channel, at which point the value of B is not considered.

The technical problems to be solved by the present application will be briefly described below.

The links between different IAB nodes, the links between an IAB node and an IAB host are all referred to as backhaul links, and are used to backhaul uplink data from a terminal device to a CU included in the IAB host, or downlink data from the CU included in the IAB host to a UE. On the backhaul link, there are one or more backhaul radio link control channels (backhaul radio link control channel, BH RLC CH) for transmitting the above data. Further, for data of data radio bearers (data radio bearer, DRBs) of different UEs (including both DRBs of different UEs and different DRBs of one UE), the relation with the BH RLC CH may be 1:1 or n:1. That is, the data of DRBs of different UEs may be aggregated and transmitted on the same BH RLC CH, or may be transmitted on different BH RLC CHs, respectively. Specifically, the mapping relationship between the DRB of the UE and the BH RLC CH depends on the configuration of the CU included in the IAB host.

Currently, for transmitting guaranteed bit rate (guaranteed bit rate, GBR) quality of service (quality of service, qoS) streams, a CU included in an IAB host configures an uplink guaranteed bit rate and a downlink guaranteed bit rate (both are referred to as guaranteed stream bit rates) of the BH RLC CH for a DU included in the IAB host or a DU included in an IAB node. The guaranteed bit rate is the bit rate that the network guarantees to be provided to the QoS flow within an average time window. Therefore, when the IAB host includes DU or IAB node includes DU, the guaranteed bit rate can be consulted to realize fair scheduling between DRBs of different aggregated UE on BH RLC CH carrying GBR QoS flow.

However, for multiple BH RLC CHs carrying non-guaranteed bit rate (non-guaranteed bit rate, non-GBR) quality of service (quality of service, qoS) flows, if the data radio bearers (data radio bearer, DRB) of one UE are aggregated on each BH RLC CH, then each BH RLC CH is fairly scheduled; if different numbers of DRBs of UEs are aggregated on each BH RLC CH and the same number of transmission resources are allocated to the multiple BH RLC CHs, the DRBs of some UEs will be treated unfairly in the BH RLC CH with the greater number of DRBs of the aggregated UEs. For example, for two BH RLC CHs, one BH RLC CH aggregates DRBs of 2 UEs, and the other BH RLC CH aggregates DRBs of 10 UEs, if an IAB host includes a distribution unit that allocates the same number of transmission resources for the two BH RLC CHs at the time of scheduling, the performance of DRBs of some UEs may be affected among the BH RLC CHs that aggregate DRBs of 10 UEs.

The embodiment of the application provides a node scheduling method 100 for downlink transmission. In the method, a DU included in a first node receives first indication information from a CU included in an access backhaul integrated IAB host, wherein the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and a second node, so that the DU included in the first node performs downlink scheduling on the one or more BH RLCs according to the scheduling parameters of the one or more BH RLCs. Wherein the one or more bhrlc CHs are bhrlc CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows, and the scheduling parameters include at least one of bit rate and scheduling level. That is, the DU included in the first node performs downlink scheduling on the one or more BH RLC CHs according to the bit rate and/or the scheduling level on the one or more BH RLC CHs, so as to ensure transmission resources of the BH RLC CHs carrying non-GBRQoS flows, thereby being beneficial to ensuring fair scheduling between data radio bearers DRBs of each terminal device aggregated on the BH RLC CHs.

The embodiment of the application also provides a node scheduling method 200 for uplink transmission. In the method, a distribution unit DU included in a first node receives first indication information from a CU included in an access backhaul integrated IAB, wherein the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and a second node, so that the DU included in the first node performs uplink scheduling on the second node according to the scheduling parameters of the one or more BH RLCs. Wherein the one or more bhrlc CHs are bhrlc CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows, and the scheduling parameters include at least one of bit rate and scheduling level. That is, the DU included in the first node performs uplink scheduling on the second node according to the bit rate and/or the scheduling level on the one or more BH RLC CHs, thereby ensuring transmission resources of the second node, and further being beneficial to ensuring fair scheduling among the one or more BH RLC CHs.

In addition, the DU included in the first node indicates the first priority bit rate and the first priority of one or more logic channels to the MT included in the second node, where the one or more logic channels are in one-to-one correspondence with the one or more BH RLC CHs, so that the MT included in the second node performs a logic channel priority LCP procedure according to the first priority bit rate and the first priority of the one or more logic channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logic channels, thereby ensuring fair scheduling among data radio bearers DRBs of each terminal device aggregated on the BH RLC CHs. Specifically, this embodiment of the present application will be described by taking the node scheduling method 300 as an example.

Examples of the present application and related embodiments are described below with reference to the accompanying drawings.

Referring to fig. 5, fig. 5 is a flowchart of a node scheduling method 100 according to an embodiment of the present application. The node scheduling method 100 is described in terms of interaction between a CU included in an IAB host and a DU included in a first node, and the node scheduling method in downlink transmission is described. The node scheduling method 100 includes, but is not limited to, the steps of:

s101, a centralized unit CU included in an access backhaul integrated IAB host determines first indication information; the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLC CH) between the first node and the second node; one or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows;

wherein the scheduling parameter comprises at least one of a bit rate and a scheduling level. The first node is an IAB host or IAB node and the second node is any one of one or more child nodes of the first node.

S102, a CU included in an IAB host sends first indication information to a DU included in a first node;

s103, receiving first indication information from the CU included in the IAB host by the DU included in the first node;

S104, the DU included in the first node performs downlink scheduling on one or more BH RLC CH according to scheduling parameters of the one or more BH RLC CH.

In S101, the scheduling parameter includes at least one of a bit rate and a scheduling level. That is, the IAB host includes CUs that determine bit rates for the one or more BH RLC CHs, or determine scheduling levels for the one or more BH RLC CHs, or determine bit rates and scheduling levels for the one or more BH RLC CHs. Wherein the scheduling level is a priority for indicating scheduling of one or more BH RLC CHs.

The first indication information determined by the CU included in the IAB host is a scheduling parameter for indicating one or more BH RLC CHs between the first node and the second node. Various implementations of determining the scheduling parameters of the one or more BH RLC CHs by the CUs included in the IAB host are set forth below:

in one implementation, the scheduling parameter of a first BH RLC CH of the one or more BH RLC CHs is determined according to the number of data radio bearers of the terminal device aggregated on the first BH RLC CH, and the first BH RLC CH is any one of the one or more BH RLC CHs. In a possible implementation manner, the larger the number of data radio bearers of the terminal device aggregated on the first BH RLC CH, the larger the scheduling parameter of the first BH RLC CH. The implementation method considers the number of DRBs of the terminal equipment aggregated on the first BH RLC CH, which is beneficial to ensuring that the DRBs of the terminal equipment aggregated on the first BH RLC CH are all scheduled when the DU included by the first node schedules the first BH RLC CH according to the scheduling parameter, namely, is beneficial to realizing fair scheduling among the DRBs of the terminal equipment aggregated on the first BH RLC CH.

For example, the IAB network is shown in fig. 6, where the first node is an IAB host and the second node is an IAB node a. The IAB host and the IAB node a comprise BH RLC CH-a, BH RLC CH-b, BH RLC CH-a and BH RLC CH-b are BH RLC CH for bearing non-GBR QoS flows. The DRB of UE#1 and the DRB of UE#2 are aggregated on the BH RLC CH-a, and the DRB of UE#3 is aggregated on the BH RLC CH-b. Thus, the IAB host may include a CU that determines the bit rate of the BH RLC CH-a to be 2kB/s and the bit rate of the BH RLC CH-b to be 1kB/s.

In another implementation, the scheduling parameter of a first BH RLC CH of the one or more BH RLC CHs is determined according to a QoS parameter of a QoS flow on the first BH RLC CH, where the QoS flow is a QoS flow corresponding to a data radio bearer of a terminal device aggregated on the first BH RLC CH, and the first BH RLC CH is any one of the one or more BH RLC CHs. Wherein the QoS parameters include latency, error rate, etc. The implementation manner considers QoS flow information corresponding to DRB of terminal equipment aggregated on a first BH RLC CH, so that when the first BH RLC CH is scheduled by a DU included in a first node according to scheduling parameters determined in the manner, the problem that DRB of part of terminal equipment aggregated on the first BH RLC CH is not scheduled can be avoided.

For example, as shown in fig. 6, the delay of QoS flows corresponding to DRBs of ue#1 aggregated on BH RLC CH-a is 2s, the delay of QoS flows corresponding to DRBs of ue#2 aggregated is 3s, and the delay of QoS flows corresponding to DRBs of ue#3 aggregated on BH RLC CH-b is 8s. The CU included in the IAB host determines that the delay requirement corresponding to the DRB of the terminal equipment aggregated on the BH RLC CH-a is higher than the delay requirement corresponding to the DRB of the terminal equipment aggregated on the BH RLC CH-b, and then the CU included in the IAB host determines that the bit rate of the BH RLC CH-a is 7kB/s and the bit rate of the BH RLC CH-b is 4kB/s, or the CU included in the IAB host determines that the scheduling level of the BH RLC CH-a is 5 and the scheduling level of the BH RLC CH-b is 2.

In yet another implementation, the scheduling parameters of the plurality of BH RLC CHs between the first node and the plurality of second nodes are determined by a DU included in the first node according to the number of DRBs of the terminal device aggregated on the plurality of BH RLC CHs or QoS parameters of QoS flows on the plurality of BH RLC CHs. That is, the DU included in the first node uniformly determines the scheduling parameters for a plurality of BH RLC CHs according to the number of DRBs of the terminal device aggregated on the plurality of BH RLC CHs between the first node and the plurality of second nodes or QoS parameters of QoS flows on the plurality of BH RLC CHs.

For example, as shown in fig. 7, the first node hosts an IAB, and the second node includes an IAB node a and an IAB node b. The IAB host and the IAB node a comprise BH RLC CH-a and BH RLC CH-b, and BH RLC CH-c is arranged between the IAB host and the IAB node b. The DRB of UE#1 and the DRB of UE#2 are aggregated on the BH RLC CH-a, the DRB of UE#3 is aggregated on the BH RLC CH-b, and the DRB of UE#5 and the DRB of UE#6 are aggregated on the BH RLC CH-c. Therefore, the DU included in the first node device determines that the scheduling levels of the BH RLC CH-a, the BH RLC CH-b and the BH RLC CH-c are 3, 2 and 3 respectively according to the number of DRBs of the terminal device aggregated on each BH RLC CH.

In yet another implementation, the one or more bhrlc CHs are also bhrlc CHs carrying GBR QoS flows. That is, the CU included in the IAB host uniformly determines scheduling parameters for the BH RLC CH carrying the non-GBR QoS flow and the BH RLC CH carrying the GBR QoS flow. Optionally, the CU included in the IAB host determines the scheduling parameters for the multiple BH RLC CHs uniformly according to the number of the DRBs of the terminal device aggregated on the BH RLC CH carrying the non-GBR QoS flow and the BH RLC CH carrying the GBR QoS flow, or the QoS parameters of the QoS flow corresponding to the DRBs of the aggregated terminal device. Optionally, since the requirement of the BH RLC CH carrying the GBR QoS flow for transmitting the service data is higher than the requirement of the BH RLC CH carrying the non-GBR QoS flow, the scheduling parameter of the BH RLC CH carrying the GBR QoS flow determined by the CU included in the IAB host is greater than the scheduling parameter of the BH RLC CH carrying the non-GBR QoS flow.

For example, as shown in fig. 8, the first node is an IAB host, the second node is an IAB node a, and BH RLC CH-a, BH RLC CH-b, and BH RLC CH-c are included between the IAB host and the IAB node a. The BH RLC CH-a and the BH RLC CH-b are BH RLC CH carrying GBR QoS flows, and BH RLC CH-c is BH RLC CH carrying non-GBR QoS flows. The DRB of UE#1 and the DRB of UE#2 are aggregated on the BH RLC CH-a, the DRB of UE#3, the DRB of UE#4 and the DRB of UE#5 are aggregated on the BH RLC CH-b, and the DRB of UE#6 is aggregated on the BH RLC CH-c. So that the bit rates determined by the CU included in the IAB host for the BH RLC CH-a, BH RLC CH-b, and BH RLC CH-c are 2kB/s, 3kB/s, and 1kB/s, respectively. It can be seen that the bit rate of the BH RLC CH-c carrying GBR QoS flows is higher than the bit rates of the BH RLC CH-a, BH RLC CH-b carrying non-GBR QoS flows.

In another implementation manner, the scheduling parameters of a plurality of BH RLC CHs between the first node and the plurality of second nodes are determined by a DU included in the first node according to the number of DRBs of terminal devices aggregated on the plurality of BH RLC CHs, or according to QoS parameters of QoS flows corresponding to DRBs of terminal devices aggregated on each BH RLC CH, where the plurality of BH RLC CHs include a BH RLC CH carrying a non-GBR QoS flow and a BH RLC CH carrying a GBR QoS flow. At this time, the IAB host uniformly determines scheduling parameters for a plurality of BH RLC CHs between the first node and the plurality of second nodes.

For example, as shown in fig. 9, the first node is an IAB node-1 b, the second node includes an IAB node-2 a and an IAB node-2 b, a BH RLC CH-a, a BH RLC CH-b, and a BH RLC CH-c are included between the IAB node-1 b and the IAB node-2 b, a BH RLC CH-d, a BH RLC CH-e, a BH RLC CH-a, a BH RLC CH-b, a BH RLC CH-c is a BH RLC CH carrying non-GBR QoS flows, a BH RLC CH-d, a BH RLC CH-e is a BH RLC CH carrying GBR QoS flows, and an IAB host determines RLC parameters of the BH CH-c, a, BH-QoS, and BH-CH-c according to the number of DRBs of terminal devices aggregated on the BH RLC CH-a, BH RLC CH-c, BH CH-b, BH CH-c, BH CH-d, and BH RLC CH-d, a corresponding to terminal devices aggregated on the BH RLC CH-e. For example, the number of DRBs of the terminal equipment aggregated on the BH RLC CH-a, the BH RLC CH-b, the BH RLC CH-c, the BH RLC CH-d and the BH RLC CH-e is 1, 2 and 3, CU included in the IAB host is BH RLC CH-a, BH RLC CH-b, BH RLC CH-c, BH RLC CH-d and BH RLC CH-e, and the bit rate of each BH RLC CH is determined to be 3kB/s, 6kB/s and 9kB/s respectively.

In this embodiment of the present application, the IAB host includes a first indication message configured by the CU for a DU included in the IAB host or an IAB node including a DU through an F1 interface application protocol (F1-application protocol, F1-AP) message of the above F1 interface. In one implementation, the CU included in the IAB host may perform the configuration of the first indication information in a message for establishing the BH RLC CH or modifying the BH RLC CH.

For S104, the following describes an embodiment in which the DU included in the first node performs downlink scheduling on one or more BH RLC CHs according to the scheduling parameters of the one or more BH RLC CHs:

in one implementation, the scheduling parameter includes a bit rate, and the DU included in the first node performs downlink scheduling on one or more BH RLC CHs according to the bit rate of the one or more BH RLC CHs, including: and scheduling downlink transmission resources for one or more BH RLC CH according to the proportion among the bit rates of the plurality of BH RLC CH. That is, the DU included in the first node schedules downlink transmission resources for one or more BH RLC CHs in an equal proportion according to the proportion between the bit rates of the plurality of BH RLC CHs, thereby ensuring that DRBs of terminal devices aggregated on the one or more BH RLC CHs are all scheduled, i.e. fair scheduling between DRBs of terminal devices aggregated on the BH RLC CHs carrying non-GBR QoS flows is achieved.

For example, as shown in fig. 6, the bit rate of the BH RLC CH-a indicated by the CU included in the IAB host as the DU included in the IAB host is 2kB/s, and the bit rate of the BH RLC CH-b is 1kB/s. That is, the ratio between the bit rate of the BH RLC CH-a and the bit rate of the BH RLC CH-b is 2:1, so that the IAB host comprises a ratio of the downlink transmission resources scheduled for the BH RLC CH-a and the BH RLC CH-b of 2:1. For example, if the DU included in the IAB host schedules a downlink transmission resource of 9kB, the DU included in the IAB host schedules a downlink transmission resource of 6kB for the BH RLC CH-a and a downlink transmission resource of 3kB for the BH RLC CH-b.

In one implementation manner, the scheduling parameters include a scheduling level, and the DU included in the first node performs downlink scheduling on the plurality of BH RLC CHs according to the scheduling level of one or more BH RLC CHs, where the method includes: and scheduling the one or more BH RLC CH according to a scheduling sequence corresponding to the scheduling level of the one or more BH RLC CH.

For example, as shown in fig. 6, the IAB network includes a DU indicated by the IAB node a and a scheduling level of the BH RLC CH-a and the BH RLC CH-b, which are respectively 7 and 3, so that the DU included by the IAB node a determines that the scheduling order of the BH RLC CH-a and the BH RLC CH-b is that the BH RLC CH-a is scheduled first and then the BH RLC CH-b is scheduled.

In another implementation, the CU included in the IAB host determines the scheduling level only for the bhrlc CH carrying the non-GBR QoS flows, but not for the bhrlc CH carrying the non-GBR QoS flows, and when the first node performs downlink scheduling on each bhrlc CH, the first node performs downlink scheduling on the bhrlc CH carrying the GBR QoS flows, and then performs downlink scheduling on the bhrlc CH carrying the non-GBR QoS flows according to the scheduling level of the bhrlc CH carrying the non-GBR QoS flows.

For example, as shown in fig. 8, in the IAB network, the CU included in the IAB host indicates that the DU included in the IAB host does not indicate the scheduling levels of the BH RLC CH-a and the BH RLC CH-b carrying the GBR QoS flow, but indicates that the scheduling level of the BH RLC CH-c carrying the non-GBR QoS flow is 3, then the DU included in the IAB host performs downlink scheduling on the BH RLC CH-a and the BH RLC CH-b first, and then performs downlink scheduling on the BH RLC CH-c.

In still another implementation manner, if the CU included in the IAB host is a scheduling level determined in a unified manner for the BH RLC CH carrying the non-GBR QoS flow and the BH RLC CH carrying the GBR QoS flow, the DU included in the first node performs downlink scheduling on the plurality of BH RLC CHs according to the scheduling levels of the BH RLC CH carrying the non-GBR QoS flow and the BH RLC CH carrying the GBR QoS flow, that is, whether a certain BH RLC CH is the BH RLC CH carrying the GBR QoS flow or not is considered.

In still another implementation manner, the scheduling parameters include a bit rate and a scheduling level, and the DU included in the first node performs downlink scheduling on one or more BH RLC CHs according to the bit rate and the scheduling level of the one or more BH RLC CHs, including: and scheduling downlink transmission resources for the plurality of BH RLCs according to the proportion among bit rates of one or more BH RLCs, and then utilizing the downlink transmission resources of the one or more BH RLCs to perform downlink scheduling for the one or more BH RLCs according to a scheduling sequence corresponding to the scheduling level of the one or more BH RLCs.

For example, as shown in fig. 6, the IAB network indicates that the bit rates of the BH RLC CH-a and the BH RLC CH-b are respectively 5kB/s and 3kB/s for the DU included in the IAB host, the scheduling levels of the BH RLC CH-a and the BH RLC CH-b are respectively 4 and 1, the DU of the IAB host schedules the downlink transmission resource of 8kB to the downlink transmission resource of 5kB for the BH RLC CH-a and schedules the downlink transmission resource of 3kB for the BH RLC CH-b according to the ratio between the bit rates of the BH RLC CH-a and the BH RLC CH-b, then performs downlink scheduling on the BH RLC CH-a by using the downlink transmission resource of 5kB, and then performs downlink scheduling on the BH RLC CH-b by using the downlink transmission resource of 3 kB.

In this embodiment, the DU included in the first node does not limit the downlink scheduling sequence of the DRBs of the terminal device aggregated on each BH RLC CH. Optionally, when the DU included in the first node performs downlink scheduling on the DRBs of the terminal devices aggregated on each BH RLC CH, a first-in first-out (first in first out, FIFO) method may be used to perform downlink scheduling on the DRBs of one or more terminal devices. That is, when the DU included in the first node performs downlink scheduling on the DRBs of the terminal devices aggregated on one BH RLC CH, the DRBs of the terminal devices that arrive first are scheduled first, and then the DRBs of the terminal devices that arrive after the scheduling.

In this embodiment of the present application, a plurality of bhrlc CHs in downlink scheduling of one or more bhrlc CHs by a DU included in a first node refers to a portion of the bhrlc CHs in the plurality of bhrlc CHs between the first node and a second node, that is, a plurality of bhrlc CHs in downlink scheduling of the plurality of bhrlc CHs by a DU included in the first node refers to one or more bhrlc CHs in the bhrlc CHs between the first node and the second node. For example, the first node and the second node include a BH RLC CH-a, a BH RLC CH-b, and a BH RLC CH-c, and the DU included in the first node may perform downlink scheduling on any one of the BH RLC CH-a, the BH RLC CH-b, and the BH RLC CH-c, or may perform downlink scheduling on any two of the BH RLC CH-a, the BH RLC CH-b, and the BH RLC CH-c, or may perform downlink scheduling on all of the BH RLC CH-a, the BH RLC CH-b, and the BH RLC CH-c. The embodiment of the application does not limit the number of the BH RLC CH for downlink scheduling of the DU included in the first node.

It can be seen that, in the embodiment of the present application, the DU included in the first node performs downlink scheduling on the one or more BH RLC CHs according to the bit rate and/or the scheduling level on the one or more BH RLC CHs, so as to ensure transmission resources of the BH RLC CHs carrying non-GBRQoS flows, and further facilitate ensuring fair scheduling between data radio bearers DRBs of each terminal device aggregated on the BH RLC CHs.

The embodiment of the present application also provides a node scheduling method 200, where the node scheduling method 200 describes a node scheduling method in uplink transmission from an interaction angle among a CU included in an IAB host, a DU included in a first node, and an MT included in a second node. Fig. 10 is a flow chart of a node scheduling method 200, the node scheduling method 200 including, but not limited to, the following steps:

s201, a centralized unit CU included in an access backhaul integrated IAB host determines first indication information; the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLC CH) between the first node and the second node; one or more BH RLC CHs are BH RLC CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows;

Wherein the scheduling parameters include at least one of a bit rate and a scheduling level; the scheduling level is a priority for indicating scheduling of the plurality of second BH RLC CHs; the first node is the IAB host or IAB node; the second node is any one of one or more child nodes of the first node.

S202, a CU included in the IAB sends first indication information to a DU included in a first node;

s203, a distribution unit DU included in the first node receives first indication information from a CU included in the access backhaul integrated IAB;

in this embodiment, S201 to S203 are the same as the above-described implementation manners of S101 to S103, and will not be described again.

S204, the DU included in the first node performs uplink scheduling on the second node according to one or more scheduling parameters of the BH RLC CH between the first node and the second node.

In one implementation, the scheduling parameter includes a bit rate, and the DU included in the first node performs uplink scheduling on the second node according to the bit rate of one or more BH RLC CHs between the first node and the second node, including: the DU included by the first node schedules uplink transmission resources for the second node and the third node according to the proportion of the sum of the bit rates of one or more BH RLC CH between the first node and the second node and the sum of the bit rates of one or more BH RLC CH between the first node and the third node; the third node is a node different from the second node among the child nodes of the first node. That is, the DU included in the first node schedules uplink transmission resources for the child nodes of each first node according to the sum of bit rates of one or more BH RLC CHs with each child node, which can ensure fair scheduling between the first node and the one or more BH RLC CHs between the child nodes.

For example, as shown in FIG. 9, the IAB network includes IAB node-1 b, IAB node-2 a, IAB node-1 b and IAB node-2 a, and BH RLC CH-a, BH RLC CH-b, BH RLC CH-c, and BH RLC CH-d, BH RLC CH-e, BH RLC CH-a, BH RLC CH-b, and BH RLC CH-c with bit rates of 1kB/s, BH RLC CH-d, and BH RLC CH-e, respectively, of 2kB/s and 3kB/s. That is, the ratio between the sum of the bit rates of the plurality of BH RLCs between IAB node-1 b and IAB node-2 a and the sum of the bit rates of BH RLCs between IAB node-1 b and IAB node-2 b is 3:5, so that the ratio of the uplink transmission resources scheduled by the DU included in the IAB node-1 for the IAB node-2 a and the IAB node-2 b is also 3:5. for example, if the DU included in the IAB node-1 b schedules 8kB uplink transmission resources, 3kB of the 8kB uplink transmission resources is scheduled to the IAB node-2 a, and 5kB of the 8kB uplink transmission resources is scheduled to the IAB node-2 b.

In another implementation, the scheduling parameter includes a bit rate, and the DU included in the first node performs uplink scheduling on the second node according to the bit rate of one or more BH RLC CHs between the first node and the second node, including: the DU included by the first node performs uplink scheduling on the second node and the third node according to the bit rate of one or more BH RLC CH between the first node and the second node and the bit rate of one or more BH RLC CH between the first node and the third node. In detail, if the bit rate of each of one or more BH RLC CHs between the first node and the second node is greater than the bit rate of each of one or more BH RLC CHs between the first node and the third node, the DU included in the first node performs uplink scheduling on the second node first and then performs uplink scheduling on the third node. The implementation manner can also ensure fair scheduling between one or more BH RLC CHs between the first node and the second node when the DU included in the first node performs uplink scheduling on the second node.

In yet another implementation, the scheduling parameters include a scheduling level, and the scheduling level is determined by the CU included in the IAB host for one or more bhrlc CHs carrying non-GBR QoS flows between the first node and each child node, and then the DU included in the first node performs uplink scheduling on the second node according to the scheduling level of the one or more bhrlc CHs between the first node and the second node, including: the DU of the first node performs uplink scheduling on one or more BH RLCs carrying GBR QoS flows between the first node and the third node, and then performs uplink scheduling on the second node and the fourth node according to the sum of scheduling levels of each BH RLC CH between the first node and the second node and the sum of scheduling levels of each BH RLC CH between the first node and the fourth node.

Wherein the third node and the fourth node are nodes different from the second node in the child nodes of the first node, and one or more BH RLC CHs between the first node and the third node are BH RLC CHs bearing GBR QoS flows, one or more BH RLC CHs between the first node and the second node, and one or more BH RLC CHs between the first node and the fourth node are BH RLC CHs bearing non-GBR QoS flows. If the sum of the scheduling levels of one or more BH RLC CH between the first node and the second node is greater than the sum of the scheduling levels of one or more BH RLC CH between the first node and the fourth node, the DU of the first node performs uplink scheduling on the third node, then performs uplink scheduling on the second node, and finally performs uplink scheduling on the fourth node.

That is, in this implementation manner, the DU included in the first node performs uplink scheduling on the child node corresponding to the bhrlc CH carrying the GBR QoS flow, and then performs uplink scheduling on the child node corresponding to the bhrlc CH carrying the non-GBR QoS flow according to the scheduling level of the bhrlc CH carrying the non-GBR QoS flow.

In yet another implementation, the scheduling parameter includes a scheduling level, where the scheduling level is determined by the CU included in the IAB host in a unified manner for one or more bhrlc CHs carrying non-GBR QoS flows and one or more bhrlc CHs carrying GBR QoS flows between the first node and each child node, and the step of performing uplink scheduling on the second node by using the DU included in the first node according to the scheduling level of the one or more bhrlc CHs between the first node and the second node includes: the DU of the first node determines a scheduling sequence for the second node and the third node according to the sum of the scheduling levels of one or more BH RLC CH between the first node and the second node and the sum of the scheduling levels of one or more BH RLC CH between the first node and the third node, and performs uplink scheduling for the second node and the third node according to the scheduling sequence. The third node is a child node different from the second node among the child nodes of the first node.

That is, in this implementation, the DU of the first node determines the scheduling order of the second node and the third node only according to the sum of the BH RLC CH scheduling levels between the first node and the second node and the size of the sum of the BH RLC CH scheduling levels between the first node and the third node, regardless of whether the BH RLC CH between the first node and the child node is the BH RLC CH carrying the GBR QoS flow or the BH RLC CH carrying the non-GBR QoS flow, and performs uplink scheduling on the second node and the third node according to the scheduling order.

For example, if the sum of the scheduling levels of one or more BH RLC CHs between the first node and the second node is smaller than the sum of the scheduling levels of one or more BH RLC CHs between the first node and the second node, the DU included in the first node performs uplink scheduling on the third node first and then performs uplink scheduling on the second node.

In yet another implementation, the scheduling parameters include a scheduling level, and the DU included in the first node performs uplink scheduling on the second node according to the scheduling level of one or more BH RLC CHs between the first node and the second node, including: the DU included in the first node performs uplink scheduling on the second node and the third node according to the scheduling level of one or more BH RLC CH between the first node and the second node and according to the scheduling level of one or more BH RLC CH between the first node and the third node. The third node is a child node different from the second node among the child nodes of the first node. In detail, if the scheduling level of each BH RLC CH of the one or more BH RLC CHs between the first node and the second node is higher than the scheduling level of each BH RLC CH of the one or more BH RLC CHs between the first node and the third node, the DU included in the first node performs uplink scheduling on the second node first and then performs uplink scheduling on the third node. The implementation manner can also ensure fair scheduling between one or more BH RLC CHs between the first node and the second node when the DU included in the first node performs uplink scheduling on the second node.

In yet another implementation, the scheduling parameters include a bit rate and a scheduling level, and then the DU included in the first node performs uplink scheduling on the second node according to the scheduling level and the bit rate of the one or more BH RLC CHs between the first node and the second node, including: the DU included in the first node schedules uplink transmission resources for the second node and the third node according to the proportion between the sum of bit rates of one or more BH RLCs between the first node and the second node and the sum of bit rates of one or more BH RLCs between the first node and the third node, then determines the scheduling sequence of the second node and the third node according to the sum of scheduling levels of one or more BH RLCs between the first node and the second node and the sum of scheduling levels of one or more BH RLCs between the first node and the third node, and finally utilizes uplink transmission resources of the second node and the third node respectively and performs uplink scheduling for the second node and the third node according to the scheduling sequence of the second node and the third node.

After S104, the DU included in the first node and the MT included in the second node may further perform the following steps, specifically described in the node scheduling method 300. Fig. 11 is a flow chart of a node scheduling method 300.

S301, a DU included in a first node sends second indication information to a mobile terminal MT included in a second node; the second indication information is used for indicating a first priority bit rate and a first priority of one or more logical channels; one or more logical channels are in one-to-one correspondence with one or more BH RLC CHs;

s302, a mobile terminal MT included in the second node receives second indication information from a distribution unit DU included in the first node;

and S303, the MT included in the second node performs a logic channel priority LCP flow according to the first priority bit rate and the first priority of one or more logic channels, and performs uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels.

In S301, one or more logical channels and one or more BH RLC CHs are in one-to-one correspondence with each other, which refers to channel mapping relations between the RLC layer and different protocol layers. The channel between the RLC layer and the MAC layer for transmitting data is called a logical channel, and the channel between the RLC layer and the BAP layer for transmitting data is called a BH RLC CH. A logical channel between the RLC layer and the MAC layer corresponds to a BH RLC CH between the RLC layer and the BAP layer. For example, the channels used for transmitting data between the RLC layer and the MAC layer include a logical channel a, a logical channel b, and a logical channel c, and then there are corresponding BH RLC CH-a, BH RLC CH-b, and BH RLC CH-c in the RLC layer and the BAP layer. Thus, the first priority bit rate and the first priority of the one or more logical channels may be used by the second node to perform LCP procedures and uplink schedule the one or more BH RLC CHs corresponding to the one or more logical channels.

In one implementation, the first priority bit rate and the first priority are determined by the DU included in the first node according to the scheduling parameter, and then the MT included in the second node performs a logical channel priority LCP procedure according to the first priority bit rate and the first priority of one or more logical channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logical channels, including: and carrying out logic channel priority LCP flow according to the first priority bit rate and the first priority of one or more logic channels by utilizing the uplink transmission resource authorized by the DU included by the first node, and carrying out uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels.

In another implementation, the first priority bit rate and the first priority are determined by a DU included in the first node according to information of DRBs of the terminal device aggregated on the BH RLC CH. In this implementation, the MT included in the second node performs a logical channel priority LCP procedure according to the first priority bit rate and the first priority of one or more logical channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logical channels, including: receiving third indication information from the central unit CU comprised by the IAB host, the third indication information being used for indicating a scaling factor of a priority bit rate and a scaling factor of a priority of the one or more logical channels; then, the MT included in the second node determines a second priority bit rate of the one or more logical channels according to the first priority bit rate and a scaling factor of the priority bit rate, and determines a second priority of the one or more logical channels according to the first priority and the scaling factor of the priority; finally, the MT included in the second node performs a logic channel priority LCP flow according to the second priority bit rate and the second priority of the one or more logic channels, and performs uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels.

That is, if the first priority bit rate and the first priority are not the DUs included in the first node, which are determined according to the scheduling parameters, the CU included in the IAB host may indicate the scaling factor regarding the priority bit rate scaling factor and the priority to the MT included in the second node, thereby facilitating the MT included in the second node to obtain the priority bit rate and the priority for performing the LCP procedure according to the priority bit rate scaling factor and the priority scaling factor.

In yet another implementation, the MT included in the second node performs a logic channel priority LCP procedure according to a first priority bit rate and a first priority of one or more logic channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logic channels, including: receiving fourth indication information from a central unit CU included in the IAB host; the fourth indication information is used for indicating a third priority bit rate and a third priority of one or more logic channels; and then, carrying out logic channel priority LCP flow according to the third priority bit rate and the third priority of the one or more logic channels, and carrying out uplink scheduling on one or more BH RLC CH corresponding to the one or more logic channels. That is, in this implementation, the priority bit rate and priority for the second node to perform LCP flows are indicated by the CU included in the IAB host to the MT included in the second node.

In this embodiment, the MT included in the second node does not limit the order of uplink scheduling of DRBs of one or more terminal devices aggregated on one BH RLC CH. Optionally, the MT included in the second node may perform uplink scheduling on the DRBs of the terminal devices aggregated on one BH RLC CH by using a FIFO method. For example, when the BH RLC CH-a between the first node and the second node is aggregated with the DRB of the ue#a and the DRB of the ue#b, and the second node performs uplink scheduling on the BH RLC CH-a, the second node uses the QoS flow corresponding to the DRB of which UE arrives first at the second node, and then the MT included in the second node schedules the DRB of which UE first. For example, when the QoS flow corresponding to the DRB of the ue#b reaches the second node first, the MT included in the second node performs uplink scheduling on the BH RLC CH-a, the QoS flow corresponding to the DRB of the ue#b is first performed uplink scheduling, and then the QoS flow corresponding to the DRB of the ue#a is performed uplink scheduling.

In this embodiment of the present application, the MT included in the second node performs a logical channel priority LCP procedure according to the first priority bit rate and the first priority of one or more logical channels, and performs uplink scheduling on one or more BH RLC CHs corresponding to the one or more logical channels, so that fair scheduling among data radio bearers DRBs of each terminal device aggregated on the BH RLC CHs can be ensured.

In order to implement the functions in the methods provided in the embodiments of the present application, any one of the core network device, the radio access network device, the wireless backhaul device, and the terminal device may include at least one of a hardware structure and a software module, where each function is implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.

As shown in fig. 12, an embodiment of the present application provides a communication apparatus 1200. The communication device 1200 may be a component (e.g., an integrated circuit, a chip, etc.) of a DU included in the first node, a component (e.g., an integrated circuit, a chip, etc.) of a CU included in the IAB host, or a component (e.g., an integrated circuit, a chip, etc.) of an MT included in the second node. The communication device 1200 may also be other communication units for implementing the method in the method embodiments of the present application. The communication apparatus 1200 may include: a communication unit 1201. Optionally, a processing unit 1202 and a storage unit 1203 may also be included.

In one possible design, one or more of the elements of FIG. 12 may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and transceivers; or by one or more processors, memories, and transceivers, to which embodiments of the present application are not limited. The processor, the memory and the transceiver can be arranged separately or integrated.

The communication apparatus 1200 has a function of implementing a DU included in the first node described in the embodiments of the present application, optionally, the communication apparatus 1200 has a function of implementing a CU included in the IAB host described in the embodiments of the present application, and optionally, the communication apparatus 1200 has a function of implementing an MT included in the second node described in the embodiments of the present application. For example, the communication apparatus 1200 includes a module or a unit or means (means) corresponding to the steps of executing the DU included in the first node and included in the first node described in the embodiments of the present application, where the function or the unit or means (means) may be implemented by software, or implemented by hardware, or implemented by executing corresponding software by hardware, or implemented by a combination of software and hardware. Reference is further made in detail to the corresponding description in the foregoing corresponding method embodiments.

In one possible design, a communication device 1200 may include:

a communication unit 1201, configured to receive first indication information from a CU included in an access backhaul integrated IAB host, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CH between a first node and a second node, and the first node is an IAB host or an IAB node;

the processing unit 1202 is further configured to perform downlink scheduling on the one or more BH RLC CHs according to the scheduling parameters of the one or more BH RLC CHs.

In one implementation manner, the scheduling parameter of a first BH RLC CH of the one or more BH RLC CHs is determined according to the number of data radio bearers of the terminal device aggregated on the first BH RLC CH, or is determined according to the QoS parameter of a QoS flow on the first BH RLC CH, where the QoS flow is a QoS flow corresponding to the data radio bearers of the terminal device aggregated on the first BH RLC CH; the first BH RLC CH is any one of the one or more BH RLC CH.

In one implementation, the one or more bhrlc CHs are also bhrlc CHs carrying GBR QoS flows.

In one implementation, the scheduling parameter includes a bit rate, and the processing unit 1202 performs downlink scheduling on the plurality of BH RLC CHs according to the bit rates of the one or more BH RLC CHs, including: and scheduling downlink transmission resources for the plurality of BH RLC CH according to the proportion among the bit rates of the plurality of BH RLC CH.

In another implementation, the scheduling parameter includes a scheduling level, and the processing unit 1202 performs downlink scheduling on one or more BH RLC CHs according to the scheduling level of the one or more BH RLC CHs, including: and carrying out downlink scheduling on the one or more BH RLC CH according to the scheduling sequence corresponding to the scheduling level of the one or more BH RLC CH.

The embodiments of the present application and the embodiments of the method shown in the node scheduling method 100 are based on the same concept, so that the technical effects brought by the embodiments are the same, and the specific principle is that reference is made to the description of the embodiments shown in the node scheduling method 100, and the description is not repeated.

In another possible design, a communication device 1200 may include:

a processing unit 1202 configured to determine first indication information, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CH between a first node and a second node;

A communication unit 1201 for transmitting the first indication information to a DU included in the first node.

In yet another possible design, a communication device 1200 may include:

a communication unit 1201, configured to receive first indication information from a CU included in an access backhaul integrated IAB, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CH between a first node and a second node, and the first node is an IAB host or an IAB node;

a processing unit 1202, configured to perform uplink scheduling on the second node according to the scheduling parameters of the one or more BH RLC CHs.

In one implementation manner, the processing unit 1202 is further configured to send second indication information to a mobile terminal MT included in the second node, where the second indication information is used to indicate a first priority bit rate and a first priority of one or more logical channels, where the one or more logical channels are in one-to-one correspondence with the one or more BH RLC CHs, and the first priority are used by the second node to perform a logical channel priority LCP procedure.

In an implementation manner, the scheduling parameter of a first BH RLC CH of the one or more BH RLC CHs is determined according to the number of data radio bearers of the terminal device aggregated on the first BH RLC CH, or is determined according to the QoS parameter of a QoS flow on the first BH RLC CH, where the QoS flow is a QoS flow corresponding to the data radio bearers of the terminal device aggregated on the first BH RLC CH, and the first BH RLC CH is any one of the one or more BH RLC CHs.

In one implementation, the first priority bit rate and the first priority are determined according to the scheduling parameter.

In one implementation, the scheduling parameter includes a bit rate, and the processing unit 1202 performs uplink scheduling on the second node according to the bit rates of one or more BH RLC CHs between the first node and the second node, and specifically performs the following steps: and scheduling uplink transmission resources for the second node and a third node according to the proportion of the sum of the bit rates of one or more BH RLC CH between the first node and the second node and the sum of the bit rates of one or more BH RLC CH between the first node and the third node, wherein the third node is a node which is different from the second node in the child nodes of the first node.

In another implementation, the scheduling parameter includes a scheduling level, and the processing unit 1202 performs uplink scheduling on the second node according to the scheduling level of one or more BH RLC CHs between the first node and the second node, including: and carrying out uplink scheduling on the second node and the third node according to the scheduling sequence corresponding to the scheduling level of one or more BH RLC CH between the first node and the second node and the scheduling sequence corresponding to the scheduling level of one or more BH RLC CH between the first node and the third node, wherein the third node is a node different from the second node in the child nodes of the first node.

The embodiments of the present application and the embodiments of the method shown in the node scheduling method 200 are based on the same concept, and the technical effects brought by the embodiments are the same, and the specific principles refer to the description of the embodiments shown in the node scheduling method 200 and are not repeated.

In yet another possible design, a communication device 1200 may include:

a communication unit 1201 configured to receive second indication information from a distribution unit DU included in a first node, the second indication information being configured to indicate a first priority bit rate and a first priority of one or more logical channels, the first node being an IAB host or an IAB node, the second node being any one of one or more child nodes of the first node;

Processing unit 1202 is configured to perform a logical channel priority LCP flow according to a first priority bit rate and a first priority of one or more logical channels, and perform uplink scheduling on one or more BH RLC CHs corresponding to the one or more logical channels.

In one implementation manner, the processing unit 1202 performs a logic channel priority LCP flow according to the first priority bit rate and the first priority of the one or more logic channels, and performs uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logic channels, which is specifically configured to perform the following steps: receiving third indication information from a central unit CU included in the IAB host; the third indication information is used for indicating the scaling factors of the priority bit rates and the scaling factors of the priorities of the one or more logical channels; determining a second priority bit rate for the one or more logical channels based on the first priority bit rate and a scaling factor for the priority bit rate, and determining a second priority for the one or more logical channels based on the first priority and the scaling factor for the priority; and carrying out logic channel priority LCP flow according to the second priority bit rate and the second priority of the one or more logic channels, and carrying out uplink scheduling on the one or more BH RLC CH corresponding to the one or more logic channels.

In one implementation manner, the processing unit 1202 performs a logic channel priority LCP flow according to the first priority bit rate and the first priority of the one or more logic channels, and performs uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logic channels, which is specifically configured to perform the following steps: and receiving fourth indication information from a centralized unit CU included in the IAB host, wherein the fourth indication information is used for indicating the third priority bit rate and the third priority of the one or more logic channels, then performing logic channel priority LCP flow according to the third priority bit rate and the third priority of the one or more logic channels, and performing uplink scheduling on the one or more BH RLCs corresponding to the one or more logic channels.

In one implementation manner, the processing unit 1202 performs a logic channel priority LCP flow according to the first priority bit rate and the first priority of the one or more logic channels, and performs uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logic channels, which is specifically configured to perform the following steps: and carrying out logic channel priority LCP flow according to the first priority bit rate and the first priority of the one or more logic channels by utilizing the uplink transmission resources authorized by the DU included by the first node, and carrying out uplink scheduling on the one or more BH RLC CH corresponding to the one or more logic channels.

The embodiments of the present application and the embodiments of the method shown in the node scheduling method 300 are based on the same concept, and the technical effects brought by the embodiments are the same, and the specific principles refer to the description of the embodiments shown in the node scheduling method 300 and are not repeated.

In yet another possible design, a communication device 1200 may include:

In one implementation, the one or more first BH RLC CHs are also BH RLC CHs carrying GBR QoS flows.

In one implementation manner, the communication unit 1201 may further send third indication information to the mobile terminal MT included in the second node; the third indication information is used for indicating the scaling factors of the priority bit rate and the scaling factors of the priority of one or more logic channels; the one or more logical channels are in one-to-one correspondence with the one or more BH RLC CHs.

In one implementation, the communication unit 1201 may further send fourth indication information to the second node; the fourth indication information is used for indicating a third priority bit rate and a third priority of one or more logic channels; the third priority bit rate and the third priority are used for the second node to perform a logical channel priority LCP flow; the one or more logical channels are in one-to-one correspondence with the one or more BH RLC CHs.

The embodiments of the present application and the embodiments of the methods shown in the node scheduling method 200 and the node scheduling method 300 are based on the same concept, so that the technical effects brought by the embodiments of the node scheduling method 200 and the node scheduling method 300 are the same, and the specific principle is referred to the description of the embodiments shown in the node scheduling method 200 and the node scheduling method 300 and will not be repeated.

Fig. 13 shows a schematic structure of a communication device. The communication apparatus 1300 may be a DU included in the first node, a CU included in the IAB host, or an MT included in the second node, a chip system, a processor, or the like that supports the DU included in the first node to implement the method, a chip system, a processor, or the like that supports the CU included in the IAB host to implement the method, or a chip, a chip system, a processor, or the like that supports the MT included in the second node to implement the method. The device can be used for realizing the method described in the method embodiment, and can be particularly referred to the description in the method embodiment.

The communications apparatus 1300 can include one or more processors 1301. The processor 1301 may be a general purpose processor or a special purpose processor, etc. For example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control communication devices (e.g., base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute software programs, and process data of the software programs.

Optionally, the communications apparatus 1300 can include one or more memories 1302 thereon, which can have instructions 1304 executable on the processor 1301 to cause the communications apparatus 1300 to perform the methods described in the method embodiments above. Optionally, the memory 1302 may also store data. The processor 1301 and the memory 1302 may be provided separately or may be integrated.

Optionally, the communications device 1300 may also include a transceiver 1305, an antenna 1306. The transceiver 1305 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc. for implementing a transceiver function. The transceiver 1305 may include a receiver, which may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

The communication apparatus 1300 is a DU included in a first node: the transceiver 1305 is configured to perform S103 in the node scheduling method 100, S203 in the node scheduling method 200, and S301 in the node scheduling method 300; processor 1301 is configured to execute S104 in node scheduling method 100 and to execute S204 in node scheduling method 200.

The communication apparatus 1300 is a CU included in the IAB host: the transceiver 1305 is used for S102 in the node scheduling method 100, and performs S202 in the node scheduling method 200; processor 1301 is configured to execute S101 in node scheduling method 100 and to execute S201 in node scheduling method 200.

The communication apparatus 1300 is an MT included in a second node: the transceiver 1305 is configured to perform S302 in the node scheduling method 300; processor 1301 is configured to perform S303 in node scheduling method 300.

In another possible design, processor 1301 may include a transceiver to implement the receive and transmit functions. For example, the transceiver may be a transceiver circuit, or an interface circuit. The transceiver circuitry, interface or interface circuitry for implementing the receive and transmit functions may be separate or may be integrated. The transceiver circuit, interface or interface circuit may be used for reading and writing codes/data, or the transceiver circuit, interface or interface circuit may be used for transmitting or transferring signals.

In yet another possible design, the processor 1301 may have instructions 1303 stored therein, where the instructions 1303 run on the processor 1301 may cause the communication apparatus 1300 to perform the method described in the above method embodiment. Instructions 1303 may be solidified in processor 1301, in which case processor 1301 may be implemented in hardware.

In yet another possible design, communication device 1300 may include circuitry to implement the functions of transmitting or receiving or communicating of the foregoing method embodiments. The processors and transceivers described in embodiments of the present application may be implemented on integrated circuits (integrated circuit, ICs), analog ICs, radio frequency integrated circuits RFICs, mixed signal ICs, application specific integrated circuits (application specific integrated circuit, ASIC), printed circuit boards (printed circuit board, PCB), electronics, and the like. The processor and transceiver may also be fabricated using a variety of IC process technologies such as complementary metal oxide semiconductor (complementary metal oxide semiconductor, CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (Bipolar Junction Transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication device described in the above embodiment may be a DU included in the first node, a CU included in the IAB host, or an MT included in the second node, but the scope of the communication device described in the embodiment of the present application is not limited thereto, and the structure of the communication device may not be limited by fig. 13. The communication means may be a stand-alone device or may be part of a larger device. For example, the communication device may be:

(1) A stand-alone integrated circuit IC, or chip, or a system-on-a-chip or subsystem;

(2) A set of one or more ICs, optionally including storage means for storing data, instructions;

(3) An ASIC, such as a modem (MSM);

(4) Modules that may be embedded within other devices;

(5) Receivers, terminals, smart terminals, cellular telephones, wireless devices, handsets, mobile units, vehicle devices, network devices, cloud devices, artificial intelligence devices, etc.;

(6) Others, and so on.

For the case where the communication device may be a chip or a chip system, reference may be made to the schematic structural diagram of the chip shown in fig. 14. The chip 1400 shown in fig. 14 includes a processor 1401 and an interface 1402, and may further include a memory 1403. Wherein the number of processors 1401 may be one or more, and the number of interfaces 1402 may be a plurality.

In one design, for the case where the chip is used to implement the function of the DU of the first node in the embodiments of the present application:

the interface 1402 is configured to receive first indication information from a CU included in an access backhaul integrated IAB host, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CHs between a first node and a second node, and the first node is an IAB host or an IAB node;

The processor 1401 is configured to perform downlink scheduling on one or more BH RLC CHs according to scheduling parameters of the one or more BH RLC CHs.

In another design, for the case where the chip is used to implement the function of the DU of the first node in the embodiments of the present application:

the interface 1402 is configured to receive first indication information from a CU included in an access backhaul integrated IAB, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CHs between a first node and a second node, and the first node is the IAB host or an IAB node;

the processor 1401 is configured to perform uplink scheduling on the second node according to scheduling parameters of one or more backhaul radio link control channels BH RLC CH.

Wherein the scheduling parameter includes at least one of a bit rate and a scheduling level, the scheduling level being a priority for indicating scheduling of the one or more BH RLC CHs. The one or more bhrlc CHs are bhrlc CHs carrying non-guaranteed bit rate non-GBR quality of service QoS flows. The second node is any one of one or more child nodes of the first node.

In another design, for the case where the chip is used to implement the function of the CU included in the IAB host in the embodiment of the present application:

the processor 1401 is configured to determine first indication information, where the first indication information is used to indicate scheduling parameters of one or more backhaul radio link control channels BH RLC CH between the first node and the second node;

the interface 1402 is configured to send the first indication information to a DU included in the first node.

Wherein the scheduling parameters include at least one of a bit rate and a scheduling level; the scheduling level is a priority for indicating scheduling of the one or more BH RLC CHs; the one or more BH RLCs are BH RLCs for bearing non-guaranteed bit rate non-GBR quality of service QoS flows; the first node is the IAB host or IAB node; the second node is any one of one or more child nodes of the first node.

In yet another design, for the case where the chip is used to implement the function of the MT included in the second node in the embodiment of the present application:

the interface 1402 is configured to receive second indication information from a distribution unit DU included in a first node, where the second indication information is configured to indicate a first priority bit rate and a first priority of one or more logical channels, and the first node is the IAB host or an IAB node; the second node is any one of one or more child nodes of the first node; the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLC CH) between the first node and the second node; the scheduling parameters include at least one of a bit rate and a scheduling level; the scheduling level is a priority for indicating scheduling of the one or more BH RLC CHs; the one or more BH RLCs are BH RLCs for bearing non-guaranteed bit rate non-GBR quality of service QoS flows; the second node is any one of one or more child nodes of the first node;

the processor 1401 is configured to perform a logical channel priority LCP flow according to a first priority bit rate and a first priority of the one or more logical channels, and perform uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logical channels.

The communication device 1300 and the chip 1400 in the embodiments of the present application may also perform the implementation manner described in the communication device 1200.

Those of skill would further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments herein may be implemented as electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present application.

The embodiments of the present application and the embodiments of the methods shown in the foregoing node scheduling method 100, node scheduling method 200, and node scheduling method 300 are based on the same concept, and the technical effects brought by the embodiments are the same, and the specific principles are described with reference to the embodiments shown in the foregoing node scheduling method 100, node scheduling method 200, and node scheduling method 300, and are not repeated.

It can be understood that some optional features in the embodiments of the present application may be implemented independently in some scenarios, independent of other features, such as the scheme on which they are currently based, so as to solve corresponding technical problems, achieve corresponding effects, or may be combined with other features according to requirements in some scenarios. Accordingly, the communication device provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described herein.

In this application, "transmission" may include the following three cases: data transmission, data reception, or both data transmission and data reception. In this application, "data" may include traffic data, and/or signaling data.

The terms "comprises" or "comprising" and any variations thereof, in this application, are intended to cover a non-exclusive inclusion, such that a process/method comprising a series of steps, or a system/article/apparatus that comprises a series of elements, is not necessarily limited to those steps or elements that are expressly listed or inherent to such process/method/article/apparatus.

In the description of the present application, "at least one" means one or more. "includes at least one of: a, B and C. "means may include A, or B, or C, or A and B, or A and C, or B and C, or A, B and C.

Those of skill would further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments herein may be implemented as electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system.

It should be appreciated that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The present application also provides a computer readable medium storing computer software instructions which, when executed by a communications device, implement the functions of any of the method embodiments described above.

The present application also provides a computer program product for storing computer software instructions which, when executed by a communications device, implement the functions of any of the method embodiments described above.

In the above embodiments, the implementation may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of node scheduling, the method comprising:

the method comprises the steps that a distribution unit DU included in a first node receives first indication information from a CU included in an access backhaul integrated IAB host; the first node is the IAB host or IAB node;

the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLC CH) between the first node and the second node; the scheduling parameters include at least one of a bit rate and a scheduling level; the scheduling level is a priority for indicating scheduling of the one or more BH RLC CHs; the one or more BH RLCs are BH RLCs for bearing non-guaranteed bit rate non-GBR quality of service QoS flows; the second node is any one of one or more child nodes of the first node;

And the DU included in the first node performs downlink scheduling on the one or more BH RLC CH according to the scheduling parameters of the one or more BH RLC CH.
The method of claim 1, wherein the step of determining the position of the substrate comprises,

the scheduling parameters of a first BH RLC CH in the one or more BH RLC CHs are determined according to the number of data radio bearers of the terminal equipment aggregated on the first BH RLC CH, or according to QoS parameters of QoS flows on the first BH RLC CH, where the QoS flows are QoS flows corresponding to the data radio bearers of the terminal equipment aggregated on the first BH RLC CH;

the first BH RLC CH is any one of the one or more BH RLC CH.
The method of claim 1 or 2, wherein the one or more bhrlc CHs are also bhrlc CHs carrying GBR QoS flows.
The method of any of claims 1 to 3, wherein the scheduling parameters include a bit rate, and wherein the DU included in the first node performs downlink scheduling on the one or more BH RLC CHs according to the bit rate of the one or more BH RLC CHs, including:

the DU included by the first node schedules downlink transmission resources for the one or more BH RLC CH according to a ratio between bit rates of the one or more BH RLC CH.
A method of node scheduling, the method comprising:

the centralized unit CU included in the access backhaul integrated IAB host determines first indication information;

the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and the second node; the scheduling parameters include at least one of a bit rate and a scheduling level; the scheduling level is a priority for indicating scheduling of the one or more BH RLC CHs; the one or more BH RLCs are BH RLCs for bearing non-guaranteed bit rate non-GBR quality of service QoS flows; the first node is the IAB host or IAB node; the second node is any one of one or more child nodes of the first node;

and the CU included in the IAB host sends the first indication information to the DU included in the first node.
The method of claim 5, wherein the step of determining the position of the probe is performed,

the scheduling parameters of a first BH RLC CH of the one or more BH RLC CHs are determined according to the number of data radio bearers of the terminal equipment aggregated on the first BH RLC CH, or according to QoS parameters of QoS flows on the first BH RLC CH, where the QoS flows are QoS flows corresponding to the data radio bearers of the terminal equipment aggregated on the first BH RLC CH; the first BH RLC CH is any one of the one or more BH RLC CH.
The method of claim 5 or 6 wherein the one or more bhrlc CHs are also bhrlc CHs carrying GBR QoS flows.
A method of node scheduling, the method comprising:

the method comprises the steps that a distribution unit DU included in a first node receives first indication information from a CU included in an access backhaul integrated IAB; the first node is the IAB host or IAB node;

the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLC CH) between the first node and the second node; the scheduling parameters include at least one of a bit rate and a scheduling level; the scheduling level is a priority for indicating scheduling of the one or more BH RLC CHs; the one or more BH RLCs are BH RLCs for bearing non-guaranteed bit rate non-GBR quality of service QoS flows; the second node is any one of one or more child nodes of the first node;

and the DU included in the first node performs uplink scheduling on the second node according to the scheduling parameters of the one or more BH RLC CH.
The method of claim 8, wherein the method further comprises:

The DU included in the first node sends second indication information to the mobile terminal MT included in the second node; the second indication information is used for indicating a first priority bit rate and a first priority of one or more logic channels; the one or more logical channels are in one-to-one correspondence with the one or more BH RLC CHs; the first priority bit rate and the first priority are used for performing a logical channel priority LCP procedure for an MT included in the second node.
The method according to claim 8 or 9, wherein,

the scheduling parameters of a first BH RLC CH of the one or more BH RLC CHs are determined according to the number of data radio bearers of the terminal equipment aggregated on the first BH RLC CH, or according to QoS parameters of QoS flows on the first BH RLC CH, where the QoS flows are QoS flows corresponding to the data radio bearers of the terminal equipment aggregated on the first BH RLC CH;

the first BH RLC CH is any one of the one or more BH RLC CH.
The method according to any of claims 8 to 10, wherein the one or more bhrlc CHs are also bhrlc CHs carrying GBR QoS flows.
The method according to any of claims 8 to 11, wherein the first priority bit rate and the first priority are determined according to the scheduling parameter.
The method according to any of claims 8 to 12, wherein the scheduling parameters comprise a bit rate; the DU included in the first node performs uplink scheduling on the second node according to the bit rate of one or more BH RLC CHs between the first node and the second node, including:

the DU included by the first node schedules uplink transmission resources for the second node and the third node according to the proportion of the sum of the bit rates of one or more BH RLC CH between the first node and the second node and the sum of the bit rates of one or more BH RLC CH between the first node and the third node;

the third node is a node different from the second node among child nodes of the first node.
A method of node scheduling, the method comprising:

the mobile terminal MT included in the second node receives second indication information from the distribution unit DU included in the first node; the first node is the IAB host or IAB node; the second node is any one of one or more child nodes of the first node;

The second indication information is used for indicating a first priority bit rate and a first priority of one or more logic channels; the one or more logical channels are in one-to-one correspondence with one or more BH RLC CHs between the first node and the second node; the one or more BH RLCs are BH RLCs for bearing non-guaranteed bit rate non-GBR quality of service QoS flows;

and the MT included in the second node performs a logic channel priority LCP flow according to the first priority bit rate and the first priority of the one or more logic channels, and performs uplink scheduling on the one or more BH RLC CH corresponding to the one or more logic channels.
The method of claim 14, wherein the one or more bhrlc CHs are also bhrlc CHs carrying GBR QoS flows.
The method of claim 14 or 15, wherein the MT included in the second node performs a logical channel priority LCP procedure according to a first priority bit rate and a first priority of the one or more logical channels, and performs uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logical channels, including:

The MT included in the second node receives third indication information from the central unit CU included in the IAB host; the third indication information is used for indicating the scaling factors of the priority bit rates and the scaling factors of the priorities of the one or more logical channels;

the MT included by the second node determining a second priority bit rate of the one or more logical channels according to the first priority bit rate and a scaling factor of the priority bit rate, and determining a second priority of the one or more logical channels according to the first priority and the scaling factor of the priority;

and the MT included in the second node performs a logic channel priority LCP flow according to the second priority bit rate and the second priority of the one or more logic channels, and performs uplink scheduling on the one or more BH RLC CH corresponding to the one or more logic channels.
The method of claim 14 or 15, wherein the MT included in the second node performs a logical channel priority LCP procedure according to a first priority bit rate and a first priority of the one or more logical channels, and performs uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logical channels, including:

The MT included in the second node receives fourth indication information from the centralized unit CU included in the IAB host; the fourth indication information is used for indicating a third priority bit rate and a third priority of the one or more logical channels;

and the MT included in the second node performs a logic channel priority LCP flow according to the third priority bit rate and the third priority of the one or more logic channels, and performs uplink scheduling on the one or more BH RLC CH corresponding to the one or more logic channels.
The method according to any one of claims 14 to 15, wherein the MT included in the second node performs a logical channel priority LCP procedure according to the first priority bit rate and the first priority of the one or more logical channels, and performs uplink scheduling on the one or more BH RLC CHs corresponding to the one or more logical channels, including:

and the MT included in the second node performs logic channel priority LCP flow according to the first priority bit rate and the first priority of the one or more logic channels by utilizing uplink transmission resources authorized by the DU included in the first node, and performs uplink scheduling on the one or more BH RLC CH corresponding to the one or more logic channels.
A method of node scheduling, the method comprising:

the centralized unit CU included in the access backhaul integrated IAB host determines first indication information;

the first indication information is used for indicating scheduling parameters of one or more backhaul radio link control channels (BH RLCs) between the first node and the second node; the scheduling parameters include at least one of a bit rate and a scheduling level; the scheduling level is a priority for indicating scheduling of the one or more BH RLC CHs; the one or more BH RLCs are BH RLCs for bearing non-guaranteed bit rate non-GBR quality of service QoS flows; the first node is the IAB host or IAB node; the second node is any one of one or more child nodes of the first node;

and the CU included in the IAB sends the first indication information to the DU included in the first node.
The method of claim 19, wherein the step of determining the position of the probe comprises,

the scheduling parameters of a first BH RLC CH of the one or more BH RLC CHs are determined according to the number of data radio bearers of the terminal equipment aggregated on the first BH RLC CH, or according to QoS parameters of QoS flows on the first BH RLC CH, where the QoS flows are QoS flows corresponding to the data radio bearers of the terminal equipment aggregated on the first BH RLC CH;

The first BH RLC CH is any one of the one or more BH RLC CH.
The method of claim 19 or 20, wherein the one or more bhrlc CHs are also bhrlc CHs carrying GBR QoS flows.
The method according to any one of claims 19 to 21, further comprising:

the CU included in the IAB host sends third indication information to the mobile terminal MT included in the second node; the third indication information is used for indicating the scaling factors of the priority bit rate and the scaling factors of the priority of one or more logic channels; the one or more logical channels are in one-to-one correspondence with the one or more BH RLC CHs.
The method according to any one of claims 19 to 21, further comprising:

the CU included in the IAB host sends fourth indication information to the second node; the fourth indication information is used for indicating a third priority bit rate and a third priority of one or more logic channels; the third priority bit rate and the third priority are used for the second node to perform a logical channel priority LCP flow; the one or more logical channels are in one-to-one correspondence with the one or more BH RLC CHs.
A communication device, characterized in that it comprises means for implementing any of claims 1 to 4.
A communication device, characterized in that it comprises means for implementing any of claims 5 to 7.
A communication device, characterized in that it comprises means for implementing any of claims 8 to 13.
A communication device, characterized in that it comprises means for implementing any of claims 14 to 18.
A communication device, characterized in that it comprises means for implementing any of claims 19 to 23.
A communication device comprising a processor and a communication interface for communicating with other communication devices; the processor is configured to run a program to cause the communication device to implement the method of any one of claims 1 to 4, or to implement the method of any one of claims 5 to 7, or to implement the method of any one of claims 8 to 13, or to implement the method of any one of claims 14 to 18, or to implement the method of any one of claims 19 to 23.
A communication device, comprising: a processor and an interface;

the interface is used for receiving code instructions and transmitting the code instructions to the processor;

the processor for executing the code instructions to perform the method of any one of claims 1 to 4 or for executing the code instructions to perform the method of any one of claims 5 to 7, for executing the code instructions to perform the method of any one of claims 8 to 13, for executing the code instructions to perform the method of any one of claims 14 to 18, for executing the code instructions to perform the method of any one of claims 19 to 23.
A computer readable storage medium storing a computer program comprising at least one piece of code for execution by a communication device to control the communication device to perform the method of any one of claims 1 to 4, or to perform the method of any one of claims 5 to 7, or to perform the method of any one of claims 8 to 13, or to perform the method of any one of claims 14 to 18, or to perform the method of any one of claims 19 to 23.