CN115150965B

CN115150965B - Data scheduling method, device and equipment

Info

Publication number: CN115150965B
Application number: CN202110351906.8A
Authority: CN
Inventors: 文鸣; 刘进华
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-03-31
Filing date: 2021-03-31
Publication date: 2023-06-23
Anticipated expiration: 2041-03-31
Also published as: CN115150965A; WO2022206544A1

Abstract

The application discloses a data scheduling method, a device and equipment, which belong to the technical field of communication, and the method comprises the following steps: the first IAB node receives a BAP control PDU, the first IAB node is a downstream node of the second IAB node, the BAP control PDU is used for indicating whether a topology network accessed by a third IAB node and a fourth IAB node changes, the third IAB node is an upstream IAB node after the second IAB node recovers a wireless link, and the fourth IAB node is an upstream IAB node before the second IAB node recovers the wireless link; and the first IAB node executes corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, wherein the downstream node of the first IAB node is the IAB node or the terminal. In the embodiment of the application, the first IAB node performs corresponding data scheduling operation on the downstream node according to whether the topology network accessed by the node for performing wireless link recovery is changed, so that uplink transmission data is prevented from being lost, and the transmission reliability of the uplink data is improved.

Description

Data scheduling method, device and equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a data scheduling method, device and equipment.

Background

Currently, an integrated wireless access and backhaul (integrated access and backhaul, IAB) node supports type 2/3radio link failure indication (type-2/3radio link failure indication,type-2/3RLF indication), wherein the type 2backhaul radio link failure indication (type-2backhaul radio link failure indication,type-2BH RLF indication) indicates that a radio link failure occurs between one IAB node and its parent IAB node, and notifies a child IAB node of "RLF detected"; type-3BH RLF indication indicates that the radio link recovery is successful after the radio link failure of one IAB node and its parent IAB node, and notifies the child IAB node of the RLF recovery success.

For the scenario that the IAB node and the node performing radio link recovery belong to different IAB hosting Centralized processing units (IAB-donor-Centralized units, IAB-donor-CUs), if the downstream IAB node of the IAB node receives type-3RLF indication, it starts to recover uplink scheduling of UE data, and since an anchor point (anchor point) of a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) is changed from a source CU to a target CU (a key for encrypting data or the like is changed), data that eventually reaches the target CU cannot be successfully decoded by the target CU, and data transmitted by the UE will be lost finally.

Disclosure of Invention

The embodiment of the application provides a data scheduling method, device and equipment, which can solve the problem of unnecessary loss of uplink transmission data after IAB node and wireless link recovery.

In a first aspect, a data scheduling method is provided, the method including:

a first IAB node receives a BAP control PDU, wherein the first IAB node is a downstream node of a second IAB node, the BAP control PDU is used for indicating whether a topology network accessed by a third IAB node and a fourth IAB node is changed, the third IAB node is an upstream IAB node after the second IAB node recovers a wireless link, and the fourth IAB node is an upstream IAB node before the second IAB node recovers the wireless link;

and the first IAB node executes corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, wherein the downstream node of the first IAB node is an IAB node or a terminal. In a second aspect, there is provided a data scheduling apparatus, including:

a receiving module, configured to receive, by a first IAB node, a BAP control PDU, where the first IAB node is a downstream node of a second IAB node, where the BAP control PDU is used to instruct whether a topology network accessed by a third IAB node and a fourth IAB node changes, where the third IAB node is an upstream IAB node after radio link recovery by the second IAB node, and the fourth IAB node is an upstream IAB node before radio link recovery by the second IAB node;

And the first scheduling module is used for the first IAB node to execute corresponding data scheduling operation on the downstream node of the first IAB node according to the BAP control PDU, wherein the downstream node of the first IAB node is an IAB node or a terminal.

In a third aspect, there is provided a terminal comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the steps of the method according to the first aspect.

In a fourth aspect, a terminal is provided, including a processor and a communication interface, where the communication interface is configured to receive a BAP control PDU by a first IAB node, where the first IAB node is a downstream node of a second IAB node, where the BAP control PDU is configured to instruct whether a topology network accessed by a third IAB node and a fourth IAB node changes, where the third IAB node is an upstream IAB node after radio link recovery by the second IAB node, and where the fourth IAB node is an upstream IAB node before radio link recovery by the second IAB node; the processor is configured to perform, by the first IAB node, a corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, where the downstream node of the first IAB node is an IAB node or a terminal.

In a fifth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor realizes the steps of the method according to the first aspect.

In a sixth aspect, there is provided a chip comprising a processor and a communication interface coupled to the processor for running a program or instructions implementing the steps of the method according to the first aspect.

In a seventh aspect, a computer program/program product is provided, the computer program/program product being stored in a non-volatile storage medium, the program/program product being executed by at least one processor to implement the steps of the method as described in the first aspect.

In the embodiment of the application, the first IAB node performs corresponding data scheduling operation on the downstream node according to whether the topology network accessed by the node for performing wireless link recovery is changed, so that uplink transmission data is prevented from being lost, and the transmission reliability of the uplink data is improved.

Drawings

FIG. 1a is a schematic diagram of a conventional IAB system;

FIG. 1b is a schematic diagram of a second conventional IAB system;

FIG. 1c is a third schematic diagram of a conventional IAB system;

FIG. 1d is a diagram illustrating a conventional IAB system;

fig. 1e is a schematic diagram of a structure of a conventional BAP control PDU;

fig. 2 is a flow chart of a data scheduling method according to an embodiment of the present application;

fig. 3a is one of schematic structural diagrams of a BAP control PDU according to an embodiment of the present application;

fig. 3b is a second schematic diagram of a BAP control PDU according to an embodiment of the present application;

fig. 3c is a third schematic diagram of a BAP control PDU according to an embodiment of the present application;

FIG. 3d is a diagram showing a structure of a BAP control PDU according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a data scheduling device according to an embodiment of the present application;

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

fig. 6 is a schematic structural diagram of a first IAB node according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

For a better understanding of the embodiments of the present application, the following description will be first provided:

IAB network

Referring to FIG. 1a, a schematic diagram of an IAB system is shown. An IAB node includes a Distributed Unit (DU) function and a mobile terminal (Mobile Termination, MT) function. By means of MT, an access point (i.e. IAB node) can find an upstream access point (parent IAB node) and establish a wireless connection with the DU of the upstream access point, which wireless connection is called backhaul link. After an IAB node establishes a complete backhaul link, the IAB node opens its DU function, and the DU provides cell service, i.e. the DU may provide access service for the UE. A self-backhaul loop includes an IAB-donor node having a directly connected Cable transport network (Cable transport).

Referring to FIG. 1b, a block diagram of a CU-DU of an IAB system is shown. In a self-backhauling loop, all IAB node DUs are connected to a CU node, which configures the DU via the F1 application protocol (F1 application protocol, F1-AP) protocol. The CU configures the MT through a radio resource control (Radio Resource Control, RRC) protocol. The IAB-donor node has no MT functionality.

The IAB system is introduced to solve the problem that the wired transmission network is not deployed in place when the access points are densely deployed. I.e. without a wired transmission network, the access point may rely on wireless backhaul.

The wireless link between the IAB nodes is called a Backhaul (BH) link, and the BH link is configured with a Backhaul (BH) RLC channel for wireless Backhaul.

The following describes, with reference to the accompanying drawings, a situation that may occur when an IAB node in an IAB network performs radio link recovery:

referring to FIG. 1c, there is shown an IAB network comprising IAB-donor-CU1, IAB-donor-CU2, IAB-donor-DU11, IAB-donor-DU12, IAB-donor-DU2, IAB 1-IAB 6, and UE; wherein IAB-donor-DU11 and IAB-donor-DU12 are under IAB-donor-CU1, IAB-donor-DU2 is under IAB-donor-CU2, IAB1 is under IAB-donor-DU2, IAB2 is under IAB-donor-DU11, IAB3 and IAB4 are under IAB-donor-DU12, IAB5 is a downstream IAB node of IAB4, IAB6 is a downstream IAB node of IAB5, and UE is a downstream node of IAB 6.

If there is a problem with the link between IAB4 and IAB5, i.e. the radio link fails, a radio link recovery is performed, and at this time, IAB5 may recover to any one of IAB1 to IAB4, specifically:

case one: the IAB node and the node for recovering the wireless link belong to the same IAB-donor-DU under the same IAB-donor-CU, namely, intra-IAB-donor-CU intra-IAB-donor-DU;

In case one, IAB5 is restored to IAB3, both IAB3 and IAB4 are under IAB-donor-DU12 under IAB-donor-CU1, and thus belong to intra-IAB-donor-CU, intra-IAB-donor-DU;

and a second case: the IAB node and the node for recovering the wireless link belong to different IAB-donor-DUs under the same IAB-donor-CU, namely intra-IAB-donor-CU and inter-IAB-donor-DUs;

in case two, IAB5 is restored to IAB2, IAB2 and IAB4 are under IAB-donor-CU1, but IAB2 is under IAB-donor-DU11, IAB4 is under IAB-donor-DU12, thus belonging to intra-IAB-donor-CU, inter-IAB-donor-DU;

and a third case: the IAB node and the node for recovering the wireless link belong to different IAB-donor-CUs, namely an inter-IAB-donor-CU;

