CN102056332A - Method and system for optimizing processing flow of buffer zone status report - Google Patents
Method and system for optimizing processing flow of buffer zone status report Download PDFInfo
- Publication number
- CN102056332A CN102056332A CN200910236838XA CN200910236838A CN102056332A CN 102056332 A CN102056332 A CN 102056332A CN 200910236838X A CN200910236838X A CN 200910236838XA CN 200910236838 A CN200910236838 A CN 200910236838A CN 102056332 A CN102056332 A CN 102056332A
- Authority
- CN
- China
- Prior art keywords
- bsr
- lcg
- report
- size
- triggered
- 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.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
本发明公开了一种缓冲区状态报告处理流程的优化方法，该方法包括：存在多于1个逻辑信道组(LCG)有可传输的数据，且上行资源不足以上报长缓冲区状态报告(BSR)时，选择截短BSR或新的BSR媒体接入控制(MAC)控制元的格式上报BSR；或者，选择不上报BSR，等待下次上报。本发明还公开了一种缓冲区状态报告处理流程的优化系统，该系统中，选择上报单元，用于当存在多于1个LCG有可传输的数据，且上行资源不足以上报长BSR时，选择截短BSR或新的BSR MAC控制元的格式上报BSR。采用本发明的方法及系统，针对上行资源不足以上报长BSR的情况，完善了BSR的上报。
The invention discloses a method for optimizing the processing flow of a buffer status report. The method includes: there is more than one logical channel group (LCG) with transmittable data, and the uplink resource is insufficient to report a long buffer status report (BSR) ), choose to report the BSR in the format of the truncated BSR or the new BSR medium access control (MAC) control element; or choose not to report the BSR and wait for the next report. The present invention also discloses a system for optimizing the processing flow of the buffer state report. In the system, the reporting unit is selected to be used when there is more than one LCG with transmittable data and the uplink resource is insufficient to report the long BSR. Select the truncated BSR or new BSR MAC control element format to report the BSR. By adopting the method and system of the present invention, the report of the BSR is perfected for the situation that the uplink resource is insufficient to report the long BSR.
Description
Technical Field
The present invention relates to the field of digital mobile communications technologies, and in particular, to a method and a system for optimizing a Buffer Status Reporting (BSR) processing flow in a wireless communication system.
Background
Fig. 1 is a schematic diagram of an E-UTRAN radio interface protocol uplink layer 2 structure. The E-UTRAN is an Evolved universal terrestrial Radio Access Network of a third generation mobile communication Long Term Evolution (LTE) system and is composed of a plurality of enhanced base stations (eNBs), and is expressed by Evolved universal terrestrial Radio Access Network. In fig. 1, at a Media Access Control (MAC) protocol layer, a scheduling/priority handling function entity exists. User Equipment (UE) reports the BSR, and informs the base station of information of data available for transmission in an uplink buffer, so as to implement an uplink scheduling function and a priority processing function.
The BSR is classified into three types according to different trigger conditions: regular BSR, padding BSR and periodic BSR. As described separately below.
The triggering condition of the regular BSR includes that transmittable upper layer data arrives from a logical channel belonging to a Logical Channel Group (LCG), and if there is no transmittable upper layer data in an existing logical channel belonging to the LCG, the regular BSR is triggered; if the existing logic channel belonging to the LCG has upper layer data which can be transmitted and the logic channel of the new data has higher priority than the logic channel of the existing data, the regular BSR is triggered. In addition, if the BSR retransmission timer is over time and there is upper layer data to be transmitted in the existing logical channel belonging to the LCG, the regular BSR is triggered.
The triggering condition for padding the BSR includes that the UE has obtained uplink resources, and padding bits in the uplink resources are sufficient to accommodate transmission of the BSR.
The triggering condition for periodic BSR includes BSR period timer expiration.
The transmission format of the BSR is that BSR MAC control elements are encapsulated in MAC PDUs and transmitted on an Uplink Shared Channel (UL-SCH). The BSR MAC control element includes three formats: short BSR, truncated BSR, and long BSR. Wherein, the format of the short BSR is the same as that of the truncated BSR, and the short BSR is composed of a field indicating LCG and a field indicating the size of the corresponding buffer, as shown in fig. 2. The long BSR is composed of four fields indicating a buffer size, which correspond to LCG ID #0 to LCG ID #3 in order, as shown in fig. 3. Three different BSRs may be distinguished according to a field indicating a Logical Channel Identity (LCID) in the MAC subheader, where LCID 11100 denotes a truncated BSR, LCID 11101 denotes a short BSR, and LCID 11110 denotes a long BSR.
For the regular BSR and the periodic BSR, if more than 1 LCG has transmittable data, the long BSR is adopted for reporting, otherwise, the short BSR is adopted for reporting.
For padding BSR, if padding bits are larger than or equal to the sum of the long BSR and the MAC subheader size, reporting by using the long BSR; otherwise, if more than 1 LCG has transmittable data, using the truncated BSR to report the buffer size of the LCG where the highest priority logical channel with transmittable data is located, otherwise using the short BSR to report.
At least one BSR is triggered since the last BSR transmission or the first time, the following procedure is followed: if the current Transmission Time Interval (TTI) has uplink resources for first transmission, generating a BSR MAC control element according to the rule, and starting or restarting a BSR retransmission timer; if the reported BSR is not the truncated BSR, starting or restarting a periodic BSR timer; if the current TTI does not have uplink resources for first transmission and a regular BSR is triggered, a Scheduling Request (SR) is triggered.
All triggered BSRs are cancelled in two cases, one is: the uplink grant is sufficient to transfer all the transmittable data but insufficient to transfer the BSR MAC control element and its MAC subheader; the other situation is that: a BSR is transmitted.
The triggered BSR includes a regular BSR or a periodic BSR, and the processing flow is shown in fig. 5, and includes the following steps:
102, generating a BSR MAC control element; judging whether more than 1 LCG has transmittable data, if yes, executing step 103; otherwise, go to step 104.
103, reporting by adopting a long BSR; proceed to step 105.
And step 104, reporting by adopting a short BSR.
It can be seen that the process flow of fig. 5 is not complete. In case of insufficient uplink resources (the uplink resources may be 16 bits at minimum), for example, the uplink resources available for the first transmission in the current TTI are 16 bits or 24 bits, and the triggered BSR is a periodic BSR, and there are more than 1 LCG having data to transmit. At this time, a BSR MAC control element should be generated according to the processing flow of fig. 5, and for a periodic BSR, if more than 1 LCG has transmittable data, long BSR reporting is adopted, that is, 32 bits are required, and obviously, the uplink resource at this time cannot be satisfied.
In summary, in the existing flow, how to process the situation that uplink resources are not enough to report a long BSR when a periodic BSR is involved is not standardized, and the same problem also exists when a conventional BSR is involved, and an optimization method of a BSR processing flow is urgently needed at present to solve the problem.
Disclosure of Invention
In view of this, the main objective of the present invention is to provide a method and a system for optimizing BSR processing flow, which improve BSR reporting under the condition that uplink resources are not enough to report a long BSR.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a method for optimizing a buffer status report processing flow, the method comprising: when the triggered Buffer Status Report (BSR) includes a regular BSR and/or a periodic BSR; when more than 1 Logic Channel Group (LCG) has transmittable data and uplink resources are not enough to report a long BSR, selecting a format of a truncated BSR or a new BSR Media Access Control (MAC) control element to report the BSR; or, choose not to report the BSR and wait for the next report.
Wherein, the uplink resource is not enough for reporting the long BSR specifically: the size of the uplink resource is smaller than the sum of the size of the long BSR and the MAC subheader thereof.
Wherein, the truncated BSR specifically includes: a field indicating an LCG identity and a field indicating a corresponding buffer size; wherein,
the field indicating the LCG identifier specifically indicates that: the mark of LCG to which the logic channel with highest priority can transmit data belongs; the field indicating the size of the corresponding buffer specifically indicates: a buffer size of the LCG.
Wherein, the new BSR MAC control element specifically includes: two fields indicating an LCG identity and two fields indicating a corresponding buffer size; wherein,
a field indicating LCG identity specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; another field indicating LCG identity specifically indicates: except the logical channel included in the LCG in the former field indicating the LCG identification, the identification of the LCG to which the logical channel with the highest priority level capable of transmitting data belongs; two fields indicating the size of the corresponding buffer are specifically indicated: two fields indicating LCG identification the buffer size of the LCG.
Wherein the method further comprises: triggering a Scheduling Request (SR) when the triggered BSR includes a regular BSR; or does not trigger SR.
Wherein, under the condition of reporting the BSR, the method further comprises: when the triggered BSR comprises a conventional BSR, the triggered BSR is cancelled after the BSR is reported; or, the triggered BSR is not cancelled after the BSR is reported.
Wherein, under the condition of reporting the BSR, the method further comprises: when the triggered BSR has a periodic BSR, the triggered BSR is cancelled after the BSR is reported; or, the triggered BSR is not cancelled after the BSR is reported.
Wherein, under the condition of reporting the BSR, the method further comprises: a BSR retransmission timer is started or restarted.
Wherein, under the condition of reporting the BSR, the method further comprises: starting or restarting a BSR period timer; alternatively, the BSR cycle timer is not started or restarted.
A system for optimizing a buffer status report processing flow, the system comprising: selecting a reporting unit or selecting a unit not to be reported; wherein,
selecting a reporting unit, configured to select a regular BSR and/or a periodic BSR when the triggered BSR includes the regular BSR; when more than 1 LCG has transmittable data and uplink resources are not enough to report a long BSR, selecting a format of a truncated BSR or a new BSR MAC control element to report the BSR;
selecting a non-reporting unit for when the triggered BSR includes a regular BSR and/or a periodic BSR; if more than 1 LCG has transmittable data and uplink resources are not enough to report the long BSR, selecting not to report the BSR and waiting for the next report.
The selective reporting unit is further configured to select to report the BSR when the size of the uplink resource is smaller than the sum of the long BSR and the MAC subheader thereof.
Wherein the selection reporting unit further comprises a format encapsulation module, wherein,
under the condition of adopting the format encapsulation of the truncated BSR, the format encapsulation module is configured to, in the encapsulated truncated BSR, specifically include: a field indicating an LCG identity and a field indicating a corresponding buffer size; wherein, the field indicating the LCG identifier specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; the field indicating the size of the corresponding buffer specifically indicates: a buffer size of the LCG; or,
under the condition of adopting the format encapsulation of the new BSR MAC control element, the format encapsulation module is configured to, in the encapsulated new BSR MAC control element, specifically include: two fields indicating an LCG identity and two fields indicating a corresponding buffer size; wherein, a field indicating the LCG identifier specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; another field indicating LCG identity specifically indicates: except the logical channel included in the LCG in the former field indicating the LCG identification, the identification of the LCG to which the logical channel with the highest priority level capable of transmitting data belongs; two fields indicating the size of the corresponding buffer are specifically indicated: two fields indicating LCG identification the buffer size of the LCG.
And the select no-report unit is further configured to select no-report BSR for waiting for next report when the size of the uplink resource is smaller than the sum of the long BSR and the MAC subheader thereof.
The triggered BSR comprises a conventional BSR and/or a periodic BSR; when more than 1 LCG has transmittable data and uplink resources are not enough to report a long BSR, selecting a format of a truncated BSR or a new BSR MAC control element to report the BSR; or, choose not to report the BSR and wait for the next report.
The adoption of the invention perfects the BSR processing flow when the uplink resource is not enough to report the long BSR for the conventional BSR and/or the periodic BSR, namely: for a conventional BSR and/or a periodic BSR, when uplink resources are not enough to report a long BSR, selecting a format of a truncated BSR or a new BSR MAC control element to report the BSR; or, choose not to report the BSR and wait for the next report.
Drawings
FIG. 1 is a diagram of a conventional E-UTRAN radio interface protocol uplink layer 2 architecture;
FIG. 2 is a diagram of a conventional short BSR, or truncated BSR, format;
FIG. 3 is a diagram of a conventional long BSR format;
FIG. 4 is a diagram of a new BSR format according to the present invention;
FIG. 5 is a flow chart illustrating BSR processing in the prior art;
FIG. 6 is a schematic diagram of an embodiment of a first aspect of the present invention;
fig. 7 is a schematic diagram of a second embodiment of the present invention.
Detailed Description
The basic idea of the invention is: the processing flow of the BSR when the uplink resource is not enough to report the long BSR for the conventional BSR and/or the periodic BSR is perfected, namely: for a conventional BSR and/or a periodic BSR, when uplink resources are not enough to report a long BSR, selecting a format of a truncated BSR or a new BSR MAC control element to report the BSR; or, choose not to report the BSR and wait for the next report.
The following describes the embodiments in further detail with reference to the accompanying drawings.
A method for optimizing a buffer status report processing flow, the method comprising: when the triggered BSR includes a regular BSR and/or a periodic BSR; when there are more than 1 LCG with transmittable data and uplink resources are not enough to report a long BSR, one implementation is: and selecting a format of a truncated BSR or a new BSR MAC control element to report the BSR. The other realization mode is as follows: and selecting not to report the BSR and waiting for the next report. These two different implementations are set forth separately below.
In the first case: and selecting a reporting implementation mode.
For a conventional BSR or a periodic BSR, the uplink resource is insufficient for reporting the long BSR, which is specifically: the size of the uplink resource is smaller than the sum of the size of the long BSR and the MAC subheader thereof.
When generating a BSR MAC control element in a truncated BSR format to implement reporting, the truncated BSR specifically includes: a field indicating an LCG identification and a field indicating a corresponding buffer size.
Wherein, the field indicating the LCG identifier specifically indicates: there is an identification of the LCG to which the highest priority logical channel over which data may be transmitted belongs.
The field indicating the size of the corresponding buffer specifically indicates: the buffer size of the LCG in the field indicating the LCG identification.
When a new BSR MAC control element is generated in a format of the BSR MAC control element to implement reporting, the new BSR MAC control element specifically includes: two fields indicating LCG identification and two fields indicating the corresponding buffer size.
Wherein, a field indicating the LCG identifier specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; another field indicating LCG identity specifically indicates: in addition to the logical channel included in the LCG in the previous field indicating the LCG identification, there is an identification of the LCG to which the highest priority logical channel that can transmit data belongs.
Two fields indicating the size of the corresponding buffer are specifically indicated: two fields indicating LCG identification the buffer size of the LCG.
In the second case: and selecting an implementation mode without reporting.
For a conventional BSR or a periodic BSR, the uplink resource is insufficient for reporting the long BSR, which is specifically: the size of the uplink resource is smaller than the sum of the size of the long BSR and the MAC subheader thereof.
And aiming at the periodic BSR, the size of the uplink resource is smaller than the sum of the long BSR and the MAC subhead thereof, and the BSR is selected not to be reported to wait for the next report.
For the conventional BSR, the size of the uplink resource is smaller than the sum of the long BSR and the MAC subheader thereof, and the BSR is selected not to be reported to wait for the next reporting.
In both cases, whether reporting the BSR or not, the method further includes: triggering an SR when the triggered BSR comprises a regular BSR; or does not trigger SR.
In case of reporting BSR, the method further comprises: when the triggered BSR comprises a conventional BSR, the triggered BSR is cancelled after the BSR is reported; or, the triggered BSR is not cancelled after the BSR is reported. Wherein cancelling or not cancelling a "triggered BSR" involved in a triggered BSR, comprises: a regular BSR; the method optionally comprises the following steps: padding BSR, and/or periodic BSR.
In case of reporting BSR, the method further comprises: when the triggered BSR has a periodic BSR, the triggered BSR is cancelled after the BSR is reported; or, the triggered BSR is not cancelled after the BSR is reported. Wherein cancelling or not cancelling a "triggered BSR" involved in a triggered BSR, comprises: a periodic BSR; the method optionally comprises the following steps: padding BSR, and/or regular BSR.
In case of reporting BSR, the method further comprises: a BSR retransmission timer is started or restarted.
In case of reporting BSR, the method further comprises: starting or restarting a BSR period timer; alternatively, the BSR cycle timer is not started or restarted.
In summary, the present invention mainly includes the following contents:
the invention mainly aims at the condition that uplink resources are not enough to report a long BSR, perfects the processing flow of BSR reporting, and relates to a conventional BSR and a periodic BSR. Furthermore, the present invention also involves a handling scheme for the problem of whether an SR needs to be triggered or not, for a conventional BSR.
The specific contents are as follows:
the first scheme is as follows: and selecting the condition of reporting the BSR.
For the regular BSR and the periodic BSR, if more than 1 LCG has transmittable data and the size of the uplink resource is smaller than the sum of the size of the long BSR and the size of the MAC subheader thereof, reporting the BSR.
Further, the reported BSR format is a truncated BSR, or a new BSR MAC control element format is introduced. The new BSR MAC control element format includes fields indicating two LCG identities and corresponding buffer sizes, as shown in fig. 4. Adopting the truncated BSR, wherein the field indicating the LCG identification refers to the identification of the LCG to which the logical channel with the highest priority level capable of transmitting data belongs; the field indicating the corresponding buffer size refers to the buffer size of the LCG described above. Adopting the new BSR MAC control element format, wherein the field indicating the LCG identifier refers to the identifier of the LCG to which the logical channel with the highest priority for transmitting data belongs, and the identifier of the LCG to which the logical channel with the highest priority for transmitting data belongs except the logical channels included by the LCG; the field indicating the corresponding buffer size refers to the buffer sizes of the above two LCGs.
Here, the description is made with respect to the above "the field indicating the LCG identifier refers to an identifier of an LCG to which a logical channel having the highest priority for transmitting data belongs, and an identifier of an LCG to which a logical channel having the highest priority for transmitting data belongs, in addition to the logical channels included in the above LCG":
for example, logical channels 1, 2, 3, 4, where 1, 2 belong to LCG1, 3 belongs to LCG2, 4 belongs to LCG3, and the priority of the logical channels is 1 > 2 > 3 > 4. If all 4 logical channels have data to transmit, the new BSR format only reports the buffer sizes of LCG1 and LCG 2. Wherein, LCG1 is determined by logical channel 1; LCG2 is determined by logical channel 3. Although logical channel 2 has higher priority than logical channel 3, logical channel 2 belongs to LCG1 and has been reported.
Further, reporting the BSR, and starting or restarting a BSR retransmission timer.
Further, reporting the BSR, and starting or restarting a BSR period timer; or reporting the BSR, and not starting or restarting a BSR period timer.
Further, for a conventional BSR, if the BSR is reported, an SR is triggered; or reporting the BSR for the conventional BSR, and not triggering the SR.
Further, for a regular BSR, the triggered BSR is cancelled after the BSR is sent; or for a regular BSR, not cancelling the triggered BSR after transmitting the BSR.
Further, for a periodic BSR, canceling the triggered BSR after the BSR is sent; or for periodic BSR, not cancelling the triggered BSR after transmitting the BSR.
Scheme II: the case of not transmitting BSR is chosen.
For the periodic BSR, if more than 1 LCG has transmittable data and the size of the uplink resource is smaller than the sum of the size of the long BSR and the size of the MAC subheader thereof, the BSR is not reported and the next transmission is waited.
For the conventional BSR, if more than 1 LCG has transmittable data and the size of the uplink resource is smaller than the sum of the size of the long BSR and the size of the MAC subheader thereof, the BSR is not reported and the next transmission is waited.
The invention is illustrated below.
Since padding BSR does not have the problems described in the present invention, the following embodiments describe the case where the present invention is used for regular BSR or periodic BSR.
Assume that the UE has 4 logical channels: LC1, LC2, LC3, and LC4, which respectively belong to 4 logical channel groups: LCG1, LCG2, LCG3 and LCG4, wherein the priority levels are as follows: LC1 > LC2 > LC3 > LC 4. Assume that all 3 logical channels, except LC2, have upper layer data to transmit.
Embodiment of scheme one:
the processing flow of the UE per TTI is shown in fig. 6, and includes the following steps:
step 601: judging whether the current TTI has uplink resources for first transmission, if so, entering step 602; if not, go to step 603.
Step 602: generating a BSR MAC control element. Judging whether more than 1 LCG has transmittable data, if yes, entering step 6021; if not, go to step 6022;
it should be noted here that the format of padding BSR reporting adopts the existing procedure, and the reason is that: and when the uplink resources are not enough to report the long BSR, reporting the padding BSR for the truncated BSR by adopting a format of the BSR MAC control element. If padding BSR is reported in step 602, step 604 is entered according to the prior art. The following steps 6021-6024 are directed only to the regular BSR and the periodic BSR.
Step 6021: and judging whether the uplink resources are enough to report the long BSR, namely whether the size of the uplink resources is larger than or equal to the size of the long BSR and the MAC subheader thereof, if so, entering a step 6023, and if not, entering a step 6024.
Step 6022: and generating a BSR MAC control element by using the short BSR, and entering step 604.
Step 6023: and generating a BSR MAC control element by using the long BSR, and entering step 604.
Step 6024: generating BSRMAC control element using truncated BSR or newly introduced BSR MAC control element format, and proceeding to step 604.
It should be noted that, if uplink resources are not enough to report the newly introduced BSR MAC control element format, for example, only 16 bits are needed, at this time, the identity and the buffer size of the LCG1 can be reported only by using the truncated BSR. If the uplink resources are sufficient to report the newly introduced BSR MAC Control element format, for example, only 24 bits are available, the identifier and buffer size of the LCG1 may be reported by using a truncated BSR, and the remaining 16 bits may be used to report a Power overhead reporting (PHR) MAC Control element, or data from a Dedicated Control Channel (DCCH), or data from a Dedicated Traffic Channel (DTCH), etc.; the identities and buffer sizes of LCGs 1 and 2 may also be reported in a newly introduced BSR MAC control element format.
Step 603: and judging whether the triggered BSR has a regular BSR or not, and if so, triggering the SR.
Step 604: and starting or restarting a BSR retransmission timer, starting or restarting a BSR periodic timer, judging whether the triggered BSR has a conventional BSR or not, and triggering the SR if the triggered BSR has the conventional BSR.
Here, the processing of the BSR cycle timer in this step is to be explained.
In the prior art, the BSR cycle timer is processed by starting or restarting the BSR cycle timer, except for using a truncated BSR. Only padding BSRs are used in the prior art with truncated BSRs. However, in the present invention, the regular BSR and the periodic BSR may also adopt truncated BSR.
For padding BSR, the prior art is still adopted, that is, the BSR cycle timer is started or restarted when a long BSR or a short BSR is adopted, and the BSR cycle timer is not started or restarted when a truncated BSR is adopted.
For the regular BSR and the periodic BSR, a BSR period timer is started or restarted when a long BSR or a short BSR is adopted.
For the conventional BSR and periodic BSR, the same processing may be adopted when the truncated BSR or the newly introduced BSR MAC control element format is adopted, such as all starting or restarting the BSR periodic timer, or all not starting or restarting the BSR periodic timer; or different processes are adopted, such as one BSR starts or restarts the BSR period timer, and the other BSR does not start or restart the BSR period timer.
In addition, even if there is a regular BSR, the SR may not be triggered because the UE considers that the base station has the ability to reallocate the uplink grant for reporting the BSR or data according to the reported BSR.
For the scenario that the triggered BSR has a conventional BSR and a periodic BSR, if a BSR MAC control element is generated by adopting a truncated BSR or a newly introduced BSR MAC control element format, all the triggered BSRs are cancelled after the BSR is sent; alternatively, not all BSRs that have triggered are cancelled.
For the scenario with regular BSR and without periodic BSR, the same process can be adopted, that is: both scenarios cancel the triggered BSR, or neither scenario cancels the triggered BSR; different treatments may also be used, namely: one scenario cancels BSR, and the other scenario does not cancel BSR.
Example of scheme two:
the processing flow of the UE per TTI is shown in fig. 7, and includes the following steps:
step 701: judging whether the current TTI has enough uplink resources for first transmission, if so, entering step 702; if not, step 703 is entered.
It should be noted here that if the triggered BSR only has a padding BSR, there is no regular BSR or periodic BSR, and the uplink resource used for the first transmission is sufficient as follows: there are uplink resources. Otherwise, namely: the triggered BSR includes a regular BSR or a periodic BSR, and if there are more than 1 LCG data to be reported, the sufficient uplink resource for first transmission refers to: the size of the uplink resource is larger than or equal to the size of the long BSR and the MAC subheader thereof; otherwise, the sufficient uplink resource for the first transmission refers to: the size of the uplink resource is larger than or equal to the size of the short BSR and the MAC subheader thereof.
Step 702: generating a BSR MAC control element, starting or restarting a BSR retransmission timer, and starting or restarting a BSR periodic timer (not starting or restarting when truncating the BSR).
It should be noted here that, for the regular BSR, the periodic BSR, and the padding BSR, the BSR MAC control element is generated by using the prior art.
Step 703: and judging whether the triggered BSR has a regular BSR or not, and if so, triggering the SR.
A system for optimizing a buffer status report processing flow, the system comprising either: selecting a reporting unit, or selecting a non-reporting unit.
When the system comprises a selective reporting unit, the selective reporting unit is used for triggering the BSR to comprise a regular BSR and/or a periodic BSR; when more than 1 LCG has transmittable data and uplink resources are not enough to report the long BSR, a format of a truncated BSR or a new BSR MAC control element is selected to report the BSR.
When the system comprises a selection non-reporting unit, the selection non-reporting unit is used for selecting a regular BSR and/or a periodic BSR when the triggered BSR comprises the regular BSR; if more than 1 LCG has transmittable data and uplink resources are not enough to report the long BSR, selecting not to report the BSR and waiting for the next report.
Here, for the selective reporting unit, the selective reporting unit is further configured to select the reporting BSR when the size of the uplink resource is smaller than the sum of the long BSR and the size of the MAC subheader thereof.
The selective reporting unit further includes a format encapsulation module, where, in the case of adopting format encapsulation of the truncated BSR, the format encapsulation module is configured to, in the encapsulated truncated BSR, specifically include: a field indicating an LCG identification and a field indicating a corresponding buffer size. Wherein, the field indicating the LCG identifier specifically indicates: there is an identification of the LCG to which the highest priority logical channel over which data may be transmitted belongs. The field indicating the size of the corresponding buffer specifically indicates: buffer size of LCG.
Under the condition of adopting the format encapsulation of the new BSR MAC control element, the format encapsulation module is used for encapsulating the new BSR MAC control element, and specifically comprises the following steps: two fields indicating LCG identification and two fields indicating the corresponding buffer size. Wherein, a field indicating the LCG identifier specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; another field indicating LCG identity specifically indicates: in addition to the logical channel included in the LCG in the previous field indicating the LCG identification, there is an identification of the LCG to which the highest priority logical channel that can transmit data belongs. Two fields indicating the size of the corresponding buffer are specifically indicated: two fields indicating LCG identification the buffer size of the LCG.
For the selected non-reporting unit, the selected non-reporting unit is further configured to select the non-reporting BSR to wait for the next reporting when the size of the uplink resource is smaller than the sum of the long BSR and the MAC subheader thereof.
Here, the Scheduling process referred to above is denoted by Scheduling; priority handling is denoted by priority handling; the Regular buffer status report is expressed as Regular BSR; the Padding buffer status report is expressed as Padding BSR; the Periodic buffer status report is expressed in a Periodic BSR; the BSR retransmission Timer is expressed by retxBSR-Timer; the BSR period Timer is expressed as periodicBSR-Timer; the MAC Control Element is expressed by MAC Control Element, which is called MAC CE for short; PDU refers to protocol data unit; short BSR is denoted short BSR; the truncated BSR is denoted as truncated BSR; the long BSR is denoted as long BSR.
In fig. 1, the packet data convergence protocol is denoted as PDCP; radio link control is denoted RLC; medium access control is expressed in MAC; header compression is denoted ROHC; security is expressed as Security; segment/automatic repeat request is denoted by segm. Scheduling/prioritization is represented by Scheduling/priority handling; multiplexing is represented by Multiplexing; hybrid automatic repeat request is denoted HARQ; radio Bearers are denoted as Radio beacons; logical Channels are denoted by Logical Channels; transport Channels are denoted Transport Channels.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (13)
1. A method for optimizing a buffer status report processing flow, the method comprising: when the triggered Buffer Status Report (BSR) includes a regular BSR and/or a periodic BSR; when more than 1 Logic Channel Group (LCG) has transmittable data and uplink resources are not enough to report a long BSR, selecting a format of a truncated BSR or a new BSR Media Access Control (MAC) control element to report the BSR; or, choose not to report the BSR and wait for the next report.
2. The method of claim 1, wherein the uplink resource is insufficient for reporting the long BSR specifically: the size of the uplink resource is smaller than the sum of the size of the long BSR and the MAC subheader thereof.
3. The method according to claim 2, wherein the truncated BSR specifically includes: a field indicating an LCG identity and a field indicating a corresponding buffer size; wherein,
the field indicating the LCG identifier specifically indicates that: the mark of LCG to which the logic channel with highest priority can transmit data belongs; the field indicating the size of the corresponding buffer specifically indicates: a buffer size of the LCG.
4. The method according to claim 2, wherein the new BSR MAC control element specifically includes: two fields indicating an LCG identity and two fields indicating a corresponding buffer size; wherein,
a field indicating LCG identity specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; another field indicating LCG identity specifically indicates: except the logical channel included in the LCG in the former field indicating the LCG identification, the identification of the LCG to which the logical channel with the highest priority level capable of transmitting data belongs; two fields indicating the size of the corresponding buffer are specifically indicated: two fields indicating LCG identification the buffer size of the LCG.
5. The method according to any one of claims 1 to 4, characterized in that the method further comprises: triggering a Scheduling Request (SR) when the triggered BSR includes a regular BSR; or does not trigger SR.
6. The method according to any of claims 1 to 4, wherein in case of reporting BSR, the method further comprises: when the triggered BSR comprises a conventional BSR, the triggered BSR is cancelled after the BSR is reported; or, the triggered BSR is not cancelled after the BSR is reported.
7. The method according to any of claims 1 to 4, wherein in case of reporting BSR, the method further comprises: when the triggered BSR has a periodic BSR, the triggered BSR is cancelled after the BSR is reported; or, the triggered BSR is not cancelled after the BSR is reported.
8. The method according to any of claims 1 to 4, wherein in case of reporting BSR, the method further comprises: a BSR retransmission timer is started or restarted.
9. The method according to any of claims 1 to 4, wherein in case of reporting BSR, the method further comprises: starting or restarting a BSR period timer; alternatively, the BSR cycle timer is not started or restarted.
10. A system for optimizing a buffer status report process flow, the system comprising: selecting a reporting unit or selecting a unit not to be reported; wherein,
selecting a reporting unit, configured to select a regular BSR and/or a periodic BSR when the triggered BSR includes the regular BSR; when more than 1 LCG has transmittable data and uplink resources are not enough to report a long BSR, selecting a format of a truncated BSR or a new BSR MAC control element to report the BSR;
selecting a non-reporting unit for when the triggered BSR includes a regular BSR and/or a periodic BSR; if more than 1 LCG has transmittable data and uplink resources are not enough to report the long BSR, selecting not to report the BSR and waiting for the next report.
11. The system of claim 10, wherein the means for selecting to report is further configured to select to report the BSR when a size of an uplink resource is smaller than a sum of a long BSR and a size of a MAC subheader thereof.
12. The system according to claim 11, wherein the selective reporting unit further comprises a format encapsulation module, wherein,
under the condition of adopting the format encapsulation of the truncated BSR, the format encapsulation module is configured to, in the encapsulated truncated BSR, specifically include: a field indicating an LCG identity and a field indicating a corresponding buffer size; wherein, the field indicating the LCG identifier specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; the field indicating the size of the corresponding buffer specifically indicates: a buffer size of the LCG; or,
under the condition of adopting the format encapsulation of the new BSR MAC control element, the format encapsulation module is configured to, in the encapsulated new BSR MAC control element, specifically include: two fields indicating an LCG identity and two fields indicating a corresponding buffer size; wherein, a field indicating the LCG identifier specifically indicates: the mark of LCG to which the logic channel with highest priority can transmit data belongs; another field indicating LCG identity specifically indicates: except the logical channel included in the LCG in the former field indicating the LCG identification, the identification of the LCG to which the logical channel with the highest priority level capable of transmitting data belongs; two fields indicating the size of the corresponding buffer are specifically indicated: two fields indicating LCG identification the buffer size of the LCG.
13. The system of claim 10, wherein the unit for selecting not to report is further configured to select not to report the BSR for the next reporting when the size of the uplink resource is smaller than the sum of the size of the long BSR and the size of the MAC subheader thereof.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910236838XA CN102056332A (en) | 2009-11-02 | 2009-11-02 | Method and system for optimizing processing flow of buffer zone status report |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910236838XA CN102056332A (en) | 2009-11-02 | 2009-11-02 | Method and system for optimizing processing flow of buffer zone status report |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102056332A true CN102056332A (en) | 2011-05-11 |
Family
ID=43960103
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910236838XA Pending CN102056332A (en) | 2009-11-02 | 2009-11-02 | Method and system for optimizing processing flow of buffer zone status report |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102056332A (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102905382A (en) * | 2012-10-16 | 2013-01-30 | 中兴通讯股份有限公司 | Method for sending data in LTE (Long Term Evolution) system by using uplink authorization and terminal equipment |
| CN102932939A (en) * | 2012-10-12 | 2013-02-13 | 中兴通讯股份有限公司 | Method and system for optimizing uplink scheduling of LTE (Long Term Evolution) system, base station and terminal |
| CN102984659A (en) * | 2011-09-02 | 2013-03-20 | 普天信息技术研究院有限公司 | A reporting method for a buffer status report in a TD-LTE system |
| CN103249090A (en) * | 2012-02-14 | 2013-08-14 | 华为技术有限公司 | Method and device for buffer state report |
| WO2015139373A1 (en) * | 2014-03-21 | 2015-09-24 | 中兴通讯股份有限公司 | Method and device for reporting and receiving buffer status |
| WO2017166197A1 (en) * | 2016-03-31 | 2017-10-05 | 华为技术有限公司 | Buffer processing method, and user equipment |
| WO2018171710A1 (en) * | 2017-03-24 | 2018-09-27 | 华为技术有限公司 | Method and device for processing information |
| WO2018227566A1 (en) * | 2017-06-16 | 2018-12-20 | Oppo广东移动通信有限公司 | Information transmission method and device |
| CN109151878A (en) * | 2017-06-15 | 2019-01-04 | 株式会社Kt | For configuring the method and device thereof of the buffer status reporting about next generation mobile communication |
| WO2019015513A1 (en) * | 2017-07-21 | 2019-01-24 | 夏普株式会社 | Wireless communication method and device |
| WO2019056277A1 (en) * | 2017-09-21 | 2019-03-28 | Oppo广东移动通信有限公司 | Information transmission method and device |
| WO2019134130A1 (en) * | 2018-01-05 | 2019-07-11 | 富士通株式会社 | Method for generating buffer status report, method for determining buffer status report, and device and communication system thereof |
| CN110121204A (en) * | 2013-03-29 | 2019-08-13 | 华为技术有限公司 | A communication method, mobility management entity device, communication device, storage medium and communication system |
| WO2019191883A1 (en) * | 2018-04-02 | 2019-10-10 | Oppo广东移动通信有限公司 | Method for triggering scheduling request, and terminal device |
| CN110800328A (en) * | 2017-09-21 | 2020-02-14 | Oppo广东移动通信有限公司 | A cache state reporting method, terminal and computer storage medium |
| CN112292900A (en) * | 2018-06-21 | 2021-01-29 | 上海诺基亚贝尔股份有限公司 | Optimized BSR for limited traffic mixing |
| WO2021043104A1 (en) * | 2019-09-06 | 2021-03-11 | 深圳市中兴微电子技术有限公司 | Method and apparatus for reporting buffer status report, and user terminal and computer-readable storage medium |
| CN112566280A (en) * | 2014-08-08 | 2021-03-26 | 创新技术实验室株式会社 | Method and apparatus for transmitting buffer status report in wireless communication system supporting inter-terminal communication |
| US11452000B2 (en) | 2018-01-16 | 2022-09-20 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for reporting data volume of data duplication, user equipment, and network device |
-
2009
- 2009-11-02 CN CN200910236838XA patent/CN102056332A/en active Pending
Cited By (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102984659A (en) * | 2011-09-02 | 2013-03-20 | 普天信息技术研究院有限公司 | A reporting method for a buffer status report in a TD-LTE system |
| CN102984659B (en) * | 2011-09-02 | 2016-03-16 | 普天信息技术有限公司 | The report method of the buffer status report in a kind of TD-LTE system |
| US9532264B2 (en) | 2012-02-14 | 2016-12-27 | Huawei Technologies Co., Ltd. | Buffer state reporting method and apparatus |
| WO2013120435A1 (en) * | 2012-02-14 | 2013-08-22 | 华为技术有限公司 | Method and device for buffer state report |
| CN103249090A (en) * | 2012-02-14 | 2013-08-14 | 华为技术有限公司 | Method and device for buffer state report |
| CN102932939A (en) * | 2012-10-12 | 2013-02-13 | 中兴通讯股份有限公司 | Method and system for optimizing uplink scheduling of LTE (Long Term Evolution) system, base station and terminal |
| CN102905382B (en) * | 2012-10-16 | 2015-09-16 | 中兴通讯股份有限公司 | Method and terminal equipment for sending data using uplink authorization in LTE system |
| CN102905382A (en) * | 2012-10-16 | 2013-01-30 | 中兴通讯股份有限公司 | Method for sending data in LTE (Long Term Evolution) system by using uplink authorization and terminal equipment |
| CN110121204B (en) * | 2013-03-29 | 2024-01-05 | 华为技术有限公司 | A communication method, mobile management entity device, communication device, storage medium and communication system |
| CN110121204A (en) * | 2013-03-29 | 2019-08-13 | 华为技术有限公司 | A communication method, mobility management entity device, communication device, storage medium and communication system |
| WO2015139373A1 (en) * | 2014-03-21 | 2015-09-24 | 中兴通讯股份有限公司 | Method and device for reporting and receiving buffer status |
| US10091687B2 (en) | 2014-03-21 | 2018-10-02 | Zte Corporation | Method and device for reporting and receiving buffer status |
| CN112566280A (en) * | 2014-08-08 | 2021-03-26 | 创新技术实验室株式会社 | Method and apparatus for transmitting buffer status report in wireless communication system supporting inter-terminal communication |
| WO2017166197A1 (en) * | 2016-03-31 | 2017-10-05 | 华为技术有限公司 | Buffer processing method, and user equipment |
| WO2018171710A1 (en) * | 2017-03-24 | 2018-09-27 | 华为技术有限公司 | Method and device for processing information |
| US11153934B2 (en) | 2017-03-24 | 2021-10-19 | Huawei Technologies Co., Ltd. | Information processing method and device |
| CN109151878A (en) * | 2017-06-15 | 2019-01-04 | 株式会社Kt | For configuring the method and device thereof of the buffer status reporting about next generation mobile communication |
| CN109565897A (en) * | 2017-06-16 | 2019-04-02 | Oppo广东移动通信有限公司 | method and device for transmitting information |
| WO2018227566A1 (en) * | 2017-06-16 | 2018-12-20 | Oppo广东移动通信有限公司 | Information transmission method and device |
| WO2019015513A1 (en) * | 2017-07-21 | 2019-01-24 | 夏普株式会社 | Wireless communication method and device |
| US11234156B2 (en) | 2017-09-21 | 2022-01-25 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Information transmission method and device |
| CN110800369A (en) * | 2017-09-21 | 2020-02-14 | Oppo广东移动通信有限公司 | Method and device for transmitting information |
| CN111314957A (en) * | 2017-09-21 | 2020-06-19 | Oppo广东移动通信有限公司 | Method and device for transmitting information |
| WO2019056277A1 (en) * | 2017-09-21 | 2019-03-28 | Oppo广东移动通信有限公司 | Information transmission method and device |
| CN110800328A (en) * | 2017-09-21 | 2020-02-14 | Oppo广东移动通信有限公司 | A cache state reporting method, terminal and computer storage medium |
| CN111314957B (en) * | 2017-09-21 | 2022-04-12 | Oppo广东移动通信有限公司 | Method and device for transmitting information |
| CN110800369B (en) * | 2017-09-21 | 2024-06-21 | Oppo广东移动通信有限公司 | Method and device for transmitting information |
| WO2019134130A1 (en) * | 2018-01-05 | 2019-07-11 | 富士通株式会社 | Method for generating buffer status report, method for determining buffer status report, and device and communication system thereof |
| US11452000B2 (en) | 2018-01-16 | 2022-09-20 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for reporting data volume of data duplication, user equipment, and network device |
| WO2019191883A1 (en) * | 2018-04-02 | 2019-10-10 | Oppo广东移动通信有限公司 | Method for triggering scheduling request, and terminal device |
| CN112292900A (en) * | 2018-06-21 | 2021-01-29 | 上海诺基亚贝尔股份有限公司 | Optimized BSR for limited traffic mixing |
| WO2021043104A1 (en) * | 2019-09-06 | 2021-03-11 | 深圳市中兴微电子技术有限公司 | Method and apparatus for reporting buffer status report, and user terminal and computer-readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102056332A (en) | Method and system for optimizing processing flow of buffer zone status report | |
| JP6952710B2 (en) | Improved mechanism for QoS implementation in vehicle communications | |
| US10616943B2 (en) | Terminal for supporting device to device communication and method for operating same | |
| US10778379B2 (en) | Uplink signal transmission method and user equipment | |
| US10187193B2 (en) | Method and apparatus for transceiving data using plurality of carriers in mobile communication system | |
| TWI422266B (en) | Method and apparatus for improving uplink transmission in a wireless communication system | |
| US10555208B2 (en) | Method for performing a buffer status reporting in a wireless communication system and device therefor | |
| CN102763481B (en) | For in wireless communication system based on competition up link transmit method and apparatus | |
| US11844079B2 (en) | Method and apparatus for transmitting data unit in wireless communication system | |
| CN118826965A (en) | Method, system and apparatus for transmitting data with different reliabilities | |
| US8498260B2 (en) | Methods of packet element transmission in wireless communications system | |
| EP3982580A1 (en) | Method and apparatus for transmitting and receiving data using plurality of carriers in mobile communication system | |
| JP2019522430A (en) | Improved support for quality of service for V2X transmissions | |
| KR20100027925A (en) | A method of requesting a radio resource allocation in a wireless communication system | |
| US20100254480A1 (en) | Method of transmitting a data block in a wireless communication system | |
| US11877301B2 (en) | Method and apparatus for transmitting buffer size information in wireless communication system | |
| US11497061B2 (en) | Method and apparatus for performing random access procedure for unlicensed band n wireless communication system | |
| US10863553B2 (en) | V2X operation method performed by terminal in wireless communication system and terminal using same | |
| CN102119511A (en) | Method for communicating in a network, a secondary station and a system therefor | |
| CN101677460B (en) | Configuration method, terminal and base station of radio resource scheduling | |
| US11026117B2 (en) | Method for transmitting signals by user equipment in wireless communication system and apparatus therefor | |
| HK1197341A1 (en) | Method and apparatus for resource release in a wireless communication network | |
| EP2873282B1 (en) | Technique for uplink data processing | |
| Duan et al. | An Improved Approach of Sending BSR and SR Based on MAC Layer in LTE System |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110511 |