CN111148147B - BSR reporting method and relay node - Google Patents

BSR reporting method and relay node Download PDF

Info

Publication number
CN111148147B
CN111148147B CN201811302727.XA CN201811302727A CN111148147B CN 111148147 B CN111148147 B CN 111148147B CN 201811302727 A CN201811302727 A CN 201811302727A CN 111148147 B CN111148147 B CN 111148147B
Authority
CN
China
Prior art keywords
bsr
relay node
value
request message
previous
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201811302727.XA
Other languages
Chinese (zh)
Other versions
CN111148147A (en
Inventor
鲍炜
杨晓东
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN201811302727.XA priority Critical patent/CN111148147B/en
Publication of CN111148147A publication Critical patent/CN111148147A/en
Application granted granted Critical
Publication of CN111148147B publication Critical patent/CN111148147B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0278Traffic management, e.g. flow control or congestion control using buffer status reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the invention provides a BSR reporting method and a relay node, wherein the method comprises the following steps: reporting a first BSR according to a first request message or a prediction result, wherein the first request message is sent by a first node and includes a scheduling request SR or a second BSR, the prediction result includes a result of predicting that data will be received in a specific future time period, and/or a predicted uplink data amount expected to be received by the relay node in the specific future time period, wherein the uplink data amount is greater than 0. The embodiment of the invention can reduce the data transmission delay.

Description

BSR reporting method and relay node
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method for reporting a buffer status report (Buffer Status Report, BSR) and a relay node.
Background
A New relay node is introduced in a New air interface (NR) system, for example: an integrated access backhaul (Integrated Access and Backhaul, IAB) node. The relay node can extend network coverage in a wireless cascading manner. Specifically, the terminal may be connected to a home (donor) node (e.g., IAB donor) through one or more relay nodes. In the data transmission process, after receiving data sent by a previous-hop (or referred to as a previous-hop) node, a relay node reports a buffer status report (Buffer Status Report, BSR) to a next-hop node to apply for uplink transmission resources, where the previous-hop node may be a terminal or another relay node. Therefore, the BSR is reported to the next hop node only after the data sent by the previous hop is received, so that the data transmission delay is larger.
Disclosure of Invention
The embodiment of the invention provides a BSR reporting method and a relay node, which are used for solving the problem of larger data transmission delay.
In a first aspect, an embodiment of the present invention provides a BSR reporting method, which is applied to a relay node, including:
reporting a first BSR according to a first request message or a prediction result, wherein the first request message is sent by a first node and includes a scheduling request (Scheduling Request, SR) or a second BSR, the prediction result includes a result of predicting that data will be received in a specific future time period, and/or an uplink data amount expected to be received by the relay node in the specific future time period, where the uplink data amount is greater than 0.
In a second aspect, an embodiment of the present invention provides a relay node, including:
and the reporting module is used for reporting the first BSR according to a first request message or a prediction result, wherein the first request message is sent by a first node and comprises an SR or a second BSR, the prediction result comprises a result of predicting that data will be received in a future specific time period, and/or the predicted uplink data amount expected to be received by the relay node in the future specific time period is greater than 0.
In a third aspect, an embodiment of the present invention provides a relay node, including: the system comprises a memory, a processor and a program stored in the memory and capable of running on the processor, wherein the program realizes the steps in the BSR reporting method provided by the embodiment of the invention when being executed by the processor.
In a fourth aspect, an embodiment of the present invention provides a computer readable storage medium, where a computer program is stored on the computer readable storage medium, where the computer program when executed by a processor implements steps in a BSR reporting method provided by an embodiment of the present invention.
In the embodiment of the present invention, a first BSR is reported according to a first request message or a prediction result, where the first request message is sent by a first node and includes an SR or a second BSR, the prediction result includes a result that data will be received in a predicted specific time period in the future, and/or an uplink data amount expected to be received by the relay node in the predicted specific time period in the future, where the uplink data amount is greater than 0. Therefore, the relay node receives the SR or the BSR or has a prediction result, and the BSR is reported without reporting the BSR after receiving the data sent by the previous hop, so that the data transmission delay can be reduced.
Drawings
FIG. 1 is a block diagram of a network system to which embodiments of the present invention are applicable;
fig. 2 is a flowchart of a BSR reporting method provided in an embodiment of the present invention;
fig. 3 is a schematic diagram of BSR indication information according to an embodiment of the present invention;
fig. 4 is a schematic diagram of another BSR indication information according to an embodiment of the present invention;
fig. 5 is a schematic diagram of another BSR indication information according to an embodiment of the present invention;
fig. 6 is a block diagram of a relay node according to an embodiment of the present invention;
fig. 7 is a block diagram of another relay node according to an embodiment of the present invention;
fig. 8 is a block diagram of another relay node according to an embodiment of the present invention;
fig. 9 is a block diagram of another relay node according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means at least one of the connected objects, e.g., a and/or B, meaning that it includes a single a, a single B, and that there are three cases of a and B.
In embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
Embodiments of the present application are described below with reference to the accompanying drawings. The BSR reporting method and the relay node provided by the embodiment of the application can be applied to a wireless communication system. The wireless communication system may be a 5G system, or an evolved long term evolution (Evolved Long Term Evolution, lte) system, or a subsequent evolved communication system.
Referring to fig. 1, fig. 1 is a block diagram of a network system to which an embodiment of the present invention is applicable, and as shown in fig. 1, the network system includes a terminal 11, at least one relay node 12, and a home node (node) 13, where the terminal 11 may be a User Equipment (UE) or other terminal side devices, for example: terminal-side devices such as a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer), a personal digital assistant (personal digital assistant, PDA for short), a mobile internet Device (Mobile Internet Device, MID) or a Wearable Device (weardable Device), it should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present invention. The terminal 11 may be connected to the home node 13 through one or more relay nodes 12, where the relay nodes 12 may be IAB nodes, or terminals with a relay function, or other types of devices with a relay function of a base station, and it should be noted that, in the embodiment of the present invention, the specific type of the relay nodes 12 is not limited, and in addition, the relay nodes may also be referred to as a relay or a relay device. The host node 13 may be an IAB node, or may be a node with a wired backhaul, where the host node 13 and the core network may be connected by a wired link, which is not limited, and the host node 13 may be connected to the core network by other means. It should be noted that the specific type of the host node 13 is not limited in the embodiment of the present invention. In which 2 relay nodes are illustrated in the figure.
Referring to fig. 2, fig. 2 is a flowchart of a BSR reporting method according to an embodiment of the present invention, where the method applies a relay node, as shown in fig. 2, and includes the following steps:
step 201, reporting a first BSR according to a first request message or a prediction result, where the first request message is sent by a first node and includes an SR or a second BSR, the prediction result includes a result of predicting that data will be received in a specific future time period, and/or a predicted uplink data amount expected to be received by the relay node in the specific future time period, where the uplink data amount is greater than 0.
The first node may be a terminal or another relay node, and specifically, the first node may be a previous hop node of the relay node, where the previous hop node refers to a node in a previous hop of the relay node in an uplink transmission path. For example: in the uplink transmission path, the terminal is connected to the first relay node, and the first relay node is connected to the second relay node, then the previous hop node of the first relay node is the terminal, and the next hop (or called next hop) node of the first relay node is the second relay node, and the previous hop node of the second relay node is the first relay node.
The SR may be an SR that is transmitted when the LC of the terminal has data to transmit, for example: triggering BSR reporting, and as no uplink resource is available, the terminal applies the SR configuration corresponding to the LC to send the SR, wherein the uplink resource can be an uplink shared channel (Uplink Shared Channel, UL-SCH) resource.
The second BSR may be a triggered BSR report when the LC of the previous hop terminal has data to be transmitted, or may be a triggered BSR report when the LC of the previous hop relay node of the relay node has data to be transmitted.
The future specific time period may be a future specific time period after the first BSR is generated or after the first BSR is reported, for example: future 10ms or 20ms, etc.
It should be noted that, the above prediction result includes a result of predicting that data will be received in a future specific time period, and/or the predicted amount of uplink data expected to be received by the relay node in the future specific time period may be understood to include the following three cases:
1. the predicted outcome is an outcome of predicting that data will be received within a specified time period in the future, i.e., by the outcome indicating that data will be received within the specified time period in the future;
2. The prediction result includes the uplink data amount expected to be received by the relay node in the future specific time period, that is, the prediction result can indicate that the data amount will be predicted in the future specific time period, and since the uplink data amount is greater than 0, the data amount can also indicate that the data will be received in the future specific time period;
3. the prediction result includes a result of predicting that data will be received in a future specific time period, and the amount of uplink data expected to be received by the relay node in the future specific time period, that is, the prediction result includes two information, where the information is used to indicate that data will be received in the future specific time period, and the other information is used to specifically indicate the amount of uplink data expected to be received.
The prediction result may be predicted according to historical statistics, for example: predicting the expected received data amount of the relay node in the future specific time length according to the historical statistical data; alternatively, the data may be received within the above-described future specific time period based on predictions based on historical statistics, such as: when the prediction indicates that data will be received within the specific time period in the future, then the first BSR may be reported. Of course, in the embodiment of the present invention, prediction can only be performed by historical statistics, for example: the prediction may also be performed according to the current service type of the next hop node (e.g., terminal), or the number of the next hop nodes, to obtain the prediction result.
It should be noted that, in the embodiment of the present invention, if the relay node predicts the above prediction result, that is, predicts that data will be received in a specific time period in the future, the corresponding first BSR may be reported.
Preferably, the predicted result is a predicted result that satisfies a preset trigger BSR reporting condition, that is, when the predicted result satisfies the preset trigger BSR reporting condition, the relay node reports the first BSR. The first BSR is reported only when the prediction result meets the preset triggering BSR reporting condition, so that the accuracy of BSR reporting can be improved.
The preset trigger BSR reporting condition may be predefined in a protocol, or configured by a next hop node (or called a parent node) of the relay node, or configured by a network side to the relay node, or the like. For example: the preset triggering BSR reporting condition is that the expected received data amount is greater than or equal to a specific threshold, that is, when the prediction result indicates that the expected received data amount of the relay node is greater than or equal to the specific threshold within the specific future time length, reporting the first BSR. Or, the preset triggering BSR reporting condition may be that it is predicted that the buffered data of the LC with the highest priority in the relay node will never exist, that is, the LC does not currently buffer data, but it is predicted that the data corresponding to the LC will be received in a specific time period in the future; so that the first BSR may be reported when it is predicted that data corresponding to the highest priority LC will be received within a certain time period in the future. Or, the preset trigger BSR reporting condition may be that it is predicted that data corresponding to a certain LC will be received in a specific time period in the future, and no data is currently cached in the LC higher than the LC in the relay node, that is, when it is predicted that data corresponding to a certain LC will be received in a specific time period in the future, and no data is currently cached in the LC higher than the LC in the relay node, the first BSR may be reported.
Specifically, step 201 is to report a first BSR to a next hop node of the relay node, so as to apply for uplink resources through the BSR, that is, uplink resources allocated to the relay node after the next hop node of the relay node receives the first BSR, for example: uplink scheduling (UL grant).
The steps can be realized, the relay node receives the SR or the BSR, or the BSR reporting is carried out with the prediction result, and the BSR is not required to be reported after the data sent by the previous hop is received, so that the data transmission delay can be reduced.
As an optional implementation manner, the reporting the first BSR according to the first request message includes:
determining a first Logic Channel (LC) corresponding to the first request message and having data to be sent;
reporting the first BSR, wherein the LC triggering the first BSR comprises a second LC, wherein the second LC is used for transmitting the data of the first LC
The first LC to be sent may be an LC to be sent by the first node indicated by the first request message, or may determine that the first node has an LC to be sent by data according to a corresponding relationship between SR configuration of the SR and a logical channel, or determine that the first node has an LC to be sent by data according to a corresponding relationship between the BSR and a logical channel.
The second LC may be data determined according to an internal mapping relationship of the relay node and used for transmitting the first LC, where the second LC is used for transmitting the data of the first LC may be understood that, when receiving the data sent by the first node through the first LC, the data is loaded into a buffer corresponding to the second LC of the relay node, where the buffer includes PDCP and RLC layer buffers.
The triggering the LC of the first BSR to include the second LC may be triggering the LC of the first BSR to be the second LC, that is, triggering the BSR to report based on the second LC. The first BSR may be a BSR corresponding to a logical channel group (Logical Channel Group, LCG) to which the second LC belongs, for example: the first BSR may be used to indicate a Buffer Status (BS) value of the LCG to which the second LC belongs.
It should be noted that, since the first BSR is reported after receiving the request message, that is, before the first BSR is reported, the relay node does not yet receive the data sent by the first node through the first LC, when reporting the first BSR, the second LC may be empty, that is, there is no data buffer.
In this embodiment, after receiving the SR or the BSR, reporting the BSR may be implemented, so that before receiving the data sent by the first node, the BSR is triggered by the second LC to apply for uplink resources of the relay node, thereby reducing the data transmission delay.
As an alternative embodiment, in case the first request message includes the SR, the first LC includes:
and the SR used by the SR configures the corresponding LC.
The SR configuration may be a network configuration to the terminal, and the SR configuration may include a transmission period, transmission resources, and corresponding LCs, etc. The relay node may determine the SR configuration used by the relay node after receiving the SR. Preferably, the network may configure one or more SRs for the terminal, each SR corresponding to one or more logical channels. Thus, when one LC triggers a BSR, if the terminal does not have an UL-SCH available, the terminal may transmit an SR using an SR configuration corresponding to the LC.
In this embodiment, the SR configuration corresponds to LC one by one. So that the first LC can be directly determined through the SR configuration.
Or, the SR configuration corresponds to a plurality of LCs, and the first LC includes one LC of the plurality of LCs corresponding to the SR configuration. For example: the relay node selects one LC among the plurality of LCs as the first LC. Preferably, the one LC is the highest priority LC or the lowest priority LC among the plurality of LCs, that is, the relay node regards the highest priority LC or the lowest priority LC among the plurality of LCs as the first LC.
Note that, the correspondence between the SR configuration and the LC may be preset, or a protocol may be predefined, which is not limited.
In this embodiment, since the first LC to which data is to be transmitted may be determined according to the SR configuration used by the SR, it may be avoided to add additional signaling to indicate the first LC, so as to save transmission overhead, and in addition, since the content of the SR may not be changed, it may be possible to improve compatibility of the above method.
As an alternative embodiment, in case the first request message includes the second BSR, the first LC includes:
and the LCG indicated by the second BSR corresponds to LC.
The LCG may be an LCG indicated by an LCG ID in the second BSR, or the LCG may be a highest priority LCG in LCGs with data to be transmitted indicated by the second BSR.
In this embodiment, the LCGs are in one-to-one correspondence with LCs, so that the first LC can be directly determined by the LCG.
Or, the LCG corresponds to a plurality of LCs, and the first LC includes one LC of the LCG corresponds to the plurality of LCs. For example: the relay node selects one LC among the plurality of LCs as the first LC. Preferably, the one LC is the highest priority LC or the lowest priority LC among the plurality of LCs, that is, the relay node regards the highest priority LC or the lowest priority LC among the plurality of LCs as the first LC.
Note that, the correspondence between LCG and LC may be preset, or a predefined protocol, etc., which is not limited thereto.
In this embodiment, since the first LC to which data is to be transmitted may be determined according to the LCG, it may be avoided to add additional signaling to indicate the first LC, so as to save transmission overhead, and in addition, since the content of the LCG may not be changed, it may be possible to improve compatibility of the foregoing method.
As an optional implementation manner, the second LC is currently empty, and the LC in the relay node with a higher priority than the second LC is currently empty; or alternatively
The second LC is currently empty and the second LC in the relay node has the highest priority.
The fact that the second LC is currently empty may be understood that when the first BSR is triggered, the second LC is empty, that is, the second LC does not have a data buffer, because, when the relay node triggers the first BSR, the first node does not send data to the relay node through the first LC yet. The current null of the LCs with higher priority than the second LC in the relay node may be that all LCs with higher priority than the second LC in the relay node are null. The second LC with the highest priority in the relay node may be the LC with the highest priority in all LCs of the relay node.
In this embodiment, when the second LC is currently empty and the LC in the relay node with a higher priority than the second LC is currently empty, the first BSR is triggered to report; or, when the second LC is currently empty and the priority of the second LC in the relay node is highest, the first BSR is triggered to report, so as to reduce the data transmission delay.
As an optional implementation manner, if after the first BSR is reported and before the uplink scheduling is received, the relay node receives a second request message sent by a second node, where the LC to be sent corresponding to the second request message has data corresponding to the second LC, or the LC to be sent corresponding to the second request message has data corresponding to other LCs with priority lower than that of the second LC.
Wherein, the above-mentioned relay node ignoring the second request message may be understood that the relay node triggers the BSR not based on the second LC or on other LCs having a priority lower than that of the second LC.
The uplink scheduling may be, for example, uplink scheduling that the relay node sends to the relay node after reporting the first BSR to a next hop node, where the next hop node sends the first BSR to the relay node: and the next hop node performs uplink scheduling on the return of the first BSR to the relay node.
The second request message may be an SR or a BSR, and the second node may be a previous hop node of the relay node, that is, the previous hop node of the relay node may include the first node and the second node.
In addition, it is understood that the LC to be sent with data corresponds to the second LC, and the second LC is also used to transmit data of the LC, that is, the second LC is used to transmit data of the first LC, and is also used to transmit data of the LC to be sent with data corresponding to the second request message. The LC to be sent with data corresponding to the second request message may refer to a manner of determining the first LC, which is not described herein.
In this embodiment, if the second request message sent by the second node is received after the first BSR is reported and before the uplink scheduling is received, the relay node ignores the second request message, that is, triggers BSR not based on the second LC or on other LCs with priority lower than that of the second LC, so that the situation that the same LC triggers multiple BSRs and the situation that the low-priority LC triggers the BSR again when the high-priority LC has triggered the BSR can be avoided.
As an alternative embodiment, the method further comprises:
And setting a variable corresponding to the second LC to be a first value, wherein when the variable is the first value, the variable indicates that the second LC has triggered a BSR or indicates that the LC with priority lower than or equal to that of the second LC cannot trigger the BSR.
It should be noted that, the setting the variable corresponding to the second LC to the first value may be performed before the step 201, for example: when the second BSR is triggered, a variable corresponding to the second LC may be set to a first value, or when a BS value to be indicated by the second BSR is determined, a variable corresponding to the second LC may be set to a first value. Or the setting of the variable corresponding to the second LC to the first value may be performed after the step 201.
The first value may be a true value, or another value, and the inability to trigger the BSR may also be referred to as being unable to trigger the BSR.
Since the variable corresponding to the second LC is set to the first value by reporting the first BSR, it can be accurately ensured that if the second request message sent by the second node is received after the first BSR is reported and before the uplink scheduling is received, the relay node triggers the BSR not based on the second LC or not based on other LCs with priority equal to or lower than the second LC.
In addition, after the setting the variable corresponding to the second LC to the first value, the method may further include:
and if the uplink scheduling is received, setting a variable corresponding to the second LC to be a second value, wherein when the variable is the second value, the variable indicates that the second LC does not trigger the BSR.
For example: the uplink data transmission paths are as follows: terminal- > IAB node1- > IAB node2- > IAB donor, where the relay node is IAB node1, after the BSR is triggered by the LC5 of IAB node1 (LC 5 of the second LC), if the SR/BSR of another terminal or sub-IAB node reports data corresponding to the LC5 of IAB node1 before the uplink scheduling (UL grant) of IAB node2 is received, the BSR of IAB node1 is not triggered. The specific implementation method is exemplified as follows:
after determining that the data of the previous hop node will cause LC5 to trigger the first BSR, IAB node1 sets a variable v=true corresponding to LC 5; wherein LC5 and other LCs with priority equal to lower than LC5 will not trigger BSR when v=true;
when IAB node1 receives the uplink scheduling (UL grant) sent by IAB node2, the variable v corresponding to LC5 is set to false.
Optionally, the variable corresponds to the second LC, and the variable also corresponds to an LC with the same priority as the second LC.
In this embodiment, the variable may correspond to a plurality of LCs with the same priority, that is, the LCs with the same priority share a variable, so whether the LCs can trigger the BSR may be managed by setting the value of the variable, thereby improving the management performance of the relay node on BSR triggering. For example: LC1 and LC2 trigger the BSR if they have the same priority, neither LC1 nor LC2 trigger the BSR until the schedule is received.
As an optional implementation manner, the first BSR is used to indicate at least one of the following:
the BS value of the relay node;
virtual BS values.
In the embodiment of the invention, the BS value may represent the amount of buffered data.
The BS value of the relay node may be a BS value or a BSR corresponding to a buffer of the relay node, where the BS value or the BSR corresponding to the buffer of the relay node may be a BS value or a BSR corresponding to a current buffer of the relay node.
The virtual BS value may be a BS value that is virtual to the relay node, for example: the virtual BS value may be a preset value, such as a BS value defined in a protocol, or a BS value predefined by a relay node. The virtual BS value indicates a predicted BS value of a relay node in a future time period, so that the virtual BS value can apply resources to a next hop node in advance or let the next hop node accurately apply resources in advance by indicating the virtual BS value, thereby further improving the data transmission rate.
Optionally, the first BSR is further configured to indicate:
and the BS value reported by the previous hop, wherein the previous hop is the previous hop of the relay node in the uplink transmission path.
The BS value reported in the previous hop may be determined by an index of the BS value reported in the previous hop.
And the BS value of the previous hop may include:
and adding the BS values reported by all the nodes in the previous hop by taking LCG as granularity to obtain a sum value.
That is, the relay node may add BSs reported by all nodes of the previous hop with LCG as granularity, for example: LCG1 of terminal 1 corresponds to LCG3 of the above-mentioned relay node, and LCG2 of terminal 2 corresponds to LCG3 of the above-mentioned relay node, thus add BS value that LCG1 of terminal 1 reported and BS value that LCG2 of terminal 2 reported, as the BS value of LCG3 of the next hop node of the relay node reports.
The BS values reported by all nodes in the previous hop are added together with the LCG as granularity, so that the BS values reported by all nodes in the previous hop are more accurate.
In this embodiment, since the first BSR indicates the BS value reported in the previous hop, that is, reports the multi-hop BSR, the node of the next hop that receives the first BSR may be prepared in advance for the uplink resource that needs to be used by the relay node next, so as to further improve the data transmission delay.
In the embodiment of the present invention, the BS value indicated by the BSR may be a BS index (index) corresponding to the BS value obtained by looking up a table, and the BSR carries the index to indicate the corresponding BS value. In addition, the relay node can also reversely check the actual data quantity of each previous hop of data from the BS index, then add the data quantity, and then look up the table to obtain the final BS index.
Further, the first BSR is further configured to indicate:
and the BS value reported by the previous N hops, wherein N comprises any integer from 2 to T, and T is an integer greater than or equal to 2.
The BS value reported by the previous N hops may be the sum of BS values reported by all nodes of the previous N hops, for example: the BS value of each hop may be obtained by adding BS values reported by all nodes of the hop with LCG as granularity, where the BS values may be obtained from BSR reported from the previous hop.
In addition, all nodes of the previous N hops refer to a set of all nodes that need to go through N uplink transmissions and can reach the relay node.
And the N including any integer from 2 to T may indicate that the first BSR is also used to indicate BS values for each of the previous 2 hops to the previous T hops. For example: taking the relay node being IAB node1 as an example, the first BSR may indicate a BS value as shown in fig. 3.
Because the first BSR indicates the BS value reported in the previous N hops, the next hop node that receives the first BSR can more fully prepare the uplink resource that the relay node needs to use next, so as to further improve the data transmission delay.
As an alternative embodiment, the first BSR is further configured to indicate:
the method comprises the steps that a BS value reported by a previous M hop and a sum of BS values reported by a previous M+1 hop to a previous M+K hop are carried out, wherein M comprises any integer from 1 to H, H is an integer greater than or equal to 2, and K is an integer greater than or equal to 2; or alternatively
And the previous jump is to the sum of BS values reported by the previous J hops, wherein J is an integer greater than or equal to 2.
The BS values of the relay node and the BS values reported by the previous M hops may be referred to the related description of the above embodiments, which are not described herein. The sum of BS values reported by the previous m+1 to previous m+k hops may be the sum of BS values reported by all nodes in the previous m+1 to previous m+k hops, where the summation may be performed with LCG as granularity. And the sum of BS values reported by previous hop to previous J hop may be the sum of BS values reported by all nodes in previous hop to previous J hop.
In this embodiment, the sum of the BS value reported by the previous multi-hop and the BS value reported by the previous multi-hop may be reported, for example, taking the relay node as IAB node1 as an example, and the first BSR may indicate the BS value as shown in fig. 4. Or the sum of the BS value reported by the previous multi-hop and the BS value reported by the previous multi-hop may be reported. In this way, the next hop node receiving the first BSR may prepare in advance the uplink resource that the relay node needs to use next, so as to further improve the data transmission delay. And the sum of the BS values reported by multiple hops before reporting can save signaling overhead.
Of course, in the embodiment of the present invention, the content of the first BSR report is not limited to the two embodiments, for example: in the embodiment of the present invention, the sum of BS values of the previous W hops and BS values of the next T hops may be implemented, where w=0, 1,2 …, and t=0, 1,2, where the sum of BS values of the next T hops may be the sum of BS values reported by all nodes from the previous w+1 hop to the previous w+t hop, and when T is 0, it indicates that the sum of BS values is not indicated, and when W is 0, it indicates that the BS value of the previous hop is not indicated.
Optionally, the virtual BS values include:
the relay node predicts the uplink data quantity of the scheduled previous hop in the future specific time period, wherein the previous hop is the previous hop of the relay node in the uplink transmission path; or alternatively
The relay node expects the received uplink data amount in the future specific time period represented by the prediction result; or alternatively
A preset value.
The uplink data amount of the previous hop scheduled by the relay node may also be referred to as an uplink data amount of the previous hop scheduled by the relay node in the specific period, and the uplink data amount of the previous hop may be uplink data amounts of all nodes of the previous hop.
The amount of uplink data expected to be received by the relay node in the future specific time period may be predicted according to historical statistical data.
The preset value may be a BS value predefined in the protocol, or a BS value preset by the relay node.
In this embodiment, the triggering condition may include that when the first request message is received, the virtual BS value may include an uplink data amount of a previous hop that the relay node expects to schedule in the future specific time period, or a preset value. For example: that is, the SR or the BSR of the previous hop node triggers the relay node to transmit the BSR, but when the relay node performs BSR transmission, the BSR of the previous hop is not yet transmitted to the relay node, and at this time, the relay node may transmit a virtual BS value for the LCG where the corresponding LC is located.
In this embodiment, when the trigger condition includes the preset result, the virtual BS value may include: and the relay node predicts the uplink data quantity of the previous hop scheduled in the future specific time period, or the predicted result represents the uplink data quantity expected to be received by the relay node in the future specific time period, or a preset value.
The duration of the future specific time period may be Tms, where the value of T may be configured, for example: different values can be configured according to different scenes or services. In addition, the specific time period may be a preset time period, and preferably, the future specific time period is a time period after a specific time, where the specific time includes when the first BSR is generated or when the first BSR is generated.
In this embodiment, the virtual BS value may be reported, so that the next hop node that receives the first BSR may more fully prepare the uplink resource that the relay node needs to use next, so as to further improve the data transmission delay.
For example: and the relay node reports the data quantity transmitted by all nodes of the previous hop scheduled in a period of time after the first BSR is generated. Or when the relay node generates the first BSR, estimating a total amount of uplink data scheduled by the relay node (for example, a total size of the dynamic scheduling UL grant and/or the semi-persistent scheduling UL grant) for a period of time T, such as 10ms, and reporting the size and the buffer status information together, for example: as shown in fig. 5.
In various embodiments where the first BSR indicates BS values, if the first BSR is used to indicate at least two types of BS values, for example: hop-by-hop BS value, BS value of relay node, cumulative BS value (i.e., sum of BS values obtained by the above addition), and BS value of two or more types of virtual BS values. When the first BSR reports, in the reporting information, each reported BS value is identified by explicit or implicit indication information to be of a type, for example: the explicit or implicit indication information identifies the type or types to which each BS value reported belongs. Wherein the explicit indication information includes: indicating different BS types with different values of a specific domain when the BS reports, for example, indicating different BS types with different values of LCID (logical channel identification) domain in the MAC subheader; the implicit indication information includes correspondence between the number and arrangement order of the specified or preconfigured BS values and BS types: providing that when two sets (each set comprising a plurality of LCGs) BS values are reported, the first set is a hop-by-hop BS or BS value of the relay node; the second group is the accumulated BS value of N hops before the relay node; when two groups (each group comprises a plurality of LCG) BS values are reported, the first group is a hop-by-hop BS or the BS value of the relay node; the second group is the virtual BS values described above.
In the embodiment of the present invention, a first BSR is reported according to a first request message or a prediction result, where the first request message is sent by a first node and includes an SR or a second BSR, the prediction result includes a result that data will be received in a predicted specific time period in the future, and/or an uplink data amount expected to be received by the relay node in the predicted specific time period in the future, where the uplink data amount is greater than 0. Therefore, the relay node receives the SR or the BSR or has a prediction result, and reports the BSR without reporting the BSR after receiving the data sent by the previous hop, thereby reducing the data transmission delay.
It should be noted that, the various optional implementations provided by the embodiments of the present invention may be implemented in combination with each other, or may be implemented separately, where the following data transmission paths are: terminal- > IAB node1- > IAB node2- > IAB node, where the relay node exemplifies the BSR reporting method provided by the embodiment of the present invention for IAB node 1:
example 1:
in this implementation, the following triggering BSR sent by the previous hop node on the transmission path is illustrated by IAB node 1:
The LC1 of the terminal has uplink data (also called uplink transmission) to be sent, and triggers the BSR, and the terminal applies the SR configuration corresponding to the LC1 to send the SR because no UL-SCH resource is available;
the IAB node1 knows the terminal sending the SR according to the configuration used by the received SR, and determines the logical channel (e.g. LCA) with data waiting to be sent, and the determination method may use one of the following:
a) The SR configuration corresponds to the LC of the terminal one by one, and according to the SR configuration, the IAB ndoe1 can determine the LC with data waiting for the terminal, namely LC1; i.e. LC a is LC 1.
b) The SR configuration corresponds to LC 1-to-N of the terminal (e.g. the SR configuration used corresponds to LC1/LC2/LC3 of the terminal, priority: LC1> LC2> LC 3), the IAB ndoe1 may determine that the LC to which the terminal has data pending is one of LC1/LC2/LC3 according to the SR configuration; IAB node1 may assume that data is pending for either the highest priority LC (e.g., LC1, i.e., LC a is LC 1) or the lowest priority LC (e.g., LC3, i.e., LC a is LC 3);
IAB node1 knows from the internal mapping relation: the data of LCA of the terminal is received, and LC5 of IAB node1 is loaded; LC5 of IAB node1 is currently empty, and all LCs of IAB node1 with higher priority than LC5 are empty, BSR of IAB node1 is triggered, and LC of BSR is triggered to be LC5.
Example 2:
the embodiment is illustrated by the IAB node triggering the BSR after receiving the BSR sent by the previous hop node on the transmission path:
the terminal transmits a BSR to the IAB node 1; the BSR indicates that LCG1 is the highest priority among LCGs with data to be transmitted;
the IAB node1 knows that the terminal has data to transmit according to the received BSR, and determines a logical channel LCA having data to transmit, and the determining method may use one of the following:
a) LCG1 corresponds to the LCs of the terminals one by one, and IAB ndoe1 can determine the LCs with data to be sent according to LCG configuration;
b) LCG1 corresponds to LC 1-to-N of the terminal, and IAB ndoe1 can determine one of a plurality of LCs with data waiting to be sent according to LCG configuration; IAB NODE1 may assume that there is data pending for the LC with the highest priority or the LC with the lowest priority;
IAB node1 knows from the internal mapping relation: receiving LCA data of the UE, loading LC5 of IAB node 1; LC5 of IAB node1 is currently empty, and all LCs of IAB node1 with higher priority than LC5 are empty, BSR of IAB node1 is triggered, and LC of BSR is triggered to be LC5.
Referring to fig. 6, fig. 6 is a block diagram of a relay node according to an embodiment of the present invention, and as shown in fig. 6, a relay node 600 includes:
The reporting module 601 is configured to report a first BSR according to a first request message or a prediction result, where the first request message is sent by a first node and includes an SR or a second BSR, the prediction result includes a result that data will be received in a predicted specific future time period, and/or a predicted uplink data amount expected to be received by the relay node in the predicted specific future time period, where the uplink data amount is greater than 0.
Optionally, as shown in fig. 7, the reporting module 602 is configured to determine a first LC corresponding to the first request message and having data to be sent, and report the first BSR, where the LC triggering the first BSR includes a second LC, and the second LC is configured to transmit the data of the first LC.
Optionally, in a case where the first request message includes the SR, the first LC includes:
and the SR used by the SR configures the corresponding LC.
Optionally, the SR configuration corresponds to LC one-to-one; or alternatively
The SR configuration corresponds to a plurality of LCs, and the first LC includes one LC of the plurality of LCs for which the SR configuration corresponds.
Optionally, the one LC is the LC with the highest priority or the lowest priority among the plurality of LCs.
Optionally, in a case where the first request message includes the second BSR, the first LC includes:
and the LC corresponding to the logical channel group LCG indicated by the second BSR.
Optionally, the LCGs are in one-to-one correspondence with LCs; or alternatively
The LCG corresponds to a plurality of LCs, and the first LC includes one LC of the LCG corresponds to the plurality of LCs.
Optionally, the one LC is the LC with the highest priority or the lowest priority among the plurality of LCs.
Optionally, the second LC is currently empty, and LCs with priority higher than that of the second LC in the relay node are currently empty; or alternatively
The second LC is currently empty and the second LC in the relay node has the highest priority.
Optionally, if after the first BSR is reported and before the uplink scheduling is received, the relay node ignores the second request message, where the LC corresponding to the second request message and having data to be sent corresponds to the second LC, or the LC corresponding to the second request message and having data to be sent corresponds to other LCs with a priority lower than that of the second LC.
Optionally, as shown in fig. 7, the relay node 600 further includes:
A first setting module 602, configured to set a variable corresponding to the second LC to a first value, where when the variable is the first value, it indicates that the second LC has triggered a BSR, or indicates that an LC with a priority lower than or equal to that of the second LC cannot trigger a BSR.
Optionally, as shown in fig. 8, the relay node 600 further includes:
and a second setting module 603, configured to set a variable corresponding to the second LC to a second value if uplink scheduling is received, where when the variable is the second value, the second LC does not trigger BSR.
Optionally, the variable corresponds to the second LC, and the variable also corresponds to an LC of the same priority as the second LC.
Optionally, the prediction result is a prediction result meeting a preset trigger BSR reporting condition.
Optionally, the first BSR is configured to indicate at least one of:
the buffer status BS value of the relay node;
virtual BS values.
Optionally, the first BSR is further configured to indicate:
and the BS value reported by the previous hop, wherein the previous hop is the previous hop of the relay node in the uplink transmission path.
Optionally, the BS value reported by the previous hop includes:
and adding the BS values reported by all the nodes in the previous hop by taking LCG as granularity to obtain a sum value.
Optionally, the first BSR is further configured to indicate:
and the BS value reported by the previous N hops, wherein N comprises any integer from 2 to T, and T is an integer greater than or equal to 2.
Optionally, the first BSR is further configured to indicate:
the method comprises the steps that a BS value reported by a previous M hop and a sum of BS values reported by a previous M+1 hop to a previous M+K hop are carried out, wherein M comprises any integer from 1 to H, H is an integer greater than or equal to 2, and K is an integer greater than or equal to 2; or alternatively
And the previous jump is to the sum of BS values reported by the previous J hops, wherein J is an integer greater than or equal to 2.
Optionally, the virtual BS values include:
the relay node predicts the uplink data quantity of the scheduled previous hop in the future specific time period, wherein the previous hop is the previous hop of the relay node in the uplink transmission path; or alternatively
The relay node expects the received uplink data amount in the future specific time period represented by the prediction result; or alternatively
A preset value.
Optionally, the future specific time period is a time period after a specific time, where the specific time includes when the first BSR is generated or when the first BSR is generated.
The relay node provided by the embodiment of the invention can realize each process realized by the relay node in the method embodiment of fig. 2, and in order to avoid repetition, the description is omitted here, and the data transmission delay can be reduced.
Referring to fig. 9, fig. 9 is a block diagram of another relay node provided in an embodiment of the present invention, and as shown in fig. 9, the relay node 900 includes: processor 901, transceiver 902, memory 903, and bus interface, wherein:
a transceiver 902, configured to report a first BSR according to a first request message or a prediction result, where the first request message is sent by a first node, and includes a scheduling request SR or a second BSR, and the prediction result includes a result of predicting that data will be received in a specific future time period, and/or a predicted uplink data amount expected to be received by the relay node in the specific future time period, where the uplink data amount is greater than 0.
Optionally, the reporting the first BSR according to the first request message includes:
determining a first logic channel LC corresponding to the first request message and having data to be sent;
reporting the first BSR, wherein the LC triggering the first BSR includes a second LC, and the second LC is configured to transmit data of the first LC.
Optionally, in a case where the first request message includes the SR, the first LC includes:
and the SR used by the SR configures the corresponding LC.
Optionally, the SR configuration corresponds to LC one-to-one; or alternatively
The SR configuration corresponds to a plurality of LCs, and the first LC includes one LC of the plurality of LCs for which the SR configuration corresponds.
Optionally, the one LC is the LC with the highest priority or the lowest priority among the plurality of LCs.
Optionally, in a case where the first request message includes the second BSR, the first LC includes:
and the LC corresponding to the logical channel group LCG indicated by the second BSR.
Optionally, the LCGs are in one-to-one correspondence with LCs; or alternatively
The LCG corresponds to a plurality of LCs, and the first LC includes one LC of the LCG corresponds to the plurality of LCs.
Optionally, the one LC is the LC with the highest priority or the lowest priority among the plurality of LCs.
Optionally, the second LC is currently empty, and LCs with priority higher than that of the second LC in the relay node are currently empty; or alternatively
The second LC is currently empty and the second LC in the relay node has the highest priority.
Optionally, if after the first BSR is reported and before the uplink scheduling is received, the relay node ignores the second request message, where the LC corresponding to the second request message and having data to be sent corresponds to the second LC, or the LC corresponding to the second request message and having data to be sent corresponds to other LCs with a priority lower than that of the second LC.
Optionally, after the determining the BSR trigger condition, the processor 901 is further configured to:
and setting a variable corresponding to the second LC to be a first value, wherein when the variable is the first value, the variable indicates that the second LC has triggered a BSR or indicates that the LC with priority lower than or equal to that of the second LC cannot trigger the BSR.
Optionally, after setting the variable corresponding to the second LC to the first value, the processor 901 is further configured to:
and if the uplink scheduling is received, setting a variable corresponding to the second LC to be a second value, wherein when the variable is the second value, the variable indicates that the second LC does not trigger the BSR.
Optionally, the variable corresponds to the second LC, and the variable also corresponds to an LC of the same priority as the second LC.
Optionally, the prediction result is a prediction result meeting a preset trigger BSR reporting condition.
Optionally, the first BSR is configured to indicate at least one of:
the buffer status BS value of the relay node;
virtual BS values.
Optionally, the first BSR is further configured to indicate:
and the BS value reported by the previous hop, wherein the previous hop is the previous hop of the relay node in the uplink transmission path.
Optionally, the BS value reported by the previous hop includes:
and adding the BS values reported by all the nodes in the previous hop by taking LCG as granularity to obtain a sum value.
Optionally, the first BSR is further configured to indicate:
and the BS value reported by the previous N hops, wherein N comprises any integer from 2 to T, and T is an integer greater than or equal to 2.
Optionally, the first BSR is further configured to indicate:
the method comprises the steps that a BS value reported by a previous M hop and a sum of BS values reported by a previous M+1 hop to a previous M+K hop are carried out, wherein M comprises any integer from 1 to H, H is an integer greater than or equal to 2, and K is an integer greater than or equal to 2; or alternatively
And the previous jump is to the sum of BS values reported by the previous J hops, wherein J is an integer greater than or equal to 2.
Optionally, the virtual BS values include:
the relay node predicts the uplink data quantity of the scheduled previous hop in the future specific time period, wherein the previous hop is the previous hop of the relay node in the uplink transmission path; or alternatively
The relay node expects the received uplink data amount in the future specific time period represented by the prediction result; or alternatively
A preset value.
Optionally, the future specific time period is a time period after a specific time, where the specific time includes when the first BSR is generated or when the first BSR is generated.
The relay node can reduce the data transmission delay.
Wherein the transceiver 902 is configured to receive and transmit data under the control of the processor 901, the transceiver 902 comprising at least two antenna ports.
In fig. 9, a bus architecture may comprise any number of interconnected buses and bridges, with various circuits of the one or more processors, represented in particular by processor 901, and the memory, represented by memory 903, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 902 may be a number of elements, i.e., include a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 904 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 901 is responsible for managing the bus architecture and general processing, and the memory 903 may store data used by the processor 901 in performing operations.
Preferably, the embodiment of the present invention further provides a relay node, which includes a processor 910, a memory 909, and a computer program stored in the memory 909 and capable of running on the processor 910, where the computer program when executed by the processor 910 implements each process of the above embodiment of the BSR reporting method, and the same technical effects can be achieved, so that repetition is avoided and redundant description is omitted here.
The embodiment of the invention also provides a computer readable storage medium, and a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the process of the BSR reporting method embodiment provided by the embodiment of the invention is realized, and the same technical effect can be achieved, so that repetition is avoided, and no redundant description is provided here. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.

Claims (23)

1. The Buffer Status Report (BSR) reporting method is applied to a relay node and is characterized by comprising the following steps:
reporting a first BSR according to a first request message or a prediction result, wherein the first request message is sent by a first node and includes a scheduling request SR or a second BSR, the prediction result includes a result of predicting that data will be received in a specific future time period, and/or a predicted uplink data amount expected to be received by the relay node in the specific future time period, wherein the uplink data amount is greater than 0;
wherein, under the condition that the first BSR is reported according to the first request message, the first BSR is configured to indicate: a virtual cache state BS value, the virtual BS value comprising:
the relay node predicts the uplink data quantity of the scheduled previous hop in a specific time period in the future, wherein the previous hop is the previous hop of the relay node in an uplink transmission path; or alternatively
The relay node expects the received uplink data quantity in a specific time period in the future;
the future specific time period is a time period after a specific time, and the specific time includes when the first BSR is generated or when the first BSR is generated;
And when the first request message includes the second BSR, reporting the first BSR according to the first request message or the prediction result, including:
and determining the virtual BS value of the logical channel group LCG corresponding to the first BSR according to the second BSR so as to generate the first BSR.
2. The method of claim 1, wherein reporting the first BSR based on the first request message comprises:
determining a first logic channel LC corresponding to the first request message and having data to be sent;
reporting the first BSR, wherein the LC triggering the first BSR includes a second LC, and the second LC is configured to transmit data of the first LC.
3. The method of claim 2, wherein, in the case where the first request message includes the SR, the first LC comprises:
and the SR used by the SR configures the corresponding LC.
4. The method of claim 3, wherein the SR configuration corresponds one-to-one to the LC; or alternatively
The SR configuration corresponds to a plurality of LCs, and the first LC includes one LC of the plurality of LCs for which the SR configuration corresponds.
5. The method of claim 4, wherein the one LC is the highest priority or lowest priority LC of the plurality of LCs.
6. The method of claim 2, wherein the first LC in the case where the first request message includes the second BSR comprises:
and the LC corresponding to the logical channel group LCG indicated by the second BSR.
7. The method of claim 6, wherein the LCGs are in one-to-one correspondence with LCs; or alternatively
The LCG corresponds to a plurality of LCs, and the first LC includes one LC of the LCG corresponds to the plurality of LCs.
8. The method of claim 7, wherein the one LC is the highest priority or lowest priority LC of the plurality of LCs.
9. The method of claim 2, wherein the second LC is currently empty and LCs in the relay node having a higher priority than the second LC are currently empty; or alternatively
The second LC is currently empty and the second LC in the relay node has the highest priority.
10. The method of claim 2, wherein if a second request message sent by a second node is received after the first BSR is reported and before uplink scheduling is received, the relay node ignores the second request message, where an LC with data to be sent corresponding to the second request message corresponds to the second LC, or an LC with data to be sent corresponding to the second request message corresponds to other LCs with a priority lower than that of the second LC.
11. The method of claim 2, wherein the method further comprises:
and setting a variable corresponding to the second LC to be a first value, wherein when the variable is the first value, the variable indicates that the second LC has triggered a BSR or indicates that the LC with priority lower than or equal to that of the second LC cannot trigger the BSR.
12. The method of claim 11, wherein after setting the variable corresponding to the second LC to the first value, the method further comprises:
and if the uplink scheduling is received, setting a variable corresponding to the second LC to be a second value, wherein when the variable is the second value, the variable indicates that the second LC does not trigger the BSR.
13. The method of claim 11, wherein the variable corresponds to the second LC and the variable also corresponds to an LC of the same priority as the second LC.
14. The method of claim 1, wherein the prediction result is a prediction result that satisfies a preset trigger BSR reporting condition.
15. The method of any of claims 1-14, wherein, in the case of reporting the first BSR in accordance with the first request message, the first BSR is further to indicate:
The BS value of the relay node; or alternatively, the process may be performed,
in case the first BSR is reported according to the prediction result, the first BSR is further configured to indicate at least one of:
the BS value of the relay node;
virtual BS values.
16. The method of claim 15, wherein the first BSR is further for indicating:
and the BS value reported by the previous hop, wherein the previous hop is the previous hop of the relay node in the uplink transmission path.
17. The method of claim 16, wherein the BS value reported by the previous hop comprises:
and adding the BS values reported by all the nodes in the previous hop by taking LCG as granularity to obtain a sum value.
18. The method of claim 16, wherein the first BSR is further for indicating:
and the BS value reported by the previous N hops, wherein N comprises any integer from 2 to T, and T is an integer greater than or equal to 2.
19. The method of claim 15, wherein the first BSR is further for indicating:
the method comprises the steps that a BS value reported by a previous M hop and a sum of BS values reported by a previous M+1 hop to a previous M+K hop are carried out, wherein M comprises any integer from 1 to H, H is an integer greater than or equal to 2, and K is an integer greater than or equal to 2; or alternatively
And the previous jump is to the sum of BS values reported by the previous J hops, wherein J is an integer greater than or equal to 2.
20. The method of claim 15, wherein the virtual BS value comprises, in the case of reporting the first BSR according to the prediction result:
the relay node predicts the uplink data quantity of the scheduled previous hop in the future specific time period, wherein the previous hop is the previous hop of the relay node in the uplink transmission path; or alternatively
The relay node expects the received uplink data amount in the future specific time period represented by the prediction result; or alternatively
A preset value.
21. A relay node, comprising:
the reporting module is configured to report a first BSR according to a first request message or a prediction result, where the first request message is sent by a first node and includes an SR or a second BSR, the prediction result includes a result of predicting that data will be received in a specific future time period, and/or a predicted uplink data amount expected to be received by the relay node in the specific future time period, where the uplink data amount is greater than 0;
wherein, under the condition that the first BSR is reported according to the first request message, the first BSR is configured to indicate: a virtual BS value, the virtual BS value comprising:
The relay node predicts the uplink data quantity of the scheduled previous hop in the future specific time period, wherein the previous hop is the previous hop of the relay node in the uplink transmission path; or alternatively
The relay node expects the received uplink data amount in the future specific time period represented by the prediction result;
the future specific time period is a time period after a specific time, and the specific time includes when the first BSR is generated or when the first BSR is generated;
and when the first request message includes the second BSR, reporting the first BSR according to the first request message or the prediction result, including:
and determining the virtual BS value of the logical channel group LCG corresponding to the first BSR according to the second BSR so as to generate the first BSR.
22. A relay node, comprising: a memory, a processor, and a program stored on the memory and executable on the processor, which when executed by the processor, performs the steps in the BSR reporting method of any one of claims 1 to 20.
23. A computer readable storage medium, having stored thereon a computer program which when executed by a processor performs the steps in the BSR reporting method of any of claims 1 to 20.
CN201811302727.XA 2018-11-02 2018-11-02 BSR reporting method and relay node Active CN111148147B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811302727.XA CN111148147B (en) 2018-11-02 2018-11-02 BSR reporting method and relay node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811302727.XA CN111148147B (en) 2018-11-02 2018-11-02 BSR reporting method and relay node