in case three, IAB5 is restored to IAB1, IAB1 is under IAB-donor-CU2, IAB1 is under IAB-donor-CU1, and thus belongs to inter-IAB-donor-CU;

after the backhaul link between the IAB4 and the IAB5 detects the RLF, the IAB5 sends a type-2RLF indication to the IAB6, if there is a child node below the IAB6, the IAB6 will continue to forward the type-2RLF indication to its child node if there is only a single link, and if the IAB6 has two links and the other link also receives the type-2/4RLF indication, it will also continue to forward the type-2RLF indication to its child node.

BAP Control PDU

A backhaul adaptive protocol control protocol data unit (Backhaul adaptation Protocol control Protocol Data Unit, BAP control PDU) is used to carry control information of the BAP layer. Currently, 4 BAP control PDU types have been defined:

(1) BH RLF indication (also referred to as type-4RLF indication): an IAB node may use the BAP control PDU to inform its child IAB node of a failure to recover the radio link between the IAB node and its parent node;

if the IAB network topology is assumed to be:

IAB1->IAB2->IAB3->IAB-donor-DU->IAB-donor-CU；

assuming that an RLF has occurred on the link between IAB2 and parent node IAB3 and that RLF recovery failed, IAB2 sends BH RLF indication to its child node IAB1 informing IAB1 that a problem has occurred on the link between IAB2 and IAB 3.

(2) Flow control feedback (Flow control feedback per BH RLC channel) for each BH RLC channel: the child IAB node reports the BAP control PDU type of the downlink flow control report to the parent IAB node according to the BH RLC channel;

(3) Flow control feedback (Flow control feedback per BAP routing ID) for each BAP route ID: the sub IAB node reports the BAP control PDU type of the downlink flow control report to the father IAB node according to the BAP routing ID;

(4) Flow control feedback poll (Flow control feedback polling): the father IAB node inquires the child IAB node about the BAP control PDU type of the downlink flow control report, and the father IAB node sends the BAP control PDU type to the child IAB node;

referring to fig. 1d, a header structure of a BAP control PDU is shown:

wherein a PDU Type (PDU Type) field is used to indicate the Type of BAP control PDU, and the existing BAP control PDU Type indication is shown in Table 1:

bit (Bit)	Description (Description)
		0000	Flow control feedback per BH RLC channel
0001	Flow control feedback per BAP routing ID
		0010	Flow control feedback polling
0011	BH RLF indication
		0100-1111	Reserved

TABLE 1

Case of using BAP control PDU:

(1) type-2BH RLF indication: an IAB node fails in radio link with its parent IAB node and notifies the child IAB node of the RLF discovery;

(2) type-3BH RLF indication: after the radio link between one IAB node and the father IAB node fails, the radio link is successfully recovered, and the child IAB node is informed of the successful recovery of the RLF;

the specific prescription is as follows:

(1) RAN2 supports 2/3RLF indication (action TS impact pending, FFS detailed information pending) (RAN 2 to support type-2/3RLF indication (FFS specified behavior(s) TS image, FFS details)).

(2) Type 2RLF indicates that deactivation or reduction of SR and/or BSR transmissions can be used (type-2 RLF indication may be used to trigger deactivation or reduction of SR and/or BSR transmissions).

For the scenario that the IAB node and the node performing radio link recovery belong to different IAB-donor-CUs (inter CUs), if the downstream IAB node of the IAB node receives type-3RLF indication, it starts to recover uplink scheduling of UE data, and since the anchor point of PDCP changes from the source CU to the target CU (a key used to encrypt data, etc. is changed), it may cause that data eventually reaching the target CU cannot be successfully decoded by the target CU, and data sent by the UE will be lost eventually.

The data scheduling method provided by the embodiment of the application is described in detail below through some embodiments and application scenarios thereof with reference to the accompanying drawings.

Referring to fig. 2, an embodiment of the present application provides a data scheduling method, which is characterized in that the method includes:

step 201: the first IAB node receives the BAP control PDU;

step 202: the first IAB node executes corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU;

in this embodiment of the present application, the first IAB node is a downstream node of the second IAB node, and the BAP control PDU is used to indicate whether a topology network accessed by the third IAB node and the fourth IAB node changes, where the third IAB node is an upstream IAB node after the second IAB node performs radio link recovery, and the fourth IAB node is an upstream IAB node before the second IAB node performs radio link recovery; the downstream node of the first IAB node is an IAB node or a terminal.

Specifically, taking the scenario shown in fig. 1c as an example for explanation, the first IAB node in the embodiment of the present application corresponds to IAB6 in fig. 1c, the second IAB node corresponds to IAB5 in fig. 1c, the third IAB node corresponds to any one of IAB1 to IAB4 in fig. 1c (i.e., the second IAB node may restore to any one of IAB1 to IAB4 after radio link restoration), and the fourth IAB node corresponds to IAB4 in fig. 1c (i.e., the second IAB node corresponds to an IAB node downstream of IAB4 before radio link restoration).

It should be noted that, in the embodiment of the present application, the BAP control PDU is used to indicate a change in a topological structure between an IAB node that issues the message and an IAB node that performs radio link recovery, where the topological structure refers to a network deployment, and whether the topology network accessed by the third IAB node and the fourth IAB node changes refers to a change situation of the network deployment after the radio link recovery is performed.

In the embodiment of the application, by designing a BAP control PDU capable of indicating whether the accessed topology network changes, specifically, designing a new type-3RLF indication signaling, the first IAB node can acquire the change condition of the topology network after the wireless link is recovered, and execute the corresponding data scheduling operation, thereby avoiding losing uplink transmission data and improving the transmission reliability of uplink data.

The present embodiments provide several implementations of BAP control PDUs:

embodiment one:

in this embodiment of the present application, the BAP Control PDU includes a first indication field, optionally, as shown in fig. 3a, 1 reserved bit in the header of the existing BAP Control PDU is defined as a topology indication (TI, topology indicator in fig. 3 a), and the change situation of the topology network is indicated by the TI, which is specifically as follows:

(1) When the first indication field is a first value, for example ti=0, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU, which indicates that the topology relationship is "same CU"; when the first indication field is a second value, for example ti=1, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs, which indicates that the topology relationship is "different CUs";

(2) When the first indication field is a first value, for example ti=0, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU, which indicates that the topology relationship is "homodonor-DU"; when the first indication field is a second value, for example ti=1, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs, which indicates that the topology relationship is that the radio link is restored to a new donor-DU, that is, "different donor-DU";

(3) When the first indication field is a first value, for example ti=0, the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are the same IAB node, which indicates that the radio link recovery is successful, and the topology structure is not changed; when the first indication field is a second value, for example ti=1, the BAP control PDU is used to indicate that the third IAB node and the fourth IAB node are different IAB nodes, which indicates that the radio link recovery is successful, but the topology structure has changed;

optionally, the first IAB node performs, according to the BAP control PDU, a corresponding data scheduling operation on a downstream node of the first IAB node, including:

(1) When the first indication field is a first value, e.g., ti=0, the first IAB node resumes uplink scheduling to a downstream node of the first IAB node;

(2) When the first indication field is a second value, for example ti=1, the first IAB node stops uplink scheduling to a node downstream of the first IAB node.

Embodiment two:

n new type-3RLF indications are defined in the PDU type field of the BAP control PDU, indicating different backhaul link recovery situations, for example, N new type-3RLF indications are defined in 0100-1111 reserved from the PDU type field, specifically as follows:

(1) When the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is in the same IAB-donor-DU; when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs under the same IAB-donor-CU; when the PDU type field of the BAP control PDU is a third value, the BAP control PDU is used for indicating that a topology network accessed by a third IAB node and the fourth IAB node is under different IAB-donor-CUs;

that is, 3 new PDU types are selected from reserved 0100-1111, e.g., 0100, 0101 and 0110 are used to represent 3 cases of radio link restoration to original donor-DU, radio link restoration to new donor-DU under control of original CU, and radio link restoration to new donor-DU under control of new CU, respectively.

(2) When the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU; when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs;

That is, 2 new PDU types are selected from reserved 0100-1111, e.g., 0100, 0101 are used to represent 2 cases of restoration to the original and restoration to the new donor-DU, respectively.

(3) When the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU; when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;

that is, 2 new PDU types are selected from reserved 0100-1111, e.g., 0100, 0101 are used to represent 2 cases of restoring to the DONOR DU under the control of the original CU and restoring to the DONOR-DU under the control of the new CU, respectively.

(4) When the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the third IAB node and the fourth IAB node are the same IAB node; when the PDU type field of the BAP control PDU is the second value, the BAP control PDU is used for indicating that the third IAB node and the fourth IAB node are different IAB nodes.

That is, 2 new PDU types are selected, e.g., 0100, 0101 are used to indicate 2 cases where radio link recovery is successful and the topology is unchanged and indicate that radio link recovery is successful but the topology has changed, respectively.

Embodiment III:

in this embodiment of the present application, the BAP Control PDU includes a second indication field, optionally, as shown in fig. 3b, 1 new PDU Type is selected from 0100-1111 reserved in the PDU Type field of the BAP Control PDU, where 0100 indicates that the BAP Control PDU is Type3 RLF indication, and a topology adaptive indication field (Topology adaptation indicator) is newly added in the header of the existing BAP Control PDU, that is, the second indication field, and indicates, through the second indication field, whether the topology relationship changes and/or the information that changes after the radio link is successfully recovered, as follows:

the second indication field in the BAP control PDU is used to indicate any one of the following:

(1) The topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU;

(2) The topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs under the same IAB-donor-CU;

(3) The topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;

alternatively, the second indication field in the BAP control PDU is used to indicate any one of:

(2) The topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs;

(1) The topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU;

(2) The topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;

(1) The third IAB node and the fourth IAB node are the same IAB node;

(2) The third IAB node is a different IAB node than the fourth IAB node.

It should be noted that, the difference between the second embodiment and the third embodiment is that, when the second embodiment is adopted, the first IAB node needs to detect the PDU type field in the BAP control PDU first, and then detect the value of the PDU type field, so as to obtain the topology network condition of the access of the third IAB node and the fourth IAB node, that is, the method includes two steps; in the third embodiment, after the first IAB node detects Topology adaptation indicator in the BAP control PDU, the topology network condition of the access of the third IAB node and the fourth IAB node can be known. That is, in the third embodiment, only 1 new PDU type is adopted in the PDU type field, and no enhancement is performed.

Embodiment four:

in this embodiment of the present application, the BAP control PDU includes a third indication field, where the third indication field is used to indicate to the first IAB node which backhaul link is successfully recovered by the radio link, specifically, the first IAB node may have one or more upstream IAB nodes, taking the scenario shown in fig. 1d as an example, assuming that the IAB5 establishes a connection with the IAB3 and the IAB4 nodes respectively (i.e., the IAB5 is in a dual-connection scenario, its parent node is IAB3 and IAB 4), the backhaul link between the IAB3 and the IAB4 and the IAB5 fails in a radio link, after a period of time, the IAB3 and the IAB5 needs to send the BAP control PDU to the downstream node, if the BAP control PDU does not carry identification information indicating which link is successfully recovered (i.e., the BH link between the IAB3 and the IAB5, or the BH k between the IAB4 and the IAB 5), then the downstream node, such as the IAB6, cannot know which backhaul link is successfully recovered by the specific one after the time, and thus the first backhaul link needs to be successfully recovered.

Specifically, when the third indication field is the target value, the BAP control PDU is used to indicate to the first IAB node that the backhaul link corresponding to the target value is successfully recovered; i.e. the first IAB node can know which backhaul link recovery was successful according to the third indication field.

Wherein the third indication field comprises any one of:

a reserved field in the BAP control PDU;

BAP route identification (BAP routing ID);

a return Link identification (BH Link ID) which is uniformly managed and numbered by an IAB-donor-CU for each Link under a topology network, and is sent to each IAB node through F1AP or RRC signaling;

a Path identifier (Path ID) indicates the transmission Path of a certain packet.

As shown in fig. 3c and 3d, 1 reserved bit in the header of the existing BAP Control PDU is multiplexed, and according to the reserved bit, which backhaul link is successfully recovered is indicated, for example: the reserved bit indicates that the first returned link of the first IAB node and the upstream IAB node is successfully recovered when the reserved bit takes a first value, and indicates that the second returned link of the first IAB node and the upstream IAB node is successfully recovered when the reserved bit takes a second value.

Note that, the BAP routing ID (20 bits) is equal to the Path ID (10 bits) plus the destination ID (10 bits)), that is, BAP routing id=path id+destination ID, where Path ID represents the transmission Path of the packet and destination ID represents the target IAB node to which the packet is to be transmitted.

In some embodiments, the first IAB node performs a corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, including at least one of:

(1) When the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU, that is, indicating that the topology relationship is intra-CU, the first IAB node resumes the uplink scheduling of the downstream node of the first IAB node, or resumes the uplink scheduling of the downstream node of the first IAB node after the IAB-donor-CU performs BAP route configuration reconfiguration or BAP route mapping configuration reconfiguration, or whether to resume the uplink scheduling depends on implementation;

it should be noted that "reconfiguration" in the above-described "BAP route configuration reconfiguration" and "BAP route map configuration reconfiguration" means that one such configuration is received again and then the old configuration is replaced with the new configuration.

BAP routing configuration reconfiguration data for intermediate node transmissions: after receiving the data transmitted by the last IAB node, an IAB node analyzes the data in the BAP layer, and if the destination ID (destination ID) obtained after analysis is the node, the IAB node stops transmitting downwards; if the node is not the node, the next-hop IAB node corresponding to the BAP routing ID carried in the BAP header in the BAP routing configuration is found according to the BAP routing configuration, so that data transmission is performed.

BAP route map configuration is for data from higher layers: if a data packet is generated from a higher layer (higher protocol layer than the BAP layer) of an IAB node, when the BAP layer generates data, the BAP header needs to be filled with a BAP routing ID to indicate where the node needs to transmit, and through which path to transmit, the BAP routing map configuration is used at this time, that is, the BAP routing ID corresponding to the BAP header needs to be filled is found from the BAP routing map configuration according to the packet header of the IP layer.

Whether or not to resume uplink scheduling is implementation dependent (Left to implementation), meaning that specific operations see implementation methods of respective vendors and are not standardized.

(2) When the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs, namely indicating that the topology relationship is inter-IAB-donor-CUs, before the IAB-donor-CUs complete RRC reconfiguration on all terminals served by the first IAB node, the first IAB node stops uplink scheduling on a downstream node of the first IAB node;

(3) When the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU or under different IAB-donor-DUs under the same IAB-donor-CU, that is, indicating that the topology relationship is intra-IAB-donor-CU, intra-IAB-donor-DU or intra-IAB-donor-CU, and inter-donor-DU, the first IAB node resumes the uplink scheduling of the downstream node of the first IAB node, or resumes the uplink scheduling of the downstream node of the first IAB node after the IAB-donor-CU is reconfigured by the BAP routing configuration or the BAP routing mapping configuration, or whether to resume the uplink scheduling depends on implementation.

In some embodiments, the method further comprises:

(1) The first IAB node stops uplink scheduling of a downstream node of the first IAB node;

(2) When the preset condition is met, the first IAB node resumes the uplink scheduling of the downstream node of the first IAB node;

wherein the preset conditions include at least one of the following:

(1) The first IAB node receives the scheduling message from the second IAB node, i.e. if a node is scheduled by an upstream node, the node may start scheduling uplink transmission data of its downstream node.

(2) The IAB-donor-CU completes RRC reconfiguration on all terminals served by the first IAB node;

(3) The downstream node receives a new BAP route configuration or BAP route mapping configuration from the IAB-donor-CU;

(4) The downstream node receives an indication information for recovering the transmission of the uplink data from the IAB-donor-CU, the IAB-donor-DU or the second IAB node.

It should be noted that, in the data scheduling method provided in the embodiments of the present application, the execution body may be a data scheduling device, or a control module in the data scheduling device for executing the data scheduling method. In the embodiment of the present application, a data scheduling device executes a data scheduling method as an example, and the data scheduling device provided in the embodiment of the present application is described.

Referring to fig. 4, a data scheduling apparatus 400 according to an embodiment of the present application includes:

a receiving module 401, configured to receive, by a first IAB node, a BAP control PDU, where the first IAB node is a downstream node of a second IAB node, and the BAP control PDU is configured to instruct whether a topology network accessed by a third IAB node and a fourth IAB node is changed, where the third IAB node is an upstream IAB node after radio link recovery by the second IAB node, and the fourth IAB node is an upstream IAB node before radio link recovery by the second IAB node;

and a first scheduling module 402, configured to execute, by the first IAB node, a corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, where the downstream node of the first IAB node is an IAB node or a terminal.

In some embodiments, the BAP control PDU includes a first indication field;

when the first indication field is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB host centralized processing unit IAB-donor-CU; when the first indication domain is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CU;

Or alternatively, the process may be performed,

when the first indication domain is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same host distribution processing unit IAB-donor-DU; when the first indication domain is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs;

or alternatively, the process may be performed,

when the first indication field is a first value, the BAP control PDU is used for indicating that the third IAB node and the fourth IAB node are the same IAB node; when the first indication field is a second value, the BAP control PDU is used for indicating that the third IAB node and the fourth IAB node are different IAB nodes;

the first scheduling module is further configured to:

when the first indication field is a first value, the first IAB node resumes uplink scheduling to a downstream node of the first IAB node;

and when the first indication domain is a second value, the first IAB node stops uplink scheduling of a downstream node of the first IAB node.

In some embodiments, when the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used to indicate that the topology network accessed by the third IAB node and the fourth IAB node is in the same IAB-donor-DU; when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs under the same IAB-donor-CU; when the PDU type field of the BAP control PDU is a third value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;

Or alternatively, the process may be performed,

when the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU; when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs;

or alternatively, the process may be performed,

when the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU; when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;

or alternatively, the process may be performed,

when the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the third IAB node and the fourth IAB node are the same IAB node; and when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the third IAB node and the fourth IAB node are different IAB nodes.

In some embodiments, the BAP control PDU includes a second indication field;

the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU;

the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs under the same IAB-donor-CU;

the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;

or alternatively, the process may be performed,

the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs;

or alternatively, the process may be performed,

the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU;

Or alternatively, the process may be performed,

the third IAB node and the fourth IAB node are the same IAB node;

the third IAB node and the fourth IAB node are different IAB nodes.

In some embodiments, the first scheduling module is further configured to at least one of:

when the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-CU, the first IAB node resumes uplink scheduling to the downstream node of the first IAB node, or resumes uplink scheduling to the downstream node of the first IAB node after the IAB-donor-CU performs BAP route configuration reconfiguration or BAP route mapping configuration reconfiguration;

when the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs, before the IAB-donor-CU completes radio resource control RRC reconfiguration for all terminals served by the first IAB node, the first IAB node stops uplink scheduling for a downstream node of the first IAB node;

and when the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB-donor-DU or under different IAB-donor-DU under the same IAB-donor-CU, the first IAB node resumes the uplink scheduling of the downstream node of the first IAB node, or resumes the uplink scheduling of the downstream node of the first IAB node after the IAB-donor-CU performs BAP route configuration or BAP route mapping configuration reconfiguration.

In some embodiments, the apparatus further comprises:

the second scheduling module is configured to stop uplink scheduling for a downstream node of the first IAB node by the first IAB node;

the third scheduling module is configured to, when a preset condition is met, resume uplink scheduling for a downstream node of the first IAB node by the first IAB node;

wherein the preset conditions include at least one of:

the first IAB node receives a scheduling message from a second IAB node;

the IAB-donor-CU completes RRC reconfiguration on all terminals served by the first IAB node;

the downstream node receiving a new BAP route configuration or BAP route mapping configuration from the IAB-donor-CU;

and the downstream node receives the instruction information for recovering the uplink data transmission from the IAB-donor-CU, the IAB-donor-DU or the second IAB node.

In some embodiments, the BAP control PDU includes a third indication field;

when the third indication domain is the target value, the BAP control PDU is used for indicating successful return link recovery corresponding to the target value to the first IAB node;

wherein the third indication field comprises any one of the following:

a reserved field in the BAP control PDU;

BAP routing ID；

BH Link ID；

Path ID。

The data scheduling device in the embodiment of the present application may be a device, a device with an operating system or an electronic device, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus or electronic device may be a mobile terminal or a non-mobile terminal. By way of example, mobile terminals may include, but are not limited to, the types of terminals 11 listed above, and non-mobile terminals may be servers, network attached storage (Network Attached Storage, NAS), personal computers (personal computer, PCs), televisions (TVs), teller machines, self-service machines, etc., and embodiments of the present application are not limited in detail.

The data scheduling device provided in the embodiment of the present application can implement each process implemented by the method embodiment of fig. 2, and achieve the same technical effects, so that repetition is avoided, and no further description is provided herein.

Optionally, as shown in fig. 5, the embodiment of the present application further provides a communication device 500, including a processor 501, a memory 502, and a program or an instruction stored in the memory 502 and capable of running on the processor 501, where, for example, the communication device 500 is a terminal, the program or the instruction is executed by the processor 501 to implement each process of the foregoing embodiment of the data scheduling method, and achieve the same technical effects. When the communication device 500 is a network side device, the program or the instruction, when executed by the processor 501, implements the respective processes of the foregoing data scheduling method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

The embodiment of the application also provides a first IAB node, which comprises a processor and a communication interface, wherein the communication interface is used for the first IAB node to receive a BAP control PDU, the first IAB node is a downstream node of a second IAB node, the BAP control PDU is used for indicating whether a topology network accessed by a third IAB node and a fourth IAB node changes, the third IAB node is an upstream IAB node after radio link recovery of the second IAB node, and the fourth IAB node is an upstream IAB node before radio link recovery of the second IAB node; the processor is configured to perform, by the first IAB node, a corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, where the downstream node of the first IAB node is an IAB node or a terminal. The network side device embodiment corresponds to the network side device method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

Specifically, the embodiment of the application also provides a first IAB node. As shown in fig. 6, the first IAB node 600 includes: an antenna 61, a radio frequency device 62, a baseband device 63. The antenna 61 is connected to a radio frequency device 62. In the uplink direction, the radio frequency device 62 receives information via the antenna 61, and transmits the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes information to be transmitted, and transmits the processed information to the radio frequency device 62, and the radio frequency device 62 processes the received information and transmits the processed information through the antenna 61.

The above-described band processing means may be located in the baseband means 63, and the method performed by the first IAB node in the above embodiment may be implemented in the baseband means 63, the baseband means 63 comprising a processor 64 and a memory y5.

The baseband apparatus 63 may, for example, comprise at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 6, where one chip, for example, a processor 64, is connected to a memory 65 to invoke a program in the memory 65 to perform the network device operations shown in the above method embodiment.

The baseband apparatus 63 may also include a network interface 66 for interacting with the radio frequency apparatus 62, such as a common public radio interface (common public radio interface, CPRI for short).

Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 65 and executable on the processor 64, the processor 64 calls the instructions or programs in the memory 65 to execute the method executed by each module shown in fig. 6, and achieve the same technical effects, and are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the embodiment of the data scheduling method, and the same technical effect can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used for running a program or an instruction, so as to implement each process of the embodiment of the data scheduling method, and achieve the same technical effect, so that repetition is avoided, and no redundant description is provided here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method for scheduling data, comprising:

the method comprises the steps that a first wireless access and backhaul integrated IAB node receives a backhaul self-adaptive protocol control protocol data unit (BAP control PDU), wherein the first IAB node is a downstream node of a second IAB node, the BAP control PDU is used for indicating whether a topology network accessed by a third IAB node and a fourth IAB node changes, the third IAB node is an upstream IAB node after wireless link recovery of the second IAB node, and the fourth IAB node is an upstream IAB node before wireless link recovery of the second IAB node;

and the first IAB node executes corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, wherein the downstream node of the first IAB node is an IAB node or a terminal.

2. The method of claim 1, wherein the BAP control PDU includes a first indication field;

Or alternatively, the process may be performed,

when the first indication field is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under the same IAB host distribution processing unit IAB-donor-DU; when the first indication domain is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs;

or alternatively, the process may be performed,

the first IAB node executes corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, including:

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

when the PDU type field of the BAP control PDU is a first value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is in the same IAB-donor-DU; when the PDU type field of the BAP control PDU is a second value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-DUs under the same IAB-donor-CU; when the PDU type field of the BAP control PDU is a third value, the BAP control PDU is used for indicating that the topology network accessed by the third IAB node and the fourth IAB node is under different IAB-donor-CUs;

or alternatively, the process may be performed,

Or alternatively, the process may be performed,

or alternatively, the process may be performed,

4. The method of claim 1, wherein the BAP control PDU includes a second indication field;

or alternatively, the process may be performed,

the third IAB node and the fourth IAB node are the same IAB node;

the third IAB node and the fourth IAB node are different IAB nodes.

5. The method according to any of claims 2 to 4, wherein the first IAB node performs a corresponding data scheduling operation on a downstream node of the first IAB node according to the BAP control PDU, comprising at least one of:

6. The method according to claim 4, wherein the method further comprises:

the first IAB node stops uplink scheduling of a downstream node of the first IAB node;

when a preset condition is met, the first IAB node resumes uplink scheduling to a downstream node of the first IAB node;

wherein the preset conditions include at least one of:

the first IAB node receives a scheduling message from a second IAB node;

7. The method of claim 1, wherein the BAP control PDU includes a third indication field;

wherein the third indication field comprises any one of the following:

a reserved field in the BAP control PDU;

BAP route identification BAP routing ID;

returning a Link ID (BH Link ID);

path identification Path ID.

8. A data scheduling apparatus, comprising:

9. The apparatus of claim 8, wherein the BAP control PDU comprises a first indication field;

Or alternatively, the process may be performed,

or alternatively, the process may be performed,

the first scheduling module is further configured to:

10. The apparatus of claim 8, wherein the device comprises a plurality of sensors,

or alternatively, the process may be performed,

Or alternatively, the process may be performed,

11. The apparatus of claim 8, wherein the BAP control PDU includes a second indication field;

or alternatively, the process may be performed,

Or alternatively, the process may be performed,

or alternatively, the process may be performed,

the third IAB node and the fourth IAB node are the same IAB node;

the third IAB node and the fourth IAB node are different IAB nodes.

12. The apparatus according to any one of claims 9 to 11, wherein the first scheduling module is further configured to at least one of:

13. The apparatus of claim 11, wherein the apparatus further comprises:

a second scheduling module, configured to stop uplink scheduling for a downstream node of the first IAB node by the first IAB node;

the third scheduling module is used for enabling the first IAB node to resume uplink scheduling of a downstream node of the first IAB node when a preset condition is met;

Wherein the preset conditions include at least one of:

the first IAB node receives a scheduling message from a second IAB node;

14. The apparatus of claim 8, wherein the BAP control PDU includes a third indication field;

wherein the third indication field comprises any one of the following:

a reserved field in the BAP control PDU;

BAP routing ID；

returning a Link ID (BH Link ID);

Path ID。

15. a first IAB node comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which program or instruction when executed by the processor implements the steps of the data scheduling method of any one of claims 1 to 7.

16. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, implement the steps of the data scheduling method of any one of claims 1 to 7.