NR-U LBT MAC Procedure

Abstract

The present invention provides an apparatus, method, and storage medium for implementing the NR-U LBT MAC procedure. [Solution] A method associated with an existing Media Access Control (MAC) procedure that helps maintain the proper operation and performance of the MAC procedure when a wireless transceiver unit (WTRU) is operating in an unlicensed frequency band, comprising: detecting one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures); extending a Bandwidth Portion (BWP) inactive timer based on the detected failures; and switching to an alternative Bandwidth Portion based on the detected failures.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 62 / 736,816, filed Sep. 26, 2018, entitled "NR - U LBT MAC Proc edures" and U.S. Provisional Patent Application No. 62 / 753,579, filed Oct. 31, 2018, entitled "NR - U LBT MAC Procedures", the contents of both applications are incorporated herein by reference.

Background Art

[0002] LTE Licensed - Assisted Access 3GPP Release 16 NR supports unlicensed operation without using the licensed - assisted connections available in previous releases. In previous releases, since there was always a licensed connection, there was no need to ensure a high level of QoS for unlicensed connections.

[0003] To operate unlicensed, a Listen Before Talk (LBT) procedure is necessary to obtain access to the channel without interfering with existing traffic.

[0004] A carrier aggregation having at least one SCell operating in an unlicensed frequency band is called Licensed - Assisted Access (LAA). Thus, in LAA, the set of serving cells configured for a UE operates in an unlicensed frequency band according to frame configuration type 3 and has at least one It always includes SCell, which is also called LAA SCell. Unless otherwise specified, LAA SCell functions as a regular SCell.

[0005] LAA eNB and UE listen before performing transmission in LAA SCell. Apply Fortalk (LBT). When LBT is applied, the transmitter listens on the channel. / Detects and determines whether the channel is free or busy. If specified, the transmitter may transmit; otherwise, it shall not transmit. LAA eNB uses channel access signals from other technologies for the purpose of LAA channel access. When using, 3GPP TS 36.321 (E-UTRA), media access control (Medium Access Control: MAC) protocol specification, V15.2.0[1] LAA The maximum energy detection threshold requirement will continue to be met. Further context is 3G. PP TS 36.321, (E-UTRA), Media Access Control (MAC) Protocol This specification may be included in V15.2.0. [Overview of the Initiative]

[0006] Maintaining proper operation and performance of MAC procedures, such as when operating in unlicensed frequency bands. Methods, apparatus, and systems associated with existing MAC procedures that may be possessed are described herein. This is disclosed. If an LBT failure occurs in NR-U, the existing MAC procedure is inappropriate. Taking the wrong action can lead to unintended consequences.

[0007] The outline of this invention is further described in the following simplified forms for carrying out the invention. It is provided to introduce the selection of concepts in a form. The summary of this invention is not intended to identify the main features or essential features of the subject matter, nor is it intended to be used to limit the scope of the subject matter recited in the claims. Furthermore, the subject matter recited in the claims is not restricted by any or all of the limitations that solve any disadvantages described in any part of this disclosure.

[0008] A more detailed understanding can be obtained from the following description given through examples related to the accompanying drawings.

Brief Description of the Drawings

[0009] [Figure 1] FIG. 1 shows an exemplary system for the NR-U LBT MAC procedure. [Figure 2] FIG. 2 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 3] FIG. 3 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 4] FIG. 4 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 5] FIG. 5 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 6] FIG. 6 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 7] FIG. 7 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 8] FIG. 8 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 9] FIG. 9 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 10]FIG. 10 shows an exemplary method associated with the NR-U LBT MAC procedure. [Figure 11] FIG. 11 shows an exemplary display (e.g., graphical user interface) that can be generated based on the method, system, and device of the NR-U LBT MAC procedure. [Figure 12A] FIG. 12A shows an exemplary communication system. [Figure 12B] FIG. 12B shows an exemplary system including a RAN and a core network. [Figure 12C] FIG. 12C shows an exemplary system including a RAN and a core network. [Figure 12D] FIG. 12D shows an exemplary system including a RAN and a core network. [Figure 12E] FIG. 12E shows another exemplary communication system. [Figure 12F] FIG. 12F is a block diagram of an exemplary apparatus or device such as a WTRU. [Figure 12G] FIG. 12G is a block diagram of an exemplary computing system.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] For example, when operating in an unlicensed frequency band, methods, apparatuses, and systems associated with the MAC procedure that help maintain the proper operation and performance of the MAC procedure are disclosed in this specification. When an LBT failure occurs in NR-U, existing MAC procedures may perform inappropriate actions and result in unintended consequences.

[0011]

[0011] Specific problems related to the MAC procedures addressed in this specification include, among other things, Bandwidth Part (BWP) operation procedures, random access procedures, power headroom Reporting (Power Headroom Reporting: PHR) procedure, Scell ​​activation or deactivation Activation procedure, intermittent reception procedure, scheduling request (SR) Procedures, buffer status reporting procedures, logical channel prioritization procedures, or UE and This may include issues related to the coordination of the Node B (NB) MAC procedure.

[0012] If a bandwidth partial operation procedure issue occurs and an LBT failure occurs, the bandwidth partial inactive Even if the current contract has expired and there is UL or DL ​​data to be scheduled, the initial or It may switch to a fault BWP.

[0013] If an LBT failure occurs due to a problem with the random access procedure, 1) Random access response Without allowing a sufficient number of submission opportunities (e.g., a threshold number) for the answer, random actions The response window may expire, and 2) In order to successfully send the preamble, Without allowing a sufficient number of preamble transmissions, the preamble transmission counter is the most The number of transmissions may reach a large number, and 3) there are enough PDCCH transmitters to respond to MSG3 transmissions. The conflict resolution timer may expire without allowing the meeting to proceed, or 4) Pre-an Even without a bull transmission, power ramping increases, resulting in inaccurate power settings. Sometimes.

[0014] If an LBT failure occurs due to a Power Headroom Reporting (PHR) procedure issue, 1) NB This means that it is not possible to determine when the PHR was calculated and what was transmitted at that time. This results in an inaccurate power headroom determination, and 2) PHR period timer, Reset, SCell activation, PSCell addition, or P due to the expiration of the prohibition timer. HR triggers may occur prematurely and 3) PHR calculations may not reflect actual transmissions. If this is the case, the power headroom may be calculated inaccurately, or 4) PHR Even if no transmission occurs, the PHR prohibition timer may be set.

[0015] In the SCell activation / deactivation procedure problem, if an LBT failure occurs, S If there is UL or DL ​​data to be scheduled on Cell, do not use SCell The SCell deactivation timer may expire when the system becomes active.

[0016] If an LBT failure occurs due to a problem with the intermittent reception procedure, the UL or should be scheduled. If there is DL data, PDCCH reception is stopped and the duration timer or The inactive timer may expire.

[0017] If an LBT failure occurs due to a problem with the scheduling request procedure, 1) Failed SR transmission The message does not initiate the random access procedure, and 2) even if no SR is sent, the SR ban is still valid. A setting may be made, and 3) a sufficient number of SR transmissions necessary to make SR transmission successful. Without allowing this, the SR transmission counter may reach the maximum number of transmissions, or 4) Even if no SR transmission occurs, the SR hold may be cleared.

[0018] If an LBT failure occurs due to a buffer status reporting procedure issue, UL-SCH resource If S is available, BSR may not be sent, and SR will not be triggered.

[0019] If an LBT failure occurs due to a problem with the logical channel prioritization procedure, MAC PD U may not be able to send in subsequent grants, resulting in user data and control systems being lost. Gunnering is lost.

[0020] If an LBT failure occurs due to a coordination issue between the MAC procedure of the UE and NB, the UE will appropriately Actions that achieve MAC procedures that need to be recognized by NB for a specific action This can happen. Furthermore, the NB may perform actions unrelated to the UE's behavior.

[0021] Considering the problems in the example above, avoid taking inappropriate actions and prevent unintended consequences. To that end, modify existing MAC procedures or create new MAC procedures that can account for LBT failures. Creation may exist. Below is an overview of how the problem can be addressed.

[0022] Figure 1 shows an exemplary system for the NR-U LBT MAC procedure. Step 1 In 11, UE101 has a channel access from base station 102 to UE101. The information is obtained. The information is downlink information signaled from base station 102. It is possible. In step 112, UE101 connects to the uplink channel of base station 102. Information regarding access (e.g., uplink information) can be detected. Uplink information This includes Listen-Before-Talk (LBT) operation or other operations (e.g., 3GPP TS). 36.213 (This can be detected by performing the operation in Section 15 of V14.8.0) In step 113, the information from step 111 or step 112 (for example, A MAC procedure operation can be achieved based on (uplink / downlink information). The order is as disclosed herein, in particular (e.g., PHR, BSR, BFD), L BTR121 (for example, Figure 10), DRX122 (for example, Figure 6), BWP operation 123 ( For example, Figure 2), or random access 124 (for example, Figure 3), scheduling required This may include Figure 125 (for example, Figure 7). In this specification, uplink or downlink It is intended that channel access information may be used in the steps described above.

[0023] Figures 2 to 10 show exemplary methods associated with the NR-U LBT MAC procedure. This is described in more detail herein.

[0024] Figure 2 shows an exemplary method for the Bandwidth Partial (BWP) operation procedure. For example, step In version 131, one or more LBT failures (e.g., uplink / downlink LBT failures) may occur. A threshold number of failures is detected. In step 132, the failures detected in step 131 Based on this, the BWP inactive timer can be extended. UL or DL ​​to be scheduled. Since data may exist, switching to the initial or default BWP can be avoided. The inactive timer can be extended. In step 133, detected in step 131 Based on the failure, it switches to an alternative bandwidth portion.

[0025] Figure 3 shows an exemplary method for a random access procedure. For example, step 141 In this case, one or more LBT failures (e.g., uplink / downlink LBT failure threshold) A value (number) is detected. Based on the failure detected in step 141, UE101 steps Steps 142, 143, 144, or 145 may be performed. In step 142, The random access response window can be extended. Step 142 is to extend the random access response window. A sufficient number of transmission opportunities may be allowed. In step 143, preamble transmission cow The input may not be incremented. Step 143 is successful in sending the preamble. A sufficient number of preamble transmissions may be allowed to occur. In step 144, conflict The resolution timer can be extended, which is when a sufficient number of PDCCH transmitters respond to the MSG3 transmission. The meeting may be permitted. In step 145, it may be possible to avoid increasing power ramping. This can help maintain appropriate power settings. In step 146, RA question The problem is presented to the higher levels, and the RA procedure may be considered unsuccessful. In step 147, Switching to an alternative bandwidth portion is possible. In this specification, steps 142 through 142 are used. It is intended that one or more of the 47 may occur based on step 141.

[0026] Figure 4 shows an exemplary method for a power headroom reporting procedure. For example, step In 151, one or more LBT failures (e.g., uplink / downlink LBT failures) A threshold number of failures is detected. Based on the failures detected in step 151, UE101 Steps 152, 153, 154, 155, 156, 157, or 158 may be performed. In step 152, UE101 tells base station 102 (for example) when the PHR has been calculated. If so, it can be shown in node B). In step 153, UE101 sends during PHR calculation The transmitted information can be shown to base station 102. In step 154, UE 101, LB When a T failure occurs, the base station 102 may be notified. In step 155, UE101 This may indicate to base station 102 that there was a delay in PHR transmission. In step 156 PHR period timer, reset, SCell activation, PSCell addition, or prohibition. PHR triggering may be delayed due to timer expiration. In step 157, the PHR meter The calculation may take into account lost or delayed transmissions. In step 158, PHR The prohibition timer may not be set, or it may be delayed.

[0027] Figure 5 shows an exemplary method for SCell activation / deactivation procedures. For example, in step 161, one or more LBT failures (e.g., uplink / downlink failures) The threshold number of link LBT failures is detected. Based on step 161, step 16 In step 2, the SCell deactivation timer may be extended, which means that on the SCell Additional UL or DL ​​data scheduling opportunities may be permitted.

[0028] Figure 6 shows an exemplary method for an intermittent reception procedure. For example, in step 171 , if one or more LBT failures (e.g., the threshold number of uplink / downlink LBT failures) Detected. Based on step 171, the duration or inactive timer This can be extended, which may allow for additional UL or DL ​​data scheduling opportunities. In step 173, the DRX short-cycle timer may be applied. Step 17 In 4, the duration or inactive timer is MCOT, CWS or It can be aligned with CCA. In step 175, the DRX setting can be adjusted. So, one or more of steps 172 through 175 are based on step 171. It is intended that this may occur.

[0029] Figure 7 shows an exemplary method for scheduling request procedures. For example, step 1 In 81, one or more LBT failures (e.g., uplink / downlink LBT failures) A threshold number of failures is detected. Based on the failures detected in step 181, UE101 Steps 182, 183, 184, or 185 may be performed. In step 182, The SM access response window may be initiated. In step 183, the SR ban time The timer may not be set, or the setting of the prohibit timer may be delayed. In step 184, The SR transmission counter allows a sufficient number of SR transmissions to be successful. Therefore, it may not be incremented. In step 185, SR hold is critical It may not be cleared, or the clearing of the SR hold may be delayed. In step 186, alternative band A switch to the bandwidth portion may occur. In this specification, steps 182 to 186 It is intended that one or more of these may occur based on step 181.

[0030] Figure 8 shows an exemplary method for a buffer status reporting procedure. For example, step In 191, one or more LBT failures (e.g., uplink / downlink LBT failures) A threshold number of failures is detected. Based on step 192, UL-SCH resources are available. Even if it's not a playable ability, SR can still be triggered.

[0031] Figure 9 shows an exemplary method for a logical channel prioritization procedure. For example, step In version 201, one or more LBT failures (e.g., uplink / downlink LBT failures) may occur. A threshold number of failures is detected. Based on the failures detected in step 201, UE101 Step 202 or 203 may be performed. In step 202, the MAC PDU is configured It may not be built. In step 203, the MAC PDU is reformatted. This can then be made available for transmission in subsequent grants.

[0032] Figure 10 shows how UE101 reports LBT failure or success information to base station 102. This illustrates an exemplary method, which improves coordination between UE101 and base station MAC procedures. This can be made possible. For example, in step 211, one or more LBT failures (e.g., up A threshold number of Plink / Downlink LBT failures is detected based on step 211. UE101 will report an LBT failure or indicate which steps are affected and how. The report may include LBT success / failure within the set period. Includes statistics. In step 214, the report includes timing information, CCA, MCOT, and or includes CWS. In step 215, the transmit disable timer minimizes the frequency of reporting. It is set to be so. In this specification, one of steps 212 to 215 The above is intended to be what can occur based on step 181.

[0033] Figures 2–10 show exemplary methods associated with the NR-U LBT MAC procedure. Several NR-U LBT MAC procedures are described in more detail below.

[0034] (Impact of NR-U LBT operation on MAC) The disclosed subject matter may apply to overall MAC operation and numerous specific MAC procedures. These MAC procedures involve Bandwidth Partial Operation (BWP) and Random Access (RAP). ss:RA), Power Headroom Report (PHR), SCell Activation and Deactivation Thriving, Logical Channel Prioritization (LCP), Discontinuous Reception (DRX), Scheduling Request (SR), Fast Status Report (Buffer Status Report: BSR), and in some cases, new L This may include BT MAC procedures, etc.

[0035] LBT failures could have unnecessary and unintended consequences for these MAC procedures. If there is a recognition of LBT failure or success, these MAC procedures do not require LBT. It can operate in the same manner and with the same performance as in the licensed frequency band. The steps that may be disclosed in the first MAC procedure (e.g., random access) (e.g., The action is applicable to the second MAC procedure (e.g., BWP operation). It is intended to be obtained. Therefore, the steps are generally limited to specific MAC procedures. I can't.

[0036] (General considerations regarding LBT failures in both UL and DL) Regarding the impact on MAC procedures, LBT failures should be considered in UL or DL. There is a MAC procedure and specific actions within the procedure that enable LBT for UL and DL. Both failures may be considered, or LBT failures may be UL only or DL ​​only. This may be considered. Furthermore, how LBT display is provided to Macs, and The information provided may vary depending on whether it's a UL (Urban Revision) or DL ​​(Digital Download).

[0037] In UL LBT operation, the PHY layer may indicate LBT success or failure to the MAC. The LBT success or failure indication may be associated with the UL transmission, or UL The LBT procedure may be performed independently of the UL transmission. Each UL LBT success or failure This display may be associated with one or more MAC procedures.

[0038] In DL LBT operation, the NB signals the UE whether DL LBT was successful or failed. The success or failure of the DL LBT may be associated with the DL transmission, and Alternatively, the DL LBT procedure may be performed independently of DL transmission. Each DL LBT success Alternatively, the failure indication may be associated with one or more MAC procedures.

[0039] Depending on the MAC procedure and the specific actions within the procedure, if there is no associated transmission This may also be necessary to perform LBT. The current MAC procedure requires constant access to the channel. This assumes that access exists and that there is no suspension or blocking of transmissions. This may be necessary. For example, if the UE assigns a downlink in the MAC procedure or If an uplink grant is not detected, transmit on the downlink or uplink. One possible assumption is that there is no data to schedule for. However, LBT The scheduled transmission is blocked or delayed due to a failure. Data may exist. In this case, the MAC procedure may result in unintended or undesirable outcomes. They may take actions that could lead to undesirable results.

[0040] In this disclosure, LBT failures or When success is mentioned, both uplink LBT and downlink LBT are considered. This is possible. MAC procedures and specific actions within those procedures can affect UL and DL LBT. Both failures are considered, or only LBT failures for UL or only for DL ​​are considered. ru.

[0041] It is not necessary to signal or indicate both LBT failure and success to the MAC. It should be noted that if there is no indication of LBT failure, it can be interpreted as success, and if there is an indication of success If it is not present, it may be interpreted as a failure. UL LBT indication from the PHY layer only indicates LBT failure. It can be shown that the DL LBT display from NB can only indicate LBT success.

[0042] The LBT success or failure indication may be provided periodically under known circumstances, or It may also be triggered by specific actions performed by MAC procedures. The success or failure of LBT may be periodically signaled by NB, UL LBT The success or failure of a particular MAC procedure may be indicated by the PHY layer depending on its behavior. Periodic displays may be augmented by on-demand displays driven by MAC procedures. Please note that the opposite is also true.

[0043] The indication of LBT success or failure may also relate to the behavior of a particular LBT procedure. Yes or display provides information about the operation of two or more LBT procedures over a known period of time. It may also be provided. The period may be the period since the last report. The UL LBT marking is special This can be caused by the operation of a specific LBT procedure, and the DL LBT display may appear multiple times over a certain period (e.g.) For example, it can provide information about LBT operation (threshold number).

[0044] The success or failure of the LBT is indicated by the carrier and BWP (singular) on which the LBT is performed. It may provide information regarding the success of uplink or downlink LBT. In addition to indicating failure, further LBT procedure information may be provided to the MAC procedure. AC procedures consider downlink and uplink transmission opportunities. For the C procedure to work correctly, transmissions must be possible on both the uplink and downlink. It may be necessary to recognize periods when it is possible or impossible to perform. In addition to, or included in, the indication of LBT success or failure, Clear Channel evaluation. The period of the Clear Channel Assessment (CCA), the selected maximum channel occupancy time. Maximum Channel Occupancy Time (MCOT), selected contention window. Contention Window Size (CWS) and other timing information are stored on the MAC. This will enable the proper determination of downlink and uplink transmission opportunities. Disclosed in the specification. MCOT, CWS, or other timings are selected. Channel Access Priority Class (CAPC) ) or it can be identified by another index.

[0045] (Displays Downlink LBT success / failure) To execute the DRX cycle, during the DRX duration of the UE, DL LB It has been discussed that the indication of success can be signaled from NB to UE. This is D The period during which the RX inactive timer is running, and, if applicable, the DRX active time. It should be extended to include all periods that constitute it. For example, UE is DRX on Demand A random access or scheduling request procedure is initiated while not within a simulation. In that case, LBT failure will be necessary for proper operation and performance, similar to when LBT is not required. Sometimes it's necessary to acknowledge defeat.

[0046] Furthermore, as a more comprehensive way to address this issue, we have a known regular method of contacting the UE. Considering the success of the DL LBT that is continuously transmitted, the actual outside of the DRX active time The MAC procedure being performed can benefit from the recognition of DL LBT success and failure. To make it.

