NR-U LBT MAC procedure

Abstract

To provide methods, apparatuses and systems associated with existing MAC procedures that operate at unlicensed frequencies, have Listen Before Talk (LBT) procedures for gaining access to a channel without interfering with existing traffic, and are useful in maintaining proper operation and performance of the MAC procedures.SOLUTION: A bandwidth part (BWP) operation procedure comprises: detecting one or more LBT failures; based on the detected failures, extending a BWP inactivity timer so as to avoid switching to an initial or default BWP if UL or DL data to be scheduled is present; and, based on the detected failures, switching to an alternate bandwidth part.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application is a continuation of the application filed on September 26, 2018, entitled "NR-U LBT MAC Proc No. 62 / 736,816 entitled "Third Edition," and U.S. Provisional Patent Application No. 2018 / 10 / 184,499 entitled "Third Edition," A patent application entitled "NR-U LBT MAC Procedures" was filed on the 31st of this month. This application claims the benefit of U.S. Provisional Patent Application No. 62 / 753,579, the contents of both applications being incorporated herein by reference. The present application is incorporated by reference. [Background technology]

[0002] LTE Licensed Assisted Access 3GPP Release 16 NR is a Supports unlicensed operation without using a previously available license-assisted connection. In previous releases, there was always a licensed connection, which resulted in high performance with unlicensed connections. There was no need to ensure a high level of QoS.

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

[0004] A carrier group with at least one SCell operating in an unlicensed frequency band Ligation is Licensed-Assisted Access (LAA) Therefore, in LAA, the set of serving cells configured for the UE is called shall have at least one UE operating in unlicensed spectrum according to frame structure type 3. Always includes a SCell, also called an LAA SCell. Unless otherwise specified, The LAA SCell functions as a regular SCell.

[0005] The LAA eNB and UE must perform a listen before transmitting on the LAA SCell. Apply Lightning-Band-Talk (LBT). When LBT is applied, the transmitter listens to the channel. / Senses and determines if the channel is free or busy. If so, the transmitter may transmit, otherwise it does not transmit. The eNB may transmit channel access signals of other technologies for the purpose of LAA channel access. If used, 3GPP TS 36.321 (E-UTRA), Media Access Control LAA of the Medium Access Control (MAC) Protocol Specification, V15.2.0 [1] The maximum energy detection threshold requirements shall still be met. PP TS 36.321, (E-UTRA), Media Access Control (MAC) Protocol The col specification may be included in V15.2.0. Summary of the Invention

[0006] Maintaining proper operation and performance of MAC procedures, including when operating in unlicensed spectrum The present disclosure provides a method, apparatus, and system associated with existing MAC procedures that can be maintained. When an LBT failure occurs in NR-U, the existing MAC procedure is inappropriate. may perform unintended actions that could result in unintended consequences.

[0007] This Summary of the Invention is presented in a simplified form that is further described in the Detailed Description below. This Summary is provided to introduce a selection of concepts in a format that is consistent with the claimed subject matter. It is not intended to identify key or essential features of the subject matter, and Nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, claimed subject matter may be derived from any or all of the methods described anywhere in this disclosure. Not bound by restrictions that solve all disadvantages.

[0008] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which: do. [Brief explanation of the drawings]

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

[0010] For example, proper operation and performance of MAC procedures when operating in unlicensed spectrum. The present invention provides a method, apparatus, and system associated with MAC procedures that help maintain the functionality of In case of LBT failure in NR-U, the existing MAC procedure is They may perform inappropriate actions and have unintended consequences.

[0011] Specific issues related to the MAC procedure addressed herein include, among others, the bandwidth portion Minute (Bandwidth Part: BWP) operating procedure, random access procedure, power headroom Power Headroom Reporting (PHR) procedure, Scell ​​activation or deactivation Activation procedure, discontinuous reception procedure, Scheduling Request (SR) procedure, buffer status reporting procedure, logical channel prioritization procedure, or UE and Issues associated with the coordination of Node B (NB) MAC procedures may be included.

[0012] If an LBT failure occurs due to a problem with the bandwidth part operation procedure, the bandwidth part inactive timer is Even if the time expires and there is UL or DL ​​data to schedule, the initial or It may switch to the fault BWP.

[0013] If an LBT failure occurs due to a problem with the random access procedure, 1) random access without allowing a sufficient number (e.g., a threshold number) of transmission opportunities for the response. 2) the access response window may expire, and 3) the time required for a successful preamble transmission. The preamble transmission counter is maximized without allowing a sufficient number of preamble transmissions. 3) A sufficient number of PDCCH transmitters respond to the MSG3 transmission. The contention resolution timer may expire without allowing the session to proceed, or 4) Increased power ramping even when there is no bull transmission, resulting in inaccurate power settings This sometimes happens.

[0014] If an LBT failure occurs due to a Power Headroom Reporting (PHR) procedure issue, 1) NB It is not possible to determine when the PHR was calculated and what was sent at that time. ,which results in inaccurate power headroom determination; 2) the PHR period timer; P due to reconfiguration, SCell activation, PSCell addition, or prohibit timer expiration HR triggers may occur inappropriately early, and 3) PHR calculations may not simulate actual transmissions. 4) Power headroom may be calculated inaccurately when PHR is set to The PHR prohibit timer may be set even if there is no transmission.

[0015] If an LBT failure occurs due to SCell activation / deactivation procedure issue, When there is UL or DL ​​data to be scheduled on the cell, the SCell is deactivated. The SCell may become activated and the SCell deactivation timer may expire.

[0016] If an LBT failure occurs due to an issue with the discontinuous reception procedure, the UL or If there is DL data, PDCCH reception is stopped and the on-duration timer or The inactivity timer may expire.

[0017] If an LBT failure occurs due to a problem in the scheduling request procedure, 1) the failed SR transmission 2) Even if there is no SR transmission, the SR prohibition time is 3) A sufficient number of SR transmissions may be required for a successful SR transmission. 4) The SR transmission counter may reach the maximum number of transmissions without allowing SR pending may be cleared even if there is no SR transmission.

[0018] If an LBT failure occurs due to a buffer status reporting procedure issue, the UL-SCH resource If a resource is available, a BSR may not be sent and an 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 transmit in subsequent grants, resulting in the loss of user data and control signals. Gunning is lost.

[0020] If an LBT failure occurs due to a coordination issue between the UE and NB MAC procedures, the UE performs actions that accomplish the MAC procedure that needs to be known to the NB for the appropriate action. Additionally, the NB may perform actions that are independent of the UE's behavior.

[0021] Consider the issues in the examples above to avoid taking inappropriate actions and unintended consequences. Modification of existing MAC procedures or development of new MAC procedures that can take into account LBT failures so that Below is an outline of how the problem can be addressed:

[0022] Figure 1 shows an example system for the NR-U LBT MAC procedure. Step 1 In 11, the UE 101 receives a request from the base station 102 regarding channel access to the UE 101. The information is downlink information signaled from the base station 102. In step 112, the UE 101 receives an uplink channel to the base station 102. Information about the uplink access (e.g., uplink information) can be detected. is used for Listen Before Talk (LBT) operation or other operations (e.g., 3GPP TS 36.213 V14.8.0 Section 15) In step 113, the information in step 111 or step 112 (e.g., The operation of the MAC procedure can be achieved based on the uplink / downlink information. The order may be, as disclosed herein, particularly (e.g., PHR, BSR, BFD), L BTR 121 (e.g., FIG. 10), DRX 122 (e.g., FIG. 6), BWP operation 123 ( 2), or random access 124 (e.g., FIG. 3), scheduling requirements 7. In this specification, uplink or downlink It is contemplated that channel access information may be used in the above steps.

[0023] 2-10 illustrate exemplary methods associated with the NR-U LBT MAC procedure. , as described in more detail herein.

[0024] FIG. 2 illustrates an exemplary method for a bandwidth portion (BWP) operation procedure. In step 131, one or more LBT failures (e.g., uplink / downlink LBT failures) In step 132, the failures detected in step 131 are The BWP inactivity timer may be extended based on the UL or DL ​​to be scheduled. data may exist so that switching to the initial or default BWP can be avoided. In step 133, the inactivity timer may be extended. Based on the reported failure, the system switches to an alternate bandwidth portion.

[0025] 3 illustrates 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 thresholds) Based on the failure detected in step 141, the UE 101 Steps 142, 143, 144, or 145 may be performed. Step 142 may extend the random access response window for the random access response. In step 143, the preamble transmission count is calculated. The counter may not be incremented. Step 143 indicates that the preamble transmission was successful. In step 144, a sufficient number of preamble transmissions may be allowed to occur. The resolution timer may be extended to ensure that a sufficient number of PDCCH transmitters respond to the MSG3 transmission. In step 145, power ramping may be prevented from increasing. This can help maintain proper power settings. The problem is indicated to higher layers and the RA procedure may be considered unsuccessful. There may be a switch to an alternative bandwidth portion. It is contemplated that one or more of 47 may occur based on step 141.

[0026] FIG. 4 illustrates an exemplary method for a power headroom reporting procedure. For example, steps In 151, one or more LBT failures (e.g., uplink / downlink LBT failures) Based on the failures detected in step 151, the UE 101 Steps 152, 153, 154, 155, 156, 157 or 158 may be performed. In step 152, the UE 101 determines when the PHR is calculated by the base station 102 (e.g., In step 153, the UE 101 may indicate to the Node B (e.g., Node B) the PHR sent during the PHR calculation. In step 154, the UE 101 may indicate to the base station 102 what has been received. In step 155, the UE 101 may indicate to the base station 102 when a T failure has occurred. may indicate to the base station 102 that there was a delay in the PHR transmission. ,PHR period timer, reconfiguration, SCell activation, PSCell addition, or prohibition PHR triggering due to timer expiration may be delayed. The calculation may take into account lost or delayed transmissions. The inhibit timer may not be set or may be delayed.

[0027] FIG. 5 illustrates an example method for SCell activation / deactivation procedures. For example, in step 161, one or more LBT failures (e.g., uplink / downlink Based on step 161, step 16 In 2, the SCell deactivation timer may be extended, which means that Additional UL or DL ​​data scheduling opportunities may be allowed.

[0028] 6 illustrates an exemplary method for an intermittent reception procedure. For example, in step 171 , one or more LBT failures (e.g., a threshold number of uplink / downlink LBT failures) Based on step 171, the on-duration or inactivity timer is detected. may be extended, which may allow additional UL or DL ​​data scheduling opportunities. In step 173, a DRX short cycle timer may be applied. In 4, the on-duration or inactivity timer is MCOT, CWS or In step 175, the DRX settings may be adjusted. In this example, one or more of steps 172 to 175 are based on step 171. It is intended that this may occur.

[0029] FIG. 7 illustrates an exemplary method for a scheduling request procedure. For example, step 1 In 81, one or more LBT failures (e.g., uplink / downlink LBT failures) Based on the failure detected in step 181, the UE 101 Steps 182, 183, 184, or 185 may be performed. A random access response window may be initiated. In step 183, the SR prohibition timer In step 184, the timer may not be set or the setting of the inhibit timer may be delayed. The SR transmission counter allows a sufficient number of SR transmissions to be made for a successful SR transmission. In step 185, the SR pending is cleared. In step 186, the alternate band is In this specification, steps 182 to 186 are It is contemplated that one or more of these may occur based on step 181.

[0030] FIG. 8 illustrates an exemplary method for a buffer status reporting procedure. For example, steps 191, one or more LBT failures (e.g., uplink / downlink LBT failures) Based on step 192, UL-SCH resources are available. Even if the device is not capable of detecting the SR, the SR may be triggered.

[0031] FIG. 9 illustrates an exemplary method for a logical channel prioritization procedure. In step 201, one or more LBT failures (e.g., uplink / downlink LBT failures) Based on the failure detected in step 201, the UE 101 Step 202 or 203 may be performed. In step 202, the MAC PDU is constructed. In step 203, the MAC PDU is reformatted. This may allow transmission in subsequent grants.

[0032] FIG. 10 shows a method for the UE 101 to report LBT failure or success information to the base station 102. An exemplary method is shown, which aims to improve the coordination between UE 101 and base station MAC procedures. For example, in step 211, one or more LBT failures (e.g., A threshold number of uplink / downlink LBT failures is detected based on step 211. , UE 101 reports LBT failure or which procedures are affected and how. In step 213, the report may include the success / failure of the LBT within the set period. In step 214, the report includes timing information, CCA, MCOT, or In step 215, the prohibit timer is set to minimize the frequency of reports. In this specification, one or more of steps 212 to 215 are set to It is contemplated that the above may occur based on step 181.

[0033] 2-10 illustrate exemplary methods associated with the NR-U LBT MAC procedure. The 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 be applied to general MAC operations and to a number of specific MAC procedures. These MAC procedures include Bandwidth Part (BWP) operation, Random Access (Random Access ss:RA), Power Headroom Reporting (PHR), SCell activation and deactivation Activation, Logical Channel Prioritization (LCP), Discontinuous Reception (DRX), Scheduling Request (SR), and Buffer Status Report (BSR), and possibly a new L It may include BT MAC procedures, etc.

[0035] LBT failures may have unwanted and unintended effects on these MAC procedures. With the knowledge of LBT failure or success, these MAC procedures no longer require LBT. can operate in the same manner, and with similar performance, as in unlicensed spectrum. The steps that may be disclosed in the first MAC procedure (e.g., random access) are: action) is applicable to a second MAC procedure (e.g., BWP operation) Therefore, the steps are generally limited to a specific MAC procedure. I can't.

[0036] (General considerations for LBT failures for both UL and DL) Regarding the impact on the MAC procedure, LBT failures in UL or DL ​​should be considered. The MAC procedure and specific actions within the procedure determine the LBT for the UL and DL. Both failures may be considered, or UL only or DL ​​only LBT failures may be considered. Additionally, how the LBT indication is provided to the MAC, and What information is provided may vary between UL and DL.

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

[0038] For DL ​​LBT operation, the NB signals DL LBT success or failure to the UE. An indication of success or failure of DL LBT may be associated with the DL transmission, or Alternatively, the DL LBT procedure may be performed independently of the DL transmission. Alternatively, the indication of failure may be associated with one or more MAC procedures.

[0039] Depending on the MAC procedure and the specific actions within the procedure, there may be cases where there is no relevant transmission. may also be required to perform LBT. Current MAC procedures require constant access to the channel. This assumes that access exists and that there is no stalling or blocking of transmission. For example, if the UE is performing a downlink allocation or If no uplink grant is detected, the There can be an assumption that there is no data to schedule for LBT. A message that should be scheduled for transmission that is blocked or delayed by a failure In this case, the MAC procedure must be able to avoid unintended or unwanted consequences. may perform actions that may have negative consequences.

[0040] In this disclosure, LBT failure or When success is mentioned, both uplink LBT and downlink LBT are considered. The MAC procedure and specific actions within the procedure may Both failures are considered, or LBT failures of only UL or only DL are considered. do.

[0041] It is not necessary to signal or indicate both LBT failure and success to the MAC. It should be noted that the absence of an indication of LBT failure can be interpreted as success, and the indication of success The UL LBT indication from the PHY layer only indicates an LBT failure. DL LBT indication from NB may indicate LBT success only.

[0042] Indications of LBT success or failure may be provided periodically under known circumstances, or It may also be triggered by a specific action performed by the MAC procedure. The success or failure of the LBT may be signaled periodically by the NB, and the UL LBT The success or failure of the MAC procedure may be indicated by the PHY layer depending on the operation of the particular MAC procedure. The periodic display may be augmented by on-demand display driven by MAC procedures. Note that this is also true for

[0043] The indication of success or failure of LBT may also be related to the behavior of a specific LBT procedure. Yes, or the display provides information about the behavior of two or more LBT procedures over a known period of time. The period can be the period since the last report. The UL LBT marking is DL LBT indications may be due to the operation of a specific LBT procedure, and may be due to multiple (e.g. For example, it may provide information about the LBT operation of a threshold number.

[0044] The indication of success or failure of the LBT depends on the carrier on which the LBT is performed and the BWP (singular or It may provide information about the success or failure of uplink or downlink LBT. In addition to the indication of a successful or failed LBT procedure, further LBT procedure information may be provided to the MAC procedure. The AC procedure considers downlink and uplink transmission opportunities. For the C procedure to work properly, transmissions must be possible on the uplink and downlink. In some cases, it may be necessary to recognize periods during which the system is or is not viable. , in addition to or included in the indication of success or failure of LBT, Clear Channel Assessment (CCA) period, selected maximum channel occupancy time ( Maximum Channel Occupancy Time (MCOT), selected contention window Contention Window Size (CWS), and other timing information are sent to the MAC. This allows for proper determination of downlink and uplink transmission opportunities. MCOT, CWS, or other timing may be selected. Channel Access Priority Class (CAPC) ) or another index.

[0045] (Downlink LBT success / failure indication) To perform the DRX cycle, the DL LB It has been discussed that an indication of T success could be signaled from the NB to the UE. The period during which the RX inactivity timer is running, and possibly the DRX active time For example, if the UE is in DRX on demand mode, the period should be extended to include all periods that constitute the If a random access or scheduling request procedure is initiated while the If LBT is not required, the LBT failure will be ignored for proper operation and performance as when LBT is not required. Sometimes you need to acknowledge defeat.

[0046] Additionally, a more comprehensive way to address this issue is to communicate with the UE in a known, periodic manner. Considering the DL LBT success indications sent continuously, it is possible to perform this outside of the DRX active time. The MAC procedure performed can benefit from the recognition of DL LBT success and failure. To do so.

[0047] The indication of DL LBT success may be a new explicit signal or may be implicitly detected. For example, DL LBT success may be implicitly determined by the reception of SSB or DRS. A new explicit signal may be detected, indicating a new DCI format (e.g., individual UEs may It may be addressed to a group of UEs or broadcast to all UEs. (It can be).

[0048] DRX on durations are generally staggered for different UEs, so DL Periodically and continuously signaling indications of LBT success does not necessarily increase complexity. It does not increase the signaling overhead or resource usage. The overhead can be reduced.

[0049] Also, the signaling DL LBT indication can be UE specific or DRX on duration. Note that the UE may be specific to a group of UEs that share the same location. Cell-specific DL LBT representation allows for more efficient use of resources and This can result in consistent MAC procedure operation and performance.

[0050] It is also considered that the indication of LBT success may not be a single indication. The logged information may also provide information about the period since the last successful LBT indication. The signaled information is used by the NB to, for example, select a specific channel or BWP, In this case, the MAC address can provide information about how much access the network has. The sequence may have continuous awareness of DL LBT success or failure over time, thereby ,The impact of DL LBT failure on MAC procedure can be more accurate.

[0051] The indication of downlink success also allows the MAC procedure to accurately determine transmission opportunities. To ensure that To achieve this, the indication of success of the LBT may include Channel Assessment (CCA) period, selected Maximum Channel Occupancy Time (MCOT), selected The assigned contention window size (CWS) or the appropriate downlink transmission opportunity Other timing information provided to the MAC to enable appropriate decisions may be added or MCOT, CWS, or other timing information may be included in the selected timing. by a Channel Access Priority Class (CAPC) or another index that represents the can be identified.

[0052] (Uplink LBT success / failure indication) In addition to the NB indicating the LBT failure or success status to the UE, the UE also BT failure or success information may be provided to the NB.

[0053] As disclosed herein, there are several potential impacts to the UE MAC procedure: The NB knows how LBT failure or success affected a particular MAC procedure. There may be several cases where it may be necessary to If the DRX cycle is affected, the NB must ensure that the UE is scheduled appropriately. must be recognized.

[0054] The LBT procedure may do more than indicate a UL LBT failure to the NB. After an LBT failure occurs, other actions may be taken. Thus, the behavior of existing MAC procedures may be affected by LBT failures. LBT procedures have the potential to perform new actions to resolve LBT failures For example, channel access priorities are adjusted to increase the likelihood of LBT success. obtain.

[0055] The total number of LBT failures may be counted, which may be Alternatively, the LBT Failure Counters (FC) may be Subsequent LBT failures may be counted and the LBT FC may be reset to zero upon a successful LBT. The period during which LBT failures can be counted may be a sliding window of time. If the LBT failure counter exceeds a specified or configured threshold, the LBT state is It can be considered a failure if the specified or set number of LBT failures is not exceeded. , or if a specified or configured number of LBT success indications are received, the LBT status is The MAC procedure can be considered successful if there are any individual LBT failures associated with the MAC procedure. Instead of counting the LBT status, the MAC procedure checks the LBT status. For example, the MAC procedure may adjust the counters and timers according to Depending on the LBT state, the timer and counter may be extended or may be deemed to have reached their maximum threshold. The LBT status may be indicated to higher layers, e.g. to affect RRC procedures. can.

[0056] To provide information on the success or failure of UL LBT, a new MAC LBT report ( A LBT Report (LBTR) procedure may be defined. The LBTR MAC CE may May provide historical information about LBT results, relative to when the report was generated. It may span a certain period of time, e.g., since the last LBTR MAC CE was sent. The MAC CE determines which MAC procedure(s) are affected. may provide information about when or if an LBT failure occurred, thereby Thus, NB may attempt to correlate which procedure(s) were affected. LBTR MAC CE also fails, for example, BWP LBT, and BWP If the LBT is successful, the LBT result may include the BWP information. , LBTR reporting period may be set.

[0057] Alternatively, UL physical control signaling may provide an indication of UL LBT failure or success. This may be the case for scheduled or new UL signaling, It can be transmitted on the UL CH or piggybacked on the PUSCH. Lack of reception of PUCCH or PUCCH may be interpreted as a UE LBT failure. New UL signaling can be a signal that NB reception is already aware of. It may require physical resources and be configured to occur at a known time. .

[0058] Uplink LBT success and failure indications also allow the MAC procedure to accurately determine transmission opportunities. In order to be able to do so, when and how transmission can be made To achieve this, the LBT success or in addition to or including an indication of failure of Clear Channel Assessment (CCA) period, selected Maximum Channel Occupancy Time (MCOT), selected contention win The byte size (CWS), or other timing information is provided to the MAC for uplink transmission. It is proposed that the appropriate judgment of the opportunity for MCOT, CWS, or other The timing is the Channel Access Priority Class (CAPC) that represents the selected timing. Or it may be identified by another index.

[0059] (LBT impact on MAC timers and counters) LBT failure may result in the loss of a transmission opportunity. This also leads to a longer time to achieve success. The MAC procedure is also Before sending, consider the amount of transmission opportunities and the time to complete them. C Proper execution of the procedure requires a certain number of transmission opportunities and, in some cases, successful completion of the procedure. The period until completion must take into account the possibility of LBT failure.

[0060] In the existing MAC procedure, when a MAC PDU is presented to the PHY layer or when a PHY access When a command is given to the PHY to transmit uplink control information (e.g., SR), Assume that PDUs or PHY uplink control information is transmitted. When the MAC CE associated with this M is constructed and multiplexed into a MAC PDU, It can be assumed that the MAC CE is transmitted. To limit the frequencies at which E or PHY uplink control information may be transmitted, When the CE is established and MAC PDUs are given to the PHY layer, or when the PHY uplink When the PHY is instructed to transmit network control information, an inhibit timer may be set. Properly control how often MAC CE or PHY uplink control information can be transmitted. To ensure that packets are sent when necessary, the settings of these inhibit timers are also The failure of BT may be taken into account.

[0061] The sequence of processing MAC procedures can also be considered. Existing procedures are performed by the PHY layer. Before the LBT is performed, counters and timers are inserted when the MAC procedure is performed. Regarding the impact on existing MAC procedures, several methods can be considered. This may involve: 1) The MAC receiving an indication of LBT failure from a PHY layer counter. 2) LBT is successful and the timer and and counter is running, or 3) since the first MAC step is performed or After it is first set, the counter(s) or timer(s) LBT failures are recorded during the time period up to which these maximum thresholds are reached.

[0062] When the MAC receives an indication of LBT failure from the PHY layer counters, it will consider the transmission to have failed. Counters and timers are adjusted so that they are incremented when the MAC procedure is executed. The counters set are decremented so that they are not changed from what they were set to before the procedure was executed. This can be a bit more complicated in the case of timers. The time should not take into account the duration of the LBT failure. The behavior of the timers depends on how they are used for different MAC procedures. There are several options: a) The MAC procedure associated with the LBT failure is performed. The time period from the time the MAC procedure is executed until the next opportunity to perform the MAC procedure is subtracted from the timer, or or add to the maximum time threshold (when the timer expires), b) upon receipt of an LBT failure indication c) Stop the timer and restart it at the next opportunity to perform a MAC procedure; or d) restart the timer of the MAC procedure associated with the LBT failure. from the time the timer is set (startup or restart) to the next opportunity to set the timer for the MAC procedure. The period is subtracted from the timer or added to the maximum time threshold (when the timer expires) When).

[0063] One concern with this approach is the time at which the MAC procedure is performed and the MAC procedure related Associated LBT failure indication counter(s) or timer(s) What happens when the time between receiving and transmitting reaches its maximum value? One way to address this issue is to This method allows the MAC to automatically retransmit a previous transmission when a timer or counter reaches its maximum value. It checks whether the LBT display is waiting, and after it is determined that the LBT display was successful, The goal is to invoke only the actions associated with the expiration of a timer or counter.

[0064] If the LBT is successful, the timer and counter are activated. In this way, the MAC procedure When executed, the counter(s) and timer(s) are acted upon. When the LBT is successful, the counter is incremented and the timer is checked or One problem with this approach is that the timer or counter is not triggered when the LBT is successful. The MAC procedure is performed differently when the data reaches their maximum threshold. There are several options for dealing with this situation: When executing a procedure, the timers and counters are used to If the thresholds have been adjusted, it can be checked whether they have reached their maximum thresholds. If a MAC procedure is executed, it will be executed as if the counter or timer had reached its maximum threshold. An action may be performed.

[0065] LBT failure occurs when the first MAC procedure is performed or when it is first configured. , the point counter(s) or timer(s) reach their maximum The time period up to the threshold may be recorded. When the timer or counter reaches the maximum threshold, The record of LBT failure is checked, and if an LBT failure occurs, the procedure considers the LBT failure. To achieve this, use either (a) or (b) of the following: There can be multiple options, such as: (a) the action to be taken when the maximum threshold is reached; Depending on the number of LBT failures or the duration of the LBT failures, the task (b) the maximum threshold for the timer and counter is adjusted, or The number of failures and the duration of the LBT failures so that the action taken is not performed at this time In response, the timer and counter are restarted.

[0066] LBT failures affecting timers and counters can cause unacceptable delays (e.g. For example, a threshold may be reached, or the MAC procedure may stall indefinitely. AC procedure counters and timers may never reach their maximum thresholds. The indicated MAC procedure modifications take into account the possibility of continuous or substantial LBT failures. In this case, the MAC procedure is performed with a maximum extension of time so that each MAC procedure is properly performed. A maximum extension of the MAC procedure counter (MAC Proc) may be considered. Procedure Counter (MAC PC) and MAC Procedure Timer (MAC Limiting the extension of AC PT can be addressed in the following ways: 1) MAC procedure LBT failure Failure Counter (LBT FC), MAC PC and MAC P 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 may be counted, which may be within a specified or set period. The BT FC may count consecutive LBT failures, and the LBT FC counts consecutive LBT failures. The LBT FC period is the time allowed for the MAC procedure to complete. It can be a period, or a sliding window of time. In a particular MAC procedure, two or more The LBT FC above may be used. The MAC procedure performs independent actions in parallel. In this case, each procedure may have an LBT FC. The LBT FC has a maximum value. When the LBT FC reaches its maximum count, the MA Upon failure of LBT for C procedure, MAC PC or MAC PT will not be extended. When the LBT FC reaches the maximum count, the MAC procedure will Take action as if PT had reached its maximum value, which causes the MAC procedure to fail. It can be considered that

[0068] MAC PC and MAC PT extension counter (EC), LBT failure, MAC The maximum threshold for PC or MAC PT is extended. The criteria for extension are specified or set. It can be a specified or configured number of LBT failures within a specified period. For example, C may be the maximum threshold for PT. EC is the total number of MAC PC or MAC PT prolongations. The number of times a person has a disability may be counted, which may be within a specified or set period. Alternatively, EC may be counted consecutively for MAC PC or MAC PT prolongation. The EC period is the time allowed for the MAC procedure to complete, or a sliding time A particular MAC procedure may use more than one EC. If C procedures perform independent actions in parallel, each procedure may have an EC. may have a specified or configured maximum value. When the EC reaches the maximum count, When the LBT of the MAC procedure fails, the MAC PC or MAC PT will not be extended. Alternatively, if the EC reaches the maximum count, the MAC procedure will terminate with MAC PC or MAC PT. may take action as if the maximum value had been reached, which would 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 for each LBT failure or for a specified number of failures within a specified or configured period. The period can be extended after a set or configured number of LBT failures. For example, the period can be extended after the current M There may be a maximum threshold for AC PT. The maximum threshold for MAC PC or MAC PT is The LBT may be extended if a set number of consecutive LBT failures are met. When the AC PT reaches the designated or set EMT, the MAC PC or MA The maximum threshold for CPT may not be extended, which may result in the MAC procedure being considered unsuccessful. possible.

[0070] The MAC procedure also has a timer that is used to control how often the procedure is performed. These timers may be known as prohibit timers. When a procedure is executed, the inhibit timer is set to the earliest time that the procedure is allowed to be executed again. The MAC procedure currently sets these timers when the procedure is executed. To address this, several methods or systems can be used, for example: 1) The inhibit timer does not have to be set when the procedure is executed, but is set by the success or failure of the LBT. May or may not be set. Only upon successful LBT of a transmission associated with a MAC procedure. , the inhibit timer should be set. It may take some time for the LBT procedure to succeed. In this case, the start of the prohibit timer may be delayed relative to when the MAC procedure is performed. This is done where necessary to ensure that the frequency with which the MAC procedure is performed is appropriately limited. Or, 2) The prohibition timer that may be set during the MAC procedure may be set during the MAC procedure. Cleared when an LBT failure indication is received for the associated transmission. If a transmission is delayed due to a transmission order, the prohibit timer is counted down until the MAC procedure is performed and the LBT is successful. may be extended to take into account the time it takes for

[0071] (Lost scheduling and transmission opportunities) The MAC procedure may also take into account downlink allocations and uplink grants. LBT failure may result in the loss of downlink allocation and uplink grant. If the NB determines that the LBT has failed, the PDCCH scheduling opportunity is lost. In addition, even if the UE receives PDCCH scheduling, it may lose LBT. If it is determined to be a failure, the uplink transmission opportunity is lost.

[0072] A downlink assignment or an uplink grant is received within the configured monitoring period. If there is no reception, multiple MAC procedures take action. LBT success is determined by not receiving a downlink assignment and an uplink grant. The MAC procedure criteria may be taken into account for the success or failure of uplink or downlink LBT. Additionally, further LBT procedure information may be provided to the MAC procedure. In addition to or included in the failure indication, a Clear Channel Assessment (CCA) period, Selected Maximum Channel Occupancy Time (MCOT), selected contention window size CWS, or other timing information is provided to the MAC for downlink and access This allows for proper determination of link transmission opportunities. The tag is a Channel Access Priority Class (CAPC) or other tag that represents the selected timing. The index can be specified by:

[0073] During the configured monitoring period, If no LBT is received, an LBT failure is detected, or an LBT success is not detected In this case, several options may be considered. If no LBT success is detected during the monitoring period, action is taken by the MAC procedure. The action may not be performed. - Within the monitoring period, the set minimum threshold for detecting LBT success or consecutive LBT success is met. If it is not reached, no action may be taken by the MAC procedure. If an LBT failure is detected during the monitoring period, no action is taken by the MAC procedure. It may not be carried out. - Reaching the set maximum threshold of LBT failure or consecutive LBT failures within the monitoring period If so, no action may be taken by the MAC procedure. The number or duration of uplink or downlink transmission opportunities is determined by the CCA, MCOT, WS, or can be more accurately determined from other timing information.

[0074] Actions not performed by the MAC procedure are actions that are performed during the configured monitoring period. If no downlink assignment or uplink grant is received, the currently specified These are actions that could have been taken by the MAC procedure in question, for example: - If an LBT failure is detected while the BWP inactivity timer is running, or if an LBT success occurs If no downlink allocation or uplink graph is detected during this period, Even if no notification is received, the BWP switch to the initial or default BWP is not performed. It will not be carried out. During that time, if a DRX active time LBT failure is detected, or if an LBT success is detected, If no downlink assignment or uplink grant is issued during this period, If not received, DRX inactive may still be reset.

[0075] Even if uplink transmission is not possible due to LBT failure, MAC procedures must be considered. The impact on the MAC procedure is that the PDCCH scheduling opportunity may be lost due to an LBT failure. The MAC procedure is the same as if an uplink grant is not received. or if the uplink ground is not acceptable for the data that can be sent (e.g. , LCP limit), UL transmission failure by LBT is the same as currently being performed. For example, during the backoff period after an LBT failure, the MAC procedure If no grant is received, or if no uplink grant is received for data available to send, If is not accepted (e.g. LCP restrictions), it may behave as it does now.

[0076] The conventional MAC procedure is that when a MAC PDU is presented to the PHY layer, it is transmitted This is not necessarily the case when performing LBT. MAC procedures that refer to C-PDU transmission consider the transmission to be LBT successful or unsuccessful. This should be clarified by referring to the LBT success within the MAC procedure, or This is achieved by clarifying that the MAC PDU transmission criteria include LBT success. obtain.

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

[0078] (Impact of NR-U LBT on specific MAC procedures) (Impact of NR-U LBT on specific MAC procedures) A new LBT MAC procedure can be introduced. This procedure will report the failure or success of LBT to N B. As described herein, the UE MAC procedure There can be multiple possible effects on the NB. In many cases, the NB will need to It may be necessary to be aware of their impact on the MAC procedure.

[0079] Each UE MAC procedure affected by an LBT failure shall In order to maintain coordination between the UE and the NB, it may be necessary to signal the effect to the NB. However, this may require introducing additional complexity into many MAC procedures.

[0080] An exemplary method is for the NB to consider LBT information and change these procedures by LBT operation. By implementing the specified behavior, it is possible to adjust that behavior to other MAC procedures. A new separate MAC procedure to indicate the LBT status (e.g., success or failure) to the NB so that The purpose is to define

[0081] Therefore, the UE PHY layer LBT success or failure indication may be provided to the MAC. The PHY layer determines the amount of primitives signaled between the MAC layer and the PHY layer. In order to limit the number of LBT MACs, some preprocessing can be done. integrates these LBT indications to implement the Listen-Before-Talk Reporting (LBTR) MAC system. A Control Element (CE) can be created to prevent LBT failures or The UE PHY layer may provide information about the success of the LBT in addition to the LBT success or failure indication. The LBT timing information may be provided to the MAC layer by, for example, includes a CCA period and may select an MCOT or CWS period.

[0082] LBTR can provide UL and DL LBT failures separately. UL LBT failures are N signaling to maintain coordination of MAC procedures. However, DL LBT failures that the UE is aware of may also be useful to the NB. This is because the UE may not be able to detect the Is there any case where the NB cannot assume that the DL LBT failure issued was realized by the UE? The UE misses or fails to receive the NB DL LBT failure or success indication. There's a chance it could have been lost.

[0083] The LBTR procedure requires one or more LBTRs to initiate the procedures that lead to the sending of an LBTR. A trigger may be required. The trigger may include one or more of the following methods: In this method, an LBT failure that reaches a threshold can be a trigger. There may be a failure threshold. This threshold may be a threshold number of LBT failures over a known period of time, or a The urgency of reporting may depend on the traffic timing supported. These parameters may need to be configurable, as they may be type dependent. In the second method, the trigger is based on the fact that some effect on other MAC procedures is required for proper operation. This may be when a change in the operation of the procedure needs to be recognized by the NB. For example, changes to the DRX behavior that affect the active time or the DRX cycle. In the third method, the trigger is the MAC DRX procedure. In a fourth method, the trigger can be based on the frequency of the LBTR. This may be based on an LBTR inhibit timer that is introduced to limit

[0084] The LBTR procedure is performed based on the LBT failure or success over the set LBTR monitoring period. You can count your merits. For example, During the LBTR monitoring period, the LBT failure count is equal to the set LBT failure count. If it is greater, the LBTR may be triggered. During the LBTR monitoring period, the LBT success count does not reach the set minimum LBT success count. If so, the LBTR may be triggered.

[0085] Over the set LBTR monitoring period, the LBTR procedure is performed on consecutive LBT failures or or successes. During the LBTR monitoring period, the consecutive LBT failure count exceeds the set LBT failure count. If the value is greater than the threshold, the LBTR may be triggered. - During the LBTR monitoring period, the consecutive LBT success count is set to consecutive LBT success. If it is below the minimum value, the LBTR may be triggered.

[0086] If another MAC procedure triggers LBTR, it may set the LBTR pending indicator. The LBTR pending indication can be later used during MAC PDU multiplex assembly. Check to make sure the LBTR MAC CE is built.

[0087] The LBTR may include the following information: -Count of LBT failures or successes since the last LBTR - The number of LBT failures or consecutive LBT failures since the last LBTR is greater than the configured maximum number of LBT failures. Number of times the high threshold was exceeded - The LBT success count or consecutive LBT success count has not been set since the last LBTR. The number of consecutive LBT successes below the minimum value In addition to UL LBT failures, DL LBT failures detected by the UE shall also be reported. There is MAC procedure that triggered LBTR · A timestamp associated with when the LBTR PDU is constructed. CCA, MCOT, or CWS information

[0088] Similar operations may be provided by the PHY layer or the RRC layer, and the PHY layer or the RR It should be noted that C-layer signaling may also be used to convey similar information to the NB. .

[0089] RRC maps the LBTR MAC CE designated logical channel in the UE. Alternatively, the access priority may be set to the channel access priority class. The L priority class may be designated as the highest priority channel access priority class. The BTR procedure may also include a general LBT status determination procedure, or an independent LBT The state procedure may be utilized by LBTR and other MAC procedures. Minimize the complexity introduced into the AC procedure, e.g., each MAC step has an impact on that procedure. Instead of counting LBT failures that have an effect, only the LBT state is checked.

[0090] The total number of LBT failures may be counted, which may be Alternatively, LBT FC may count consecutive LBT failures, and L If the BT is successful, the LBT FC is reset to zero. A failed LBT can be counted. The period may be a sliding window of time. If the specified threshold is exceeded, the LBT state is considered to have failed. or if the configured number of LBT failures is not received, or if the specified or configured If the same number of LBT success indications are received, the LBT state is considered successful. The procedure counts the individual LBT failures associated with the MAC procedure, rather than counting the individual LBT failures. The MAC procedure may check the counter and the T state according to the LBT state. For example, the MAC procedure may extend counters and timers, or Depending on the BT state, the timer and counter may be considered to have reached their maximum threshold. , may be indicated to a higher layer, e.g., to perform an RRC procedure.

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

[0092] LBT failures may result in downlink allocation and In this case, BWP is set to default or It may be inappropriate to make a switch to the initial BWP(s).

[0093] If an LBT failure occurs while the BWP inactivity timer is running, the activity The BWP inactivity timer associated with the active DL BWP should be extended. This is because the downlink allocation and uplink grant are lost due to an LBT failure. Ensures that a BWP switch to the default or initial BWP is not performed when A BWP switch to the default or initial BWP may be necessary to BWP inactivity timer runs only if there is no data to send. The examples in this specification are based on the MAC specification 3GPP TS 38.3 21, (NR), See Media Access Control (MAC) Protocol Specification, V15.2.0 (also referred to herein as [2]). Many of the exemplary modifications are As underlined in this specification, for example, the MAC specification may be modified as follows: stomach. If the bwp-InactivityTimer is set, the MAC entity , for each activated serving cell, it shall be: 1>defaultDownlinkBWP is set and the active DL BW P is not the BWP indicated by defaultDownlinkBWP, or , 1>defaultDownlinkBWP is not set and there is no active DL B If WP is not initialDownlinkBWP, 2> C-RNTI indicating a downlink assignment or an uplink grant or If a PDCCH addressed to CS-RNTI is received with an active BWP, or 2> C-RNTI indicating a downlink assignment or an uplink grant or If a PDCCH addressed to CS-RNTI is received for an active BWP, and teeth, 2> If a MAC PDU is sent with the configured uplink grant or or 2> If an LBT failure is detected on an active BWP, 3> If there is no current random access procedure associated with this serving cell, and teeth, 3> When receiving this PDCCH addressed to C-RNTI, If the current random access procedure is completed successfully (e.g., Section 5.1.4 and and as specified with respect to Section 5.1.5), 4> bwp-InactivityTime associated with an active DL BWP Start or restart r.

[0094] This criterion is also based on LBT success detection while BWP is inactive. For example, If the bwp-InactivityTimer is set, the MAC entity , for each activated serving cell, it shall be: 1>defaultDownlinkBWP is set and the active DL BW P is not the BWP indicated by defaultDownlinkBWP, or , 1>defaultDownlinkBWP is not set and there is no active DL B If WP is not initialDownlinkBWP, 2> C-RNTI indicating a downlink assignment or an uplink grant or If a PDCCH addressed to CS-RNTI is received with an active BWP, or 2> C-RNTI indicating a downlink assignment or an uplink grant or If a PDCCH addressed to CS-RNTI is received for an active BWP, and teeth, 2> If a MAC PDU is sent with the configured uplink grant or or 2> If no LBT success is detected in the active BWP, 3> If there is no current random access procedure associated with this serving cell, and teeth, 3> When receiving this PDCCH addressed to C-RNTI, If the current random access procedure is completed successfully (e.g., Section 5.1.4 and and as specified with respect to Section 5.1.5), 4> bwp-InactivityTime associated with an active DL BWP Start or restart r.

[0095] An LBT failure may not be a single instance. During execution, multiple LBT failures or successes may be detected. As shown, LBT failure or success is determined by the uplink LBT or downlink LBT. Refer to both.

[0096] Counting LBT failures or LBT successes for a certain period, or consecutive LBTs for a certain period A procedure may be defined to count T failures or consecutive LBT successes. or consecutive LBT failures exceed the configured maximum LBT failure threshold, or If success or consecutive LBT successes can be less than the minimum LBT success threshold set For example, modify the MAC specification as follows: You may do so. If the bwp-InactivityTimer is set, the MAC entity For each activated serving cell, 1>defaultDownlinkBWP is set and the active DL BW P is not the BWP indicated by defaultDownlinkBWP, or , 1>defaultDownlinkBWP is not set and there is no active DL B If WP is not initialDownlinkBWP, 2> C-RNTI indicating a downlink assignment or an uplink grant or If a PDCCH addressed to CS-RNTI is received with an active BWP, or 2> C-RNTI indicating a downlink assignment or an uplink grant or If a PDCCH addressed to CS-RNTI is received for an active BWP, and teeth, 2> If a MAC PDU is sent with the configured uplink grant or or 2> When the LBT failure count exceeds the LBT failure threshold for an active BWP, 3> If there is no current random access procedure associated with this serving cell, and teeth, 3> When receiving this PDCCH addressed to C-RNTI, If the current random access procedure is completed successfully (e.g., Section 5.1.4 and and as specified with respect to Section 5.1.5), 4> bwp-InactivityTime associated with an active DL BWP Start or restart r, 4>Reset the LBT failure count.

[0097] In the above procedure, an LBT failure is detected when the BWP inactivity timer is running. During this period, a PDCCH for BWP switching is received on the active DL BWP. When, or PDC on an active BWP or uplink grant for a BWP When a CH is received or a MAC PDU is sent or received for a configured grant It applies to the period from when it is received until the BWP inactivity timer expires. It should be noted that:

[0098] The BWP inactivity timer can be extended for a period different from the initial setting. The period for which the active timer is extended may be another set value or may be It may be a value according to the amount of BT failure or success determined.

[0099] Additionally, an LBT failure may trigger a switch between configured BWPs. An LBT failure may not be a single instance. It may also be the detection of multiple LBT failures or successes within a period of time. Thus, LBT failure or success refers to uplink LBT or downlink LBT. This may happen.

[0100] Counting LBT failures or LBT successes for a certain period, or consecutive LBTs for a certain period A procedure may be defined to count T failures or consecutive LBT successes. Or if consecutive LBT failures exceed the configured maximum LBT failure threshold, or if LBT failure The activity is activated only if the success or consecutive LBT successes are below the set minimum LBT success threshold. The active BWP will be switched to another configured active BWP.

[0101] Also, the BPW inactivity timeout is set so that the UE never reverts to the initial or default BPW. significantly extend the inactivity timer, or set the inactivity timer indefinitely due to an LBT failure. In this case, it may be necessary to avoid extending the BWP inactive period. MAC specification may limit the number of restarts to a specified or configured maximum value. may be modified as follows: 1> On an active BWP, BWP-Inactivity-LBT-Failure- Count>BWP-Inactivity-LBT Failure Thresho ld, and 1>LBT-BWP-InactivityRestartCount<=LBT-BW If P-Inactivity-Restart-Threshold, 2> Set BWP-Inactivity-LBT-Failure-Count to 0 hand, 2>Increment LBT-BWP-InactivityRestartCount by 1 Mention it, 2> bwp-InactivityTime associated with an active DL BWP Start or restart r. 1>If an LBT failure is detected, 2>Increment BWP-Inactivity-LBT-Failure-Count Enter. If the LBT BWP inactivity restart threshold is exceeded, the following actions good. 1>LBT-BWP-InactivityRestartCount>LBT-BWP -Inactivity-Restart-Threshold, 2> A BWP switch to the default or initial BWP is performed, 2> An indication identifying 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 reception procedure take into account the impact of LBT in NR-U: You can also put it in.

[0103] Even if the RA response window expires, if an LBT failure is detected after the preamble transmission, If the NB receives a preamble transmission, it may extend the RA response window. This may also be necessary if the random access response is delayed due to an LBT failure. When the UE detects that the RA has missed a transmission opportunity, it may extend the RA response window.

[0104] For example, the MAC specification may be modified as follows: 1> ra-ResponseWi set in RACH-ConfigCommon When the window expires and a random access matching the PREAMBLE_INDEX is sent, If no random access response containing a preamble identifier is received, 1> ra-Resp set in BeamFailureRecoveryConfig When the ONSEWindow expires and when a PDCCH addressed to C-RNTI is received If not, 2>If an LBT failure is detected, 3> Contention-free random access for beam failure recovery requests by MAC entities If a preamble is sent, 4> The ra-Respo set in BeamFailureRecoveryConfig Restart NseWindow and 4> While the ra-ResponseWindow is running, the Monitor the response to the beam failure recovery request on the PDCCH of the SpCell, 3> Otherwise, 4> ra-ResponseWind set in RACH-ConfigCommon Restart ow, 4> While the ra-ResponseWindow is running, the RA-RNTI PDCCH of the SpCell for the specified random access response(s) Monitor and 2> Otherwise (LBT failure not detected), 3>Consider the random access response not to have been received successfully.

[0105] In the above procedure, an LBT failure is detected when the RA response window is not working. The period from the preamble transmission to the first expiration of the RA response window after the preamble transmission. or until the RA conflict resolution timer expires due to LBT detection and the final restart occurs. This applies to the period from the time of the request to the time the next ra-ResponseWindow expires. It should be noted that:

[0106] Alternatively, a procedure may be defined to count LBT failures or LBT successes. If the LBT failure exceeds the configured maximum LBT failure threshold, or if the LBT success exceeds the configured The RA response window is restarted only if the RA response window can be less than the specified minimum LBT success threshold. do.

[0107] Alternatively, the RA response window is set to BeamFailureRecoveryConf ig or RACH-ConfigCommon. The period for which the RA response window is extended may be another configured value, or It may be a value according to the amount of detected LBT failure or determined success. The LBT failure is handled so that the UE never determines that the random access response was not received successfully. Prevents significantly or indefinitely extending random access responses due to failure In some cases, it may be necessary to avoid restarting the RA response window. For example, the MAC specification may be modified to stomach. 1>RA-ResponseWindow-LBT-Failure-Count>RA -ResponseWindow-LBT-FailureThreshold If, 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. Increment, 2>Start or restart ra-ResponseWindow. 1>If an LBT failure is detected, 2>Insert RA-ResponseWindow-LBT-Failure-Count Decrease. RA-ResponseWindow-LBT-FailureThreshold If exceeded, you may take the following actions: 1>LBT-RA-ResponseWindowRestartCount>LBT- If RA-ResponseWindow-Restart-Threshold , 2> The random access response is considered not to have been received successfully.

[0108] Here is another example: If LBT fails, increment the preamble transmission counter. For example, 1> ra-ResponseWi set in RACH-ConfigCommon If the window expires and the transmitted random access preamble identifier matches If no random access response containing an identifier is received, 1> ra-Resp set in BeamFailureRecoveryConfig When the ONSEWindow expires and when a PDCCH addressed to C-RNTI is received If not, 2> The random access response is not considered to have been 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, 4> When a random access preamble is sent by SpCell, 5> Present the random access problem to higher layers, 4>If this random access procedure is triggered for an SI request, 5> The random access procedure is considered unsuccessful, 3> Otherwise, if a random access preamble is transmitted on the SCell, 4> The random access procedure is considered unsuccessful.

[0109] The preamble transmission counter may be decremented upon detection of an LBT failure. Ba, 1> The physical layer receives the selected PRACH, the corresponding RA-RNTI (if available), and P PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARG Use ET_POWER to instruct the device to send a random access preamble. , 1>If an LBT failure is detected, 2> Decrement PREAMBLE_TRANSMISSION_COUNTER by 1 To do.

[0110] Note that in the above procedure, LBT failure may apply to preamble transmission. To prevent the UE from determining that the random access response was not received successfully, the LBT Failures should not significantly increment the preamble transmission counter or There should be an attempt to avoid incrementing the tumble transmission counter indefinitely. In that case, the RA response window restart is limited to a specified or configured maximum value. For example, the MAC specification may be modified as follows: 1> ra-ResponseWi set in RACH-ConfigCommon If the window expires and the label that matches the PREAMBLE_INDEX sent If no random access response containing a random access preamble identifier is received, 1> ra-Resp set in BeamFailureRecoveryConfig When the ONSEWindow expires and when a PDCCH addressed to C-RNTI is received If not, 2> The random access response is not considered to have been received successfully, 2>If no PreambleTransmissionLBT failure is detected, or Or, 2>RA-PreambleTransmission-LBT-Failure-Co unt>RA-PreambleTransmission-LBT-FailureT If hreshold, 3>Increment PREAMBLE_TRANSMISSION_COUNTER by 1 Enter, 3>PREAMBLE_TRANSMISSION_COUNTER=preamble If TransMax+1, 4> When a random access preamble is sent by SpCell, 5>Indicates random access problems to higher layers, 4>If this random access procedure is triggered for an SI request, 5> The random access procedure is considered unsuccessful, 3> Otherwise, if a random access preamble is transmitted on the 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 assign a 2) indicates an access problem, or 2) considers the random access procedure unsuccessful.

[0112] Alternatively, the MAC specification may 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 hreshold, 3> When a random access preamble is sent by SpCell, 4> Indicate random access problems to higher layers, 3>If this random access procedure is triggered for an SI request, 4> The random access procedure is considered unsuccessful, 3> Otherwise, if a random access preamble is transmitted on the SCell, 4> The random access procedure is considered unsuccessful.

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

[0114] If the RA contention resolution expires but an LBT failure is detected after the preamble transmission, the R A contention resolution may be extended. This means that even if the NB receives the MSG3 transmission, it may still receive the LBT failure. This may be necessary due to the PDCCH transmission being delayed due to the LBT failure. If the UE detects that an opportunity has been missed, it may extend the RA contention resolution timer.

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

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

[0117] Alternatively, a procedure may be defined to count LBT failures or LBT successes. If the LBT failure exceeds the configured maximum LBT failure threshold, or if the LBT success exceeds the configured RA conflict resolution is only restarted if the LBT success threshold is less than the specified minimum LBT success threshold.

[0118] Alternatively, the RA conflict resolution timer may be set for a period different from the configured RA conflict resolution timer. The period for which the RA conflict resolution timer is extended may be set to another value. , or a value depending on the amount of detected LBT failure or determined success. Also, the RA contention resolution time is set to 0 so that the UE never determines that contention resolution was not successful. or extending the RA conflict resolution timer indefinitely due to an LBT failure. In that case, restarting the RA conflict resolution timer is 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 hreshold, and 1>LBT-RA-ContentionResolutionTimerRestar tCount<=LBT-RAContentionResolutionRestar If t-Threshold, 2>RA-ContentionResolution-LBT-Failure-Co Set unt to 0, 2>LBT-RA-ContentionResolutionTimerRestar Increment tCount by 1, 2>Start the ra-ContentionResolutionTimer and retry HARQ. Restart the ra-ContentionResolutionTimer after each transmission, 2> Regardless of the possibility of measurement gaps, ra-ContentionResolu While the tionTimer is running, the PDCCH is monitored. 1>If an LBT failure is detected, 2>RA-ContentionResolution-LBT-Failure-Co Increment unt. RA-ContentionResolution-LBTRestartThres If the hold is exceeded, you may perform the following actions: 1>LBT-RA-ContentionResolutionTimerRestar tCount>LBT-RA-ContentionResolutionRestar If t-Threshold, 2> The random access response is considered not to have been received successfully.

[0119] (Random access preamble transmission) The following modifications to the random access preamble transmission procedure address the impact of LBT in NR-U: Take into account the sound.

[0120] If LBT fails, the preamble power ramping counter should not be incremented. For example, The MAC entity shall, for each random access preamble: do. 1>If PREAMBLE_TRANSMISSION_COUNTER is greater than 1, If, and 1> If no notification of the power ramping counter pause has been received from the lower layer, and Beauty, 1> If the selected SSB has not changed (i.e., the previous random access priority same as amble transmission), 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 upon detection of an LBT failure. For example, 1> The physical layer receives the selected PRACH, the corresponding RA-RNTI (if available), and P PREAMBLE_INDEX, and PREAMBLE_RECEIVED_TARGE T_POWER is used to indicate that a random access preamble should be sent. 2>If an LBT failure is detected, 2>Decrement PREAMBLE_POWER_RAMPING_COUNTER by 1 Enter.

[0122] Note that in the above procedure, LBT failure may apply to preamble transmission. is.

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

[0124] PHR MAC CE transmission is blocked due to LBT failure and retransmission occurs after a certain time If so, to notify the NB when the PHR has been calculated or Additional signaling is introduced to inform the NB of the transmission conditions.

[0125] In order for NB to process PHR properly, it is necessary to know under what conditions the PHR was calculated. This may be necessary for NB to recognize it.

[0126] The PHR is determined by the nominal UE maximum transmit power and the UL- the difference between the estimated power of the SCH or SRS transmission and the nominal UE maximum power, UL-SCH and PUCCH transmission estimates on the 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 real or virtual. The PHR is calculated based on the PUCCH transmission time. If the UL-SCH is actually transmitted, the NB must know what was transmitted when calculating the PHR. It may be necessary to recognize it.

[0128] If not operating in an unlicensed frequency band and LBT is not used, the NB It is possible to determine when HR calculations were performed. NB is scheduled and received. Since the UL-SCH is known at this point, the P HR can be interpreted, but LBT fails and transmission is delayed until LBT is successful. If the PHR is extended, the NB shall determine what was transmitted on the UL-SCCH when calculating the PHR. cannot be done.

[0129] Below we present several ways to address this issue. First, the calculation of PHR Provides additional indication to the PHR that allows the NB to determine when this has occurred. It may be the delay due to LBT relative to the time of the first LBT failure, or it may be an absolute time reference. The second method is to inform the NB what has been transmitted on the UL-SCCH. Provides additional information with the PHR, which approximates what was transmitted on the UL-SCCH It may be an indexed value or the physical details of the transmission when calculating the PHR. In the third method, the NB can calculate the effective delay incurred by the LBT due to the PHR. The failure or success of the LBT may be independently indicated to the NB so that it can be determined. The method uses the grant used when the PHR was calculated (e.g., uplink grant) ) with the PHR to inform the NB.

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

[0131] Here is another example: The trigger condition for PHR should consider LBT failure. Available UL resources, PHR periodic timer expiry, PHR reconfiguration, SCell activation; and PSCell additional trigger criteria should only be considered if LBT is successful. The addition of LBT criteria is mutually exclusive to each existing trigger, and therefore: It may only affect a subset of existing criteria.

[0132] For example (if all triggers are taken into account), the MAC specification might be modified as follows: . If any of the following events occur, the Power Headroom Report (PHR) shall be triggered. The phr-ProhibitTimer expires or expires and the MAC entity The entity has UL resources for a new transmission and this transmission is blocked due to an LBT failure. If no PHR has been received since the last transmission of a PHR at this MAC entity, At least one activated MAC entity is used as a reference for the For the serving cell, the path loss is phr-Tx-PowerFactorChang changed by more than e dB, Note 1: The path loss variation of one cell evaluated above is currently The measured path loss and the path loss reference in use at the time of the last PHR transmission between the path loss measured at the time of the It's irrelevant. phr-PeriodicTimer expires and then LBT is successful, When the power headroom reporting function is configured or reconfigured by higher layers, the LBT is subsequently is functional and is not used to disable its functionality, Activating the SCell of the MAC entity with the configured uplink; LBT then becomes successful, Addition of a PSCell (i.e., when a PSCell is newly added or changed), and subsequent success of LBT, The phr-ProhibitTimer expires or expires and the MAC entity If the service has UL resources for a new transmission and this transmission is blocked due to an LBT failure, The active MAC entity has no uplink configured. For any of the subscribed serving cells, the following is true: This cell has UL resources allocated for transmission or PUCCH transmission and the power management for this cell (as specified in TS38.101

[10] ) The required power backoff by the P-MPRc) is After transmission, the MAC entity determines if this cell has been allocated UL resources for transmission. When there was a PUCCH transmission or when there was a PUCCH transmission, rChange Changed by more than dB.

[0133] These changes are calculated by the PHR when the LBT is successful and the UE accesses the channel. or may be necessary to ensure that the information is transmitted.

[0134] Here is another example: PHR calculation and transmission is only considered if LBT is successful. It should be.

[0135] Nominal UE maximum transmit power and UL-SCH transmission per activated serving cell or the difference between the estimated power of the SRS transmission and the nominal UE maximum power and SpCel and the estimated power of UL-SCH and PUCCH transmission on the PUCCH SCell. Calculations using differential information should also only be considered in the case of successful LBT.

[0136] When checking whether UL resources are available for the PHR MAC CE, the LBT It may also be necessary to determine success. Having available UL resources may It does not matter whether the MAC CE's transmission is blocked by LBT.

[0137] For example, the MAC specification may be modified as follows: The MAC entity has UL resources allocated for the new transmission and the LBT is successful. If successful, the MAC entity: 1> First UL resource allocated for a new transmission since the last MAC reset If 2> Start phr-PeriodicTimer, 1> The power headroom reporting procedure triggers at least one PHR and cancels If it is determined that the cell is not celled, and 1> The allocated UL resources are allocated to the MAC entity as a result of the logical channel prioritization. MAC CE for the PHR that the entity is configured to send, and its subheader If applicable, and 1>LBT was judged to be successful, 2>If multiplePHR is set, 3> For each access point with a configured uplink associated with any MAC entity For the activated serving cell, 4> Type 1 or Type 3 power head loop for the corresponding uplink carrier Get the value of 4> This MAC entity has allocated U for transmission in this serving cell If the LBT is successful and the LBT has been successful, or 4> The other MAC entity (if configured) receives the allocated MAC address for transmission. If the cell has UL resources and the LBT is determined to be successful in this serving cell, and the higher layer If -ModeOtherCG is set to real, 5> Corresponding P from the physical layer CMAX,f,c Get the value of the field, 3>If phr-Type2SpCell is set, 4> Set the Type 2 power headroom value for the SpCell of this MAC entity. Get it, 4> Corresponding P from the physical layer CMAX,f,c Get the value of the field, 3>If phr-Type2OtherCell is set, 4> If other CGs are set, 5> Type 2 power headroom value for the SpCell of the other MAC entity Get 5> If phr-ModeOtherCG is set to a real value by a higher layer, 6> The physical layer sends the corresponding P to the SpCell of the other MAC entity. CMAX, f,c Get the value of the field, 4> Otherwise, if the PUCCH SCell is configured and activated, 5>Get the Type 2 power headroom value for the PUCCH SCell. 5> Corresponding P from the physical layer CMAX,f,c Get the value of the field, 3> If the LBT is judged to be successful, the procedure in 6.1 of [2] is followed based on the value reported by the physical layer. The configured ServCellIndex and MA, as defined in Section 3.9. Generate and send PHR MAC CE according to the PUCCH(s) of the C entity and instructing the multiplexing and assembly procedure to 2> Otherwise (i.e., the single-entry PHR format is used), 3> Type 1 power header routing from the physical layer of the corresponding uplink carrier of the PCell Get the value of 3> Corresponding P from the physical layer CMAX,f,c Get the value of the field. 3> If the LBT is judged to be successful, the procedure in 6.1 of [2] is followed based on the value reported by the physical layer. 4.3.8, to generate and transmit the PHR MAC CE. directing the multiplexing and assembly procedure to 2> Start or restart phr-PeriodicTimer, 2> Start or restart phr-ProhibitTimer, 2> Cancel all triggered PHR(s).

[0138] While the above example MAC-specific modifications are described in terms of LBT success, the examples are It may be expressed in terms of no BT failures as well. It should be noted that in this example, the modifications are mutually exclusive. Sometimes only a kit is required.

[0139] Another example is shown below. Furthermore, when an LBT failure is detected for a transmission containing a MAC PHR CE, , the PHR prohibit timer should not be set, or cleared if set. It is disclosed that

[0140] When the physical layer is instructed to transmit a MAC PDU containing a MAC PHR CE, the PHR The prohibit timer is started or restarted only upon determination of LBT success for a MAC PDU transmission. For example, the MAC specification may be modified as follows: 1>If the LBT is judged to be successful, 2> Start or restart phr-PeriodicTimer, 2> Start or restart phr-ProhibitTimer, 2> Cancel all triggered PHR(s).

[0141] While the above example MAC-specific modifications are described in terms of LBT success, the examples are It may also be expressed in terms of no BT failures.

[0142] Alternatively, the PHR inhibit timer or PHR period timer may be set as in the existing procedure. It may be started, but if it is determined that the LBT has failed, the PHR prohibition timer is cleared. or the PHR period timer is reset to the remaining value before the last reset due to an LBT failure. Alternatively, it may be reset to a different time value, such as a set time value.

[0143] This modification prevents the PHR prohibit timer from being set so that subsequent PHR transmissions cannot be delayed. or periodically when PHR transmission is blocked by LBT failure. Ensure that the PHR period timer is not reset so that a valid PHR is not delayed. Sometimes it's necessary to make it real.

[0144] (SCell activation / deactivation) The following modifications to the SCell activation / deactivation procedure are required for L in NR-U: Take into account the impact of BT.

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

[0146] Due to LBT failure, NB misses DL transmission opportunity (downlink allocation (single or multiple) One or more MAC PDUs may be lost) or UL transmission may be blocked (MAC PDUs When the UE detects that the SCell is not being transmitted, the SCell deactivation timer is extended. .

[0147] There may be several options how to achieve this. -SCell deactivation timer is extended or restarted when LBT failure is detected If an LBT failure is detected when the SCell deactivation timer expires, The inactivity timer is extended or restarted.

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

[0149] For example, the MAC specification may be modified as follows: 1> Otherwise, deactivate the SCell. If an activated MAC CE is received, or 1> sCellDeactivation associated with activated SCell If nTimer expires and no LBT failure is detected, 2> Deactivate the SCell according to the timing defined in TS 38.213. Turn it into a 2> Stop the sCellDeactivationTimer associated with the SCell do, 2> Stop the bwp-InactivityTimer associated with the SCell, 2> Any configured downlink allocation associated with the SCell, and any Clear each of the configured uplink grants of type 2, 2> Any configured uplink grant type 1 associated with the SCell Pause, 2> Flush all HARQ buffers associated with the SCell. 1> sCellDeactivation associated with activated SCell If nTimer expires and LBT failure is detected, 2> Restart the sCellDeactivationTimer associated with the SCell. Move.

[0150] In the above step(s), an LBT failure is detected when a non-SCell During the activation timer running, from SCell deactivation or configuration Since the last MAC PDU was transmitted in the configured uplink grant, or SCell inactivity since the UE last received a specified downlink allocation The period from the time the activation timer is set until it first expires or until the LBT detection The next SCell inactivity time since the Cell inactivity timer expired and last started. Note that this applies to the period until the activation timer expires.

[0151] Or, when an LBT failure of an SCell is detected, 1>If an LBT failure is detected, 2> Restart the sCellDeactivationTimer associated with the SCell. Move.

[0152] Or, LBT failure or LBT success, or consecutive LBT failure or consecutive LBT A procedure may be defined to count successes. , if the configured maximum LBT failure threshold is exceeded, or if the LBT is successful or if consecutive LBT successes occur SCell inactivity occurs only if the LBT success rate can be less than the configured minimum LBT success threshold. For example, the MAC specification may be modified as follows: 1>ScellDeactLBT-Failure-Count>ScellDeact If LBT-Failure-Threshold, 2> Restart the sCellDeactivationTimer associated with the SCell. Move, 2>Set ScellDeactLBT-Failure-Count to 0. 1>If an LBT failure occurs, 2>Increment ScellDeactLBT-Failure-Count.

[0153] Alternatively, the SCell deactivation timer may be set to The SCell deactivation timer can be extended for a different period than the The period may be another set value, or may be determined based on the number of LBT failures detected or determined. It may be a value depending on the amount of success, and may also be a value that ensures that the UE is never deactivated. ,Significantly extending the SCell deactivation timer or,LBT failure In some cases, it may be necessary to avoid extending the inactivity timer indefinitely. If , the SCell deactivation timer restarts at the specified or configured maximum For example, the MAC specification may be modified as follows: 1>ScellDeact-LBT-Failure-Count>ScellDeact t-LBT-FailureThreshold, and 1>LBT-ScellDeactTimerRestartCount<=LBT-S If cellDeact-Restart-Threshold, 2> Set ScellDeact-LBT-Failure-Count to 0, 2> Set LBT-ScellDeactTimerRestartCount to 1 Rement, 2> Restart the sCellDeactivationTimer associated with the SCell. Move. 1>If an LBT failure is detected, 2> Increment ScellDeact-LBT-Failure-Count .

[0154] If ScellDeact-LBT-FailureThreshold is exceeded, You may perform the following actions: 1>LBT-ScellDeactTimerRestartCount<=LBT-S If cellDeact-Restart-Threshold, 2> Make the SCell inactive according to the timing defined in TS38.213[6]. Actively 2> Stop the sCellDeactivationTimer associated with the SCell do, 2> Stop the bwp-InactivityTimer associated with the SCell, 2> Any configured downlink allocation associated with the SCell, and any Clear each of the configured uplink grants of type 2, 2> Any configured uplink grant type 1 associated with the SCell Pause, 2> Flush all HARQ buffers associated with the SCell.

[0155] (Discontinuous Reception (DRX)) The following modifications of 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 switched to long DRX. This transition occurs when a successful LBT is detected or when the LBT It should only be executed if no failures are 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 the drx-ShortCycleTimer.

[0157] Disclosed herein are set thresholds for maximum LBT failure or minimum LBT success. The UE will only initiate DRX if the count of LBT failures or LBT successes exceeds a threshold. Short cycles may continue to be used. For example: 1> The drx-ShortCycleTimer expires and the LBT success counter is the minimum LB If the success threshold is exceeded, 2> Use a long DRX cycle, 2> Otherwise, 2>Start or restart the drx-ShortCycleTimer.

[0158] Alternatively, if an LBT failure is detected or if an LBT success is not detected, Extend the DRX active time, which means starting or restarting the DRX inactivity timer. Also, when the DRX inactivity timer expires, the DR This will start or restart the X short cycle timer, which will This allows the cycle to continue to be used. Additional PDCCH UL and DL signals may be required for tuning opportunities. Scheduling opportunities may be possible. For example, modifying the MAC specification as follows: good. 3>If the PDCCH indicates a new transmission (DL or UL), 4> drx-InactivityTime at the first symbol after PDCCH reception Start or restart r, 3>If LBT failure is detected, 4>Start or restart the drx-InactivityTimer.

[0159] Preferably, the DRX inactivity timer is started or restarted when the LBT is lost within a certain period of time. The duration depends on the number of times that the LBT is not detected or the number of times that the LBT is not detected. duration of the inactivity timer or duration of the on-duration and inactivity It can be a combination of the time that the active timer is running, for example: 1>If LBT success is not detected, drx-onDurationTimer When it expires, 2> Start or restart the drx-InactivityTimer, 1> If LBT success is not detected, the drx-InactivityTimer When it expires, 2>Start or restart the drx-InactivityTimer.

[0160] LBT failure may not be a single instance. Multiple LBT failures or successes The DRX procedure may be the detection of a series of LBs that affect the UE reception of the PDDCH. It may only be started after a T failure.

[0161] Counting a missed or successful LBT, or consecutive missed or consecutive LBs A procedure may be defined to count T successes, LBT failures, or consecutive LBT failures. exceeds the configured maximum LBT failure threshold, or if the LBT is successful or consecutive DRX inactive only if success can be less than the configured minimum LBT success threshold The timer is restarted. For example, 1> If the LBT success count is less than the LBT minimum success threshold, the on-duration timer When expires, 2>Start or restart the drx-InactivityTimer. Also, the DRX inactivity timer is significantly reduced so that the UE never enters DRX. or extending the DRX inactivity timer indefinitely due to an LBT failure. In some cases, it may be necessary to avoid this, in which case the DRX inactivity timer restart is The MAC specification may be limited to a specified or configured maximum value. For example, It may be corrected to. 1>DRX-Inactivity-LBT-Failure-Count>DRX-I nactivity-LBT-FailureThreshold, and 1>DRX-Inactivity-TimerRestartCount<=DRX- If Inactivity-Restart-Threshold, 2> Set DRX-Inactivity-LBT-Failure-Count to 0 hand, 2> Set DRX-Inactivity-TimerRestartCount to 1. Increment, 2> Start or restart the drx-InactivityTimer, 1>If an LBT failure is detected, 2>Increment DRX-Inactivity-LBT-Failure-Count Enter. If DRX-Inactivity-LBTRestartThreshold is exceeded If so, the following actions may be taken: 1>DRX-Inactivity-TimerRestartCount>DRX-I Inactivity-Restart-Threshold 2> If a short DRX cycle is configured, 3>drx - First symbol after InactivityTimer expires, or DRX The first symbol after the end of receiving the command MAC CE is drx-ShortCycle Start or restart the Timer 3> Use a short DRX cycle, 2> Otherwise, 3> Use long DRX cycles.

[0162] By initiating or restarting inactivity time when an LBT failure occurs Extending the DRX active time is a configurable option or is currently It should depend on the active service, for example, if the URLLC service is supported. If LBT failures can be avoided, it is better to maintain scheduling opportunities when LBT failures occur. It becomes more important.

[0163] Alternatively, the DRX active time extension can be extended by the configured DRX inactivity time. The period of the timer may be different from that of the timer itself. A period relative to the amount of LBT failures detected during the current DRX active time period. Good too.

[0164] In another example, the DRX procedure can be dynamically adapted to reduce the overhead caused by LBT operation. There may be a way to address the inefficiency of DRX: the UE wakes up each DRX cycle. When using the DRX option, the DRX setting may be dynamically adjusted depending on the LBT operation. You may periodically adjust the duration, inactivity, or DRX cycle. This may be every DRX cycle.

[0165] Before transmission, the NB determines the clear channel assessment (CCA) and assigns the channel access priority class. Select CAPC. CAPC includes the maximum channel occupation time (MCOT) and cost A Constraint Window Size (CWS) is selected. Transmission is not permitted during the MCOT period. However, transmissions cannot be made during the CCA and CWS periods. The DRX operation of the UE can be dynamically adjusted to dynamically adjust the timing, as determined by the NB. This allows the signal to better match the available transmission opportunities.

[0166] To achieve this, the downlink In addition to or included in the LBT success indication, the CCA period, selected MCOT, CWS or other timing information may be provided to the MAC, and the downlink and uplink This allows for more accurate determination of transmission opportunities for the Plink. Other timings are determined by the channel access priority class (CAP) that represents the selected timing. C) or may be identified by another index.

[0167] Based on the reception of LBT timing information, the UE DRX procedure is aligned with the MCOT period. Dynamically adjusts the active time to accommodate DRX during CWS and possibly CCA periods. applies.

[0168] For example, at the beginning of each DRX cycle, the MCOT selected by the NB is ondurated. Similarly, the inactivity timer must be set to match the selected MCOT. The setting may be configured to:

[0169] Alternatively, the UE may enter DRX during the CWS and possibly CCA periods. For example, Active Time may overlap with MCOT periods or may include CWS and possibly CC. Only on-duration and inactive time periods that do not overlap with the A period are included. For example, the MAC specification may be modified as follows:

[0170] If a DRX cycle is configured, the active time includes the following times: . 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 running Between, and While the drx-MCOT-Timer is running.

[0171] or alternatively, If a DRX cycle is configured, the active time includes the following times: . 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 running Between, and While the drx-CWS-Timer is not running.

[0172] (Scheduling Request) The following modification of the SR procedure takes into account the effect of LBT in NR-U.

[0173] If there is a pending SR and the LBT is determined to have failed for a period of time, A random access procedure should be initiated and any pending SRs should be cancelled. This may be necessary if PUCCH resources become unavailable due to an LBT failure. In this case, an RA procedure is attempted, and if this procedure fails, a radio 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 In contrast, it is assumed that: 1> The MAC entity configures a valid PUCCH resource for the pending SR. If not, or 1>If an LBT failure is detected, 2> Start the random access procedure (see, for example, Section 5.1 of [2]) in the SpCell. , cancel a pending SR.

[0174] The validity of PUCCH resources is also defined for LBT success or LBT failure. For example, the MAC specification may be modified as follows:

[0175] PUCCH link on BWP active during SR transmission opportunity where LBT failure is not determined Only the source is considered valid.

[0176] As long as at least one SR is pending, the MAC entity will For , it is assumed that: 1> The MAC entity configures a valid PUCCH resource for the pending SR. If not, 2> Start the random access procedure (see, for example, Section 5.1 of [2]) in the SpCell. , cancel a pending SR.

[0177] The above example is sometimes expressed in terms of detecting "no LBT failure", but it can also be expressed in terms of "LBT success". LBT failure or LBT success is sometimes expressed as the detection of a single instance. There may be multiple LBT failures or successes detected. The RA procedure It may be started only after a series of LBT failures that affect the SR transmission of PUCCH.

[0178] A procedure 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 success is less than the set minimum LBT success threshold, the random access procedure is started only.

[0179] Another example is shown below. When the physical layer is instructed to transmit an SR, the SR prohibition timer is started only when determining the LBT success for the SR transmission, 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 2> when the sr-ProhibitTimer is not running at the SR transmission opportunity, and 2> when the PUCCH resource of the SR transmission opportunity does not overlap with the measurement gap, and and 2> when the PUCCH resource at the time of SR transmission does not overlap with the UL-SCH resource, and 2> when 3> SR_COUNTER < sr-TransMax, and 4> instruct the physical layer to signal an SR on one valid PUCCH resource for the SR, 4> and when determined to be LBT successful, 5> start the sr-ProhibitTimer, 5> and increment the SR_COUNTER by 1.

[0180] Alternatively, as is done in existing procedures, the SR inhibit timer is started and the SR counter is The prohibition timer may be incremented, but if the LBT is determined to be unsuccessful, the prohibition timer is stopped. The SR counter may be decremented.

[0181] This fix is ​​that the SR counter does not reach the SR Trans Max, causing the SR transmission Release physical resources and initiate RA procedures when the device is blocked due to an LBT failure. Ensure that no SR inhibit timer is set that would delay subsequent SR transmissions, so that For this reason, it may be necessary.

[0182] Also, to ensure that the UE never determines that the SR transmission procedure was not successful, the LBT failure Do not increment the SR transmission counter significantly or disable the SR transmission counter. It may be necessary to avoid not incrementing the SR transmission count at the deadline. The non-incrementing can be limited to a specified or configured maximum value. For example, the MAC specification may be modified as follows: 2> If no SR LBT failure is detected, or 2>SR-Transmission-LBT-Failure-Count>SR-T If transmission-LBT-FailureThreshold, 3>Increment SR_COUNTER by 1, 3> 2>If SRTransmission-LBT-Failure is detected, 2>Increment SRTransmission-LBT-Failure-Count Enter.

[0183] RA-PreambleTransmission-LBT-FailureThre If the threshold is exceeded, the following actions may be taken or the MAC specification may be modified as follows: You can modify it as follows. 2>If SR-Transmission-LBT-Failure is detected, 2>Increment SR-Transmission-LBT-Failure-Count Mention it, 2>SR-Transmission-LBT-Failure-Count>STra nsmission-LBT-FailureThreshold,

[0184] Here is another example: Pending only if LBT success is determined for BSR transmission. The SR(s) may be cancelled and the SR inhibit timer may be stopped. ,Prohibition of delaying subsequent SR transmission when the current SR cannot be transmitted due to LBT failure May be necessary to ensure that the timer is not set.

[0185] For example, if the LBT is determined to be successful for a MAC PDU transmission, this PDU is The last event that triggered the BSR (see section 5.4.5 of [2]) before the PDU assembly If the BSR MAC CE has buffer state up to (and including) Any pending SRs triggered before MAC PDU assembly shall be cancelled. and each sr-ProhibitTimer shall be stopped.

[0186] The above example can be expressed in terms of LBT failure detection instead of LBT success detection as follows: If an LBT failure is not detected for a MAC PDU transmission, this PDU may be C The last event that triggered the BSR (see section 5.4.5 of [2]) before the PDU assembly Contains the BSR MAC CE with buffer state up to (and including) the event If this occurs, any pending SRs triggered before MAC PDU assembly are cancelled. and each sr-ProhibitTimer shall be stopped.

[0187] Alternatively, when a MAC PDU containing a BSR is presented to the PHY layer, the existing procedures Any pending SR(s) may be cancelled and the inhibit timer may expire. It may be stopped, but if LBT failure (or equivalently, no LBT success) is detected, If set, any pending SR(s) are restored and the inhibit timer is restarted. This may also be done.

[0188] (Buffer status report) The following modification of the BSR procedure takes 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, but If a transmission is blocked due to an LBT failure, an SR may be triggered. If an available grant is lost due to a This may be necessary because a new SR may be needed to ensure For example, the MAC specification may be modified as follows: 2> A regular BSR is triggered and logicalChannelSR-DelayTi If mer is not running, 3> If there are no UL-SCH resources available for new transmissions, or 3> The MAC entity has one or more uplink grants configured. Logical channel SR masking is performed by higher layers. If a regular BSR is not triggered for a logical channel with SR-Mask configured, If so, or 3> UL-SCH resources available for new transmissions trigger the BSR(s). The LCP mapping limit (5 in [2]) set for the logical channel(s) (see section 4.3.1) or 3> There are UL-SCH resources available for transmission and LBT failure is detected for this transmission If 4> Trigger a scheduling request.

[0190] The above revised text is written from the perspective of LBT failure, but it can also be written from the perspective of LBT without success. It may also be expressed as a point.

[0191] An LBT failure or LBT success may not be a single instance. T may be a failure or success detection. SR does not affect MAC BSR CE transmission. It may only be triggered after a series of LBT failures.

[0192] Also, count LBT failures or LBT successes, or consecutive LBT failures or A procedure may be defined to count consecutive LBT successes. If BT failure exceeds the configured maximum LBT failure threshold, or if LBT success or consecutive SR is triggered only if the LBT success can be less than the set minimum LBT success threshold. can be.

[0193] BSR MAC CE transmission is blocked due to LBT failure and retransmits after a certain time If so, to inform the NB when the BSR was calculated or when the PHR was calculated. Additional signaling is introduced to inform the NB of the transmission conditions when

[0194] For the NB to handle the BSR properly, it must know when the BSR was calculated. It may be necessary to

[0195] If not operating in an unlicensed frequency band and LBT is not used, the NB The SR content can be roughly obtained when it was determined. NB is scheduled and I am aware of what I have received and the rules of the BSR, so I can interpret the BSR appropriately. However, if LBT fails and transmission is delayed until LBT succeeds, the NB becomes stale. It may receive a BSR or an incorrect BSR, which may be needed by the UE. More resources allocated than required or less resources than required by the UE This leads to a penalty in terms of the service, transmission delay and QoS guarantee. We present several ways to handle this. The first method is to determine when the BSR calculation is constructed. Provides an additional indication to the BSR that the NB can use to determine if the first LBT failure occurred. It may be a delay due to LBT relative to the time between the two, or it may be an absolute time reference. In this method, so that the NB can determine the effective delay incurred by the LBT for the BSR, The failure or success of the LBT may be indicated independently to the NB. In the third method, the PHR is calculated. Inform the NB of the grants used when the grant was calculated (e.g., uplink grants) Provide additional information with the PHR.

[0196] It is preferable to receive additional information that allows the NB to know when the BSR was established. It is preferable, but not necessary, to provide accurate information. This means that the UE notifies the NB of the LBT failure and By showing success, NB can determine that there was an LBT failure that delayed the BSR. This can be realized by:

[0197] Here is another example: The trigger condition for BSR should consider LBT failure. Data becomes available and the currently specified regular BSR trigger criteria, padding B The trigger criteria for the SR trigger condition, BSR retransmission timer expiration, and BSR period timer expiration are met. The addition of LBT criteria should only be considered if LBT has been successful. Mutually exclusive to triggers and therefore only affects a subset of existing criteria Can be given.

[0198] For example (if all triggers are taken into account), the MAC specification might be modified as follows: . A BSR shall be triggered if any of the following events occur: The MAC entity receives new UL data available for logical channels belonging to the LCG. has, and The new UL data is stored in any logical group that contains available UL data belonging to any LCG. belongs to a logical channel with a higher priority than the channel priority, and the LBT subsequently succeeds ,or, None of the logical channels belonging to the LCG contain available UL data, and BT then becomes successful. In this case, the BSR is called a "regular BSR" as follows: UL resources are allocated and the number of padding bits is reported to the buffer status report MAC If the size is equal to or greater than the size of the CE plus its subheader, and the LBT is subsequently successful, the BSR is called "Padding BSR" as follows: The retxBSR-Timer expires and at least one of the logical channels belonging to the LCG If one contains UL data and the LBT is subsequently successful, then the BSR can be This is called "regular BSR" If the periodicBSR-Timer expires and the LBT is subsequently successful, the BSR is called a "periodic BSR" as follows: The MAC entity shall be: 1> The buffer status reporting procedure triggers at least one BSR to report the buffer status. If it is determined that the cancellation has not been made, 2> If UL-SCH resources are available for new transmission and LBT is determined to be successful If, 3> Multiplex and assemble to generate BSR MAC CE(s). Instruct the procedure 3> Unless all generated BSRs are long or short truncated SRs, p Start or restart the periodicBSR-Timer 3>Start or restart the retxBSR-Timer.

[0199] Even if multiple events trigger a BSR, a MAC PDU is sent to at most one BSR. Regular and periodic BSRs are implemented using padding. It shall take precedence over BSR.

[0200] The MAC entity may request a grant for the transmission of new data on any UL-SCCH. When this is received, the retxBSR-Timer shall be restarted.

[0201] The UL grant(s) must be able to accommodate all pending data available for transmission and must be LBT successful. It has been determined that this is a success, but it is sufficient to additionally accommodate the BSR MAC CE and its subheaders. If the LBT is not successful, all triggered BSRs can be canceled. When a MAC PDU containing a BSR MAC CE is transmitted, the MAC PDU is assembled. All BSRs triggered before the BSR shall be cancelled. The above revised text is written from the perspective of LBT success, but it is not written from the perspective of LBT failure. It may also be expressed as a point.

[0202] An LBT failure or LBT success may not be a single instance. T may be a failure or success detection. SR does not affect MAC BSR CE transmission. It may only be triggered after a series of LBT failures.

[0203] Also, counting LBT failures or LBT successes, or consecutive LBT failures or successes You may define a procedure to count consecutive LBT successes. If the LBT failure exceeds the configured maximum LBT failure threshold, or if the LBT success or SR is triggered only if consecutive LBT successes can be less than the set minimum LBT success threshold. Be ragged.

[0204] While the above example MAC-specific modifications are described in terms of LBT success, the examples are It may be expressed in terms of no BT failures as well.

[0205] Alternatively, the BSR period timer and the BSR retransmission timer may be set as they are in existing procedures. However, if the LBT is determined to be a failure, the BSR period timer and the BSR retransmission timer to the remaining value before the last reset due to an LBT failure, or It may be reset to a different time value, such as a set time value.

[0206] This fix reduces the BSR period when BSR transmission is blocked due to LBT failure. BSR period timer or BSR retransmission timer to prevent delays in automatic transmission or BSR retransmission. This may be necessary to ensure that the transmit timer cannot be reset.

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

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

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

[0210] The MAC entity shall use the MAC P of the HARQ entity if the following conditions are met: DU shall not be generated. The MAC entity is configured with skipUplinkTxDynamic and H The grant presented to the ARQ entity is addressed to the C-RNTI, and is the uplink grant configured for the grant indicated to the HARQ entity, and, - The non-transmission required for this PUSCH transmission as specified in TS38.212 There is no periodic CSI, and The MAC PDU contains 0 MAC SDUs, and The MAC PDU contains only periodic BSRs and the data available to any LCG. There is no data or the MAC PDU contains only a padding BSR, or No LBT failures were detected.

[0211] Alternatively, the criteria may be that a successful LBT is detected.

[0212] This modification may result in this MAC PDU not being accepted for subsequent grants (e.g. For example, for the size of the UL grant), and the generated MAC CE(s). ) may provide incorrect information (e.g., PHR, BSR...) when transmitting MAC PDUs For this reason, it may be necessary.

[0213] Another example is shown below. Alternatively, a MAC PDU may be generated and provided to the physical layer. ,If an LBT failure for this MAC PDU is detected, the LCP ,procedure must be restarted to establish a new MA. Generate a C PDU.

[0214] To achieve this, the MAC SDU embedded within this MAC PDU is These MAC SDUs may be stored until the LBT success is determined. Instead of having to recreate these MAC SDUs from the MAC PDUs It can be easily reprocessed.

[0215] In the simpler case, if the grant is larger, the UE removes the padding and The UE can either multiplex additional data in the remaining space according to the CP, or AC SDU and CE) to ensure that data has been processed for the previous grant. The goal is to recreate the LCP as if it had never been created.

[0216] However, even in this case, the MAC CE previously determined by the LAA has already been established. In some cases, older PHR CEs may be allowed. In that case, the network Based on the submission, it may be unclear how the PHR was calculated.

[0217] Timers and counters for MAC procedures (BSR, PHR...) are counted from the last (failed) transmission. Reconstructing the CE is complicated because it has already been affected by trust.

[0218] The trigger is re-evaluated when the MAC PDU multiplexing and assembly is re-performed. , the MAC CE may 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 complicated case is what to do when the grant is smaller. First, the LCP Then, it determines what can be sent from the previous PDU according to Recover a MAC SDU and the timers of the MAC procedures associated with the MAC CE's transmission Resets the timers and counters to the values ​​they had before the MAC CE was constructed. The parameter can be set.

[0220] No new high priority data or other MAC CE triggers have been received since the last transmission. To address this possibility, multiplexing assemblies The retry procedure does not prioritize MAC SDUs associated with failed MAC PDU transmissions. There is a saying.

[0221] Similar issues can occur with MAC CE, which are now outdated and no longer available on MAC Backing out procedures are complicated.

[0222] The NB will be informed that the MAC CE transmission has been delayed or will be sent back when it was originally scheduled to be sent. You should know.

[0223] Another problem is that segmentation is performed in RLC, and the SDUs in the MAC may be too large. The MAC request causes RLC to back out the previous RLC PDU. One way to deal with this is to use a RLC PDUs, and other S that may not be multiplexed into a new MAC PDU transmission. The solution is to spoof an RLC negative response to the DU.

[0224] (Beam Failure Detection and Recovery) The following modifications to the beam obstruction and detection procedures take into account the effects of LBT in NR-U: Even if the beam failure recovery timer expires, the random access procedure for beam failure recovery is If an LBT failure is detected since the start of the sequence, the beam failure recovery timer should be extended. This can result in early expiration of the beam failure recovery timer and possibly cell reselection or RR. This may be necessary to avoid C(re)establishment.

[0225] The entities performing the steps shown in this specification, such as those shown in FIGS. 2-10, are logically It is understood that the steps may be performed by any entity. Stored in the memory of a device, server, or computer system such as The exemplary method disclosed herein may be stored in a processor and executed on the processor. You can skip steps, combine steps, or It is intended to be added.

[0226] Table 1 provides exemplary abbreviations or definitions.

[0227] [Table 1-1]

[0228] [Table 1-2]

[0229] [Table 1-3]

[0230] FIG. 11 illustrates the method, system, and methodology for the NR-U LBT MAC procedure described herein. and device (e.g., a graphical user interface). A display interface 901 (e.g., a touch screen) is shown. The display (Non-display) provides information on NR-UL, especially PHR-related parameters and method flows. The text of block 902 associated with the BT MAC procedure may be provided. Progress of any of the steps described in the document (e.g., messages sent or steps A successful completion of the process may be displayed in block 902. Additionally, the graphical output 902 may include The graphical output may be displayed on a display interface 901. Topologies of devices implementing methods, systems, and devices for BT MAC procedures; A graphical output of the progress of any method or system discussed herein, Good too.

[0231] 3rd Generation Partnership Project: 3GPP) is a group of companies that develops radio access, core transport networks, and codecs. ,security, and service capabilities, including work on quality of service, cellular Developing technical standards for communication network technology. :RAT) standards include WCDMA (commonly known as 3G), LTE (commonly known as LTE-Advanced standards, and the new LTE standard also known as "5G." There is a new radio technology (New Radio: NR). Development of the 3GPP NR standard will continue. This is expected to include the definition of next generation radio access technologies (new RATs). New flexible wireless access offerings below 7 GHz and new ones above 7 GHz This is expected to include the provision of ultra-mobile broadband wireless access. Flexible wireless access is a new, non-backward compatible wireless technology in new frequency bands below 6 GHz. It consists of line access and includes 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 different requirements. Mobile broadband includes ultra-high-speed applications such as indoor use and hotspots. Centimeter and millimeter wave frequency bands offer mobile broadband access opportunities. It is expected that ultra-mobile broadband will include centimeter waves and and mmWave-specific design optimization for flexible wireless access below 7 GHz It is anticipated that a shared design framework will be used.

[0232] 3GPP has identified a variety of use cases that NR is expected to support. This results in a wide variety of user preferences regarding data rates, latency, and mobility. The use cases fall into the following general categories: Enhanced Mobile Broadband (eMBB) ultra-reliable, low-latency communications Ultra-Reliable Low-Latency Communication (URLLC), large-scale machine types Massive Machine Type Communications (mMTC), network operations (e.g. For example, network slicing, routing, migration and interworking and Enhanced Vehicle-To-Everything : eV2X) communication, Vehicle-To-Vehicle Communication (V 2V), Vehicle-To-Infrastructure Communication :V2I), Vehicle-To-Network Communication (V2N) , Vehicle-To-Pedestrian Communication (V2P), and other These categories include vehicle communications with the public or private entities. Specific services and applications include, for example, monitoring and sensor networks, data Remote control of devices, two-way remote control, personal cloud computing, video Streaming, Wireless Cloud-Based Office, and First Responder Connectivity , Automobile emergency call system, Disaster warning, 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. All of these and other use cases are contemplated herein.

[0233] FIG. 12A illustrates the system and method shown in FIGS. 1 through 10 as described and claimed herein. Exemplary methods and apparatus for the NR-U LBT MAC procedure, such as A communication system 100 is shown. The communication system 100 includes a wireless transceiver unit (WTE). ansmit / Receive Unit:WTRU)102a, 102b, 102c, 102d, 102e , 102f, or 102g (which may be referred to generally or collectively as WTRU102 or The communication system 100 may include a wireless access point (WTRU) 102. 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, It may also include other networks 112 and network services 113. The network service 113 includes, for example, a V2X server, a V2X function, a ProSe server, a Pro Se functionality, IoT services, video streaming, or edge computing It may include, etc.

[0234] The concepts disclosed herein may be implemented in any number of WTRUs, base stations, networks, or networks. It will be appreciated that the WTRU 102a may be used in conjunction with other network elements. Each of 102b, 102c, 102d, 102e, 102f, or 102g is Any type of equipment or device configured to operate or communicate in a wired environment. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may 12A, 12B, 12C, 12D, 12E, or 12 Although the device may be illustrated as a handheld wireless communication device in F, it is not intended for 5G wireless communication. In the various use cases illustrated, each WTRU transmits or receives wireless signals. may include any type of apparatus or device configured to receive, and It will be appreciated that the present invention may be embodied in, by way of example only, User Equipment. t:UE), mobile station, fixed or mobile subscriber unit, pager, cellular telephone, Personal Digital Assistant (PDA), Smartphone Phones, laptops, tablets, netbooks, notebook computers, personal computers mobile computers, wireless sensors, home appliances, smart watches or smart wear, etc. Wearable devices, medical or electronic health devices, robots, industrial equipment, drones , vehicles such as cars, buses, trucks, trains, or airplanes.

[0235] The communication system 100 may also include a base station 114a and a base station 114b. In the example of FIG. 12A, each base station 114a and 114b is shown as a single element. In practice, base stations 114a and 114b may be any number of interconnected base stations or The base station 114a may include a core network 106 / 107 / 109, Internet 110, Network Services 113, or other networks WTRU to facilitate access to one or more communication networks, such as the network 112. 102a, 102b, and 102c. Similarly, the base station 114b may be any type of device configured to , Core Network 106 / 107 / 109, Internet 110, Other Networks 112, or network services 113. To facilitate access, a Remote Radio Head (RRH) 118a, 118b, Transmission and Reception Point (TRP) 119a , 119b, or at least one of the roadside units (RSUs) 120a, 120b. Any type of device configured to interface with one another wired or wirelessly The RRHs 118a and 118b may be connected to the core network 106 / 107 / 109. , the Internet 110, a network service 113, or other networks 112 to facilitate access to one or more communication networks, such as configured to wirelessly interface with at least one WTRU, e.g., WTRU 102c. It may be any type of device.

[0236] TRP119a, 119b are the core network 106 / 107 / 109, the internet network 110, network services 113, or other networks 112. To facilitate access to the communication network on It may be any type of device configured to wirelessly interface with one The RSUs 120a and 120b are connected to the core network 106 / 107 / 109, Internet 110, other networks 112, or network services 113, etc. To facilitate access to one or more communication networks, the WTRU 102e or 102f. For example, the base stations 114a and 114b may be wireless base station devices (Ba Transceiver Station (BTS), Node B, eNode B, Home Node B, Home eNodeB, Next Generation NodeB (gNodeB), satellite, site Whether it is a controller, access point (AP), wireless router, etc. good.

[0237] The base station 114a may be part of the RAN 103 / 104 / 105, which may include Base Station Controller (BSC), Wireless Network Controller Radio Network Controller (RNC), relay nodes, and other base stations or networks Similarly, the base station 114b may also include networking elements (not shown). 3b / 104b / 105b, which may include BSC, RNC, relay nodes The base station 11 may also include other base stations or network elements (not shown), such as 4a is a device that transmits or receives radio signals within a particular geographic area, which may be called a cell (not shown). Similarly, the base station 114b may be configured to receive the NR-U LBT MAC PROCEDURE METHOD, SYSTEM, AND DEVICE FOR SUCH CELL (not shown) within a specific geographic area that may be referred to as a Similarly, the base station 114b may be referred to as a cell (not shown). configured to transmit or receive wired or wireless signals within a specific geographic area The cell may be further divided into cell sectors. For example, the base station 114a The associated cell may be divided into three sectors. Thus, in one embodiment: The base station 114a may include, for example, three transceivers, one for each sector of the cell. In one embodiment, the base station 114a is a multiple-input multiple-output (MIO) Multiple Input / Output (MIMO) technology may be employed, thus allowing multiple transmitters per sector of a cell. A transceiver may also be used.

[0238] The base station 114a communicates with the WTRU 1 via the air interface 115 / 116 / 117. The device may communicate with one or more of 102a, 102b, 102c, or 102g, and may communicate with any suitable Wireless communication links (e.g., Radio Frequency (RF), microwave, infrared) Infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. The air interface 115 / 116 / 117 may be any suitable wireless interface. The IP address may be established using a RAT.

[0239] The base station 114b receives signals via wired or air interfaces 115b / 116b / 117b. RRH118a, 118b, TRP119a, 119b, or RSU120a, 120b, which may communicate with one or more of the cable, optical fiber, etc.) or wireless communication links (e.g., radio frequency (RF), microwave Wave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc. The air interfaces 115b / 116b / 117b may be implemented using any suitable radio access technology. (RAT) may be used.

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

[0241] WTRU 102a, 102b, 102c, 102d, 102e, or 102f is via air interfaces 115d / 116d / 117d such as IDR link communications. The communication may be via any suitable wireless communication link (e.g., radio frequency (RF), microwaves, infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. The air interface 115d / 116d / 117d may be implemented using any suitable wireless access point. The method may be established using RAT.

[0242] The communication system 100 may be a multiple access system, such as CDMA, TDMA, It employs one or more channel access methods such as FDMA, OFDMA, and SC-FDMA. For example, the base station 114a and the WTR in the RAN 103 / 104 / 105 In U102a, 102b, 102c, or RAN103b / 104b / 105b RRH118a, 118b, TRP119a, 119b and RSU120a, 120b and WTRUs 102c, 102d, 102e, and 102f are universal mobile communication Universal Mobile Telecommunications System (UMTS) terrestrial wireless access The wireless technology may be implemented using UMTS Terrestrial Radio Access (UTRA) or other wireless technologies. , and wideband CDMA (WCDMA) is used to communicate with the air interface 115 / 116 / 117 or 115c / 116c / 117c may be established respectively. DMA is a standard for High-Speed ​​Packet Access (HSPA) or evolving Includes communication protocols such as Evolved HSPA (HSPA+) HSPA stands for High-Speed ​​Downlink Packet Access. Packet Access (HSDPA) or High-Speed ​​Uplink Packet Access (High-Speed It may also include High-Speed ​​Uplink Packet Access (HSUPA).

[0243] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c, or , RRH118a, 118b, and TRP11 in RAN103b / 104b / 105b 9a, 119b, or RSUs 120a, 120b and WTRUs 102c, 102d is Evolved UMTS Terrestrial Radio Access (EUMTS Terrestrial Radio Access) It may also implement wireless technologies such as E-UTRA, Long Term Evolution ( Long Term Evolution (LTE) or LTE Advanced (LTE-Advanced) A) Using the air interface 115 / 116 / 117 or 115c / 116c / In the future, the air interfaces 115 / 116 / 117c may be established. 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies are based on LTE D2D and V2X technologies and interfaces. Similarly, 3GPP NR technology may include NR V Includes 2X technology and interfaces (e.g., sidelink communications).

[0244] The base station 114a and the WTRU 102a in the RAN 103 / 104 / 105 RAN 02b, 102c, and 102g, or RAN 103b / 104b / 105b RRH118a, 118b, TRP119a, 119b, or RSU120a, 1 20b and WTRUs 102c, 102d, 102e, and 102f comply with IEEE 802.1 6 (e.g., WiMAX (Worldwide Interoperability for Microwave Access)) , CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, provisional standard Interim Standard 2000 (IS-2000), Interim Standard 95 (Interim St Interim Standard 856 (IS-856) , GSM (Global System for Mobile communication) (registered trademark), EDGE (En Enhanced Data rates for GSM Evolution), GERAN (GSM EDGE), and other wireless technologies The technology may be implemented.

[0245] The base station 114c in FIG. 12A may be, for example, a wireless router, a Home Node B, a Home eNodeB, or a B, or an access point, and as disclosed herein, Establishments, to implement the methods, systems, and devices of the U LBT MAC procedure, Wireless connectivity in localized areas such as homes, vehicles, trains, air, satellites, factories, campuses, etc. Any suitable RAT for facilitating this may be utilized. and a WTRU 102, e.g., a WTRU 102e, that communicates with a wireless local area network (WLAN). (Wireless Local Area Network: WLAN) 1. Similarly, the base station 114c and the WTRU 102d may implement a radio technology such as , Wireless Personal Area Network (WPAN) ) wireless technology such as IEEE802.15 may be implemented. In this embodiment, the base station 114c and the WTRU 102, e.g., the WTRU 102e, To establish a cocell or femtocell, a cellular-based RAT (e.g., WCD MA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) may also be used. As shown in FIG. 12A, base station 114c has a direct connection to the Internet 110. Therefore, the base station 114c may be connected to the core network 106 / 107 / 109. It may not be necessary to access the Internet 110 via the

[0246] RAN103 / 104 / 105 or RAN103b / 104b / 105b are core networks. The network may be in communication with the network 106 / 107 / 109, which may include voice, Data, messaging, authorization and authentication, applications, or voice over internet Voice Over Internet Protocol (VoIP) services configured to provide one or more of the TRUs 102a, 102b, 102c, and 102d It may be any type of network, for example, the core network 106 / 107 / 109 provides call control, billing services, mobile location-based services, prepaid calling services, Internet connectivity, packet data network connectivity, Ethernet (registered trademark) It may provide high-level security features such as user authentication, etc. It may also perform security functions.

[0247] Although not shown in Figure 12A, RAN103 / 104 / 105 or RAN103 b / 104b / 105b or core network 106 / 107 / 109 is RAN10 3 / 104 / 105 or RAN103b / 104b / 105b same RAT or different It is understood that the RAN may communicate directly or indirectly with other RANs employing different RATs. For example, RAN 103 / 104 / 1 may utilize E-UTRA radio technology. In addition to being connected to RAN 05 or RAN 103b / 104b / 105b, Networks 106 / 107 / 109 also include other networks employing GSM or NR radio technology. The RAN may be in communication with the RAN (not shown).

[0248] The core network 106 / 107 / 109 also includes the WTRUs 102a, 102b, 10 2c, 102d, and 102e are connected to the PSTN 108, the Internet 110, or other networks. The PSTN 108 may also function as a gateway for accessing the network 112. is a circuit exchange that provides Plain Old Telephone Service (POTS). The Internet 110 may include a switched telephone network. Transmission Control Protocol (TCP) in the TCP suite ), User Datagram Protocol (UDP), Internet Use common communication protocols such as the Internet Protocol (IP), Includes a global system of interconnected computer networks and devices Network 112 may be owned or operated by another service provider. For example, the network 112 may include a wired or wireless communication network. Any type of packet data network (e.g., IEEE 802.3 Ethernet) network) or another core network connected to one or more RANs. This is RAN103 / 104 / 105 or RAN103b / 104b / 105 The same RAT as b or a different RAT may be employed.

[0249] WTRUs 102a, 102b, 102c, 102d, 10 2e, and some or all of 102f may include multi-mode capabilities, e.g., WTRUs 102a, 102b, 102c, 102d, 102e, and 102f are As disclosed herein, the method, system, and To implement the device, it is necessary to communicate with different wireless networks via different wireless links. For example, the WTRU 102g shown in FIG. The base station 114a may employ cellular-based wireless technology, and the IEEE 802.11b may employ cellular-based wireless technology. It may be configured to communicate with base station 114c, which may employ wireless technology.

[0250] Although not shown in FIG. 12A, the user equipment may have a wired connection to the gateway. It will be understood that the gateway is a residential gateway. The RG may be a central gateway (RG). 9. Many of the ideas contained herein are WTRU This may equally apply to UEs that connect to the network using a wired connection. For example, it will be understood that the wireless interfaces 115, 116, 117 and 118 The ideas that apply to 15c / 116c / 117c can be applied to wired connections as well. .

[0251] FIG. 12B illustrates a method for the NR-U LBT MAC procedure as disclosed herein. , systems, and devices may be implemented in an exemplary RAN 103 and core network As mentioned above, the RAN 103 is a system diagram of the air interface 115. to communicate with the WTRUs 102a, 102b, and 102c via the UTRA radio The RAN 103 may also be in communication with the core network 106. As shown in FIG. 12B, the RAN 103 includes Node Bs 140a, 140b, and 140c. 40c, each of which communicates with the WTRU via the air interface 115. 102a, 102b, and 102c, and Each of the Node Bs 140a, 140b, and 140c may be a particular The RAN 103 may also include an RNC 142a, an RNC 142b, and an RNC 142c. The RAN 103 may include any number of Node Bs and wireless networks. It is understood that the radio network controller (RNC) may also include It would be.

[0252] As shown in FIG. 12B, Node Bs 140a and 140b communicate with RNC 142a. Additionally, Node B 140c may be in communication with RNC 142b. 40a, 140b, and 140c communicate with their respective RNs via the Iub interface. RNCs 142a and 142b may communicate with Iur The RNCs 142a and 142b may communicate with each other via the RNC interface. It identifies each Node B 140a, 140b, and 140c to which it is connected. Furthermore, each of the RNCs 142a and 142b may be configured to control , outer loop power control, load control, admission control, packet scheduling, handover Other functionality such as server control, macro diversity, security features, and data encryption may be configured to perform or support

[0253] The core network 106 shown in FIG. 12B includes a media gateway (MG). MGW) 144, Mobile Switching Center (MSC) ) 146, Serving GPRS Support Node (SGS N) 148, or Gateway GPRS Support Node (GGPRS Support Node Each of the above elements may be part of the core network 106. Although illustrated as a single entity, any one of these elements may be a core network operator. It will be understood that the information contained in the Internet may be owned or operated by entities other than the Internet.

[0254] RNC 142a in RAN 103 communicates with the core network via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may and 102c, providing access to circuit-switched networks such as the PSTN 108 to Communications between TRUs 102a, 102b, and 102c and traditional landline communications devices may be facilitated.

[0255] RNC 142a in RAN 103 also communicates with the core network via the IuPS interface. The SGSN 148 may be connected to the GGSN 1 50. The SGSN 148 and the GGSN 150 may be connected to the WTRU 102a, 102b, and 102c to a packet-switched network such as the Internet 110. provides access to the WTRUs 102a, 102b, and 102c and the IP-enabled devices. The device may facilitate communication between the device and the network.

[0256] The core network 106 may also be owned or operated by other service providers. It may also be connected to other networks 112, which may include other wired or wireless networks. good.

[0257] FIG. 12C illustrates a method for the NR-U LBT MAC procedure as disclosed herein. , systems, and devices may be implemented in an exemplary RAN 104 and core network 1 RAN 104 is a system diagram of the air interface 116. to communicate with the WTRUs 102a, 102b, and 102c via the E-UTRA wireless The RAN 104 may also be in communication with a core network 107. stomach.

[0258] The RAN 104 may include eNodeBs 160a, 160b, and 160c. It will be appreciated that the RAN 104 may include any number of eNodeBs. Each of the base stations 160a, 160b, and 160c communicates with the other base stations 160a, 160b, and 160c via the air interface 116. and one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c. For example, the eNodeBs 160a, 160b, and 160c may include MI Therefore, the eNodeB 160a may implement multiple antennas. The antenna is used to transmit wireless signals to and from the WTRU 102a. The signal may be received.

[0259] Each of the eNodeBs 160a, 160b, and 160c serves a particular cell (not shown). ), radio resource management decisions, handover decisions, uplink or configured to handle user scheduling in the downlink, etc. As shown in FIG. 12C, eNodeBs 160a, 160b, and 160c may They may communicate with each other via two interfaces.

[0260] The core network 107 shown in FIG. 12C includes a mobility management gateway (Mobility Management Gateway). Management Gateway (MME) 162, Serving Gateway 164, and Packet Packet Data Network (PDN) Gateway 166 Each of the aforementioned elements is shown as part of the core network 107, which Any one of these elements may be owned by an entity other than the core network operator. It will be understood that the information may be owned or operated by the organization.

[0261] The MME 162 communicates with the eNodeB 160a in the RAN 104 via the S1 interface. , 160b, and 160c, and function as control nodes. For example, the MME 162 may Authentication of users, activation / deactivation of bearers, WTRUs 102a, 102b, and and 102c may play a role in selecting a particular serving gateway during initial connection. The MME 162 also communicates with the RAN 104 and other wireless technologies such as GSM or WCDMA. It provides a control plane function for switching between other RANs (not shown) that employ Good too.

[0262] The serving gateway 164 communicates with the e within the RAN 104 via the S1 interface. Node Bs 160a, 160b, and 160c may be connected to each of the Node Bs 160a, 160b, and 160c. The gateway 164 generally provides communication between the WTRUs 102a, 102b, and 102c. The Serving Gateway may route and forward user data packets. 164 also provides anchoring of the user plane during eNodeB handover; When downlink data is available at WTRUs 102a, 102b, and 102c Triggering paging, context of WTRUs 102a, 102b, and 102c It may also perform other functions, such as managing and storing the records.

[0263] The serving gateway 164 may also be connected to a PDN gateway 166. , which provides WTRUs 102a, 102b, and 102c with access to the Internet 110, etc. WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g, 102h, 102i, 102m ... It may facilitate communication between the O2c and IP-enabled devices.

[0264] The core network 107 may facilitate communication with other networks, for example: The core network 107 provides the WTRUs 102a, 102b, and 102c with a PSTN 108 to provide access to a circuit-switched network, such as the WTRUs 102a, 102 b, and 102c and conventional landline communications devices. For example, the core network 107 may be configured to provide an interface between the core network 107 and the PSTN 108. IP gateways (e.g., IP multimedia subsystems) that act as interfaces It may also include an IP Multimedia Subsystem (IMS) server, or Additionally, the core network 107 may communicate with the WTRUs 102a, 102b, and and 102c, other wired or It may provide access to a network 112, which may include a wireless network.

[0265] FIG. 12D illustrates a method for the NR-U LBT MAC procedure as disclosed herein. , systems, and devices may be implemented in an exemplary RAN 105 and core network RAN 105 communicates with WTR 109 via air interface 117. NR radio technology may be employed to communicate with U 102a and 102b. 05 may also communicate with the core network 109. Non-3GPP Interworking Function (Non-3GPP Interworking Function: N3IWF) 199 is an air interface 198 with the WTRU 102c. The N3IWF 199 may also communicate with the core network 109.

[0266] The RAN 105 may include gNodeBs 180a and 180b. It will be appreciated that the gNodeB 180a may include any number of gNodeBs. and 180b communicate with WTRU 102a and WTRU 102b, respectively, via air interface 117. The integrated access point may include one or more transceivers for communicating with the access point 102a and 102b. If a backhaul connection is used, the same air traffic between the WTRU and the gNode B must be used. An interface may be used, which connects to the core network via one or more gNBs. The g Node Bs 180a and 180b may be MIMO, MU- MIMO or digital beamforming techniques may be implemented. The WTRU 102a may transmit wireless signals to the WTRU 102a using, for example, multiple antennas. The RAN 105 may transmit and receive wireless signals from the WTRU 102a. It should be understood that other types of base stations, such as R It will be appreciated that the AN 105 may employ one or more types of base stations. For example, the RAN may employ eNodeBs and gNodeBs.

[0267] The N3IWF 199 may include a non-3GPP access point 180c. It will be appreciated that F199 may include any number of non-3GPP access points. The non-3GPP access point 180c communicates with the WLAN over the air interface 198. It may also include one or more transceivers for communicating with the TRU 102c. Access point 180c communicates over air interface 198 using 802.11. The WTRU 102c may communicate with the WTRU 102b via the WTRU 102c

[0268] Each of the gNodeBs 180a and 180b is associated with a particular cell (not shown). Radio resource management decisions, handover decisions, uplink or downlink It may also be configured to handle scheduling of users on the link, etc. As shown in 2D, g-node Bs 180a and 180b may be connected to the Xn interface, for example. They may communicate with each other via

[0269] The core network 109 shown in FIG. 12D is a 5G core network. k:5GC). The core network 109 may be a Thus, multiple communication services may be provided to interconnected customers. The network 109 consists of a number of entities that perform the functionality of the core network. As used herein, "core network entity" or "network function" refers to a The term "functionality" refers to any entity that performs one or more functions of the core network. Such a core network entity is the system illustrated in Figure 12G. A device or computer configured for wireless or network communication, such as a Computer-executable instructions stored in a system's memory and executed on its processor It is understood that the present invention may be implemented in the form of a logical entity (software) .

[0270] In the example of FIG. 12D, the 5G core network 109 provides access and mobility management functionality. Access and Mobility Management Function (AMF) 172, Session Management Function (Session Management Function: SMF) 174, User Plane Function (User P User Data Management Function (UPF) 176a and 176b, and User Data Management Function (UDP) 176b. Management Function (UDM) 197, Authentication Server Function (Authentication Server Function:AUSF)190, Network Exposure Function: NEF (Policy Control Function) 196, Policy Control Function (PCF) 184, Non 3GPP Interworking Function (N3IWF) 199, User Data Repository (User Each of the aforementioned elements may be integrated into the 5G Core Network. Although illustrated as part of Work 109, any one of these elements may be part of the core network. It is understood that the Furthermore, the 5G core network will consist of all of these elements. It may be composed of additional elements, and multiple instances of each of these elements may be used. It will also be understood that the network functions may be configured in a mutually exclusive manner. It indicates that the router is directly connected to the other router, but the diameter routing agent or message It should be understood that communication may be via a routing agent such as a message bus. is.

[0271] In the example of Figure 12D, connectivity between network functions is achieved through a set of interfaces or standards. Network functions are achieved through other network functions or services. A service that is invoked or called by It will be appreciated that a network may be modeled, described, or implemented as a set of nets. Network function service calls are made via direct connections between network functions, message buses, and This may be achieved through message exchange, calling software functions, etc.

[0272] The AMF 172 may be connected to the RAN 105 via an N2 interface and may control For example, the AMF 172 may perform functions such as registration management, connection management, reachability management, and AMF may also play the role of security management, access authentication, and access authorization. This is responsible for transferring the tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive the user plane data from the SMF via the N11 interface. The AMF 172 may receive tunnel configuration information for the N1 interface. Routes NAS packets to and from the WTRUs 102a, 102b, and 102c via The N1 interface is not shown in Figure 12D.

[0273] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly, the SMF connects to the PCF184 via the N7 interface, as well as to the PCF184 via the N4 interface. The SMF 174 may be connected to the UPFs 176a and 176b via a control interface. For example, the SMF 174 may perform session management, WTRU1, IP address assignment for 02a, 102b, and 102c, UPF176a and and managing and configuring traffic steering rules in UPF176b, and In addition, it may be responsible for generating downlink data notifications to the AMF 172.

[0274] UPF176a and UPF176b are WTRU102a, 102b, and 102 c, access to a packet data network (PDN) such as the Internet 110; to provide communication between the WTRUs 102a, 102b, and 102c and other devices. The UPF 176a and the UPF 176b may also facilitate the WTRU 102a, 102b, and 102c to provide access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or It may be any type of network that exchanges packets of data. a and UPF176b receive traffic from SMF174 via the N4 interface. UPF 176a and UPF 176b may receive steering rules from N6 By connecting a packet data network with the N9 interface or By connecting with each other and with other UPFs at the same interface, may provide access to a packet data network; In addition, UPF176 also manages packet routing and forwarding, policy rules, Enforcement, handling quality of service for user plane traffic, downlink packet It may also play a role in buffering data.

[0275] The AMF 172 is also connected to the N3IWF 199 via the N2 interface, for example. The N3IWF may be configured to handle wireless interfaces not defined by 3GPP, for example. Facilitates connectivity between the WTRU 102c and the 5G core network 170 via LTE technology. AMF interacts with N3I in the same or similar manner as it interacts with RAN105. May interact with WF199.

[0276] The PCF184 is connected to the SMF174 via the N7 interface and the N15 interface. It is connected to the AMF172 via the N5 interface and to the application N15 and N5 may be connected to an Application Function (AF) 188. The interface is not shown in Figure 12D. The PCF 184 is connected to the AMF 172 and Provides policy rules to control plane nodes such as SMF174 The PCF 184 may allow the AMF to enforce these rules. The policy can be distributed to the WTRUs 102a, 102b, and 102c through the The AMF 172 is configured to allow WTRUs 102a, 102b, and 102c to The policy may then be transmitted to the WTRUs 102a, 102b, and 102c. may be enforced or applied in c.

[0277] UDR178 also serves as a repository for authentication credentials and subscription information. UDRs allow network functions to add to and read from data in the repository. , may be connected to a network function so that it can be modified. For example, UDR1 78 may be connected to the PCF 184 via an N36 interface. 178 may connect to the NEF 196 via an N37 interface, and the UDR 178 may be connected to the UDM 197 via an N35 interface.

[0278] The UDM197 acts as an interface between the UDR178 and other network functions. The UDM 197 allows network functions to access the UDR 178. For example, the UDM197 may be connected to the AMF172 via the N8 interface. The UDM197 may be connected to the SMF174 via an N10 interface. Similarly, the UDM197 connects to the AUSF190 via the N13 interface. The UDR 178 and the UDM 197 may be tightly integrated.

[0279] The AUSF190 performs authentication-related operations and communicates with the UDM1 through the N13 interface. 78 and connects to AMF172 via the N12 interface.

[0280] The NEF196 will identify capabilities and services within the 5G Core Network109 as The disclosure is made to the Application Function (AF) 188. The disclosure is made on the N33 API interface. The NEF may be connected to the AF188 via the N33 interface. In addition, other networks will be able to share the capabilities and services of the 5G core network109. It may also be connected to the network function.

[0281] The application functions 188 correspond to the network functions of the 5G core network 109. The interaction between the application function 188 and the network function is This may be via a direct interface or may occur via the NEF 196. Application functions 188 may be considered part of the 5G core network 109. Often, or outside the 5G core network 109, mobile network operators It may also be deployed by companies that have business relationships with

[0282] Network slicing is a technology that allows mobile network operators to It can be used to support one or more "virtual" core networks behind an interface. This is a mechanism for "sliding" a core network into one or more virtual networks. "issuing" different services running across different RANs or a single RAN Network slicing allows operators to: Various market scenarios with diverse requirements for functionality, performance, and isolation Creating a customized network to provide the best solution for Rio It is possible.

[0283] 3GPP is adapting the 5G core network to support network slicing Network slicing is a key technology for network operators, as they are highly diverse and A diverse set of 5G use cases (e.g., Massive IoT) will place extreme demands on , Critical Communications, V2X, and Enhanced Mobile Broadband) It is a great tool that can be used to support network slicing. Otherwise, each use case will have its own unique set of performance, scalability, and availability requirements. If so, the network architecture can efficiently support a wider range of use cases. may not be flexible and scalable enough to accommodate new networks. The introduction of network services should be more efficient.

[0284] Referring again to FIG. 12D, in a network slicing scenario, the WTRU 102 a, 102b, or 102c connects to the AMF172 via the N1 interface. An AMF may be logically part of one or more slices. The connection or communication of TRU 102a, 102b, or 102c is controlled by one or more UPF1 76a and 176b, SMF 174, and other network functions. UPF176a and 176b, SMF174, and other network functions They may be part of the same slice or different slices. When they are part of a RICE, they share different computing resources, security, They may be separated from each other in the sense that they can use credentials etc. .

[0285] The core network 109 may facilitate communication with other networks, for example: The core network 109 is an interface between the 5G core network 109 and the PSTN 108. IP Multimedia Subsystem (IMS) servers that act as interfaces It may also contain or communicate with a gateway, e.g., a core network Call 109 is a short message service that allows communication via short message service. It may also include a Short Message Service (SMS) service center. For example, the 5G core network 109 may communicate with the WTRU 102a. , 102b, and 102c and the server or application function 188. Additionally, the core network 170 may facilitate the exchange of WT P data packets. RUs 102a, 102b, and 102c may have other services owned or operated by other service providers. access to network 112, which may include other wired or wireless networks operated by A service may be provided.

[0286] As described herein and shown in Figures 12A, 12C, 12D, or 12E Core network entities are required to comply with certain existing 3GPP specifications for those entities. Although identified by the given names, their entities and functionality may change in the future. They may be identified by other names and specific entities or functions may be subject to future 3GPP It is understood that this specification may be combined with future specifications published by 3GPP, including NR specifications. Therefore, the structure illustrated in FIG. 12A, FIG. 12B, FIG. 12C, FIG. 12D, or FIG. 12E may be The specific network entities and functionality illustrated and shown are for illustrative purposes only. The subject matter disclosed and claimed herein is provided herein whether presently defined or not. may be embodied or implemented in any similar communication system, whether now or hereafter defined. It is understood that

[0287] FIG. 12E illustrates a wireless LAN using the NR-U LBT MAC procedure implemented as described herein. 1 illustrates an exemplary communication system 111 in which the systems, methods, and apparatus may be used. The system 111 includes radio transmit / receive units (WTRUs) A, B, C, D, E, and F, a base station gNB 121, a V2X server 124, and a road side unit (RSU) 123a, and 123b. In fact, the concepts presented herein may be applied to any number of W May be applied to TRUs, base stations gNBs, V2X networks, or other network elements One or some or all of WTRUs A, B, C, D, E, and F may WTRUs A, B, and C may be outside the range of network coverage 131. form a V2X group, of which WTRU A is the group leader, and W TRUs B and C are group members.

[0288] WTRUs A, B, C, D, E, and F are located in the access network coverage area. When they are in the same location, they communicate with each other over the Uu interface 129 via the gNB 121. In the example of FIG. 12E, WTRUs B and F may be in the access network coverage area. WTRUs A, B, C, D, E, and F are shown in Figure 131. under the access network coverage 131 or Whether outside of the interface 131, the interface 125a, 125b, or 128 via any slide link interface (e.g. PC5 or NR PC5) For example, in the example of FIG. 12E, the access network coverage WRTU D, outside 131, communicates with WTRU F, which is within coverage of 131 .

[0289] WTRUs A, B, C, D, E, and F are connected to a vehicle-to-network (V2N) network. 3 or side link interface 125b, b. WTRUs A, B, C, D, E, and F may communicate with vehicle-to-infrastructure The V2X server 124 communicates with the V2I interface 127. WTRUs A, B, C, D, E, and F are connected to the vehicle-to-pedestrian (V2P) interface. The UE may communicate with another UE via interface 128.

[0290] FIG. 12F illustrates the WTRU of FIG. 12A, FIG. 12B, FIG. 12C, FIG. 12D, or FIG. 12E. 102, or as described herein, such as in FIG. 1 (e.g., UE 101), Wireless communication according to a system, method, and apparatus implementing a RU LBT MAC procedure 1 is a block diagram of an exemplary apparatus or device WTRU 102 that may be configured for operation. As shown in FIG. 12F, the example WTRU 102 includes a processor 118, a Transceiver 120, transmit / receive 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) The W may include a GPS chipset 136, and other peripherals 138. It is understood that TRU 102 may include any subcombination of the foregoing elements. Also, the base stations 114a and 114b, or the base stations 114a and 114b may represent a node, for example, but not limited to, a base station (BTS), a node Node B, Site Controller, Access Point (AP), Home Node B, Evolved Node B (eNodeB), Home evolved NodeB (HeNB), Home evolved NodeB Gateway The hops, next generation Node Bs (gNode Bs), and proxy nodes, etc., are particularly and may include some or all of the elements illustrated in the NR-U 1 is an exemplary implementation of the disclosed system and method for the LBT MAC procedure. Good too.

[0291] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital Digital Signal Processor (DSP), multiple microprocessors, One or more microprocessors, controllers, or microcontrollers associated with a DSP core controller, Application Specific Integrated Circuit (ASIC) ), Field Programmable Gate Array (FP GA circuits, other types of integrated circuits (ICs), state machines The processor 118 may be a processor for signal coding, data processing, power control, input / output power processing, or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120. The transceiver may be coupled to the transmit / receive element 122. FIG. Although the processor 11 and transceiver 120 are shown as separate components, 8 and transceiver 120 may be integrated together in an electronic package or chip. It will be understood that.

[0292] The transmit / receive element 122 of the UE communicates with the base station via the air interface 115 / 116 / 117. between stations (e.g., base station 114a in FIG. 12A) or air interface 115d / 116d / 117d to transmit or receive signals to or from another UE. For example, the transmit / receive element 122 may be configured to transmit or receive RF signals. The transmit / receive element 122 may be, for example, an IR, UV, or It may be an emitter / detector configured to transmit or receive visible light signals. The receiving element 122 may be configured to transmit and receive both RF and optical signals. The transmit / receive element 122 may be configured to transmit or receive any combination of wireless or wired signals. It will be understood that the present invention may be configured as follows.

[0293] Furthermore, although the transmit / receive element 122 is illustrated as a single element in FIG. 12F, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 10 2 may employ MIMO technology. Thus, the WTRU 102 two or more transmitting and receiving elements for transmitting and receiving radio signals via the base 115 / 116 / 117 122 (e.g., multiple antennas).

[0294] The transceiver 120 modulates and transmits / receives signals to be transmitted by the transmit / receive element 122. The receiver 122 may be configured to demodulate the signal received by the receiver 122. , the WTRU 102 may have multi-mode capabilities. 120 indicates that the WTRU 102 supports multiple RATs, for example, NR and IEEE 802.11 or communicates via NR and E-UTRA, or different RRHs, TRPs, RSUs, if or multiple beams to allow nodes to communicate with the same RAT over multiple beams. The transceiver may include:

[0295] The processor 118 of the WTRU 102 controls the speaker / microphone 124, the keypad 126, or display / touchpad / indicator 128 (e.g., LCD display) Liquid Crystal Display (LCD) display unit or organic light-emitting diode (OLED) Organic Light-Emitting Diode (OLED) display unit The processor 118 may also include a processor 118a, 118b, 118c, 118d, 118e, 118f ... Also, the speaker / microphone 124, keypad 126, or display / touch The processor 1 may output user data to the touchpad / indicator 128. 18 can be any type of memory, such as non-removable memory 130 or removable memory 132. The information may be accessed from and stored in the appropriate memory of the The hard memory 130 may be a random-access memory (RAM), a link Read-Only Memory (ROM), hard disk, or any other The removable memory 132 may include any type of memory storage device. Subscriber Identity Module (SIM) cards, memory sticks , a Secure Digital (SD) memory card, etc. The processor 118 may be hosted on a cloud or edge computing platform. Such as on a server or home computer (not shown) where the WTRU 102 is hosted. It may access information from and store data in memory that is not physically located in the processor. The processor 118 may be a processor for the LBT FC in some embodiments described herein. Depending on whether the setup was successful or unsuccessful, a display or indicator will appear. may be configured to control the lighting pattern, image, or color on the display 128; indicates the status of the NR-U LBT MAC procedure and related components in another way. The control lighting pattern on the display or indicator 128 may be configured to The patterns, images, or colors may be any of the illustrations (e.g., reflects the state of either the method flow or the component in Figures 1 to 10 The messages and procedures for the NR-U LBT MAC procedure are described herein. The messages and procedures are disclosed as follows: Microphone 124, keypad 126, or display / touchpad / indicator Others may request resources via the server 128 and be displayed on the display 128. Among them, interfaces for requesting, setting, or querying NR-U LBT MAC procedure related information It may be extended to provide a custom interface / API.

[0296] The processor 118 receives power from a power supply 134 and operates in conjunction with the other components within the WTRU 102. The power supply 134 may be configured to distribute or control power to the WTRU components. 102. For example, power supply 13 4 may include one or more dry batteries, solar cells, fuel cells, etc.

[0297] The processor 118 may also be coupled to a GPS chipset 136. The chipset 136 stores location information (e.g., longitude and latitude) in addition to information from the GPS chipset 136. Alternatively, or in addition, the WTRU 102 may communicate with a base station (e.g., base station 114a, 114b, 4b) via the air interface 115 / 116 / 117. based on the timing of signals received from two or more nearby base stations. The WTRU 102 may determine its location. The WTRU 102 may obtain location information by any suitable location-determination method. It will be appreciated that information may be obtained.

[0298] The processor 118 may also be coupled to other peripherals 138, Device 138 may include one or more devices that provide additional features, functionality, or wired or wireless connectivity. The peripheral device 13 may include the above software or hardware modules. 8 includes various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic components, amplifier, satellite transceiver, digital camera (for photos or videos), 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) radio unit, Digital music player, media player, video game player module, internet It may also include a web browser.

[0299] The WTRU102 is ideal for sensors, home appliances, smart watches, smart wear, and other applications. Wearable devices, medical or electronic health devices, robots, industrial equipment, drones , in other equipment or devices, such as vehicles, including automobiles, trucks, trains, or airplanes The WTRU 102 may include an interconnection interface that may constitute one of the peripherals 138. Such devices or equipment may communicate with one another via one or more interconnection interfaces, such as a may be connected to other components, modules, or systems of the device.

[0300] FIG. 12G is a block diagram of an exemplary computing system 90, which includes: One or more of the communication networks shown in Figures 12A, 12C, 12D, and 12E The apparatus and system shown in Figures 1 through 10 and described and claimed herein NR-U LBT MAC procedures such as systems and methods are 5. Core network 106 / 107 / 109, PSTN 108, Internet 110 , other networks 112, or specific nodes in network services 113 The computing system 90 may be embodied as a computer, a network, a network device, a network interface, a network interface card, a network function, or a network entity. , consisting of a computer or server and controlled primarily by computer-readable instructions The computer readable instructions may be in the form of software or other such No matter where the software is stored or how it is accessed Such computer-readable instructions may be executed within the processor 91 to The processor 91 may be a general-purpose processor, a dedicated processor, or the like. processors, conventional processors, digital signal processors (DSPs), multiple microprocessors one or more microprocessors, controllers, microphones, controllers, application specific integrated circuits (ASICs), field programmable gates FPGA circuits, other types of integrated circuits (ICs), state machines, etc. The processor 91 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the WTRU 90 to operate in a telecommunications network. The coprocessor 81 may execute optional functions different from the main processor 91. A processor that may perform additional functions or assist processor 91. 91 or coprocessor 81 may receive or respond to an LBT failure, or other NR-U LBT Receives and generates data relating to the methods and apparatus disclosed herein for MAC procedures , and may be processed.

[0301] In operation, processor 91 fetches, decodes, and executes instructions to perform computing tasks. with other resources via the system bus 80, which is the main data transfer path for the operating system. Such a system bus transfers information between the computers in the computing system 90. The system bus 80 connects the components and defines the medium for data exchange. In other words, there is a data line for sending data and an address line for sending addresses. It also includes control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is a Peripheral Component Interconnect (Pe PCI bus.

[0302] The memory coupled to the system bus 80 is a random access memory (RAM). RAM 82 and ROM 93 Such memories include circuits that can store and retrieve information. RAM 82 generally contains stored data that cannot be easily altered. , which may be read by the processor 91 or other hardware device, or Access to the RAM 82 or ROM 93 is controlled by the memory controller 92. The memory controller 92 may be controlled by a virtual address when an instruction is executed. The memory controller may provide an address translation function that translates addresses into physical addresses. 92 also separates processes within a system, separating system processes from user processes. Therefore, a program running in the first mode may be protected from RAM can only access memory that is mapped by the process's virtual address space. and the virtual addresses of other processes unless memory sharing between processes is configured. It is not possible to access memory within the space.

[0303] Additionally, the computing system 90 may transmit instructions from the processor 91 to the printer 9 4, to communicate with peripherals such as keyboard 84, mouse 95, and disk drive 85. The peripheral controller 83 may be responsible for:

[0304] The display 86 controlled by the display controller 96 is It is used to display the visual output generated by the operating system 90. Such visual output includes text, graphics, animated graphics, and The visual output may include video. The display 86 may be provided in the form of a CRT. based video displays, LCD based flat panel displays, gas plasma It may be implemented as a computer-based flat panel display or a touch panel. The display controller 96 generates the video signal that is sent to the display 86. Contains the electronic components necessary for

[0305] Furthermore, the computing system 90 is D, or RAN 103 / 104 / 105, core network 106 / 1 in Figure 12E. 07 / 109, PSTN 108, Internet 110, WTRU 102, or other The computer may be connected to an external communication network or device, such as a network 112. 90, and the computing system 90 is used to connect them may be able to communicate with other nodes or functional entities of the network, e.g. It may also include communications circuitry such as a wireless or wired network adapter 97. may be used alone or in combination with processor 91 to implement the specific devices described herein. may be used to perform the sending and receiving steps of a device, node, or functional entity. stomach.

[0306] Any or all of the devices, systems, methods, and processes described herein The computer-executable instructions (e.g., programs) stored on a computer-readable storage medium The instructions may be embodied in the form of program code, which may be transmitted to the processor 118 or 91. When executed by a processor such as It is understood that the present invention relates to performing or causing to be performed, methods, and processes. Any steps, actions, or functions described in this document may be performed over a wireless or wired network. on a processor of a device or computing system configured for network communication Such may be implemented in the form of computer-executable instructions. A data-readable storage medium is any non-transitory (e.g., tangible or physical) device for storing information. Volatile and non-volatile, removable and removable implemented in any suitable (or similar) method or technology Such computer-readable storage media include non-transitory media, but do not include signals. The computer readable storage medium may include RAM, ROM, EEPROM, flash memory or Other memory technologies, CD-ROM, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk hard disk storage or other magnetic storage device, or to store desired information other tangible or physical objects that can be used in and accessed by a computing system This includes, but is not limited to, physical media.

[0307] A preferred method, system, or In describing the apparatus as illustrated in the figures, specific terminology has been employed for the sake of clarity. However, it is not intended that claimed subject matter be limited to the particular terms so selected. Although not illustrated, each specific element is intended to be illustrative and not restrictive, and all elements operate in a similar manner to accomplish a similar purpose. It should be understood that the present invention includes technical equivalents of the above.

[0308] The various techniques described herein may be implemented in hardware, firmware, software, or other configurations. or any combination thereof, as appropriate. The hardware, firmware, and software are used to manage the various nodes of a communications network. The device may reside on a device located in a computer system that performs the methods described herein. When used in the present invention, , "equipment", "network equipment", "node", "device", "network node" " and " may be used interchangeably. Additionally, the use of the word "or" is not intended to limit the scope of the present specification. Unless otherwise specified in the document, the term is used generically and inclusively.

[0309] This written specification uses examples to disclose the invention, including the best mode. and to create and use any device or system, and to The invention is patentable and should not be construed as limiting the scope of the invention. The scope of the invention is defined by the claims and does not include other embodiments (e.g., For example, skipping steps, adding steps, or adding steps between the exemplary methods disclosed herein. Such other implementations may include the steps of: Examples may be used where the structural elements do not differ from the literal language of the claims, or or equivalent structural elements that differ substantially from the literal language of the claims, It is intended to be within the scope of the claims.

[0310] This written specification uses examples to disclose the subject matter, including the best mode. and to make and use any device or system, and any incorporated method The invention is patentable and is not intended to be a substitute for the invention described above. The scope of the present invention is defined by the claims, and does not include, for example, other embodiments ( For example, steps may be skipped between exemplary methods disclosed herein, particularly those shown in FIGS. 2-10. (including skipping, combining steps, or adding steps) Such other embodiments are within the scope of the appended claims without departing from the literal language of the claims. or have structural elements that are substantially different from the literal language of the claims. If the invention includes structural elements such as the above, it is intended to be included within the scope of the claims.

[0311] The methods, systems, and devices described herein may, among other things, be used in conjunction with the means NR- U LBT MAC procedure may be provided. LBT failure of the SR procedure may result in 1) an alternative BW 2) initiating an RA procedure; or 3) maintaining an SR pending state. LBT failure in the DRX procedure may result in: 1) the expiration of the on-duration or inactivity timer Extending,2) the on-duration or inactivity timer of,MCOT,,CWS,, or This could lead to either CCA alignment or 3) short-cycle application. A procedure LBT failure results in: 1) generating or transmitting a statistical report; or 2) Setting the prohibit timer. 1) extending the BWP inactivity timer, or 2) switching to an alternate BWP. This paragraph and the next paragraph (or related paragraphs in this specification) All combinations of steps (including removing or adding steps) are contemplated.

[0312] The methods, systems, and apparatus, as described herein, include, among other things, means N The present invention provides a method, system, and computer-readable storage for a RU LBT MAC procedure. The medium or device may, among other things, perform random access procedures, SCell activation / deactivation Activation procedure, discontinuous reception procedure, scheduling request procedure, buffer status reporting procedure logical channel prioritization procedures, coordination of UE and NB MAC procedures, power head routing The present invention has a means for determining LBT failure for the system reporting procedure or the bandwidth portion operation procedure. A method, system, computer-readable storage medium, or apparatus includes a preamble transmission counter. is greater than 1 and a notification to pause the power ramping counter has been received from lower layers. The method for determining whether the selected SSB has not changed and whether an LBT failure has not been detected Based on the step and the decision step, the preamble power ramping counter is incremented by one. The method includes providing an instruction to increment the number of bits. The storage medium or device may be configured to obtain an indication of the LBT status associated with the user equipment (UE). (e.g., received from a remote device or using a local sensor) Detecting the LBT Report MAC Control Element (LBTR MAC CE) Listen-before-talk (LBT) and media access control (MACC) AC), and the LBTR MAC CE has a means for operation associated with the LBT state The method, system, computer-readable storage medium, or apparatus may include an indication of the LB The LBT timing information is provided to the MAC layer. including the duration of channel assessment, maximum channel occupancy time, or contention window The method, system, computer-readable storage medium, or apparatus may be configured to: Detecting a first threshold of LBT failure or a second threshold of LBT success associated with and adjusting the DRX setting based on detecting the first threshold or the second threshold. associated with Listen Before Talk (LBT) and Discontinuous Reception (DRX) The DRX setting can be set to on duration or inactive time. The method, system, computer-readable storage medium, or apparatus of the present invention may include The base station has a means for providing information to the UE, and the information is associated with the base station or the UE. The UE may include downlink information about the access channel. The information about the uplink or downlink may be automatically detected. In one embodiment, the UE may perform different MAC procedures depending on the uplink information. The LBT failure notification and downlink information are used to decide whether or not to report an LBT failure, or which procedure to follow. The method may determine whether to report whether the affected device is affected. The storage medium or device acquires downlink information detected by the base station and The link information is associated with the base station's channel access and is used for downlink listening. The uplink information may include an indication of autotalk failure, and the uplink information may include an indication of autotalk failure. The uplink information is associated with the channel access of the device and may include an indication of a downlink listen-before-talk failure, and an indication of an uplink listen-before-talk failure. Listen before talk failure indication or Downlink Listen before talk failure indication and performing a media access control operation based on the uplink listen. Listen-before-talk failure (or success), or downlink listen-before-talk Failure (or success) is determined by the scheduling request procedure, the buffer status reporting procedure, and the logic physical channel prioritization procedure, discontinuous reception procedure, SCell activation or deactivation Activation procedure, power headroom reporting procedure, random access procedure, listen-before procedure This paragraph and All combinations (steps) of the following paragraphs (or related paragraphs herein) (including the deletion or addition of

[0313] The method, system, computer-readable storage medium, or apparatus includes a method for managing a MAC procedure. The method, system, computer-readable storage medium, or apparatus includes a downlink The downlink information includes a means for acquiring channel access information from a base station (to the device). and a means for obtaining uplink information (e.g., user equipment), The uplink information is associated with channel access (e.g., to a base station) by the device. , and performs media access control operations based on uplink or downlink information. The downlink information may be detected by the base station. The uplink information may be The channel access information may be detected by the device. The execution of the media access control operation may involve the non-access of portions of the bandwidth. The uplink or downlink information may include extending an active timer. , includes uplink or downlink listen-before-talk failure information. When DL LBT failure information is received, BWP may be switched (BWP operation MA C procedure, the switchover is to a pre-configured alternative BWP. The execution of a media access control operation extends the random access response window. and the uplink or downlink information may include Contains downlink listen-before-talk failure information. The line indicates that the preamble transmission counter should not be incremented or that the contention resolution timer should be The uplink or downlink information may include extending or downlink listen-before-talk failure information. Execution may include maintaining or decreasing the power ramping, The uplink or downlink information is sent to the uplink or downlink listen-before The disclosed subject matter avoids the termination of the RA procedure due to an LBT failure. Furthermore, exceeding the preamble transmission LBT failure threshold indicates an RA problem to higher layers. , the RA procedure may be considered unsuccessful. Based on determining whether there is a talk-before-talk failure or success, the physical applica- This may include determining that the link control channel resources are valid, which may include the SR procedure. The order may be associated with reaching the LBT failure threshold and releasing the PUCCH resource. CCA, MCOT, or CWS information may be provided along with LBT success information. Also, LBT success that includes this CCA, MCOT, or CWS information is not considered a failure. This can be equivalent to an LBT failure indication, since it means that there was no LBT. In DRX, the LBT failure can be judged by the LBT success indication. This may be covered by applying a workout cycle or extending active time. The number of times an LBT failure extends the active time when restarting the activity timer. In addition, the DRX setting is adjusted when the LBT fails. It may be associated with the duration, inactivity, or DRX cycle timers. For LBTR, when the LBT fails or succeeds, the success or failure of the LBT is known. If the threshold is exceeded for a period of time, a report to the base station is triggered and the report is sent. After that, a prohibition timer is set to limit the frequency of reports, and reports may include CCA, MCOT, or This may include timing information such as the LBT reaching a known threshold. An SR failure will trigger an RA procedure (e.g., an LBT failure will cause the SR transmission counter to (This is achieved by limiting the number of times the LBT is not incremented), and SR is prohibited when the LBT fails. The SR hold may be maintained if the stop timer is not set or if the LBT fails. The execution of the access control action is based on the listen-before-talk failure indication of the scheduling request transmission. Based on this, determining whether a scheduling request has failed or initiating a random access procedure. The execution of the medium access control operation may include initiating a scheduling request. Determine scheduling request failure based on outgoing listen-before-talk failure indication This may include switching between different bandwidth portions or switching between different media access control. The execution of the action may involve extending a MAC procedure timer or counter in the device, The impact on performance when achieved by uplink or downlink channel access It affects the performance of the device and allows it to perform the same functions as licensed operation, or the device This paragraph and the next paragraph ( or the relevant paragraphs of this specification) (including

[0314] The method, system, computer-readable storage medium, or apparatus includes a method for managing a MAC procedure. The method, system, computer-readable storage medium, or apparatus includes a step of receiving data from a base station. means for obtaining downlink information, the downlink information being related to channel access of the device; associated with the device and obtains uplink information. The uplink information is detected by the device. , and performs media access control operations based on uplink or downlink information. The execution of the media access control operation includes means for deactivating portions of the bandwidth. The uplink or downlink information may include extending a timer. It may also include link or downlink listen-before-talk failure information. Performing the access control action may include extending the random access response window. Often, the uplink or downlink information is The execution of the media access control operation may include the following: Incrementing the amble transmission counter or extending the contention resolution timer The uplink or downlink information may include The information may include listen-before-talk failure information for the link. The row can maintain or decrease the power ramping (e.g., not increase it). The uplink or downlink information may include It may also include downlink listen-before-talk failure information. The execution of the operation is based on the listen-before-talk failure or failure success (e.g., threshold success or failure). The physical uplink control is based on determining whether or not there is a The method may include determining that the PUCCH resource is available. Performing access control operations may include coordinating discontinuous reception operations, such as uplink or or downlink information is signaled from the base station in discontinuous reception cycles, Channel evaluation period, maximum channel occupancy time, or downlink listen-before-talk success The performing of the media access control operation may include a success indication. adjusting the active time to be consistent with the maximum channel occupancy time period; and discontinuous reception during the contention window size period or clear channel evaluation period. The alignment with the maximum channel occupancy time period may include applying This may include adjusting a login timer or adjusting an inactivity timer. Performing media access control operations is dependent on the influence of uplink or downlink information. The media access control may include reporting media access control actions that are subject to the media access control. The execution of control actions is performed by media accesses affected by uplink or downlink information. The uplink or downlink information may include reporting access control operations. , may include uplink or downlink listen-before-talk failure information. Execution of the media access control operations is performed by determining whether one or more of the media access control operations are performed by the access control unit. This includes reporting how the system is affected by uplink or downlink information. The execution of the media access control operation may include one of the media access control operations. Reports how one or more are affected by uplink or downlink information and the uplink or downlink information may include It may also include downlink listen-before-talk failure information. In general, LBT failure The uplink or downlink information, such as the number of times the signal is received, or the success of the signal, is disclosed herein, among other things. The device may be a user equipment. All combinations of the paragraphs (or related paragraphs of this specification) (including deletion of steps) or additions) is intended.

Claims

1. 1. A wireless transmit / receive unit (WTRU) comprising a processor and a memory, The processor and the memory determining that one or more Listen Before Talk (LBT) failures have occurred; Attempting to transmit a random access preamble based on the determination that the one or more LBT failures have occurred; Determine that there is an LBT failure in the transmission of the random access preamble, where, based on the determination that there is an LBT failure in the transmission of the random access preamble, a preamble transmission counter and a preamble power ramping counter are not incremented; starting or restarting a timer based on a determination that there was an LBT failure in the transmission of the random access preamble; It is determined that the LBT failure counter has reached the set failure display number, switching from a first Bandwidth Part (BWP) to a second BWP based on a determination that the LBT failure counter has reached a configured number of failures; configured to send an LBT report Medium Access Control (MAC) control element (CE) indicating LBT failure information to a base station; WTRU.

2. A WTRU as described in claim 1, wherein the timer is associated with a sliding time window, and the sliding time window corresponds to a period extended by detection of an LBT failure.

3. The WTRU of claim 1 , wherein the LBT report MAC CE is transmitted to the base station using available uplink shared channel (UL-SCH) resources.

4. The WTRU of claim 1 , wherein the processor and memory are further configured to reset the LBT failure counter to zero.

5. The WTRU of claim 1, wherein the indication of failure is associated with at least one uplink failure and at least one downlink failure.

6. The WTRU of claim 1 , wherein the determination that one or more LBT failures have occurred is based on a physical layer indication.

7. The WTRU of claim 1 , wherein the determination that there has been a failure in transmitting the random access preamble is based on a physical layer indication.

8. 1. A method performed by a wireless transmit / receive unit (WTRU), comprising: determining that one or more Listen Before Talk (LBT) failures have occurred; attempting to transmit a random access preamble based on the determination that the one or more LBT failures have occurred; and Determining that there is an LBT failure in the transmission of the random access preamble, and based on the determination that there is an LBT failure in the transmission of the random access preamble, a preamble transmission counter and a preamble power ramping counter are not incremented; starting or restarting a timer based on a determination that there was an LBT failure in transmitting the random access preamble; determining that the LBT failure counter has reached a set number of failure indications; switching from a first Bandwidth Part (BWP) to a second BWP based on a determination that the LBT failure counter has reached a configured number of failures; Sending an LBT report Medium Access Control (MAC) control element (CE) indicating LBT failure information to a base station; and A method comprising:

9. The method described in claim 8, wherein the timer is associated with a sliding time window, and the sliding time window corresponds to a period extended by the detection of an LBT failure.

10. The method of claim 8, wherein the LBT report MAC CE is transmitted to the base station using available uplink shared channel (UL-SCH) resources.

11. The method of claim 8 , further comprising resetting the LBT failure counter to zero.

12. The method of claim 8, wherein the indication of failure is associated with at least one uplink failure and at least one downlink failure.

13. The method of claim 8 , wherein the determination that one or more LBT failures have occurred is based on a physical layer indication.

14. The method of claim 8 , wherein the determination that there has been a failure in transmitting the random access preamble is based on a physical layer indication.