WO2011150709A1 - 一种缓冲区状态报告处理的方法和装置 - Google Patents

一种缓冲区状态报告处理的方法和装置 Download PDF

Info

Publication number
WO2011150709A1
WO2011150709A1 PCT/CN2011/071936 CN2011071936W WO2011150709A1 WO 2011150709 A1 WO2011150709 A1 WO 2011150709A1 CN 2011071936 W CN2011071936 W CN 2011071936W WO 2011150709 A1 WO2011150709 A1 WO 2011150709A1
Authority
WO
WIPO (PCT)
Prior art keywords
bsr
timer
mac pdu
triggered
cancelled
Prior art date
Application number
PCT/CN2011/071936
Other languages
English (en)
French (fr)
Inventor
陈思
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP11789088A priority Critical patent/EP2525600A1/en
Priority to US13/578,873 priority patent/US20120314672A1/en
Publication of WO2011150709A1 publication Critical patent/WO2011150709A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/002Transmission of channel access control information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/188Time-out mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0833Random access procedures, e.g. with 4-step access

Definitions

  • the present invention relates to resource allocation techniques in mobile communications, and more particularly to a method and apparatus for buffer status report processing. Background technique
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • LTE Third Generation Mobile Long Term Evolution
  • uplink data is shared by physical uplink.
  • the channel (PUSCH, Physical Uplink Shared Channel M is dedicated; the uplink radio resource is allocated by the evolved NodeB (eNB) to each user terminal (UE, User Equipment).
  • eNB evolved NodeB
  • the access technology used by E-UTRAN is Orthogonal Frequency Division Multiplexing (OFDM) technology, the radio resource management of the E-UTRAN system has the characteristics of large bandwidth and multiple time processes compared with the second generation mobile communication system, and its radio resources are time-based. And the two-dimensional frequency and the number of users that can be carried are greatly increased.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the LTE system has specially formulated for uplink transmission resource allocation of users.
  • Control message The control message dedicated to the resource allocation of the PUSCH is sent by the eNB to the UE, and the resource allocation control message is also referred to as an uplink grant (UL Grant, UpLink Grant), and the UL Grant is in the physical downlink control channel ( Sent on PDCCH, Physical Downlink Control Channel).
  • the UE In the initial stage of transmitting data, the UE usually needs to utilize the resources of the competition. For example: After the UE has accessed the network, it can enter the dormant state (dormant) during the gap of data to save the battery cost of the UE and the resource overhead of the network.
  • the network may not reserve resources for the UE or only When there is uplink data to be transmitted, the UE sends a signaling to the network through random access or through a reserved number of resources, for example, on a dedicated signaling channel, to obtain subsequent uplink transmission resources.
  • the method for obtaining the subsequent uplink transmission resource by using the random access or the reserved resource is as shown in FIG. 1.
  • the eNB can actually transmit data upstream (MSG3 in step 103) after the eNB answers (MSG2 in step 102). Due to the previous two steps (steps 101, 102), the UE has a delay from when the uplink data arrives to when it actually transmits.
  • a method for transmitting a subsequent uplink transmission resource by using a Scheduling Request (SR) on a physical uplink control channel (PUCCH, Physical Uplink Control Channel) has a delay of 11.5 ms.
  • SR Scheduling Request
  • the existing scheme uses a pre-scheduled resource, as shown in FIG. 2, that is, the network side always allocates a dedicated uplink resource to the UE regardless of whether the UE has data (step 201), when the UE needs When the data is transmitted in the uplink, the dedicated uplink resource can be used to transmit data (step 202). That is to say, the UE can transmit data uplink in MSG1, and its transmission delay can be reduced to 5.5 ms in the LTE system.
  • the shortcoming of this scheme is: Regardless of whether the UE has uplink data transmission, the eNB needs to reserve a part of dedicated resources to the UE, which will cause resource waste.
  • the dedicated uplink resource may be changed to a contention-based uplink resource (step 301), that is, a contention based uplink transmission, also called CB (Contention based transmission) transmission, and uplink resources are in several Sharing within the UE, when the UE needs to use, the data is transmitted through the competition (step 302); as shown in FIG. 3, when the number of shared UEs is small, the method can achieve better performance.
  • a contention-based uplink resource that is, a contention based uplink transmission, also called CB (Contention based transmission) transmission
  • CB contention based transmission
  • uplink resources are in several Sharing within the UE, when the UE needs to use, the data is transmitted through the competition (step 302); as shown in FIG. 3, when the number of shared UEs is small, the method can achieve better performance.
  • the LTE system requires the UE to report the status of the amount of data stored in its own buffer.
  • the report reports the status of the buffer (BSR, Buffer Status).
  • the form of Report is reported to the eNB.
  • the logical channel (LCH, Logical Channel) of the UE is divided into four logical channel groups (LCG, Logical Channel Group) according to the priority level.
  • the BSR reports the group number of each LCG and all LCHs in the group. Information about the amount of data that can be transferred.
  • the BSR only reports the information of the transmittable data amount of the LCH belonging to the LCG, and does not report the information of the transmittable data amount of the LCH that does not belong to the LCG.
  • the subsequent LCH refers to the LCH belonging to the LCG
  • the uplink data refers to the uplink data that can be transmitted.
  • the BSR is encapsulated into a MAC Control Element (CE) in the Media Access Control Protocol Data Unit (MAC), which is called a BSR MAC CE.
  • CE Media Access Control Protocol Data Unit
  • the MAC PDU is transmitted on the PUSCH.
  • the UE reports the state of the data stored in its own buffer by transmitting a MAC PDU carrying the BSR MAC CE.
  • the BSR is an important reference information for the eNB to perform reasonable radio resource scheduling for the UE, the LTE system specifies various types and transmission rules of the BSR.
  • the BSR is classified into a regular buffer status report (Regular BSR), a periodic buffer status report (RTB), and a padding status report (Padding BSR) depending on the event that triggers the BSR.
  • Regular BSR regular buffer status report
  • RTB periodic buffer status report
  • Padding BSR padding status report
  • the trigger conditions of Regular BSR include:
  • the UE buffer has uplink data, and new uplink data arrives, and the LCH to which the new uplink data belongs has a higher priority than the LCH to which the existing uplink data belongs;
  • the UE buffer has uplink data, and the BSR retransmission timer (RETX-BSR_TIMER) times out; or
  • the UE buffer has no uplink data, and new uplink data arrives.
  • the trigger condition of the Periodic BSR is: The BSR cycle timer (PERIODIC BSR TIMER ) times out.
  • the trigger condition of the Padding BSR is: In the case of an uplink resource, the padding part of the foot is sufficient To accommodate the BSR MAC CE, that is, the number of bits filled in the uplink resource is greater than or equal to the sum of the sizes of the BSR MAC CE and its MAC subheader.
  • the Padding BSR can make the eNB obtain the LCG data change in the UE buffer in a timely manner.
  • the reported BSR is called a Long BSR (Long BSR); otherwise, the reported BSR It is called Short BSR (Short BSR).
  • TTI Transmitted Time Interval
  • the upper 4 BSRs are called long BSRs; if there are multiple LCGs in the TTIs that send BSRs, they can be transmitted.
  • the reported BSR is called a truncated BSR. If there are no multiple LCGs that can transmit data in the TTI of the BSR, the reported BSR is called a short BSR.
  • a MAC PDU can include at most one BSR MAC CE, that is, even if multiple events trigger the BSR at the same time, only one BSR MAC CE will be sent.
  • the UE's BSR-related timer processing includes the following:
  • the UE starts or restarts the periodic BSR timer ( periodicBSR-Timer);
  • the UE restarts the retransmission BSR timer.
  • a BSR-related MAC PDU refers to: a MAC PDU carrying a BSR MAC CE, or a MAC PDU not carrying a BSR MAC CE.
  • the application scenario of the MAC PDU that does not carry the BSR MAC CE is: In the case of a BSR that has been triggered but has not been cancelled, if the uplink resource can accommodate all the transmit data (Pending data), the BSR MAC CE can no longer be accommodated. And its corresponding subhead
  • the upstream authorization can accommodate all the data that can be transmitted (pending data) but can no longer accommodate the BSR MAC CE and its corresponding subheader (subheader);
  • the sent MAC PDU carries the BSR MAC CE.
  • the BSR sends the following actions: Restart cycle BSR timer, restart Retransmit BSR timer, cancel all triggered BSRs.
  • the BSR fails to be sent, the BSR will not be triggered by the UE within a certain period of time, such as:
  • the UE does not generate a BSR MAC CE to report how much data is to be transmitted. If the eNB is unable to know the amount of data to be transmitted by the UE, the eNB may allocate an inappropriate uplink resource to the UE or not allocate the subsequent uplink resource to the UE. As a result, the uplink data of the UE may be accumulated and cannot be sent in time, affecting the uplink of the UE. Transmission performance.
  • the reliability of the transmission can be ensured by a hybrid automatic repeat request (HARQ, Hybrid Auto Repeat Request).
  • HARQ Hybrid Auto Repeat Request
  • the probability of the BSR sending failure is low. That is, the BSR is sent by the general uplink resource, and the UE is less affected by the BSR transmission failure.
  • the UE occupies the CSR uplink resource to send the BSR in addition to being affected by the quality of the channel, there are conflicts caused by multiple UEs occupying the same CB resource; in addition, considering the complexity of implementation
  • the CB transmission may not support HARQ, so the probability of failure of the CB transmission is higher than the probability of failure of the general uplink resource transmission. That is to say, the uplink resource that occupies the CB sends a BSR, and the UE is greatly affected by the failure of the BSR transmission.
  • the main object of the present invention is to provide a method and an apparatus for processing a buffer status report, so as to solve the problem that the UE is affected by the failure of the BSR transmission when the BSR is sent by the uplink resource that occupies the CB in the prior art. problem.
  • the present invention provides a method for buffer status report processing, the method comprising: performing at least one of the following processing manners in the case of using a contention-based uplink resource transmission buffer status report (BSR) :
  • BSR contention-based uplink resource transmission buffer status report
  • MAC PDU media access control layer protocol data unit
  • the BSR-related MAC PDU is occupied by the uplink resource
  • the BSR is cancelled according to the type of the triggered BSR.
  • the triggered BSR is cancelled. Determining whether to cancel the triggered BSR according to the type of the triggered BSR, specifically: if the triggered BSR includes a regular buffer status report (Regular BSR), the regular BSR is not cancelled when the MAC PDU is formed;
  • Regular BSR regular buffer status report
  • the triggered BSR includes a periodic buffer status report (RTBSR)
  • RTBSR periodic buffer status report
  • the Padding BSR is cancelled when the MAC PDU is formed.
  • the method further includes: restarting the retransmission BSR timer and/or the periodic BSR timer upon receiving an indication that the BSR related MAC PDU is successfully sent.
  • the triggered BSR is all BSRs that are triggered but not cancelled before the MAC PDU is formed.
  • the present invention also provides an apparatus for buffer status report processing, the apparatus comprising: a BSR processing module, configured to perform at least one of the following processing manners when a BSR is transmitted using a contention-based uplink resource :
  • the BSR is not cancelled when the MAC PDU related to the BSR is occupied by the uplink resource.
  • the triggered BSR is cancelled.
  • the BSR-related MAC PDU is occupied by the uplink resource
  • the BSR is cancelled according to the type of the triggered BSR.
  • the triggered BSR is cancelled.
  • the BSR processing module is further used, In the case that the triggered BSR includes a Regular BSR, the Regular BSR is not cancelled when the MAC PDU is formed;
  • the triggered BSR includes a Periodic BSR
  • the Periodic BSR is cancelled or not cancelled when the MAC PDU is formed
  • the Padding BSR is included in the triggered BSR, the Padding BSR is cancelled when the MAC PDU is formed.
  • the BSR processing module is further configured to restart the retransmission BSR timer and/or the periodic BSR timer when receiving an indication that the BSR related MAC PDU is successfully sent.
  • the triggered BSR is all BSRs that are triggered but not cancelled before the MAC PDU is formed.
  • the device is applied to a User Terminal (UE) or a Relay Node (RN).
  • UE User Terminal
  • RN Relay Node
  • the method and the device for processing the buffer status report provided by the present invention can reduce the impact on the UE when the BSR fails to transmit the BSR by using the BSR-related timer processing and the BSR cancellation processing, thereby enabling the base station to Timely and accurately understand the data volume status of the UE buffer, and allocate appropriate subsequent uplink resources to the UE to achieve the purpose of optimizing uplink scheduling.
  • FIG. 1 is a flowchart of obtaining a subsequent uplink transmission resource by means of a competition in the prior art
  • FIG. 2 is a flowchart of uplink transmission by means of pre-configuring resources in the prior art
  • FIG. 3 is a schematic diagram of the prior art
  • FIG. 4 is a flowchart of a method for buffer status report processing according to Embodiment 1 of the present invention
  • FIG. 5 is a flowchart of a method for buffer status report processing according to Embodiment 2 of the present invention
  • FIG. 6 is a flowchart of a method for buffer status report processing according to Embodiment 3 of the present invention.
  • the present invention provides a BSR processing method, which is a method for processing a BSR related timer in the case of transmitting a BSR based on the contention-based uplink resource. And cancel the operation of the BSR to improve.
  • the processing of the BSR related timer provided by the present invention includes at least one of the following manners:
  • the uplink grant when receiving the uplink grant indicating the uplink resource based on the contention, does not restart the retransmission BSR timer (retxBSR-Timer); the uplink grant is not limited to the uplink grant used to send the BSR;
  • the retxBSR-Timer and/or the periodic BSR timer are not restarted.
  • the retxBSR-Timer is not restarted.
  • the retxBSR-Timer is restarted. Timer and/or periodBSR-Timer, where the MAC
  • the PDU is sent by occupying the uplink resource.
  • the operation of canceling the BSR provided by the present invention includes at least one of the following ways:
  • the BSR is not cancelled when the BSR-related MAC PDU is formed by the uplink resource, and the triggered BSR is cancelled when the BSR-related MAC PDU is successfully sent.
  • the BSR type determines whether to cancel the triggered BSR. When the BSR-related MAC PDU is sent successfully, the triggered BSR is cancelled.
  • the method of determining whether to cancel the triggered BSR according to the type of the triggered BSR is as follows: If the triggered BSR includes a Regular BSR, the MAC PDU is not cancelled when the MAC PDU is formed.
  • the periodic BSR may be cancelled or the Periodic BSR may not be cancelled.
  • the triggered BSR includes a Padding BSR
  • the Padding BSR is cancelled when the MAC PDU is formed.
  • the triggered BSR refers to a BSR that is triggered but not cancelled before the MAC PDU is formed and the MAC PDU is formed.
  • any of the above-described processing of the BSR-related timer and the operation of canceling the BSR may be used in combination. The method of the above BSR processing will be further elaborated below in conjunction with specific embodiments.
  • the first embodiment of the present invention describes: there is at least one BSR that has been triggered but not cancelled.
  • the network element 1 is allocated to the network element 2 for the network element 2 to send new data based on the contention-based uplink resource.
  • the processing method of the BSR-related timer of the present invention is combined with the method of canceling the BSR in the prior art. As shown in FIG. 4, the following steps are specifically included:
  • Step 401 The network element 2 receives the contention-based uplink grant (CB grant) sent by the network element 1, and instructs the network element 2 to send new data on the uplink shared channel (UL-SCH, Uplink Shared Channel). Do not restart retxBSR-Timer.
  • CB grant contention-based uplink grant
  • UL-SCH Uplink Shared Channel
  • the method for the network element 2 to receive the CB grant sent by the network element 1 is: the network element 2 obtains the CB grant on the downlink control channel according to the CB-RNTI (Contention Based Radio Network Temporary Identity) indication.
  • the CB grant carries information about the uplink resource based on the contention, such as resource block information, modulation and coding mode information, and the like.
  • Step 402 The network element 2 sets up a MAC PDU. At this time, the periodicBSR-Timer is not restarted, and the retxBSR-Timer is not restarted, and all triggered BSRs are cancelled.
  • the network element 2 constructs a MAC PDU according to the uplink resource in step 401. If the uplink resource is sufficient to accommodate all the transmit data, but not enough to accommodate the BSR MAC CE and its corresponding subheader, the MAC PDU may not carry the BSR MAC CE and only carry all transportable data. data. At this time, since all the transmittable data has been sent through the MAC PDU, the network element 1 can know the amount of data that can be transmitted by the network element 2 even if the BSR MAC CE is not sent, that is, the network element 2 has no further The amount of data transferred.
  • the MAC PDU carries the BSR MAC CE if the uplink resources are insufficient to accommodate all of the transmittable data, or are sufficient to accommodate all of the transmittable data enough to accommodate the BSR MAC CE and its corresponding subheaders.
  • the network element 1 can know the amount of data that can be transmitted by the network element 2 according to the information in the BSR MAC CE.
  • NE 2 does not restart BSR-related timers (such as periodicBSR-Timer and retxBSR-Timer). If the CB grant sends a BSR, the success probability of sending a BSR is lower than that of a dedicated uplink resource. If the CB grant fails to send a BSR, the timing is not restarted.
  • the timer can be timed out earlier so that the Periodic BSR (periodic BSR-Timer timeout) or the Regular BSR (the retxBSR-Timer timeout condition) can be retriggered as early as possible.
  • Step 403 the network element 2 sends a MAC PDIL
  • Step 404 The network element 2 receives an indication that the MAC PDU from the network element 1 is successfully sent. At this time, the network element 2 restarts the periodicBSR-Timer, and restarts the retxBSR-Timer.
  • This embodiment describes an example in which the method A1 and the method A2 are combined in the processing of the BSR-related timer in the case where the BSR-related timer includes both the periodicBSR-Timer and the retxBSR-Timer.
  • the processing of the BSR related timers includes the following combinations:
  • Method A1 is combined with method A2:
  • the timers related to the LA and the BSR include only the periodicBSR-Timer, excluding the retxBSR-Timer.
  • the remaining steps are different from the embodiment in the following steps:
  • the periodicBSR-Timer is not restarted in step 402, but the retxBSR-Timer is restarted; the periodicBSR is restarted in step 404.
  • -Timer optionally restart retxBSR-Timer;
  • the lb and BSR related timers only include retxBSR-Timer, excluding periodicBSR-Timer:
  • the remaining steps are different from this embodiment in that: retxBSR-Timer is not restarted in step 402, but periodicBSR-Timer is restarted; retxBSR is restarted in step 404 - Timer, optionally restart periodicBSR-Timer.
  • the Periodic BSR or Regular BSR can be re-triggered as early as possible. Because the process is the same whether it triggers a BSR or multiple BSRs.
  • the periodic BSR-Timer and retxBSR-Timer are not restarted when the MAC PDU is set up, so that the timer expires earlier, so that the Periodic BSR (periodic BSR-Timer timeout) and the Regular BSR (regxBSR-) can be retriggered as early as possible.
  • the case of Timer timeout The case of Timer timeout).
  • the BSR-related timer includes only the periodicBSR-Timer, and does not include the retxBSR-Timer.
  • the remaining steps are different from the embodiment in the following steps: Step 402 does not restart the periodicBSR-Timer, and restarts the retxBSR-Timer; Restart periodicBSR-Timer, optionally restart retxBSR-Timer;
  • the Periodic BSR can be retriggered as early as possible. Because the process is the same whether it triggers a BSR or multiple BSRs.
  • the BSR-related timer includes only the retxBSR-Timer, and does not include the periodicBSR-Timer.
  • the remaining steps are different from the embodiment in the following steps: Step 402: Restarting the retxBSR-Timer and restarting the periodicBSR-Timer; Restart retxBSR- Timer, optionally restart periodicBSR-Timer;
  • the Regular BSR can be retriggered as early as possible. Because the process is the same whether it triggers a BSR or multiple BSRs.
  • Step 401, Step 403 is the same as the embodiment shown in FIG. 4; optional retention step 404;
  • step 402 the timer has been restarted in step 402 and the interval between step 402 and step 404 is short, as in the case of frequency division duplex (FDD) in the LTE system, it is within 4 ms, so step 404 may not be needed. Restarting the timer has little effect.
  • FDD frequency division duplex
  • Embodiment 2 of the present invention describes that there is at least one that has been triggered but not cancelled.
  • the processing method of the BSR related timer in the prior art is used and the cancellation according to the present invention.
  • the BSR approach combines scenarios. As shown in FIG. 5, the following steps are specifically included:
  • Step 501 The network element 2 receives the contention-based uplink grant (CB grant) sent by the network element 1, and instructs the network element 2 to send new data on the UL-SCH. At this time, the network element 2 restarts the retxBSR-Timer.
  • CB grant contention-based uplink grant
  • the method for the network element 2 to receive the uplink authorization sent by the network element 1 is the same as that described in step 401 of the first embodiment, and is not described here.
  • Step 502 The network element 2 sets up a MAC PDU. At this time, the network element 2 restarts the periodicBSR-Timer, and restarts the retxBSR-Timer, and does not cancel all the triggered BSRs.
  • the method for forming a MAC PDU by the network element 2 is the same as that described in step 401 of the first embodiment, and details are not described herein again.
  • the process of canceling the BSR may also be: in step 502, the BSRs of different types are treated differently, and if they are Regular BSRs, they are not canceled; if they are Padding BSRs, they are canceled; if they are Periodic BSRs, they are optionally canceled. Because the Padding BSR is a supplementary BSR, even if there is no Padding BSR, the influence on the network element 1 scheduling network element 2 is not large, so this You can cancel the Padding BSR.
  • Step 503 the network element 2 sends a MAC PDIL
  • Step 504 The network element 2 receives the indication that the MAC PDU from the network element 1 is successfully sent, and the network element 2 cancels all the triggered BSRs.
  • All triggered BSRs refer to: BSRs that were triggered in step 502 and before step 502, but not cancelled. Because step 502 and step 504 are separated by a certain time, during this time, the newly triggered BSR is not excluded, and the newly triggered BSRs are not cancelled because the MAC PDUs are successfully sent because they are indicated in the buffer. The amount of data to be transmitted is different from the amount of data indicated in the MAC PDU.
  • Embodiment 3 of the present invention describes that there is at least one that has been triggered but not cancelled.
  • the processing method of the BSR-related timer according to the present invention is compared with the method for canceling the BSR. Combined scenes. As shown in FIG. 6, the following steps are specifically included:
  • Step 601 The network element 2 receives the contention-based uplink grant (CB grant) sent by the network element 1, and instructs the network element 2 to send new data in the UL-SCH. At this time, the network element 2 does not restart the retxBSR-Timer.
  • CB grant contention-based uplink grant
  • Step 602 The network element 2 sets up a MAC PDU. At this time, the network element 2 does not restart the periodicBSR-Timer, does not restart the retxBSR-Timer, and does not cancel all triggered BSRs.
  • the process of canceling the BSR may be: in step 602, different types of BSRs are treated differently; if it is a Regular BSR, it is not canceled; if it is a Padding BSR, it is canceled; if it is a Periodic BSR, it is optionally canceled. Because the Padding BSR is a supplementary BSR, even if there is no Padding BSR, the influence on the network element 1 scheduling network element 2 is not large, so the Padding BSR can be cancelled here.
  • Step 603 The network element 2 sends a MAC PDU.
  • Step 604 The network element 2 receives the indication that the MAC PDU from the network element 1 is successfully sent, and the network element 2 restarts the periodicBSR-Timer, restarts the retxBSR-Timer, and cancels all triggered BSRs. All triggered BSRs refer to: BSRs that were triggered in step 602, and before step 602, but not cancelled. Because step 602 and step 604 are separated by a certain time, during this time, the newly triggered BSRs are not excluded, and these newly triggered BSRs are not cancelled because the MAC PDUs are successfully sent because they are indicated in the buffer. The amount of data to be transmitted is different from the amount of data indicated in the MAC PDU.
  • This embodiment describes an example in which the method A1 and the method A2 are combined in the processing of the BSR-related timer in the case where the BSR-related timer includes both the periodicBSR-Timer and the retxBSR-Timer.
  • the processing of BSR related timers includes the following combinations:
  • Method A1 is combined with method A2:
  • the timers related to the LA and BSR include only the periodicBSR-Timer, excluding the retxBSR-Timer.
  • the difference from the embodiment shown in FIG. 6 is that the periodicBSR-Timer is not restarted in step 602, but the retxBSR-Timer is restarted; Restart the periodicBSR-Timer, optionally restart retxBSR-Timer;
  • the lb and BSR related timers only include the retxBSR-Timer, excluding the periodicBSR-Timer:
  • the difference from the embodiment shown in FIG. 6 is: the retxBSR-Timer is not restarted in step 602, but the periodicBSR-Timer is restarted; Restart retxBSR-Timer, optionally restart periodicBSR-Timer.
  • the BSR related timer includes both periodicBSR-Timer and retxBSR-Timer: the remaining steps (steps 602-604) are the same as the embodiment shown in FIG. 6;
  • the periodic BSR-Timer and retxBSR-Timer are not restarted when the MAC PDU is set up, so that the timer expires earlier, so that the timer can be retriggered as early as possible.
  • Periodic BSR the case of periodicBSR-Timer timeout
  • Regular BSR the case of retxBSR-Timer timeout
  • the BSR-related timer includes only the periodicBSR-Timer, and does not include the retxBSR-Timer.
  • the remaining steps are different from the embodiment in the following steps: Step 602 does not restart the periodicBSR-Timer, and restarts the retxBSR-Timer; Restart periodicBSR-Timer, optionally restart retxBSR-Timer;
  • the Periodic BSR can be retriggered as early as possible. Because the process is the same whether it triggers a BSR or multiple BSRs.
  • the BSR-related timer includes only the retxBSR-Timer, and does not include the periodicBSR-Timer.
  • the remaining steps are different from the embodiment in the following steps: Step 602 does not restart the retxBSR-Timer, and restarts the periodicBSR-Timer; Restart retxBSR- Timer, optionally restart periodicBSR-Timer;
  • the Regular BSR can be retriggered as early as possible. Because the process is the same whether it triggers a BSR or multiple BSRs.
  • step 601 is used only, and the method A2 is not used, that is, the periodicBSR-Timer is restarted in step 602, and the retxBSR-Timer is restarted; step 601, step 603 is the same as the embodiment shown in FIG. 6; optional retention step 604;
  • the retxBSR-Timer is not restarted upon receiving the contention-based uplink grant, so that the timer expires earlier, so that the Regular BSR can be re-triggered as early as possible.
  • the timer since the timer has been restarted in step 602, and the time interval between step 602 and step 604 is shorter, as in the case of FDD in the LTE system, it is less than 4 ms, so step 604 may not need to restart the timer, and the impact is not significant.
  • the network element 1, the network element 2, and the subframe for transmitting the MAC PDU related to the BSR have the following combinations:
  • network element 1 is an eNB
  • network element 2 is a UE
  • the subframe is each subframe.
  • the subframe is an uplink subframe
  • the network element 1 is a relay node (RN, Relay Node)
  • the network element 2 is a UE
  • the subframe is Uu. Uplink subframe;
  • the network element 1 is a donor base station (DeNB, Donor eNB), the network element 2 is an RN, and the subframe is an uplink subframe of Un.
  • the present invention further provides a device for buffer status report processing, which is applied to a UE or an RN, and the device includes: a BSR processing module, When the uplink resource sends the BSR, at least one of the following processing modes is performed:
  • the BSR that cancels the trigger is determined according to the type of the triggered BSR.
  • the triggered BSR is cancelled.
  • the BSR processing module is further configured to: when the triggered BSR includes the Regular BSR, the regular BSR is not cancelled when the MAC PDU is formed; and when the triggered BSR includes the Periodic BSR, the MAC PDU is cancelled when the MAC PDU is formed. Or cancel the Periodic BSR; if the Padding BSR is included in the triggered BSR, the Padding BSR is cancelled when the MAC PDU is formed.
  • the BSR processing module is further configured to restart the retransmission BSR timer and/or the periodic BSR timer when receiving the indication that the BSR related MAC PDU is successfully sent.
  • the present invention does not limit the indication of successful or failed BSR transmission.
  • the network element 1 transmits a downlink assignment (DL assignment) or an uplink grant (UL grant) to the network element 2 that successfully transmits at a fixed offset, where the CB RNTI and the C-RNTI are carried (such as C.
  • the indication of the -RNTI MAC control element, or the network element 2 receives the downlink assignment or the uplink grant within a period of time after transmitting the BSR, and considers that the transmission is successful.
  • the BSR-related MAC PDU in the present invention is consistent with the description of the prior art, that is, the MAC PDU refers to a MAC PDU carrying a BSR MAC CE or a MAC PDU carrying no BSR MAC CE.
  • the application scenario of the MAC PDU that does not carry the BSR MAC CE is: In the case that there is a BSR that is triggered but has not been canceled, if the uplink resource can accommodate all transmittable data (pending data) but can no longer accommodate the BSR MAC CE The MAC PDU of its corresponding sub-data, but does not carry the BSR MAC CE.

Landscapes

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

Abstract

本发明公开一种缓冲区状态报告(BSR)处理的方法和装置,在采用基于竞争的上行资源发送BSR时,执行以下方式的至少一种:A、收到指示基于竞争的上行资源的上行授权时,不重启重传BSR定时器;B、有该上行资源时,不重启重传BSR定时器和/或周期BSR定时器;C、占用该上行资源组建BSR相关的MACPDU时,不取消触发的BSR;收到该MACPDU发送成功的指示时,取消触发的BSR;D、占用该上行资源组建BSR相关的MACPDU时,根据BSR类型确定是否取消触发的BSR;收到该MACPDU发送成功的指示时,取消触发的BSR。通过本发明,降低了占用基于竞争的上行传输资源发送BSR失败对UE的影响。

Description

一种緩冲区状态报告处理的方法和装置 技术领域
本发明涉及移动通信中的资源分配技术, 尤其涉及一种緩冲区状态报 告处理的方法和装置。 背景技术
在第三代移动通信长期演进(LTE, Long Term Evolution ) 系统的演进 型通用陆地无线接入网 (E-UTRAN , Evolved Universal Terrestrial Radio Access Network )中,上行链路的数据通过物理上行链路共享信道( PUSCH, Physical Uplink Shared Channel M专输;由演进型基站( eNB, evolved NodeB ) 分配上行链路无线资源给每个用户终端(UE, User Equipment )。 E-UTRAN 釆用的接入技术是正交频分复用 (OFDM, Orthogonal Frequency Division Multiplexing )技术, E-UTRAN系统的无线资源管理和第二代移动通信系统 相比, 具有大带宽、 多时间进程的特点, 其无线资源是以时间和频率两维 出现的, 能够承载的用户数量大大增加。
为了能够按照每个 UE的需求分配资源和提供服务,以在上行传输中实 现较好的复用性能, 同时也为了充分灵活高效的利用系统带宽, LTE 系统 为用户的上行传输资源分配制定了专门的控制消息。其中,专用于对 PUSCH 进行资源分配的控制消息是由 eNB发送给 UE的, 该资源分配控制消息又 称为上行链路授权(UL Grant, UpLink Grant ), UL Grant在物理下行链路 控制信道 ( PDCCH, Physical Downlink Control Channel )上发送。
UE在传输数据的初始阶段, 通常需要利用竟争的资源。 例如: 当 UE 在已经接入网络后, 在数据的间隙过程中可以进入休眠状态(dormant ), 以 节省 UE的电池开销和网络的资源开销, 网络可以不给 UE预留资源或者只 预留很少的资源; 当有上行数据需要发送时, UE通过随机接入或者通过预 留的少数资源, 例如在专用的信令信道上发送信令通知网络, 以获取后续 的上行传输资源。
上述通过随机接入或者通过预留资源获取后续的上行传输资源的方 法, 如图 1所示, 在发送过程中, 当 UE需要上行发送数据时, 首先发送一 个请求(步骤 101中的 MSG1 )给 eNB,在 eNB应答(步骤 102中的 MSG2 ) 后, UE才能真正上行发送数据(步骤 103中的 MSG3 )。 由于有了前面两 个步骤(步骤 101、 102 ), 导致 UE从上行数据到达时到真正发送时有一个 时延。 在 LTE 系统中, 釆用在物理上行链路控制信道(PUCCH, Physical Uplink Control Channel )上发送调度请求( SR, Scheduling Request )获取后 续的上行传输资源的方法, 其时延一般有 11.5ms。
为了减少上述时延, 现有方案釆用预调度资源的方式, 如图 2 所示, 即网络侧不论 UE是否有数据, 总是分配一个专用的上行资源给 UE (步骤 201 ), 当 UE需要上行发送数据时, 即可以利用该专用的上行资源发送数据 (步骤 202 )。 也就是说, UE在 MSG1就可以上行发送数据, 其发送时延 在 LTE系统中可以减少到 5.5ms。 然而, 该方案的缺点就是: 不论 UE是否 有上行数据传输, eNB都需要预留一部分专用资源给 UE, 会造成资源的浪 费。
为了避免上述的资源浪费, 可以将上述专用的上行资源改为基于竟争 的上行资源(步骤 301 ),即基于竟争的上行传输,也称 CB( Contention based transmission )传输, 上行资源在几个 UE内共享, 当 UE需要使用时, 通过 竟争发送数据(步骤 302 ); 如图 3所示, 当共享的 UE数量较少时, 釆用 该方法可以取得较好的性能。
为了保证给每个 UE合理的分配无线资源, LTE系统要求 UE报告自身 緩冲区内存储的数据量状态,该报告以緩冲区状态报告(BSR, Buffer Status Report )的形式上报给 eNB。在 LTE系统中, UE的逻辑信道(LCH, Logical Channel )按照优先级的高低,被分成 4个逻辑信道组( LCG, Logical Channel Group ), BSR报告的就是各个 LCG的组序号和组内所有 LCH的可传输数 据量的信息。 由此可见, BSR只上报属于 LCG的 LCH的可传输数据量的 信息, 不上报不属于 LCG的 LCH的可传输数据量的信息。 为了描述简单, 后续的 LCH指的都是属于 LCG的 LCH, 上行数据指的都是可传输的上行 数据。
BSR封装为媒体接入控制层协议数据单元(MAC PDU, Media Access Control Protocol Data Unit ) 中的一个 MAC控制元( CE, Control Element ), 称之为 BSR MAC CE。 MAC PDU是在 PUSCH上进行发送的, UE通过发 送携带 BSR MAC CE的 MAC PDU来报告自身緩冲区内存储的数据量状 态。
由于 BSR是 eNB对 UE进行合理的无线资源调度的重要参考信息, 因 此 LTE系统规定了多种 BSR的类型和发送规则。 根据触发 BSR的事件的 不同, BSR被分为常规緩冲区状态报告 (Regular BSR )、 周期緩冲区状态 报告 ( Periodic BSR )和填充緩冲区状态报告 ( Padding BSR )。
其中, Regular BSR的触发条件包括:
A、 UE緩冲区有上行数据, 并且有新的上行数据到达, 该新的上行数 据所属的 LCH比已有的上行数据所属的 LCH的优先级高; 或者
B、 UE緩冲区有上行数据,并且 BSR重传定时器( RETX—BSR— TIMER ) 超时; 或者
C、 UE緩冲区没有上行数据, 并且有新的上行数据到达。
Periodic BSR的触发条件为: BSR周期定时器( PERIODIC BSR TIMER ) 超时。
Padding BSR的触发条件为: 有上行资源的情况下, 其中的填充部分足 以容纳 BSR MAC CE,即上行资源中填充的比特数量大于或等于 BSR MAC CE及其 MAC子头 (subheader ) 的大小之和。
当上行链路没有发送 Regular BSR和 Periodic BSR时, Padding BSR可 以更及时的让 eNB获得 UE緩冲区中 LCG数据变化的情况。
对于 Regular BSR和 Periodic BSR,如果发送 BSR的传输时间间隔( TTI, Transform Time Interval ) 内有多个 LCG有可传输的数据, 那么上报的 BSR 称为长 BSR ( Long BSR ); 否则, 上报的 BSR称为短 BSR ( Short BSR )。
对于 Padding BSR, 如果填充比特大于或等于长 BSR及其对应的子头 ( subheader ) 的大小之和, 那么上 4艮的 BSR称为长 BSR; 如果发送 BSR 的 TTI 内有多个 LCG有可传输的数据, 那么上报的 BSR称为截短 BSR ( Truncated BSR ),如果发送 BSR的 TTI内不存在多个 LCG有可传输的数 据, 那么上报的 BSR称为短 BSR。
在至少有一个已经触发但是没有取消的 BSR的情况下, 如果当前这个 TTI存在可用于发送新数据 ( new transmission )的上行资源, 那么 UE生成 BSR MAC CE。 一个 MAC PDU中至多包括一个 BSR MAC CE, 也就是说, 即使同时有多个事件触发了 BSR, 也只会发送一个 BSR MAC CE。
UE对 BSR相关的定时器处理包括如下:
1、 如果生成的 BSR MAC CE上报的 BSR不是 Truncated BSR, 那么 UE启动或者重启周期 BSR定时器 ( periodicBSR-Timer );
2、 有用于发送新数据的上行授权时, 启动或者重启重传 BSR定时器 ( retxBSR-Timer );
3、有用于发送新数据的上行授权的指示时, UE重启重传 BSR定时器。 组建 BSR相关的 MAC PDU时, UE取消所有触发的 BSR。 所述 BSR 相关的 MAC PDU指的是: 携带 BSR MAC CE的 MAC PDU, 或者不携带 BSR MAC CE的 MAC PDU。 其中, 不携带 BSR MAC CE的 MAC PDU的应用场景是: 在有触发了 但是还没有取消的 BSR的情况下, 如果上行资源可以容纳所有可传输的数 据 (pending data ) 但是无法再容纳 BSR MAC CE 及其相应的子头
MAC PDU, 但是不携带 BSR MAC CE。
也就是说以下两种情况下, UE取消所有触发的 BSR:
1、 上行授权可以容纳所有可传输的数据 ( pending data )但是无法再容 纳 BSR MAC CE及其对应的子头 ( subheader );
2、 发送的 MAC PDU携带 BSR MAC CE。
综上所述, BSR发送时还包括以下行为: 重启周期 BSR定时器、 重启 重传 BSR定时器、 取消所有触发的 BSR。
如果 BSR发送失败, 则将导致 UE在一定时间内没有触发的 BSR, 比 如:
1、 由于周期 BSR定时器重启, 因此一段时间内不会触发新的 Periodic
BSR;
2、 由于重传 BSR定时器重启, 因此一段时间内不会触发新的 Regular BSR;
3、 已经触发的 BSR被取消。
由此可见, 在 BSR发送失败的情况下, 即使 eNB为 UE分配了发送新 数据的上行资源, UE也不会生成 BSR MAC CE上报自身有多少数据量待 传输。 eNB在无法获知 UE有多少数据量待传输的情况下, 可能为 UE分配 了不合适的上行资源甚至没有为 UE分配后续的上行资源,导致 UE的上行 数据堆积而无法及时发送, 影响 UE的上行传输性能。
在 UE占用一般的上行资源发送 BSR的情况下, 可以通过混合自动重 传请求( HARQ , Hybrid Auto Repeat Request )保证其传输的可靠性, 因此 BSR发送失败的概率较低; 也就是说, 占用一般的上行资源发送 BSR, UE 受到 BSR发送失败的影响较小。
而在 UE占用 CB的上行资源发送 BSR的情况下, 除了受到信道质量 好坏的影响之外,还存在由于多个 UE抢占相同的 CB资源而导致的冲突问 题; 此外, 考虑到实现的复杂性, CB传输可能不支持 HARQ , 因此 CB传 输的失败概率比一般上行资源传输的失败概率要高。也就是说, 占用 CB的 上行资源发送 BSR, UE受到 BSR发送失败的影响较大。 发明内容
有鉴于此, 本发明的主要目的在于提供一种緩冲区状态报告处理的方 法和装置, 以解决现有技术中 UE在占用 CB的上行资源发送 BSR时, 受 BSR发送失败的影响较大的问题。
为达到上述目的, 本发明的技术方案是这样实现的:
本发明提供了一种緩冲区状态报告处理的方法, 该方法包括: 在釆用基于竟争的上行资源发送緩冲区状态报告(BSR )的情况下,执 行以下处理方式中的至少一种:
A、 在收到指示基于竟争的上行资源的上行授权时, 不重启重传 BSR 定时器;
B、在有所述上行资源时, 不重启重传 BSR定时器和 /或周期 BSR定时 器;
C、 在占用所述上行资源组建 BSR相关的媒体接入控制层协议数据单 元(MAC PDU ) 时, 不取消触发的 BSR; 在收到 BSR相关的 MAC PDU 发送成功的指示时, 取消触发的 BSR;
D、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 根据触发的 BSR的类型确定是否取消触发的 BSR;在收到 BSR相关的 MAC PDU发送 成功的指示时, 取消触发的 BSR。 所述根据触发的 BSR的类型确定是否取消触发的 BSR, 具体为: 如果触发的 BSR中包括常规緩冲区状态报告 ( Regular BSR ), 则组建 所述 MAC PDU时不取消所述 Regular BSR;
如果触发的 BSR中包括周期緩冲区状态报告 ( Periodic BSR ), 则组建 所述 MAC PDU时取消或者不取消所述 Periodic BSR;
如果触发的 BSR中包括填充緩冲区状态报告 ( Padding BSR ), 则组建 所述 MAC PDU时取消所述 Padding BSR。
该方法进一步包括:在收到 BSR相关的 MAC PDU发送成功的指示时, 重启所述重传 BSR定时器和 /或周期 BSR定时器。
所述触发的 BSR为组建所述 MAC PDU之前、 以及组建同时触发的 , 但未取消的所有 BSR。
本发明还提供了一种緩冲区状态报告处理的装置, 该装置包括: BSR 处理模块, 用于在釆用基于竟争的上行资源发送 BSR的情况下, 执行以下 处理方式中的至少一种:
A、 在收到指示基于竟争的上行资源的上行授权时, 不重启重传 BSR 定时器;
B、在有所述上行资源时, 不重启重传 BSR定时器和 /或周期 BSR定时 哭口.?
C、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 不取消触发 的 BSR; 在收到 BSR相关的 MAC PDU发送成功的指示时, 取消触发的 BSR;
D、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 根据触发的 BSR的类型确定是否取消触发的 BSR;在收到 BSR相关的 MAC PDU发送 成功的指示时, 取消触发的 BSR。
所述 BSR处理模块进一步用于, 在触发的 BSR中包括 Regular BSR的情况下, 组建所述 MAC PDU时 不取消所述 Regular BSR;
在触发的 BSR中包括 Periodic BSR的情况下, 组建所述 MAC PDU时 取消或者不取消所述 Periodic BSR;
在触发的 BSR中包括 Padding BSR的情况下 , 组建所述 MAC PDU时 取消所述 Padding BSR。
所述 BSR处理模块进一步用于,在收到 BSR相关的 MAC PDU发送成 功的指示时, 重启所述重传 BSR定时器和 /或周期 BSR定时器。
所述触发的 BSR为组建所述 MAC PDU之前、 以及组建同时触发的 , 但未取消的所有 BSR。
该装置应用于用户终端 (UE )或中继节点 (RN ) 中。
本发明所提供的一种緩冲区状态报告处理的方法和装置, 通过对 BSR 相关定时器的处理、 BSR取消的处理, 降低了占用 CB资源发送 BSR失败 时对 UE的影响, 从而使得基站能够及时、 准确地了解 UE緩冲区的数据量 状态, 并为 UE分配合适的后续上行资源, 达到优化上行调度的目的。 附图说明
图 1为现有技术中通过竟争的方式获取后续上行传输资源的流程图; 图 2为现有技术中通过预配置资源的方式进行上行传输的流程图; 图 3为现有技术中通过竟争资源的方式进行上行传输的流程图; 图 4为本发明实施例一的緩冲区状态报告处理的方法流程图; 图 5为本发明实施例二的緩冲区状态报告处理的方法流程图; 图 6为本发明实施例三的緩冲区状态报告处理的方法流程图。 具体实施方式
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。 为降低占用 CB资源发送 BSR失败时对 UE的影响, 本发明提供了一 种 BSR处理的方法, 旨在釆用基于竟争的上行资源发送 BSR的情况下,对 BSR相关定时器的处理方法, 以及取消 BSR的操作进行改进。
由此, 本发明提供的 BSR相关定时器的处理包括以下方式中的至少一 种:
Al、 在收到指示基于竟争的上行资源的上行授权时, 不重启重传 BSR 定时器(retxBSR-Timer ); 所述上行授权不限定是用于发送 BSR的上行授 权;
A2、 在有所述上行资源时, 不重启 retxBSR-Timer和 /或周期 BSR定时 器( periodicBSR-Timer ); 可选的, 在收到 BSR相关的 MAC PDU发送成功 的指示时,重启该 retxBSR-Timer和 /或 periodicBSR-Timer,其中,所述 MAC
PDU是占用所述上行资源发送的。
本发明提供的取消 BSR的操作包括以下方式中的至少一种:
B1、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 不取消触发 的 BSR;收到 BSR相关的 MAC PDU发送成功的指示时,取消触发的 BSR;
B2、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 根据触发的
BSR的类型确定是否取消触发的 BSR;收到 BSR相关的 MAC PDU发送成 功的指示时, 取消触发的 BSR。
其中, 根据触发的 BSR的类型确定是否取消触发的 BSR, 具体为: 如果触发的 BSR中包括 Regular BSR, 则组建 MAC PDU时不取消该
Regular BSR;
如果触发的 BSR中包括 Periodic BSR, 则组建 MAC PDU时可以取消 该 Periodic BSR, 也可以不取消该 Periodic BSR;
如果触发的 BSR中包括 Padding BSR, 则组建 MAC PDU时取消该 Padding BSR。 在取消 BSR的操作中,所述的触发的 BSR是指组建 MAC PDU之前以 及组建 MAC PDU时触发的但未取消的 BSR。 另外 , 上述 BSR相关定时器 的处理, 以及取消 BSR的操作中的任意一种方式都可以组合使用。 下面再 结合具体实施例对上述 BSR处理的方法进一步详细阐述。
本发明的实施例一描述的是: 存在至少一个已经触发但是没有取消的 BSR,有网元 1分配给网元 2的用于网元 2发送新数据的基于竟争的上行资 源的情况下, 釆用本发明所述 BSR相关定时器的处理方法与现有技术中取 消 BSR的方法相结合的场景。 如图 4所示, 具体包括以下步骤:
步骤 401 , 网元 2收到网元 1发送的基于竟争的上行授权( CB grant ), 指示网元 2在上行共享信道(UL-SCH, Uplink Shared Channel )发送新数 据, 此时网元 2不重启 retxBSR-Timer。
网元 2收到网元 1发送的 CB grant的方法是: 网元 2根据基于竟争无 线网络临时标识 (CB-RNTI, Contention Based Radio Network Temporary Identity )指示在下行控制信道获得该 CB grant。 该 CB grant中携带基于竟 争的上行资源的信息, 如资源块信息、 调制编码方式信息等。
步骤 402, 网元 2组建 MAC PDU, 此时不重启 periodicBSR-Timer, 且 不重启 retxBSR-Timer, 并取消所有触发的 BSR。
网元 2根据步骤 401中的上行资源组建 MAC PDU。如果上行资源足以 容纳所有可传输的数据 ( pending data ), 但是不足以再容纳 BSR MAC CE 及其对应的子头 ( subheader ) , 则 MAC PDU也可以不携带 BSR MAC CE , 只携带所有可传输的数据。 此时, 因为所有可传输的数据都已经通过 MAC PDU发送了, 所以即使不发送 BSR MAC CE, 网元 1也可以知道网元 2的 可传输的数据量, 即此时网元 2没有进一步可传输的数据量。 如果上行资 源不足以容纳所有可传输的数据, 或者既足以容纳所有可传输的数据又足 以容纳 BSR MAC CE及其对应的子头, 则 MAC PDU携带 BSR MAC CE。 此时, 网元 1根据 BSR MAC CE中的信息可以知道网元 2的可传输的数据 量。
在本步骤中, 网元 2不重启 BSR相关的定时器(如 periodicBSR-Timer 和 retxBSR-Timer )。 由于多个网元抢占 CB资源造成冲突的关系, 占用 CB grant发送 BSR的成功概率比占用专用的上行资源发送 BSR的成功概率要 低; 如果占用 CB grant发送 BSR失败了, 那么不重启所述定时器能够使所 述定时器超时得早一些, 从而能尽早重新触发 Periodic BSR ( periodicBSR-Timer超时的情况)或者 Regular BSR ( retxBSR-Timer超时 的情况)。
步骤 403 , 网元 2发送 MAC PDIL
步骤 404, 网元 2收到来自网元 1的 MAC PDU发送成功的指示, 此时 网元 2重启 periodicBSR-Timer, 并重启 retxBSR-Timer。
本实施例描述的是在 BSR相关的定时器既包括 periodicBSR-Timer, 又 包括 retxBSR-Timer的情况下,对 BSR相关的定时器的处理中方法 A1与方 法 A2相结合的示例。 除了本实施例中的示例以外, 对 BSR相关的定时器 的处理还包括以下的组合方式:
1、 方法 A1与方法 A2相结合:
la 、 BSR 相关的定时器只 包括 periodicBSR-Timer , 不包括 retxBSR-Timer: 其余步骤与本实施例不同之处在于: 步骤 402 中不重启 periodicBSR-Timer , 但是重启 retxBSR-Timer; 步骤 404 中 重启 periodicBSR-Timer, 可选地重启 retxBSR-Timer;
lb 、 BSR 相 关 的 定时器只 包括 retxBSR-Timer , 不 包括 periodicBSR-Timer: 其余步骤与本实施例不同之处在于: 步骤 402 中不重 启 retxBSR-Timer , 但是重启 periodicBSR-Timer; 步骤 404 中重启 retxBSR- Timer, 可选地重启 periodicBSR-Timer。 通过本组合方式,能够尽早地重新触发 Periodic BSR或者 Regular BSR。 因为不管是触发了一个 BSR还是多个 BSR, 发送的流程都是一样的。
2、只釆用方法 A2,不釆用方法 A1 : (即步骤 401中重启 retxBSR-Timer ) 2a、 所述 BSR 相关的定时器既包括 periodicBSR-Timer , 又包括 retxBSR-Timer: 其余步骤(步骤 402~404 )与图 4所示实施例相同;
通过本组合方式, 组建 MAC PDU 时不重启 periodicBSR-Timer 和 retxBSR-Timer , 使得所述定时器超时得早一些, 从而能尽早重新触发 Periodic BSR ( periodicBSR-Timer 超时的情况 ) 和 Regular BSR ( retxBSR-Timer超时的情况)。
2b、 所述 BSR 相关的定时器只包括 periodicBSR-Timer , 不包括 retxBSR-Timer, 其余步骤与本实施例的不同之处在于: 步骤 402中不重启 periodicBSR-Timer , 重 启 retxBSR-Timer ; 步 骤 404 中 重 启 periodicBSR-Timer , 可选的重启 retxBSR-Timer;
通过本组合方式, 能够尽早地重新触发 Periodic BSR。 因为不论是触发 了一个 BSR还是多个 BSR, 发送的流程都是一样的。
2c、 所述 BSR 相关的定时器只包括 retxBSR-Timer , 不包括 periodicBSR-Timer, 其余步骤与本实施例的不同之处在于: 步骤 402 中不 重启 retxBSR-Timer , 重启 periodicBSR-Timer; 步骤 404 中重启 retxBSR- Timer, 可选的重启 periodicBSR-Timer;
通过本组合方式, 能够尽早地重新触发 Regular BSR。 因为不论是触发 了一个 BSR还是多个 BSR, 发送的流程都是一样的。
3、 只釆用方法 A1 , 不釆用方法 A2 , 即: 步骤 402 中重启 periodicBSR-Timer, 重启 retxBSR-Timer; 步骤 401、 步骤 403同图 4所示 的实施例; 可选的保留步骤 404;
通过本组合方式, 在收到基于竟争的上行授权的情况下不重启 retxBSR-Timer , 使得所述定时器超时得早一些, 从而能尽早重新触发 Regular BSR。 另外, 由于步骤 402中已经重启了定时器, 而步骤 402和步 骤 404相隔的时间很短,如 LTE系统中频分双工( FDD , Frequency Division Duplex )情况下为 4ms以内, 因此步骤 404可以不需要重启定时器, 影响 不大。
本发明的实施例二描述的是: 存在至少一个已经触发但是没有取消的
BSR,有网元 1分配给网元 2的用于网元 2发送新数据的基于竟争的上行资 源的情况下, 釆用现有技术中 BSR相关定时器的处理方法与本发明所述取 消 BSR的方法相结合的场景。 如图 5所示, 具体包括以下步骤:
步骤 501 , 网元 2收到网元 1发送的基于竟争的上行授权(CB grant ), 指示网元 2在 UL-SCH发送新数据, 此时网元 2重启 retxBSR-Timer。
网元 2收到网元 1发送的所述上行授权的方法与实施例一中步骤 401 所述一致, 此处不再——赘述。
步骤 502,网元 2组建 MAC PDU,此时网元 2重启 periodicBSR-Timer, 并重启 retxBSR-Timer, 且不取消所有触发的 BSR。
网元 2组建 MAC PDU的方法与实施例一中步骤 401所述一致, 此处 不再一一赘述。
此时不取消所有触发的 BSR, 那么在后续如果还有可用于发送新数据 的上行授权, 无论是否是基于竟争的, 因为还存在已经触发但是没有取消 的 BSR, 那么网元 2还会利用所述上行授权发送 BSR。 也就是说, 即使本 次利用基于竟争的上行授权发送 BSR失败, 后续还能重新发送。
在本实施例中, 对 BSR取消的处理还可以是: 在步骤 502中区分对待 不同类型的 BSR,如果是 Regular BSR则不取消;如果是 Padding BSR则取 消;如果是 Periodic BSR则可选取消。 因为 Padding BSR是一种补充性质的 BSR, 即使没有 Padding BSR, 对网元 1调度网元 2的影响也不大, 因此此 处可以取消 Padding BSR。
步骤 503 , 网元 2发送 MAC PDIL
步骤 504, 网元 2收到来自网元 1的 MAC PDU发送成功的指示, 网 元 2取消所有触发的 BSR。
所有触发的 BSR指的是: 在步骤 502中、 以及步骤 502之前触发的, 但未取消的 BSR。 因为步骤 502与步骤 504之间相隔一定的时间, 在这段 时间内, 不排除新触发了 BSR, 这些新触发的 BSR不会因为 MAC PDU发 送成功而被取消, 因为它们指示的緩冲区中的待传输的数据量信息与 MAC PDU中指示的数据量信息不同。
本发明的实施例三描述的是: 存在至少一个已经触发但是没有取消的
BSR,有网元 1分配给网元 2的用于网元 2发送新数据的基于竟争的上行资 源的情况下,釆用本发明所述 BSR相关定时器的处理方法与取消 BSR的方 法相结合的场景。 如图 6所示, 具体包括以下步骤:
步骤 601 , 网元 2收到网元 1发送的基于竟争的上行授权( CB grant ), 指示网元 2在 UL-SCH发送新数据, 此时网元 2不重启 retxBSR-Timer。
步骤 602,网元 2组建 MAC PDU,此时网元 2不重启 periodicBSR-Timer, 不重启 retxBSR-Timer, 且不取消所有触发的 BSR。
在本实施例中, 对 BSR取消的处理还可以是: 在步骤 602中区分对待 不同类型的 BSR,如果是 Regular BSR则不取消;如果是 Padding BSR则取 消;如果是 Periodic BSR则可选取消。 因为 Padding BSR是一种补充性质的 BSR, 即使没有 Padding BSR, 对网元 1调度网元 2的影响也不大, 因此此 处可以取消 Padding BSR。
步骤 603 , 网元 2发送 MAC PDU。
步骤 604, 网元 2收到来自网元 1的 MAC PDU发送成功的指示, 网元 2重启 periodicBSR-Timer, 重启 retxBSR-Timer, 并取消所有触发的 BSR。 所有触发的 BSR指的是: 在步骤 602中、 以及步骤 602之前触发的, 但未取消的 BSR。 因为步骤 602与步骤 604之间相隔一定的时间, 在这段 时间内, 不排除新触发了 BSR, 这些新触发的 BSR不会因为 MAC PDU发 送成功而被取消, 因为它们指示的緩冲区中的待传输的数据量信息与 MAC PDU中指示的数据量信息不同。
本实施例描述的是在 BSR相关的定时器既包括 periodicBSR-Timer, 又 包括 retxBSR-Timer的情况下, 釆用对 BSR相关的定时器的处理中方法 A1 与方法 A2相结合的示例。 除了本实施例中的示例以外, 对 BSR相关的定 时器的处理还包括以下的组合方式:
1、 方法 A1与方法 A2相结合:
la 、 BSR 相关的定时器只 包括 periodicBSR-Timer , 不包括 retxBSR-Timer: 与图 6 所示实施例的不同之处在于: 步骤 602 中不重启 periodicBSR-Timer , 但是重启 retxBSR-Timer; 步骤 604 中 重启 periodicBSR-Timer, 可选地重启 retxBSR-Timer;
lb 、 BSR 相 关 的 定时器只 包括 retxBSR-Timer , 不 包括 periodicBSR-Timer: 与图 6所示实施例的不同之处在于: 步骤 602中不重 启 retxBSR-Timer , 但是重启 periodicBSR-Timer; 步骤 604 中重启 retxBSR-Timer, 可选地重启 periodicBSR-Timer。
通过本组合方式,能够尽早地重新触发 Periodic BSR或者 Regular BSR。 因为不管是触发了一个 BSR还是多个 BSR, 发送的流程都是一样的。
2、只釆用方法 A2,不釆用方法 A1 : (即步骤 601中重启 retxBSR-Timer )
2a、 所述 BSR 相关的定时器既包括 periodicBSR-Timer , 又包括 retxBSR-Timer: 其余步骤(步骤 602~604 )与图 6所示实施例相同;
通过本组合方式, 组建 MAC PDU 时不重启 periodicBSR-Timer 和 retxBSR-Timer , 使得所述定时器超时得早一些, 从而能尽早重新触发 Periodic BSR ( periodicBSR-Timer 超时的情况 ) 和 Regular BSR ( retxBSR-Timer超时的情况)。
2b、 所述 BSR 相关的定时器只包括 periodicBSR-Timer , 不包括 retxBSR-Timer, 其余步骤与本实施例的不同之处在于: 步骤 602中不重启 periodicBSR-Timer , 重 启 retxBSR-Timer ; 步 骤 604 中 重 启 periodicBSR-Timer , 可选的重启 retxBSR-Timer;
通过本组合方式, 能够尽早地重新触发 Periodic BSR。 因为不论是触发 了一个 BSR还是多个 BSR, 发送的流程都是一样的。
2c、 所述 BSR 相关的定时器只包括 retxBSR-Timer , 不包括 periodicBSR-Timer, 其余步骤与本实施例的不同之处在于: 步骤 602 中不 重启 retxBSR-Timer , 重启 periodicBSR-Timer; 步骤 604 中重启 retxBSR- Timer, 可选的重启 periodicBSR-Timer;
通过本组合方式, 能够尽早地重新触发 Regular BSR。 因为不论是触发 了一个 BSR还是多个 BSR, 发送的流程都是一样的。
3、 只釆用方法 A1 , 不釆用方法 A2 , 即: 步骤 602 中重启 periodicBSR-Timer, 重启 retxBSR-Timer; 步骤 601、 步骤 603同图 6所示 的实施例; 可选的保留步骤 604;
通过本组合方式, 在收到基于竟争的上行授权的情况下不重启 retxBSR-Timer , 使得所述定时器超时得早一些, 从而能尽早重新触发 Regular BSR。 另外, 由于步骤 602中已经重启了定时器, 而步骤 602和步 骤 604相隔的时间 4艮短, 如 LTE系统中 FDD情况下为 4ms以内 , 因此步 骤 604可以不需要重启定时器, 影响不大。
需要说明的是, 在以上各实施例中, 所述网元 1、 网元 2及发送所述 BSR相关的 MAC PDU的子帧有以下组合方式:
a、 网元 1为 eNB, 网元 2为 UE, FDD情况下所述子帧为每一个子帧, 时分双工 (TDD , Time Division Duplex )情况下所述子帧为上行子帧; b、 网元 1为中继节点(RN, Relay Node ), 网元 2为 UE, 所述子帧为 Uu的上行子帧;
c、 网元 1为施主基站(DeNB, Donor eNB ), 网元 2为 RN, 所述子帧 为 Un的上行子帧。
对应上述緩冲区状态报告处理的方法, 本发明还提供了一种緩冲区状 态报告处理的装置, 应用于 UE或 RN中, 该装置包括: BSR处理模块, 用 于在釆用基于竟争的上行资源发送 BSR的情况下, 执行以下处理方式中的 至少一种:
A、 在收到指示基于竟争的上行资源的上行授权时, 不重启重传 BSR 定时器;
B、 在有上行资源时, 不重启重传 BSR定时器和 /或周期 BSR定时器;
C、在组建 BSR相关的 MAC PDU时,不取消触发的 BSR;在收到 BSR 相关的 MAC PDU发送成功的指示时, 取消触发的 BSR;
D、 在组建 BSR相关的 MAC PDU时, 根据触发的 BSR的类型确定是 否取消触发的 BSR; 在收到 BSR相关的 MAC PDU发送成功的指示时, 取 消触发的 BSR。
较佳的, BSR处理模块进一步用于,在触发的 BSR中包括 Regular BSR 的情况下, 组建 MAC PDU时不取消该 Regular BSR; 在触发的 BSR中包 括 Periodic BSR的情况下, 组建 MAC PDU时取消或者不取消该 Periodic BSR; 在触发的 BSR中包括 Padding BSR的情况下, 组建 MAC PDU时取 消该 Padding BSR。
BSR处理模块进一步用于, 在收到 BSR相关的 MAC PDU发送成功的 指示时, 重启重传 BSR定时器和 /或周期 BSR定时器。
需要说明的是, 本发明对 BSR发送成功或者失败的指示并不做限定, 根据现有公开的机制, 网元 1在固定的偏移针对发送成功的网元 2发送下 行指配( DL assignment )或者上行授权 ( UL grant )其中携带 CB RNTI和 C-RNTI (如釆用 C-RNTI MAC控制元) 的指示, 或者网元 2在发送 BSR 之后的一段时间内收到所述下行指配或者上行授权则认为发送成功。
本发明中所述 BSR相关的 MAC PDU与现有技术的描述一致, 即所述 MAC PDU指的是:携带 BSR MAC CE的 MAC PDU或者不携带 BSR MAC CE的 MAC PDU。其中,不携带 BSR MAC CE的 MAC PDU的应用场景是: 在有触发了但是还没有取消的 BSR的情况下, 如果上行资源可以容纳所有 可传输的数据 ( pending data )但是无法再容纳 BSR MAC CE及其相应的子 据的 MAC PDU, 但是不携带 BSR MAC CE。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种緩冲区状态报告处理的方法, 其特征在于, 该方法包括: 在釆用基于竟争的上行资源发送緩冲区状态报告(BSR )的情况下,执 行以下处理方式中的至少一种:
A、 在收到指示基于竟争的上行资源的上行授权时, 不重启重传 BSR 定时器;
B、在有所述上行资源时, 不重启重传 BSR定时器和 /或周期 BSR定时 器;
C、 在占用所述上行资源组建 BSR相关的媒体接入控制层协议数据单 元(MAC PDU ) 时, 不取消触发的 BSR; 在收到 BSR相关的 MAC PDU 发送成功的指示时, 取消触发的 BSR;
D、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 根据触发的 BSR的类型确定是否取消触发的 BSR;在收到 BSR相关的 MAC PDU发送 成功的指示时, 取消触发的 BSR。
2、 根据权利要求 1所述緩冲区状态报告处理的方法, 其特征在于, 所 述根据触发的 BSR的类型确定是否取消触发的 BSR, 具体为:
如果触发的 BSR中包括常规緩冲区状态报告 ( Regular BSR ), 则组建 所述 MAC PDU时不取消所述 Regular BSR;
如果触发的 BSR中包括周期緩冲区状态报告 ( Periodic BSR ), 则组建 所述 MAC PDU时取消或者不取消所述 Periodic BSR;
如果触发的 BSR中包括填充緩冲区状态报告 ( Padding BSR ), 则组建 所述 MAC PDU时取消所述 Padding BSR。
3、根据权利要求 1或 2所述緩冲区状态报告处理的方法,其特征在于, 该方法进一步包括: 在收到 BSR相关的 MAC PDU发送成功的指示时, 重 启所述重传 BSR定时器和 /或周期 BSR定时器。
4、根据权利要求 1或 2所述緩冲区状态报告处理的方法,其特征在于, 所述触发的 BSR为组建所述 MAC PDU之前、 以及组建同时触发的 , 但未 取消的所有 BSR。
5、 一种緩冲区状态报告处理的装置, 其特征在于, 该装置包括: BSR 处理模块, 用于在釆用基于竟争的上行资源发送 BSR的情况下, 执行以下 处理方式中的至少一种:
A、 在收到指示基于竟争的上行资源的上行授权时, 不重启重传 BSR 定时器;
B、在有所述上行资源时, 不重启重传 BSR定时器和 /或周期 BSR定时 哭口.?
C、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 不取消触发 的 BSR; 在收到 BSR相关的 MAC PDU发送成功的指示时, 取消触发的 BSR;
D、 在占用所述上行资源组建 BSR相关的 MAC PDU时, 根据触发的 BSR的类型确定是否取消触发的 BSR;在收到 BSR相关的 MAC PDU发送 成功的指示时, 取消触发的 BSR。
6、 根据权利要求 5所述緩冲区状态报告处理的装置, 其特征在于, 所 述 BSR处理模块进一步用于,
在触发的 BSR中包括 Regular BSR的情况下 , 组建所述 MAC PDU时 不取消所述 Regular BSR;
在触发的 BSR中包括 Periodic BSR的情况下, 组建所述 MAC PDU时 取消或者不取消所述 Periodic BSR;
在触发的 BSR中包括 Padding BSR的情况下 , 组建所述 MAC PDU时 取消所述 Padding BSR。
7、根据权利要求 5或 6所述緩冲区状态报告处理的装置,其特征在于, 所述 BSR处理模块进一步用于,在收到 BSR相关的 MAC PDU发送成功的 指示时, 重启所述重传 BSR定时器和 /或周期 BSR定时器。
8、根据权利要求 5或 6所述緩冲区状态报告处理的装置,其特征在于, 所述触发的 BSR为组建所述 MAC PDU之前、 以及组建同时触发的 , 但未 取消的所有 BSR。
9、根据权利要求 5或 6所述緩冲区状态报告处理的装置,其特征在于, 该装置应用于用户终端 (UE )或中继节点 (RN ) 中。
PCT/CN2011/071936 2010-05-31 2011-03-17 一种缓冲区状态报告处理的方法和装置 WO2011150709A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP11789088A EP2525600A1 (en) 2010-05-31 2011-03-17 Method and apparatus for processing buffer status report
US13/578,873 US20120314672A1 (en) 2010-05-31 2011-03-17 Method and apparatus for processing buffer status report

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010188423.2A CN102264098B (zh) 2010-05-31 2010-05-31 一种缓冲区状态报告处理的方法和装置
CN201010188423.2 2010-05-31

Publications (1)

Publication Number Publication Date
WO2011150709A1 true WO2011150709A1 (zh) 2011-12-08

Family

ID=45010501

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/071936 WO2011150709A1 (zh) 2010-05-31 2011-03-17 一种缓冲区状态报告处理的方法和装置

Country Status (4)

Country Link
US (1) US20120314672A1 (zh)
EP (1) EP2525600A1 (zh)
CN (1) CN102264098B (zh)
WO (1) WO2011150709A1 (zh)

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2671880B1 (en) 2012-06-05 2015-09-16 Samsung Electronics Co., Ltd Fused polycyclic heteroaromatic compound, organic thin film including compound and electronic device including organic thin film
WO2014040301A1 (zh) * 2012-09-17 2014-03-20 华为技术有限公司 调度方法、基站、用户设备和系统
CN102932939A (zh) * 2012-10-12 2013-02-13 中兴通讯股份有限公司 一种lte系统上行调度优化方法、系统、基站及终端
WO2015035579A1 (zh) * 2013-09-11 2015-03-19 华为技术有限公司 一种数据传输方法及用户设备
US20170215201A1 (en) * 2014-07-24 2017-07-27 Lg Electronics Inc. Method and apparatus for transmitting uplink data in wireless communication system
US10149293B2 (en) * 2014-10-16 2018-12-04 Qualcomm Incorporated Transmission preemption for enhanced component carriers
WO2016112512A1 (zh) * 2015-01-15 2016-07-21 富士通株式会社 Mac控制元素的上行配置方法、装置以及通信系统
EP4236560A3 (en) * 2015-01-26 2023-11-01 Fujitsu Limited User equipment and communication system
US10470210B2 (en) * 2015-05-11 2019-11-05 Lg Electronics Inc. Method for performing RLC retransmission based on contention-based PUSCH in a wireless communication system and a device therefor
WO2016186004A1 (ja) * 2015-05-15 2016-11-24 株式会社Nttドコモ ユーザ装置、及びmacコントロールエレメント送信方法
JP7125840B2 (ja) 2015-09-18 2022-08-25 シャープ株式会社 端末装置、基地局装置、および通信方法
AU2016324082B2 (en) * 2015-09-18 2020-12-03 Sharp Kabushiki Kaisha Terminal device, base station device, communication method, and integrated circuit
WO2017063129A1 (zh) * 2015-10-12 2017-04-20 华为技术有限公司 一种资源请求方法及设备
CN106937397B (zh) * 2015-12-31 2022-04-19 中兴通讯股份有限公司 资源调度调整方法及装置
US10397947B2 (en) * 2016-08-12 2019-08-27 Qualcomm Incorporated Adaptive waveform selection in wireless communications
CN108401304B (zh) * 2017-02-04 2021-06-08 华为技术有限公司 一种缓存状态报告的触发方法、装置及系统
CN108924877B (zh) * 2017-03-24 2022-02-11 华为技术有限公司 信息的处理方法和设备
US10129255B1 (en) 2017-05-12 2018-11-13 International Business Machines Corporation Device authentication with MAC address and time period
CN107360591B (zh) * 2017-06-15 2020-01-14 电信科学技术研究院 一种上报缓存状态报告的方法和设备
CN109392008B (zh) 2017-08-11 2021-01-29 华为技术有限公司 通信方法与设备
CN109587726B (zh) 2017-09-28 2021-08-13 华为技术有限公司 通信方法、终端设备和接入网设备
CN110741675A (zh) * 2017-10-24 2020-01-31 Oppo广东移动通信有限公司 传输数据的方法、终端设备和网络设备
ES2944438T3 (es) 2018-02-09 2023-06-21 Beijing Xiaomi Mobile Software Co Ltd Método de retención de activación y aparato de retención de activación
US11432188B2 (en) * 2018-05-18 2022-08-30 Qualcomm Incorporated Indicating medium access control (MAC)-control element (CE) information
CN110831224B (zh) * 2018-08-07 2021-10-01 维沃移动通信有限公司 一种随机接入方法及终端设备
GB201812926D0 (en) * 2018-08-08 2018-09-19 Samsung Electronics Co Ltd Buffer status reporting
US11711721B2 (en) * 2019-01-25 2023-07-25 Asustek Computer Inc. Method and apparatus for triggering uplink buffer status report in a wireless communication system
CN112806053B (zh) * 2019-03-29 2023-01-24 Oppo广东移动通信有限公司 通信方法和终端设备
CN113709806A (zh) * 2020-05-20 2021-11-26 远传电信股份有限公司 基于ca及iab的用户设备及缓冲区状态上报取消方法
CN111770109B (zh) * 2020-07-13 2021-01-26 兰州城市学院 一种虚拟现实音乐歌唱练声音频和视频传输方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101562894A (zh) * 2008-04-26 2009-10-21 华为技术有限公司 一种缓冲区状态报告的发送方法及其设备
CN101572913A (zh) * 2008-04-28 2009-11-04 华为技术有限公司 缓冲区状态报告的处理方法及装置
US20090280798A1 (en) * 2008-05-07 2009-11-12 Qualcomm Incorporated Bsr prohibit timer
WO2010028157A1 (en) * 2008-09-03 2010-03-11 Qualcomm Incorporated Buffer status report triggers in wireless communications

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2461159B (en) * 2008-06-18 2012-01-04 Lg Electronics Inc Method for transmitting Mac PDUs
US20100034147A1 (en) * 2008-08-11 2010-02-11 Qualcomm Incorporated Systems, methods and apparatus for facilitating buffer status report robustness
US9167594B2 (en) * 2008-09-22 2015-10-20 Htc Corporation Method and related device of a trigger mechanism of buffer status report and scheduling request in a wireless communication system
JP2010081597A (ja) * 2008-09-26 2010-04-08 Asustek Computer Inc Bsrをトリガーするタイマーを処理する方法及び通信装置
ATE525875T1 (de) * 2008-11-04 2011-10-15 Htc Corp Verfahren zur verbesserung der aufwärtsstreckenübertragung in einem drahtlosen kommunikationssystem
EP2237633A1 (en) * 2009-04-03 2010-10-06 Panasonic Corporation Buffer status reporting in a mobile communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101562894A (zh) * 2008-04-26 2009-10-21 华为技术有限公司 一种缓冲区状态报告的发送方法及其设备
CN101572913A (zh) * 2008-04-28 2009-11-04 华为技术有限公司 缓冲区状态报告的处理方法及装置
US20090280798A1 (en) * 2008-05-07 2009-11-12 Qualcomm Incorporated Bsr prohibit timer
WO2010028157A1 (en) * 2008-09-03 2010-03-11 Qualcomm Incorporated Buffer status report triggers in wireless communications

Also Published As

Publication number Publication date
CN102264098B (zh) 2015-12-16
CN102264098A (zh) 2011-11-30
US20120314672A1 (en) 2012-12-13
EP2525600A1 (en) 2012-11-21

Similar Documents

Publication Publication Date Title
WO2011150709A1 (zh) 一种缓冲区状态报告处理的方法和装置
CN110278616B (zh) 无线通信系统中随机接入过程期间处置传送的方法和设备
US10582418B2 (en) Method and apparatus of transmitting data duplication in a wireless communication system
KR102110682B1 (ko) 무선 통신 시스템에서 랜덤 액세스 절차 동안 대역폭 부분 (bwp) 비활성 타이머를 처리하는 방법 및 장치
US10129005B2 (en) Method and apparatus for transceiving data using plurality of carriers in mobile communication system
CN111511036B (zh) 针对系统信息请求的随机接入程序的方法和设备
CN110476474B (zh) 用于执行随机接入过程的设备和方法
US10348470B2 (en) Method of controlling a monitoring operation of physical downlink channel in wireless communication system
JP6771489B2 (ja) 無線通信システムにおける複数個のサブフレーム上の上りリンク承認に基づいてack/nackを指示する方法及びその装置
EP2849357B1 (en) Method and apparatus for transmitting and receiving data using plurality of carriers in mobile communication system
JP6009064B2 (ja) バッファー状態報告の方法、システム及び装置
KR101818689B1 (ko) 캐리어 집적을 이용하는 불연속 수신 모드에서의 동작
JP2018019403A (ja) 無線通信システムにおけるランダムアクセス手順のmsg3送信を改善するための方法及び装置
KR20200103790A (ko) Nr을 위한 harq 버퍼 관리 방법
JP2011521518A (ja) ランダムアクセス手順を行う方法及び装置
WO2009057932A2 (en) Method of performing random access procedure in wireless communication system
WO2010085908A1 (zh) 用户设备接入方法及系统和网络接入设备
CN107624263A (zh) 无线通信系统中确定基于竞争的pusch的传输结果的方法及其设备
WO2011047580A1 (zh) 中继节点的数据传输冲突的处理方法和装置
USRE50037E1 (en) Method and apparatus for transceiving data using plurality of carriers in mobile communication system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11789088

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13578873

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2011789088

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE