CN115996418A - BH RLC CH remapping method and device - Google Patents

Abstract

The present application discloses a BH RLC CH remapping method and device. The BH RLC CH remapping method includes: the first backhaul node receives the first message sent by the second backhaul node, and the first message includes the first backhaul Target information of at least one BH RLC CH on the link, the first backhaul link is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least the ID of the BH RLC CH; A backhaul node determines according to the target information that the first BH RLC CH in the at least one BH RLC CH needs to be remapped; the first backhaul node determines a second BH RLC CH, and the second BH RLC CH is the first backhaul chain BH RLC CH on the road; the first backhaul node remaps the data to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission.

Description

BH RLC CH remapping method and device

technical field

This application belongs to the technical field of wireless communication, and specifically relates to a BH RLC CH remapping method and device.

Background technique

Integrated access and backhaul (IAB, integrated access and backhaul) system is a technology that New Radio (NR) Rel-16 started to formulate standards. Fig. 1 shows a schematic structural diagram of an IAB system, and Fig. 2 shows a schematic structural diagram of a centralized unit-distributed unit (Centralized Unit-Distributed Unit, CU-DU) of an IAB system, and an IAB node includes a distributed unit (Distributed Unit, DU) function part and mobile terminal (Mobile Termination, MT) function part, relying on MT, an access IAB node (ie IAB node) can find an upstream IAB node (parent IAB node), and establish a wireless connection with the DU of the upstream IAB node The wireless connection is called a backhaul link (Backhaul (BH) link). After an IAB node establishes a complete backhaul link, the IAB node opens its DU function, and the DU will provide cell services, that is, the DU can provide access services for the terminal (User Equipment, UE). A backhaul link includes a donor (donor) IAB node (or called IAB donor), and the donor IAB node has a directly connected cable transport network (Cable transport). In a backhaul link, the DUs of all IAB nodes are connected to a Centralized Unit (CU) node, and this node configures the DUs through the F1-AP protocol. The CU configures the MT through the RRC protocol. Donor IAB node does not have MT functional part.

The introduction of the IAB system is to solve the situation that the wired transmission network is not properly deployed when the access points are densely deployed. That is, when there is no wired transmission network, the access point can rely on wireless backhaul.

The wireless link between IAB nodes is called a backhaul link, and a backhaul link radio link control channel (BH RLC CH) is configured on the backhaul link for wireless backhaul.

In related technologies, if a certain backhaul link has a problem, another backhaul link may be used to offload data transmission, which is also called re-routing.

At present, in related technologies, data can be re-routed at the granularity of per BAP routing ID. Please refer to Figure 3. Figure 3 is a schematic diagram of the method for rerouting data at the granularity of per BAP routing ID in the IAB system. If There is a problem with the BAP routing ID1 link between IAB node 2 (IAB2) and the downstream IAB node (IAB4), and the data transmitted according to BAP routing ID1 can be rerouted to the route of BAP routing ID2.

The rerouting scheme for BH RLC CH is similar to BAP routing ID, that is, data is transferred (rerouted) from one backhaul link to another backhaul link to ease the congestion of data transmission. However, the above rerouting scheme cannot be used in the following situations:

1) When the IAB node has only one output link (egress link);

2) When the IAB node has multiple egress links, but the alternative BAProuting ID cannot be found on other egress links;

3) When no alternative BH RLC CH is configured on other egress links of the IAB node.

Thus, the normal transmission of BH RLC CH data cannot be guaranteed.

Contents of the invention

The embodiment of the present application provides a BH RLC CH remapping method and device, which can solve the problem that the normal transmission of BH RLC CH data cannot be guaranteed when rerouting data at the granularity of per BH RLC CH.

In the first aspect, a BH RLC CH remapping method is provided, including:

The first backhaul node receives the first message sent by the second backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link is For a backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the identity ID of the BH RLC CH;

The first backhaul node determines, according to the target information, that the first BHRLC CH in the at least one BH RLC CH needs to be remapped;

The first backhaul node determines a second BH RLC CH, and the second BH RLC CH is the BH RLC CH on the first backhaul link;

The first backhaul node remaps the data that needs to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission.

In the second aspect, a BH RLC CH remapping method is provided, which also includes:

The second backhaul node sends a first message to the first backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link is the first backhaul link A backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the ID of the BH RLC CH, and the first message is used to indicate the at least one BH RLC Whether CH needs to be remapped.

In a third aspect, a BH RLC CH remapping device is provided, including:

The first receiving module is configured to receive the first message sent by the second backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link The path is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least the ID of the BH RLC CH;

A first determining module, configured to determine, according to the target information, that the first BHRLC CH in the at least one BH RLC CH needs to be remapped;

The second determination module is configured to determine a second BH RLC CH, where the second BH RLC CH is the BH RLC CH on the first backhaul link;

A remapping module, configured to remap data that needs to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission.

In a fourth aspect, a BH RLC CH remapping device is provided, including:

The first sending module is configured to send a first message to a first backhaul node, where the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link is a backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the ID of the BH RLC CH, and the first message is used to indicate the at least one Whether BH RLC CH needs to be remapped.

According to a fifth aspect, a backhaul node is provided. The terminal includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor. The program or instruction is executed by the processor When executed, the steps of the method described in the first aspect or the second aspect are realized.

In a sixth aspect, a backhaul node is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first message sent by a second backhaul node, and the first message includes the first backhaul Target information of at least one BHRLC CH on the link, the first backhaul link is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least The ID of the BH RLC CH; the processor is configured to determine, according to the target information, that the first BH RLC CH in the at least one BH RLC CH needs to be remapped; determine a second BH RLC CH, and the second The BH RLC CH is the BH RLC CH on the first backhaul link; remapping the data that needs to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission.

In a seventh aspect, a backhaul node is provided, including a processor and a communication interface, wherein the communication interface is used to send a first message to the first backhaul node, and the first message includes the first backhaul link Target information of at least one BH RLCCH on the road, the first backhaul link is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least the The ID of the BH RLC CH, the first message is used to indicate whether the at least one BHRLC CH needs to be remapped.

In the eighth aspect, a readable storage medium is provided, and programs or instructions are stored on the readable storage medium, and when the programs or instructions are executed by a processor, the steps of the method described in the first aspect are realized, or the steps of the method described in the first aspect are realized, or The steps of the method described in the second aspect.

A ninth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run programs or instructions, and implement the method as described in the first aspect , or implement the method described in the second aspect.

In a tenth aspect, a computer program/program product is provided, the computer program/program product is stored in a non-transitory storage medium, and the computer program/program product is executed by at least one processor to implement the first The steps of the method described in the second aspect, or the program/program product is executed by at least one processor to implement the steps of the method described in the second aspect.

In the embodiment of this application, when the BH RLC CH needs to be remapped (for example, when congestion occurs), the IAB node can remap the data transmitted by the BH RLC CH that needs to be remapped to another BH on the same backhaul link For transmission on RLCCH, even if the IAB node has only one output link (egress link) or has multiple egress links, it cannot find a replacement BAP routing ID on other egress links or there is no replacement BH configured on other egress links of the IAB node When using RLC CH, the normal transmission of BH RLC CH data can be guaranteed.

Description of drawings

FIG. 1 is a schematic structural diagram of the IAB system;

FIG. 2 is a schematic diagram of the CU-DU structure of the IAB system;

Fig. 3 is a schematic diagram of a method for rerouting data at the granularity of per BAP routing ID in the IAB system;

FIG. 4 is a schematic flow diagram of a BH RLC CH remapping method according to an embodiment of the present application;

5 is a schematic diagram of the F1-U protocol stack of the IAB system;

Figure 6 is a schematic diagram of the format of the flow control message based on the BH RLC CH;

Figure 7 is a schematic diagram of the format of the flow control message based on the BAP routing ID

Fig. 8 is a schematic diagram of sending a flow control message of the IAB system;

FIG. 9 is a schematic diagram of a BH RLC CH remapping method in Embodiment 1 of the present application;

FIG. 10 is a schematic diagram of a BH RLC CH remapping method according to another embodiment of the present application;

FIG. 11 is a schematic structural diagram of a BH RLC CH remapping device according to an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a BH RLC CH remapping device according to another embodiment of the present application;

FIG. 13 is a schematic structural diagram of a backhaul node in an embodiment of the present application;

FIG. 14 is a schematic diagram of a hardware structure of a backhaul node according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of them. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments in this application belong to the protection scope of this application.

The terms "first", "second" and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. 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 described herein and that "first" and "second" distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects. In addition, "and/or" in the description and claims means at least one of the connected objects, and the character "/" generally means that the related objects are an "or" relationship.

It is worth pointing out that the technology described in the embodiment of this application is not limited to the Long Term Evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can 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 (OFDMA) , Single-carrier Frequency-Division Multiple Access (Single-carrier Frequency-Division Multiple Access, SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technologies can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies. The following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 ^th Generation, 6G) communication system.

The following describes in detail the BH RLC CH remapping method and device provided in the embodiments of the present application through some embodiments and application scenarios in conjunction with the accompanying drawings.

Please refer to Figure 4, the embodiment of the present application provides a BH RLC CH remapping method, including:

Step 41: The first backhaul node receives the first message sent by the second backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul The link is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least an identity (Identity Document, ID) of the BH RLC CH;

The first backhaul node and the second backhaul node may be IAB nodes and/or IAB-donor-DU nodes. For example, one of the first backhaul node and the second backhaul node is an IAB-donor-DU, and the other is an IAB node.

The first backhaul link is configured with at least two BH RLC CHs, and each BH RLC CH has a unique ID for identifying the BH RLC CH.

Step 42: The first backhaul node determines, according to the target information, that the first BH RLC CH in the at least one BH RLC CH needs to be remapped;

Step 43: The first backhaul node determines a second BH RLC CH, and the second BH RLC CH is the BH RLC CH on the first backhaul link;

Step 44: The first backhaul node remaps the data to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission.

In the embodiment of this application, when the BH RLC CH needs to be remapped (for example, when congestion occurs), the IAB node can remap the data transmitted by the BH RLC CH that needs to be remapped to another BH on the same backhaul link For transmission on RLCCH, even if the IAB node has only one output link (egress link) or has multiple egress links, it cannot find a replacement BAP routing ID on other egress links or there is no replacement BH configured on other egress links of the IAB node When using RLC CH, the normal transmission of BH RLC CH data can be guaranteed.

In this embodiment of the present application, optionally, the first message is a flow control (Flow Control, FC) message. Using the information in the existing flow control message to determine whether the BH RLC CH needs to be remapped, the system changes are small and the cost is low.

The flow control message is briefly introduced below.

At Rel-16, 3GPP agreed to adopt a flow control mechanism in the IAB network to solve the data congestion during downlink transmission (The DL hop-by-hop flow control is supported in IAB network). The data congestion during downlink transmission refers to IAB The data received by the node from its parent IAB node is too late to be sent to the downstream node or UE, resulting in data accumulation. When the data accumulates to the risk of buffer overflow, it will send a flow control (Flow Control, FC) feedback (congested IAB node feedback flow control info to its parent IAB node) to warn of congestion, and the IAB node that receives the flow control feedback will control the transmission rate of downlink data sent to the child IAB node.

The minimum feedback granularity of flow control information can be based on BH RLC CH or BAP routing ID.

Backhaul Adaptation Protocol (BAP) is a newly introduced protocol layer in the IAB system, which is used for data forwarding, data packet routing, flow control, etc. The specific protocol stack is shown in Figure 5.

Please refer to Figure 6 and Figure 7. Figure 6 is a schematic diagram of the format of the flow control message based on BH RLC CH, and Figure 7 is a schematic diagram of the format of the flow control message based on BAProuting ID. It can be seen from Figure 6 that the flow control message can carry at least one BHRLC CH ID and available buffer size (Available Buffer Size).

In addition, there are two different types of flow control information in the IAB technology, namely event-triggered flow control information and polling-based flow control information. Based on event triggering, the IAB child node actively sends flow control information to the IAB parent node when the data accumulation reaches a certain threshold; based on polling triggering, the IAB parent node sends polling to the IAB child node when it expects to understand the complex situation of the child node cache message to trigger the IAB child node to send polling flow control information to its parent node.

The flow control message in this embodiment of the present application may be event-based flow control information, or may be polling-based flow control information.

If the flow control message in the embodiment of the present application is based on event-triggered flow control information, the flow control message in the embodiment of the present application may only carry the BH RLC CH whose data accumulation on the first backhaul link reaches a certain threshold, It can also carry all BH RLC CHs on the first backhaul link. If the flow control message in the embodiment of the present application is based on the flow control information triggered by polling, the flow control message in the embodiment of the present application carries all BH RLC CHs on the first backhaul link.

A specific example of flow control feedback is shown in Figure 8. The IAB donor node can send downlink data to the UE through IAB node 1, IAB node 2, and IAB node 3. Once the feedback between IAB node 2 and IAB node 3 If the link encounters link congestion, then IAB node 2 will send a flow control message to its upstream node, that is, IAB node 1. After receiving the flow control message, IAB node 1 will stop or reduce sending new downlink messages to IAB node 2. data.

In the embodiment of the present application, optionally, the target information also includes the available buffer capacity of the BH RLC CH; the method further includes:

The first backhaul node judges whether the BH RLC CH needs to be remapped according to whether the available buffer capacity of the BH RLC CH is less than or equal to a first threshold;

If the available buffer capacity of the BH RLC CH is less than or equal to the first threshold, the first backhaul node determines that the BH RLC CH needs to be remapped.

That is to say, the BH RLC CH whose available buffer capacity is less than or equal to the first threshold is the BH RLC CH that needs to be remapped.

In this embodiment of the present application, optionally, the first threshold is predefined by a protocol or preconfigured by a network (CU).

In this embodiment of the present application, optionally, the first thresholds corresponding to each BH RLC CH are the same or different.

In the embodiment of the present application, optionally, the first message may also be a newly introduced message dedicated to the remapping process, that is, the first message is used to carry the target information of the BH RLC CH that needs to be remapped message, after the first return node receives the first message, it considers that the BH RLC CHs in the first message are all BH RLC CHs that need to be remapped.

In this embodiment of the present application, optionally, determining the second BH RLC CH includes: the first backhaul node selects that the transmission priority on the first backhaul link is lower than or equal to the first BH RLC CH The BH RLC CH with the transmission priority that can be remapped is used as the second BH RLC CH.

In this embodiment of the present application, optionally, the transmission priority of each BH RLC CH on the first backhaul link is configured by the IAB owner centralized unit (CU). Specifically, it can be configured through F1AP signaling or RRC signaling when establishing each BH RLC CH.

In this embodiment of the present application, optionally, the BH RLC CH that can be remapped is a BH RLC CH whose available buffer capacity is greater than the first threshold.

In the embodiment of this application, optionally, determining the second BH RLC CH includes:

If there are at least two second BH RLC CHs, the first backhaul node performs one of the following operations:

From the at least two second BH RLC CHs, selecting the second BH RLCCH with the lowest transmission priority as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, select the second BHRLC CH with the largest available buffer capacity as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, select the second BH RLCCH with the least remapping times as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, randomly select one of the second BH RLC CHs as the second BH RLC CH for remapping.

In the embodiment of the present application, a remapping times counter may be configured for each second BH RLC CH, that is, each said second BH RLC CH corresponds to one said remapping times counter, if the second BH RLC CH is selected For remapping, the first backhaul node adds one to the count of the remapping times counter of the second BH RLC CH used for remapping.

In this embodiment of the present application, optionally, the remapping times counter starts counting from 0, and is cleared to zero when the second BHRLC CH cannot be remapped.

In this embodiment of the present application, optionally, after remapping the data that needs to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission, it also includes:

If at least one of the following conditions is met, the first backhaul node stops the remapping of the first BH RLC CH:

All the second BH RLC CHs corresponding to the first BH RLC CH cannot be remapped;

The first BH RLC CH does not need to be remapped.

In this embodiment of the present application, optionally, the second BH RLC CH that cannot be remapped is a BH RLC CH whose available buffer capacity is less than or equal to the first threshold.

In this embodiment of the present application, optionally, the first BH RLC CH that does not need to be remapped is a BH RLC CH whose available buffer capacity is greater than the first threshold.

In this embodiment of the present application, optionally, the BH RLC CH remapping method further includes: the first backhaul node judging whether the first BH RLC CH does not need to be remapped.

In this embodiment of the present application, optionally, the first backhaul node judging whether the first BH RLC CH does not need to be remapped includes:

The first backhaul node receives the second message sent by the second backhaul node, and the second message includes the target information of the first BH RLC CH;

The first backhaul node determines whether the first BH RLC CH does not need to be remapped according to the target information of the first BH RLC CH in the second message.

The second message may be a newly introduced message dedicated to sending the first BH RLC CH that does not need to be remapped.

In this embodiment of the present application, optionally, the target information in the second message further includes the available buffer capacity of the BH RLC CH; The target information of the BH RLC CH, judging whether the first BH RLC CH does not need to be remapped includes:

The first backhaul node judges whether the first BH RLC CH does not need to be remapped according to whether the available buffer capacity of the first BH RLC CH is greater than or equal to the second threshold (this method is passive contact remap);

If the available buffer capacity of the first BH RLC CH is greater than or equal to the second threshold, the first backhaul node determines that the first BH RLC CH does not need to be remapped (this method is active contact remap).

In this embodiment of the present application, optionally, the second threshold is predefined by a protocol or preconfigured by a network.

In this embodiment of the present application, optionally, the second thresholds corresponding to each of the first BH RLC CHs are the same or different.

The following describes the BH RLC CH remapping method in the above embodiment in combination with specific application scenarios.

Embodiment 1: Selection of the second BH RLC CH

In this embodiment, please refer to Figure 9. There are two backhaul links between IAB1 and IAB4, namely BH link1 and BH link2. The IAB nodes on BH link1 include: IAB1, IAB2 and IAB4, and the IAB on BH link2 The nodes include: IAB1, IAB3 and IAB4. There are 5 BH RLC CHs on BH link1, namely BH RLC CH1, BH RLC CH2, BH RLCCH3, BH RLC CH4 and BH RLC CH5.

IAB1 receives the downstream flow control (DLFC) message sent by IAB2, combined with the DLFC message IAB1 can draw Table 1 (the first two columns are the target information carried by DLFC, and the last two columns are the information that the IAB1 node itself can know):

Table 1

The IAB1 node can enable remapping transmission for the BH RLC CH that needs to be remapped, that is, remap the BH RLC CH that needs to be remapped on BH link1 to other BH RLC CHs that do not need to be remapped on BH link1 (related The solution is to reroute the BH RLC CH that needs to be remapped on BH link1 to BH link2. In the embodiment of this application, regardless of whether the IAB1 node has one or more egress links, remapping is only performed on the same link):

BH RLC CH1 can optionally be remapped to a second BH RLC CH as CH3 and CH5.

BH RLC CH2 can optionally be remapped to a second BH RLC CH as CH3 and CH5.

BH RLC CH4 can optionally be remapped to a second BH RLC CH as CH5.

In the embodiment of this application, optionally, if there are at least two second BH RLC CHs in a BH RLC CH (the first BH RLC CH) that needs to be remapped, IAB1 performs one of the following operations:

From the at least two second BH RLC CHs, select the BH RLC CH with the lowest transmission priority as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, select the BH RLC CH with the largest available buffer capacity as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, select the BH RLC CH with the least remapping times as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, randomly select one BH RLC CH as the second BH RLC CH for remapping.

In this embodiment of the present application, when the remapping times of the at least two second BH RLC CHs are the same, further, arbitrary selection may be based on implementation, or selection based on transmission priority, or selection based on available buffer capacity.

This method needs to maintain a remapping count counter for each second BH RLC CH that can be remapped. Whenever a first BH RLC CH selects the second BH RLC CH for remapping transmission, the second BH RLC CH 2. Add 1 to the counter of remapping times of BH RLCCH.

Assume that IAB1 selects the remapped BH RLC CH for the BH RLC CH that needs to be remapped, as shown in Table 2:

Table 2

First BH RLC CH BH RLC CH that can be remapped BH RLC CH1 BH RLC CH5 BH RLC CH2 BH RLC CH3 BH RLC CH4 BH RLC CH5

Then the remap times counter of BH RLC CH3 is 1; the remap times counter of BH RLC CH5 is 2.

Embodiment 2: Stop the remapping of the first BH RLC CH

Time 1: IAB1 receives the DL flow control message sent by IAB2, and the obtained information is shown in Table 3:

table 3

Assume that IAB1 selects the remapped BH RLC CH for the BH RLC CH that needs to be remapped, as shown in Table 4:

Table 4

First BH RLC CH BH RLC CH that can be remapped BH RLC CH1 BH RLC CH5 BH RLC CH2 BH RLC CH3 BH RLC CH4 BH RLC CH5

Moment 2: IAB1 receives the DL flow control message sent by IAB2, and the obtained information is shown in Table 5:

table 5

It can be seen that BH RLC CH4 has released the remapping status due to the remapping transmission, but BH RLC CH1 and BH RLC CH2 are still in the remapping status; and BH RLC CH5 is carrying too many multiple mappings. The data leads to a state where remapping needs to be enabled; the IAB1 node performs the following operations on each BH RLC CH after receiving the DL flow control message:

BH RLC CH1: Since the BH RLC CH5 used for remapping needs to be remapped, and the second BH RLC CH available for selection is BH RLC CH3, so switch from BH RLC CH5 to BH RLC CH3 for remapping mapping;

BH RLC CH2: BH RLC CH5 used for remapping needs to turn on remapping, and now the second BH RLC CH available for selection is BH RLC CH3 and BH RLC CH4, because BH RLC CH4 has a lower priority , so switch from BH RLC CH5 to BH RLC CH4 for remapping;

BH RLC CH3: No need for remapping;

BH RLC CH4: Assume that 35% is the configured threshold for de-remapping (that is, the second threshold), so BH RLCCH4 stops the remapping operation and resumes normal data transmission.

BH RLC CH5: Remapping is required, but BH RLC CH5 has no second BH RLC CH to choose from, so do nothing.

To sum up, at time 2, IAB1 selects the remapped BH RLC CH for the BH RLC CH that needs to be remapped, as shown in Table 6:

Table 6

In the above embodiment, the first backhaul node selects the second BH RLCCH for remapping for the first BH RLC CH, and in some other embodiments of the present application, optionally, the second BH RLC CH is also It may be a remapped BH RLC CH configured for the first BH RLC CH in advance.

That is to say, the BH RLC CH that can be remapped can be configured for at least one BH RLC CH (it can be all BH RLCCHs) on the first backhaul link in advance. After it is determined that the BH RLC CH needs to be remapped, Then the remapable BH RLC CH configured in advance for the first BH RLC CH can be used as the second BH RLC CH. In this way, the first backhaul link does not need to perform the operation of selecting the second BH RLC CH, which saves time delay and power consumption.

In this embodiment of the present application, optionally, the second BH RLC CH is configured with an IAB host CU.

In this embodiment of the present application, optionally, the QoS characteristics and/or transmission priorities of the second BH RLC CH and the first BH RLC CH are the same or similar.

In this embodiment of the present application, optionally, the second BH RLC CH is only used for remapped data transmission of the first BH RLC CH, that is, the data configured for the first BH RLC CH in advance can be remapped The mapped second BH RLC CH is not used to transmit data under normal circumstances, and is only used to transmit the data that the corresponding first BH RLC CH needs to transmit when the corresponding first BH RLC CH needs to be remapped.

In the foregoing embodiments of the present application, optionally, the first backhaul link is an uplink backhaul link or a downlink backhaul link.

Please refer to Figure 10, the embodiment of the present application also provides a BH RLC CH remapping method, including:

Step 101: the second backhaul node sends a first message to the first backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link The path is a backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the ID of the BH RLC CH, and the first message is used to indicate the at least Whether a BH RLC CH needs to be remapped.

The indication may be an implicit indication or an explicit indication.

In the embodiment of the present application, the backhaul node sends the first message to another backhaul node on the same link, so that another backhaul node can determine whether the BH RLC CH needs to be remapped according to the first message.

Optionally, the BH RLC CH remapping method of the embodiment of the present application also includes:

The second backhaul node sends a second message to the first backhaul node, the second message includes target information of the first BHRLC CH, and the second message is used to indicate whether the first BH RLC CH has changed No remapping is required. The indication may be an implicit indication or an explicit indication.

Optionally, the first message is a flow control message.

Optionally, the target information further includes the available buffer capacity of the BH RLC CH; the BH RLC CH that needs to be remapped is a BH RLC CH whose available buffer capacity is less than or equal to the first threshold.

Optionally, the target information of the second message also includes the available buffer capacity of the BH RLC CH; when the available buffer capacity is greater than the first threshold, the first BH RLC corresponding to the available buffer capacity CH does not need to be remapped.

It should be noted that, for the BH RLC CH remapping method provided in the embodiment of the present application, the execution subject may be a BHRLC CH remapping device, or the control in the BH RLC CH remapping device for executing the BH RLC CH remapping method module. In the embodiment of the present application, the BH RLC CH remapping device provided by the embodiment of the present application is described by taking the virtual device to execute the BH RLC CH remapping method as an example.

Please refer to FIG. 11, the embodiment of the present application also provides a BH RLC CH remapping device 110, including:

The first receiving module 111 is configured to receive a first message sent by a second backhaul node, where the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul The link is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least the ID of the BH RLC CH;

The first determining module 112 is configured to determine that the first BH RLC CH in the at least one BH RLC CH needs to be remapped according to the target information;

The second determination module 113 is configured to determine a second BH RLC CH, where the second BH RLC CH is the BH RLC CH on the first backhaul link;

A remapping module 114, configured to remap data that needs to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission.

In the embodiment of this application, when the BH RLC CH needs to be remapped (for example, when congestion occurs), the IAB node can remap the data transmitted by the BH RLC CH that needs to be remapped to another BH on the same backhaul link For transmission on RLCCH, even if the IAB node has only one output link (egress link) or has multiple egress links, it cannot find a replacement BAP routing ID on other egress links or there is no replacement BH configured on other egress links of the IAB node When using RLC CH, the normal transmission of BH RLC CH data can be guaranteed.

Optionally, the first message is a flow control message.

Optionally, the target information also includes the available buffer capacity of the BH RLC CH; the BH RLC CH remapping device 110 also includes:

The first judging module is used to judge whether the BH RLC CH needs to be remapped according to whether the available buffer capacity of the BH RLC CH is less than or equal to a first threshold; if the available buffer capacity of the BH RLC CH is less than or equal to The first threshold is used to determine that the BH RLC CH needs to be remapped.

Optionally, the first thresholds corresponding to each BH RLC CH are the same or different.

Optionally, the first message is a message for carrying target information of the BH RLC CH that needs to be remapped.

Optionally, the first determination module 112 is configured to select that the transmission priority on the first backhaul link is lower than or equal to the transmission priority of the first BH RLC CH, and can be remapped The BH RLC CH, as the second BH RLC CH.

Optionally, the transmission priority of each BH RLC CH on the first backhaul link is configured by the IAB owner centralized unit CU.

Optionally, the BH RLC CH that can be remapped is a BHRLC CH whose available buffer capacity is greater than the first threshold.

Optionally, the first determination module 112 is also configured to perform one of the following operations if there are at least two second BH RLC CHs:

From the at least two second BH RLC CHs, selecting the second BH RLCCH with the lowest transmission priority as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, select the second BHRLC CH with the largest available buffer capacity as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, select the second BH RLCCH with the least remapping times as the second BH RLC CH for remapping;

From the at least two second BH RLC CHs, randomly select one of the second BH RLC CHs as the second BH RLC CH for remapping.

Optionally, the BH RLC CH remapping device 110 also includes:

A counting module, configured to add one to the count of the remapping times counter of the second BH RLC CH used for remapping.

Optionally, each of the second BH RLC CHs corresponds to a remapping times counter, and the remapping times counter starts counting from 0 until the second BH RLC CH cannot be remapped and is cleared.

Optionally, the BH RLC CH remapping device 110 also includes:

A stop module, configured to stop the remapping of the first BH RLC CH if at least one of the following conditions is met:

All the second BH RLC CHs corresponding to the first BH RLC CH cannot be remapped;

The first BH RLC CH does not need to be remapped.

Optionally, the second BH RLC CH that cannot be remapped is a BH RLC CH whose available buffer capacity is less than or equal to the first threshold.

Optionally, the first BH RLC CH that does not need to be remapped is a BH RLC CH whose available buffer capacity is greater than the first threshold.

Optionally, the BH RLC CH remapping device 110 also includes:

The second judging module is used to judge whether the first BH RLC CH does not need to be remapped.

Optionally, the second judging module is configured to receive a second message sent by the second backhaul node, where the second message includes target information of the first BH RLC CH; according to the first The target information of the first BH RLCCH in the second message is used to determine whether the first BH RLCCH does not need to be remapped.

Optionally, the target information in the second message also includes the available buffer capacity of the BH RLC CH; the second judging module is configured to determine whether the available buffer capacity of the first BH RLC CH is greater than or equal to The second threshold, judging whether the first BH RLC CH does not need to be remapped; if the available buffer capacity of the first BH RLC CH is greater than or equal to the second threshold, judging the first BH RLC CH becomes unnecessary for remapping.

Optionally, the second threshold is predefined by a protocol or preconfigured by a network.

Optionally, the second thresholds corresponding to each of the first BH RLC CHs are the same or different.

Optionally, the second BH RLC CH is a remappable BHRLC CH configured for the first BH RLC CH in advance.

Optionally, the QoS characteristic and/or transmission priority of the second BH RLC CH is the same as or similar to that of the first BH RLC CH.

Optionally, the second BH RLC CH is only used for remapped data transmission of the first BH RLC CH.

The BH RLC CH remapping device provided in the embodiment of the present application can realize each process realized by the method embodiment in FIG. 4 and achieve the same technical effect. To avoid repetition, details are not repeated here.

Please refer to FIG. 12, the embodiment of the present application also provides a BH RLC CH remapping device 120, including:

The first sending module 121 is configured to send a first message to a first backhaul node, where the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link The path is a backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the ID of the BH RLC CH, and the first message is used to indicate the at least Whether a BH RLC CH needs to be remapped.

Optionally, the BH RLC CH remapping device 120 also includes:

The second sending module is configured to send a second message to the first backhaul node, the second message includes target information of the first BHRLC CH, and the second message is used to indicate whether the first BH RLC CH has changed No remapping is required.

Optionally, the first message is a flow control message.

Optionally, the target information further includes the available buffer capacity of the BH RLC CH; the BH RLC CH that needs to be remapped is a BH RLC CH whose available buffer capacity is less than or equal to the first threshold.

Optionally, the target information of the second message also includes the available buffer capacity of the BH RLC CH; when the available buffer capacity is greater than the first threshold, the first BH RLC corresponding to the available buffer capacity CH does not need to be remapped.

The BH RLC CH remapping device provided in the embodiment of the present application can realize each process realized by the method embodiment in FIG. 10 and achieve the same technical effect. In order to avoid repetition, details are not repeated here.

As shown in FIG. 13 , the embodiment of the present application also provides a backhaul node 130, including a processor 131, a memory 132, and a program or instruction stored in the memory 132 and operable on the processor 131, the program Or when the instruction is executed by the processor 131, the various processes of the above-mentioned BH RLC CH remapping method embodiment can be achieved, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.

The embodiment of the present application also provides a backhaul node, including a processor and a communication interface, the communication interface is used to receive the first message sent by the second backhaul node, and the first message includes the first message on the first backhaul link. Target information of at least one BH RLCCH, the first backhaul link is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least the BH RLCCH Identity ID; the processor is used to determine, according to the target information, that the first BH RLC CH in the at least one BH RLC CH needs to be remapped; determine a second BH RLC CH, and the second BH RLC CH is the The BH RLC CH on the first backhaul link; remapping the data that needs to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission.

The embodiment of the present application also provides a backhaul node, including a processor and a communication interface, wherein the communication interface is used to send a first message to the first backhaul node, and the first message includes the first backhaul link Target information of at least one BHRLC CH on the road, the first backhaul link is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least the The ID of the BH RLC CH, the first message is used to indicate whether the at least one BH RLC CH needs to be remapped.

This backhaul node embodiment corresponds to the above-mentioned backhaul node method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this backhaul node embodiment, and can achieve the same technical effect.

Specifically, the embodiment of the present application also provides a backhaul node. As shown in FIG. 14 , the backhaul node 1400 includes: an antenna 141 , a radio frequency device 142 , and a baseband device 143 . The antenna 141 is connected to the radio frequency device 142 . In the uplink direction, the radio frequency device 142 receives information through the antenna 141, and sends the received information to the baseband device 143 for processing. In the downlink direction, the baseband device 143 processes the information to be sent and sends it to the radio frequency device 142 , and the radio frequency device 142 processes the received information and sends it out through the antenna 141 .

The foregoing frequency band processing device may be located in the baseband device 143 , and the method performed by the backhaul node in the above embodiment may be implemented in the baseband device 143 , and the baseband device 143 includes a processor 144 and a memory 145 .

The baseband device 143, for example, may include at least one baseband board, on which a plurality of chips are arranged, as shown in FIG. The return node operation shown in the above method embodiment.

The baseband device 143 may also include a network interface 146 for exchanging information with the radio frequency device 142, such as a common public radio interface (CPRI for short).

Specifically, the backhaul node in the embodiment of the present application further includes: instructions or programs stored in the memory 145 and executable on the processor 144, and the processor 144 calls the instructions or programs in the memory 145 to execute the The methods executed by each module are shown to achieve the same technical effect. In order to avoid repetition, the details are not repeated here.

The embodiment of the present application also provides a readable storage medium, the readable storage medium may be volatile or non-volatile, and a program or instruction is stored on the readable storage medium, the program or When the instruction is executed by the processor, each process of the above-mentioned BH RLC CH remapping method embodiment can be realized, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the foregoing embodiments. The readable storage medium includes computer readable storage medium, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above BH RLC CH remapping method The various processes of the embodiment can achieve the same technical effect, so in order to avoid repetition, details are not repeated here.

It should be understood that the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.

The embodiment of the present application also provides a computer program/program product, the computer program/program product is stored in a non-transitory storage medium, and the computer program/program product is executed by at least one processor to implement the above BH Steps of the RLC CH remapping method.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, 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.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of computer software products, which are stored in a storage medium (such as ROM/RAM, magnetic disk, etc.) , CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Under the inspiration of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can also be made, all of which belong to the protection of this application.

Claims (32)

1. a kind of backhaul radio link control channel BH RLC CH remapping method, it is characterized in that, comprising: The first backhaul node receives the first message sent by the second backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link is For a backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the identity ID of the BH RLC CH; The first backhaul node determines that the first BH RLCCH in the at least one BH RLC CH needs to be remapped according to the target information; The first backhaul node determines a second BH RLC CH, and the second BH RLC CH is the BH RLC CH on the first backhaul link; The first backhaul node remaps the data that needs to be transmitted through the first BHRLC CH to the second BHRLC CH for transmission. 2. The method according to claim 1, wherein the first message is a flow control message. 3. The method according to claim 1 or 2, wherein the target information also includes the available buffer capacity of the BH RLC CH; The method also includes: The first backhaul node judges whether the BH RLC CH needs to be remapped according to whether the available buffer capacity of the BH RLC CH is less than or equal to a first threshold; If the available buffer capacity of the BH RLC CH is less than or equal to the first threshold, the first backhaul node determines that the BH RLC CH needs to be remapped. 4. The method according to claim 3, characterized in that the first thresholds corresponding to each BH RLC CH are the same or different. 5. The method according to claim 1 or 2, wherein the first message is a message for carrying target information of the BH RLC CH that needs to be remapped. 6. The method according to claim 1, wherein the first backhaul node determines the second BH RLC CH, comprising: The first backhaul node selects a BH RLC CH whose transmission priority on the first backhaul link is lower than or equal to the transmission priority of the first BHRLC CH and can be remapped as the Second BH RLC CH. 7. The method according to claim 6, wherein the transmission priority of each BH RLC CH on the first backhaul link is configured by an IAB owner centralization unit CU. 8. The method according to claim 6, wherein the remapped BH RLC CH is a BH RLC CH whose available buffer capacity is greater than a first threshold. 9. The method according to claim 1 or 6, wherein the first backhaul node determines the second BH RLCCH, comprising: If there are at least two second BH RLC CHs, the first backhaul node performs one of the following operations: From the at least two second BH RLC CHs, selecting the second BH RLC CH with the lowest transmission priority as the second BH RLC CH for remapping; From the at least two second BH RLC CHs, select the second BH RLC CH with the largest available buffer capacity as the second BH RLC CH for remapping; From the at least two second BH RLC CHs, select the second BH RLC CH with the least number of remapping times as the second BH RLC CH for remapping; From the at least two second BH RLC CHs, randomly select one of the second BH RLC CHs as the second BH RLC CH for remapping. 10. The method of claim 9, further comprising: The first backhaul node adds one to the count of the remapping times counter of the second BH RLC CH used for remapping. 11. The method according to claim 10, wherein each of the second BH RLC CHs corresponds to one of the remapping counters, and the remapping counters start counting from 0 until the second BH Cleared when RLC CH cannot be remapped. 12. The method according to claim 1, wherein after remapping the data to be transmitted through the first BH RLC CH to the second BH RLC CH for transmission, further comprising: If at least one of the following conditions is met, the first backhaul node stops the remapping of the first BH RLC CH: All the second BH RLC CHs corresponding to the first BH RLC CH cannot be remapped; The first BH RLC CH does not need to be remapped. 13. The method according to claim 12, wherein the second BH RLCCH that cannot be remapped is a BH RLCCH whose available buffer capacity is less than or equal to the first threshold. 14. The method according to claim 12, wherein the first BH RLCCH that does not need to be remapped is a BH RLCCH with an available buffer capacity greater than a first threshold. 15. The method of claim 12, further comprising: The first backhaul node determines whether the first BH RLC CH does not need to be remapped. 16. The method according to claim 15, wherein the first backhaul node judging whether the first BH RLCCH does not need to be remapped comprises: The first backhaul node receives the second message sent by the second backhaul node, and the second message includes the target information of the first BH RLC CH; The first backhaul node determines whether the first BH RLC CH does not need to be remapped according to the target information of the first BH RLC CH in the second message. 17. The method according to claim 16, wherein the target information in the second message also includes the available buffer capacity of the BH RLC CH; The first backhaul node determines whether the first BH RLC CH does not need to be remapped according to the target information of the first BH RLC CH in the second message, including: The first backhaul node judges whether the first BH RLC CH does not need to be remapped according to whether the available buffer capacity of the first BH RLC CH is greater than or equal to a second threshold; If the available buffer capacity of the first BH RLC CH is greater than or equal to the second threshold, the first backhaul node determines that the first BH RLC CH does not need to be remapped. 18. The method according to claim 17, wherein the second threshold is predefined by a protocol or preconfigured by a network. 19. The method according to claim 17, wherein the second thresholds corresponding to each of the first BH RLC CHs are the same or different. 20. The method according to claim 1, wherein the second BH RLC CH is a remappable BH RLC CH configured for the first BHRLC CH in advance. 21. The method according to claim 20, characterized in that, the QoS characteristics and/or transmission priority of the second BH RLCCH are the same or similar to those of the first BH RLCCH. 22. The method according to claim 20, wherein the second BH RLC CH is only used for remapped data transmission of the first BHRLC CH. 23. The method according to claim 1, wherein the first backhaul link is an uplink backhaul link or a downlink backhaul link. 24. A BH RLC CH remapping method, characterized in that, comprising: The second backhaul node sends a first message to the first backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link is the first backhaul link A backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the ID of the BH RLC CH, and the first message is used to indicate the at least one BH RLC Whether CH needs to be remapped. 25. The method of claim 24, further comprising: The second backhaul node sends a second message to the first backhaul node, the second message includes target information of the first BH RLCCH, and the second message is used to indicate whether the first BH RLCCH changes No remapping is required. 26. The method according to claim 24, wherein the first message is a flow control message. 27. The method according to claim 24 or 26, wherein the target information also includes the available buffer capacity of the BH RLCCH; the BH RLCCH that needs to be remapped is that the available buffer capacity is less than or equal to the first A threshold BH RLC CH. 28. The method according to claim 25, wherein the target information of the second message also includes the available buffer capacity of the BHRLC CH; when the available buffer capacity is greater than a first threshold, the The first BH RLC CH corresponding to the available buffer capacity does not need to be remapped. 29. A BH RLC CH remapping device, characterized in that, comprising: The first receiving module is configured to receive the first message sent by the second backhaul node, the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link The path is a backhaul link between the first backhaul node and the second backhaul node, and the target information includes at least the ID of the BH RLC CH; A first determining module, configured to determine, according to the target information, that the first BH RLCCH in the at least one BH RLC CH needs to be remapped; The second determination module is configured to determine a second BH RLC CH, where the second BH RLC CH is the BH RLC CH on the first backhaul link; A remapping module, configured to remap data that needs to be transmitted through the first BH RLC CH to the second BHRLC CH for transmission. 30. A BH RLC CH remapping device, characterized in that, comprising: The first sending module is configured to send a first message to a first backhaul node, where the first message includes target information of at least one BH RLC CH on the first backhaul link, and the first backhaul link is a backhaul link between the first backhaul node and the second backhaul node, the target information includes at least the ID of the BH RLC CH, and the first message is used to indicate the at least one BH RLC Whether CH needs to be remapped. 31. A backhaul node, characterized by comprising a processor, a memory, and a program or instruction stored in the memory and operable on the processor, when the program or instruction is executed by the processor Realize the steps of the BH RLC CH remapping method as described in any one of claims 1-23, or, when the program or instruction is executed by the processor, realize the BH as described in any one of claims 24-28 Steps of the RLC CH remapping method. 32. A readable storage medium, characterized in that a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the BH RLC according to any one of claims 1-23 is realized CH remapping method, or realize the steps of the BH RLC CH remapping method as described in any one of claims 24-28.

Images