[0047] The indication of DL LBT success may be a new explicit signal or implicitly detected. It may also be possible. For example, DL LBT success is implicitly determined by the reception of SSB or DRS. If a new explicit signal can be detected, it will be in the new DCI format (for example, if an individual UE is also It is either addressed to a group of UEs or broadcast to all UEs. It is possible that...

[0048] DRX duration is generally time-shifted for different UEs, so DL Even if LBT success is signaled periodically and continuously, it does not necessarily increase complexity. or resource usage does not increase. Overhead can be reduced.

[0049] Furthermore, the signaling DL LBT display is either UE-specific or DRX Ondule It should be noted that this may be specific to the group of UEs that share the same unit. Cell-specific DL LBT display enables more efficient use of resources, and more... This can result in consistent MAC procedure operation and performance.

[0050] Furthermore, an indication of LBT success does not necessarily have to be a single indication. The linked information may also provide information about the period since the last LBT success display. The signaled information is used by the NB to, for example, send DL channels to specific channels or BWPs. This can provide information about how much access Nell has. In this case, MAC address The sequence may have a continuous recognition of DL LBT success or failure over time, and thus This allows for a more accurate assessment of the impact of DL LBT failures on MAC procedures.

[0051] The indication of a successful downlink also allows MAC procedures to accurately determine the transmission opportunity. To that end, we need to identify when transmission is possible and when it is not. This can provide timing information for LBT success. To achieve this, the display of LBT success will include a click. A-channel assessment (CCA) period, selected maximum channel occupancy time (MCOT), selection The contention window size (CWS) or the appropriateness of downlink transmission opportunities. To enable precise timing, additional timing information is provided to the MAC, or or may be included. MCOT, CWS, or other timing information may be included in the selected timing. The channel access priority class (CAPC) or another index represents the access priority class. It can be identified.

[0052] (Displays whether uplink LBT was successful or unsuccessful) In addition to the NB indicating LBT failure or success status to the UE, the UE also indicates UL L BT failure or success information may be provided to NB.

[0053] As disclosed herein, there are several potential impacts on the UE MAC procedure. Obtain. The NB recognizes how LBT failure or success affected a specific MAC procedure. There may be several cases where this is necessary. For example, DRX active time Alternatively, if the DRX cycle is affected, the NB will ensure that the UE is properly scheduled. This must be recognized.

[0054] The LBT procedure may do more than just indicate UL LBT failures in NB. Other actions may be performed after an LBT failure occurs, as described herein. However, the operation of existing MAC procedures may be affected by LBT failures. The LBT procedure has the potential to perform new actions to resolve LBT failures. For example, channel access priority is adjusted to increase the likelihood of LBT success. obtain.

[0055] The total number of LBT failures may be counted, which is specified or set. It may be within the period. Alternatively, the LBT Failure Counters (FC) may be consecutive. You may count subsequent LBT failures and reset the LBT FC to zero upon LBT success. The period over which LBT failures can be counted may be a sliding window of time. If the LBT failure counter exceeds the specified or set threshold, the LBT status is It may be considered a failure if the specified or set number of LBT failures has not been exceeded. , or when a specified or set number of LBT success indicators are received, the LBT status is This can be considered a success. MAC procedures are associated with individual LBT failures. Instead of counting, the LBT status can be checked. In the MAC procedure, the LBT status The counters and timers can be adjusted accordingly. For example, the MAC procedure adjusts the counters and timers The timer and counter may be extended, or they may be deemed to have reached their maximum threshold depending on the LBT status. Obtain. The LBT state may also be shown at a higher layer. For example, it may affect the RRC procedure. El.

[0056] To provide information on the success or failure of UL LBT, a new MAC LBT report ( The LBT Report (LBTR) procedure may be defined. The LBTR MAC CE is a previous UL It may provide historical information regarding LBT results. This is in relation to when the report was generated. This can last for a specific period of time. For example, it may last for a period of time since the last LBTR MAC CE was sent. This could be during the period. MAC CE determines which MAC procedure(s) are affected. We may provide information about when or how the LBT failure occurred. NB can attempt to correlate which steps (one or more) were affected. LBTR MAC CE also fails, for example, when BWP LBT fails, and BWP The LBT result may include BWP information if LBT is successful. RRC is located within the UE. You may also set an LBTR reporting period.

[0057] Alternatively, UL physical control signaling provides an indication of UL LBT failure or success. This may be the case for scheduled or new UL signaling, PUC It can be transmitted via CH or piggybacked to PUSCH. Periodic UL signaling The lack of receiving the signal may be interpreted as a UE LBT failure. or it could be a new UL signaling. The new UL signaling is known to NB reception. It may need to be configured to occur using physical resources and at known times. .

[0058] The display of uplink LBT success and failure also indicates that the MAC procedure accurately determines the transmission opportunity. In order to enable this, when and how it is possible to send It can provide timing information to identify when it is not possible. To achieve this, LBT success Alternatively, in addition to or included in the display of failure, Clear Channel Assessment (CCA) Duration, selected maximum channel occupancy time (MCOT), selected contention win Dowsize (CWS) or other timing information is provided to the MAC, and uplink transmission It has been proposed that this will enable proper determination of trust opportunities. MCOT, CWS, or other The timing is represented by the Channel Access Priority Class (CAPC) which indicates the selected timing. Alternatively, it can be identified by another index.

[0059] (LBT's effect on MAC timers and counters) LBT failure may result in the loss of a transmission opportunity. Furthermore, the loss of a transmission opportunity may result in the transmission... This also leads to a longer time to achieve success. The MAC procedure declares the procedure has failed. Before doing so, consider the volume of transmission opportunities and the time it will take to complete them. MA if LBT is required. For procedure C to be executed correctly, the number of transmission opportunities and, in some cases, the procedure must be completed successfully. The timeframe for completion must take into account LBT failures.

[0060] In existing MAC procedures, when the MAC PDU is given to the PHY layer, or the PHY layer When a command is given to the PHY to transmit pin link control information (e.g., SR), Assume that PDU or PHY uplink control information is being transmitted. Specific MAC procedure When the MAC CE associated with it is constructed and multiplexed into the MAC PDU, this M It can be assumed that AC CE is sent. MAC C associated with a specific MAC procedure. To limit the frequency to which E or PHY uplink control information can be transmitted, MAC When the CE is built and the MAC PDU is given to the PHY layer, or when the PHY uplink When a command is given to the PHY to transmit control information, a prohibition timer may be set. The frequency at which MAC CE or PHY uplink control information may be transmitted is appropriately controlled. To ensure that it is sent when needed, these prohibition timer settings are also L We may consider the possibility of BT failure.

[0061] The sequence of MAC processing steps may also be considered. Existing steps are performed by the PHY layer. Before LBT is executed, when the MAC procedure is executed, the counter and timer are entered. It can be modified. Regarding the impact on existing MAC procedures, several methods can be considered, This may also be related to the following: 1) MAC indicates LBT failure from PHY layer counter 2) If the timer is adjusted to account for reception and transmission failures, then the timer will be adjusted if LBT is successful. If the counter is working, or 3) after the first MAC procedure is performed, or the most After being initially set, the counter(s) or timer(s)(s) LBT failures are recorded during the period before those maximum thresholds are reached.

[0062] When the MAC receives an LBT failure indication from the PHY layer counter, it will consider the transmission failure to be a factor. The counter and timer are adjusted. Increment when the MAC procedure is executed. The counter is decremented so that it does not change from what it was set before the procedure was performed. This can be commented out. This can be somewhat complicated in the case of a timer. Optimally, the maximum of the procedure The time should not take into account the duration of the LBT failure. MAC when the LBT failure occurs. The behavior of the timer depends on how the timer is used in different MAC procedures. There are several options, including: a) The MAC procedure associated with the LBT failure is performed. The timer is subtracted from the time when the MAC procedure is executed until the next opportunity to perform it, or if a) When an LBT failure is received, add to the maximum time threshold (when the timer expires), b) when an LBT failure is received. c) Stop the timer and restart it the next time you have a chance to perform the MAC procedure, receive LBT failure message. d) Restart the timer for the MAC procedure associated with the LBT failure. From the time you set it (at startup or restart) until the next time you set the MAC procedure timer The duration is either subtracted from the timer or added to the maximum time threshold (when the timer expires). (at that time).

[0063] One concern with this approach is the time when the MAC procedure was executed and the relationship between the MAC procedure and the MAC procedure. A linked LBT failure indicator counter (one or more) or timer (one or more) What happens when the interval between receiving and receiving reaches its maximum value? One way to address this problem is... The method involves the MAC responding to the previous transmission when the timer or counter reaches its maximum value. It checks whether it is waiting for the LBT display, and after it is determined that the LBT display was successful, This involves calling only the action associated with the expiration of a timer or counter.

[0064] If LBT is successful, the timers and counters will take effect. In this way, the MAC procedure When executed, counters (one or more) and timers (one or more) are activated. It cannot be done. The counter is incremented when LBT success is displayed, and the timer checks or Adjusted. One problem with this approach is that the timer or counter when LBT success is indicated. This occurs when the maximum threshold is reached, and the MAC procedure is executed differently. This means that. There are several options to deal with this situation. MAC procedure When performing the procedure, the timers and counters will be checked to ensure that the timers and counters follow the procedure during the procedure execution. If it was adjusted in that way, it could be checked whether or not those maximum thresholds had been reached, and this In this case, the MAC procedure would be as if the counter or timer had reached its maximum threshold. Action can be taken.

[0065] LBT failure occurs when the initial MAC procedure is performed or when it is first configured. , point counters (one or more) or timers (one or more) are used to determine their maximum The period until the threshold is reached can be recorded. When the timer or counter reaches the maximum threshold, The LBT failure record is checked, and if an LBT failure occurs, the procedure takes the LBT failure into consideration. Adjust the timers and counters. To achieve this, do (a) or (b) below. There may be several options, such as: (a) Action to be taken when the maximum threshold is reached. To prevent this from happening at this point, depending on the number of LBT failures or the duration of the LBT failures, The maximum thresholds for the ima and counter are adjusted, or (b) when the maximum threshold is reached, The number of failures and the duration of LBT failures are set so that the action to be performed is not executed at this point. The timers and counters are restarted accordingly.

[0066] LBT failures affecting timers and counters result in unacceptable delays (for example) If a threshold is reached, an error may occur, or the MAC procedure may stop indefinitely. The AC procedure counter and timer may never reach the maximum threshold. Therefore, open The proposed MAC procedure changes take into account the possibility of consecutive or substantial LBT failures. In this case, the MAC procedure will extend the maximum time so that each MAC procedure is executed properly. You may consider the maximum extension of the length or counter. For example, MAC procedure counter (MAC Pro Procedure Counter (MAC PC) and MAC Procedure Timer (MAC Procedure Timer: M Limiting the extension of AC PT can be addressed in the following ways: 1) MAC procedure LBT failure Loss Counter (LBT Failure Counter: LBT FC), MAC PC and MAC P T Extension Counter (EC), or MAC PC and MAC PT Extended Maximum Threshold (EMT).

[0067] MAC Procedure LBT Failure Counter (LBT FC): LBT FC is the total number of LBT failures. It may be counted, and this may be within a specified or set period. Or, L BT FC may count consecutive LBT failures, and if LBT is successful, LBT FC It is reset to zero. The LBT FC period is the time allowed until the MAC procedure is completed. It can be a sliding window of time or interval. In certain MAC procedures, there are two or more You may also use the LBT FC mentioned above. MAC procedures execute independent actions in parallel. In this case, each step may have an LBT FC. The LBT FC has a specified maximum value. It may be set to either or when the LBT FC reaches its maximum count, MA If the LBT fails in procedure C, MAC PC or MAC PT will no longer be extended. When the LBT FC reaches its maximum count, the MAC procedure will be performed on a MAC PC or MAC The action is performed as if PT has reached its maximum value. This causes the MAC procedure to fail. It could be considered that it did.

[0068] MAC PC and MAC PT Extended Counter (EC), LBT failure, MAC The maximum threshold for PC or MAC PT is extended. The criteria for the extension are specified or configured. This could be the number of LBT failures specified or set within the specified period. For example, MA There may be a maximum threshold for C PT. EC is the total number of MAC PC or MAC PT extensions. This may be counted, and this may be within a specified or set period. Alternatively, EC may count MAC PC or MAC PT extensions consecutively. The EC period is the time allowed for the MAC procedure to be completed, or a time sliding. It can be a window. Certain MAC procedures may use two or more ECs. MA If procedure C performs independent actions in parallel, each procedure may have an EC. It may have a specified or set maximum value. When the EC reaches the maximum count, If the MAC procedure LBT fails, the MAC PC or MAC PT will no longer be extended. Furthermore, when the EC reaches its maximum count, the MAC procedure will be on a MAC PC or MAC PT The action may be performed as if the maximum value had been reached. This can cause the MAC procedure to fail. It can be considered that...

[0069] MAC PC and MAC PT Extended Maximum Threshold (EMT), LBT failure, MAC The maximum threshold for PC or MAC PT may be extended. The maximum threshold is set at the time of each LBT failure, or within a specified or set period. The period may be extended when a set number of LBT failures occur. For example, the period is currently M There may be a maximum threshold for AC PT. The maximum threshold for MAC PC or MAC PT is... It may be extended after a set or configured number of consecutive LBT failures. MAC PC or M When AC PT reaches the specified or configured EMT, MAC PC or MA The maximum threshold for C PT may no longer be extended. This means that the MAC procedure may be considered to have failed. It is possible.

[0070] MAC procedures also have a timer used to control how often the procedure is executed. Good. These timers may be known as prohibit timers. Some MAC procedures When this is executed, the prohibition timer is set to the earliest time that the procedure is allowed to be executed again. Set these. MAC procedures currently set these timers when the procedure is executed. To address this, several methods or systems may be used. For example, 1) The prohibition timer does not need to be set when the procedure is executed, but is set upon LBT success or failure. It may or may not be set. Only upon successful LBT transmission associated with the MAC procedure. A prohibition timer should be set. The LBT procedure may take some time to succeed. In this case, the start of the prohibition timer may be delayed relative to when the MAC procedure is executed. This is necessary to ensure that the frequency with which MAC procedures are executed is appropriately limited. There is a possibility of this occurring. Alternatively, 2) The prohibition timer that may be set when executing a MAC procedure may be set during the MAC procedure. The LBT failure indication for the associated transmission is cleared when it is received. If transmission is delayed due to the sequence, the prohibition timer will be set until the MAC procedure is executed and LBT is successful. The time required to determine this may be extended to take into account.

[0071] (Loss of scheduling and transmission opportunities) MAC procedures may also consider downlink allocation and uplink granting. LBT failure results in the loss of downlink allocation and uplink grants. There is a possibility that if the NB determines that the LBT has failed, the PDCCH scheduling opportunity will be lost. Also, even though PDCCH scheduling is received, the UE loses LBT. If a loss is determined, the uplink transmission opportunity will be lost.

[0072] Within the set monitoring period, assign downlinks or grant uplinks. If reception is not possible, multiple MAC procedures will take action. LBT failure also LBT success does not mean that downlink allocation and uplink grant are not received. MAC procedure criteria may be considered. Success or failure of uplink or downlink LBT. In addition, further LBT procedure information may be provided to the MAC procedure. If the LBT is successful or In addition to or included in the indication of failure, the period of Clear Channel Assessment (CCA) Selected Maximum Channel Occupancy Time (MCOT), Selected Contention Window The CWS (Clockwise Speed ​​System) or other timing information is provided to the MAC, and downlink and This enables proper determination of opportunities to send a link. MCOT, CWS, or other timing The value represents the selected timing, either as a Channel Access Priority Class (CAPC) or another It can be identified by its index.

[0073] During the set monitoring period, downlink assignment or uplink grant If a signal cannot be received, if an LBT failure is detected, or if an LBT success is not detected, In such cases, multiple options may be considered. • If LBT success is not detected during the monitoring period, the MAC procedure will be used to perform an accident. The command may not be executed. • Within the monitoring period, the set minimum threshold for detecting LBT success or continuous LBT success is reached. If the MAC address cannot be reached, the action performed may not be executed. • If an LBT failure is detected during the monitoring period, the action taken by the MAC procedure will be implemented. It may not be done. • The set maximum threshold for LBT failure or consecutive LBT failures is reached within the monitoring period. In such cases, actions performed via MAC procedures may not be executed. • The number or duration of uplink or downlink transmission opportunities may be limited by CCA, MCOT, C This can be determined more accurately from WS or other timing information.

[0074] Actions that are not performed by MAC procedures are those that occur during the configured monitoring period. If an uplink allocation or uplink grant is not received, the currently designated These are actions that may have been performed by MAC procedures. For example, • If an LBT failure is detected while the BWP inactive timer is running, or if LBT is successful If no detection occurs, during this period, downlink assignment or uplink graduation will be performed. Even if no message is received, the BWP switch to the initial or default BWP will still be performed. It will not be carried out. • If a DRX Active Time LBT failure is detected during that time, or if LBT success is detected If not issued, downlink allocation or uplink grant will be issued during this period. Even if no signal is received, the DRX inactive status may be reset.

[0075] Even if uplink transmission is not possible due to LBT failure, the MAC procedure must be considered. It is possible. The impact on the MAC procedure is that the PDCCH scheduling opportunity is affected by the LBT failure. This is the same as in the case of loss. The MAC procedure is performed when the uplink grant is not received. Or if the uplink ground is not accepted for the data that can be transmitted (for example) (LCP restrictions) and UL transmission failures via LBT are the same as currently being performed. It can be considered that, for example, during the backoff period after an LBT failure, the MAC procedure is uplink If the grant is not received, or if an uplink grant is not sent for available data, If this is not accepted (e.g., LCP restrictions), it may behave as it does now.

[0076] In the traditional MAC procedure, when a MAC PDU is provided to the PHY layer, it is sent This can be assumed. However, this is not necessarily the case when performing LBT. Therefore, MA MAC procedures that refer to C PDU transmissions consider whether the transmission is LBT successful or failed. This should be made clear. This refers to the LBT success in the MAC procedure, or This is achieved by clarifying that the MAC PDU transmission criteria include LBT success. obtain.

[0077] When MAC PDU multiplexing and assembly are re-executed, the trigger is re-evaluated. MAC CE is recovered and saved so that the reported value is recalculated, or The events that triggered these MAC CEs can be recovered.

[0078] (The impact of NR-U LBT on specific MAC procedures) (The impact of NR-U LBT on specific MAC procedures) A new LBT MAC procedure may be introduced. This procedure will determine whether LBT fails or succeeds N It may be used to notify B. UE MAC procedure as described herein. There may be multiple possible effects on this. In many cases, NB is necessary for proper operation. It may be necessary to be aware of the impact on MAC procedures.

[0079] Each UE MAC procedure affected by an LBT failure will have a corresponding MAC procedure To maintain coordination between the UE and NB, it may be possible to signal the effects on the NB. However, this may require introducing further complexity to many MAC procedures.

[0080] An example method is for the NB to consider LBT information and modify these procedures by LBT operation. By achieving the specified behavior, it becomes possible to adjust its behavior in relation to other MAC procedures. To that end, a new separate MAC procedure to indicate the LBT status (e.g., success or failure) to the NB. The goal is to define it.

[0081] Therefore, if the LBT success or failure indication of the UE PHY layer is provided to the MAC, Yes. The PHY layer controls the amount of primitives that are signaled between the MAC layer and the PHY layer. To restrict the process, some preprocessing is possible. With the new LBT MAC procedure... This integrates these LBT displays and implements the Listen-Before-Talk Reporting (LBTR) MAC system. A Control Element (CE) can be generated, thereby preventing LBT failures for a certain period of time. This can provide information about success. In addition to LBT success or failure indication, the UE PHY layer provides information about success or failure. LBT timing information may be provided to the MAC layer. For example, LBT timing information This includes the CCA period, and the MCOT or CWS period can be selected.

[0082] LBTR may provide LBT failures for UL and DL separately. UL LBT failures are N This may be unknown to B, and signaling is used to maintain coordination of MAC procedures. It is necessary. However, DL LBT failures recognized by the UE may also be useful to the NB. It is possible because it could be signaled to the UE or detected by the UE in some other way. Is it possible that the NB might not assume that the DL LBT failure was caused by the UE? This is because the UE missed the NB DL LBT failure or success indication, or failed to receive the signal. There's a possibility they lost.

[0083] The LBTR procedure is one or more steps to initiate a procedure that leads to sending an LBTR. A trigger may be required. A trigger may include one or more of the following methods: 1. In this method, LBT failures that reach a threshold can be triggered. A failure threshold may exist. This threshold is the number of LBT failures over a known period, or consecutive failures. The threshold number for LBT failures may also be used. The urgency of the report is the number of supported traffics. These parameters may need to be configurable because they can be dependent on the IP address. In the second method, the trigger has some effect on other MAC procedures, but for proper operation. This may result in a change in the behavior of the procedure that needs to be recognized by the NB. For example, this is a change in DRX behavior that affects the active time or DRX cycle. In this case, the MAC DRX procedure triggers LBTR. In the third method, the trigger is RRC It can be based on the periodic LBTR set by. In the fourth method, the trigger is the frequency of the LBTR This is based on the LBTR prohibit timer that is introduced to limit it.

[0084] The LBTR procedure will check for LBT failures or successes over the configured LBTR monitoring period. It can be counted as a merit. For example, • During the LBTR monitoring period, the LBT failure count will be equal to the set LBT failure count. If it is greater than this, LBTR may be triggered. • During the LBTR monitoring period, if the LBT success count does not reach the set minimum LBT success value If the condition is met, LBTR may be triggered.

[0085] Over the configured LBTR monitoring period, the LBTR procedure will not attempt to resolve consecutive LBT failures. This can be counted as a success. • During the LBTR monitoring period, the consecutive LBT failure count will not match the set LBT failure count. If the value is greater than the threshold, LBTR may be triggered. • During the LBTR monitoring period, the consecutive LBT success count is set to the consecutive LBT success count. If the value is below the minimum, LBTR may be triggered.

[0086] If another MAC procedure triggers LBTR, this will set the LBTR pending display. This can be due to... The LBTR hold indicator will appear later during MAC PDU multiplexing assembly. It is checked and confirmed that the LBTR MAC CE is built.

[0087] LBTR may contain the following information: • Count of LBT failures or successes since the last LBTR • After the last LBTR, LBT failures or consecutive LBT failures will trigger the set limit of LBT failures. Number of times the threshold was exceeded • After the last LBTR, the LBT success count or consecutive LBT success count is set. The number of consecutive LBT successes less than the minimum value In addition to UL LBT failures, DL LBT failures detected by the UE are also reported. There is MAC procedure that triggered LBTR • A timestamp related to when the LBTR PDU was built. • CCA, MCOT, or CWS information

[0088] Similar operation may be provided by a PHY layer or an RRC layer, It should be noted that similar information may be transmitted to the NB using layer C signaling. .

[0089] RRC maps to the logical channel specified in LBTR MAC CE within the UE. You may set the priority of the channel access priority class. Alternatively, you can set the access priority You may also specify the previous class as the highest priority channel access priority class. The BTR procedure may also include a general LBT state determination procedure, or an independent LBT procedure. The state procedure may be utilized by LBTR and other MAC procedures. This method is used by each M Minimize the complexity introduced into AC procedures. For example, each MAC procedure affects the procedure. It doesn't count the number of LBT failures; it simply checks the LBT status.

[0090] The total number of LBT failures may be counted, which is specified or set. It may be within the period. Alternatively, LBT FC may count consecutive LBT failures, L If the BT is successful, the LBT FC is reset to zero. LBT failures can be counted. The period may be a sliding window of time. The LBT failure counter is specified. If the specified or set threshold is exceeded, the LBT status is considered to have failed. Or if the specified number of LBT failures are not received, or if the specified or set number If a certain number of LBT success indicators are received, the LBT status is considered successful. MAC The procedure counts individual LBT failures associated with MAC procedures, rather than LB The T state may be checked. In the MAC procedure, the counter and Timers can be adjusted. For example, a MAC procedure can extend the counter and timer, or L Depending on the BT state, the timer and counter may be considered to have reached the maximum threshold. The LBT state is It may also be shown to a higher level. For example, the RRC procedure is performed.

[0091] (BWP operation procedure) The following modifications to the BWP operation procedure, even taking into account the impact of LBT operation in NR-U, good.

[0092] Due to LBT failure, downlink allocation and BWP inactive timer period occurred. This may block the uplink grant. In this case, BWP will default or Switching to the initial BWP(s) (singular or plural) may be inappropriate.

[0093] If LBT failure is determined while the BWP inactive timer is running, The BWP inactive timer associated with a specific DL BWP should be extended. This means that downlink allocation and uplink grants are lost due to LBT failure. If this occurs, ensure that a BWP switch to the default or initial BWP is not performed. This may be necessary to do so. Switching to the default or initial BWP is The BWP non-activity timer only executes if there is no data to actually send during its execution. This should be done. The examples described herein are in accordance with MAC Specification 3GPP TS 38.3 21. (NR), Media Access Control (MAC) Protocol Specification, V15.2.0 You may refer to (and refer to herein as [2]). Many of the exemplary modifications are Underlined in this specification. For example, the MAC specification may be modified as follows: stomach. If bwp-InactivityTimer is set, the MAC entity For each activated serving cell, the following shall apply: 1> If the defaultDownlinkBWP is configured and the active DL BW P is not the BWP indicated by the defaultDownlinkBWP, or , 1> If the defaultDownlinkBWP is not configured and the active DL B WP is not the initialDownlinkBWP, 2> If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received on the active BWP, or, 2> If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received for the active BWP, or also is, 2> If a MAC PDU is transmitted with a configured uplink grant or received with a configured downlink assignment, or, 2> If an LBT failure is detected on the active BWP, 3> If there is no current random access procedure associated with this serving cell, or also is, 3> When this PDCCH addressed to the C-RNTI is received and the current random access procedure associated with this serving cell has completed successfully (e.g., as defined in Sections 5.1.4 and 5.1.5 of [2]), 4> Start or restart the bwp-InactivityTime r associated with the active DL BWP.

[0094] This criterion may also be based on detection of LBT success during BWP inactivity. For example, e.g., If the bwp-InactivityTimer is set, the MAC entity shall, for each active serving cell, do the following: 1. If the defaultDownlinkBWP is set and the active DL BW P is not the BWP indicated by the defaultDownlinkBWP, or 1. If the defaultDownlinkBWP is not set and the active DL B WP is not the initialDownlinkBWP, 2. If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink allocation or uplink grant is received on the active BWP, or 2. If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink allocation or uplink grant is received for the active BWP, or 2. If a MAC PDU is transmitted with a set uplink grant or received with a set downlink allocation, or 2. If no LBT success is detected on the active BWP, or 3. If there is no current random access procedure associated with this serving cell, or 3. If the current random access procedure associated with this serving cell has completed successfully upon reception of this PDCCH addressed to the C-RNTI (e.g., as specified in Sections 5.1.4 and 5.1.5 of [2]), 3. If there is no current random access procedure associated with this serving cell, or or 3. If the current random access procedure associated with this serving cell has completed successfully upon reception of this PDCCH addressed to the C-RNTI (e.g., as specified in Sections 5.1.4 and 5.1.5 of [2]), 4. Start or restart the bwp-InactivityTimer associated with the active DL BWP r .

[0095] LBT failures may not occur in a single instance. The BWP inactive timer may be... This may involve detecting multiple LBT failures or successes during execution. As such, LBT failure or success is determined by the uplink LBT or downlink LBT. Refer to both.

[0096] Count LBT failures or LBT successes over a certain period, or count consecutive LBTs over a certain period. You may define a procedure to count T failures or consecutive LBT successes. LBT failure Alternatively, if consecutive LBT failures exceed the configured maximum LBT failure threshold, or if LBT If success or consecutive LBT successes may be less than the set minimum LBT success threshold, The BWP inactive timer will be restarted. For example, modify the MAC specification as follows. You may do so. If bwp-InactivityTimer is set, MAC entity For each activated serving cell, the following shall apply: 1>defaultDownlinkBWP is set and the DL BWP is active. If P is not the BWP indicated by defaultDownlinkBWP, or , 1>defaultDownlinkBWP is not set and the active DL B If WP is not initialDownlinkBWP, 2> C-RNTI or indicating downlink allocation or uplink grant If a PDCCH addressed to CS-RNTI is received on an active BWP, or, 2> C-RNTI or indicating downlink allocation or uplink grant If a PDCCH addressed to CS-RNTI is received by an active BWP, when 2>the MAC PDU is transmitted with the configured uplink grant or received with the configured downlink allocation, or when 2>the LBT failure count exceeds the LBT failure threshold in the active BWP, 3>when there is no current random access procedure associated with this serving cell, or when 3>upon receiving this PDCCH addressed to the C-RNTI, when the current random access procedure associated with this serving cell has completed successfully (e.g., as defined in Sections 5.1.4 and 5.1.5 of [2]), then 4>start or restart the bwp-InactivityTime r associated with the active DL BWP to reset the LBT failure count.

[0097] In the above procedure, the detection of an LBT failure means that during the period when the BWP inactivity timer is running, when receiving a PDCCH for BWP switching on the active DL BWP, or when receiving a PDCCH on the active BWP or for the uplink grant of the BWP, or when transmitting or receiving a MAC PDU for the configured grant, it is applied during the period from the time of receiving the PDCCH until the BWP inactivity timer expires. It should be noted that

[0098] this applies. The BWP inactivity timer can be extended for a period different from the initial setting value. The period for which the BWP inactivity timer is extended can be a different setting value, or a value depending on the amount of detected LBT failures or determined successes.

[0099] ​​​​​Additionally, LBT failures can trigger a switch between configured BWPs. LBT failures may not occur in a single instance. Multiple LBT failures or successes within the interval may be detected. Also, as shown herein LBT failure or success refers to the uplink LBT or downlink LBT. It can happen.

[0100] Count LBT failures or LBT successes over a certain period, or count consecutive LBTs over a certain period. You may define a procedure to count T failures or consecutive LBT successes. LBT failure Alternatively, if the number of consecutive LBT failures exceeds the set maximum LBT failure threshold, or if LBT fails Only if the success rate or consecutive LBT success rate is below the set minimum LBT success threshold, The active BWP can be switched to another configured active BWP.

[0101] Also, to ensure that UE never reverts to its initial or default BWP, BPW deactivation Significantly extend the active timer, or indefinitely deactivate the inactive timer due to LBT failure. It may be necessary to avoid extending the period. In that case, BWP inactive time MAC restarts may be limited to a specified or configured maximum value. For example, MAC specifications You may also modify it as follows: 1> With an active BWP, BWP-Inactivity-LBT-Failure- Count>BWP-Inactivity-LBT Failure Thresho If it is ld, and, 1>LBT-BWP-InactivityRestartCount<=LBT-BW If it is P-Inactivity-Restart-Threshold, 2> Set BWP-Inactivity-LBT-Failure-Count to 0 hand, 2>Increment LBT-BWP-InactivityRestartCount by 1 Comment, 2> bwp-InactivityTime associated with active DL BWP Start or restart r. 1>If an LBT failure is detected, 2> Increment BWP-Inactivity-LBT-Failure-Count To do. If the LBT BWP inactive restart threshold is exceeded, even if the following actions are performed good. 1>LBT-BWP-InactivityRestartCount>LBT-BWP -If Inactivity-Restart-Threshold is active, 2> A BWP switch to the default or initial BWP is performed. 2> An indication that identifies the BWP is sent to the upper layer, 2>SCell is deactivated.

[0102] (Random access procedure) (Random access response received) The following modifications to the random access response receiving procedure take into account the impact of LBT in NR-U. You can put it in there.

[0103] Even if the RA response window has expired, if an LBT failure is detected after the preamble has been sent, In addition, the RA response window can be extended. This is because the NB has received the preamble transmission. This may also be necessary if random access responses are delayed due to LBT failure. When the UE detects that the transmission opportunity has been missed, the RA response window may be extended.

[0104] For example, the MAC specification could be modified as follows: 1>RA-ResponseWi configured in RACH-ConfigCommon The ndow has expired, and a random accessory matching the submitted PREAMBLE_INDEX has been added. If you have not received a random access response containing a spriamble identifier, 1>ra-Resp configured in BeamFailureRecoveryConfig If the onceWindow expires and a PDCCH addressed to C-RNTI is received If not, 2>If an LBT failure is detected, 3> Conflict-free random access for beam fault recovery requests by MAC entities If a preamble is sent, 4> ra-Respo configured in BeamFailureRecoveryConfig Restart nseWindow, 4>ra-ResponseWindow is identified by C-RNTI while it is running. The response to beam fault recovery requests is monitored by the PDCCH of the SpCell. 3> Otherwise, 4> ra-ResponseWind configured in RACH-ConfigCommon Restart OW, 4>ra-ResponseWindow is running, RA-RNTI SpCell's PDCCH for identified random access responses (one or more) Surveillance, 2> Otherwise (LBT failure will not be detected), 3> Assume that the random access response was not received successfully.

[0105] In the above procedure, LBT failure is detected when the RA response window has been activated. During this period, from the preamble transmission until the first RA response window after preamble transmission expires... The system restarts after the period up to that point, or when the RA conflict resolution timer expires due to LBT detection. From then until the next ra-ResponseWindow expires, it will be applied. This should be noted.

[0106] Alternatively, you could define a procedure to count LBT failures or LBT successes. If the number of LBT failures exceeds the configured maximum LBT failure threshold, or if the number of LBT successes exceeds the configured maximum LBT failure threshold, The RA response window is restarted only if it is below the minimum LBT success threshold. ru.

[0107] Alternatively, the RA response window is BeamFailureRecoveryConf Extend for a period different from the value set in ig or RACH-ConfigCommon. It is possible. The period during which the RA response window is extended may be a different setting, or The value may correspond to the amount of LBT failures detected or the amount of LBT success determined. LBT failures ensure that the UE never determines that the reception of the domain access response was unsuccessful. The random access response due to failure will be extended significantly, or extended indefinitely. There may be cases where it is necessary to avoid this. In that case, the restart of the RA response window will remain as specified. Alternatively, it may be limited to the set maximum value. For example, the MAC specification may be modified as follows: stomach. 1>RA-ResponseWindow-LBT-Failure-Count>RA -ResponseWindow-LBT-FailureThreshold Combined, and, 1>LBT-RA-ResponseWindowRestartCount<=LBT -RA-ResponseWindow-Restart-Threshold If, 2> Set RA-ResponseWindow-LBT-Failure-Count to 0 Set it up, 2> Set LBT-RA-ResponseWindowRestartCount to 1. Reduce, 2>ra - Start or restart ResponseWindow. 1>If an LBT failure is detected, 2> Add RA-ResponseWindow-LBT-Failure-Count Create. RA-ResponseWindow-LBT-FailureThreshold If it exceeds this limit, you may take the following actions. 1>LBT-RA-ResponseWindowRestartCount>LBT- If RA-ResponseWindow-Restart-Threshold is active , 2> Assume that the random access response was not received successfully.

[0108] Here is another example: If LBT fails, increment the preamble transmission counter. I have explained that it should not be done. For example, 1>RA-ResponseWi configured in RACH-ConfigCommon If the ndow expires, and a random access preamble matching the submitted entry is issued, If you have not received a random access response that includes Besshi, 1>ra-Resp configured in BeamFailureRecoveryConfig If the onceWindow expires and a PDCCH addressed to C-RNTI is received If not, 2> It is assumed that the random access response was not received successfully. 2>If no LBT failure is detected, 3> Increment PREAMBLE_TRANSMISSION_COUNTER by 1. Enter, 3>PREAMBLE_TRANSMISSION_COUNTER=preamble If TransMax+1 is used, 4>When a random access preamble is sent via SpCell, 5> Present the random access problem to the upper layers, 4>If this random access procedure is triggered in response to an SI request, 5> The random access procedure is considered to have failed. 3> Otherwise, if a random access preamble is sent in SCell, 4> The random access procedure is considered unsuccessful.

[0109] The preamble transmit counter may be decremented when an LBT failure is detected. For example. Ba, 1> In the physical layer, select PRACH, corresponding RA-RNTI (if available), P REAMBLE_INDEX and PREAMBLE_RECEIVED_TARG Use ET_POWER to instruct the system to send a random access preamble. , 1>If an LBT failure is detected, 2>Decrement PREAMBLE_TRANSMISSION_COUNTER by 1 To do.

[0110] In the above procedure, it should be noted that LBT failure may apply to preamble transmission. Therefore, LBT is used so that the UE does not determine that the random access response was not received successfully. Failure to significantly increment the preamble transmission counter, or preamble There should be an attempt to avoid indefinitely failing to increment the message transmission counter. In that case, the restart of the RA response window will be limited to the specified or set maximum value. It may be limited. For example, the MAC specification may be modified as follows: 1>RA-ResponseWi configured in RACH-ConfigCommon If the ndow expires, and if the submitted PREAMBLE_INDEX matches If you have not received a random access response that includes a random access preamble identifier, 1>ra-Resp configured in BeamFailureRecoveryConfig If the onceWindow expires and a PDCCH addressed to C-RNTI is received If not, 2> It is assumed that the random access response was not received successfully. 2>If no PreambleTransmissionLBT failure is detected, That is, 2>RA-PreambleTransmission-LBT-Failure-Co unt>RA-PreambleTransmission-LBT-FailureT If it is hreshold, 3> Increment PREAMBLE_TRANSMISSION_COUNTER by 1. Enter, 3>PREAMBLE_TRANSMISSION_COUNTER=preamble If TransMax+1 is used, 4>When a random access preamble is sent via SpCell, 5> Show the problem of random access in the upper layers, 4>If this random access procedure is triggered in response to an SI request, 5> The random access procedure is considered to have failed. 3> Otherwise, if a random access preamble is sent in SCell, 4> The random access procedure is considered unsuccessful. 1>PreambleTransmission-LBT-Failure detected case, 2>RA-PreambleTransmission-LBT-Failure-Co Increment unt.

[0111] RA-PreambleTransmission-LBT-FailureThre If the threshold is exceeded, the following actions may be taken: 1) Randomly add to the upper layer This indicates an access problem, or 2) the random access procedure is considered to have failed.

[0112] Alternatively, the MAC specification can be modified as follows: 1>PreambleTransmission-LBT-Failure detected case, 2>RA-PreambleTransmission-LBT-Failure-Co Increment unt, 2>RA-PreambleTransmission-LBT-Failure-Co unt>RA-PreambleTransmission-LBT-FailureT If it is hreshold, 3> If a random access preamble is sent via SpCell, 4> Show the problem of random access in the upper layers, 3>If this random access procedure is triggered in response to an SI request, 4> The random access procedure is considered to have failed. 3> Otherwise, if a random access preamble is sent in SCell, 4> The random access procedure is considered unsuccessful.

[0113] (Conflict resolution) The following modifications to the random access race resolution procedure take into account the impact of LBT in NR-U. You can put it in there.

[0114] Even if RA conflict resolution is completed, if an LBT failure is detected after preamble transmission, R A conflict resolution may be extended. This means that even if the NB receives the MSG3 transmission, the LBT will fail. This may be necessary due to further delays in PDCCH transmission. NB transmits due to LBT failure. If the UE detects that an opportunity has been missed, it may extend the RA conflict resolution timer.

[0115] For example, the MAC specification could be modified as follows: 1>When ra-ContentionResolutionTimer expires, 2>If an LBT failure is detected, 3> Start ra-ContentionResolutionTimer and restart HARQ Restart ra-ContentionResolutionTimer after each transmission. 3> Regardless of the possibility of measurement gaps occurring, ra-ContentionResolu While tionTimer is running, it monitors PDCCH, 2> Otherwise, 3>Discard TEMPORARY_C-RNTI, 3> The competitive resolution was deemed unsuccessful.

[0116] In the above procedure, LBT failure is detected when the RA conflict resolution timer is running. During this period, from the transmission of MSG3 until the first time the RA conflict resolution timer expires after the transmission of MSG3. During that period, or after the RA conflict resolution timer expires due to LBT detection and is last activated, It should be noted that this applies to the period until the next RA conflict resolution timer expires.

[0117] Alternatively, you could define a procedure to count LBT failures or LBT successes. If the number of LBT failures exceeds the configured maximum LBT failure threshold, or if the number of LBT successes exceeds the configured maximum LBT failure threshold, RA conflict resolution is restarted only if it is possible that the result is below the minimum LBT success threshold.

[0118] Alternatively, the RA conflict resolution timer may only be set for a period different from the configured RA conflict resolution timer. It may be extended. The period for which the RA conflict resolution timer is extended may be set to a different value. Alternatively, it may be a value corresponding to the number of LBT failures detected or the number of determined successes. Furthermore, to ensure that UE never determines that the conflict resolution was unsuccessful, RA conflict resolution times Significantly extend the timer, or extend the RA conflict resolution timer indefinitely due to LBT failure. There are times when it is necessary to avoid this. In that case, restarting the RA conflict resolution timer is necessary. It may be limited to a defined or set maximum value. For example, the MAC specification may be modified as follows. You can correct it. 1>RA-ContentionResolution-LBT-Failure-Co unt>RA-ContentionResolution-LBT-FailureT If it is an hreshold, and 1>LBT-RA-ContentionResolutionTimerRestar tCount<=LBT-RAContentionResolutionRestar If it is a t-threshold, 2>RA-ContentionResolution-LBT-Failure-Co Set unt to 0, 2>LBT-RA-ContentionResolutionTimerRestar Increment tCount by 1, 2> Start ra-ContentionResolutionTimer and restart HARQ Restart ra-ContentionResolutionTimer after each transmission. 2> Regardless of the possibility of measurement gaps occurring, ra-ContentionResolu While tionTimer is running, monitor PDCCH. 1>If an LBT failure is detected, 2>RA-ContentionResolution-LBT-Failure-Co Increment unt. RA-ContentionResolution-LBTRestartThres If the hold limit is exceeded, you may perform the following actions. 1>LBT-RA-ContentionResolutionTimerRestar tCount>LBT-RA-ContentionResolutionRestar If it is a t-threshold, 2> Assume that the random access response was not received successfully.

[0119] (Send random access preamble) The following modifications to the Random Access Preamble Transmission Procedure are due to the LBT in NR-U Take the sound into consideration.

[0120] If LBT fails, increment the preamble power ramping counter. I have explained that it is not that. For example, The MAC entity for each random access preamble is as follows: do. 1> When PREAMBLE_TRANSMISSION_COUNTER is greater than 1 Combined, and, 1> If you have not received notification from a lower layer that the power ramping counter has been paused, Beauty, 1> If the selected SSB has not changed (i.e., the previous random access program (Same as sending an amble), and 1>If no LBT failure is detected, 2> Increment PREAMBLE_POWER_RAMPING_COUNTER by 1 Comment.

[0121] The preamble power ramping counter is decremented when an LBT failure is detected. That's also fine. For example, 1> In the physical layer, select PRACH, corresponding RA-RNTI (if available), P REAMBLE_INDEX and PREAMBLE_RECEIVED_TARGE Use T_POWER to instruct the system to send a random access preamble. 2>If an LBT failure is detected, 2> Decrease PREAMBLE_POWER_RAMPING_COUNTER by 1 To do.

[0122] In the above procedure, it should be noted that LBT failure may apply to preamble transmission. That is the case.

[0123] (Power headroom report) The following modifications to the PHR procedure take into account the impact of LBT in NR-U.

[0124] The PHR MAC CE transmission was blocked due to an LBT failure and will be retransmitted after a delay. If so, to notify the NB when the PHR is calculated, or when the PHR has been calculated Additional signaling will be introduced to notify the NB of the transmission conditions.

[0125] For NB to process PHRs properly, it needs to know the conditions under which the PHRs were calculated. NB may need to recognize this in some cases.

[0126] PHR has a rated UE maximum transmit power and UL- per activated serving cell. Regarding the difference between the estimated power of SCH transmission or SRS transmission, and the rated UE maximum power, UL-SCH and PUCCH transmission on SpCell and PUCCH SCell The calculation also uses information about the difference from the constant power.

[0127] Existing PHR signaling is based on whether UL-SCH transmission is actual or virtual transmission. Determine whether or not a PUCCH was sent when the PHR was calculated. If UL-SCH is an actual transmission, the NB will determine what was transmitted when calculating the PHR. It may be necessary to recognize it.

[0128] If it is not operating in an unlicensed frequency band and LBT is not being used, NB is P It is possible to determine when the HR calculation was performed. NB is determined by whether it was scheduled or received. Because it is recognized that, at this point it is possible to recognize what was transmitted via UL-SCH. HR can be interpreted. However, LBT fails, and transmission is delayed until LBT succeeds. If delayed, the NB will determine what was transmitted via UL-SCCH when calculating the PHR. It's not possible.

[0129] The following are several methods for addressing this problem. The first method involves calculating the PHR. This provides the PHR with additional information so that the NB can determine when it was performed. This could be the delay caused by LBT relative to the time of the first LBT failure, or it could be based on absolute time. Alternatively, the second method involves notifying the NB of what was transmitted via UL-SCCH. Additional information is provided along with the PHR. This approximates what was transmitted on UL-SCCH. It may be an indexed value, or the physical details of the transmission at the time of PHR calculation. It may be. In the third method, the effective delay incurred by LBT for PHR is compensated by NB. The failure or success of the LBT may be shown independently to the NB so that it can be determined. (Fourth) The law stipulates that the grant used when the PHR was calculated (e.g., uplink grant) Provide additional information along with the PHR to notify the NB of the following:

[0130] The NB receives additional information that allows it to understand how the PHR was calculated. It is preferable to do so, but it is not absolutely necessary. Alternatively, if the actual PHR is fraudulent... If accurate information is provided, the NB can at least recognize it. This means that the UE can inform the NB of the LB. By indicating T failure and success, the NB determines that there was an LBT failure that delayed the PHR. It can be achieved by making it possible.

[0131] Another example is shown below. The trigger condition for PHR should take LBT failure into consideration. Available Available UL resources, PHR period timer expiration, PHR reset, SCell activation; The PSCell additional trigger criteria should only be considered if LBT is successful. Yes. The addition of LBT criteria is mutually exclusive for each existing trigger, and therefore, It may only affect a subset of existing standards.

[0132] For example (considering all triggers), the MAC specification may be modified as follows: . If any of the following events occur, the Power Headroom Report (PHR) will It is assumed that this will be triggered. • When phr-ProhibitTimer expires, or expires, MAC entity T has a UL resource for a new transmission, but this transmission is blocked by an LBT failure. When not, the passcode has been used in this MAC entity since the last transmission of the PHR. At least one activated MAC entity used as a reference to For the serving cell, the path loss is phr-Tx-PowerFactorChang The change exceeded e dB. Note 1: The path loss variation of one cell evaluated above is currently based on the current path loss reference. The measured path loss and the path loss reference used at the time of the last transmission of the PHR This is between the measured path loss and the current path loss, and whether the path loss reference changed during that time is not relevant. It's irrelevant. • The phr-PeriodicTimer expires, and then LBT succeeds. • When the power headroom reporting function is configured or reset by the upper layer, LBT subsequently It is effective and not used to disable its functionality. • Activate the SCell of the MAC entity that has configured uplinks. LBT subsequently became successful. • Addition of PSCell (i.e., when a new PSCell is added or modified), And LBT succeeds thereafter, • phr-ProhibitTimer expires, or expires and MAC entity If the user has UL resources for a new transmission, and this transmission is blocked by an LBT failure... Not activated, and the activation of any MAC entity with configured uplinks For any of the converted serving cells, the following applies: • Is a UL resource allocated for sending to this cell, or is it a PUCCH send? There is a power management for this cell (as specified in TS38.101

[10] ) The required power backoff (allowed by P-MPRc) is at the end of the PHR. After transmission, the MAC entity is allocated a UL resource for transmission to this cell. When phr-Tx-PowerFacto was active or when a PUCCH transmission occurred, The change exceeded rChange dB.

[0133] These changes mean that PHR is calculated when LBT is successful and UE accesses the channel. Or it may be necessary to ensure that it is sent.

[0134] Another example is shown below. PHR calculation and transmission are only considered if LBT is successful. It should be done.

[0135] Rated UE maximum transmit power and UL-SCH transmit power per activated serving cell Or the difference with the estimated power of SRS transmission, and the rated UE maximum power and SpCel l and estimated power of UL-SCH and PUCCH transmission on PUCCH SCell Calculations using information about the difference should only be considered if the LBT is successful.

[0136] When checking whether a UL resource is compatible with PHR MAC CE, LBT It may also be necessary to determine success. Having available UL resources is PHR This is unrelated to MAC CE transmissions being blocked by LBT.

[0137] For example, the MAC specification could be modified as follows: A MAC entity has an UL resource allocated for a new transmission, LBT If it is determined to be successful, the MAC entity will 1> The first UL resource allocated for new transmissions since the last MAC reset If that is the case, 2>Start phr-PeriodicTimer, 1> The power headroom reporting procedure triggers at least one PHR, and can If it is determined that it is not a cell, and, 1>Assigned UL resources are prioritized by the MAC Enterprise as a result of logical channel prioritization. MAC CE for PHR configured to be transmitted by the device, and its subheader If applicable, and 1> The LBT was determined to be successful. 2>If multiplePHR is set, 3> Each MAC entity has a configured uplink associated with it. For activated serving cells, 4> Type 1 or Type 3 power head rope for the corresponding uplink carrier Get the value of the element, 4> This MAC entity is assigned to send in this serving cell. If you have L resources and LBT is determined to be successful, or 4> The other MAC entity (if configured) is assigned for transmission. Having UL resources, and determining LBT success in this serving cell, the higher layer performs phr -ModeOtherCG is set to a real number, 5> From the physical layer to the corresponding P CMAX,f,c Field Boy acquired and asked 3>If phr-Type2SpCell is set, 4> The value of Type 2 power headroom for the SpCell of this MAC entity. Obtain, 4> From the physical layer to the corresponding P CMAX,f,c Field Boy acquired and asked 3>If phr-Type2OtherCell is set, 4>If other CGs are set, 5> The value of Type 2 power headroom for the SpCell of the other MAC entity. Obtain, 5>If phr-ModeOtherCG is set to a real number by the upper layer, 6> The corresponding P from the physical layer to the SpCell of the other MAC entity. CMAX, f,c Field Boy acquired and asked 4> Otherwise, if PUCCH SCell is set and activated, 5>Get the Type 2 power headroom value for PUCCH SCell 5> From the physical layer to the corresponding P CMAX,f,c Field Boy acquired and asked 3>If LBT is determined to be successful, based on the values ​​reported from the physical layer, see [2] 6.1 As defined in Section 3.9, the configured ServCellIndex and MA PHR MAC CE is generated according to the PUCCH (singular or plural) of the C entity. The multiplexing and assembly procedures are instructed to call and transmit, 2> Otherwise (i.e., the single-entry PHR format is used), 3> From the physical layer of the corresponding uplink carrier of the PCell to the Type 1 power head route Get the value of the element, 3> From the physical layer to the corresponding P CMAX,f,c Get the field value. 3>If LBT is determined to be successful, based on the values ​​reported from the physical layer, see [2] 6.1 As defined in Section 3.8, generate and transmit PHR MAC CE To provide instructions for the multiplexing and assembly procedures, 2> Start or restart phr-PeriodicTimer, 2> Start or restart phr-ProhibitTimer, 2> Cancel all triggered PHRs (single or multiple).

[0138] The above example MAC-specific changes are described from the perspective of LBT success, but the example is L This can also be expressed similarly from the perspective of having no BT failures. In this example, it should be noted that the changes are mutually exclusive. Subsequent changes of the disclosed changes Sometimes only the kit is needed.

[0139] Another example is shown below. Furthermore, when detecting LBT failures in transmissions including MAC PHR CE A PHR prohibition timer should not be set, or if one is set, it should be cleared. It has been disclosed that this should be the case.

[0140] If the physical layer is instructed to send a MAC PDU containing a MAC PHR CE, then the PHR The prohibition timer is only activated or restarted when the success of the MAC PDU transmission is determined. It should be done. For example, the MAC specification may be modified as follows: 1>If LBT is determined to be successful, 2> Start or restart phr-PeriodicTimer, 2> Start or restart phr-ProhibitTimer, 2> Cancel all triggered PHRs (single or multiple).

[0141] The above example MAC-specific changes are described from the perspective of LBT success, but the example is L It may also be expressed from the perspective of having no BT failures.

[0142] Alternatively, the PHR disable timer or PHR cycle timer may be handled in the existing procedure. It may be started, but if LBT is determined to have failed, the PHR prohibition timer will be cleared. Alternatively, the PHR period timer may be set to the remaining value before the last reset due to an LBT failure. Alternatively, you can reset it to a different time value, such as a pre-set time value.

[0143] This fix prevents the PHR ban timer from being set so that subsequent PHR transmissions are not delayed. Either do this, or periodically when PHR transmission is blocked by LBT failure To prevent delays in the PHR, ensure that the PHR cycle timer is not reset. It may be necessary to make it a reality.

[0144] (Activating / Deactivating SCell) The following modifications to the SCell activation / deactivation procedure are in L in NR-U. Take the effects of BT into consideration.

[0145] If an LBT failure is detected while the SCell deactivation timer is running, The deactivation timer is extended. This prevents unintended SCell deactivation. It may be necessary to avoid it.

[0146] Due to the LBT failure, the NB missed the opportunity to send a DL (downlink assignment (singular) (or multiple) data may be lost, or UL transmission may be blocked (MAC PDU If the UE detects that a message is not being sent, the SCell deactivation timer is extended. .

[0147] There may be multiple options for achieving this. • When an LBT failure is detected, the SCell deactivation timer is extended or restarted. • If an LBT failure is detected when the SCell deactivation timer expires, The deactivation timer is extended or restarted.

[0148] It should be noted that LBT failure can sometimes mean a lack of LBT success. For example, the UE PHY layer may indicate an LBT failure to the UE MAC, or the NB may indicate an UE MAC may sometimes indicate LBT success.

[0149] For example, the MAC specification could be modified as follows: 1> Otherwise, deactivate SCell, SCell Activate / Deactivate If a tidied MAC CE is received, or, 1> sCellDeactivation associated with activated SCells If nTimer expires and no LBT failure is detected, 2> According to the timing defined in TS 38.213, deactivate SCell Transformed into, 2>Stop the sCellDeactivationTimer associated with SCell. do, 2>Stop the bwp-InactivityTimer associated with SCell, 2> Any configured downlink assignment associated with SCell, and any Clear each of the Type 2 uplink grants that have been set up, 2>Type 1 of any configured uplink grant associated with SCell Pause, 2>Flush all HARQ buffers associated with SCell. 1> sCellDeactivation associated with activated SCells If nTimer expires and an LBT failure is detected, 2> Restart the sCellDeactivationTimer associated with the SCell. To move.

[0150] In the above procedure (one or more), the detection of an LBT failure means that SCell failure During the period the activation timer is running, SCell deactivation or setting From the time the last MAC PDU was sent on the uplink grant, or from the time the setting Since the UE last received a specified downlink assignment, SCell inactive The period from when the bleed timer is set until the first time it expires, or when LBT detection occurs. The cell deactivation timer expires and the cell is last activated, and the next SCell deactivation timer... It should be noted that this applies to the period until the activation timer expires.

[0151] Alternatively, when SCell detects an LBT failure, 1>If an LBT failure is detected, 2> Restart the sCellDeactivationTimer associated with the SCell. To move.

[0152] Alternatively, LBT failure or LBT success, or consecutive LBT failures or consecutive LBT You may define a procedure to count successes. If LBT fails or consecutive LBT fails If the set maximum LBT failure threshold is exceeded, or if LBT is successful or continuous LBT is not achieved, SCell inactivation occurs only if the success rate is below the set minimum LBT success threshold. The bleed timer will be restarted. For example, the MAC specification may be modified as follows: 1>ScellDeactLBT-Failure-Count>ScellDeact If it is LBT-Failure-Threshold, 2> Restart the sCellDeactivationTimer associated with the SCell. Move, 2>Set ScellDeactLBT-Failure-Count to 0. 1>If LBT fails, 2>Increment ScellDeactLBT-Failure-Count.

[0153] Alternatively, the SCell deactivation timer is set to deactivate the SCell. The timer may be extended for a different period. The SCell deactivation timer is extended. The period may be set to a different value, or the LBT failure or determination may be detected. The value may be based on the amount of success. Also, ensure that the UE is never deactivated. , significantly extending the SCell deactivation timer, or SC due to LBT failure There are times when it is necessary to avoid extending the ell inactive timer indefinitely. In this case, the SCell deactivation timer restart will occur at the specified or set maximum The values ​​may be restricted. For example, the MAC specification may be modified as follows: 1>ScellDeact-LBT-Failure-Count>ScellDeact If it is t-LBT-FailureThreshold, and, 1>LBT-ScellDeactTimerRestartCount<=LBT-S If it is cellDeact-Restart-Threshold, 2>Set ScellDeact-LBT-Failure-Count to 0, 2> Ink LBT-ScellDeactTimerRestartCount by 1 Rement, 2> Restart the sCellDeactivationTimer associated with the SCell. To move. 1>If an LBT failure is detected, 2>Increment ScellDeact-LBT-Failure-Count .

[0154] If the ScellDeact-LBT-FailureThreshold is exceeded, You may perform the following actions. 1>LBT-ScellDeactTimerRestartCount<=LBT-S If it is cellDeact-Restart-Threshold, 2>Deactivate SCell according to the timing defined in TS38.213[6] By making it interactive, 2>Stop the sCellDeactivationTimer associated with SCell. do, 2>Stop the bwp-InactivityTimer associated with SCell, 2> Any configured downlink assignment associated with SCell, and any Clear each of the Type 2 uplink grants that have been set up, 2>Type 1 of any configured uplink grant associated with SCell Pause, 2>Flush all HARQ buffers associated with SCell.

[0155] (Intermittent reception (DRX)) The following modifications to the DRX procedure take into account the impact of LBT in NR-U.

[0156] When the short cycle timer expires, the short DRX cycle is replaced by a long DRX cycle. The cycle may transition. This transition occurs if LBT success is detected, or LBT It should only be executed if no failure is detected. For example, 1>When drx-ShortCycleTimer expires and LBT success is detected, 1> Use a long DRX cycle, 1> Otherwise, 2> Start or restart drx-ShortCycleTimer.

[0157] This specification discloses the setting thresholds for maximum LBT failure or minimum LBT success. The UE will only proceed to DRX if the LBT failure or LBT success count exceeds the threshold. Short cycles can continue to be used. For example, 1>drx-ShortCycleTimer expires and the LBT success counter reaches minimum LB If the T success threshold is exceeded, 2> Use a long DRX cycle, 2> Otherwise, 2> Start or restart drx-ShortCycleTimer.

[0158] Alternatively, if an LBT failure is detected or an LBT success is not detected, Extend the DRX active time. This starts or restarts the DRX inactive timer. This can be achieved by starting it up. Also, when the DRX inactive timer expires, DR The X short cycle timer is started or restarted, which causes the DRX short The cycle can be used continuously. Furthermore, this allows the schedule lost due to LBT failure to be recovered. Further PDCCH UL and DL may be required for the opportunity to conduct a thorough examination. Scheduling opportunities may become available. For example, even if the MAC specification is modified as follows: good. 3>If PDCCH indicates a new transmission (DL or UL), 4> The first symbol after PDCCH reception ends, drx-InactivityTime Start or restart r, 3>If an LBT failure is detected, 4> Start or restart drx-InactivityTimer.

[0159] Preferably, the DRX inactive timer is started or restarted within a certain period of time when the LBT fails This depends on whether multiple failures or failures of LBT successes have occurred. The duration is ondu The duration of the ration or the duration of the inactive timer, duration and inactive This could be a combination of the time periods during which the time timer is running. For example, 1>If LBT success is not detected, drx-onDurationTimer When it expires, 2> Start or restart drx-InactivityTimer, 1>If LBT success is not detected, drx-InactivityTimer When it expires, 2> Start or restart drx-InactivityTimer.

[0160] LBT failures may not occur in a single instance. Multiple LBT failures or successes may occur. The detection may also involve a series of LBs that affect the UE reception of the PDDCH. It may only be started after T has failed.

[0161] Count LBT failures or LBT successes, or consecutive LBT misses or consecutive LBs You may define a procedure to count T successes. LBT failure or consecutive LBT failures. However, if the set maximum LBT failure threshold is exceeded, or if LBT is successful or continuous LBT is not performed, DRX deactivates only if success is possible below the configured minimum LBT success threshold. The timer will be restarted. For example, 1> If the LBT success count is less than the LBT minimum success threshold, the duration timer When it expires, 2> Start or restart drx-InactivityTimer. Furthermore, to ensure that the UE never enters the DRX, the DRX inactive timer is significantly reduced. Extend the timer, or extend the DRX inactive timer indefinitely due to LBT failure. There are times when it is necessary to avoid this. In that case, restarting the DRX inactive timer is , it may be limited to a specified or set maximum value. For example, the MAC specification may be as follows: You may revise it to this. 1>DRX-Inactivity-LBT-Failure-Count>DRX-I If the nactivity-LBT-FailureThreshold is met, and 1>DRX-Inactivity-TimerRestartCount<=DRX- If the Inactivity-Restart-Threshold is active, 2> Set DRX-Inactivity-LBT-Failure-Count to 0 hand, 2> Set DRX-Inactivity-TimerRestartCount to 1. Create, 2> Start or restart drx-InactivityTimer, 1>If an LBT failure is detected, 2> Increment DRX-Inactivity-LBT-Failure-Count To do. DRX-Inactivity-LBTRestartThreshold In that case, you may perform the following actions. 1>DRX-Inactivity-TimerRestartCount>DRX-I If nactivity-restart-threshold is present 2> If a short DRX cycle is set, 3>drx - The first symbol after the expiration of InactivityTimer, or DRX The first symbol after the MAC CE command has finished receiving, drx-ShortCycle Start or restart the timer, 3> Use a short DRX cycle, 2> Otherwise, 3> Use a long DRX cycle.

[0162] By starting or restarting the inactive time when an LBT failure occurs. Is extending the DRX active time a configurable option, or is it currently available? It should depend on an active service. For example, the URLLC service supports If possible, it is better to maintain scheduling opportunities when an LBT failure occurs. It will become more important.

[0163] Alternatively, the extended DRX active time is set to the DRX inactive time. It may be different from the timer period. It may be a different setting value, or preferably The period for the amount of LBT failures detected during the current DRX active time period. That's good too.

[0164] In another example, by dynamically adapting the DRX procedure, the LBT operation is generated There may be a way to address the inefficiency of DRX. UE wakes up each DRX cycle. In this case, the DRX setting may be dynamically adjusted according to the LBT operation. For example, the DRX setting may be dynamically adjusted according to the LBT operation. You can periodically adjust the duration, inactivity, or DRX cycle. Yes. This may be for each DRX cycle.

[0165] Before transmission, the NB determines the Clear Channel Assessment (CCA) and the channel access priority class. Select CAPC. CAPC includes Maximum Channel Occupancy Time (MCOT) and Co The Concentration Window Size (CWS) is selected. Transmission is disabled during the MCOT period. While transmission is possible, transmission is not possible during the CCA and CWS periods. Since the timing can be dynamically adjusted, the DRX operation of the UE is dynamically adjusted and determined by the NB. The transmission opportunities can be matched more effectively.

[0166] To achieve this, each DRX cycle is signaled from the NB downlink In addition to the LBT success indicator, or included therein, the CCA period, selected MCOT if CWS or other timing information may be provided to MAC, downlink and uplink. This will allow for more accurate determination of opportunities to send a plink. MCOT, CWS, or Other timings represent the channel access priority class (CAP) that indicates the selected timing. C) It can be identified by another index.

[0167] Based on the reception of LBT timing information, the UE DRX procedure aligns with the MCOT period. The active time is dynamically adjusted to enable DRX during CWS and, if applicable, CCA periods. Apply this.

[0168] For example, at the start of each DRX cycle, the MCOT selected by the NB is ondule You may set the timing. Similarly, the inactive timer will be aligned with the selected MCOT. It may be configured to do so.

[0169] Alternatively, the UE may enter the DRX during the CWS and, if applicable, the CCA period. In this case, the active time may overlap with the MCOT period, or with CWS and possibly CC. This includes only durations and inactive time periods that do not overlap with Period A. For example, the MAC specification could be modified as follows:

[0170] If a DRX cycle is set, the active time includes the following: . • drx-onDurationTimer, or drx-InactivityTi mer, or drx-RetransmissionTimerDL, or drx- RetransmissionTimerUL, or ra-ContentionRe The solutionTimer (as described in Section 5.1.5) is being executed. between, and While drx-MCOT-Timer is running.

[0171] Or instead, If a DRX cycle is set, the active time includes the following: . • drx-onDurationTimer, or drx-InactivityTi mer, or drx-RetransmissionTimerDL, or drx- RetransmissionTimerUL, or ra-ContentionRe The solutionTimer (as described in Section 5.1.5) is being executed. between, and • While drx-CWS-Timer is not running.

[0172] (Scheduling request) The following modifications to the SR procedure take into account the impact of LBT in NR-U.

[0173] If there are pending SRs and, in some cases, LBT failures are detected after a certain period of time, The DOM access procedure should be initiated, and any pending SRs should be canceled. This means that, This may be necessary if the PUCCH resource becomes unavailable due to an LBT failure. In this case, the RA procedure is attempted, and if this procedure fails, wirelessly resolves the issue. A link failure is declared. For example, the MAC specification may be modified as follows: As long as at least one SR is pending, the MAC entity will have access to each pending SR. In contrast, the following shall apply: 1> The MAC entity sets a valid PUCCH resource for the pending SR. If not present, or 1>If an LBT failure is detected, 2> Start a random access procedure in SpCell (see, for example, section 5.1 of [2]) Cancel the pending SR.

[0174] The validity of the PUCCH resource is also defined for LBT success or LBT failure. That's also fine. For example, the MAC specification could be modified as follows:

[0175] PUCCH on the active BWP during an SR transmission opportunity when LBT failure has not been detected. Only the source is considered valid.

[0176] As long as at least one SR is pending, the MAC entity will not process each pending SR The following applies to the situation: 1> The MAC entity sets a valid PUCCH resource for the pending SR. If not, 2> Start a random access procedure in SpCell (see, for example, section 5.1 of [2]) Cancel the pending SR.

[0177] The above example can sometimes be expressed from the perspective of detecting "no LBT failures," but "LBT It is sometimes expressed as the detection of "success". LBT failure or LBT success is a single instance This is not always the case. Multiple LBT failures or successes may be detected. The RA procedure is: It may be started only after a series of LBT failures that affect the SR transmission of PUCCH.

[0178] Procedures may be defined to count LBT failures or LBT successes, or to count consecutive LBT failures or consecutive L BT successes. If the LBT failure or consecutive LBT failures exceed the set maximum LBT failure threshold, or if the LBT success or consecutive LB T successes may be less than the set minimum LBT success threshold, the random access procedure is started.

[0179] Another example is shown below. When the physical layer is instructed to transmit SR, the SR prohibition timer is started only when the LBT success for the SR transmission is determined, and the SR counter can be incremented. For example, the MAC specification may be modified as follows. When 2> the MAC entity has an SR transmission opportunity on a valid PUCCH resource for the set SR, and When 2> at the SR transmission opportunity, the sr-ProhibitTimer is not running, and When 2> the PUCCH resource of the SR transmission opportunity does not overlap with the measurement gap, and and When 2> the PUCCH resource at the time of SR transmission does not overlap with the UL-SCH resource, and When 3> SR_COUNTER < sr-TransMax, and When 4> the physical layer is instructed to signal SR on one valid PUCCH resource for SR, and when it is determined that the LBT is successful, When 5> start the sr-ProhibitTimer, When 5> increment the SR_COUNTER by 1.

[0180] ​​​​Alternatively, as is done in existing procedures, the SR prohibition timer is activated and the SR counter is It may be incremented, but if LBT failure is detected, the prohibition timer will be stopped. It is also acceptable for the SR counter to be decremented.

[0181] This fix addresses the issue where the SR counter does not reach SR Trans Max, and SR transmission When blocked by an LBT failure, release physical resources and initiate the RA procedure. To ensure that the SR prohibition timer, which delays subsequent SR transmissions, is not set, Therefore, it may be necessary.

[0182] Furthermore, to ensure that the UE never determines that the SR transmission procedure was unsuccessful, LBT failures are not detected. Do not increment the SR transmission counter by a large amount, or do not use the SR transmission counter. In some cases, it may be necessary to avoid not incrementing the deadline. The incrementing may be limited to a specified or set maximum value. For example, the MAC specifications could be modified as follows: 2>If no SR LBT failure is detected, or, 2>SR-Transmission-LBT-Failure-Count>SR-T If the transmission-LBT-FailureThreshold is met, 3>Increment SR_COUNTER by 1, 3> 2>If SRTransmission-LBT-Failure is detected, 2> Increment SRTransmission-LBT-Failure-Count To do.

[0183] RA-PreambleTransmission-LBT-FailureThre If the hold is exceeded, you may perform the following actions, or change the MAC specifications as follows. You can change it to "uni". 2>If SR-Transmission-LBT-Failure is detected, 2> Increment SR-Transmission-LBT-Failure-Count Comment, 2>SR-Transmission-LBT-Failure-Count>STra If the mission-LBT-FailureThreshold is active,

[0184] Another example is shown below. Only when LBT success for BSR transmission is determined, pending The SR(s)(single or multiple) may be canceled, and the SR ban timer may be stopped. , prohibiting delaying subsequent SR transmissions when the current SR is not transmitted due to LBT failure. This may be necessary to ensure that the timer is not set.

[0185] For example, if LBT success is determined for MAC PDU transmission, and this PDU is MAC Last event that triggered BSR (see section 5.4.5 of [2]) before PDU assembly If the BSR MAC CE has buffer states up to (and included in) the timestamp All pending SRs triggered before MAC PDU assembly will be canceled. Each sr-ProhibitTimer will be stopped.

[0186] The above example can be expressed as follows, from the perspective of LBT failure detection, instead of LBT success detection. It is acceptable. If LBT failure is not detected for MAC PDU transmission, this PDU is MA The last time a BSR was triggered before the C PDU assembly (see section 5.4.5 of [2]) Includes a BSR MAC CE with a buffer state up to (and included in) venting. In this case, all pending SRs triggered before MAC PDU assembly will be canceled. Assuming this is the case, each sr-ProhibitTimer will be stopped.

[0187] Alternatively, when a MAC PDU containing a BSR is provided to the PHY layer, the existing procedure is performed In this way, pending SRs (single or multiple) may be canceled, and the ban timer It may be stopped, but if LBT failure (or equivalent to no LBT success) is detected... If this is confirmed, the pending SR(s) (single or multiple) will be restored and the prohibit timer will be restarted. It's okay.

[0188] (Buffer status report) The following modifications to the BSR procedure take into account the impact of LBT in NR-U.

[0189] A regular BSR is triggered, and there may be UL-SCH resources available for transmission, If transmission is blocked due to an LBT failure, an SR may be triggered. If available grants are lost, subsequent grants will become available for BSR transmission. Sometimes a new SR is needed to make it work, so this may be necessary. Yes, it is. For example, the MAC specification could be modified as follows: 2> A regular BSR is triggered, and logicalChannelSR-DelayTi If mer is not executed, 3> If there are no UL-SCH resources available for a new transmission, or 3> Uplink grants (single or multiple) are set for the MAC entity. Logical Channel SR masking is performed by the upper layer. Regular BSRs are not triggered for logical channels where SR-Mask is set. If you bought, or 3> If a UL-SCH resource is available for a new transmission, BSR(singular or plural) The LCP mapping limit set on the logical channel(s)(5 of [2]) If the conditions (see Section 4.3.1) are not met, or 3> There are UL-SCH resources available for transmission, and an LBT failure is detected for this transmission. If that happens, 4> Trigger a scheduling request.

[0190] The above revised text is written from the perspective of LBT failure, but from the perspective of no LBT success It can also be represented by points.

[0191] LBT failures or successes may not occur with a single instance; multiple LBs may be involved. T may be detected as failure or success. SR affects MAC BSR CE transmission. The boss may only be triggered after a series of LBT failures.

[0192] Additionally, it counts LBT failures or LBT successes, or consecutive LBT failures or You may define a procedure to count consecutive LBT successes. LBT failure or consecutive LBTs If the number of BT failures exceeds the set maximum LBT failure threshold, or if LBT is successful or continuous SR is triggered only if LBT success is possible to be below the set minimum LBT success threshold. It can be done.

[0193] The BSR MAC CE transmission was blocked due to an LBT failure and will be retransmitted after a delay. If so, the NB will be notified of when the BSR was calculated, or when the PHR is calculated. Additional signaling is introduced to notify the NB of the transmission conditions when this occurs.

[0194] For the NB to process the BSR properly, it needs to know when the BSR was calculated. It may be necessary to do so.

[0195] If it is not operating in an unlicensed frequency band and LBT is not being used, then NB is B It is possible to roughly obtain when the content of the SR was judged. NB is scheduled and Because they are aware of what they have received and the rules of the BSR, they can interpret the BSR appropriately. However, if LBT fails and transmission is delayed until LBT succeeds, NB becomes outdated. You may receive a BSR or an inaccurate BSR, and in some cases, it may be required by the UE. Allocating more resources than is required, or fewer resources than are needed by the UE. This can lead to penalties for transmission delays and QoS guarantees. Below are some ways to address this issue. Several methods for dealing with this are presented. The first method is to determine when the BSR calculation was constructed. Provide BSR with additional information so that NB can make a determination. This is done when the first LBT fails. The delay may be based on LBT for the interval, or it may be based on absolute time. In this method, the NB can determine the effective delay caused by the LBT for BSR, The failure or success of LBT may be shown independently to NB. In the third method, PHR is calculated Notify the NB of the grant used when it was calculated (e.g., uplink grant). Additional information will be provided along with the PHR.

[0196] It would be beneficial for the NB to receive additional information that allows them to know when the BSR was built. It seems like it, but it's not necessary. Or, in situations where BSR is providing inaccurate information... In total, NB must at least recognize this. This means that UE will tell NB about LBT failure and By demonstrating success, the NB can determine that there was an LBT failure that delayed the BSR. This can be achieved by doing so.

[0197] Another example is shown below. The trigger condition for BSR should take LBT failure into consideration. The data is now available, and the currently specified regular BSR trigger criteria, padding B The trigger criteria for SR trigger condition, BSR retransmission timer expiration, and BSR period timer expiration are met. This should only be considered if LBT is successful. Adding LBT criteria to each of the existing criteria They are mutually exclusive with respect to triggers and therefore only affect a subset of existing criteria. To be able to give.

[0198] For example (considering all triggers), the MAC specification may be modified as follows: . A BSR will be triggered if any of the following events occur. • MAC entities can access new UL data in logical channels belonging to LCG. possess, and, • Which logic does the new UL data contain any available UL data belonging to any LCG? It belongs to a logical channel with a higher priority than the channel's priority, and LBT subsequently succeeds. ,or, • None of the logical channels belonging to LCG contain any available UL data, L BT subsequently succeeded. In this case, the BSR is called a "regular BSR," as follows: • UL resources are allocated, and the number of padding bits is reported in the buffer status MAC. The size is greater than or equal to the CE plus its subheaders, and if LBT is successful thereafter, BSR This is called "padding BSR" as follows: • The retxBSR-Timer has expired, and at least one of the logical channels belonging to the LCG One contains UL data, and if LBT is successful thereafter, the BSR is as follows: Uni is called "regular BSR", • If the periodicBSR-Timer expires and LBT is subsequently successful, BSR This is called a "periodic BSR" as follows: The MAC entity is defined as follows: 1> The buffer status reporting procedure triggers at least one BSR, and If it is determined that it has not been canceled, 2>When UL-SCH resources are available for a new transmission and LBT is determined to be successful If, 3> Multiplexing and assembly to generate BSR MAC CE(singular or plural) Follow the instructions in the procedure. 3> Unless all generated BSRs are long or short truncated SRs, p Start or restart eriodicBSR-Timer, 3> Start or restart retxBSR-Timer.

[0199] Even if multiple events trigger a BSR, MAC PDU can only access one BSR. This shall include MAC CE. Regular BSR and periodic BSR shall be padding. It shall take precedence over BSR.

[0200] MAC entities grant new data transmissions in any UL-SCCH Upon receiving this message, the retxBSR-Timer will be restarted.

[0201] UL grants (single or multiple) can be applied to all pending data that can be sent, and LBT The success was determined, but it is not sufficient to further adapt BSR MAC CE and its subheaders. If not, all triggered BSRs may be canceled. LBT success is determined. When a MAC PDU containing a BSR MAC CE is sent, the MAC PDU assembly All BSRs triggered before the BR will be canceled. The above revised text is written from the perspective of LBT success, but from the perspective of LBT failure not occurring. It can also be represented by points.

[0202] LBT failures or successes may not occur with a single instance; multiple LBs may be involved. T may be detected as failure or success. SR affects MAC BSR CE transmission. The boss may only be triggered after a series of LBT failures.

[0203] Also, count LBT failures or LBT successes, or consecutive LBT failures or The procedure may be defined to count consecutive LBT successes. LBT failure or consecutive If the number of LBT failures exceeds the configured maximum LBT failure threshold, or if LBT is successful or SR is triggered only if the number of consecutive LBT successes is less than the set minimum LBT success threshold. It will be rigged.

[0204] The above example MAC-specific changes are described from the perspective of LBT success, but the example is L This can also be expressed similarly from the perspective of having no BT failures.

[0205] Alternatively, the BSR period timer and BSR retransmission timer can be handled using existing procedures. It may be started or restarted, but if LBT failure is determined, the BSR period timer And the BSR retransmission timer is set to the remaining value before the last reset due to LBT failure, or For example, it will be reset to a different time value, such as a set time value.

[0206] This fix corrects the BSR period when BSR transmission is blocked by LBT failure. To prevent delays in transmission or retransmission of BSRs, use a BSR period timer or BSR retransmission timer. This may be necessary to ensure that the signal timer cannot be reset.

[0207] (Logical Channel Prioritization (LCP) Procedure) ) The following modifications to the LCP procedure may take into account the impact of LBT in NR-U.

[0208] If an LBT failure is detected before transmission, a MAC PDU should not be generated.

[0209] For example, the MAC specification could be modified as follows:

[0210] A MAC entity is a MAC P of a HARQ entity if it meets the following conditions. DU will not be generated. • The MAC entity is set to skipUplinkTxDynamic, H Whether the grant shown in the ARQ entity is addressed to C-RNTI, This is an uplink grant that has been set up, as indicated by the HARQ entity. And, • As specified in TS38.212, the non-password required for this PUSCH transmission There is no periodic CSI, and, • MAC PDU contains 0 MAC SDUs, and • MAC PDUs only contain periodic BSRs and data available for any LCG Either there is no TA, or the MAC PDU only contains padding BSR, or • No LBT failures were detected.

[0211] Alternatively, the criterion could be whether LBT success was detected.

[0212] This fix may prevent this MAC PDU from being accepted by subsequent grants (e.g.) For example, due to the size of the UL grant, and also the generated MAC CE (singular or plural). ) may provide incorrect information (e.g., PHR, BSR...) when transmitting MAC PDU. Therefore, it may be necessary.

[0213] Another example is shown below. Alternatively, you could generate a MAC PDU and provide it to the physical layer. When an LBT failure is detected in this MAC PDU, the LCP procedure is restarted and a new MA is created. Generate a C PDU.

[0214] To achieve this, the MAC SDU, which was integrated into this MAC PDU, These MAC SDUs may be stored until LBT success is determined. Wouldn't it be necessary to recreate these MAC SDUs from the MAC PDUs? It can be reprocessed.

[0215] A simpler example is when the grant is larger, the UE removes the padding, L The remaining space is used to multiplex additional data according to the CP, or the UE is a sub-PDU (M AC SDU and CE) are backed out, and the data is processed for the previous grant. The goal is to reshape the LCP as if it had never been formed.

[0216] However, even in this case, the MAC CE previously determined by LAA has already been constructed. In some cases, older PHR CEs may be allowed. In that case, the network is what Sometimes it's unclear how the PHR was calculated based on the transmission.

[0217] The timers and counters for MAC procedures (BSR, PHR, etc.) are based on the previous (failed) transmission. Rebuilding CE is complicated because it has already been affected by Shin.

[0218] When MAC PDU multiplexing and assembly are re-executed, the trigger is re-evaluated. The MAC CE can be recovered and saved so that the reported value is recalculated, or The events that triggered these MAC CEs can be recovered.

[0219] A more complex case is what to do when the grant is smaller. First, LCP Based on this, determine what can be sent from the previous PDU. Next, determine what will not be sent. Recover a MAC SDU and the MAC procedure timer associated with sending a MAC CE. And reset the counters to the values ​​before MAC CE was built for the timer and counters. You can set the tag.

[0220] Since the last transmission, new high-priority data or other MAC CE triggers and An event may have been received. To address this possibility, multiplexed assembly The procedure does not prioritize MAC SDUs associated with failed MAC PDU transmissions. There is.

[0221] The same problem can occur with MAC CE, and these are now outdated. Backing out the procedure is complicated.

[0222] NB indicates that the MAC CE transmission was delayed, or that it was originally scheduled to be transmitted. This should be known.

[0223] Another issue is that segmentation is performed using RLC, and the MAC's SDU may be too large. It is possible that the MAC request RLC will back out the previous RLC PDU. The matter is very complex. One way to deal with this is to address this MAC SDU RLC PDUs and other S may not be multiplexed to new MAC PDU transmissions. The strategy is to feign an RLC negative response to a DU.

[0224] (Beam fault detection and recovery) The following modifications to beam obstruction and detection procedures take into account the effects of LBT in NR-U. Even if the beam fault recovery timer expires, random access to beam fault recovery will be required. If an LBT failure is detected after the start of the sequence, the beam failure recovery timer should be extended. This is due to the early expiration of the beam fault recovery timer, and in some cases, cell reselection or RR. It may be necessary to avoid C(re)establishment.

[0225] The entities that perform the steps shown herein, such as in Figures 2 to 10, are logical It is understood that this may be performed by an entity. The steps are shown in Figures 12A to 1. Stored in the memory of a device, server, or computer system as shown in 2G It may be stored and executed on that processor. Exemplary methods disclosed herein In between, you can skip steps, combine steps, or change steps It is intended to be added.

[0226] Table 1 provides illustrative abbreviations or definitions.

[0227] [Table 1-1]

[0228] [Table 1-2]

[0229] [Table 1-3]

[0230] Figure 11 shows the method, system, and of the NR-U LBT MAC procedure described herein. And exemplary displays that can be generated based on the device (e.g., graphical user The interface is shown. Display interface 901 (for example, touchscreen) The display (N-Display) specifically includes PHR-related parameters and method flows, etc., NR-UL The text of block 902 associated with the BT MAC procedure may be provided. The progress of any of the steps described in the document (for example, the message sent or the step) The success of the operation may be displayed in block 902. Furthermore, graphical output 902 may be displayed in the The output may be displayed on the display interface 901. The graphical output is NR-U L The BT MAC procedure method, system, and device topology for implementing the device. The graphical output of the progress of any method or system discussed herein, That's good too.

[0231] 3rd Generation Partnership Project: 3GPP) is a framework for wireless access, core transport networks, and codecs. Cellular We develop technical standards for communication network technologies. (Recent Radio Access Technology) :RAT) standards include WCDMA (registered trademark) (commonly called 3G), LTE (commonly (These are referred to as 4G), the LTE-Advanced standard, and the newer "5G" There is a new wireless technology (New Radio: NR). Development of 3GPP NR standards will continue. This is expected to include a definition of next-generation wireless access technology (new RAT). Providing new flexible wireless access below 7GHz, and new above 7GHz It is expected that this will include the provision of ultra-mobile broadband wireless access. Flexible wireless access is a new wireless incompatible wireless in the new frequency band below 6GHz. By comprising line access and including different operating modes that can be multiplexed in the same frequency band, It is expected to address a wide range of 3GPP NR use cases with varying requirements. Mobile broadband includes, for example, ultralight applications such as indoor use and hotspots. The centimeter wave and millimeter wave frequency bands provide opportunities for mobile broadband access. It is expected to be included. Especially in ultra-mobile broadband, centimeter wave Furthermore, through design optimization specifically for millimeter waves, it is compatible with flexible wireless access below 7GHz and common It is expected to provide a design framework.

[0232] 3GPP has identified various use cases that NR is expected to support. As a result, a wide variety of users regarding data rate, latency, and mobility have emerged. The requirements for the experience have arisen. Use cases include the following common categories, and extended models. Enhanced Mobile Broadband (eMBB) ultra-high reliability low latency communication Ultra-Reliable Low-Latency Communication (URLLC), large-scale machine type Communications (Massive Machine Type Communications: mMTC), network operation (for example) Network slicing, routing, migration and interwork Enhanced Vehicle-To-Everything (enhanced vehicle-to-everything), as well as energy efficiency. Vehicle-to-Vehicle Communication (V2X) is a type of communication between vehicles. 2V), Vehicle-to-Infrastructure Communication Vehicle-to-Network Communication (V2N) , Vehicle-to-Pedestrian Communication (V2P), and other This may include any of the following: Specific services and applications include, for example, monitoring and sensor networks, and Remote control of devices, two-way remote control, personal cloud computing, video Streaming, wireless cloud-based office, first responder connectivity , car emergency call system, disaster alert, real-time gaming, multi-person video calls Autonomous driving, augmented reality, touch internet, virtual reality, home automation, Bots and aerial drones are just a few examples of these uses. All of the above and other use cases are intended in this specification.

[0233] Figure 12A shows the system described and claimed herein as shown in Figures 1 to 10. Examples of methods and apparatus for the NR-U LBT MAC procedure, such as the method and apparatus, may be used. This shows the communication system 100. The communication system 100 includes a wireless transceiver unit (Wireless Tr ansmit / Receive Unit:WTRU)102a, 102b, 102c, 102d, 102e , 102f, or 102g (these are generally or collectively WTRU102 or It may include (sometimes called WTRU102). The communication system 100 is wireless Radio Access Network (RAN) 103 / 104 / 105 / 10 3b / 104b / 105b, core network 106 / 107 / 109, public switched telephone network (Public Switched Telephone Network: PSTN) 108, Internet 110, Other networks 112 and network services 113 may also be included. Work Service 113 includes, for example, V2X servers, V2X functions, ProSe servers, Pro SE functionality, IoT services, video streaming, or edge computing It may include [various things].

[0234] The concepts disclosed herein apply to any number of WTRUs, base stations, networks, or NETs. It will be understood that it may be used in conjunction with the WTRU102a. Each of 102b, 102c, 102d, 102e, 102f, or 102g is without Any type of device or apparatus configured to operate or communicate in a linear environment This may also apply to each WTRU102a, 102b, 102c, 102d, 102e, 102f, Alternatively, 102g is shown in Figures 12A, 12B, 12C, 12D, 12E, or 12 In some cases, F is illustrated as a handheld wireless communication device, but it is intended for 5G wireless communication. In the various use cases illustrated, each WTRU transmits or This may include any type of device or apparatus configured to receive, and It is understood that this may be made concrete, and as just one example, User Equipment t:UE), mobile station, fixed or mobile subscriber unit, pager, cellular phone, Personal Digital Assistant (PDA), Smartphone Phone, laptop, tablet, netbook, notebook computer, personal Computers, wireless sensors, home appliances, smartwatches or smart wear, etc. Wearable devices, medical or electronic health devices, robots, industrial equipment, drones This includes vehicles such as automobiles, buses, trucks, trains, or airplanes.

[0235] The communication system 100 may also include base stations 114a and 114b. In example 12A, each base station 114a and 114b is illustrated as a single element. In practice, base stations 114a and 114b can connect to any number of interconnected base stations or Network elements may be included. Base station 114a is part of core network 106 / 107 / 109, Internet 110, Network Services 113, or other network To facilitate access to one or more communication networks such as Ku112, WTRU It wirelessly interfaces with at least one of 102a, 102b, and 102c. It may be any type of device configured to do so. Similarly, base station 114b Core network 106 / 107 / 109, Internet 110, other networks Access to one or more communication networks, such as 112 or network services 113. To facilitate the process, a Remote Radio Head (RRH) 118a is used. 118b, Transmission and Reception Point (TRP) 119a , 119b, or Roadside Unit (RSU) 120a, 120b at least One and any type of device configured to interface via wired or wireless It may be there. RRH118a and 118b are on the core network 106 / 107 / 109 , Internet 110, network services 113, or other networks 112 To facilitate access to one or more communication networks, such as the WTRU102 At least one, for example, configured to interface wirelessly with the WTRU102c. Any type of device is acceptable.

[0236] TRP119a and 119b are core networks 106 / 107 / 109, Internet One of the following: network 110, network service 113, or other network 112 To facilitate access to the above communication network, at least WTRU102d It may be any type of device configured to interface wirelessly with one of them. RSU120a and 120b are for core networks 106 / 107 / 109, Network 110, other networks 112, or network services 113, etc. To facilitate access to one or more communication networks, WTRU102e or Any type configured to wirelessly interface with at least one 102f It may also be a device. For example, base stations 114a and 114b are radio base station equipment (Ba se Transceiver Station (BTS), Node B, eNode B, Home Node B, Home eNode-B, Next Generation Node-B (gNode-B), satellite, site Even if it is a controller, access point (AP), wireless router, etc. good.

[0237] Base station 114a may also be part of RAN103 / 104 / 105, which is, Base Station Controller (BSC), Wireless Network Controller Radio Network Controller (RNC), relay nodes, and other base stations or networks It may also include twerk elements (not shown). Similarly, base station 114b RAN10 It may also be part of 3b / 104b / 105b, which includes BSC, RNC, and relay nodes. Other base stations or network elements (not shown) may also be included. Base station 11 4a transmits or receives radio signals within a specific geographical area that may be called a cell (not shown). It may be configured to believe. Similarly, base station 114b is disclosed herein For NR-U LBT MAC procedure methods, systems, and devices, such as cell Transmitting or receiving wired or wireless signals within a specific geographical area that may be called (not shown). It may be configured as follows. Similarly, base station 114b may be called a cell (not shown). Configured to transmit or receive wired or wireless signals within a specific geographical area. The cell may be further divided into cell sectors. For example, at base station 114a The associated cell may be divided into three sectors. Therefore, in one embodiment, Even if the base station 114a includes three transceivers, one for each sector of the cell, Good. In one embodiment, the base station 114a is a Multiple-Input Multiple Output Input: MIMO technology may be used, and therefore multiple inputs per sector of a cell You may use a lanciba.

[0238] Base station 114a connects to WTRU1 via air interfaces 115 / 116 / 117. It may communicate with one or more of 02a, 102b, 102c, or 102g, and any appropriate Wireless communication links (e.g., radio frequency (RF), microwave, infrared) Infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. ) may also be used. Air interface 115 / 116 / 117 is any suitable wireless interface Access Technique (RAT) may be used to establish this.

[0239] Base station 114b connects via wired or air interface 115b / 116b / 117b And RRH118a, 118b, TRP119a, 119b, or RSU120a, It may communicate with one or more of the 120b, which may be any suitable wired connection (e.g., cable). (e.g., fiber optic cables, etc.) or wireless communication links (e.g., radio frequency (RF), microwave) (Waves, infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc.) The air interface 115b / 116b / 117b can be used with any suitable wireless access technology. (RAT) may be used to establish this.

[0240] RRH118a, 118b, TRP119a, 119b or RSU120a, 120 b is WTRU102c via air interface 115c / 116c / 117c, It may communicate with one or more of 102d, 102e, and 102f, which is any suitable radio. Communication links (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV)) ), visible light, centimeter wave, millimeter wave, etc. may also be used. Air interface 115c / 1 16c / 117c may be established using any appropriate radio access technology (RAT) good.

[0241] WTRU102a, 102b, 102c, 102d, 102e, or 102f are, They communicate with each other via air interfaces 115d / 116d / 117d, such as Idlink communication. Communication may be conducted using any suitable wireless communication link (e.g., radio frequency (RF)). (Microwaves, infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc.) It is also acceptable. The air interface 115d / 116d / 117d can be used with any suitable wireless interface. It may be established using RAT (Real-Action Technique).

[0242] The communication system 100 may be a multiple access system, and may include CDMA, TDMA, It employs one or more channel access methods such as FDMA, OFDMA, and SC-FDMA. This may also be the case. For example, base stations 114a and WTR in RAN103 / 104 / 105. In U102a, 102b, 102c, or RAN103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, and RSU120a, 120b Furthermore, WTRU102c, 102d, 102e, and 102f are for universal mobile communications. System (Universal Mobile Telecommunications System: UMTS) Terrestrial Wireless Act Wireless technologies such as UMTS (Terrestrial Radio Access: UTRA) can be implemented. , using Wideband CDMA (WCDMA) air interface 115 / 116 / 117 or 115c / 116c / 117c may be established respectively. WC DMA is an advanced version of High-Speed ​​Packet Access (HSPA). Includes communication protocols such as Evolved High-Speed ​​Packet Access (HSPA: HSPA+). Yes, it is. HSPA stands for High-Speed ​​Downlink Packet Access. Packet Access (HSDPA) or High-Speed ​​Uplink Packet Access (High-Speed ​​Packet Access) It may include Uplink Packet Access (HSUPA).

[0243] In one embodiment, base station 114a and WTRU 102a, 102b, 102c, or , RRH118a, 118b, TRP11 in RAN103b / 104b / 105b 9a, 119b, or RSU120a, 120b and WTRU102c, 102d This refers to the evolved UMTS Terrestrial Radio Access: It is also acceptable to implement wireless technologies such as E-UTRA, and Long-Term Evolution ( Long Term Evolution (LTE) or LTE-Advanced (LTE- A) Use air interface 115 / 116 / 117 or 115c / 116c / Each of the 117c interfaces may be established. In the future, air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies are LTE D2D and V2X technologies and interfaces. It may also include sidelink communication. Similarly, 3GPP NR technology is NR V Includes 2X technology and interfaces (such as sidelink communication).

[0244] Base stations 114a and WTRU102a, 1 in RAN103 / 104 / 105 In 02b, 102c, and 102g, or RAN103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, or RSU120a, 1 20b and WTRU102c, 102d, 102e, 102f are IEEE 802.1 6 (For example, WiMAX (Worldwide Interoperability for Microwave Access)) , CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, provisional standard Interim Standard 2000 (IS-2000), Interim Standard 95 (Interim St Standard 95 (IS-95), Interim Standard 856 (IS-856) GSM (Global System for Mobile communication) (registered trademark), EDGE (En Wireless technologies such as Improved Data Rates for GSM Evolution, GERAN (GSM EDGE), etc. It's okay to implement the technique.

[0245] In Figure 12A, base station 114c is, for example, a wireless router, home node B, and home e node. B may be an access point, as disclosed herein, NR- To implement the methods, systems, and devices of the ULBT MAC procedure, the business establishment Wireless connectivity in localized areas such as homes, vehicles, trains, airborne, satellite, manufacturing plants, and campuses. Any suitable RAT may be used to facilitate this. In one embodiment, base station 114c And WTRU102, for example WTRU102e, is a wireless local area network. To establish a Wireless Local Area Network (WLAN), IEEE 802.1 Wireless technologies such as 1 may be implemented. Similarly, base stations 114c and WTRU102d Wireless Personal Area Network (WPAN) To establish this, wireless technologies such as IEEE 802.15 may be implemented. In this embodiment, the base station 114c and WTRU102, for example WTRU102e, are To establish a cocell or femtocell, a cellular-based RAT (e.g., WCD) is used. You may also use MA, CDMA2000, GSM, LTE, LTE-A, NR, etc. As shown in Figure 12A, base station 114c has a direct connection to the internet 110. It may be there. Therefore, base station 114c is on the core network 106 / 107 / 109 It is not necessary to access the internet 110 via this method.

[0246] RAN103 / 104 / 105 or RAN103b / 104b / 105b are coreanes. It may also communicate with networks 106 / 107 / 109, and this network is for voice, Data, messaging, authorization and authentication, applications, or voiceover The Voice Over Internet Protocol (VoIP) service is available on W Configured to provide one or more TRU102a, 102b, 102c, and 102d. It can be any type of network. For example, core network 106 / 107 / 109 provides call control, billing services, mobile location-based services, and prepaid calling services. Internet connectivity, packet data network connectivity, Ethernet (registered trademark) (Target) May provide connectivity, video distribution, etc., and high-level security such as user authentication. You may execute the function.

[0247] Although not shown in Figure 12A, RAN103 / 104 / 105 or RAN103 b / 104b / 105b or core network 106 / 107 / 109 is RAN10 Same RAT as 3 / 104 / 105 or RAN103b / 104b / 105b or different RAT It is understood that it may communicate directly or indirectly with other RANs that employ the same RAT. It will likely be done. For example, RAN103 / 104 / 1 which can utilize E-UTRA wireless technology. In addition to being connected to 05 or RAN103b / 104b / 105b, Corene Network 106 / 107 / 109 also employs GSM or NR radio technology. It may also be communicating with the RAN (not shown).

[0248] Core networks 106 / 107 / 109 also include WTRU102a, 102b, and 10 2c, 102d, 102e are PSTN108, Internet 110, or other networks. It may also function as a gateway to access work 112. PSTN108 This refers to the network exchange that provides Plain Old Telephone Service (POTS). It may include a telephone network. Internet 110 is the TCP / IP Internet Protocol Transmission Control Protocol (TCP) in ColSuite ), User Datagram Protocol (UDP), Internet It uses a common communication protocol such as the Internet Protocol (IP). Including a global system of interconnected computer networks and devices That's fine too. Network 112 is owned or operated by another service provider. It may include wired or wireless communication networks. For example, network 112 is Any type of packet data network (e.g., IEEE 802.3 Ethernet) (This may include a network) or another core network connected to one or more RANs. This is RAN103 / 104 / 105 or RAN103b / 104b / 105 You may use the same RAT as in b, or a different RAT.

[0249] WTRU102a, 102b, 102c, 102d, 10 in communication system 100 Some or all of the 2e and 102f may include multimode capability, for example, WTRU102a, 102b, 102c, 102d, 102e, and 102f are Honmei As disclosed in the details, the methods, systems, and of the NR-U LBT MAC procedure To implement the device, it communicates with different wireless networks via different wireless links. It may include multiple transceivers for this purpose. For example, the WTRU102g shown in Figure 12A. This includes base stations 114a and IEEE 802 that can employ cellular-based wireless technology. It may be configured to communicate with a base station 114c that can employ wireless technology.

[0250] Although not shown in Figure 12A, user devices may also be connected to the gateway via a wired connection. It will be understood that the gateway is a residential gateway. It may also be a `Real Gateway (RG)`. The RG is the core network 106 / 107 / 10 Connectivity to 9 may be provided. Many of the ideas contained herein are WTRUs. This can also be applied to UEs, and UEs that connect to the network using a wired connection. This will be understood. For example, wireless interfaces 115, 116, 117 and 1 The ideas that apply to 15c / 116c / 117c can also be applied to wired connections. .

[0251] Figure 12B shows the method of the NR-U LBT MAC procedure as disclosed herein. Exemplary RAN103 and core network that can implement systems and devices This is a system diagram of 106. As shown above, RAN103 is air interface 115 To communicate with WTRU102a, 102b, and 102c via UTRA radio The technology may be adopted. RAN103 is also communicating with core network 106. Good. As shown in Figure 12B, RAN103 is located at nodes B140a, 140b, and 1 40c may also be included, and these are each connected via the air interface 115 to the WTRU Includes one or more transceivers for communicating with 102a, 102b, and 102c Alternatively, nodes B140a, 140b, and 140c are special within RAN103. It may be associated with a specific cell (not shown). RAN103 is also RNC142a, 142b may be included. RAN103 is any number of node B and wireless network It is understood that a controller (Radio Network Controller: RNC) may be included. It is likely.

[0252] As shown in Figure 12B, nodes B140a and B140b communicate with RNC142a Good. Furthermore, node B140c may also be communicating with RNC142b. Node B1 40a, 140b, and 140c are connected via the Iub interface to their respective RNs. It may also communicate with C142a and 142b. RNC142a and 142b are Iur They may communicate with each other via an interface. RNC142a and 142b This connects to each node B140a, 140b, and 140c. They may be configured to control. Furthermore, each of RNC142a and 142b Outer loop power control, load control, reception control, packet scheduling, hand-operated Other functionalities include overdrive control, macrodiversity, security features, and data encryption. It may be configured to perform or support this.

[0253] The core network 106 shown in Figure 12B includes a media gateway. MGW)144, Mobile Switching Center (MSC) )146, Serving GPRS Support Node (SGS) N)148, or Gateway GPRS Support Node It may also include de:GGSN)150. Each of the aforementioned elements is part of the core network 106. Although illustrated as such, any one of these elements is the core network operator It will be understood that it may be owned or operated by entities other than itself.

[0254] RNC142a within RAN103 communicates with the core network via the IuCS interface. It may be connected to MSC146 in 106. MSC146 is connected to MGW144. It may be done. MSC146 and MGW144 are WTRU102a, 102b, and By providing access to circuit-switched networks such as PSTN108 in 102c, W Communication between TRU102a, 102b, and 102c and conventional landline communication devices. This may be made easier.

[0255] RNC142a within RAN103 also communicates via the IuPS interface to the core network. It may be connected to SGSN148 in network 106. SGSN148 is connected to GGSN1 It may be connected to 50. SGSN148 and GGSN150 are WTRU102a, 102b and 102c to packet-switched networks such as Internet 110 Provides access to WTRU102a, 102b, and 102c, and IP-enabled devices Communication with the chair may be facilitated.

[0256] Core network 106 is also owned or operated by other service providers. Even if connected to other networks 112, which may include other wired or wireless networks good.

[0257] Figure 12C shows the method of the NR-U LBT MAC procedure as disclosed herein. Exemplary RAN104 and core network 1, which can implement the system and equipment. This is the system diagram for 07. As shown above, RAN104 has an air interface 116. To communicate with WTRU102a, 102b, and 102c via E-UTRA, Line technology may be used. RAN104 may also communicate with core network 107. stomach.

[0258] RAN104 may include e-nodes B160a, 160b, and 160c, It will be understood that RAN104 may contain any number of enodes B. B160a, 160b, and 160c are each connected via the air interface 116 and one or more transceivers for communicating with WTRU102a, 102b, and 102c It may include a . For example, enodes B160a, 160b, and 160c are MI MO technology may be implemented. Therefore, e-node B160a can, for example, have multiple antennas. Using this method, a radio signal is transmitted to WTRU102a, and a radio signal is received from WTRU102a. You may receive the number.

[0259] Each of the e-nodes B160a, 160b, and 160c is a specific cell (not shown). ) may be associated with wireless resource management decisions, handover decisions, and uplinks. Or configured to handle user scheduling in the downlink, etc. Alternatively, as shown in Figure 12C, e-nodes B160a, 160b, and 160c are X They may communicate with each other via two interfaces.

[0260] The core network 107 shown in Figure 12C is a mobility management gateway. Management Gateway (MME) 162, Serving Gateway 164, and Packet Includes Packet Data Network (PDN) Gateway 166 This is also good. Although each of the aforementioned elements is illustrated as part of the core network 107, this Any one of these elements is located by an entity other than the core network operator. It will be understood that it may be owned or operated.

[0261] MME162 connects to e-node B160a in RAN104 via the S1 interface. They may be connected to 160b and 160c respectively, and function as control nodes. This is also good. For example, MME162 is used in WTRU102a, 102b, and 102c. The authentication, bearer activation / deactivation, WTRU102a, 102b, and It can also play a role in selecting a specific serving gateway during the initial connection of the 102c. The MME162 also supports RAN104 and other wireless technologies such as GSM or WCDMA. It provides a control plane function for switching with other RANs (not shown) that employ this technology. That's good too.

[0262] The serving gateway 164, via the S1 interface, accesses the RAN104. It may be connected to nodes B160a, 160b, and 160c, respectively. Gateway 164 is generally used between WTRU 102a, 102b, and 102c. User data packets may be routed and forwarded at the serving gateway. 164 also anchors the user plane during eNode B handover. When downlink data is available on WTRU102a, 102b, and 102c Triggering paging, in the context of WTRU102a, 102b, and 102c Other functions may be performed, such as managing and saving items.

[0263] Serving gateway 164 may also be connected to PDN gateway 166. This includes WTRU102a, 102b, and 102c, as well as Internet 110, etc. Provides access to the packet-switched network, WTRU102a, 102b, 1 Communication between the 02c and an IP-enabled device may be facilitated.

[0264] The core network 107 may facilitate communication with other networks. For example, Core network 107 connects to WTRU102a, 102b, and 102c, and to the PSTN. Provides access to circuit-switched networks such as WTRU102a, WTRU102 b, and 102c may facilitate communication between them and conventional landline communication devices. Example For example, the core network 107 is the network between the core network 107 and the PSTN 108. An IP gateway that functions as an interface (e.g., an IP multimedia subsystem It may include an IP Multimedia Subsystem (IMS) server, or it may also include an IMS server. Communication is permitted. Furthermore, the core network 107 is WTRU102a, 102b, and 102c, other wired or operated by other service providers Access to network 112, which may include a wireless network, may be provided.

[0265] Figure 12D shows the method of the NR-U LBT MAC procedure as disclosed herein. Exemplary RAN105 and core network that can implement systems and devices This is a system diagram of 109. RAN105 is connected to WTR via air interface 117. NR radio technology may be employed to communicate with U102a and 102b. RAN1 05 may also communicate with the core network 109. Non-3GPP interworking Function (Non-3GPP Interworking Function: N3IWF) 199 is an air interface. To communicate with WTRU102c via 198, non-3GPP wireless technology may be used. N3IWF199 may also communicate with core network 109.

[0266] RAN105 may include g nodes B180a and 180b. RAN105 is It will be understood that it may contain any number of g-nodes B. g-node B180a and 180b respectively connect to WTRU102a via air interface 117, and It may include one or more transceivers for communicating with 102b. Integrated Access When a backhaul connection is used, the same air is used between the WTRU and the g node B. An interface may be used, which is a core network via one or more gNBs. Workpiece 109 may also be used. gNodes B180a and 180b are MIMO, MU- MIMO or digital beamforming technology may be implemented. Therefore, g The B180a, for example, uses multiple antennas to send wireless signals to the WTRU102a. It may transmit and receive radio signals from WTRU102a. RAN105 is e-no It should be understood that other types of base stations, such as D-B, may also be used. It will be understood that AN105 may employ one or more types of base stations. For example, the RAN may employ e-node B and g-node B.

[0267] N3IWF199 may include a non-3GPP access point 180c. It is understood that F199 may include any number of non-3GPP access points. It is likely. The non-3GPP access point 180c can connect via the air interface 198. It may include one or more transceivers for communicating with the TRU102c. Access Point 180c uses 802.11 via Air Interface 198 It is also possible to communicate with WTRU102c.

[0268] Each of the g-nodes B180a and B180b is associated with a specific cell (not shown). It may be done, for wireless resource management decisions, handover decisions, uplink or downlink decisions. It may be configured to handle user scheduling and other related tasks within the link. (Figure 1) As shown in 2D, g nodes B180a and 180b are, for example, Xn interfaces They may communicate with each other via S.

[0269] The core network 109 shown in Figure 12D is a 5G core network. k:5GC) may also be used. The core network 109 is connected to the wireless access network. Therefore, a large number of communication services may be provided to interconnected customers. Work 109 consists of numerous entities that perform the functionality of the core network. When used in this specification, "core network entity" or "network device" The term "function" refers to any entity that performs one or more functions of the core network. This means that such core network entities are systems illustrated in Figure 12G. Devices or computers configured for wireless or network communications, such as the Mu90. Computer executable instructions stored in system memory and executed on that processor. It is understood that logical entities may be implemented in the form of (software). .

[0270] In the example shown in Figure 12D, the 5G core network 109 is an access and mobility management device. Access and Mobility Management Function (AMF) 172, Session Management Function (Session Management Function: SMF) 174, User Plane Function (User P lane Function:UPF)176a and 176b, User Data Management Function Management Function (UDM) 197, Authentication Server Function Function: AUSF)190, Network Exposure Function: NEF)196, Policy Control Function (PCF)184, Non 3GPP Interworking Function (N3IWF) 199, User Data Repository (User It may also include Data Repository:UDR)178. Each of the aforementioned elements is part of the 5G core network. Although illustrated as part of workpiece 109, any one of these elements is a corenet It is understood that it may be owned or operated by entities other than the twerk operator. It will likely be done. Furthermore, the 5G core network is not composed of all of these elements. It may be omitted, or it may consist of additional elements, and multiple instances of each of these elements. It will also be understood that it may be composed of the following: This indicates a direct connection to the routing agent or messenger. It should be understood that communication may also be conducted via routing agents such as buses. That is the case.

[0271] In the example in Figure 12D, connectivity between network functions is a set of interfaces or criteria. It is achieved through points. Network functions are other network functions or services Services that are invoked or called by It will be understood that it can be modeled, described, or implemented as a set. Calls to work function services are made via direct connections between network functions and message buses. This may be achieved through message exchange, software function calls, or other means.

[0272] AMF172 may be connected to RAN105 via the N2 interface, and control It may function as a node. For example, AMF172 can handle registration management, connection management, and reachability. It may also be responsible for access control, access authentication, and access authorization. AMF is the user plane. It is responsible for transferring the tunnel configuration information to RAN105 via the N2 interface. It is also possible that the AMF172 transmits data from the SMF to the user plane via the N11 interface. The tunnel configuration information may be received. The AMF172 is generally an N1 interface. Routing NAS packets between WTRU102a, 102b, and 102c via It may be transferred in this manner. The N1 interface is not shown in Figure 12D.

[0273] The SMF174 may be connected to the AMF172 via the N11 interface. Similarly, SMF is connected to PCF184 via the N7 interface, as well as the N4 interface. It may be connected to UPF176a and 176b via a face. SMF174 controls It may function as a node. For example, SMF174 can manage sessions, WTRU1 IP address assignment for 02a, 102b, and 102c, UPF176a and the management and configuration of traffic steering rules in UPF176b, as well as It may also be responsible for generating downlink data notifications for AMF172.

[0274] UPF176a and UPF176b are WTRU102a, 102b, and 102 c. Access to packet data networks (PDNs) such as Internet 110. Provides communication between WTRU102a, 102b, and 102c and other devices. This may be made easier. UPF176a and UPF176b also WTRU102a, 102b and 102c provide access to other types of packet data networks. They may provide. For example, other network 112 is an Ethernet network or It may be any type of network that exchanges data packets. UPF176 a and UPF176b receive traffic from SMF174 via the N4 interface. Steering rules may be received. UPF176a and UPF176b are N6 By connecting the packet data network via the interface, or via the N9 interface By connecting with each other and with other UPFs on each other, the packet data network You may provide access to the packet data network. In addition, UPF176 handles packet routing and forwarding, and policy rules. Implementation, quality of service processing for user plane traffic, downlink packets It can also play a role such as buffering.

[0275] The AMF172 can also be connected to the N3IWF199 via the N2 interface, for example. It may be. N3IWF is, for example, a wireless interface not defined by 3GPP. Through this technology, the connection between WTRU102c and the 5G core network 170 is facilitated. AMF interacts with RAN105 in the same or similar way as N3I. It may interact with WF199.

[0276] The PCF184 is connected to the SMF174 via the N7 interface, and the N15 interface It connects to the AMF172 via the faceplate, and applications are connected via the N5 interface. The Application Function (AF) 188 may be connected. N15 and N5 The interface is not shown in Figure 12D. PCF184 is AMF172 and By providing policy rules to control plane nodes such as SMF174, the control plane nodes It may be possible for the government to enforce these rules. PCF184 is an AMF N1 in Policies can be delivered to WTRU102a, 102b, and 102c via the TAFFACE. To that end, the policy for WTRU102a, 102b, and 102c is applied to AMF172. - may be sent. Subsequently, the policy will be WTRU102a, 102b, and 102 It may be enforced or applied under c.

[0277] UDR178 also functions as a repository for authentication credentials and enrollment information. Good. UDR allows network functionality to add to and read data within the repository. It may be connected to a network function so that it can be modified. For example, UDR1 78 may be connected to PCF184 via the N36 interface. Similarly, UDR 178 may also be connected to NEF196 via the N37 interface, UDR178 It may also be connected to the UDM197 via the N35 interface.

[0278] The UDM197 serves as an interface between the UDR178 and other network functions. It may work. UDM197 allows UDR178 access to network functions. This is also possible. For example, UDM197 can be connected to AMF172 via the N8 interface. Even if the UDM197 is connected to the SMF174 via the N10 interface, Good. Similarly, UDM197 connects to AUSF190 via the N13 interface. It is also possible that UDR178 and UDM197 are tightly integrated.

[0279] The AUSF190 performs authentication-related operations and communicates via the N13 interface to the UDM1 Connect to 78, and then connect to AMF172 via the N12 interface.

[0280] NEF196 provides capabilities and services within the 5G core network 109. The application will be made public via the AF188 API interface. This may be done as follows. The NEF may also be connected to the AF188 via the N33 interface. In order to expose the capabilities and services of the 5G core network 109, other networks You may connect to the work function.

[0281] Application function 188 is compatible with the network function of the 5G core network 109. They may interact. The interaction between application function 188 and network function is This may occur via a direct interface or via NEF196. Even if application function 188 is considered part of the 5G core network 109 Often, or outside the 5G core network 109, mobile network operators It may be implemented by companies that have business relationships with the company.

[0282] Network slicing is a method used by mobile network operators to control the network infrastructure of their network infrastructure. It can be used to support one or more "virtual" core networks behind the face. This is a mechanism that "slashes" the core network into one or more virtual networks. "Issing" means different services running across different RANs or a single RAN. This relates to supporting the type. Network slicing allows operators to Sina in various markets where diverse requirements such as functionality, performance, and isolation are demanded. Create a customized network to provide the best solution for Rio. It is possible.

[0283] 3GPP is making 5G core networks compatible with network slicing. It is being designed. Network slicing is a very diverse and sometimes This presents a diverse range of 5G use cases that demand extreme requirements (e.g., massive IoT). (critical communications, V2X, and enhanced mobile broadband) It is an excellent tool that can be used to port. It uses network slicing technology. Otherwise, each use case will have its own set of performance, scalability, and availability requirements. If present, the network architecture can efficiently support a wider range of use cases. It may not be flexible and scalable enough to port. Furthermore, new networks The implementation of network services should be carried out more efficiently.

[0284] Referring again to Figure 12D, in the network slicing scenario, WTRU102 a, 102b, or 102c connect to the AMF172 via the N1 interface. AMF may be part of one or more slices. Connecting or communicating with TRU102a, 102b, or 102c to one or more UPF1 It may be compatible with 76a and 176b, SMF174, and other network functions. UPF176a and 176b, SMF174, and other network functions They may be parts of the same slice or different slices. When they are part of Rice, they have different computing resources, security In the sense that credentials can be used, they are separate from each other. .

[0285] The core network 109 may facilitate communication with other networks. For example, Core network 109 is connected to PSTN 108. IP multimedia subsystem (IMS) servers and other IPs that function as interfaces. It may include a gateway, or it may communicate with one. For example, a core network 109 is a short message service that enables communication via the Short Message Service. This may include a Short Message Service (SMS) service center, Alternatively, it may communicate with it. For example, the 5G core network 109 may communicate with WTRU102a Non-I between 102b and 102c and the server or application function 188 The exchange of P data packets may be facilitated. Furthermore, the core network 170 WT RU102a, 102b, and 102c are owned by other service providers Access to network 112, which may include other wired or wireless networks being operated. You may offer a meal.

[0286] As described herein and shown in Figures 12A, 12C, 12D, or 12E Core network entities are defined in certain existing 3GPP specifications for those entities. Although identified by the given name, in the future, those entities and functionalities may be It may be identified by other names, and a specific entity or function may be referred to in future 3GPP It is understood that this can be combined with future specifications issued by 3GPP, including NR specifications. Therefore, it is explained in Figures 12A, 12B, 12C, 12D, or 12E. Specific network entities and functionalities explicitly shown are for illustrative purposes only. The subject matter provided, disclosed and claimed herein is as currently defined. This may be embodied or implemented in any similar communication system, regardless of how it may be defined in the future. It is understood that this is the case.

[0287] Figure 12E shows the implementation of the NR-U LBT MAC procedure as described herein. An exemplary communication system 111 is shown in which a system, method, or apparatus may be used. TEM111 includes Wireless Transceiver Units (WTRUs) A, B, C, D, E, F, and Base Station gNB. 121, V2X server 124, and Roadside Unit (RSU) 123a, and may include 123b. In practice, the concepts presented herein are any number of W Applicable to TRU, base station gNB, V2X networks, or other network elements. One or some or all WTRU A, B, C, D, E, and F are accessories. Network coverage may be outside the scope of WTRU A, B, and C. These form a V2X group, of which WTRU A is the group lead, and W TRU B and C are group members.

[0288] WTRU A, B, C, D, E, and F are those that have access to network coverage. If located within J131, they communicate with each other via gNB121 and Uu interface 129. This may also be the case. In the example in Figure 12E, WTRUs B and F are access network coverage. As shown in 131. WTRU A, B, C, D, E, and F are those which they access It is under network coverage 131, or access network coverage Regardless of whether it is outside of 131, interface 125a, 125b, or 128 Which slide link interface (e.g., PC5 or NR PC5) can be used to communicate with each other? Direct communication is also possible. For example, in the example in Figure 12E, access network coverage WRTU D, located outside coverage 131, communicates with WTRU F, located within coverage 131. .

[0289] WTRU A, B, C, D, E, and F are equipped with Vehicle-to-Network Communication (V2N) 13 3 or via side link interface 125b, RSU 123a or 123 b may communicate. WTRU A, B, C, D, E, and F are vehicle-versus-infrastructure. Even if you communicate with the V2X server 124 via the Rakucha communication (V2I) interface 127 Good. WTRU A, B, C, D, E, and F are vehicle-to-pedestrian communication (V2P) interfaces. Communication with another UE may be conducted via face 128.

[0290] Figure 12F is the WTRU of Figures 12A, 12B, 12C, 12D, or 12E. 102, or as described herein, such as in Figure 1 (e.g., UE101), N Wireless communication according to systems, methods, and apparatus that implement the RU LBT MAC procedure. And a block of an exemplary apparatus or device WTRU102 that can be configured for operation This is a diagram. As shown in Figure 12F, the exemplary WTRU102 has a processor 118, Lanceiever 120, transmitting / receiving element 122, speaker / microphone 124, keypad 1 26, Display / Touchpad / Indicator 128, Non-removable memory 130 Removable memory 132, power supply 134, Global Positioning System (GPS) System: GPS) may include a chipset 136 and other peripherals 138. It is understood that TRU102 may include any subcombination of the aforementioned elements. It is likely that base stations 114a and 114b, or base stations 114a and 114b Nodes that can be represented, for example, but not limited to, base station equipment (BTS), no Node B, Site Controller, Access Point (AP), Home Node B, Advanced Node B (e node B), Home-type node B (HeNB), Home-type node B gateway The next-generation node B (g node B), and proxy nodes, in particular, are shown in Figure 12F. This may include some or all of the elements illustrated in the figure, and the NR-U as described herein. Exemplary implementations of the disclosed system and method for performing the LBT MAC procedure That's good too.

[0291] Processor 118 includes general-purpose processors, dedicated processors, conventional processors, and digital processors. Digital Signal Processor (DSP), multiple microprocessors, One or more microprocessors, controllers, or microcontrollers associated with the DSP core. - Application Specific Integrated Circuit (ASIC) ), Field Programmable Gate Array (FP) GA) circuits, other types of integrated circuits (ICs), state machines It may also be something like n. Processor 118 is responsible for signal coding, data processing, power control, input / output Force processing, or any other function that enables the WTRU102 to operate in a wireless environment. The operation may be performed. The processor 118 may be coupled to the transceiver 120, The lanceiver may be coupled to the transmit / receive element 122. Figure 12F shows the processor 118 Although the transceiver 120 is shown as a separate component, the processor 11 The 8 and transceiver 120 may be integrated together in an electronic package or chip. This will be understood.

[0292] The UE's transceiver element 122 connects to the base station via air interfaces 115 / 116 / 117. To and from a station (for example, base station 114a in Figure 12A), or via air interface 115d Configure to transmit or receive signals to or from another UE via / 116d / 117d It may be configured such that, for example, the transmitting / receiving element 122 is configured to transmit or receive an RF signal. An antenna may be constructed. The transmitting / receiving element 122 may be, for example, IR, UV, or It may be an emitter / detector configured to transmit or receive a visible light signal. The receiving element 122 may be configured to transmit and receive both RF signals and optical signals. The transmitting / receiving element 122 transmits or receives any combination of wireless or wired signals. It will be understood that it may be structured in a certain way.

[0293] Furthermore, although the transmitting / receiving element 122 is shown as a single element in Figure 12F, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU10 2 may employ MIMO technology. Therefore, WTRU102 is an air interface Two or more transceiver elements for sending and receiving wireless signals via 115 / 116 / 117 122 (for example, multiple antennas) may be included.

[0294] The transceiver 120 modulates the signal to be transmitted by the transmitting and receiving element 122, and transmits and receives The signal received by the signal element 122 may be configured to demodulate the signal. The WTRU102 may have multimode capability. Therefore, the transceiver 120 is WTRU102 which supports multiple RATs, for example, NR and IEEE802.11 or It communicates via NR and E-UTRA, or different RRH, TRP, RSU, if Multiple beams to enable communication between nodes using the same RAT, It may include a transceiver.

[0295] The WTRU102 has a processor (118), a speaker / microphone (124), and a keypad. 126, or display / touchpad / indicator 128 (e.g., LCD display) Liquid Crystal Display (LCD) display unit, or organic light-emitting display unit. Combined with an OLED (Organic Light-Emitting Diode) display unit. It may be set up and user input data may be received from these. Processor 118 is Also, speaker / microphone 124, keypad 126, or display / touch User data may be output to the Chipad / Indicator 128. Furthermore, processor 1 18 is any type, such as non-removable memory 130 or removable memory 132. Information may be accessed from the appropriate memory of the device, and data may be saved to memory. Non-removable Blue Memory 130 is Random-Access Memory (RAM), Read-only memory (ROM), hard disk, or any other It may include a type of memory storage device. Removable memory 132 is a member. Subscriber Identity Module (SIM) card, memory stick This may include Secure Digital (SD) memory cards, etc. The processor 118 is suitable for cloud or edge computing platforms. On a server or home computer (not shown) that is being stored, WTRU102 Information may be accessed and data stored from memory that is not physically located there. Rossessa 118 is used in some of the examples described herein for LBT FCs. Depending on whether the setup was successful or unsuccessful, the display or indicator will show It may also be configured to control lighting patterns, images, or colors on the 128, and This shows the status of the NR-U LBT MAC procedure and related components in a different way. It may be configured as follows: Control lighting pattern on display or indicator 128 The images or colors shown or described in this specification are not representative of the actual figures (e.g., Reflects the state of either the method flow or component in Figures 1-10, etc. This specification includes messages and procedures for the NR-U LBT MAC procedure. It is disclosed. The message and procedure are disclosed to the user regarding the input source (e.g., speaker / Microphone 124, Keypad 126, or Display / Touchpad / Indicator Requesting resources via Caterer 128 and other things that may be displayed on Display 128 Among these, the following are used to request, configure, or query NR-U LBT MAC procedure-related information. It may be extended to provide an interface / API.

[0296] The processor 118 receives power from the power supply 134 and powers the other components in the WTRU 102. Power supply 134 may be configured to distribute or control power to the WTRU. It may be any suitable device for supplying power to 102. For example, power supply 13 Item 4 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0297] Furthermore, the processor 118 may be coupled to the GPS chipset 136, The topset 136 contains location information (e.g., longitude and) about the current location of WTRU102. It may be configured to provide latitude, in addition to information from the GPS chipset 136. Alternatively, WTRU102 is a base station (e.g., base stations 114a, 11 4b) Location information may be received via air interface 115 / 116 / 117. or based on the timing of signals received from two or more nearby base stations The position may be determined. WTRU102 determines the position using any appropriate position determination method. It will be understood that it is permissible to obtain the information.

[0298] The processor 118 may also be coupled to other peripherals 138, and these peripherals Device 138 provides one or more additional features, functionality, or wired or wireless connectivity. The above may include software or hardware modules. For example, peripheral device 13 8 includes various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, and electronic sensors. Pass, satellite transceiver, digital camera (for photos or video), universal serial Universal Serial Bus (USB) port or other interconnection interface Vibration devices, TV transceivers, hands-free headsets, Bluetooth (Registered Trademark) Module, Frequency Modulated (FM) Wireless Unit, De Digital music player, media player, video game player module, internet This may include web browsers, etc.

[0299] WTRU102 is used in sensors, home appliances, smartwatches, or smart wear. Wearable devices, medical or electronic health devices, robots, industrial equipment, drones , within other devices or equipment such as automobiles, trucks, trains, or airplanes It may be included. WTRU102 may constitute one of the peripheral devices 138. Such devices or It may be connected to other components, modules, or systems of the device.

[0300] Figure 12G is a block diagram of an exemplary computing system 90, which is, One or more of the communication networks shown in Figures 12A, 12C, 12D, and 12E The apparatus, as well as the devices shown in Figures 1 to 10 and described and claimed herein. NR-U LBT MAC procedures, including stems and methods, are RAN103 / 104 / 10 5. Core Network 106 / 107 / 109, PSTN 108, Internet 110 , other networks 112, or specific networks in network services 113 It can be embodied in a code or functional entity, etc. Computing system 90 is It consists of a computer or server and is primarily controlled by computer-readable instructions. Computer-readable instructions may also be in the form of software, or similar. Regardless of where the software is stored or by what means it is accessed Good. Such computer-readable instructions are executed within processor 91, and the computer... The operating system 90 may be operated. The processor 91 is a general-purpose processor, dedicated Processor, conventional processor, digital signal processor (DSP), multiple micro- One or more microprocessors, controllers, and microphones associated with the processor and DSP core. Locomotive controllers, application-specific integrated circuits (ASICs), field-programmable gates Array (FPGA) circuits, other types of integrated circuits (ICs), state machines, etc. It is also acceptable. The processor 91 performs signal coding, data processing, power control, input / output processing, and This includes any other functionality that would enable the WTRU90 to operate on telecommunications networks. This may be done. The coprocessor 81 has different options than the main processor 91. It is a processor that can perform additional functions or assist processor 91. 91 or coprocessor 81 receives or responds to LBT failures, etc., NR-U LBT Receiving and generating data related to the methods and apparatus disclosed herein for MAC procedures. They may also be processed.

[0301] During operation, the processor 91 fetches, decodes, and executes instructions, and computes The system's main data transfer path is the system bus 80, which connects to other resources. Information is transferred via this system bus. Such a system bus is used within the computing system 90. It connects components and defines the medium for data exchange. System bus 80 is typical. In terms of data lines, there are data lines for sending data and address lines for sending addresses. This also includes control lines for sending interrupts and operating the system bus. An example of a system bus 80 like this is the Peripheral Component Interconnect (Pe It is a ripheral component interconnect (PCI) bus.

[0302] The memory connected to the system bus 80 is random access memory. Memory (RAM) 82 and Read Only Memory (ROM) 93 Includes. Such memory includes circuits that can store and retrieve information. ROM9 3 generally includes saved data that cannot be easily modified. The data stored in RAM82 , which can be read by processor 91 or other hardware devices, or It can be changed. Access to RAM82 or ROM93 is to the memory controller92. Therefore, it may be controlled. When an instruction is executed, the memory controller 92 controls the virtual address A memory controller may provide an address translation function that converts responses to physical addresses. 92 also isolates processes within the system, separating system processes from user processes. A memory protection function may be provided to release the program. RAM can only access memory mapped by the virtual address space of that process. Unless memory sharing between processes is configured, the virtual address of another process may be affected. It is not possible to access memory within the space.

[0303] Furthermore, the computing system 90 receives instructions from the processor 91 to the printer 9 4. Communicate with peripherals such as keyboard 84, mouse 95, and disk drive 85. It may also include a peripheral device controller 83 that plays a role in this.

[0304] The display 86, controlled by the display controller 96, is a computer This is used to display the visual output generated by the 90-inch display system. The visual output includes text, graphics, animated graphics, and Video may be included. Visual output is a graphical user interface. It may be provided in the form of a User Interface (GUI). Display 86 is a CRT Base video displays, LCD-based flat panel displays, gas plasma It may be implemented as a flat panel display or touch panel. The display controller 96 generates a video signal to be sent to the display 86. Includes the necessary electronic components.

[0305] Furthermore, the computing system 90 is shown in Figures 12A, 12B, 12C, and 12 D, or Figure 12E, RAN103 / 104 / 105, Core Network 106 / 1 07 / 109, PSTN108, Internet 110, WTRU102, or other The computer connects to an external communication network or device, such as network 112. Used to connect the computing system 90, the computing system 90 uses them It may be possible to communicate with other nodes or functional entities in the network, for example. It may include a communication circuit such as a wireless or wired network adapter 97. This can be used alone or in combination with the processor 91, in the specific configurations described herein. It may be used to perform sending and receiving steps for a place, node, or functional entity. stomach.

[0306] Any or all of the apparatus, systems, methods, and processes described herein However, computer executable instructions stored on a computer-readable storage medium (for example, programme This instruction may be embodied in the form of a Gram code, and this instruction is on processor 118 or 91 When executed by a processor such as the system described herein, the processor will be given the system described herein. It is understood that the methods and processes described herein are to be implemented or carried out. Specifically, this specification Any of the steps, actions, or functions described in this document may not be performed on a wireless or wired network. On the processor of a device or computing system configured for work communication It may be implemented in the form of such computer executable instructions that are executed. A readable storage medium is any non-temporary (e.g., tangible or physical) medium for storing information. Volatile and non-volatile, removable and removable (implemented by appropriate methods or techniques) This includes media that are impossible to store, but such computer-readable storage media do not contain signals. Computer-readable storage media include RAM, ROM, EEPROM, flash memory, and Other memory technologies include CD-ROM and Digital Versatile Disk. DVD) or other optical disc storage, magnetic cassette, magnetic tape, magnetic disc To store the desired information in a magnetic storage device or other magnetic storage device. Other tangible or physical objects used for and accessible by computing systems This includes, but is not limited to, rational media.

[0307] Preferred methods, systems, or methods for the NR-U LBT MAC procedure, which are the subject of this disclosure. When describing the apparatus as shown in the diagram, specific terminology is used for clarity. However, And the subject matter described in the claims is not limited to the specific terms thus selected. Not illustrated, each specific element operates in a similar manner to achieve a similar purpose. It should be understood that this includes the technical equivalent of [the original].

[0308] The various technologies described herein include hardware, firmware, and software. A, or a combination thereof, may be implemented as needed. Hardware, firmware, and software are various notes in communication networks. The device may be permanently stationed in a location. The device implements the method described herein. To that end, they may operate individually or in combination with each other. "device", "network device", "node", "device", "network node" Terms such as "" may be used interchangeably. Furthermore, the use of the word "or" in this specification Unless otherwise specified in the text, it is generally used comprehensively.

[0309] This written specification uses examples to disclose the invention, including the best mode. Furthermore, you may create and use any device or system, and any embedded one. To enable those skilled in the art to implement the invention, including by enforcing the law. To obtain a patent. The extent to which this is possible is defined by the claims and other embodiments that a person skilled in the art could conceive of (for example) If, for example, a step is skipped between the exemplary methods disclosed herein, This may include combining or adding steps. For example, if a structural element has no different meaning from the literal language of the claims, Or, if it includes equivalent structural elements that are substantially different from the literal language of the claims, It is intended to be included within the scope of the claim.

[0310] This written specification uses examples to disclose the subject matter, including the best mode. Furthermore, you may create and use any device or system, and any incorporated method To enable those skilled in the art to carry out the subject matter, including performing the following actions. The scope is defined by the claims, for example, other embodiments that a person skilled in the art could conceive of ( For example, the steps between the exemplary methods disclosed herein, particularly in Figures 2 to 10, This includes (tippling, combining steps, or adding steps). It may appear that such other embodiments are not in the literal language of the claims. If it has structural elements, or if it is substantially different from the literal language of the claims If such structural elements are included, they are intended to be included in the claims.

[0311] The methods, systems, and apparatus described herein, among other things, include means NR- A U LBT MAC procedure may be provided. Due to LBT failure of the SR procedure, 1) alternative BW This could lead to: 1) switching to P, 2) initiating the RA procedure, or 3) maintaining the SR pending state. . Due to LBT failure in the DRX procedure, 1) the duration or inactive timer 1) Extension, 2) Onduation or inactive timer, MCOT, CWS, or This could lead to either alignment with CCA, or 3) application of short cycles. Due to the LBT failure in procedure A, 1) generating or sending statistical reports, or 2) Setting a prohibit timer, which can lead to a BWP procedure LBT failure, 1 ) Extend the BWP inactive timer, or 2) Switch to an alternative BWP. This may lead to... This paragraph and the following paragraph (or related paragraphs in this specification) All combinations of the lagraf (including the removal or addition of steps) are intended.

[0312] Methods, systems, and apparatus, in particular, as described herein, means N RU LBT MAC procedures may be provided. Methods, systems, computer-readable storage. The medium or device is, in particular, a random access procedure, SCell activation / deactivation. Active activation procedure, intermittent reception procedure, scheduling request procedure, buffer status reporting procedure Order, logical channel prioritization procedure, UE and NB MAC procedure adjustment, power head routing The system has means for determining LBT failure with respect to the reporting procedure or the bandwidth partial operation procedure. A method, system, computer-readable storage medium, or apparatus is a preamble transmission counter. If the value is greater than 1, a notification to pause the power ramping counter has been received from a lower layer. A method to determine that the selected SSB has not been changed and that no LBT failure has been detected. Based on the stage and the judgment step, set the preamble power ramping counter to 1. It has means of providing an incrementing instruction. Method, system, computer-readable The storage medium or device retrieves the LBT status associated with the user equipment (UE). (For example, receiving from a remote device or using a local sensor) To detect, and to generate an LBT reporting MAC control element (LBTR MAC CE) This may include Listen-Before-Talk (LBT) and Media Access Control (M). Having means for operation associated with AC, LBTR MAC CE is LBT form May include a description of the state. Methods, systems, computer-readable storage media, or devices may include LB It has means for providing T timing information to the MAC layer. LBT timing information is clear Includes the channel evaluation period, maximum channel occupancy time, or contention window. The method, system, computer-readable storage medium, or device may be a user-defined equipment (UE). ) to detect a first threshold for LBT failure or a second threshold for LBT success associated with ) This includes adjusting the DRX settings based on the detection of a first or second threshold. It can be seen, associated with Listen-Before-Talk (LBT) and Intermittent Reception (DRX). It has means for operation. DRX settings are based on duration or inactivity. It may contain M. The method, system, computer-readable storage medium, or apparatus of the present invention The base station has means of providing information to the UE, and the information is associated with the base station or the UE. It may include downlink information regarding the access channel. The UE may include uplink information. Information related to this may be automatically detected. Based on uplink information or downlink information. The UE may perform a different MAC procedure. In one embodiment, the UE performs an uplink procedure. Use the report and downlink information to determine whether or not to report an LBT failure, or which procedure to follow. You may decide whether or not to report whether or not you are affected. (Method, system, computer-readable) The storage medium or device acquires downlink information detected by the base station, and down Link information is associated with the base station's channel access and downlink listening. The system may include a message indicating a fortalk failure, acquire uplink information, and the uplink information is stored in the device. Detected by, the uplink information is associated with the device's channel access, up This may include an indication of a Listen Before Talk failure on the uplink, and the Listen Before Talk failure on the uplink. Display of before-talk failure or downlink listening display of before-talk failure Based on this, it has means to perform media access control operations. Uplink listening Listen to BeforeTalk failed (or succeeded), or downlink Listen to BeforeTalk Failure (or success) is determined by the scheduling request procedure, buffer status reporting procedure, and logic. Channel prioritization procedure, intermittent reception procedure, SCell activation or deactivation Activation procedure, power headroom reporting procedure, random access procedure, listenbefort This can be detected by a work report procedure or a bandwidth partial operation procedure. All combinations of the following paragraphs (or related paragraphs in this specification) (step This is intended to include the deletion or addition of elements.

[0313] A method, system, computer-readable storage medium, or device is a tool for managing MAC procedures. It has steps. A method, system, computer-readable storage medium, or apparatus is downlink It has means to acquire information, and downlink information is channel access (to the base station equipment) It is associated with the system and has means for acquiring uplink information (e.g., user equipment), The link information is associated with the device's channel access (e.g., to a base station). Based on uplink or downlink information, media access control operations are performed. To be carried out. Downlink information may be detected by the base station. Uplink information is It may be detected by the device. Channel access information is in listen-before-talk operation. This may also be related information. The execution of media access control operations is a non-abandonment of the bandwidth portion. This may include extending the active timer, and the uplink or downlink information may be extended. , including uplink or downlink listen-before-talk failure information. UL also It is possible to switch BWP when DL LBT failure information is received (BWP operation MA) Procedure C is independent of the switchover, and the switchover is to a pre-configured alternative BWP. (Also good). Executing media access control operations extends the random access response window. This may include, and uplink or downlink information may be uplink or Includes downlink listen-before-talk failure information. Actual media access control operation. The line does not increment the preamble send counter, or the conflict resolution timer This may include extending the uplink or downlink information, and the uplink information may extend to This includes downlink listen-before-talk failure information. Media access control operation The execution may include maintaining or reducing power ramping, and Uplink or downlink information is available before listening to the uplink or downlink. - Includes information on talk failures. The disclosed subject is to avoid stopping the RA procedure due to LBT failure. Furthermore, if the preamble transmission LBT failure threshold is exceeded, an RA problem is indicated in the upper layers. The RA procedure may be considered unsuccessful. The execution of the media access control operation may be considered unsuccessful. Based on determining whether there is a failure or success in the before-talk, the physical app This may include determining that the SR control channel resource is valid, which is a SR method. Even if the sequence is associated with reaching the LBT failure threshold and releasing the PUCCH resource, i. CCA, MCOT, or CWS information may be provided together with LBT success information. Furthermore, if LBT success includes this CCA, MCOT, or CWS information, success is recognized as failure. This means that it was not present, and therefore may be equivalent to an LBT failure indication. LBT is referenced. In this case, it can be determined by the LBT success indicator. In DRX, when LBT fails, show This may be covered by applying a tocycle or extending the active time. Furthermore, inactivation may be prevented. When restarting the activity timer, what is the number of times LBT failures extend the active time? There may be limitations. Furthermore, adjust the DRX settings when LBT fails. This is Duration, inactivity, or associated with the DRX cycle timer Regarding LBTR, when LBT fails or succeeds, the success or failure of LBT is known. If the threshold is exceeded over the specified period, a report to the base station is triggered and the report is sent. Furthermore, a ban timer is set to limit the frequency of reports, and reports include CCA, MCOT, and This may include timing information such as CWS. SR failure triggers the RA procedure (for example, LBT failure triggers the SR transmission counter...) (Achieved by limiting the number of times it does not increment), SR prohibited when LBT fails. If the stop timer is not set, or if LBT fails, the SR hold may be maintained. The execution of the cess control operation is indicated by a List Before Talk failure display for scheduling request transmission. Based on this, determine if the scheduling request has failed, or open a random access procedure. This may include initiating the process. The execution of media access control operations is subject to scheduling requests. Based on the transmission listen-before-talk failure indication, determine if the scheduling request has failed. This may include, or switching bandwidth portions. Media access control The operation involves extending the MAC procedure timer or counter of the device, and the MAC procedure The operation is affected when achieved by uplink or downlink channel access. To provide resonance and enable performance similar to licensed operation, or for the device to access the channel This may include reporting the information to the base station. (This paragraph and the next paragraph) (or any combination of the relevant paragraphs of this specification) (deletion or addition of steps) (including) is intended.

[0314] A method, system, computer-readable storage medium, or device is a tool for managing MAC procedures. It has stages. A method, system, computer-readable storage medium, or apparatus is connected from a base station. The device has means for acquiring downlink information, and the downlink information is used for channel access of the device. Associated, uplink information is acquired, and the uplink information is detected by the device. Based on uplink or downlink information, media access control operations are performed. It has the means to perform the media access control operation, which involves inactive bandwidth portion. This may include extending the timer, and the uplink or downlink information may be up May include Listen Before Talk failure information for links or downlinks. The execution of access control actions may include extending the random access response window. Often, uplink or downlink information is used for uplink or downlink connections. It may include information about Sunbeforetalk failures. Increment the amble transmission counter, or extend the conflict resolution timer. It may include, and uplink or downlink information may include uplink or downlink It may include information about the Listen Before Talk failure of the link. The row maintains or decreases power ramping (for example, does not increase it). This may include uplink or downlink information, and uplink or downlink information may include uplink or downlink information. It may include information about ListenBeforeTalk failures in Unlink. Media access control The execution of the operation will result in a Listen Before Talk failure or failure success (for example, threshold success or failure). Based on determining whether or not there is a trigger (by), physical uplink control This may include determining whether the channel (PUCCH) resource is valid. The execution of access control operations may include adjusting intermittent reception operations, uplink Alternatively, downlink information is signaled from the base station in an intermittent reception cycle, clearing Channel evaluation period, maximum channel occupancy time, or downlink listen before talk duration It may include power instructions. Performing media access control operations is required for intermittent reception operations. Furthermore, adjust the active time to match the maximum channel occupancy period. Intermittent reception during the contention window size period or clear channel evaluation period This may include applying the maximum channel occupancy period. This may include adjusting the active timer or the inactive timer. Performing access control operations is affected by uplink or downlink information. This may include reporting media access control actions that receive media access control. The execution of your actions is affected by media elements such as uplink or downlink information. This may include reporting access control operations, and uplink or downlink information may be provided. This may include uplink or downlink listen-before-talk failure information. The execution of a media access control operation is performed when one or more of the media access control operations are A This includes reporting how it is affected by uplink or downlink information. That's fine. Executing a media access control operation is one of the media access control operations. Report how one or more of these are affected by uplink or downlink information. This may include, and uplink or downlink information may be uplink or It may also include downlink listen-before-talk failure information. Generally, LBT failures Uplink or downlink information, such as success, is disclosed herein, among other things. This can trigger MAC operations such as those described above. The device may be a user device. All combinations of laphrases (or related paragraphs in this specification) (deletion of steps) (or including additions) is intended.

Claims

1. It is a device, Processor and The processor comprises a memory coupled to the processor, and the memory is controlled by the processor When executed, the processor stores executable instructions that enable the operation, and the operation teeth, The acquisition of downlink information, which is obtained by the base station. The downlink information is detected and associated with the channel access of the base station. This includes the display of a failed ListenBeforeTalk in Unlink, The acquisition of uplink information, wherein the uplink information is obtained by the device. The uplink information is detected and associated with the channel access of the device. This includes displaying a failure message for the "Click Listen Before Talk" function. The display of the uplink's Listen Before Talk failure or the downlink's Listen Before Talk failure Based on the display of Sunbeforetalk failure, perform media access control actions. 、 A device including a device.

2. The execution of the aforementioned media access control operation is performed for the scheduling request procedure, alternative band The apparatus according to claim 1, including switching to a bandwidth portion.

3. The execution of the media access control operation is performed for the scheduling request procedure, The apparatus according to claim 1, comprising initiating an access procedure.

4. The execution of the aforementioned media access control operation is performed for the scheduling request procedure. The apparatus according to claim 1, comprising keeping a queuing request in a pending state.

5. The execution of the media access control operation is performed for the intermittent reception procedure, on duration The apparatus according to claim 1, further comprising extending the inactive timer.

6. The execution of the media access control operation is performed for the intermittent reception procedure, on duration Alternatively, an inactive timer, clear channel evaluation, maximum channel occupancy time, or con The apparatus according to claim 1, comprising matching the tension window size.

7. The execution of the media access control operation is performed for the intermittent reception procedure, short cycle The apparatus according to claim 1, including the application of IMA.

8. The execution of the aforementioned media access control operation is performed using alternative bandwidth for random access procedures. The apparatus according to claim 1, including switching to a portion.

9. The execution of the aforementioned media access control operation is for the random access procedure, To provide a random access problem display to the upper layers, The random access procedure is indicated as unsuccessful, The apparatus according to claim 1, including the following:

10. The execution of the aforementioned media access control operation is for the Listen Before Talk reporting procedure, A claim comprising providing a report including statistics on ListenBeforeTalk failures or successes. The apparatus described in 1.

11. The execution of the aforementioned media access control operation is for the Listen Before Talk reporting procedure, The apparatus according to claim 1, comprising setting a prohibition timer for setting the frequency of reporting.

12. The execution of the aforementioned media access control operation is a bandwidth-partial non-access operation for bandwidth-partial procedures. Claim 1, which includes extending the tive timer or switching to an alternative bandwidth portion. The device described above.

13. The acquisition of downlink information, which is obtained by the base station. The downlink information is detected and associated with the channel access of the base station. This includes the display of a failed ListenBeforeTalk in Unlink, The process involves acquiring uplink information, and the uplink information is detected by the device. The uplink information is then associated with the channel access of the device, and up This includes displaying a link listening before talk failure, The display of the uplink's Listen Before Talk failure or the downlink's Listen Before Talk failure Based on the display of Sunbeforetalk failure, perform media access control actions. 、 Methods that include...

14. Failure of the uplink's listen before talk or the downlink's listen before talk Fortalk failures occur in the scheduling request procedure, buffer status reporting procedure, and logical chat. Channel prioritization procedure, intermittent reception procedure, SCell activation or deactivation. Modification procedure, power headroom reporting procedure, random access procedure, listen before talk The method according to claim 13, as detected by a reporting procedure or a bandwidth partial operation procedure.

15. The computer having a computer program stored on a computer-readable storage medium A computer-readable storage medium, wherein the computer program is stored in a data processing unit. It is possible to run the computer program, and the computer program is executed by the data processing unit. When the data processing steps according to any one of claims 13 to 14 are performed A computer-readable storage medium adapted for execution by a unit.

Images