NR-u LBT mac procedures
Patent Information
- Application Number
- IN202117018650
- Authority / Receiving Office
- IN · IN
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-09-26
- Filing Date
- 2021-04-22
- Publication Date
- 2026-07-09
- Estimated Expiration
- 2039-09-26
AI Technical Summary
In NR-U systems, Listen Before Talk (LBT) failures can lead to inappropriate actions in MAC procedures, resulting in unintended consequences such as incorrect power settings, data loss, and disrupted communication due to improper handling of bandwidth part inactivity, random access, power headroom reporting, SCell activation/deactivation, discontinuous reception, scheduling requests, and buffer status reporting.
Modifying existing MAC procedures to account for LBT failures by extending timers, adjusting counters, and providing explicit LBT success/failure indications to prevent inappropriate actions and ensure proper operation, including the introduction of new procedures like the Listen Before Talk Report (LBTR) to coordinate UE and NB MAC operations.
The proposed solution ensures stable and efficient MAC procedure operation in NR-U systems by preventing unintended consequences of LBT failures, maintaining data integrity, and optimizing resource management, thereby improving overall system performance and user data transmission.
Abstract
Description
CROSS-REFERENCE TO RELATED APPLICATIONSThis application claims the benefit of U.S. Provisional Patent Application No.62 / 736,816, filed on September 26, 2018, entitled“NR-U LBT MAC Procedures,” and U.S. Provisional Patent Application No. 62 / 753,579, filed on October 31, 2018, entitled“NR-U LBT MAC Procedures,” the contents of both applications are hereby incorporated by reference herein.BACKGROUND
[0001] LTE Licensed Assisted Access. 3GPP release 16 NR will support unlicensed operation without a licensed assisted connection which was available in previous releases. Since in previous releases there was always a licensed connection, it was not necessary to ensure a high level of QoS on the unlicensed connection.
[0002] Operation in unlicensed requires Listen Before Talk (LBT) procedures to not interfere with existing traffic and gain access to the channel.
[0003] Carrier aggregation with at least one SCell operating in the unlicensed spectrum is referred to as Licensed- Assisted Access (LAA). In LAA, the configured set of serving cells for a UE therefore always includes at least one SCell operating in the unlicensed spectrum according to frame structure Type 3, also called LAA SCell. Unless otherwise specified, LAA SCells act as regular SCells.
[0004] LAA eNB and UE apply Listen-Before-Talk (LBT) before performing a transmission on LAA SCell. When LBT is applied, the transmitter listens to / senses the channel to determine whether the channel is free or busy. If the channel is determined to be free, the transmitter may perform the transmission; otherwise, it does not perform the transmission. If an LAA eNB uses channel access signals of other technologies for the purpose of LAA channel access, it shall continue to meet the LAA maximum energy detection threshold requirement in3GPP TS 36.321, (E-UTRA), Medium Access Control (MAC) protocol specification, V15.2.0 [1] Further context may be included in 3GPP TS 36.321, (E-UTRA), Medium Access Control (MAC) protocol specification, VI 5.2.0.SUMMARY
[0005] Disclosed herein are methods, apparatuses, and systems associated with existing MAC procedures that may maintain proper operation and performance of MAC procedures, suchas when operating in unlicensed spectrum. In NR-U when LBT failures occur existing MAC procedures may take inappropriate actions resulting in unintended consequences.
[0006] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not constrained to limitations that solve any or all disadvantages noted in any part of this disclosure.BRIEF DESCRIPTION OF THE DRAWINGS
[0007] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:
[0008] FIG. 1 illustrates an exemplary system for NR-U LBT MAC procedures;
[0009] FIG. 2 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0010] FIG. 3 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0011] FIG. 4 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0012] FIG. 5 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0013] FIG. 6 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0014] FIG. 7 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0015] FIG. 8 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0016] FIG. 9 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0017] FIG. 10 illustrates an exemplary method associated with NR-U LBT MAC procedures;
[0018] FIG. 11 illustrates an exemplary display (e.g., graphical user interface) that may be generated based on the methods, systems, and devices of NR-U LBT MAC procedures;
[0019] FIG. 12A illustrates an example communications system;
[0020] FIG. 12B illustrates an exemplary system that includes RANs and core networks;
[0021] FIG. 12C illustrates an exemplary system that includes RANs and core networks;
[0022] FIG. 12C illustrates an exemplary system that includes RANs and core networks;
[0023] FIG. 12E illustrates another example communications system;
[0024] FIG. 12F is a block diagram of an example apparatus or device, such as a WTRU; and
[0025] FIG. 12G is a block diagram of an exemplary computing system.DETAILED DESCRIPTION
[0026] Disclosed herein are methods, apparatuses, and systems associated with MAC procedures that help maintain proper operation and performance of MAC procedures, for example, when operating in unlicensed spectrum. In NR-U when LBT failures occur existing MAC procedures may take inappropriate actions resulting in unintended consequences.
[0027] Specific issues related to MAC procedures addressed herein may include issues associated with bandwidth part (BWP) operation procedure, random access procedure, Power Headroom Reporting (PHR) procedure, SCell activation or deactivation procedure,discontinuous reception procedure, scheduling request (SR) procedure, buffer status reporting procedure, logical channel prioritization procedure, or coordination of UE and node B (NB) MAC procedures, among other things.
[0028] The Bandwidth Part Operation Procedure Issue -When LBT Failures occur: The Bandwidth Part Inactivity Timer may expire resulting in switching to the Initial or Default BWP even when there is UL or DL data to be scheduled.
[0029] The Random Access Procedure Issue - When LBT failures occur: 1) The Random Access Response Window may expire without allowing a sufficient number (e.g., threshold number) of transmission opportunities for the Random Access Response; 2) The Preamble Transmission Counter may reach the maximum number of transmissions without allowing for a sufficient number preamble transmissions needed for successful preamble transmission; 3) The Contention Resolution Timer may expire without allowing for a sufficient number of PDCCH transmission opportunities in response to MSG3 transmission; or 4) The power ramping may be increased even when there is no preamble transmission resulting in incorrect power setting.
[0030] The Power Headroom Reporting (PHR) Procedure Issue - When LBT failures occur: 1) The NB may not be able to determine when the PHR was calculated, and what was transmitted at that time, resulting in an incorrect power headroom determination; 2) PHR triggering due to the PHR Periodic Timer, reconfiguration, SCell Activation, PSCell Addition, or Prohibit Timer expiration may occur inappropriately early; 3) PHR Calculation may incorrectly calculate power headroom assuming a real transmission; or 4) The PHR Prohibit timer may be set even when there was no PHR transmission.
[0031] The SCell Activation / Deactivation Procedure Issue - When LBT failure occur: The SCell Deactivation Timer may expire, deactivating the SCell when there is UL or DL data to be scheduled on the SCell.
[0032] The Discontinuous Reception Procedure Issue - When LBT failures occur: The On Duration or Inactivity Timers may expire, stopping PDCCH reception, when there is UL or DL data to be scheduled.
[0033] The Scheduling Request Procedure Issue - When LBT failures occur: 1) Failed SR transmissions will not initiate a Random Access procedure; 2) The SR Prohibit timer may be set even when there was no SR transmission; 3)The SR Transmission Counter may reach the maximum number of transmissions without allowing for a sufficient number SR transmissions needed for successful SR transmission; or 4) SR Pending may be cleared even when there is no SR transmission.
[0034] The Buffer Status Reporting Procedure Issue - When LBT failures occur: When there may be UL-SCH resources available, BSR may not be transmitted and an SR will not be triggered.
[0035] The Logical Channel Prioritization Procedure Issue - When LBT failures occur: A MAC PDU may not be able to be transmitted in a subsequent grant resulting in loss of user data and control signaling.
[0036] Coordination of UE and NB MAC Procedures Issue - When LBT failures occur: The UE may take actions effecting MAC procedures that need to be known to the NB for proper operation. Additionally, the NB may take actions independent of UE behavior.
[0037] In view of the aforementioned example issues, there may be modification of existing MAC procedures ore the creation of new MAC procedures that may take into account LBT failures so that inappropriate actions are not taken and unintended consequences are avoided. A summary of how the issues may be addressed are disclosed below.
[0038] FIG. 1 illustrates an exemplary system for NR-U LBT MAC procedures. At step111, UE 101 may obtain information regarding base station 102 channel access to the UE 101.The information may be downlink information signaled from base station 102. At step 112, UE 101 may detect information about uplink channel access (e.g., uplink information) to the base station 102. The uplink information may be detected by doing Listen-Before-Talk (LBT) operation or another operation (e.g., operations within 3GPP TS 36.213 V14.8.0 section 15). At step 113, based on the information of step 111 or step 112 (e.g., upbnk / downbnk information), MAC procedure operation may be effected. MAC procedures may include LBTR 121 (e.g., FIG. 10), DRX 122 (e.g., FIG. 6), BWP operation 123 (e.g., FIG. 2), or random access 124 (e.g., FIG. 3), Scheduling Request 125 (e.g., FIG. 7) among others as disclosed herein (e.g., PHR, BSR, or BFD). It is contemplated herein that uplink or downlink channel access information may be used in the steps above.
[0039] FIG. 2 - FIG. 10 illustrate exemplary methods associated with NR-U LBT MAC procedures, which are described in more detail herein.
[0040] FIG. 2 illustrates an exemplary method for a bandwidth part (BWP) operation procedure. For example, at step 131, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. At step 132, based on the detected failure of step 131, a BWP inactivity timer may be extended. The inactivity timer may be extended so that switching to the initial or default BWP may be avoided because there may be UL or DL data to be scheduled. At step 133, based on the detected failure of step 131, switching to alternate Bandwidth Part.
[0041] FIG. 3 illustrates an exemplary method for a random access procedure.- For example, at step 141, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on the detected failure of step 141, UE 101 may execute steps 142, 143, 144, or 145. At step 142, the random access response window may be extended. Step 142 may allow for a sufficient number of transmission opportunities for the random access response. At step 143, the preamble transmission counter may not be incremented. Step 143 may allow for a sufficient number of preamble transmissions to be made to allow for successful preamble transmission. At step 144, the contention resolution timer may be extended, which may allow for a sufficient number of PDCCH transmission opportunities in response to MSG3 transmission. At step 145, the power ramping may not be increased, which may assist in maintaining proper power setting. At step 146, RA problem may be indicated to higher layers and consider RA procedure unsuccessful. At step 147, there may be a switch to alternate bandwidth part. It is contemplated herein that one or more of step 142 through step 147 may occur based on step 141.
[0042] FIG. 4 illustrates an exemplary method for a power headroom reporting procedure. For example, at step 151, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on the detected failure of step 151, UE 101 may execute steps 152, 153, 154, 155, 156, 157, or 158. At step 152, UE 101 may indicate to base station 102 (e.g., node B) when the PHR was calculated. At step 153, UE 101 may indicate to base station 102 what was transmitted at the time of PHR calculation. At step 154, UE 101 may indicate to base station 102 when LBT failures have occurred. At step 155, UE 101 may indicate to base station 102 that there has been a delay in PHR transmission. At step 156, PHR triggering due to the PHR Periodic Timer, reconfiguration, SCell Activation, PSCell Addition, or Prohibit Timer expiration may be delayed. At step 157, PHR Calculation may take into account lost or delayed transmissions. At step 158, PHR prohibit timer may be not set or may be delayed.
[0043] FIG. 5 illustrates an exemplary method for a SCell Activation / Deactivation Procedure. For example, at step 161, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on step 161, at step 162, the SCell deactivation timer may be extended, which may allow for additional UL or DL data scheduling opportunities on the SCell.
[0044] FIG. 6 illustrates an exemplary method for a discontinuous reception procedure. For example, at step 171, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on step 171, the On Duration or Inactivity Timers may be extended, which may allow for additional UL or DL data scheduling opportunities. At step 173, DRX Short Cycle timer may be applied. At step 174, On Duration or Inactivity timers may be aligned with MCOT, CWS or CCA. At step 175, DRX configuration may be adjusted. It is contemplated herein that one or more of step 172 through step 175 may occur based on step 171.
[0045] FIG. 7 illustrates an exemplary method for a scheduling request procedure. For example, at step 181, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on the detected failure of step 181, UE 101 may execute steps 182, 183, 184, or 185. At step 182, a random access procedure may be initiated. At step 183, the SR prohibit timer may not be set or the setting of the prohibit timer may be delayed. At step 184, the SR transmission counter may not be incremented to allow for a sufficient number of SR transmissions needed for successful SR transmission. At step 185, SR pending may not be cleared or the clearing of SR Pending may be delayed. At step 186, there may be a switching to an alternate bandwidth part. It is contemplated herein that one or more of step 182 through step 186 may occur based on step 181.
[0046] FIG. 8 illustrates an exemplary method for a buffer status reporting procedure. For example, at step 191, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on step 192, even though there may be UL-SCH resources available, an SR may be triggered.
[0047] FIG. 9 illustrates an exemplary method for a logical channel prioritization procedure.- For example, at step 201, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on the detected failure of step 201, UE 101 may execute steps 202 or 203. At step 202, a MAC PDU may not be built. At step 203, a MAC PDU may be reformatted, which may allow for transmission in a subsequent grant.
[0048] FIG. 10 illustrates an exemplary method for UE 101 reporting LBT failure or success information to the base station 102, which may allow improved coordination of UE 101 and base station MAC Procedures. For example, at step 211, one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) are detected. Based on step 211, UE 101 may report LBT failures or report which procedures are affected and how. At step 213, Report includes LBT success / failure statistics within configured period of time. At step 214, Report includes timing information, CCA, MCOT, or CWS. At step 215, Transmission Prohibit timer set to minimize frequency of reporting. It is contemplated herein that one or more of step 212 through step 215 may occur based on step 181.
[0049] FIG. 2 - FIG. 10 illustrate exemplary methods associated with NR-U LBT MAC procedures. Multiple NR-U LBT MAC procedures are described in more detail below.NR-U LBT Operation Effect on MAC
[0050] The disclosed subject matter may apply to the overall MAC operation and numerous specific MAC procedures. These MAC procedures may include bandwidth part (BWP) operation, random access (RA), power headroom reporting (PHR), Scell activation and deactivation, logical channel prioritization (LCP), discontinuous reception (DRX), scheduling request (SR), buffer status report (BSR), and potentially a new LBT MAC procedure and others.
[0051] LBT Failures can result in unnecessary and unintended effects on these MAC procedures. With knowledge of LBT Failures or successes these MAC procedures may operate similarly and with similar performance to operation in licensed spectrum where LBT is not required. It is contemplated that the steps (e.g., actions) that may be disclosed with a first MAC procedure (e.g., Random Access) may be applicable to a second MAC procedure (e.g., BWP Operation). Therefore, the steps are generally not limited to a particular MAC procedure.General Considerations for Both UL and DL LBT Failures
[0052] With respect to the effect on MAC procedures LBT failures may be considered in the UL or in the DL. Depending on the MAC procedure, and specific actions within the procedure, both UL and DL LBT failures may be considered, or only UL or only DL LBT failures may be considered. Additionally, how LBT indications are provided to the MAC and what information is provided may be different for the UL and DL.
[0053] For UL LBT operation the PHY layer may indicate to the MAC, LBT success or failure. The UL LBT success or failure indication may be associated with an UL transmission or the UL LBT procedure may be performed independently of an UL transmission. Each UL LBT success or failure indication may be associated with one or more MAC procedures.
[0054] For DL LBT operation the NB may signal to the UE DL LBT success or failures. The DL LBT success or failure indication may be associated with an DL transmission or the DL LBT procedure may be performed independently of an DL transmission. Each DL LBT success or failure indication may be associated with one or more MAC procedures.
[0055] Depending on the MAC procedure, and specific actions within the procedure it may be necessary to perform LBT even when there is no associated transmission. This may be necessary since currently MAC procedures assume there is constant access to the channel and there is no halting or blocking of transmissions. For example, if the UE detects no downlink assignments or uplink grants MAC procedures there may be an assumption that there is no data to be scheduled for transmission in the downlink or uplink. But there may be data to be scheduled for transmission which has been blocked or delayed by LBT failures. In this case MAC procedures may take actions which may result in unintended or unwanted consequences.
[0056] When LBT Failure or Success may be referred to in this disclosure for overall MAC operation or specific MAC procedures, both uplink LBT or downlink LBT may be considered. Depending on the MAC procedure, and specific actions within the procedure, both UL and DL LBT failures are considered, or just UL or just DL LBT failures are considered.
[0057] It should be noted it is not necessary to signal or indicate to the MAC both LBT Failures and Successes. Lack of am LBT Failure indication may be interpreted as a Success, and lack of a Success indication may be interpreted as a Failure. UL LBT indications from the PHY layer may only indicate LBT Failures, and DL LBT indications from the NB may only indicate LBT Successes.
[0058] LBT success or failure indication may be provided periodically on known occasions or maybe triggered by specific actions taken by a MAC procedure. DL LBT successes or failures may be periodically signaled by the NB, and UL LBT successes or failures may be indicated by the PHY layer depending on operation of specific MAC procedures. Note periodic indications may be augmented by on demand indications driven by MAC procedures and vice versa.
[0059] LBT success or failure indications may be for a specific LBT procedure operation or the indications may provide information on more than one LBT procedure operation over a known period of time. The period of time may be the period since the last report. UL LBT indications may result from a specific LBT procedure operation, and DL LBT indications may provide information on multiple (e.g., a threshold number of) LBT operations over a period of time.
[0060] LBT success or failure indications may provide information on the carrier and BWP(s), where the LBT is performed. In addition to uplink or downlink LBT success, failure, indications further LBT procedure information may be provided to MAC procedures. MAC procedures take into account transmission opportunities in the downlink and uplink. For proper operation of these MAC procedures it may be necessaryto know the time periods transmissions can or can’t be made in the uplink and downlink. To accomplish this, it is disclosed herein an addition to, or included with the LBT success or failure indication, the period of Clear Channel Assessment (CCA), the selected Maximum Channel Occupancy Time (MCOT), the selected Contention Window Size (CWS), and other timing information is provided to the MAC to allow for proper determination of downlink and uplink transmission opportunities. The MCOT, CWS, or other timing may be identified by the Channel Access Priority Class (CAPC) or another index representing the selected timing.Downlink LBT Success / Failure Indications
[0061] It has been discussed that a DL LBT Success indication may be signaled from the NB to the UEs during the UEs’ DRX On Duration to effect DRX cycles. This should be extended to include the period the DRX Inactivity Timer is running, and potentially all periods that comprise DRX Active Time. For example, when a Random Access or Scheduling Request procedure is initiated while the UE is not within the DRX On Duration, knowledge of LBT failures may be necessaryfor proper operation and performance similar to operation when LBT is not required.
[0062] Further, as a more comprehensive way to address this problem consider DL LBT Success indications that are continuously transmitted in a periodic manner known to the UE to allow MAC procedures which run outside of the DRX Active Time to benefit from the knowledge of DL LBT Success and Failures.
[0063] The DL LBT Success indication may be a new explicit signal or implicitly detected. For example, DL LBT Success may be implicitly detected by reception of SSB or DRS, and the new explicit signal may be a new DCI format (e.g., addressed to individual UE or a group of UEs or broadcast to all UEs).
[0064] Signaling DL LBT Success indications continuously in a periodic manner does not necessarily add complexity or require greater use of resources because DRX On Durations are in general staggered in time for different UE’s. Depending on the periodicity signaling overhead may even be reduced.
[0065] It should also be noted that signaling DL LBT indications may be UE specific or specific to groups of UE’s that share DRX On Durations. Cell specific DL LBT indications can result in a more efficient use of resources and more consistent MAC procedure operation and performance.
[0066] It is also considered the LBT Success indication may not be a single indication. The information signaled may also provide information for the period since the last LBT Success indication. The information signaled may also provide information for how long the NB has access of the DL channel, for example, to a specific channel or BWP. In this case, MAC procedures may have continuous knowledge over time of DL LBT Success or Failure which may result in more accurate effect on MAC procedures due to DL LBT Failure.
[0067] Downlink success indications may also provide timing information identifying periods when transmissions can and cannot be made in order for MAC procedures to be able to determine transmission opportunities accurately. To accomplish this, there may be an addition to, or included with the LBT success indication, the period of Clear Channel Assessment (CCA), the selected Maximum Channel Occupancy Time (MCOT), the selected Contention Window Size (CWS), or other timing information provided to the MAC to allow for proper determination of downlink transmission opportunities. The MCOT, CWS, or other timing information may be identified by the Channel Access Priority Class (CAPC) or another index representing the selected timing.Uplink LBT Success / Failure Indications
[0068] In addition to the NB indicating LBT Failure or Success status to the UE, the UE may provide UL LBT Failure or Success information to the NB.
[0069] As disclosed herein, there may be multiple potential effects on UE MAC procedures. There may be multiple cases where it may be necessary for the NB to know how LBT Failure or Success have affected certain MAC procedures. For example, if DRX Active Time or DRX Cycles have been affected the NB must know for the UE to be properly scheduled.
[0070] The LBT procedure may do more than indicate UL LBT failures to the NB. After a significant amount of UL LBT failures, other actions may be taken. As discussed herein, operation of existing MAC procedures may be affected by LBT failures. The new LBT procedure has the possibility to take new actions to help resolve LBT failures. For example, the channel Access Priority may be adjusted to increase the chance of successful LBT.
[0071] Total number of LBT failures may be counted, which maybe within a specified or configured period of time. Alternatively, LBT Failure Counters (FC) may count consecutive LBT failures, and upon an LBT success the LBT FC may be reset to zero. The period in which LBT failures may be counted may be a sliding window in time. When the LBT failure counter exceeds a specified or configured threshold, the LBT State may be considered failed. If a specified or configured number of LBT failures have not been exceeded or a specified or configured number of LBT success indications are received, the LBT State may be considered successful. MAC procedures may check the LBT State rather than counting individual LBT failures associated with the MAC procedure. MAC procedures may adjust counters and timers according to the LBT State. For example, MAC procedures may extend counters and timers, or consider timers and counters to have reached the maximum thresholds depending on the LBT State. The LBT State may also be indicated to higher layers. For example, to affect RRC procedures.
[0072] A new MAC LBT Report (LBTR) procedure may be defined to provide UL LBT success or failure information. A LBTR MAC CE may provide historical information on previous UL LBT results. This may be over a certain period relative to when the report was generated. For example, it may be the period since the last LBTR MAC CE was transmitted. The MAC CE may provide information relative to which MAC procedure(s) was affected or when the LBT failure occurred so that the NB may attempt correlate which procedure(s) were affected. The LBTR MAC CE may also include BWP information in the LBT results for e.g., on which BWP LBT fails and on which BWP LBT was successful. RRC may configure into the UE, the LBTR reporting period.
[0073] Alternatively, UL physical control signaling may provide UL LBT Failure orSuccess indication. This may be carried on PUCCH or piggybacked on PUSCH if scheduled or new UL signaling. Lack of reception of an periodic UL signaling may be interpreted as UE LBT Failure. This may be the PUCCH or new UL signaling. New UL signaling may have to be configured so that NB reception occurs at a known physical resource and at a known time.
[0074] Uplink LBT success or failure indications may also provide timing information identifying periods when transmissions can and cannot be made in order for MAC procedures to be able to able to determine transmission opportunities accurately. To accomplish this, it is proposed in addition to, or included with the LBT success or failure indication, the period of Clear Channel Assessment (CCA), the selected Maximum Channel Occupancy Time (MCOT), the selected Contention Window Size (CWS), or other timing information is provided to the MAC to allow for proper determination of uplink transmission opportunities. The MCOT, CWS, or other timings may be identified by the Channel Access Priority Class (CAPC) or another index representing the selected timing.LBT Effect on MAC Timers and Counters
[0075] LBT failures may result in lost transmission opportunities. Loss of transmission opportunities also result in a greater period of time to achieve successful transmissions. MAC procedures consider an amount of transmission opportunities and period of time to complete before declaring failure of the procedure. To properly perform MAC procedures when LBT is required, the count of transmission opportunities and possibly the period allowed for the procedure to complete successfully need to consider LBT failures.
[0076] Existing MAC procedures assume when a MAC PDU is given to the PHY layer or an instruction is given to the PHY to transmit PHY uplink control information (e.g. SR), the PDU or the PHY uplink control information is transmitted. When a MAC CE associated with a particular MAC procedure is built and multiplexed into a MAC PDU it may be assumed this MAC CE is transmitted. To limit the frequency a MAC CE or PHY uplink control information associated with particular MAC procedures may be transmitted, prohibit timer may be set when the MAC CE is built and the MAC PDU may be given to the PHY layer, or when instruction is given to the PHY to transmit PHY uplink control information. To properly control the frequency a MAC CE or PHY uplink control information may be transmitted and ensure it is transmitted when needed setting of these prohibit timers also may consider LBT failures.
[0077] The sequence of processing MAC procedures also may be considered. Existing procedures may increment counters and timers may run when the MAC procedure executes before LBT is performed by the PHY layer. Multiple methods may be considered with regard to affecting the existing MAC procedures, which may be related to the following: 1) When theMAC receives an indication of LBT failure from the PHY layer counters and timers are adjusted to take the transmission failure into account; 2) When LBT succeeds timers and counters are acted upon; or 3) LBT failure are recorded during the period between when the initial MAC procedure was performed or between when they were initially set to the point counter(s) or timer(s) reach their maximum threshold.
[0078] When the MAC receives an indication of LBT failure from the PHY layer counters and timers are adjusted to take the transmission failure into account. Counters that were incremented when the MAC procedure was performed may be decremented so that they are unchanged from what they were set to before the procedure was performed. This may be somewhat more complex for the timers. Optimally the maximum time for the procedure should not consider the period of LBT failure. There are multiple options for effecting MAC timers when LBT failures occur depending on how the timers are used for different MAC procedures: a). The period from when the MAC procedure associated with the LBT failure was performed to the next opportunity to perform the MAC procedure is subtracted from the timers or is added to the maximum time threshold (when the timer expires); b). The timer is stopped upon reception of the LBT failure indication and restarted upon the next opportunity to perform the MAC procedure; c). The timer is restarted upon the LBT failure indication; or d). The period from when the timer in the MAC procedure associated with the LBT failure was set (start or restart) to the next opportunity to set the timer in the MAC procedure is subtracted from the timers or is added to the maximum time threshold (when the timer expires).
[0079] One concern with this approach is what happens when between the time when the MAC procedure was performed and reception of an LBT failure indication counter(s) or timer(s) associated with the MAC procedure reaches the maximum value. One way to address this issue would be when a timer or counter reaches its maximum value the MAC checks if it is awaiting an LBT indication for the previous transmission and only invokes the actions associated with the timer or counter expiration after a successful LBT indication is determined.
[0080] When LBT succeeds timers and counters are acted upon. In this method, when the MAC procedure is performed counter(s) and timers(s) are not acted on. Upon indication of LBT success, the counters are incremented and timers are checked or adjusted. One issue with this approach is if upon the LBT success indication the timers or counters have reached their maximum threshold, which in cases mean the MAC procedure would have been performed differently. There are a few options to deal with this situation: When performing the MAC procedure timers and counters may be checked to see if upon performing the procedure the timers or counters would have reached their maximum thresholds if they had been adjustedaccording to the procedure, and in this case the MAC procedure may take actions as if the counters or timers had reached their maximum thresholds.
[0081] LBT failures may be recorded during the period between when the initial MAC procedure was performed or between when they were initially set to the point counter(s) or timers(s) reach their maximum threshold. When timers or counters reach their maximum threshold the LBT failure record is checked, and if LBT failures have occurred the procedures adjust the timers and counters to take the LBT failures into account. There may b multiple options to accomplish this as the following (a) or (b): (a) The maximum timer and counter thresholds are adjusted according to the number of LBT failures or the time period of LBT failures so that actions taken upon reaching maximum thresholds are not taken at this time; or (b) The timers and counters are restarted according to the number of failures and the time period of the LBT failures so that actions taken upon reaching maximum thresholds are not taken at this time.
[0082] LBT failures affecting timers and counters may result in an unacceptable delay (e.g., reaching a threshold) or even endlessly stalling of a MAC procedure. MAC procedure counters and timers may never reach their maximum thresholds. The disclosed changes to the MAC procedures therefore may take into account the possibility of continuous or a significant amount of LBT failures. In this case, the MAC procedures may take into account a maximum extension in time or maximum extension of counters so each MAC procedure is properly performed. For example, limiting extensions in MAC procedure counters (MAC PC) and timers (MAC PT) may be addressed by the following methods: 1) MAC procedure LBT Failure Counters (LBT FC); MAC PC and MAC PT Extension Counters (EC); or MAC PC and MAC PT Extended Maximum Thresholds (EMT).
[0083] MAC procedure LBT Failure Counters (LBT FC): LBT FC’s may count total LBT failures, which maybe within a specified or configured period of time. Alternatively, LBT FC’s may count consecutive LBT failures, and upon an LBT success the LBT FC is reset to zero. LBT FC periods maybe the time allowed for a MAC procedure to complete, or maybe sliding windows in time. A specific MAC procedure may have more than one LBT FC. When a MAC procedure performs independent actions in parallel each may have an LBT FC. LBT FC’s may have specified or configured maximums. When an LBT FC reaches a maximum count, the MAC PC or MAC PT are no longer extended upon LBT failure for the MAC procedure. Alternatively, when an LBT FC reaches a maximum count the MAC procedure takes actions as if the MAC PC or MAC PT have reached their maximum values. In cases this results in the MAC procedure to be considered to have failed.
[0084] MAC PC and MAC PT Extension Counters (EC): LBT failures cause MAC PC or MAC PT maximum thresholds to be extended. The criteria for extending maybe a specified or configured number of LBT failures within a specified or configured period of time. For example, it may be the MAC PT maximum threshold. EC’s may count total MAC PC or MAC PT extensions, which maybe within a specified or configured period of time. Alternatively, EC’s may count consecutive MAC PC or MAC PT extensions. EC periods maybe the time allowed for a MAC procedure to complete, or maybe sliding windows in time. A specific MAC procedure may have more than one EC. When a MAC procedure performs independent actions in parallel each may have an EC. EC’s may have specified or configured maximums. When and EC reaches a maximum count the MAC PC or MAC PT are no longer extended upon LBT failure for the MAC procedure. Alternatively, when an EC reaches a maximum count the MAC procedure may take actions as if MAC PC’s or MAC PT’s have reached their maximum values. This may result in the MAC procedure to be considered to have failed.
[0085] MAC PC and MAC PT Extended Maximum Thresholds (EMT): LBT failures may cause MAC PC or MAC PT maximum thresholds to be extended. The MAC PC or MAC PT maximum thresholds may be extended upon each LBT failure or upon a specified or configured number of LBT failures within a specified or configured period of time. For example, the period of time may be the current MAC PT maximum threshold. The MAC PC or MAC PT maximum thresholds maybe extended upon a specified or configured consecutive number of LBT failures. When MAC PC or MAC PT reach a specified or configured EMT, the MAC PC or MAC PT maximum thresholds may no longer be extended. In cases this results in the MAC procedure to be considered to have failed.
[0086] MAC procedures may also have timers that may be used to control the frequency the procedure is performed. These timers may be known as prohibit timers. When some MAC procedures are performed prohibit timers set the earliest time the procedure is allowed to be performed again. MAC procedures currently set these timers when the procedure is performed. Multiple methods or systems may be used to address this, such as 1) Prohibit timers may be no longer set when the procedures are performed and may be now set or not depending on LBT success or failure. Only upon LBT Success for the transmission associated with theMAC procedure should prohibit timers be set. The LBT procedure may take some time to succeed. In this case starting of the prohibit timer may be delayed relative to when the MAC procedure was performed. This may be necessaryto ensure the frequency the MAC procedure is performed is properly restricted; or 2) Prohibit timers which may be set upon performing the MAC procedure are cleared if an LBT Failure indication is received for the transmission associated with the MAC procedure. If the LBT procedure results in a delayed transmission the prohibit timer may be extended to take the time from when the MAC procedure was performed to the time when LBT success was determined into account.Lost Scheduling and Transmission Opportunities
[0087] MAC procedures may also take into account downlink assignments and uplink grants. LBT Failures may result in loss of downlink assignments and uplink grants. When the NB determines LBT Failure PDCCH scheduling opportunities may be lost. Also, when the UE determines LBT Failure even though PDCCH scheduling is received the uplink transmission opportunity is lost.
[0088] Multiple MAC procedures take actions when downlink assignments or uplink grants may not be received within a configured monitoring time period. LBT Failures or LBT Successes may be taken into account in MAC procedure criteria for not receiving downlink assignments and uplink grants. In addition to uplink or downlink LBT success, failure, indications further LBT procedure information may be provided to MAC procedures. In addition to, or included with the LBT success or failure indication, the period of Clear ChannelAssessment (CCA), the selected Maximum Channel Occupancy Time (MCOT), the selected Contention Window Size (CWS), or other timing information is provided to the MAC to allow for proper determination of downlink and uplink transmission opportunities. The MCOT, CWS, or other timing may be identified by the Channel Access Priority Class (CAPC) or another index representing the selected timing.
[0089] Multiple options may be considered if during the configured monitoring period when no downlink assignments or uplink grants may be received, LBT Failure is detected or LBT Success is not detected:If no LBT Success has been detected during the monitoring time period no actions may be taken by the MAC procedure.If a configured minimum threshold of LBT Success or continuous LBT success detections is not reached within the monitoring time period no actions may be taken by the MAC procedure.If an LBT Failure has been detected during the monitoring time period no actions may be taken by the MAC procedure.If a configured maximum threshold of LBT Failure or continuous LBT Failure detections is reached within the monitoring time period no actions may be taken by the MAC procedure.The number of or the time period of uplink or downlink transmission opportunities may be more accurately determined from CCA, MCOT, CWS, or other timing information.
[0090] Actions that are not taken by the MAC procedure are actions that may have been taken by the currently specified MAC procedure when no downlink assignments or uplink grants are received during the configured monitoring period. For example:If during the time the BWP Inactivity timer is running LBT Failures are detected or LBT Successes are not detected, BWP switching to the Initial or Default BWP will not be performed even though no downlink assignments or uplink grants were received during this period.If during the time the DRX Active Time LBT Failures are detected or LBT Successes are not detected, the DRX Inactivity may be reset even though no downlink assignments or uplink grants were received during this period.
[0091] MAC procedures may also need to take into account when an uplinktransmission cannot be made due to LBT Failure. The effect on MAC procedures is the same as when LBT Failures result in lost PDCCH scheduling opportunities. MAC procedures may consider UL transmission failures due to LBT the same as is currently performed currently when no uplink grant is received or when the uplink grant is not acceptable for data available for transmission (e.g., LCP restriction). For e.g., during back-off periods following LBT failure, the MAC procedures may behave as it currently behaves when no uplink grant is received or when the uplink grant is not acceptable for data available for transmission (e.g. LCP restriction).
[0092] Conventional MAC procedures may assume when a MAC PDU is provided to the PHY layer it is transmitted. When LBT is performed this will not always be the case.Therefore, MAC procedures that refer to MAC PDU transmission should clarify a transmission considers LBT Success or Failure. This may be accomplished by referring to LBT Success within the MAC procedures or clarifying MAC PDU transmission criteria includes LBT Success.
[0093] MAC CE’s may be recovered and stored or the events that triggered these MAC CE’s are restored so when multiplexing and assembly of the MAC PDU is reperformed, triggering is reevaluated and reported values recalculated.NR-U LBT Effect on Specific MAC ProceduresThe LBT Operation Procedure
[0094] A new LBT MAC Procedure may be introduced. This procedure may be used to inform the NB of LBT failures or successes. As described herein, there may be multiple possible effects on UE MAC procedures. In many cases it may be necessary for the NB to know the effect on these MAC procedures for proper operation.
[0095] It is possible that each UE MAC procedure affected by LBT Failures signals the effect to the NB to maintain coordination between the UE and NB for the respective MAC procedure. But this may require additional complexity to be introduced to many MAC procedures.
[0096] An exemplary way is to define a new separate MAC procedure which indicates LBT State (e.g., Successes or Failures) to the NB so that the NB may take the LBT information into account and adjust its behavior relative to other MAC procedures by realizing the altered behavior of these procedures by LBT operation.
[0097] Therefore, UE PHY layer LBT Success or Failure indications may be provided to the MAC. It is possible the PHY layer does some pre-processing to limit the amount of primitives signaled between the MAC and PHY layers. The new LBT MAC procedure may consolidate these LBT indications and may generate a Listen Before Talk Report (LBTR) MAC control element (CE) which may provide information on LBT Failures or Successes over a period of time. In addition to LBT Success or Failure indications, the UE PHY layer may provide LBT timing information to the MAC layer. For example, LBT timing information may include CCA time periods, select MCOT or CWS periods.
[0098] The LBTR may provide UL and DL LBT failures separately. UL LBT failures may be unknown to the NB and need to be signaled to maintain MAC procedure coordination. But also DL LBT failures the UE is aware of may be useful to the NB since the NB may not be able to assume what DL LBT failures, that are signaled to the UE or otherwise detected by the UE, were realized by the UE. The UE may have missed or failed to receive NB DL LBT failure or success indications.
[0099] The LBTR procedure may require one or more triggers to initiate the procedure resulting in cases of transmitting the LBTR. The triggers may include one or more of the following ways. In a first way, LBT Failures reaching a threshold may be a trigger. There may be an RRC configured LBT Failure threshold. This threshold may be a threshold number of LBTFailures over a known time period or a threshold number of consecutive LBT Failures. These parameters may need to be configurable since the reporting urgency may be dependent of the type of traffic supported. In a second way, a trigger may be when certain effects on other MAC procedures results in a change of operation of that procedure which needs to be known by the NB for proper operation. For example, any change in DRX operation that effects Active Time or the DRX cycle. In this case the MAC DRX procedure triggers the LBTR. In a third way, a trigger may be based on RRC configured periodic LBTRs. In a fourth way, a trigger may be based on an LBTR Prohibit timer being introduced to limit LBTR frequency.
[00100] The LBTR procedure may count LBT Failures or Successes over a configured LBTR Monitoring Period. For example:If LBT Failure Count is greater than a configured LBT Failure Count within a LBTR Monitoring Period an LBTR may be triggered.If LBT Success Count is less than a configured LBT Success Minimum within a LBTR Monitoring Period an LBTR may be triggered.
[00101] The LBTR procedure may count consecutive LBT Failures or Successes over a configured LBTR Monitoring Period.- If consecutive LBT Failure Count is greater than a configured consecutive LBT Failure Count within a LBTR Monitoring Period, an LBTR is triggered.- If consecutive LBT Success Count is less than a configured consecutive LBT Success Minimum within a LBTR Monitoring Period, an LBTR is triggered.
[00102] When other MAC Procedures trigger an LBTR this may be by setting an LBTR Pending indication. The LBTR Pending indication is later checked during MAC PDU multiplexing assembly to see an LBTR MAC CE is to be built.
[00103] The LBTR may include the following information:Count of LBT Failures or Successes since the last LBTR- Number of times LBT Failures or consecutive LBT Failures have exceeded a maximum configured LBT Failure threshold since the last LBTR- Number of time LBT Success Count or consecutive LBT Success Count is less than a configured consecutive LBT Success Minimum since last LBTRIn addition to UL LBT failures DL LBT failures which have been detected by the UE may also be reportedThe MAC procedure that triggered the LBTRTime stamp related to when the LBTR PDU is built.CCA, MCOT or CWS information
[00104] It should be noted that similar operations may be provided by the PHY layer or RRC layer, and PHY layer or RRC layer signaling may be used to convey similar information to the NB.
[00105] RRC may configured into the UE, the priority of the channel access priority class mapped to the logical channel specified for LBTR MAC CE. Alternatively, the access priority class may be specified as the channel access priority class with the highest priority. The LBTR procedure may also comprise a general LBT State determination procedure, or an independent LBT State procedure may be utilized by the LBTR and other MAC procedures. This method would minimize complexity introduced to each MAC procedure. For example, rather than each MAC procedure counting LBT failures affecting the procedure an LBT State would just be checked.
[00106] Total number of LBT failures may be counted, which maybe within a specified or configured period of time. Alternatively, LBT FC’s may count consecutive LBT failures, and upon a LBT success the LBT FC is reset to zero. The period in which LBT failures may be counted may be sliding windows in time. When the LBT failure counter exceeds a specified or configured threshold the LBT State is considered failed. If a specified or configured number of LBT failures have not been received or a specified or configured number of LBT success indications are received the LBT State is considered successful. MAC procedures may check the LBT State rather than counting individual LBT failures associated with associated with the MAC procedure. MAC procedures may adjust counters and timers according to the LBT State. For example, MAC procedures may extend counters and timers, or consider timers and counters to have reached the maximum thresholds depending on the LBT State. The LBT State may also be indicated to higher layers. For example, to effect RRC procedures.BWP Operation Procedure
[00107] The following modifications to the BWP Operation procedure may take into account the effect of LBT operation in NR-U.
[00108] It is possible that LBT Failures results in blocking downlink assignments and uplink grants during a period of the BWP Inactivity Timer. In this case it may be inappropriate to perform BWP switching to the Default or Initial BWP(s).
[00109] If during the period the BWP Inactivity Timer is running LBT Failure(s) is determined the BWP Inactivity Timer associated with the active DL BWP should be extended. This, may be necessary to ensure BWP switching to the Default or Initial BWP is not performed when downlink assignments and uplink grants may be lost due to LBT Failure. BWP switching to the Default or Initial BWP should only be performed when there is really no data to be transmitted while the BWP Inactivity Timer is running. The examples herein may refer to the MAC specification 3GPP TS 38.321, (NR), Medium Access Control (MAC) protocol specification, V15.2.0 (herein also referred as [2]). Many of the exemplary modifications are underlined herein. For example, the MAC specification may be modified as follows:If the bwp-InactivityTimer is configured, the MAC entity shall for each activated Serving Cell: l> if the defaultDownlinkBWP is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP; orl> if the defaultDownlinkBWP is not configured, and the active DL BWP is not the initialDownlinkB WP :2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received for the active BWP; or2> if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment; or2> if LBT Failure has been detected on the active BWP:3> if there is no ongoing random access procedure associated with this Serving Cell; or3> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI (e.g., as specified with regard to subclauses 5.1.4 and 5.1.5 of [2]):4> start or restart the bwp-InactivityTimer associated with the active DL BWP.
[00110] The criteria may also be based on LBT Success detections while the BWP Inactivity is running. For example:If the bwp-InactivityTimer is configured, the MAC entity shall for each activated Serving Cell: l> if the defaultDownlinkBWP is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP; orl> if the defaultDownlinkBWP is not configured, and the active DL BWP is not the initialDownlinkB WP :2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received for the active BWP; or2> if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment; or2> if no LBT Success has been detected on the active BWP:3> if there is no ongoing random access procedure associated with this Serving Cell; or3> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI (e.g., as specified with regard to subclauses 5.1.4 and 5.1.5 of [2]):4> start or restart the bwp-InactivityTimer associated with the active DL BWP.
[00111] The LBT Failure may not be a single instance. It may be multiple LBT Failure or Success detections while the BWP Inactivity Timer is running. Also, as indicated herein, LBT Failure or Success is refers to both uplink LBT or downlink LBT.
[00112] A procedure may be defined to count LBT Failures or LBT Successes over a period of time, or to count consecutive LBT Failures or consecutive LBT Successes over a period of time. Only if LBT Failures or consecutive LBT Failure exceeding a configured Maximum LBT Failure Threshold or if LBT Successes or consecutive LBT Successes may be less than a configured Minimum LBT Success Threshold, is the BWP Inactivity Timer restarted. For example, the MAC specification may be modified as follows:If the bwp-InactivityTimer is configured, the MAC entity shall for each activated Serving Cell: l> if the defaultDownlinkBWP is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP; orl> if the defaultDownlinkBWP is not configured, and the active DL BWP is not the initialDownlinkB WP :2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or2> if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received for the active BWP; or2> if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment; or2> if LBT Failure Count has exceeded the LBT Failure Threshold on the active BWP:3> if there is no ongoing random access procedure associated with this Serving Cell; or3> if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI (e.g., as specified with regard to subclauses 5.1.4 and 5.1.5 of [2]):4> start or restart the bwp-InactivityTimer associated with the active DL BWP;4> reset the LBT Failure Count.
[00113] In the above procedures it should be noted that LBT Failure has been detected applies to the period while the BWP Inactivity Timer is running, the period from when a PDCCH for BWP switching is received on the active DL BWP, or PDCCH reception of an uplink grant on or for the active BWP, or a MAC PDU is transmitted or received for a configured grant, to the moment the BWP Inactivity Timer expires.
[00114] The BWP Inactivity Timer may be extended by a period different from the initial configured value. The period the BWP Inactivity Timer is extended may be another configured value or a value depending on the amount of detected LBT failures or successes determined.
[00115] LBT failures may also trigger switching between configured BWPs. The LBT Failure may not be a single instance. It may be multiple LBT Failure or Success detections within a specified or configured period of time. Also, as indicated herein, LBT Failure or Success may refer to uplink LBT or downlink LBT.
[00116] A procedure may be defined to count LBT Failures or LBT Successes over a period of time, or to count consecutive LBT Failures or consecutive LBT Successes over a period of time. Only if LBT Failures or consecutive LBT Failure exceeding a configured Maximum LBT Failure Threshold or if LBT Successes or consecutive LBT Successes are less than a configured Minimum LBT Success Threshold, is the Active BWP switched to an alternate configured Active BWP.
[00117] It is also may be necessary to avoid significantly extending the BPW Inactivity timer or even indefinitely extending the Inactivity timer due to LBT failures so that the UE never returns to the Initial or Default BWP. Restarting of the BWP Inactivity Timer then may be limited to a specified or configured maximum. For example, the MAC specification may be modified as follows:l> if BWP-Inactivitv-LBT-Failure-Count > BWP-Inactivity-LBT Failure Threshold on the active BWP: andl> if LBT-BWP-InactivitvRestartCount <= LBT-BWP-Inactivitv-Restart-Threshold:2> set the BWP-Inactivitv-LBT-Failure-Count to 0:2> increment LBT-BWP-InactivitvRestartCount by 1:2> start or restart the bwp-InactivityTimer associated with the active DL BWP.l> If LBT Failure has been detected:2> Increment BWP-Inactivity-LBT-Failure-Count.When the LBT BWP Inactivity Restart Threshold is exceeded the following actions mav be taken:l> if LBT-BWP-InactivitvRestartCount > LBT-BWP-Inactivitv-Restart-Threshold:2> BWP switching to the Default or Initial BWP is performed:2> An indication identifying the BWP is sent to higher layers:2> The SCell is deactivated:Random Access ProceduresRandom Access Response Reception
[00118] WThe following modifications to the Random Access Response Reception procedure may take into account the effect of LBT in NR-U.
[00119] If the RA Response Window expires but LBT Failures have been detected since the preamble transmission the RA Response Window may be be extended. This may be necessary since the NB may have received the preamble transmission, but the Random Access Response is delayed due to LBT Failure. When the UE detects the NB has missed transmission opportunities the RA Response window may be extended.
[00120] For example, the MAC specification may be modified as follows:l> if ra-Response Window configured in RACH-ConflgCommon expires, and if the Random Access Response containing Random Access Preamble identifiers that matches the transmitted PREAMBLE INDEX has not been received; orl> if ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if the PDCCH addressed to the C-RNTI has not been received:2> If LBT Failure has been detected:3> if the contention-free Random Access Preamble for beam failure recovery request was transmitted bv the MAC entity:4> restart the ra-ResponseWindow configured inBeamFailureRecoveryConfis .4> monitor the PDCCH of the SpCell for response to beam failure recovery request identified bv the C-RNTI while ra-ResponseWindow is running.3> else:4> restart the ra-ResponseWindow configured in RACH-ConfigCommon:4> monitor the PDCCH of the SnCell for Random Access Resnonsets) identified bv the RA-RNTI while the ra-ResponseWindow is running.2> else (LBT Failure not detected):3> consider the Random Access Response reception not successful;
Claims
What is Claimed:
1. An apparatus comprisinga processor; anda memory coupled with the processor, the memory storing executable instructions that when executed by the processor cause the processor to effectuate operations comprising:obtaining downlink information, wherein the downlink information is detected by a base station, wherein the downlink information is associated with channel access of the base station and comprises an indication of downlink listen-before-talk failure;obtaining uplink information, wherein the uplink information is detected by the apparatus, wherein the uplink information is associated with channel access of the apparatus and comprises an indication of uplink listen-before-talk failure; andbased on the indication of uplink listen-before-talk failure or the indication of downlink listen-before-talk failure, executing medium access control operations.
2. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a scheduling request procedure, switching to an alternate bandwidth part.
3. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a scheduling request procedure, initiating a random access procedure.
4. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a scheduling request procedure, maintaining a scheduling request pending state.
5. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a discontinuous reception procedure, extending an onDuration timer or Inactivity timer.
6. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a discontinuous reception procedure, aligning an onDuration timer or Inactivity timer to clear channel assessment, maximum channel occupancy time, or contention window size.
7. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a discontinuous reception procedure, applying a shorty cycle timer.
8. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a random access procedure, switching to an alternate bandwidth part.
9. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a random access procedure:providing a random access problem indication to higher layers; andindicating the random access procedure is unsuccessful.
10. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a listen-before-talk report procedure, providing a report comprising statistics of listen-before-talk failure or success.
11. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a listen-before-talk report procedure, setting a prohibit timer for setting frequency of reporting.
12. The apparatus of claim 1, wherein the executing of medium access control operations comprises for a bandwidth part procedure, extending a bandwidth part inactivity timer or switching to an alternate bandwidth part.
13. A method comprisingobtaining uplink information, wherein the uplink information is detected by an apparatus, wherein the uplink information is associated with channel access of the apparatus and comprises an indication of uplink listen-before-talk failure; and14. The method of claim 13, wherein the uplink listen-before-talk failure or the downlink listen-before-talk failure is detected by a scheduling request procedure, a buffer status reporting procedure, a logical channel prioritization procedure, a discontinuous reception procedure, a SCell activation or deactivation procedure, a power headroom reporting procedure, a random access procedure, listen-before-talk report procedure, or bandwidth part operations procedure.
15. A computer-readable storage medium having a computer program stored thereon, the computer program being loadable into a data-processing unit and adapted to cause the data-processing unit to execute method steps according to any one of claims 13 to 14 when the computer program is run by the data-processing unit.NR-U LBT MAC PROCEDURES
