Preemptive BSR arrangement method, device, and electronic device

Abstract

To provide preemptive buffer states report (BSR) arrangement method, device and electronic device that reduce transmission delay and reduce the waste of uplink transmission grants due to the preemptive BSR.SOLUTION: A method for arranging a recursive preemptive BSR includes an integrated access and backhaul (IAB) node receiving an arrangement parameter for a preemptive BSR transmitted from a centralized unit (CU). The arrangement parameter is used to indicate whether the IAB node triggers a recursive preemptive BSR, and the recursive preemptive BSR is a preemptive BSR which is generated by the IAB node based on the received preemptive BSR and is to be transmitted to a parent IAB node.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to China Patent Application No. 202011120095.2, filed in China on October 19, 2020, the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the field of communications technology, and in particular to a method, device and electronic device for deploying a preemptive BSR. [Background technology]

[0003] According to the current protocol, an integrated access backhaul (IAB) node cannot trigger a preemptive BSR to be sent to a parent IAB node based on a received preemptive BSR. However, if the preemptive BSR cannot trigger a preemptive BSR, when the backhaul link is long and a low-latency requirement business of the backhaul link service is used, the long-delay problem caused by multi-hop uplink wireless transmission is severe. Even if a preemptive BSR program is adopted, the transmission delay of the uplink is still obviously larger than the transmission delay of the downlink. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments of the present application provide a method, device and electronic device for configuring a preemptive BSR, which can reduce transmission delay and reduce the waste of uplink transmission permission caused by the preemptive BSR. [Means for solving the problem]

[0005] According to a first aspect, an embodiment of the present application provides a method for configuring a recursive preemptive BSR, the method for configuring a recursive preemptive BSR includes: The method includes a self-backhauled IAB node receiving configuration parameters for a preemptive BSR, the configuration parameters being used to indicate whether the IAB node should trigger a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on the received preemptive BSR and sent to a parent IAB node.

[0006] According to a second aspect, an embodiment of the present application provides a method for configuring a recursive preemptive BSR, the method for configuring a recursive preemptive BSR includes: The method includes a centralized unit CU sending a configuration parameter of a preemptive BSR to a self-backhauled IAB node, the configuration parameter being used to indicate whether the IAB node triggers a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on a received preemptive BSR and sent to a parent IAB node.

[0007] According to a third aspect, an embodiment of the present application provides a configuration device of a recursive preemptive BSR for use in an IAB node, the configuration device of the recursive preemptive BSR comprising: The present invention includes a receiving module for receiving a configuration parameter of a preemptive BSR, the configuration parameter being used to indicate whether the IAB node should trigger a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on the received preemptive BSR and sent to a parent IAB node.

[0008] According to a fourth aspect, an embodiment of the present application provides a configuration device of a recursive preemptive BSR used in a centralized unit, the configuration device of the recursive preemptive BSR comprising: The present invention includes a transmitting module for transmitting configuration parameters of a preemptive BSR to a self-backhauled IAB node, the configuration parameters being used to indicate whether the IAB node should trigger a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on a received preemptive BSR and transmitted to a parent IAB node.

[0009] According to a fifth aspect, an embodiment of the present application further provides an electronic device, the electronic device including a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions being operable when executed by the processor to realize steps of the method described above.

[0010] According to a sixth aspect, an embodiment of the present application provides a readable storage medium having a program or instructions stored thereon, the program or instructions, when executed by a processor, implementing the steps of the method as set forth above.

[0011] According to a seventh aspect, an embodiment of the present application provides a chip, the chip including a processor and a communication interface, the communication interface coupled to the processor, the processor running a program or instructions and adapted to implement a method according to the first or second aspect.

[0012] According to an eighth aspect, there is provided a computer program product, the program product being stored in a non-volatile storage medium, the program product being executed by at least one processor to implement the method according to the first aspect or to implement the method according to the second aspect. Effect of the Invention

[0013] In the embodiment of the present application, the centralized unit sends configuration parameters of a preemptive BSR to the IAB node, and the IAB node can accurately control whether to trigger a preemptive BSR based on the preemptive BSR according to actual conditions, thereby reducing the transmission delay and reducing the waste of uplink transmission permission caused by the preemptive BSR. [Brief description of the drawings]

[0014] [Figure 1] 1 shows a schematic diagram of a wireless communication system; [Diagram 2] A schematic diagram of the IAB system is shown. [Diagram 3] The CU-DU structure diagram of the IAB system is shown. [Figure 4] 1 shows a schematic diagram of triggering a preemptive BSR based on a UL grant and a BSR. [Diagram 5] 1 shows a schematic diagram of the format of the MAC CE of a preemptive BSR. [Figure 6] 2 illustrates a flowchart of a configuration method for a recursive preemptive BSR on an IAB node side in an embodiment of the present application; [Figure 7] 1 illustrates a flowchart of a method for configuring a recursive preemptive BSR on the centralization unit side in an embodiment of the present application. [Figure 8] 1 shows a flowchart of a recursive preemptive BSR in a specific embodiment of the present application. [Figure 9] 1 shows a schematic diagram of the format of a BSR MAC CE in an embodiment of the present application. [Figure 10] 1 illustrates a structural schematic diagram of an IAB node side iterative preemptive BSR configuration device in an embodiment of the present application; [Figure 11] 1 shows a structural schematic diagram of a configuration device of a repetitive preemptive BSR on the centralized unit side in an embodiment of the present application; [Figure 12] 1 shows a schematic diagram of the configuration of a terminal according to an embodiment of the present application. [Figure 13] 1 shows a schematic configuration diagram of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] The following are drawings in the examples of this application: In combination with the above, the technical solutions in the embodiments of the present application are clearly described, and it is obvious that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present application are all within the scope of protection of the present application.

[0016] The terms "first," "second," etc. in the specification and claims of this application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that the data so used may be interchanged where appropriate, such that the embodiments of this application may be performed in an order other than that shown or described herein. Note that "and / or" in the specification and claims indicates at least one of the objects connected, and the character " / " generally indicates that the related objects are in an "or" relationship.

[0017] The techniques described herein are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but may also be applied to various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are always used interchangeably. A CDMA system may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and the like. UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system may implement radio technologies such as Global System for Mobile Communication (GSM), etc. An OFDMA system may implement radio technologies such as UltraMobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, FLASH-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).LTE and higher LTE (e.g., LTE-A) are newer versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP®). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP®2). The techniques described herein may be used for the systems and radio technologies mentioned above or other systems and radio technologies. The following description describes an NR system for illustrative purposes and uses NR terminology in most of the following description, but these techniques may be applied to applications other than NR system applications.

[0018] The following description provides examples, but is not intended to be limiting of the scope, applicability, or arrangement of the claimed invention. Modifications may be made in the function and arrangement of the elements discussed without departing from the spirit and scope of the present disclosure. Various examples may omit, substitute, or add various steps or assemblies as appropriate. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Also, features described with reference to some examples may be combined in other examples.

[0019] Referring to FIG. 1, FIG. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a mobile Internet device (Mobile Internet Device, MID), a wearable device, or an in-vehicle device, and it should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network side equipment 12 may be a base station or a core network, where the base station may be a 5G or later version base station (e.g., gNB, 5G NR NB, etc.), or a base station in other communication systems (e.g., eNB, WLAN access point, or other access point), or a location server (e.g., E-SMLC or LMF (Location Manager Function)), where the base station may be called a Node B, an evolved Node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, or any other suitable term in the art, and as long as the same technical effect is achieved, the base station is not limited to a specific technical term, and it should be explained that in the embodiments of this application, only a base station in an NR system is taken as an example, but the embodiment base station of this application is not limited to a specific type and a specific communication system.

[0020] FIG. 2 shows a schematic diagram of an integrated access backhaul (IAB) system. The IAB node includes a distributed unit (DU) functional part and a mobile termination (MT) functional part. Through the MT, an access point (i.e., IAB node) can discover an upstream access point (parent IAB node) and establish a wireless connection with the DU of the upstream access point, which is called a backhaul link. After an IAB node establishes a complete backhaul link, the IAB node opens its DU function, and the DU can provide cell service, i.e., the DU can provide access service to a user equipment (UE). A self-backhaul circuit includes a donor IAB node (or called IAB donor), which has a wired transmission network directly connected thereto. Here, Access is access, Access IAB node is access IAB node, Intermediate IAB node is intermediate IAB node, and cable transport is wired transmission.

[0021] Figure 3 is a diagram of the CU-DU (Centralized Unit-Distributed Unit) structure of an IAB system. In one self-backhaul circuit, the DUs of all IAB nodes are connected to one centralized unit (CU) node, which configures the DUs via the F1 protocol (F1 Application Protocol or F1 control protocol). The CU configures the MTs via the Radio Resource Control (RRC) protocol. The Donor IAB node does not have an MT function.

[0022] The introduction of the IAB system is intended to solve the problem of insufficient deployment of wired transmission networks when access points are deployed densely, i.e., without a wired transmission network, access points have to rely on wireless backhaul.

[0023] In order to reduce uplink data transmission delay, one IAB node may trigger a preemptive BSR after receiving a Buffer Status Report (BSR) from a UE or a downstream node, and may decide whether to trigger based on an uplink transmission grant (UL grant) sent to a downstream IAB node or UE. The triggering mechanism of the two preemptive BSRs is shown in FIG. 4. In this method of determining the preemptive BSR based on data to be received in the future, the upstream node can reduce transmission delay by scheduling early based on expected data. Here, Child Node is a child node, Parent Node is a parent node, Regular BSR is a regular BSR, and Data is data.

[0024] Currently, the preemptive BSR is transmitted in the same format as the long BSR Media Access Control (MAC) Control element (CE), and the format of the preemptive BSR MAC CE is shown in Figure 5, where LCG (Logical Channel Group) is the logical channel group and Buffer Size is the size of the buffer.

[0025] According to the current protocol, an IAB node cannot trigger a preemptive BSR to be sent to a parent IAB node based on the received preemptive BSR. However, if the preemptive BSR cannot trigger the preemptive BSR, when the backhaul link is long and the backhaul link service is used for low-latency requirements, the long-delay problem caused by multi-hop uplink wireless transmission is severe. Although the preemptive BSR program is adopted, the uplink transmission delay is still obviously larger than the downlink transmission delay. Based on this, it is necessary to further study how to trigger the preemptive BSR based on the preemptive BSR so that the network can use the optimized preemptive BSR program and meet the quality requirements of the low-latency service.

[0026] On the other hand, if one IAB node (IAB N1) is configured to trigger and transmit a preemptive BSR to its parent IAB node, and its parent IAB node (IAB N2) transmits uplink transmission grants to this IAB node based on the received preemptive BSR, IAB N2 can trigger a preemptive BSR to its higher parent IAB node (IAB N3) based on these uplink transmission grants. However, due to the uncertainty of radio link transmission, the amount of data actually received by IAB N2 may have a large difference compared to the amount of data expected to be received. If the expected data does not arrive, it will cause a waste of the uplink transmission grant that IAB N3 transmits to IAB N2 based on the received preemptive BSR. If IAB N2 does not trigger a preemptive BSR to send to IAB N3 based on these transmission grants, when IAB N2 receives data sent by IAB N1 based on these uplink transmission grants, IAB N2 needs to trigger a conventional BSR process and request an uplink transmission grant from IAB N1, during which there is a relatively large transmission delay. Therefore, the method of triggering a preemptive BSR based on a preemptive BSR needs to overcome the problem of resource waste as much as possible.

[0027] An embodiment of the present application provides a configuration method for preemptive buffer status report (BSR), as shown in FIG. 6, including:

[0028] Step 101: A self-backhauled IAB node receives configuration parameters of a preemptive BSR, the configuration parameters being used to indicate whether the IAB node triggers a recursive preemptive BSR, which is a preemptive BSR that the IAB node generates based on the received preemptive BSR and sends to a parent IAB node.

[0029] In the embodiment of the present application, the centralized unit sends configuration parameters of a preemptive BSR to the IAB node, and the IAB node can accurately control whether to trigger a preemptive BSR based on the preemptive BSR according to actual conditions, thereby reducing the transmission delay and reducing the waste of uplink transmission permission caused by the preemptive BSR.

[0030] In an embodiment of the present application, the CU can be configured to allow an access IAB node to determine whether and how an upstream IAB node further triggers a preemptive BSR based on the received preemptive BSR, including a new preemptive BSR MAC CE format. An upstream IAB node can determine whether to further trigger a preemptive BSR based on the indication in the received preemptive BSR and / or the CU's preconfiguration. In this way, the CU and the IAB node can precisely control whether a preemptive BSR can be triggered based on the preemptive BSR in some cases, thereby reducing the waste of uplink transmission grants.

[0031] In this embodiment, a preemptive BSR that can instruct a parent IAB node to generate a recursive preemptive BSR may be referred to as an initial recursive preemptive BSR, and a preemptive BSR generated based on a received preemptive BSR may be referred to as a recursive preemptive BSR.

[0032] In some embodiments, the configuration parameters include at least one of the following:

[0033] List of logical channel groups LCG that can trigger a recursive preemptive BSR. In one specific example, LCG1 and LCG2 are configured in UE1, and the CU configures the IAB node to trigger a recursive preemptive BSR based on LCG1, and does not configure the IAB node to trigger a recursive preemptive BSR based on LCG2. If the BSR received by the IAB node from the UE indicates that there is data in LCG1 or that there is data in both LCG1 and LCG2, the initial recursive preemptive BSR sent to the parent IAB node can indicate that the recursive preemptive BSR can be triggered based on LCG1. If the BSR received by the IAB node from the UE indicates that there is no data in LCG1 but there is data in LCG2, the initial recursive preemptive BSR sent to the parent IAB node cannot indicate that the recursive preemptive BSR is triggered.

[0034] LCH list of logical channels that can trigger a recursive preemptive BSR.

[0035] A list of data radio bearer DRBs for which a repetitive preemptive BSR can be triggered.

[0036] A list of business types that can trigger a recurring preemptive BSR.

[0037] The type of user equipment UE that can trigger the repetitive preemptive BSR. In one specific example, the access IAB node may be configured to determine whether to allow the triggering of the early repetitive preemptive BSR based on the main business of the UE, for example, the CU may be configured to cause the access IAB node to trigger the early repetitive preemptive BSR based on the BSR from an Ultra-reliable and Low Latency Communication (URLLC) UE, and in another specific example, the CU may directly configure the access IAB node to trigger the early repetitive preemptive BSR for a specific UE, for example, the access IAB node may be configured to trigger the early repetitive preemptive BSR based on the BSR of a high-added-value UE.

[0038] The number of iterations that a repeat preemptive BSR can be triggered. It may be configured according to LCG, LCH, DRB, service type, or UE, and this number can indicate the number of hops that the service data information can be preemptively transmitted.

[0039] A time budget for triggering a repeated preemptive BSR. This may be configured according to LCG, LCH, DRB, service type, or UE, and indicates within what expected time the service data buffer information can be repeatedly transmitted to the upstream IAB node.

[0040] In this embodiment, the number of times and time budget that the repeated preemptive BSR can be triggered are introduced, and the unlimited repeated preemptive BSR transmission can avoid the error between the amount of data that can actually be transmitted and the uplink buffer report becoming too large after multiple hops, which causes the preemptive report to lose its meaning, and avoid the waste of uplink transmission permission. On the other hand, if the repeated preemptive BSR is too long, the uplink buffer status of the IAB node will change due to the generation of new business data, and the difference between the buffer status of the preemptive BSR report and the actual buffer status will become large, and at this time, if the repeated preemptive BSR is triggered again based on the preemptive BSR, it will lose its meaning.

[0041] In some embodiments, the configuration parameters are: First indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a recursive preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

[0042] In some embodiments, if congestion occurs on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is not triggered, and if congestion does not occur on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is triggered.

[0043] In one specific embodiment, the trigger flow of a recursive preemptive BSR is shown in FIG. 8, where a CU configures IAB N1, IAB N2 and IAB N3 to trigger a recursive preemptive BSR, and when IAB N1 decides to trigger and send a recursive preemptive BSR, IAB N1 sends an initial recursive preemptive BSR1 (in which a recursive instruction parameter is carried) to IAB N2, and IAB N2 decides that it can further trigger a recursive preemptive BSR based on the recursive parameter carried in the preemptive BSR1, and IAB N2 sends a recursive preemptive BSR2 (in which a recursive instruction parameter is carried) to IAB N3. If IAB N1 decides to trigger and send a general preemptive BSR (i.e., a non-repeatable preemptive BSR), IAB N1 sends a preemptive BSR3 (which is indicated as non-repeatable) to IAB N2, and IAB N2 decides not to trigger any further repetitive preemptive BSRs after receiving preemptive BSR3.

[0044] Here, the CU may be configured to determine whether to trigger a recursive preemptive BSR according to the preemptive BSR information received by the subsequent intermediate node, or the CU may be configured to determine whether to trigger a recursive preemptive BSR according to the preemptive BSR information received by the subsequent intermediate node. For example, when congestion occurs in an uplink link from one intermediate IAB node to a parent IAB node, the intermediate IAB node may not temporarily trigger a recursive preemptive BSR, and may normally trigger a recursive preemptive BSR after the congestion occurring in the uplink link to the parent IAB node is resolved. The determination of whether congestion occurs in the uplink link may be based on the amount of uplink data to be transmitted exceeding a preset threshold.

[0045] In some embodiments, the configuration parameters may be conveyed to a BSR Media Access Control MAC Control Element CE.

[0046] In some embodiments, the BSR MAC CE includes one or more Logical Channel Identity (LCID) values, each indicating the number of times a repeated preemptive BSR may be triggered.

[0047] In some embodiments, the method further comprises: The method further includes selecting an LCID value from the one or more LCID values ​​that indicates the number of times a repeated preemptive BSR may be triggered after a preemptive BSR has been triggered.

[0048] In this embodiment, the MAC CE format of the conventional preemptive BSR can be used as is, as shown in FIG. 5. A new LCID is used to indicate the repeated preemptive BSR and the number of repetitions. In one specific example, if it is predefined that at most one repetition can be performed, a new LCID is required instead of the original LCID. After receiving the preemptive BSR with this new LCID, when an IAB node triggers a further preemptive BSR based on this preemptive BSR, the existing preemptive BSR MAC CE format may be used. In another specific example, if it is predefined that at most two repetitions can be performed, two new LCIDs, LCID1 (corresponding to one repetition) and LCID2 (corresponding to two repetitions), are required, and when an IAB node receives the preemptive BSR MAC CE carrying LCID2, it determines that it can trigger a further preemptive BSR, and generates a preemptive BSR MAC CE carrying LCID1. After the parent IAB node receives the preemptive BSR MAC CE carrying LCID1, the actions are the same as in the above example, except that the LCID here can be the conventional LCID (6 bits) or the eLCID (extended LCID, 8 bits or 16 bits). This method does not require a new BSR MAC CE PDU format.

[0049] In some embodiments, the BSR MAC CE includes a first bitmap, where each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a recurring preemptive BSR based on the corresponding LCG.

[0050] In this embodiment, a new preemptive BSR MAC CE format can be introduced, in which a bitmap is introduced, where each LCG corresponds to one bit to indicate whether the parent IAB node can further trigger a recursive preemptive BSR based on this LCG, and this MAC CE format is shown in FIG. 9, where the LCGi bit set (i.e., the value is 1) indicated by the shaded portion indicates that a recursive preemptive BSR can be triggered based on the buffer report of this LCG, and vice versa is not possible.

[0051] In some embodiments, the BSR MAC CE includes a first repetition count indication for indicating a number of times a repetitive preemptive BSR for at least some LCGs may be triggered; or The BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

[0052] In this embodiment, one new preemptive BSR MAC CE format called repetitive preemptive BSR MAC CE can be introduced, which carries an indication indicating whether a repetitive preemptive BSR can be triggered or the number of repetitive preemptive BSRs. In one way, the repetitive preemptive BSR MAC CE carries one repetition count indication, indicating the repetition counts of some or all LCGs, e.g., only the number of repetitions of the highest priority LCG. In another way, the repetitive preemptive BSR MAC CE carries multiple repetition count indications, each of which indicates the repetition counts of one or multiple LCGs, and in one specific example, each LCG has one associated repetition count indication field indicating the repetition count of the preemptive BSR of the corresponding LCG, and in another specific example, multiple LCGs share one associated repetition count indication field indicating the repetition count of the preemptive BSR of these LCGs.

[0053] In some embodiments, the method further comprises: When an IAB node generates a second iterative preemptive BSR to send to a parent IAB node based on the received first iterative preemptive BSR, the method further includes subtracting 1 from the value of the first iterative count indication or the second iterative count indication in the first iterative preemptive BSR and writing it to the second iterative preemptive BSR.

[0054] That is, when a new preemptive BSR MAC CE format is adopted and this preemptive BSR MAC CE format includes the number of iterative preemptive BSRs, when an IAB node generates a new iterative preemptive BSR based on the received iterative preemptive BSR, it should subtract 1 from the iteration number indicated by the received iterative preemptive BSR and write it into the generated iterative preemptive BSR. If a repeat count indication field in a received repeat preemptive BSR is 0, it indicates that a new repeat preemptive BSR cannot be triggered or generated based on the LCG corresponding to this repeat count indication field; that is, if a received repeat preemptive BSR includes one or more repeat count indication fields and at least one of them is greater than 0, a repeat preemptive BSR to be sent to the parent IAB node can be further triggered or generated according to the buffer status of the LCG corresponding to the repeat count indication field greater than 0; if all the repeat count indication fields are 0, a repeat preemptive BSR to be sent to the parent IAB node cannot be triggered or generated based on this repeat preemptive BSR.

[0055] In some embodiments, the BSR MAC CE includes a time budget indication for indicating a time budget within which a recurring preemptive BSR of at least one LCG may be triggered.

[0056] In this embodiment, a new preemptive BSR MAC CE format called recursive preemptive BSR MAC CE can be introduced, which carries an indication of the expected time budget in which a recursive preemptive BSR can be triggered. This time budget may be arranged according to the LCG, and one or more or all LCGs can have one time budget indication, and if the time budget indicated in the recursive preemptive BSR received by an IAB node is larger than the time budget required for scheduling the corresponding uplink transmission process by this IAB node, it can also trigger a recursive preemptive BSR, but not vice versa.

[0057] In some embodiments, the method further comprises: When an IAB node generates a second iterative preemptive BSR to send to a parent IAB node based on the received first iterative preemptive BSR, the method further includes subtracting the time budget required for the uplink transmission process scheduled at this hop from the value of the time budget instruction in the first iterative preemptive BSR to obtain a remaining time budget, and setting the remaining time budget as the value of the time budget instruction of the second iterative preemptive BSR.

[0058] That is, when a new preemptive BSR MAC CE format is adopted and this preemptive BSR MAC CE format includes a time budget for triggering a recursive preemptive BSR, when an IAB node determines that it can trigger a recursive preemptive BSR, it should subtract the time budget required for the uplink transmission process scheduled at this hop from the time budget indicated by the received recursive preemptive BSR to obtain the remaining time budget, write it into the generated recursive preemptive BSR, and send the generated new recursive preemptive BSR to the parent IAB node.

[0059] The embodiment of the present application further provides a configuration method for a preemptive buffer status report (BSR), as shown in FIG. The method includes a centralized unit CU sending a configuration parameter of a preemptive BSR to a self-backhauled IAB node, the configuration parameter being used to indicate whether the IAB node triggers a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on a received preemptive BSR and sent to a parent IAB node.

[0060] In an embodiment of the present application, the CU can be configured to allow an access IAB node to determine whether and how an upstream IAB node further triggers a preemptive BSR based on the received preemptive BSR, including a new preemptive BSR MAC CE format. An upstream IAB node can determine whether to further trigger a preemptive BSR based on the indication in the received preemptive BSR and / or the CU's preconfiguration. In this way, the CU and the IAB node can precisely control whether a preemptive BSR can be triggered based on the preemptive BSR in some cases, thereby reducing the waste of uplink transmission grants.

[0061] In some embodiments, the configuration parameters include at least one of the following:

[0062] List of logical channel groups LCG that can trigger a recursive preemptive BSR. In one specific example, LCG1 and LCG2 are configured in UE1, and the CU configures the IAB node to trigger a recursive preemptive BSR based on LCG1, and does not configure the IAB node to trigger a recursive preemptive BSR based on LCG2. If the BSR received by the IAB node from the UE indicates that there is data in LCG1 or that there is data in both LCG1 and LCG2, the initial recursive preemptive BSR sent to the parent IAB node can indicate that the recursive preemptive BSR can be triggered based on LCG1. If the BSR received by the IAB node from the UE indicates that there is no data in LCG1 but there is data in LCG2, the initial recursive preemptive BSR sent to the parent IAB node cannot indicate that the recursive preemptive BSR is triggered.

[0063] LCH list of logical channels that can trigger a recursive preemptive BSR.

[0064] A list of data radio bearer DRBs for which a repetitive preemptive BSR can be triggered.

[0065] A list of business types that can trigger a recurring preemptive BSR.

[0066] The type of user equipment UE that can trigger the repetitive preemptive BSR. In one specific example, the access IAB node may be configured to determine whether to allow the triggering of the early repetitive preemptive BSR based on the main business of the UE, for example, the CU may be configured to cause the access IAB node to trigger the early repetitive preemptive BSR based on the BSR from an Ultra-reliable and Low Latency Communication (URLLC) UE, and in another specific example, the CU may directly configure the access IAB node to trigger the early repetitive preemptive BSR for a specific UE, for example, the access IAB node may be configured to trigger the early repetitive preemptive BSR based on the BSR of a high-added-value UE.

[0067] The number of iterations that a repeat preemptive BSR can be triggered. It may be configured according to LCG, LCH, DRB, service type, or UE, and this number can indicate the number of hops that the service data information can be preemptively transmitted.

[0068] A time budget for triggering a repeated preemptive BSR. This may be configured according to LCG, LCH, DRB, service type, or UE, and indicates within what expected time the service data buffer information can be repeatedly transmitted to the upstream IAB node.

[0069] In this embodiment, the number of times and time budget that the repeated preemptive BSR can be triggered are introduced, and the unlimited repeated preemptive BSR transmission can avoid the error between the amount of data that can actually be transmitted and the uplink buffer report becoming too large after multiple hops, which causes the preemptive report to lose its meaning, and avoid the waste of uplink transmission permission. On the other hand, if the repeated preemptive BSR is too long, the uplink buffer status of the IAB node will change due to the generation of new business data, and the difference between the buffer status of the preemptive BSR report and the actual buffer status will become large, and at this time, if the repeated preemptive BSR is triggered again based on the preemptive BSR, it will lose its meaning.

[0070] In some embodiments, the configuration parameters are: First indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a recursive preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

[0071] In some embodiments, if congestion occurs on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is not triggered, and if congestion does not occur on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is triggered.

[0072] In one specific embodiment, the trigger flow of a recursive preemptive BSR is shown in FIG. 8, where a CU configures IAB N1, IAB N2 and IAB N3 to trigger a recursive preemptive BSR, and when IAB N1 decides to trigger and send a recursive preemptive BSR, IAB N1 sends an initial recursive preemptive BSR1 (in which a recursive instruction parameter is carried) to IAB N2, and IAB N2 decides that it can further trigger a recursive preemptive BSR based on the recursive parameter carried in the preemptive BSR1, and IAB N2 sends a recursive preemptive BSR2 (in which a recursive instruction parameter is carried) to IAB N3. If IAB N1 decides to trigger and send a general preemptive BSR (i.e., a non-repeatable preemptive BSR), IAB N1 sends a preemptive BSR3 (which is indicated as non-repeatable) to IAB N2, and IAB N2 decides not to trigger any further repetitive preemptive BSRs after receiving preemptive BSR3.

[0073] Here, the CU may be configured to determine whether to trigger a recursive preemptive BSR according to the preemptive BSR information received by the subsequent intermediate node, or the CU may be configured to determine whether to trigger a recursive preemptive BSR according to the preemptive BSR information received by the subsequent intermediate node. For example, when congestion occurs in an uplink link from one intermediate IAB node to a parent IAB node, the intermediate IAB node may not temporarily trigger a recursive preemptive BSR, and may normally trigger a recursive preemptive BSR after the congestion occurring in the uplink link to the parent IAB node is resolved. The determination of whether congestion occurs in the uplink link may be based on the amount of uplink data to be transmitted exceeding a preset threshold.

[0074] In some embodiments, the configuration parameters are conveyed to a BSR Media Access Control MAC Control Element CE.

[0075] In some embodiments, the configuration parameters may be conveyed to a BSR Media Access Control MAC Control Element CE.

[0076] In some embodiments, the BSR MAC CE includes one or more Logical Channel Identity (LCID) values, each indicating the number of times a repeated preemptive BSR may be triggered.

[0077] In some embodiments, The method further includes selecting an LCID value from the one or more LCID values ​​that indicates the number of times a repeated preemptive BSR may be triggered after a preemptive BSR has been triggered.

[0078] In this embodiment, the MAC CE format of the conventional preemptive BSR can be used as is, as shown in FIG. 5. A new LCID is used to indicate the repeated preemptive BSR and the number of repetitions. In one specific example, if it is predefined that at most one repetition can be performed, a new LCID is required instead of the original LCID. After receiving the preemptive BSR with this new LCID, when an IAB node triggers a further preemptive BSR based on this preemptive BSR, the existing preemptive BSR MAC CE format may be used. In another specific example, if it is predefined that at most two repetitions can be performed, two new LCIDs, LCID1 (corresponding to one repetition) and LCID2 (corresponding to two repetitions), are required, and when an IAB node receives the preemptive BSR MAC CE carrying LCID2, it determines that it can trigger a further preemptive BSR, and generates a preemptive BSR MAC CE carrying LCID1. After the parent IAB node receives the preemptive BSR MAC CE carrying LCID1, the actions are the same as in the above example, except that the LCID here can be the conventional LCID (6 bits) or the eLCID (extended LCID, 8 bits or 16 bits). This method does not require a new BSR MAC CE PDU format.

[0079] In some embodiments, the BSR MAC CE includes a first bitmap, where each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a recurring preemptive BSR based on the corresponding LCG.

[0080] In this embodiment, a new preemptive BSR MAC CE format can be introduced, in which a bitmap is introduced, where each LCG corresponds to one bit to indicate whether the parent IAB node can further trigger a recursive preemptive BSR based on this LCG, and this MAC CE format is shown in FIG. 9, where the LCGi bit set (i.e., the value is 1) indicated by the shaded portion indicates that a recursive preemptive BSR can be triggered based on the buffer report of this LCG, and vice versa is not possible.

[0081] In some embodiments, the BSR MAC CE includes a first repetition count indication for indicating a number of times a repetitive preemptive BSR for at least some LCGs may be triggered; or The BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

[0082] In this embodiment, one new preemptive BSR MAC CE format called repetitive preemptive BSR MAC CE can be introduced, which carries an indication indicating whether a repetitive preemptive BSR can be triggered or the number of repetitive preemptive BSRs. In one way, the repetitive preemptive BSR MAC CE carries one repetition count indication, indicating the repetition counts of some or all LCGs, e.g., only the number of repetitions of the highest priority LCG. In another way, the repetitive preemptive BSR MAC CE carries multiple repetition count indications, each of which indicates the repetition counts of one or multiple LCGs, and in one specific example, each LCG has one associated repetition count indication field indicating the repetition count of the preemptive BSR of the corresponding LCG, and in another specific example, multiple LCGs share one associated repetition count indication field indicating the repetition count of the preemptive BSR of these LCGs.

[0083] In some embodiments, the BSR MAC CE includes a time budget indication for indicating a time budget within which a recurring preemptive BSR of at least one LCG may be triggered.

[0084] In this embodiment, a new preemptive BSR MAC CE format called recursive preemptive BSR MAC CE can be introduced, which carries an indication of the expected time budget in which a recursive preemptive BSR can be triggered. This time budget may be arranged according to the LCG, and one or more or all LCGs can have one time budget indication, and if the time budget indicated in the recursive preemptive BSR received by an IAB node is larger than the time budget required for scheduling the corresponding uplink transmission process by this IAB node, it can also trigger a recursive preemptive BSR, but not vice versa.

[0085] It should be noted that the execution body of the recursive preemptive BSR placement method according to the embodiment of the present application may be a recursive preemptive BSR placement device, or a module for executing and loading the recursive preemptive BSR placement method in the recursive preemptive BSR placement device. In the embodiment of the present application, the recursive preemptive BSR placement method according to the embodiment of the present application is described by taking the recursive preemptive BSR placement device executing and loading the recursive preemptive BSR placement method as an example.

[0086] The embodiment of the present application provides a configuration device for a recursive preemptive BSR used in an IAB node 300, as shown in FIG. 10, the device includes: The device further includes a receiving module 310 for receiving a configuration parameter of a preemptive BSR, the configuration parameter being used to indicate whether the IAB node should trigger a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on the received preemptive BSR and sent to a parent IAB node.

[0087] In some embodiments, the configuration parameters are: A list of logical channel groups (LCGs) for which a recursive preemptive BSR can be triggered; A list of logical channels (LCH) for which a recursive preemptive BSR can be triggered; a list of data radio bearers DRBs for which a recursive preemptive BSR can be triggered; A list of business types that can trigger a recurring preemptive BSR; the type of user equipment UE that can trigger a repetitive preemptive BSR; The number of times a recursive preemptive BSR can be triggered and and a time budget within which a recurring preemptive BSR can be triggered.

[0088] In some embodiments, the configuration parameters are: First indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a recursive preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

[0089] In some embodiments, if congestion occurs on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is not triggered, and if congestion does not occur on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is triggered.

[0090] In some embodiments, the configuration parameters are conveyed to a BSR Media Access Control MAC Control Element CE.

[0091] In some embodiments, the BSR MAC CE includes one or more logical channel identifier LCID values, each indicating the number of times a repeated preemptive BSR may be triggered.

[0092] In some embodiments, The system further includes a processing module for selecting, from the one or more LCID values, an LCID value that indicates the number of times a repeat preemptive BSR may be triggered after a preemptive BSR has been triggered.

[0093] In some embodiments, the BSR MAC CE includes a first bitmap, where each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a recurring preemptive BSR based on the corresponding LCG.

[0094] In some embodiments, the BSR MAC CE includes a first repetition count indication for indicating a number of times a repetitive preemptive BSR for at least some LCGs may be triggered; or The BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

[0095] In some embodiments, the apparatus further comprises: When the IAB node generates a second iterative preemptive BSR to be sent to a parent IAB node based on the received first iterative preemptive BSR, the IAB node further includes a first generation module for subtracting 1 from the value of the first iterative count indication or the second iterative count indication in the first iterative preemptive BSR and writing it to the second iterative preemptive BSR.

[0096] In some embodiments, the BSR MAC CE includes a time budget indication for indicating a time budget within which a recurring preemptive BSR of at least one LCG may be triggered.

[0097] In some embodiments, the apparatus further comprises: When the IAB node generates a second iterative preemptive BSR to send to a parent IAB node based on the received first iterative preemptive BSR, the IAB node further includes a second generating module for subtracting a time budget required for an uplink transmission process scheduled at this hop from a time budget instruction value in the first iterative preemptive BSR to obtain a remaining time budget, and setting the remaining time budget as a time budget instruction value of the second iterative preemptive BSR.

[0098] The configuration device of the recursive preemptive BSR in the embodiment of the present application may be a device, or may be a component, integrated circuit, or chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. Illustratively, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), and the non-mobile electronic device may be a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit machine, or a self-service machine, and the embodiment of the present application is not specifically limited.

[0099] The configuration device of the recursive preemptive BSR in the embodiment of the present application may be a device having an operating system, which may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited.

[0100] It should be noted that the execution body of the recursive preemptive BSR placement method according to the embodiment of the present application may be a recursive preemptive BSR placement device, or a module for executing and loading the recursive preemptive BSR placement method in the recursive preemptive BSR placement device. In the embodiment of the present application, the recursive preemptive BSR placement method according to the embodiment of the present application is described by taking the recursive preemptive BSR placement device executing and loading the recursive preemptive BSR placement method as an example.

[0101] The embodiment of the present application provides a configuration device for a recursive preemptive BSR used in a consolidation unit 400, as shown in FIG. 11, which includes: The self-backhauled IAB node includes a sending module 410 for sending a configuration parameter of a preemptive BSR to the self-backhauled IAB node, the configuration parameter being used to indicate whether the IAB node should trigger a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on a received preemptive BSR and sent to a parent IAB node.

[0102] In some embodiments, the configuration parameters are: A list of logical channel groups (LCGs) for which a recursive preemptive BSR can be triggered; A list of logical channels (LCH) for which a recursive preemptive BSR can be triggered; a list of data radio bearers DRBs for which a recursive preemptive BSR can be triggered; A list of business types that can trigger a recurring preemptive BSR; the type of user equipment UE that can trigger a repetitive preemptive BSR; The number of times a recursive preemptive BSR can be triggered and and a time budget within which a recurring preemptive BSR can be triggered.

[0103] In some embodiments, the configuration parameters are: First indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a recursive preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

[0104] In some embodiments, if congestion occurs on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is not triggered, and if congestion does not occur on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is triggered.

[0105] In some embodiments, the configuration parameters are conveyed to a BSR Media Access Control MAC Control Element CE.

[0106] In some embodiments, the BSR MAC CE includes one or more logical channel identifier LCID values, each indicating the number of times a repeated preemptive BSR may be triggered.

[0107] In some embodiments, The system further includes a processing module for selecting, from the one or more LCID values, an LCID value that indicates the number of times a repeat preemptive BSR may be triggered after a preemptive BSR has been triggered.

[0108] In some embodiments, the BSR MAC CE includes a first bitmap, where each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a recurring preemptive BSR based on the corresponding LCG.

[0109] In some embodiments, the BSR MAC CE includes a first repetition count indication for indicating a number of times a repetitive preemptive BSR for at least some LCGs may be triggered; or The BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

[0110] In some embodiments, the BSR MAC CE includes a time budget indication for indicating a time budget within which a recurring preemptive BSR of at least one LCG may be triggered.

[0111] The configuration device of the recursive preemptive BSR in the embodiment of the present application may be a device having an operating system, which may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited.

[0112] Optionally, the embodiment of the present application further provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and can run on the processor, and when the program or instruction is executed by the processor, each process of the embodiment of the arrangement method of the iterative preemptive BSR can be realized and the same technical effect can be achieved. In order to avoid repetition of the description, no further description will be given here.

[0113] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices described above.

[0114] The electronic device of this embodiment may be a terminal. FIG. 12 is a hardware structure schematic diagram of a terminal for implementing each embodiment of the present application, and the terminal 50 includes, but is not limited to, components such as a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. As can be understood by those skilled in the art, the terminal structure shown in FIG. 12 does not constitute a limitation on the terminal, and the terminal may include more or less components than the number of components shown, or a combination of some components, or a different arrangement of components. In the embodiment of the present application, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, and a pedometer.

[0115] It should be understood that in the embodiment of the present application, the radio frequency unit 51 may be used to transmit and receive information or transmit and receive signals during a call. Specifically, it receives downlink data from a base station, and then processes the data through the processor 510, and transmits uplink data to the base station. In general, the radio frequency unit 51 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. It should be noted that the radio frequency unit 51 can also communicate with other devices through a wireless communication system or network.

[0116] The memory 59 may be used to store software programs and various data. The memory 59 may mainly include a program storage area and a data storage area. Here, the program storage area can store an operating system, an application program required for at least one function (e.g., a voice playback function, an image playback function, etc.), and the data storage area can store data generated by using the mobile phone (e.g., audio data, a phone book, etc.). The memory 59 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk memory device, a flash memory device, or other volatile solid-state memory device.

[0117] Processor 510 is the control center of the terminal, and is connected to each part of the entire terminal by various interfaces and lines, and runs or executes software programs and / or modules stored in memory 59, and also accesses data stored in memory 59, performs various functions of the terminal, processes data, and monitors the entire terminal. Processor 510 may include one or at least two processing units, and preferably, processor 510 may integrate an application processor and a modem processor, where the application processor is mainly for processing the operating system, user interface, and application programs, and the modem processor is mainly for processing wireless communication. As can be understood, the modem processor does not have to be integrated into processor 510.

[0118] The terminal 50 may further include a power source 511 (e.g., a battery) for powering each component, and preferably, the power source 511 may be logically connected to the processor 510 by a power management system, so that the power management system can realize functions such as charge / discharge management and power consumption management.

[0119] The terminal 50 also includes several functional modules not shown, which will not be further described here.

[0120] In some embodiments, the processor 510 is used to receive configuration parameters for a preemptive BSR, the configuration parameters being used to indicate whether the IAB node should trigger a recursive preemptive BSR, which is a preemptive BSR that the IAB node generates based on the received preemptive BSR and sends to a parent IAB node.

[0121] In some embodiments, the configuration parameters are: A list of logical channel groups (LCGs) for which a recursive preemptive BSR can be triggered; A list of logical channels (LCH) for which a recursive preemptive BSR can be triggered; a list of data radio bearers DRBs for which a recursive preemptive BSR can be triggered; A list of business types that can trigger a recurring preemptive BSR; the type of user equipment UE that can trigger a repetitive preemptive BSR; The number of times a recursive preemptive BSR can be triggered and and a time budget within which a recurring preemptive BSR can be triggered.

[0122] In some embodiments, the configuration parameters are: First indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a recursive preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

[0123] In some embodiments, if congestion occurs on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is not triggered, and if congestion does not occur on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is triggered.

[0124] In some embodiments, the configuration parameters are conveyed to a BSR Media Access Control MAC Control Element CE.

[0125] In some embodiments, the BSR MAC CE includes one or more logical channel identifier LCID values, each indicating the number of times a repeated preemptive BSR may be triggered.

[0126] In some embodiments, the processor 510 is adapted to select an LCID value from the one or more LCID values ​​that indicates the number of times a repeat preemptive BSR can be triggered after a preemptive BSR has been triggered.

[0127] In some embodiments, the BSR MAC CE includes a first bitmap, where each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a recurring preemptive BSR based on the corresponding LCG.

[0128] In some embodiments, the BSR MAC CE includes a first repetition count indication for indicating a number of times a repetitive preemptive BSR for at least some LCGs may be triggered; or The BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

[0129] In some embodiments, when an IAB node generates a second iterative preemptive BSR to send to a parent IAB node based on a received first iterative preemptive BSR, the processor 510 is used to subtract 1 from the value of the first iterative count indication or the second iterative count indication in the first iterative preemptive BSR and write it to the second iterative preemptive BSR.

[0130] In some embodiments, the BSR MAC CE includes a time budget indication for indicating a time budget within which a recurring preemptive BSR of at least one LCG may be triggered.

[0131] In some embodiments, when an IAB node generates a second iterative preemptive BSR to send to a parent IAB node based on the received first iterative preemptive BSR, the processor 510 is used to subtract the time budget required for the uplink transmission process scheduled at this hop from the value of the time budget indication in the first iterative preemptive BSR to obtain a remaining time budget, and set the remaining time budget as the value of the time budget indication of the second iterative preemptive BSR.

[0132] The electronic device of this embodiment may further be a network side device. As shown in Fig. 13, this network side device 600 includes an antenna 61, a radio frequency device 62, and a baseband device 63. The antenna 61 and the radio frequency device 62 are connected. In the uplink direction, the radio frequency device 62 receives information through the antenna 61, and transmits the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be transmitted and transmits it to the radio frequency device 62, and the radio frequency device 62 processes the received information and then transmits it through the antenna 61.

[0133] The above frequency band processing device may be located in a baseband device 63, and the method performed by the network side equipment in the above embodiments may be implemented in the baseband device 63, which includes a processor 64 and a memory 65.

[0134] The baseband device 63 may include, for example, at least one baseband board, on which a plurality of chips are installed, and as shown in FIG. 13, one of the chips is, for example, a processor 64, which is connected to a memory 65, calls a program in the memory 65, and performs the operation of the network side device shown in the embodiment of the above method.

[0135] The baseband unit 63 may further include a network interface 66, which is used to exchange information with the radio frequency unit 62, the interface being, for example, a common public radio interface (CPRI).

[0136] The processor here may be one processor or a collective term for multiple processing elements, for example, the processor may be a CPU, an ASIC, or one or more integrated circuits configured to implement the method executed by the network side device, such as one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, etc. The storage element may be one memory or a collective term for multiple storage elements.

[0137] Memory 65 may be volatile or nonvolatile memory, or may include both volatile and nonvolatile memory. Here, the nonvolatile memory may be Read-Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), or flash memory. The volatile memory may be Random Access Memory (RAM), which is used as an external cache. By way of example and not of limitation, many types of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (DRAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM), and Direct Rambus Random Access Memory (Direct Rambus RAM, DRRAM). Memory 65 as described herein is intended to include, without being limited to, these and any other suitable types of memory.

[0138] In some embodiments, processor 64 is used to send preemptive BSR configuration parameters to the self-backhauled IAB node, the configuration parameters being used to indicate whether the IAB node should trigger a recursive preemptive BSR, which is a preemptive BSR that the IAB node generates based on a received preemptive BSR and sends to a parent IAB node.

[0139] In some embodiments, the configuration parameters are: A list of logical channel groups (LCGs) for which a recursive preemptive BSR can be triggered; A list of logical channels (LCH) for which a recursive preemptive BSR can be triggered; a list of data radio bearers DRBs for which a recursive preemptive BSR can be triggered; A list of business types that can trigger a recurring preemptive BSR; the type of user equipment UE that can trigger a repetitive preemptive BSR; The number of times a recursive preemptive BSR can be triggered, and and a time budget within which a recurring preemptive BSR can be triggered.

[0140] In some embodiments, the configuration parameters are: First indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a recursive preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

[0141] In some embodiments, if congestion occurs on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is not triggered, and if congestion does not occur on the uplink link from the intermediate node to the parent IAB node, a recursive preemptive BSR is triggered.

[0142] In some embodiments, the configuration parameters are conveyed to a BSR Media Access Control MAC Control Element CE.

[0143] In some embodiments, the BSR MAC CE includes one or more logical channel identifier LCID values, each indicating the number of times a repeated preemptive BSR may be triggered.

[0144] In some embodiments, processor 64 is adapted to select an LCID value from the one or more LCID values ​​that indicates the number of times a repeat preemptive BSR may be triggered after a preemptive BSR has been triggered.

[0145] In some embodiments, the BSR MAC CE includes a first bitmap, where each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a recurring preemptive BSR based on the corresponding LCG.

[0146] In some embodiments, the BSR MAC CE includes a first repetition count indication for indicating a number of times a repetitive preemptive BSR for at least some LCGs may be triggered; or The BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

[0147] In some embodiments, the BSR MAC CE includes a time budget indication for indicating a time budget within which a recurring preemptive BSR of at least one LCG may be triggered.

[0148] The embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the arrangement method of the recursive preemptive BSR can be realized and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0149] Here, the processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0150] 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, the processor runs a program or instruction, and is used to realize each process of the embodiment of the configuration method of the iterative preemptive BSR, and can achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0151] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, or systems on chips.

[0152] It should be explained that in this specification, the terms "comprise", "include", or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article, or apparatus that includes a set of elements not only includes those elements, but also includes other elements not specifically listed or inherent to such process, method, article, or apparatus. In the absence of further limitations, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. It should be pointed out that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in the reverse order based on the functions involved, for example, the described method can be performed in a different order than described, and various steps can be added, omitted, or combined. Also, features described with reference to some examples can be combined in other examples.

[0153] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. Based on this understanding, the technical solution of the present application may be substantially or in part embodied in the form of a software product. The computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0154] The above describes the embodiments of the present application in conjunction with the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take the suggestions of this application and make many forms without departing from the spirit and scope of the claims of this application, all of which belong to the protection scope of this application.

Claims

1. A method for configuring a preemptive buffer status report (BSR), comprising: A method for configuring a preemptive buffer status report BSR, comprising: a self-backhauled IAB node receiving a configuration parameter for a preemptive BSR, the configuration parameter being used to indicate whether the IAB node should trigger a recursive preemptive BSR, the recursive preemptive BSR being a preemptive BSR generated by the IAB node based on the received preemptive BSR and sent to a parent IAB node.

2. The configuration parameters are: a list of logical channel groups (LCG) for which a repetitive preemptive BSR can be triggered; a list of logical channels LCH for which a repetitive preemptive BSR can be triggered; a list of data radio bearers DRB for which a repetitive preemptive BSR can be triggered; A list of transaction types that can trigger a recurring preemptive BSR; - the types of user equipment UE that can trigger a repeated preemptive BSR; The number of times a repeat preemptive BSR can be triggered; and and a time budget during which repeated preemptive BSR can be triggered.

3. The configuration parameters are: a first indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a repeated preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

4. The method for configuring a preemptive BSR according to claim 3, further comprising the steps of: not triggering a repeated preemptive BSR when congestion occurs on an uplink link from the intermediate node to a parent IAB node; and triggering a repeated preemptive BSR when congestion does not occur on an uplink link from the intermediate node to a parent IAB node.

5. The method of claim 2, wherein the configuration parameters are conveyed in a BSR Media Access Control (MAC) Control Element (CE).

6. The method of claim 5, wherein the BSR MAC CE includes one or more logical channel identifier (LCID) values, each of which indicates a number of times a repeated preemptive BSR can be triggered.

7. The method for configuring a preemptive BSR according to claim 6, further comprising: selecting, from the one or more LCID values, an LCID value indicating a number of times a repeated preemptive BSR can be triggered after a preemptive BSR has been triggered.

8. 6. The method of claim 5, wherein the BSR MAC CE includes a first bitmap, and each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a repeated preemptive BSR based on the corresponding LCG.

9. The BSR MAC CE includes a first repetition count indication for indicating the number of times a repetitive preemptive BSR of at least some LCGs can be triggered; or The method of claim 5, wherein the BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

10. The method comprises:

10. The method for arranging a preemptive BSR according to claim 9, further comprising: when an IAB node generates a second repetitive preemptive BSR to be sent to a parent IAB node based on the received first repetitive preemptive BSR, subtracting 1 from the value of the first repetitive count indication or the second repetitive count indication in the first repetitive preemptive BSR and writing the value to the second repetitive preemptive BSR.

11. The method of claim 5, wherein the BSR MAC CE includes a time budget indication for indicating a time budget within which a repeated preemptive BSR of at least one LCG can be triggered.

12. The method comprises:

12. The method of claim 11, wherein when an IAB node generates a second repetitive preemptive BSR to be sent to a parent IAB node based on the received first repetitive preemptive BSR, the method further comprises: subtracting a time budget required for an uplink transmission process scheduled at this hop from a time budget indication value in the first repetitive preemptive BSR to obtain a remaining time budget, and setting the remaining time budget as a time budget indication value of the second repetitive preemptive BSR.

13. A method for configuring a preemptive buffer status report (BSR), comprising: A method for configuring a preemptive buffer status report BSR, comprising: a centralization unit (CU) sending a configuration parameter of a preemptive BSR to a self-backhauled IAB node, the configuration parameter being used to indicate whether the IAB node triggers a repeated preemptive BSR, the repeated preemptive BSR being a preemptive BSR generated by the IAB node based on a received preemptive BSR and sent to a parent IAB node.

14. The configuration parameters are: a list of logical channel groups (LCG) for which a repetitive preemptive BSR can be triggered; a list of logical channels LCH for which a repetitive preemptive BSR can be triggered; a list of data radio bearers DRB for which a repetitive preemptive BSR can be triggered; A list of transaction types that can trigger a recurring preemptive BSR; - the types of user equipment UE that can trigger a repeated preemptive BSR; The number of times a repeat preemptive BSR can be triggered; and and a time budget within which repeated preemptive BSR can be triggered.

15. The configuration parameters are: a first indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a repeated preemptive BSR; and second indication information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

16. The method for configuring a preemptive BSR according to claim 15, further comprising: not triggering a repeated preemptive BSR if congestion occurs on an uplink link from the intermediate node to a parent IAB node; and triggering a repeated preemptive BSR if congestion does not occur on an uplink link from the intermediate node to a parent IAB node.

17. The method for configuring a preemptive BSR according to claim 14, wherein said configuration parameters are conveyed in a BSR Media Access Control (MAC) Control Element (CE).

18. 18. The method of claim 17, wherein the BSR MAC CE includes one or more logical channel LCID identifier values, each of which indicates a number of times a repeated preemptive BSR can be triggered.

19. The method for configuring a preemptive BSR according to claim 18, further comprising: selecting, from the one or more LCID values, an LCID value indicating a number of times a repeated preemptive BSR can be triggered after a preemptive BSR has been triggered.

20. 18. The method of claim 17, wherein the BSR MAC CE includes a first bitmap, and each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a repeated preemptive BSR based on the corresponding LCG.

21. The BSR MAC CE includes a first repetition count indication for indicating the number of times a repetitive preemptive BSR of at least some LCGs can be triggered; or The method of claim 17, wherein the BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

22. The method of claim 17, wherein the BSR MAC CE includes a time budget indication for indicating a time budget within which a repetitive preemptive BSR of at least one LCG can be triggered.

23. A configuration device for preemptive buffer status report (BSR), comprising: A preemptive buffer status report BSR configuration device comprising: a receiving module for receiving a preemptive BSR configuration parameter, the configuration parameter being used to indicate whether an IAB node triggers a repeated preemptive BSR, the repeated preemptive BSR being a preemptive BSR generated by the IAB node based on the received preemptive BSR and sent to a parent IAB node.

24. The configuration parameters are: a list of logical channel groups (LCG) for which a repetitive preemptive BSR can be triggered; a list of logical channels LCH for which a repetitive preemptive BSR can be triggered; a list of data radio bearers DRB for which a repetitive preemptive BSR can be triggered; A list of transaction types that can trigger a recurring preemptive BSR; - the types of user equipment UE that can trigger a repeated preemptive BSR; The number of times a repeat preemptive BSR can be triggered; and and a time budget during which repeated preemptive BSR can be triggered.

25. The configuration parameters are: a first indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a repeated preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

26. The preemptive BSR configuration device according to claim 25, wherein if congestion occurs on an uplink link from the intermediate node to a parent IAB node, a repeated preemptive BSR is not triggered, and if congestion does not occur on an uplink link from the intermediate node to a parent IAB node, a repeated preemptive BSR is triggered.

27. The preemptive BSR configuration device according to claim 24, wherein the configuration parameters are conveyed in a BSR Media Access Control (MAC) Control Element (CE).

28. The preemptive BSR configuration device according to claim 27, wherein the BSR MAC CE includes one or more logical channel identifier (LCID) values, each of which indicates a number of times a repeated preemptive BSR can be triggered.

29. 29. The preemptive BSR configuration device of claim 28, further comprising a processing module for selecting, from the one or more LCID values, an LCID value indicating a number of times a repeated preemptive BSR can be triggered after a preemptive BSR is triggered.

30. The preemptive BSR configuration device according to claim 27, wherein the BSR MAC CE includes a first bitmap, and each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a repeated preemptive BSR based on the corresponding LCG.

31. The BSR MAC CE includes a first repetition count indication for indicating the number of times a repetitive preemptive BSR of at least some LCGs can be triggered; or The preemptive BSR configuration device according to claim 27, wherein the BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

32. The apparatus comprises:

32. The preemptive BSR placement device according to claim 31, further comprising a first generating module for subtracting 1 from a value of the first repetition count indication or the second repetition count indication in the first repetition preemptive BSR and writing the value in the second repetition preemptive BSR when the IAB node generates a second repetition preemptive BSR to be sent to a parent IAB node based on the received first repetition preemptive BSR.

33. The preemptive BSR configuration device according to claim 27, wherein the BSR MAC CE includes a time budget indication for indicating a time budget within which a repetitive preemptive BSR of at least one LCG can be triggered.

34. The apparatus comprises:

34. The preemptive BSR placement device of claim 33, further comprising: a second generating module for, when an IAB node generates a second repetitive preemptive BSR to be sent to a parent IAB node based on the received first repetitive preemptive BSR, subtracting a time budget required for an uplink transmission process scheduled at this hop from a time budget indication value in the first repetitive preemptive BSR to obtain a remaining time budget, and setting the remaining time budget as a time budget indication value of the second repetitive preemptive BSR.

35. A configuration device for preemptive buffer status report (BSR), comprising: A preemptive buffer status report BSR configuration device comprising: a transmitting module for transmitting a preemptive BSR configuration parameter to a self-backhauled IAB node, the configuration parameter being used to indicate whether the IAB node should trigger a repeated preemptive BSR, the repeated preemptive BSR being a preemptive BSR generated by the IAB node based on a received preemptive BSR and sent to a parent IAB node.

36. The configuration parameters are: a list of logical channel groups (LCG) for which a repetitive preemptive BSR can be triggered; a list of logical channels LCH for which a repetitive preemptive BSR can be triggered; a list of data radio bearers DRB for which a repetitive preemptive BSR can be triggered; A list of transaction types that can trigger a recurring preemptive BSR; - the types of user equipment UE that can trigger a repeated preemptive BSR; The number of times a repeat preemptive BSR can be triggered; and and a time budget within which repeated preemptive BSR can be triggered.

37. The configuration parameters are: a first indication information for indicating whether a subsequent intermediate node of the IAB node should trigger a repeated preemptive BSR; and second instruction information for instructing a subsequent intermediate node of the IAB node to determine whether to trigger a repeated preemptive BSR based on the received preemptive BSR.

38. The preemptive BSR configuration device according to claim 37, wherein if congestion occurs on an uplink link from the intermediate node to a parent IAB node, a repeated preemptive BSR is not triggered, and if congestion does not occur on an uplink link from the intermediate node to a parent IAB node, a repeated preemptive BSR is triggered.

39. The preemptive BSR configuration device according to claim 36, wherein the configuration parameters are conveyed in a BSR Media Access Control (MAC) Control Element (CE).

40. The preemptive BSR configuration device according to claim 39, wherein the BSR MAC CE includes one or more logical channel identifier (LCID) values, each of which indicates a number of times a repeated preemptive BSR can be triggered.

41. The preemptive BSR configuration device of claim 40, further comprising a processing module for selecting, from the one or more LCID values, an LCID value indicating a number of times a repeated preemptive BSR can be triggered after a preemptive BSR is triggered.

42. The preemptive BSR configuration device according to claim 39, wherein the BSR MAC CE includes a first bitmap, and each bit in the first bitmap corresponds to an LCG and is used to indicate whether to trigger a repeated preemptive BSR based on the corresponding LCG.

43. The BSR MAC CE includes a first repetition count indication for indicating the number of times a repetitive preemptive BSR of at least some LCGs can be triggered; or The preemptive BSR configuration device according to claim 39, wherein the BSR MAC CE includes a second repetition count indication for indicating a number of times a repetitive preemptive BSR of at least one LCG can be triggered.

44. The preemptive BSR configuration apparatus according to claim 39, wherein the BSR MAC CE includes a time budget indication for indicating a time budget within which a repetitive preemptive BSR of at least one LCG can be triggered.

45. An electronic device comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the electronic device performing the steps of the method according to any one of claims 1 to 12, or performing the steps of the method according to any one of claims 13 to 22, when the program or instructions are executed by the processor.

46. A readable storage medium having a program or instructions stored thereon, the program or instructions implementing the steps of the method according to any one of claims 1 to 12, or implementing the steps of the method according to any one of claims 13 to 22, when executed by a processor.

47. A chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and wherein the processor runs a program or instructions to implement steps of the preemptive BSR placement method of any one of claims 1 to 12, or is used to implement steps of the preemptive BSR placement method of any one of claims 13 to 22.

48. A computer program product, the program product being stored in a non-volatile storage medium, the program product being executed by at least one processor to implement the steps of the method for placing a preemptive BSR according to any one of claims 1 to 12, or to implement the steps of the method for placing a preemptive BSR according to any one of claims 13 to 22.

Images