Publications (2)

Publication Number Publication Date
CN111148147A CN111148147A (en) 2020-05-12
CN111148147B true CN111148147B (en) 2023-10-03

Family

ID=70516034

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811302727.XA Active CN111148147B (en) 2018-11-02 2018-11-02 BSR reporting method and relay node

Country Status (1)

Country Link
CN (1) CN111148147B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113301604B (en) * 2020-02-24 2023-04-07 维沃移动通信有限公司 Buffer status reporting method, relay terminal equipment and computer readable storage medium
CN113923711A (en) * 2020-07-09 2022-01-11 大唐移动通信设备有限公司 Method and device for reporting buffer status report and relay terminal
WO2022106972A1 (en) * 2020-11-20 2022-05-27 Telefonaktiebolaget Lm Ericsson (Publ) Application layer preemptive scheduling requests for ultra-low latency
CN114007233B (en) * 2021-10-22 2024-03-22 锐迪科微电子科技(上海)有限公司 Buffer status report BSR reporting method and device and electronic equipment
WO2024015274A1 (en) * 2022-07-11 2024-01-18 Interdigital Patent Holdings, Inc. Methods and apparatuses for performing uplink (ul) data prediction and reporting predicted ul buffer status
WO2024016147A1 (en) * 2022-07-19 2024-01-25 Qualcomm Incorporated Bsr based on traffic estimation
CN115868236A (en) * 2022-09-26 2023-03-28 北京小米移动软件有限公司 Information transmission control method, information transmission control device, communication equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998621A (en) * 2009-08-21 2011-03-30 华为技术有限公司 Buffer status report (BSR) reporting method, relay node (RN), evolved node base (eNB) and system
CN104185290A (en) * 2013-05-24 2014-12-03 中兴通讯股份有限公司 Data scheduling method, relay equipment, relay node and system
WO2017074437A1 (en) * 2015-10-30 2017-05-04 Nokia Technologies Oy Procedures for reporting buffer status
CN108243458A (en) * 2016-12-27 2018-07-03 北京信威通信技术股份有限公司 A kind of method and device of the resource allocation of multi-hop Mesh network
CN108307426A (en) * 2017-12-19 2018-07-20 上海华为技术有限公司 A kind of resource regulating method and device based on wireless tcp

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101632739B1 (en) * 2009-06-18 2016-06-22 한국전자통신연구원 Data Transmission Method In Communication Systems and Relay Performing the Method
US9585038B2 (en) * 2013-03-13 2017-02-28 Futurewei Technologies, Inc. Forward traffic announcements for enhanced resource reservation in high speed mobile relays

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998621A (en) * 2009-08-21 2011-03-30 华为技术有限公司 Buffer status report (BSR) reporting method, relay node (RN), evolved node base (eNB) and system
CN104185290A (en) * 2013-05-24 2014-12-03 中兴通讯股份有限公司 Data scheduling method, relay equipment, relay node and system
WO2017074437A1 (en) * 2015-10-30 2017-05-04 Nokia Technologies Oy Procedures for reporting buffer status
CN108243458A (en) * 2016-12-27 2018-07-03 北京信威通信技术股份有限公司 A kind of method and device of the resource allocation of multi-hop Mesh network
CN108307426A (en) * 2017-12-19 2018-07-20 上海华为技术有限公司 A kind of resource regulating method and device based on wireless tcp

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"R2-103131 Discussion on BSR with Relay";ZTE;《3GPP tsg_ran\WG2_RL2》;20100504;全文 *
R2-1707455 "BSR enhancements for pre-processing";MediaTek Inc.;《3GPP tsg_ran\WG2_RL2》;20170625;全文 *
S2-010813 "Missing LCS QoS, Priority, Request type, Assistance data, Client type, Stop reporting type parameters over Iu interface RANAP 25.413 (LOCATION REPORTING CONTROL and LOCATION REPORT messages)";S2;《3GPP tsg_sa\WG2_Arch》;20010316;全文 *

Also Published As

Publication number Publication date
CN111148147A (en) 2020-05-12

Similar Documents

Publication Publication Date Title
CN111148147B (en) BSR reporting method and relay node
RU2407194C2 (en) Requesting clearance from basic station to send packets in queue at mobile station in compliance with its transmission delay
US8385931B2 (en) Methods and arrangements for allocating scheduling request resources in a wireless communication system
US8948006B2 (en) System for managing uplink quality of service (QoS) in cellular network
JP6044813B2 (en) Communications system
US20170303319A1 (en) Transmission resource requesting method and apparatus
RU2510598C2 (en) Method and device in wireless communication system
US10728920B2 (en) Method, apparatus, and system for controlling data transmission
US20090113086A1 (en) Method for providing a buffer status report in a mobile communication network
US8854999B2 (en) Method and arrangement in a wireless communication system
KR102082281B1 (en) Message transmission method and user equipment
WO2021160061A1 (en) Method of logical channel prioritization to support sidelink relay
US20220150938A1 (en) Bsr triggering method and device, and storage medium and user equipment
US20220322343A1 (en) Resource allocation for carrier aggregation
CN112584342B (en) Communication method and communication device
EP3338499B1 (en) Decreasing free-riding data traffic in uplink scheduling
WO2019240808A1 (en) Backhaul scheduling
CN110830955A (en) Control method of user equipment, control method of base station and user equipment
CN111132223B (en) Data packet transmission method and communication equipment
CN113557779B (en) Method and equipment for scheduling request transmission
CN112567858B (en) Shared resource configuration for bandwidth portions
US10098040B2 (en) Use of shared resources indicated by template frame
EP2009943B1 (en) Uplink transmission in mobile networks
CN113940122A (en) Method, device and system for determining association between logical channel groups
CN113260071B (en) BSR reporting method, network device and computer readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant