CN111148147A - BSR reporting method and relay node - Google Patents
BSR reporting method and relay node Download PDFInfo
- Publication number
- CN111148147A CN111148147A CN201811302727.XA CN201811302727A CN111148147A CN 111148147 A CN111148147 A CN 111148147A CN 201811302727 A CN201811302727 A CN 201811302727A CN 111148147 A CN111148147 A CN 111148147A
- Authority
- CN
- China
- Prior art keywords
- bsr
- relay node
- value
- data
- hop
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling 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, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted uplink data amount expected to be received by the relay node in the future specific time period, and the uplink data amount is greater than 0. The embodiment of the invention can reduce the data transmission time delay.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a Buffer Status Report (BSR) reporting method and a relay node.
Background
A relay node is newly introduced into a New Radio (NR) system, for example: an Integrated Access and Backhaul (IAB) node. The relay node can expand the network coverage in a wireless cascading mode. Specifically, the terminal may be connected to a host (donor) node (e.g., IAB donor) via 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 (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 node of the next hop 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, aiming at solving the problem of longer data transmission delay.
In a first aspect, an embodiment of the present invention provides a BSR reporting method, applied to a relay node, including:
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 a Scheduling Request (SR) or a second BSR, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted uplink data amount expected to be received by the relay node in the future specific 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:
a reporting module, 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, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted amount of uplink data that is expected to be received by the relay node in the future specific time period, where the amount of uplink data is greater than 0.
In a third aspect, an embodiment of the present invention provides a relay node, including: the BSR reporting method includes a memory, a processor, and a program stored in the memory and capable of running on the processor, where the program implements the steps of the BSR reporting method provided in the embodiments of the present invention when 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, and when the computer program is executed by a processor, the computer program implements steps in the BSR reporting method provided in the 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, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted amount of uplink data that is expected to be received by the relay node in the future specific time period, where the amount of uplink data is greater than 0. Therefore, when the relay node receives the SR or the BSR, or the prediction result exists, the BSR is reported, and the BSR does not need to be reported after the data sent by the previous hop is received, so that the data transmission delay can be reduced.
Drawings
Fig. 1 is a block diagram of a network system to which an embodiment of the present invention is applicable;
fig. 2 is a flowchart of a BSR reporting method according to 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 provided in the embodiment of the present invention;
fig. 5 is a schematic diagram of another BSR indication information provided in the embodiment of the present invention;
fig. 6 is a structural diagram of a relay node according to an embodiment of the present invention;
fig. 7 is a structural diagram of another relay node according to an embodiment of the present invention;
fig. 8 is a structural diagram of another relay node according to an embodiment of the present invention;
fig. 9 is a structural diagram of another relay node according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, 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 expressly listed, 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 that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.
In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
Embodiments of the present invention are described below with reference to the accompanying drawings. The BSR reporting method and the relay node provided by the embodiment of the invention can be applied to a wireless communication system. The wireless communication system may be a 5G system, an Evolved Long Term Evolution (lte) system, or a subsequent lte communication system.
Referring to fig. 1, fig. 1 is a structural 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 host node (donor node) 13, where the terminal 11 may be a User Equipment (UE) or other terminal-side devices, for example: a terminal side Device such as a Mobile phone, a Tablet personal Computer (Tablet personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device), it should be noted that a specific type of the terminal 11 is not limited in the embodiment of the present invention. The terminal 11 may be connected to the host node 13 through one or more relay nodes 12, where the relay node 12 may be an IAB node, or a terminal with a relay function, or another type of device with a relay function of a base station, and it should be noted that in the embodiment of the present invention, a specific type of the relay node 12 is not limited, and the relay node may also be referred to as a relay or a relay device. The host node 13 may be an IAB donor may be a node having a wired backhaul (wiredbackhaul), and the host node 13 and the core network may be connected through a wired link, which is not limited to this, and the host node 13 may also be connected with the core network through other manners. It should be noted that the specific type of the host node 13 is not limited in the embodiment of the present invention. In the figure, 2 relay nodes are illustrated as an example.
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, and as shown in fig. 2, the method includes the following steps:
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, so that the previous-hop node of the first relay node is the terminal, 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 sent when the LC of the terminal has data to send, for example: triggering BSR reporting, and sending an SR by the terminal by applying SR configuration corresponding to the LC because no Uplink resource is available, wherein the Uplink resource can be an Uplink Shared Channel (UL-SCH) resource.
The second BSR may be a BSR report triggered when the LC of the previous hop terminal has data to send, or a BSR report triggered when the LC of the previous hop relay node of the relay node has data to send.
The future specific time period may be a future specific time period after the first BSR is generated or reported, for example: future 10ms or 20ms, etc.
It should be noted that the prediction result includes a result that data is predicted to be received in a future specific time period, and/or the predicted amount of uplink data that the relay node expects to receive in the future specific time period may be understood to include the following three cases:
the prediction result is a result of predicting that the data will be received in a specific time period in the future, namely the result indicates that the data will be received in the specific time period in the future;
the prediction result includes the amount of uplink data expected to be received by the relay node in the specific future time period, that is, the prediction result can indicate the amount of data predicted to be received in the specific future time period, and since the amount of uplink data is greater than 0, the amount of data can also indicate that the data is received in the specific future time period;
and thirdly, the prediction result comprises a result of predicting that the data will be received in a specific time period in the future and the amount of uplink data expected to be received by the relay node in the specific time period in the future, that is, the prediction result comprises two pieces of information, wherein the two pieces of information are used for indicating that the data will be received in the specific time period in the future, and the other piece of information is used for specifically indicating the amount of uplink data expected to be received.
The prediction result may be predicted according to historical statistical data, for example: predicting the data volume expected to be received by the relay node in the future specific time span according to historical statistical data; alternatively, data is predicted to be received in the future for a certain period of time based on historical statistics, such as: when the prediction result indicates that data will be received within the future specific time period, the first BSR may be reported. Of course, in the embodiment of the present invention, prediction may be performed only through historical statistical data, for example: the prediction result can be obtained according to the current service type of the next-hop node (e.g., terminal), or the number of the next-hop nodes.
It should be noted that, in the embodiment of the present invention, when the relay node predicts the prediction result, that is, predicts that data will be received in a specific time period in the future, the relay node may report the corresponding first BSR.
Preferably, the prediction result is a prediction result that meets a preset trigger BSR reporting condition, that is, when the prediction result meets 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 BSR reporting condition, so that the BSR reporting accuracy can be improved.
The preset BSR reporting condition may be predefined in a protocol, configured by a next-hop node (or referred to as a parent node) of the relay node, configured by a network side to the relay node, or the like. For example: the preset 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 future specific time period, the first BSR is reported. Or, the preset BSR reporting condition may be that it is predicted that the cache data of the LC with the highest priority in the relay node will exist from scratch, that is, the LC does not currently have cache data, but it is predicted that the data corresponding to the LC will be received in a specific time period in the future; therefore, when the data corresponding to the LC with the highest priority is predicted to be received in a specific time period in the future, the first BSR can be reported. Or, the preset BSR reporting condition may be that data corresponding to a certain LC is predicted to be received in a future specific time period, and no data is currently buffered in the LC with a priority higher than that of the LC in the relay node, that is, when data corresponding to a certain LC is predicted to be received in a future specific time period and no data is currently buffered in the LC with a priority higher than that of 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, the next-hop node of the relay node receives the uplink resources allocated to the relay node after receiving the first BSR, for example: uplink scheduling (UL grant).
Through the steps, the relay node reports the BSR after receiving the SR or the BSR or having a prediction result, and does not need to report the BSR after receiving the data sent by the previous hop, so that the data transmission delay can be reduced.
As an optional implementation manner, the reporting of the first BSR according to the first request message includes:
determining a first Logical Channel (LC) to which data is to be sent, corresponding to the first request message;
reporting the first BSR, wherein the LC triggering the first BSR comprises a second LC, and the second LC is used for transmitting data of the first LC
The first LC to which data is sent may be an LC to which data is sent by the first node indicated by the first request message, or may determine that the first node has the LC to which data is sent according to a correspondence between SR configuration of an SR and a logical channel, or determine that the first node has the LC to which data is sent according to a correspondence between a BSR and a logical channel.
The second LC may be data for transmitting the first LC, which is determined according to an internal mapping relationship of the relay node, where the second LC is configured to transmit the data of the first LC, and it may be understood that, after 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 a PDCP layer buffer and an RLC layer buffer.
The LC triggering the first BSR may include a second LC, where the LC triggering the first BSR is the second LC, that is, the second LC triggers BSR reporting. The first BSR may be a BSR corresponding to a 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 an 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 reporting the first BSR, the relay node has not received 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, the BSR reporting may be performed after receiving the SR or the BSR, so that the BSR may be triggered by the second LC before receiving the data sent by the first node to apply for the uplink resource of the relay node, thereby reducing the data transmission delay.
As an optional implementation manner, in a case that the first request message includes the SR, the first LC includes:
the SR used by the SR configures the corresponding LC.
The SR configuration may be a network configuration to a terminal, and the SR configuration may include a transmission cycle, a transmission resource, and a corresponding LC. After receiving the SR, the relay node may determine an SR configuration used by the relay node. 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 BSR, if the terminal does not have UL-SCH available, the terminal may transmit SR using SR configuration corresponding to the LC.
In this embodiment, the SR configuration corresponds to the LC one-to-one. So that the first LC can be directly determined by 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 of the LCs among the plurality of LCs as the first LC. Preferably, the one LC is an LC having a highest priority or a lowest priority among the plurality of LCs, that is, the relay node uses an LC having a highest priority or a lowest priority among the plurality of LCs as the first LC.
It should be noted that, the SR configuration and LC correspondence may be preset, or a protocol is predefined, and the like, which is not limited in this respect.
In this embodiment, the first LC to be sent with data may be determined according to the SR configuration used by the SR, so that an additional signaling indication of the first LC may be avoided to save transmission overhead, and in addition, the compatibility of the above method may be improved because the content of the SR may not be changed.
As an optional implementation manner, in a case that the first request message includes the second BSR, the first LC includes:
the LCG indicated by the second BSR corresponds to the LC.
The LCG may be an LCG indicated by an LCG ID in the second BSR, or the LCG may be an LCG of a highest priority among LCGs to which data is to be transmitted, indicated by the second BSR.
In this embodiment, the LCGs correspond to the LCs one-to-one, 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 plurality of LCs corresponding to the LCG. For example: the relay node selects one of the LCs among the plurality of LCs as the first LC. Preferably, the one LC is an LC having a highest priority or a lowest priority among the plurality of LCs, that is, the relay node uses an LC having a highest priority or a lowest priority among the plurality of LCs as the first LC.
The correspondence between the LCG and the LC may be preset, or a protocol is predefined, and the correspondence is not limited thereto.
In this embodiment, the first LC to which data is to be sent may be determined according to the LCG, so that an additional signaling indication of the first LC may be avoided to save transmission overhead, and in addition, the content of the LCG may not be changed, so that the compatibility of the above method may be improved.
As an optional implementation manner, the second LC is currently empty, and an LC with a higher priority than the second LC in the relay node is currently empty; or
The second LC is currently empty and the second LC is highest priority in the relay node.
The second LC is currently empty, which may be understood as that the second LC is empty when the first BSR is triggered, that is, the second LC has no data buffer, because the first node has not sent data to the relay node through the first LC when the relay node triggers the first BSR. The LC having a higher priority than the second LC in the relay node may be currently empty, and all LCs having a higher priority than the second LC in the relay node may be empty. And the second LC may have the highest priority in the relay node, and the second LC may be the LC having the highest priority among all LCs in the relay node.
In this embodiment, it may be implemented that when a second LC is currently empty and an LC with a higher priority than the second LC in the relay node 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, triggering the reporting of the first BSR may be implemented, so as to reduce data transmission delay.
As an optional implementation manner, 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 there is an LC to be sent for data and the second LC corresponding to the second request message, or there is an LC to be sent for data and another LC having a priority lower than that of the second LC corresponding to the second request message.
The above-mentioned ignoring of the second request message by the relay node may be understood as that the relay node triggers the BSR not based on the second LC or other LCs having a lower priority than the second LC.
The uplink scheduling may be uplink scheduling that the relay node sends to the relay node after reporting the first BSR to the next-hop node, for example: and the next hop node performs uplink scheduling returned to the relay node according to the first BSR.
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, the LC to be sent with data corresponds to the second LC, which may be understood as that 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. For the LC to be sent corresponding to the second request message, reference may be made to a manner of determining the first LC, which is not described herein again.
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, the BSR is not triggered based on the second LC or based on other LCs having a lower priority than the second LC, so that a situation where the same LC triggers multiple BSRs and a situation where a low-priority LC triggers a BSR again when a high-priority LC has triggered a BSR can be avoided.
As an optional implementation, the method further comprises:
setting a variable corresponding to the second LC as a first value, wherein when the variable is the first value, the variable indicates that the second LC already triggers a BSR, or indicates that the LC with the priority lower than or equal to the second LC cannot trigger the BSR.
It should be noted that, the setting of the variable corresponding to the second LC to the first value may be performed before step 201, for example: when the second BSR is triggered, the variable corresponding to the second LC may be set to a first value, or when the BS value that the second BSR needs to indicate is determined, the variable corresponding to the second LC may be set to the first value. Or the above-mentioned setting of the variable corresponding to the second LC to the first value may be performed after step 201.
The first value may be a true (true) value or another value, and the non-triggering BSR may also be referred to as a non-triggering BSR.
Since the reporting of the first BSR sets the variable corresponding to the second LC to the first value, it can be accurately ensured that the relay node does not trigger the BSR based on the second LC or other LCs having a priority equal to or lower than the second LC if the second request message sent by the second node is received after the reporting of the first BSR and before the uplink scheduling is received.
In addition, after the setting the variable corresponding to the second LC to the first value, the method may further include:
and if 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 path is: a terminal- > IAB node1- > IAB node2- > IAB node, where the relay node is IAB node1 as an example, after LC5 of IAB node1 (the second LC is LC5) triggers a BSR, before receiving an uplink scheduling (UL grant) of IAB node2, if there is data of LC5 corresponding to IAB node1 reported by SR/BSRs of other terminals or sub-IAB nodes, the BSR of IAB node1 is not triggered. The specific implementation method is as follows:
the IAB node1 sets the variable v corresponding to LC5 to true after determining that the data of the previous-hop node will cause LC5 to trigger the first BSR; wherein, when v is true, LC5 and other LCs with priority equal to lower than LC5 will not be able to trigger a BSR;
when IAB node1 receives the uplink schedule (UL grant) sent by IAB node2, set variable v corresponding to LC5 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 corresponds to multiple LCs with the same priority, that is, multiple LCs with the same priority share one variable, so that whether multiple LCs can trigger a BSR can be managed by setting the value of the variable, thereby improving the BSR triggering management performance of the relay node. For example: LC1 and LC2, if they have the same priority, then LC1 triggered the BSR, and neither LC1 nor LC2 could trigger the BSR until the schedule was received.
As an optional implementation manner, the first BSR is configured to indicate at least one of the following:
a BS value of the relay node;
virtual BS values.
In the embodiment of the present invention, the BS value may represent the amount of buffered data.
The BS value of the relay node may be a BS value or BSR corresponding to the buffer of the relay node, where the BS value or BSR corresponding to the buffer of the relay node may be a BS value or BSR corresponding to the current buffer of the relay node.
The virtual BS value may be a BS value virtualized by the relay node, for example: the virtual BS value may be a preset value, such as a BS value defined in the protocol, or a BS value predefined by the relay node. The virtual BS value represents a predicted BS value of the relay node in a future time period, so that the virtual BS value can be indicated to extract the resource application from the next hop node or lead the next hop node to accurately apply the resource in advance, and the data transmission rate can be further improved.
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 by the previous hop may be determined by an index of the BS value reported by the previous hop.
And the BS value of the previous hop may include:
and the BS values reported by all the nodes in the previous hop take LCG as a sum value obtained by granularity addition.
That is, the relay node may add BSs reported by all nodes of the previous hop by using the LCG as the granularity, for example: the LCG1 of the terminal 1 corresponds to the LCG3 of the relay node, and the LCG2 of the terminal 2 corresponds to the LCG3 of the relay node, so that the BS value reported by the LCG1 of the terminal 1 and the BS value reported by the LCG2 of the terminal 2 are added and reported as the BS value of the LCG3 of the next hop node of the relay node.
The LCG is used as the granularity for addition, so that the reported BS value is more accurate, and in the embodiment of the present invention, the BS value of the previous hop is not limited to be added by using the LCG as the granularity, and in some scenarios, the BS values reported by all nodes of the previous hop may be added to obtain one BS value.
In this embodiment, since the first BSR indicates the BS value reported in the previous hop, that is, reports the multi-hop BSR, the next-hop node receiving the first BSR can prepare the uplink resource to be used by the relay node in advance, so as to further improve the data transmission delay.
It should be noted that, 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 through table lookup, and the BSR carries the index to indicate the corresponding BS value. In addition, the relay node can also find the actual data volume of each previous hop of data back to the BS index, add the data volumes, and find the table to obtain the final BS index.
Further, the first BSR is further configured to indicate:
and the BS value reported by the first 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 first N hops may be a sum of BS values reported by all nodes of the first 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, and these BS values may be obtained from BSR reported by a previous hop.
In addition, all the nodes of the previous N hops are a set of all the nodes that need to go through uplink transmission N times and can reach the relay node.
And the N includes any integer from 2 to T, which may indicate that the first BSR is further configured to indicate a BS value of each of the first 2 hops to the first T hops. For example: taking the relay node as the 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 by the first N hops, the next hop node receiving the first BSR can more fully prepare the uplink resource that needs to be used by the relay node next time, so as to further improve the data transmission delay.
As an optional implementation, the first BSR is further configured to indicate:
the method comprises the steps of reporting a BS value by a first M hop, and summing the BS values reported by the first M +1 hop to a first M + K hop, 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
And the sum of the reported BS values from the previous jump to the previous J jump, wherein J is an integer greater than or equal to 2.
The BS value of the relay node and the BS value reported by the previous M hops may refer to the related description of the above embodiments, which is not described herein again. The sum of BS values reported from the first M +1 hop to the first M + K hop may be the sum of BS values reported from all nodes in the first M +1 hop to the first M + K hop, where the summation may be performed by using LCG as a granularity. The sum of the BS values reported by the previous hop to the previous J hop may be the sum of the BS values reported by all nodes in the previous hop to the 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 the IAB node1 as an example, 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. Therefore, the next hop node receiving the first BSR can prepare the uplink resource which needs to be used by the relay node in advance, so as to further improve the data transmission delay. And the sum of BS values reported by multiple hops before reporting can save signaling overhead.
Of course, in the embodiment of the present invention, the content reported by the first BSR is not limited to the two embodiments, for example: the BS value of the relay node may be only reported, that is, in the embodiment of the present invention, a sum of a BS value of a previous W hop by hop + a BS value of a next T hop may be implemented, where W is 0,1,2 …, and T is 0,1,2, where the sum of the BS values of the next T hop may be a sum of BS values reported by all nodes from the previous W +1 hop to the previous W + T hop, where T is 0 and indicates that the sum of the BS values is not indicated, and W is 0 and indicates that the BS value of the previous W hop by hop is not indicated.
Optionally, the virtual BS value includes:
the relay node predicts the uplink data volume of a previous hop scheduled in the future specific time period, wherein the previous hop is the previous hop of the relay node in an uplink transmission path; or
The predicted result represents the amount of uplink data expected to be received by the relay node in the specific future time period; or
A preset value.
The uplink data amount of the previous hop scheduled by the relay node may also be referred to as the 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 the uplink data amount of all nodes of the previous hop.
The amount of uplink data expected to be received by the relay node in the specific future 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, when the triggering condition includes that the first request message is received, the virtual BS value may include an uplink data amount of a previous hop expected to be scheduled by the relay node in the future specific time period, or a preset value. For example: that is, the SR or BSR of the previous hop node triggers the relay node to send the BSR, but when the relay node sends the BSR, the BSR of the previous hop is not yet sent to the relay node, and at this time, the relay node may send 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: the uplink data amount of the previous hop expected to be scheduled by the relay node in the future specific time period, or the uplink data amount expected to be received by the relay node in the future specific time period represented by the prediction result, or a preset value.
The duration of the future specific time period may be Tms, where the size of the value 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 future specific time includes when the first BSR is generated or when the first BSR is completely generated.
In this embodiment, reporting the virtual BS value may be implemented, so that the next-hop node that receives the first BSR can more fully prepare uplink resources that the relay node needs to use next, so as to further improve data transmission delay.
For example: and the relay node reports the data volume transmitted by all nodes of the previous hop scheduled and scheduled in a period of time after the first BSR is generated. Or when the relay node generates the first BSR, it estimates the total amount of uplink data scheduled for a later period of time T, e.g. 10ms (e.g. the total size of the dynamically scheduled UL grant and/or the semi-persistently scheduled UL grant), and reports 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: a hop-by-hop BS value, a BS value of the relay node, an accumulated BS value (i.e., the sum of the BS values obtained by the above-described addition), and a virtual BS value. At the time of reporting the first BSR, in the reporting information, the type of each reported BS value is identified by explicit or implicit indication information, for example: the explicit or implicit indication information identifies that each reported BS value belongs to one type or several types. Wherein the explicit indication information includes: when the BS reports, different BS types are indicated by different values of a specific domain, for example, different BS types are indicated by different values of LCID (logical channel identification) domains in MAC subheaders; the implicit indication information includes the corresponding relation between the number and the arrangement sequence of the specified or pre-configured BS values and the BS types: when two groups (each group comprises a plurality of LCGs) of BS values are reported as specified, the first group is a hop-by-hop BS or the BS value of the relay node; the second group is the accumulated BS value of the previous N hops of the relay node; when reporting two groups (each group comprises a plurality of LCGs) of BS values, the first group is a hop-by-hop BS or the BS value of the relay node; the second group is the above virtual BS value.
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, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted amount of uplink data that is expected to be received by the relay node in the future specific time period, where the amount of uplink data is greater than 0. Therefore, when the relay node receives the SR or the BSR, or the prediction result exists, the BSR is reported, and the BSR is not reported after the data sent by the previous hop is received, so that the data transmission delay can be reduced.
It should be noted that various optional implementations provided in the embodiments of the present invention may be implemented by combining with each other, or implemented separately, where the following uplink data transmission paths are: a terminal- > IAB node1- > IAB node2- > IAB node, where the relay node is IAB node1, and the BSR reporting method provided by the embodiment of the present invention is exemplified by:
example 1:
in this implementation, the IAB node1 triggers a BSR after receiving the SR sent by the previous hop node on the transmission path, for example:
the LC1 of the terminal has uplink data (also called uplink transmission) to be sent, triggers BSR, and sends SR by applying SR configuration corresponding to the LC1 as 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 to be sent, and the determination method may adopt one of the following:
a) the SR configuration corresponds to LC of the terminal one by one, and according to the SR configuration, the IAB ndoe1 can determine that the terminal has LC to be sent, namely LC 1; i.e. LC a is LC 1.
b) The SR configuration corresponds to LC 1-to-N of the terminal (as used SR configuration corresponds to LC1/LC2/LC3 of the terminal, priority: LC1> LC2> LC3), according to the SR configuration, the IAB ndoe1 can determine that the LC for which the terminal has data to send is one of LC1/LC2/LC 3; IAB node1 may assume that the LC with the highest priority (e.g., LC1, i.e., LC a is LC1) or the LC with the lowest priority (e.g., LC3, i.e., LC a is LC3) has data to transmit;
IAB node1 knows from the internal mapping: the LCA data of the terminal is received and loaded into the LC5 of the IAB node 1; LC5 of IAB node1 is currently empty, and all LCs of IAB node1 with priority higher than LC5 are empty, then the BSR of IAB node1 is triggered, and the LC triggering the BSR is LC 5.
Example 2:
this embodiment is exemplified by that the IAB node triggers a BSR after receiving a BSR sent by a previous hop node on a transmission path:
the terminal delivers the BSR to the IAB node 1; the BSR indicates that LCG with data waiting for transmission has the highest priority LCG 1;
the IAB node1 knows that the terminal has data to transmit according to the received BSR, and determines a logical channel LCA for which data is to be transmitted, and the determination method may adopt one of the following items:
a) LCG1 corresponds to LC of the terminal one by one, and according to LCG configuration, IAB ndoe1 can determine LC with data to be sent;
b) the LCG1 corresponds to LC 1-to-N of the terminal, and the IAB ndoe1 can determine one of a plurality of LCs with data to be sent according to the LCG configuration; IAB NODE1 may assume that the LC with the highest priority or the LC with the lowest priority has data to transmit;
IAB node1 knows from the internal mapping: the LCA data of the UE is received and loaded into the LC5 of the IAB node 1; LC5 of IAB node1 is currently empty, and all LCs of IAB node1 with priority higher than LC5 are empty, then the BSR of IAB node1 is triggered, and the LC triggering the BSR is LC 5.
Referring to fig. 6, fig. 6 is a structural diagram of a relay node according to an embodiment of the present invention, and as shown in fig. 6, a relay node 600 includes:
a reporting module 601, 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, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted amount of uplink data that is expected to be received by the relay node in the future specific time period, where the amount of uplink data 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 used to transmit data of the first LC.
Optionally, in a case that the first request message includes the SR, the first LC includes:
the SR used by the SR configures the corresponding LC.
Optionally, the SR configuration corresponds to the LC one-to-one; or
The SR configuration corresponds to a plurality of LCs, and the first LC includes one of the plurality of LCs corresponding to the SR configuration.
Optionally, the LC is an LC with the highest priority or an LC with the lowest priority among the LCs.
Optionally, in a case that the first request message includes the second BSR, the first LC includes:
and the LC corresponding to the LCG indicated by the second BSR.
Optionally, the LCGs correspond to the LCs one to one; or
The LCG corresponds to a plurality of LCs, and the first LC comprises one of the LCG corresponding to the plurality of LCs.
Optionally, the LC is an LC with the highest priority or an LC with the lowest priority among the LCs.
Optionally, the second LC is currently empty, and an LC with a priority higher than that of the second LC in the relay node is currently empty; or
The second LC is currently empty and the second LC is highest priority in the relay node.
Optionally, 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 there is a LC to be sent corresponding to the second request message and the second LC corresponds to the LC, or there is a LC to be sent corresponding to the second request message and another LC having a priority lower than that of the second LC corresponds to the 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, the variable 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:
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, it indicates that the second LC does not trigger a BSR.
Optionally, the variable corresponds to the second LC, and the variable also corresponds to an LC having the same priority as the second LC.
Optionally, the prediction result is a prediction result that meets a preset BSR reporting condition.
Optionally, the first BSR is configured to indicate at least one of:
a 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 the BS values reported by all the nodes in the previous hop take LCG as a sum value obtained by granularity addition.
Optionally, the first BSR is further configured to indicate:
and the BS value reported by the first 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 of reporting a BS value by a first M hop, and summing the BS values reported by the first M +1 hop to a first M + K hop, 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
And the sum of the reported BS values from the previous jump to the previous J jump, wherein J is an integer greater than or equal to 2.
Optionally, the virtual BS value includes:
the relay node predicts the uplink data volume of a previous hop scheduled in the future specific time period, wherein the previous hop is the previous hop of the relay node in an uplink transmission path; or
The predicted result represents the amount of uplink data expected to be received by the relay node in the specific future time period; or
A preset value.
Optionally, the specific future time period is a time period after a specific time, where the specific future time includes when the first BSR is generated or when the first BSR is completely generated.
The relay node provided in the embodiment of the present invention can implement each process implemented by the relay node in the method embodiment of fig. 2, and for avoiding repetition, details are not described here, and data transmission delay can be reduced.
Referring to fig. 9, fig. 9 is a structural diagram of another relay node according to an embodiment of the present invention, and as shown in fig. 9, the relay node 900 includes: a processor 901, a transceiver 902, a memory 903, and a bus interface, wherein:
the transceiver 902 is configured to report the first BSR according to a first request message or a prediction result, where the first request message is sent by the first node and includes a scheduling request SR or a second BSR, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted amount of uplink data that the relay node is expected to receive in the future specific time period, where the amount of uplink data 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 comprises a second LC, and the second LC is used for transmitting data of the first LC.
Optionally, in a case that the first request message includes the SR, the first LC includes:
the SR used by the SR configures the corresponding LC.
Optionally, the SR configuration corresponds to the LC one-to-one; or
The SR configuration corresponds to a plurality of LCs, and the first LC includes one of the plurality of LCs corresponding to the SR configuration.
Optionally, the LC is an LC with the highest priority or an LC with the lowest priority among the LCs.
Optionally, in a case that the first request message includes the second BSR, the first LC includes:
and the LC corresponding to the LCG indicated by the second BSR.
Optionally, the LCGs correspond to the LCs one to one; or
The LCG corresponds to a plurality of LCs, and the first LC comprises one of the LCG corresponding to the plurality of LCs.
Optionally, the LC is an LC with the highest priority or an LC with the lowest priority among the LCs.
Optionally, the second LC is currently empty, and an LC with a priority higher than that of the second LC in the relay node is currently empty; or
The second LC is currently empty and the second LC is highest priority in the relay node.
Optionally, 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 there is a LC to be sent corresponding to the second request message and the second LC corresponds to the LC, or there is a LC to be sent corresponding to the second request message and another LC having a priority lower than that of the second LC corresponds to the LC.
Optionally, after determining the BSR triggering condition, the processor 901 is further configured to:
setting a variable corresponding to the second LC as a first value, wherein when the variable is the first value, the variable indicates that the second LC already triggers a BSR, or indicates that the LC with the priority lower than or equal to 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 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 having the same priority as the second LC.
Optionally, the prediction result is a prediction result that meets a preset BSR reporting condition.
Optionally, the first BSR is configured to indicate at least one of:
a 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 the BS values reported by all the nodes in the previous hop take LCG as a sum value obtained by granularity addition.
Optionally, the first BSR is further configured to indicate:
and the BS value reported by the first 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 of reporting a BS value by a first M hop, and summing the BS values reported by the first M +1 hop to a first M + K hop, 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
And the sum of the reported BS values from the previous jump to the previous J jump, wherein J is an integer greater than or equal to 2.
Optionally, the virtual BS value includes:
the relay node predicts the uplink data volume of a previous hop scheduled in the future specific time period, wherein the previous hop is the previous hop of the relay node in an uplink transmission path; or
The predicted result represents the amount of uplink data expected to be received by the relay node in the specific future time period; or
A preset value.
Optionally, the specific future time period is a time period after a specific time, where the specific future time includes when the first BSR is generated or when the first BSR is completely generated.
The relay node can reduce data transmission delay.
Wherein the transceiver 902 is configured to receive and transmit data under the control of the processor 901, and the transceiver 902 includes at least two antenna ports.
In fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 901 and various circuits of memory represented by memory 903 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 902 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 904 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 901 is responsible for managing a bus architecture and general processing, and the memory 903 may store data used by the processor 901 in performing operations.
Preferably, an embodiment of the present invention further provides a relay node, which includes a processor 910, a memory 909, and a computer program that is stored in the memory 909 and can be run on the processor 910, and when the computer program is executed by the processor 910, the respective processes of the above BSR reporting method embodiment are implemented, and the same technical effect can be achieved, and in order to avoid repetition, details are not described here again.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the BSR reporting method embodiment provided in the embodiment of the present invention, and can achieve the same technical effect, and in order to avoid repetition, the computer program is not described herein again. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an 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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (24)
1. A 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, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted uplink data amount expected to be received by the relay node in the future specific time period, and the uplink data amount is greater than 0.
2. The method of claim 1, wherein reporting the first BSR according to 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 comprises a second LC, and the second LC is used for transmitting data of the first LC.
3. The method of claim 2, wherein in a case that the first request message includes the SR, the first LC includes:
the SR used by the SR configures the corresponding LC.
4. The method of claim 3, wherein the SR configuration corresponds one-to-one with LC; or
The SR configuration corresponds to a plurality of LCs, and the first LC includes one of the plurality of LCs corresponding to the SR configuration.
5. The method of claim 4, wherein the one LC is a highest priority or a lowest priority LC among the plurality of LCs.
6. The method of claim 2, wherein in a case that the first request message includes the second BSR, the first LC comprises:
and the LC corresponding to the LCG indicated by the second BSR.
7. The method of claim 6, wherein the LCGs correspond one-to-one to LCCs; or
The LCG corresponds to a plurality of LCs, and the first LC comprises one of the LCG corresponding to the plurality of LCs.
8. The method of claim 7, wherein the one LC is a highest priority or a lowest priority LC among the plurality of LCs.
9. The method of claim 2, wherein the second LC is currently empty, and wherein LCs in the relay node having a higher priority than the second LC are currently empty; or
The second LC is currently empty and the second LC is highest priority in the relay node.
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 a LC to which data is to be sent corresponds to the second LC, or a LC to which data is to be sent corresponds to the second request message corresponds to another LC having a lower priority than the second LC.
11. The method of claim 2, wherein the method further comprises:
setting a variable corresponding to the second LC as a first value, wherein when the variable is the first value, the variable indicates that the second LC already triggers a BSR, or indicates that the LC with the priority lower than or equal to the second LC cannot trigger the BSR.
12. The method of claim 11, wherein after the setting the variable corresponding to the second LC to the first value, the method further comprises:
and if 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 satisfying a predetermined trigger BSR reporting condition.
15. The method of any of claims 1-14, wherein the first BSR is to indicate at least one of:
a buffer status 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 values reported by the previous hop comprise:
and the BS values reported by all the nodes in the previous hop take LCG as a sum value obtained by granularity addition.
18. The method of claim 16, wherein the first BSR is further for indicating:
and the BS value reported by the first 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 of reporting a BS value by a first M hop, and summing the BS values reported by the first M +1 hop to a first M + K hop, 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
And the sum of the reported BS values from the previous jump to the previous J jump, wherein J is an integer greater than or equal to 2.
20. The method of claim 15, wherein the virtual BS value comprises:
the relay node predicts the uplink data volume of a previous hop scheduled in the future specific time period, wherein the previous hop is the previous hop of the relay node in an uplink transmission path; or
The prediction result represents the amount of uplink data expected to be received by the relay node in the specific future time period; or
A preset value.
21. The method of claim 20, wherein the particular period of time in the future is a period of time subsequent to a particular time, the particular time in the future comprising when the first BSR is generated or when the first BSR is generated.
22. A relay node, comprising:
a reporting module, 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, and the prediction result includes a result predicted that data will be received in a future specific time period and/or a predicted amount of uplink data that is expected to be received by the relay node in the future specific time period, where the amount of uplink data is greater than 0.
23. A relay node, comprising: a memory, a processor and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the steps in the BSR reporting method according to any one of claims 1 to 21.
24. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the BSR reporting method according to any one of claims 1 to 21.
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 true CN111148147A (en) | 2020-05-12 |
| CN111148147B 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) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021169965A1 (en) * | 2020-02-24 | 2021-09-02 | 维沃移动通信有限公司 | Cache state reporting method, relay terminal device, and computer-readable storage medium |
| CN113923711A (en) * | 2020-07-09 | 2022-01-11 | 大唐移动通信设备有限公司 | Method and device for reporting buffer status report and relay terminal |
| CN114007233A (en) * | 2021-10-22 | 2022-02-01 | 锐迪科微电子科技（上海）有限公司 | Buffer Status Report (BSR) reporting method and device and electronic equipment |
| WO2022106972A1 (en) * | 2020-11-20 | 2022-05-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Application layer preemptive scheduling requests for ultra-low latency |
| 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 |
| WO2024065109A1 (en) * | 2022-09-26 | 2024-04-04 | 北京小米移动软件有限公司 | Information transmission control method and apparatus, communication device and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100322144A1 (en) * | 2009-06-18 | 2010-12-23 | Electronics And Telecommunications Research Institute | Data transmission method in communication system and relay apparatus performing the same |
| CN101998621A (en) * | 2009-08-21 | 2011-03-30 | 华为技术有限公司 | Buffer status report (BSR) reporting method, relay node (RN), evolved node base (eNB) and system |
| US20140274064A1 (en) * | 2013-03-13 | 2014-09-18 | Futurewei Technologies, Inc. | Forward traffic announcements for enhanced resource reservation in high speed mobile relays |
| 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 |
-
2018
- 2018-11-02 CN CN201811302727.XA patent/CN111148147B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100322144A1 (en) * | 2009-06-18 | 2010-12-23 | Electronics And Telecommunications Research Institute | Data transmission method in communication system and relay apparatus performing the same |
| CN101998621A (en) * | 2009-08-21 | 2011-03-30 | 华为技术有限公司 | Buffer status report (BSR) reporting method, relay node (RN), evolved node base (eNB) and system |
| US20120149298A1 (en) * | 2009-08-21 | 2012-06-14 | Huawei Technologies Co., Ltd. | Method for buffer status report reporting, relay node, e-utran nodeeb, and system |
| US20140274064A1 (en) * | 2013-03-13 | 2014-09-18 | Futurewei Technologies, Inc. | Forward traffic announcements for enhanced resource reservation in high speed mobile relays |
| 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)
| Title |
|---|
| MEDIATEK INC.: "R2-1707455 "BSR enhancements for pre-processing"", 《3GPP TSG_RAN\WG2_RL2》 * |
| S2: "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)"", 《3GPP TSG_SA\WG2_ARCH》 * |
| ZTE: ""R2-103131 Discussion on BSR with Relay"", 《3GPP TSG_RAN\WG2_RL2》 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021169965A1 (en) * | 2020-02-24 | 2021-09-02 | 维沃移动通信有限公司 | Cache state reporting method, relay terminal device, and computer-readable storage medium |
| CN113923711A (en) * | 2020-07-09 | 2022-01-11 | 大唐移动通信设备有限公司 | Method and device for reporting buffer status report and relay terminal |
| WO2022007952A1 (en) * | 2020-07-09 | 2022-01-13 | 大唐移动通信设备有限公司 | Method and apparatus 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 |
| CN114007233A (en) * | 2021-10-22 | 2022-02-01 | 锐迪科微电子科技（上海）有限公司 | Buffer Status Report (BSR) reporting method and device and electronic equipment |
| 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 |
| WO2024065109A1 (en) * | 2022-09-26 | 2024-04-04 | 北京小米移动软件有限公司 | Information transmission control method and apparatus, communication device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111148147B (en) | 2023-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111148147B (en) | BSR reporting method and relay node | |
| US8385931B2 (en) | Methods and arrangements for allocating scheduling request resources in a wireless communication system | |
| RU2726952C1 (en) | Data transmission method and equipment | |
| US8948006B2 (en) | System for managing uplink quality of service (QoS) in cellular network | |
| RU2486713C2 (en) | Method and devices in wireless communication system | |
| US20180234989A1 (en) | Message Transmission Method and User Equipment | |
| US8854999B2 (en) | Method and arrangement in a wireless communication system | |
| CN110115059B (en) | Method and terminal for transmitting data packet | |
| US20190159073A1 (en) | Method for transmitting information, network device and terminal device | |
| CN102308654A (en) | Method and arrangement in a wireless communication system | |
| US20220150938A1 (en) | Bsr triggering method and device, and storage medium and user equipment | |
| CN105900512B (en) | transmission resource determining method, access point and station | |
| CN112584342A (en) | Communication method and communication device | |
| CN112788698A (en) | Data processing method and device and terminal equipment | |
| CN110139389B (en) | Method and device for reporting buffer status and computer storage medium | |
| CN110225594B (en) | Method and device for adjusting scheduling request period | |
| CN111132223B (en) | Data packet transmission method and communication equipment | |
| EP3503616B1 (en) | Multi-air interface communication method and device | |
| CN113923724A (en) | Flow control method and device | |
| CN113873572A (en) | Wireless communication method and terminal equipment | |
| CN111918328A (en) | User equipment resource scheduling method and device | |
| CN113260071B (en) | BSR reporting method, network device and computer readable storage medium | |
| CN113840307B (en) | Request sending method, resource allocation method, terminal and network equipment | |
| US9480070B1 (en) | Bearer data power boosting in a wireless communication system | |
| WO2024000461A1 (en) | Methods and apparatuses for a buffer status report |
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 |