Radio Access Network (RAN)-centric data collection for New Radio (NR)-Unlicensed (U)

Abstract

The present disclosure relates to systems, methods, and apparatus for wireless communications, including computer programs encoded on computer storage media. In one aspect of the disclosure, a method for wireless communications includes determining, by a user equipment (UE), listen-before-talk (LBT) information associated with New Radio-Unlicensed (NR-U) operation of the UE. The method also includes sending, by the UE, a report including the LBT information. Other aspects and features are also claimed and described.

Description

Technical Field

[0001] Generally speaking, aspects of the present disclosure relate to wireless communication systems, and more particularly, but not limited to, data collection for New Radio (NR)-Unlicensed (U). Background Art

[0002] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks, which are typically multiple-access networks, support communications for multiple users by sharing the available network resources.

[0003] A wireless communication network may include a number of base stations or Node Bs capable of supporting communications for a number of user equipments (UEs). UEs may communicate with base stations via downlinks and uplinks. A downlink (or forward link) refers to the communication link from a base station to a UE, and an uplink (or reverse link) refers to the communication link from a UE to a base station.

[0004] The base station may send data and control information to the UE on the downlink, and / or may receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmissions from neighboring base stations or from other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from uplink transmissions of other UEs communicating with the neighboring base stations or from other wireless RF transmitters. Such interference may degrade performance on both the downlink and uplink.

[0005] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks increases with more UEs accessing long-range wireless communication networks and more short-range wireless systems being deployed in communities. Research and development continue to drive the development of wireless technologies, not only to meet the growing demand for mobile broadband access, but also to improve and enhance the user experience of mobile communications. For example, research and development has helped advance New Radio (NR) technology, which utilizes beam management, bandwidth parts (BWP), RRC_INACTIVE, multi-radio access technology (RAT) dual connectivity (MR-DC), and dual connectivity (DC) / carrier aggregation (CA). However, merging NR technology with traditional technologies presents various challenges and obstacles. For example, there are challenges in incorporating NR technology into devices and improving device performance related to NR technology. As specific, non-limiting examples, incorporating NR technology into devices has presented issues with battery life, throughput, latency, and reliability. Summary of the Invention

[0006] The following is a summary of some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive review of all anticipated features of the present disclosure, nor is it intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to provide some concepts of one or more aspects of the present disclosure in summary form as a prelude to the more detailed description that will be given later.

[0007] In one aspect of the present disclosure, a method for wireless communication includes determining, by a user equipment (UE), listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of the UE. The method also includes sending, by the UE, a report including the LBT information.

[0008] In some aspects, the report comprises a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report.

[0009] In some aspects, the LBT information includes LBT failure information.

[0010] In an additional aspect of the present disclosure, an apparatus configured for wireless communication includes means for determining, by a user equipment (UE), listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of the UE. The apparatus also includes means for transmitting, by the UE, a report including the LBT information.

[0011] In an additional aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon. The program code includes code for determining listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of a UE and initiating transmission of a report including the LBT information.

[0012] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to determine listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of a UE and initiate transmission of a report including the LBT information.

[0013] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes an interface (e.g., a transmitter, a receiver, etc.) configured for wireless communication; and a processor system coupled to the interface. The processor system is configured to determine listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of a UE; and initiate transmission of a report including the LBT information.

[0014] In an additional aspect of the present disclosure, a method for wireless communication includes determining, by a user equipment (UE), a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE. The method also includes transmitting, by the UE, a report including the RSSI and the channel occupancy information.

[0015] In some aspects, the report comprises a logged minimization of drive tests (MDT) report or an ad hoc minimization of drive tests (MDT) report.

[0016] In some aspects, the method further includes receiving, by the UE from the network entity, a configuration message for logging RSSI and channel occupancy information using logged Minimization of Drive Test (MDT) information.

[0017] In some aspects, the method further includes receiving, by the UE from the network entity, a configuration message for configuring immediate MDT measurements for RSSI and channel occupancy.

[0018] In an additional aspect of the present disclosure, an apparatus for wireless communication includes means for determining, by a user equipment (UE), a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE. The apparatus also includes means for transmitting, by the UE, a report including the RSSI and the channel occupancy information.

[0019] In an additional aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon. The program code includes code for determining a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of a UE; and initiating transmission of a report including the RSSI and channel occupancy information.

[0020] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the processor. The processor is configured to determine a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of a UE and initiate transmission of a report including the RSSI and channel occupancy information.

[0021] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes an interface (e.g., a transmitter, a receiver, etc.) configured for wireless communication; and a processor system coupled to the interface. The processor system is configured to determine a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of a UE; and to initiate transmission of a report including the RSSI and channel occupancy information.

[0022] In an additional aspect of the present disclosure, a method for wireless communication includes: sending, by a network entity, a configuration message to a user equipment (UE). The method also includes: receiving, by the network entity, a report from the UE, the report including a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE.

[0023] In some aspects, the report comprises a logged minimization of drive tests (MDT) report or an ad hoc minimization of drive tests (MDT) report.

[0024] In some aspects, the configuration message indicates that RSSI and channel occupancy information is recorded using logged minimization of drive tests (MDT) information, or configures immediate MDT measurements for RSSI and channel occupancy.

[0025] In some aspects, the method further comprises receiving an additional report, such as one comprising listen-before-talk (LBT) information associated with NR-U operation of the UE.

[0026] In some aspects, the additional reports include radio link failure (RLF) reports, random access channel (RACH) reports, or connection establishment failure (CEF) reports.

[0027] In an additional aspect of the present disclosure, an apparatus configured for wireless communication includes means for sending, by a network entity, a configuration message to a user equipment (UE). The apparatus also includes means for receiving, by the network entity, a report from the UE, the report including a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE.

[0028] In an additional aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon. The program code includes code for initiating transmission of a configuration message to a user equipment (UE); and receiving a report from the UE, the report including a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE.

[0029] In an additional aspect of the present disclosure, an apparatus configured for wireless communication includes at least one processor and a memory coupled to the processor. The processor is configured to initiate transmission of a configuration message to a user equipment (UE) and receive a report from the UE, the report including a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE.

[0030] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes an interface (e.g., a transmitter, a receiver, etc.) configured for wireless communication; and a processor system coupled to the interface. The processor system is configured to initiate transmission of a configuration message to a user equipment (UE); and receive a report from the UE, the report including a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE.

[0031] For those of ordinary skill in the art, other aspects, features, and implementations will become apparent when reviewing the following description of specific examples in conjunction with the accompanying drawings. Although features may be discussed below with respect to certain aspects and the accompanying drawings, all implementations may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used according to each example. In a similar manner, although exemplary implementations may be discussed below as device, system, or method implementations, exemplary implementations may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type may be distinguished by following the reference numeral with a dash and a second numeral, the second numeral being used to distinguish among similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, without regard to the second reference numeral.

[0033] Figure 1 is a block diagram illustrating details of a wireless communication system according to some aspects.

[0034] Figure 2 is a block diagram conceptually illustrating a design of a base station and a user equipment (UE) configured in accordance with some aspects.

[0035] Figure 3is a block diagram of an illustrative implementation of a system configured to provide data collection for user equipment (UE) that may be configured for New Radio - Unlicensed (NR-U), in accordance with some aspects.

[0036] Figure 4 is a block diagram of another illustrative implementation of a system configured to provide data collection for UEs that may be configured for NR-U in accordance with some aspects.

[0037] Figure 5 is a flow diagram illustrating example blocks executed by a UE according to some aspects.

[0038] Figure 6 is a flow diagram illustrating example blocks executed by a UE according to some aspects.

[0039] Figure 7 is a flow diagram illustrating example blocks performed by a network entity according to some aspects.

[0040] Figure 8 is a block diagram conceptually illustrating a design of a UE configured in accordance with some aspects.

[0041] Figure 9 is a block diagram conceptually illustrating a design of network entities configured in accordance with some aspects.

[0042] The appendices provide further details on various aspects of the disclosure, and the subject matter therein forms a part of the specification of this application. DETAILED DESCRIPTION

[0043] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Specifically, the detailed description includes specific details for the purpose of providing a thorough understanding of the innovative subject matter. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0044] The present disclosure provides systems, apparatus, methods, and computer-readable media for radio access network (RAN)-centric data collection for UEs that can be configured for NR-U operation. Data collection can be used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, and new radio (NR) functions and / or features (such as beam management, bandwidth part (BWP), RRC_INACTIVE, multi-radio access technology (RAT) dual connectivity (MR-DC), and dual connectivity (DC) / carrier aggregation (CA)). Data collection and operational improvements can also result in reduced operator capital expenditure (CAPEX) and operating expenditure (OPEX), for example, by more accurate base station deployment and operation with less human resource intervention. For example, the present disclosure describes the collection, storage, reporting, or a combination thereof of NR-U specific data collection. For example, the present disclosure describes that NR-U specific data collection can be used for or corresponds to a radio link failure (RLF) report for listen-before-talk (LBT) failure, a random access channel (RACH) report with LBT failure information, a connection establishment failure (CEF) report for supporting RACH failure with an LBT failure indication, or a combination thereof. As another example, the present disclosure describes that NR-U specific data collection can be used for or corresponds to a logged MDT for received signal strength indicator (RSSI) and channel occupancy reporting. In addition, the present disclosure also describes that NR-U specific data collection can be used for or corresponds to an immediate MDT for RSSI and channel occupancy reporting.

[0045] In some implementations, the UE may be configured to provide an RLF report for LBT failure. In NR-U, persistent LBT failure may lead to RLF, and at least for uplink (UL) transmissions, persistent failure may currently ultimately lead to RLF. In order to support mobility robustness optimization (MRO) for NR-U, user equipment (UE) RLF reporting for NR-U may be supported in NR. The RLF report for NR-U may include one or more parts of the RLF report for NR. In addition or alternatively, the RLF report for NR-U may include LBT information, such as LBT failure related information (e.g., LBT failure information). The LBT information may include the RLF cause for NR-U (e.g., missing RLM-RS, persistent LBT failure, etc.), the RLF type (e.g., downlink (DL) or UL LBT failure), the cell identity - Pcell / PSCell / Scell ​​in which the LBT failure was detected, the UL transmission type (e.g., SR, RACH, physical uplink shared channel (PUSCH)), the number of "N" BWPs with UL LBT failure, the BWP ID / frequency for each BWP, the interference type (e.g., wifi), the channel access scheme used for NR-based access for unlicensed spectrum, or a combination thereof. The channel access scheme may include or indicate Category 1: immediate transmission after a short switching gap; Category 2: LBT without random backoff; Category 3: LBT with random backoff using a fixed-size contention window; or Category 4: LBT with random backoff using a variable-size contention window.

[0046] In some implementations, the UE may be configured to provide a RACH report with LBT information (e.g., LBT failure information). In NR-U for a RACH procedure, if LBT fails for a Msg1 transmission opportunity, the medium access control (MAC) may fall back to the resource selection step. In some implementations, the network may enable automatic RACH parameter setting based on RACH reports received from the UE and through PRACH parameter exchange between gNBs. The RACH report (for NR-U) may include one or more parts of the NR RACH report. In addition or alternatively, the RACH report may include LBT information, such as LBT failure information. The LBT information may include or indicate the number of LBT failure detections before each RACH attempt, an indication of resource selection due to LBT failure, or a combination thereof. RACH reports for NR-U may be collected and stored by the UE and reported to NR, and vice versa. In some implementations, a RACH report (for NR-U) may include a cell ID / tracking area identity (TAI) for each of one or more RACH report entries (to enable access node RACH report retrieval and distribution), an identifier for identifying a RACH report for NR-U and a RACH report for NR in each of one or more entries of the RACH report, an indicator of a channel access scheme for NR-based access for unlicensed spectrum, or a combination thereof. The channel access scheme may include or indicate Category 1: immediate transmission after a short switching gap; Category 2: LBT without random backoff; Category 3: LBT with random backoff utilizing a fixed-size contention window; or Category 4: LBT with random backoff utilizing a variable-size contention window.

[0047] In some implementations, the UE may be configured to provide a connection establishment failure (CEF) report with LBT information (such as an LBT failure indication). The CEF report for NR-U may include one or more parts of an NR accessibility report (e.g., an LTE accessibility report). The UE may log failed RRC connection establishment and RRC recovery failures for NR. The CEF report may include or indicate the failed cell id, radio measurement results, and neighboring cells (including the SSB index of the downlink beam of both the serving cell and the neighbor cell, which is tagged with location information (if available)). In addition, in some implementations, the CEF report may include RACH failure information, such as the SSB index, the number of preambles sent on each attempted SSB, and a flag about detected contention. The flag may be per cell, RACH attempt, or SSB. In addition or alternatively, the RACH failure information may include LBT information, such as an LBT failure indication. The failure information may include a RACH failure cause value for LBT failure, an indication of UL LBT failure or DL ​​LBT failure, the number of persistent LBT failures, the interference type (e.g., wifi), the BWP ID / frequency / cell identity where the LBT failure was detected, an indication of the channel access scheme used for NR-based access to unlicensed spectrum, or a combination thereof. The channel access scheme may include or indicate Category 1: immediate transmission after a short switching gap; Category 2: LBT without random backoff; Category 3: LBT with random backoff using a fixed-size contention window; or Category 4: LBT with random backoff using a variable-size contention window.

[0048] In some implementations, the UE may be configured for log-type MDT for RSSI and channel occupancy reporting. For example, NR-U may support RSSI and channel occupancy configuration and reporting, such as measurement and periodic reporting within an interval (at least for CO). In some implementations, log-type MDT may support logging of RSSI and channel occupancy, such as when in inactive mode (such as RRC_IDLE / RRC_INACTIVE mode). In some implementations, the network may send a log-type measurement configuration (e.g., a configuration) to the UE to log RSSI and channel occupancy in RRC idle or RRC_INACTIVE mode. The configuration may include or indicate an NR-U frequency list / cell ID list for RSSI and channel occupancy logging, a logging area for NR-U, a logging interval for RSSI and channel occupancy measurements, or a combination thereof. The UE may report the contents of the log-type MDT for NR-U RSSI and channel occupancy reporting. The report may include or indicate measurement results of RSSI and channel occupancy, an indicator of channel occupancy status (e.g., low occupancy, medium occupancy, high occupancy), occupied bandwidth, NR-U frequency / cell ID, channel occupancy time, timestamp, location information, or a combination thereof.

[0049] In some implementations, the UE may be configured for immediate MDT for RSSI and channel occupancy reporting. For example, RSSI and channel occupancy reporting may be incorporated into the immediate MDT framework. In some implementations, the network may configure immediate MDT measurements for RSSI and channel occupancy reporting. For example, the network may configure immediate MDT measurements for RSSI and channel occupancy reporting to an RRC_CONNECTED mode UE for NR unlicensed frequencies. The configuration may be based on the RRC measurement process for configuration and reporting with location information. The measurements and reports for RSSI and channel occupancy include one or more parts of LTE License Assisted Access (LAA) RSSI and channel occupancy measurements / reports. The report may include location information / sensor data (if available).

[0050] Thus, the present disclosure describes radio access network (RAN)-centric data collection for UEs that can be configured for NR-U operation. Data collection can be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, New Radio (NR) or NR-U functionality and / or features, such as beam management, bandwidth part (BWP), RRC_INACTIVE, multi-radio access technology (RAT) dual connectivity (MR-DC), and dual connectivity (DC) / carrier aggregation (CA). Data collection and operational improvements can also result in reduced capital expenditure (CAPEX) and operating expenditure (OPEX) for operators, for example, through more accurate base station deployment and operation with less human resource intervention.

[0051] The present disclosure generally relates to providing or participating in communications between two or more wireless devices, such as in one or more wireless communication systems (also referred to as wireless communication networks). In various implementations, the techniques and apparatus may be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks / systems / devices), and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0052] A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and Low Code Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0053] TDMA networks can, for example, implement radio technologies such as GSM. 3GPP defines standards for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN), also denoted as GERAN. GERAN is the radio component of GSM / EDGE, along with the network of participating base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). A radio access network (RAN) refers to the component of a GSM network through which phone calls and packet data are routed from the public switched telephone network (PSTN) and the internet to user handsets (also known as user terminals or user equipment (UE)), and vice versa. A mobile phone operator's network may include one or more GERANs, and in the case of UMTS / GSM networks, the GERAN may be coupled to the Universal Terrestrial Radio Access Network (UTRAN). Operator networks may also include one or more LTE networks and / or one or more other networks. Various network types may utilize different radio access technologies (RATs) and radio access networks (RANs).

[0054] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash OFDM, and the like. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of the Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents provided by an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are either known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between various groups of telecommunications associations with the goal of defining globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond, with shared access to wireless spectrum between networks using a range of new and different radio access technologies or radio air interfaces.

[0055] 5G networks are expected to enable a wide variety of deployments, a wide variety of spectrums, and a wide variety of services and devices using a unified air interface based on OFDM. To achieve these goals, in addition to the development of new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to extend coverage to provide the following: (1) For networks with ultra-high density (e.g., ~1M nodes / km) 2 (1) coverage of the massive Internet of Things (IoT) with ultra-low complexity (e.g., ~10s of bits / second), ultra-low energy (e.g., ~10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) mission-critical control including strong security for protecting sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1ms), and users with a wide range of mobility or lack of mobility; and (3) enhanced mobile broadband including very high capacity (e.g., ~10Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experienced rates), and deep awareness for improved discovery and optimization.

[0056] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform features. These features may include: scalable numerology and transmission time intervals (TTIs); a common flexible framework to efficiently multiplex services and features using dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and improved wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, improved channel coding, and device-centric mobility. The scalability of the numerology in 5G NR (with scaling of subcarrier spacing) can efficiently address the operation of a wide variety of services across a wide variety of spectrums and a wide variety of deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, subcarrier spacing can appear, for example, using 15kHz over bandwidths of 1, 5, 10, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3 GHz, subcarrier spacing may occur with 30 kHz over 80 / 100 MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur with 60 kHz over 160 MHz bandwidth. Finally, for various deployments transmitting with the mmWave component at 28 GHz TDD, subcarrier spacing may occur with 120 kHz over 500 MHz bandwidth.

[0057] 5G NR's scalable digital scheme facilitates scalable TTIs for a wide range of latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design in which uplink / downlink scheduling information, data, and acknowledgments are in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink (which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs).

[0058] For clarity, certain aspects of apparatus and techniques may be described below with reference to exemplary LTE implementations or in an LTE-centric manner, and LTE terminology may be used in portions of the description below as an illustrative example; however, the description is not intended to be limited to LTE applications. Rather, the present disclosure relates to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces, such as those of 5G NR.

[0059] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, apparatus, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0060] Although various aspects and implementations are described in this application by way of illustration of some examples, it will be understood by those skilled in the art that additional implementations and use cases can occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and / or uses can occur via integrated chip implementations and / or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically relate to use cases or applications, there may be a variety of applicability of the described innovations. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more described aspects. In some actual settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and enforcing the claimed and described aspects. It is intended that the innovations described herein may be practiced in a wide variety of implementations, including both large / small devices of varying sizes, shapes, and compositions, chip-level components, multi-component systems (e.g., RF chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0061] Figure 1 1 shows a wireless network 100 for communication according to some aspects. The wireless network 100 may, for example, comprise a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in may have related counterparts in other network arrangements, including, for example, cellular network arrangements and non-cellular network arrangements (eg, device-to-device, or peer-to-peer, or ad hoc network arrangements, etc.).

[0062] exist Figure 1The wireless network 100 shown in FIG includes a number of base stations 105 and other network entities. A base station can be a station that communicates with a UE and can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the specific geographic coverage area of ​​a base station and / or the base station subsystem serving that coverage area, depending on the context in which the term is used. In implementations of the wireless network 100 herein, the base stations 105 can be associated with the same operator or different operators (e.g., the wireless network 100 can include multiple operator wireless networks) and can provide wireless communications using one or more of the same frequencies as neighboring cells (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof). In some examples, a single base station 105 or UE 115 can be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 can be operated by a single network operating entity.

[0063] A base station may provide communication coverage for macro cells or small cells (such as pico cells or femto cells) and / or other types of cells. A macro cell will typically cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell (such as a pico cell) will typically cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell (such as a femto cell) will typically cover a relatively small geographic area (e.g., a residence) and, in addition to restricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a residence, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown in FIG, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c use their higher-dimensional MIMO capabilities to utilize 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0064] Wireless network 100 may support synchronous operation or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous operation or asynchronous operation.

[0065] UEs 115 are dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be appreciated that, although mobile devices are generally referred to as user equipment (UE) in the standards and specifications promulgated by the Third Generation Partnership Project (3GPP), such devices may also be referred to by those skilled in the art as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, or some other appropriate terminology. Within this document, a "mobile" device or UE does not necessarily need to have the capability to move and may be stationary. Some non-limiting examples of mobile devices (such as examples of one or more of UEs 115) include mobile phones, cellular (cell) phones, smartphones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptop computers, personal computers (PCs), notebook computers, netbooks, smartbooks, tablet computers, and personal digital assistants (PDAs). The mobile device may additionally be an "Internet of Things" (IoT) or "Internet of Everything" (IoE) device, such as a car or other vehicle, a satellite radio unit, a global positioning system (GPS) device, a logistics controller, a drone, a multi-wing aircraft, a quad-wing aircraft, smart energy or security equipment, solar panels or solar arrays, municipal lighting, water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammalian implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia equipment, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, the UE may be a device that includes a universal integrated circuit card (UICC). In another aspect, the UE 115 may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The example UEs 115a-115d shown in FIG are examples of mobile smartphone-type devices accessing the wireless network 100. A UE may also be a machine specifically configured for connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The UEs 115e - 115k shown in FIG. 1 are examples of various machines configured for accessing communications of the wireless network 100 .

[0066] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, repeater, etc. Figure 1 In the embodiment of the present invention, lightning (e.g., communication link) indicates wireless transmission between a UE and a serving base station (which is a base station designated to serve the UE on the downlink and / or uplink), or desired transmission between base stations and backhaul transmission between base stations. Backhaul communication between base stations of wireless network 100 can occur using wired and / or wireless communication links.

[0067] In operation at wireless network 100, base stations 105a-105c use 3D beamforming and coordinated spatial techniques (such as coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts (such as Amber Alerts or Gray Alerts).

[0068] The wireless network 100 supports mission-critical communications using ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which is a drone. Redundant communication links with UE 115e include those from macro base stations 105d and 105e, and from small cell base station 105f. Other machine-type devices, such as UE 115f (a thermometer), UE 115g (a smart meter), and UE 115h (a wearable device), can communicate over the wireless network 100 either directly with a base station, such as small cell base station 105f and macro base station 105e, or by communicating with another user device that relays its information to the network, such as UE 115f transmitting temperature measurement information to the smart meter (UE 115g), which is then reported to the network via small cell base station 105f, in a multi-hop configuration. The wireless network 100 may also provide additional network efficiencies through dynamic, low-latency TDD / FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e.

[0069] Figure 2 Shown is a base station 105 and a UE 115 (which may be Figure 1 For a restricted association scenario (as mentioned above), the base station 105 may be Figure 1 The small cell base station 105f in the example, and the UE 115 may be a UE 115c or 115D operating in the service area of ​​the base station 105f, which, in order to access the small cell base station 105f, will be included in the list of accessible UEs for the small cell base station 105f. The base station 105 may also be some other type of base station or another network entity (e.g., a network, a network core, a network core device, etc.). Figure 2 As shown, the base station 105 may be equipped with antennas 234a through 234t, and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communications.

[0070] At the base station 105, the transmit processor 220 may receive data from a data source 212 and control information from the controller / processor 240. The control information may be for the physical broadcast channel (PBCH), the physical control format indicator channel (PCFICH), the physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), the physical downlink control channel (PDCCH), the enhanced physical downlink control channel (EPDCCH), the MTC physical downlink control channel (MPDCCH), etc. The data may be for the PDSCH, etc. The transmit processor 220 may process (e.g., encode and symbol map) the data and control information, respectively, to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for the primary synchronization signal (PSS) and the secondary synchronization signal (SSS), as well as cell-specific reference signals. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog, amplify, filter, and frequency upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

[0071] At the UE 115, antennas 252a through 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the demodulators 254a through 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0072] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for a reference signal. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 115. Processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240 .

[0073] The controllers / processors 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller / processor 240 and / or other processors and modules at the base station 105, and / or the controller / processor 28 and / or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as performing or directing the execution of the various processes described in the present invention. Figure 5-7 1 and / or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0074] Wireless communication systems operated by different network operating entities (e.g., network operators) may share spectrum. In some cases, a network operating entity may be configured to use the entire designated shared spectrum for at least a period of time prior to another network operating entity using the entire designated shared spectrum for a different period of time. Thus, to allow network operating entities to use the entire designated shared spectrum and to mitigate interfering communications between different network operating entities, certain resources (e.g., time) may be divided and allocated to different network operating entities for certain types of communications.

[0075] For example, a network operating entity may be allocated certain time resources that are reserved for exclusive communication by that network operating entity using the entire shared spectrum. A network operating entity may also be allocated other time resources in which it is given priority over other network operating entities for communication using the shared spectrum. These time resources prioritized for use by the network operating entity may be utilized on an opportunistic basis by other network operating entities if the prioritized network operating entities do not utilize these resources. Additional time resources may be allocated for use by any network operator on an opportunistic basis.

[0076] Access to the shared spectrum and arbitration of time resources among different network operating entities may be centrally controlled by a single entity, autonomously determined through a predefined arbitration scheme, or dynamically determined based on interactions between the network operator's wireless nodes.

[0077] In some cases, the UE 115 and the base station 105 may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or base station 105 may traditionally perform a medium sensing process to contend for access to the spectrum. For example, the UE 115 or base station 105 may perform a listen-before-talk (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. CCA may include an energy detection process to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, a signal power that is concentrated in a certain bandwidth and exceeds a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence used to indicate use of the channel. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel and / or acknowledgement / negative acknowledgement (ACK / NACK) feedback for packets it itself sent as a proxy for collisions.

[0078] In some implementations, the UE 115 may be configured for NR-U operation. In such an implementation, the UE 115 is configured for radio access network (RAN)-centric data collection. For example, the UE 115 may be configured for collection, storage, reporting, or a combination thereof of NR-U specific data collection. For example, the present disclosure describes that NR-U specific data collection may be used for or correspond to a radio link failure (RLF) report for listen-before-talk (LBT) failure, a random access channel (RACH) report with LBT failure information, a connection establishment failure (CEF) report for supporting RACH failure with an LBT failure indication, or a combination thereof. As another example, the present disclosure describes that NR-U specific data collection may be used for or correspond to a log-type MDT for received signal strength indicator (RSSI) and channel occupancy reporting. In addition, the present disclosure also describes that NR-U specific data collection may be used for or correspond to an immediate-type MDT for RSSI and channel occupancy reporting.

[0079] Figure 3 is a block diagram of an example wireless communication system 300 configured to provide data collection for a user equipment (UE) that may be configured for NR-U operation. In some examples, the wireless communication system 300 may implement aspects of the wireless network 100. The wireless communication system 300 includes a UE 115 and a network entity 350. As illustrative, non-limiting examples, the network entity 350 may include or correspond to a base station 105, a network, a core network, or another network device. Although one UE and one network entity are shown, in other implementations, the wireless communication system 300 may include more than one UE, more than one network entity, or both.

[0080] The UE 115 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 312, a memory 314, a transmitter 315, and a receiver 316. The processor 312 may be configured to execute instructions stored at the memory 314 to perform the operations described herein. In some implementations, the processor 312 includes or corresponds to the controller / processor 280, and the memory 314 includes or corresponds to the memory 282.

[0081] Memory 314 may include one or more modes 318 and LBT information 319. Mode 318 may include one or more modes (such as NR mode, NR-U mode), one or more channel access schemes (e.g., category 1, category 2, category 3, or category 4), an active mode, or an inactive mode of UE 115. As illustrative, non-limiting examples, the inactive mode may include an idle mode, an inactive mode, a low power mode, or another mode.

[0082] The LBT information 319 may include an RLF cause, an RLF type, a number of persistent LBT failures, a cell identifier (in which the LBT failure occurred), an uplink (UL) transmission type, a number of bandwidth parts (BWPs), a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interface type, a channel access scheme identifier, a number of LBT failures detected before a RACH attempt, an indication of resource selection due to LBT failure, a cell ID, a tracking area identifier (TAI), an NR-U RACH report identifier, an NR RACH report identifier, a RACH failure cause value for LBT failure, an indication of UL LBT failure, an indication of DL LBT failure, or a combination thereof.

[0083] The RLF cause (such as the RLF cause for NR-U) may indicate a missing radio link monitoring (RLM)-reference signal (RS) or a persistent LBT failure. The RLF type may indicate a downlink (DL) failure or a UL LBT failure. The cell identity may include or indicate the primary cell (Pcell), primary Scell ​​(PSCell), or secondary cell (Scell) in which the LBT failure was detected. The UL transmission type may include or indicate a scheduling request (SR), RACH, or physical uplink shared channel (PUSCH). The interface type may include or indicate one or more interface types, such as wireless fidelity (wifi).

[0084] The channel access scheme identifier may include or indicate a channel access scheme for NR-based access to unlicensed spectrum. For example, as an illustrative, non-limiting example, the channel access scheme identifier may include or indicate a category, such as category 1, category 2, category 3, or category 4. Category 1 may include or indicate immediate transmission after a short switching gap. Category 2 may include or indicate LBT without random backoff. Category 3 may include or indicate LBT with random backoff using a fixed-size contention window. Category 4 may include or indicate LBT with random backoff using a variable-size contention window.

[0085] The transmitter 315 is configured to send data to one or more other devices, and the receiver 316 is configured to receive data from one or more other devices. For example, the transmitter 315 can send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 316 can receive data via the network. For example, the UE 115 can be configured to send and / or receive data via: a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed within which two or more electronic devices are allowed to communicate. In some implementations, the transmitter 315 and the receiver 316 can be replaced by a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both can include or correspond to a reference Figure 2 One or more components of UE 115 are described.

[0086] The network entity 350 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 362, a memory 364, a transmitter 366, and a receiver 368. The processor 362 may be configured to execute instructions stored in the memory 364 to perform the operations described herein. In some implementations, the processor 362 includes or corresponds to the controller / processor 240, and the memory 364 includes or corresponds to the memory 242.

[0087] The transmitter 366 is configured to send data to one or more other devices, and the receiver 368 is configured to receive data from one or more other devices. For example, the transmitter 366 may send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 368 may receive data via the network. For example, the network entity 350 may be configured to send or receive data via: a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed within which two or more electronic devices are allowed to communicate. In some implementations, the transmitter 356 and the receiver 368 may be replaced by a transceiver. Additionally or alternatively, the transmitter 366, the receiver 368, or both may include or correspond to a reference to Figure 2 One or more components of base station 105 are described.

[0088] In certain implementations, the wireless communication system 300 includes a 5G network. For example, the UE 115 may include a 5G UE (e.g., a UE configured to operate in accordance with a 5G network). The network entity 350 may include a 5G base station (e.g., a base station configured to operate in accordance with a 5G network).

[0089] During operation of the wireless communication system 300, the UE 115 determines LBT information 319. The LBT information 319 may include LBT failure information. The UE 115 may generate a report 372 including the LBT information 319. The report may include a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report. The UE 115 sends the report 372 to the network entity 350.

[0090] In some implementations, the UE may be configured to provide an RLF report for LBT failure. In NR-U, persistent LBT failure may lead to RLF, at least for uplink (UL) transmissions, for which persistent failure may currently ultimately lead to RLF. In order to support mobility robustness optimization (MRO) for NR-U, user equipment (UE) RLF reporting for NR-U may be supported in NR. The RLF report for NR-U may include one or more parts of the RLF report for NR. In addition or alternatively, the RLF report for NR-U may include LBT information, such as LBT failure related information (e.g., LBT failure information). The LBT information may include the RLF cause for NR-U (e.g., missing RLM-RS, persistent LBT failure, etc.), the RLF type (e.g., downlink (DL) or UL LBT failure), the cell identity - Pcell / PSCell / Scell ​​in which the LBT failure was detected, the UL transmission type (e.g., SR, RACH, physical uplink shared channel (PUSCH)), the number of "N" BWPs with UL LBT failure, the BWP ID / frequency for each BWP, the interference type (e.g., wifi), the channel access scheme used for NR-based access for unlicensed spectrum, or a combination thereof. The channel access scheme may include or indicate category 1: immediate transmission after a short switching gap; category 2: LBT without random backoff; category 3: LBT with random backoff using a fixed-size contention window; or category 4: LBT with random backoff using a variable-size contention window.

[0091] In some implementations, the UE may be configured to provide a RACH report with LBT information (e.g., LBT failure information). In NR-U for RACH procedures, if LBT fails for a Msg1 transmission opportunity, the medium access control (MAC) may fall back to the resource selection step. In some implementations, the network may enable automatic RACH parameter setting based on RACH reports received from the UE and through PRACH parameter exchange between gNBs. The RACH report (for NR-U) may include one or more parts of the NR RACH report. In addition or alternatively, the RACH report may include LBT information, such as LBT failure information. The LBT information may include or indicate the number of LBT failure detections before each RACH attempt, an indication of resource selection due to LBT failure, or a combination thereof. RACH reports for NR-U may be collected and stored by the UE and reported to NR, and vice versa. In some implementations, a RACH report (for NR-U) may include a cell ID / tracking area identity (TAI) for each of one or more RACH report entries (to enable access node RACH report retrieval and distribution), an identifier for identifying a RACH report for NR-U and a RACH report for NR in each of one or more entries of the RACH report, an indicator of a channel access scheme for NR-based access for unlicensed spectrum, or a combination thereof. The channel access scheme may include or indicate Category 1: immediate transmission after a short switching gap; Category 2: LBT without random backoff; Category 3: LBT with random backoff utilizing a fixed-size contention window; or Category 4: LBT with random backoff utilizing a variable-size contention window.

[0092] In some implementations, the UE may be configured to provide a connection establishment failure (CEF) report with LBT information (such as an LBT failure indication). The CEF report for NR-U may include one or more parts of an NR accessibility report (e.g., an LTE accessibility report). The UE may log failed RRC connection establishment and RRC recovery failures for NR. The CEF report may include or indicate the failed cell id, radio measurement results, and neighboring cells (including the SSB index of the downlink beam of both the serving cell and the neighbor cell, which is tagged with location information (if available)). In addition, in some implementations, the CEF report may include RACH failure information, such as the SSB index, the number of preambles sent on each attempted SSB, and a flag about detected contention. The flag may be per cell, RACH attempt, or SSB. In addition or alternatively, the RACH failure information may include LBT information, such as an LBT failure indication. The failure information may include a RACH failure cause value for LBT failure, an indication of UL LBT failure or DL ​​LBT failure, the number of persistent LBT failures, the interference type (e.g., wifi), the BWP ID / frequency / cell identity in which the LBT failure was detected, an indication of the channel access scheme used for NR-based access to unlicensed spectrum, or a combination thereof. The channel access scheme may include or indicate Category 1: immediate transmission after a short switching gap; Category 2: LBT without random backoff; Category 3: LBT with random backoff using a fixed-size contention window; or Category 4: LBT with random backoff using a variable-size contention window.

[0093] therefore, Figure 3 Radio Access Network (RAN)-centric data collection for a UE that may be configured for NR-U operation is described. For example, the operations described herein provide for the collection, storage, reporting, or a combination thereof of NR-U specific data collection. For example, Figure 3 Description: NR-U specific data collection may be used for or correspond to a radio link failure (RLF) report for listen-before-talk (LBT) failure, a random access channel (RACH) report with LBT failure information, a connection establishment failure (CEF) report with LBT failure indication to support RACH failure, or a combination thereof. The data collection may be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, New Radio (NR) functionality and / or features, or NR-U functionality and / or features.

[0094] Figure 4is a block diagram of an example wireless communication system 400 configured to provide data collection for a user equipment (UE) that may be configured for NR-U operation. In some examples, the wireless communication system 300 may implement aspects of the wireless network 100 or the wireless communication system 300. The wireless communication system 300 includes a UE 115 and a network entity 350. As illustrative, non-limiting examples, the network entity 350 may include or correspond to a base station 105, a network, a core network, or another network device. Although one UE and one network entity are shown, in other implementations, the wireless communication system 300 may include more than one UE, more than one network entity, or both.

[0095] The UE 115 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 312, a memory 314, a transmitter 315, and a receiver 316. The processor 312 may be configured to execute instructions stored at the memory 314 to perform the operations described herein. In some implementations, the processor 312 includes or corresponds to the controller / processor 280, and the memory 314 includes or corresponds to the memory 282.

[0096] The memory 314 may include one or more modes 318, MTD data 422 (e.g., logged MDT data or immediate MDT data), RSSI data 427 (e.g., RSSI measurement results), and channel occupancy data 428 (e.g., channel occupancy measurement results). The mode 318 may include one or more modes of the UE 115 (such as NR mode, NR-U mode), one or more channel access schemes (e.g., category 1, category 2, category 3, or category 4), an active mode, or an inactive mode. As illustrative, non-limiting examples, the inactive mode may include an idle mode, an inactive mode, a low power mode, or another mode.

[0097] The RSSI data 427, channel occupancy data 428, or a combination thereof may include occupied bandwidth, channel occupancy time, NR-U frequency, NR-U cell ID, timestamp, location information, sensor data, an indicator of channel occupancy status (e.g., low occupancy, medium occupancy, high occupancy), or a combination thereof.

[0098] The transmitter 315 is configured to send data to one or more other devices, and the receiver 316 is configured to receive data from one or more other devices. For example, the transmitter 315 can send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 316 can receive data via the network. For example, the UE 115 can be configured to send and / or receive data via: a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed within which two or more electronic devices are allowed to communicate. In some implementations, the transmitter 315 and the receiver 316 can be replaced by a transceiver. Additionally or alternatively, the transmitter 315, the receiver 316, or both can include or correspond to a reference Figure 2 One or more components of UE 115 are described.

[0099] The network entity 350 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 362, a memory 364, a transmitter 366, and a receiver 368. The processor 362 may be configured to execute instructions stored in the memory 364 to perform the operations described herein. In some implementations, the processor 362 includes or corresponds to the controller / processor 240, and the memory 364 includes or corresponds to the memory 242.

[0100] The transmitter 366 is configured to send data to one or more other devices, and the receiver 368 is configured to receive data from one or more other devices. For example, the transmitter 366 may send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 368 may receive data via the network. For example, the network entity 350 may be configured to send or receive data via: a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed within which two or more electronic devices are allowed to communicate. In some implementations, the transmitter 356 and the receiver 368 may be replaced by a transceiver. Additionally or alternatively, the transmitter 366, the receiver 368, or both may include or correspond to a reference to Figure 2 One or more components of base station 105 are described.

[0101] In certain implementations, the wireless communication system 300 includes a 5G network. For example, the UE 115 may include a 5G UE (e.g., a UE configured to operate in accordance with a 5G network). The network entity 350 may include a 5G base station (e.g., a base station configured to operate in accordance with a 5G network).

[0102] During operation of the wireless communication system 400, the UE 115 may receive a configuration message 370 from the network entity 350. The configuration message 470 may indicate that RSSI and channel occupancy information is logged using log-type Minimization of Drive Test (MDT) information, or may indicate that an immediate MDT measurement for RSSI and channel occupancy is configured. In some implementations, the configuration message 470 may be based on an RRC measurement procedure for configuration and reporting including location information. Additionally or alternatively, the configuration message 470 may include or indicate an NR-U frequency list / cell ID list for RSSI and channel occupancy logging, a logging area for NR-U, a logging interval for RSSI and channel occupancy measurements, or a combination thereof.

[0103] The UE 115 determines a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE. The RSSI and channel occupancy information may include or correspond to RSSI data 427, channel occupancy data 428, or a combination thereof. The RSSI and channel occupancy information includes RSSI and channel occupancy measurement results, an indicator of channel occupancy status (low occupancy, medium occupancy, high occupancy), occupied bandwidth, NR-U frequency / cell ID, channel occupancy time, timestamp, location information, or a combination thereof.

[0104] UE 115 sends a report 472 including RSSI and channel occupancy information. In some implementations, report 472 may include MTD data 422, RSSI data 427, channel occupancy data 428, or a combination thereof. Report 472 may include a logged minimization of drive tests (MDT) report. Additionally or alternatively, report 472 may include an ad hoc minimization of drive tests (MDT) report. An ad hoc MDT report may include location information, sensor data, or a combination thereof.

[0105] In some implementations, the UE may be configured for log-type MDT for RSSI and channel occupancy reporting. For example, NR-U may support RSSI and channel occupancy configuration and reporting, such as measurement and periodic reporting within an interval (at least for CO). In some implementations, log-type MDT may support logging of RSSI and channel occupancy, such as when in an inactive mode (such as RRC_IDLE / RRC_INACTIVE mode). In some implementations, the network may send a log-type measurement configuration (e.g., a configuration) to the UE to log RSSI and channel occupancy in RRC idle or RRC_INACTIVE mode. The configuration may include or indicate an NR-U frequency list / cell ID list for RSSI and channel occupancy logging, a logging area for NR-U, a logging interval for RSSI and channel occupancy measurements, or a combination thereof. The UE may report the contents of the log-type MDT for NR-U RSSI and channel occupancy reporting. The report may include or indicate measurement results of RSSI and channel occupancy, an indicator of channel occupancy status (e.g., low occupancy, medium occupancy, high occupancy), occupied bandwidth, NR-U frequency / cell ID, channel occupancy time, timestamp, location information, or a combination thereof.

[0106] In some implementations, the UE may be configured for immediate MDT for RSSI and channel occupancy reporting. For example, RSSI and channel occupancy reporting may be incorporated into the immediate MDT framework. In some implementations, the network may configure immediate MDT measurements for RSSI and channel occupancy reporting. For example, the network may configure immediate MDT measurements for RSSI and channel occupancy reporting to RRC_CONNECTED mode UEs for NR unlicensed frequencies. The configuration may be based on the RRC measurement process for configuration and reporting with location information. The measurements and reports for RSSI and channel occupancy include one or more parts of LTE License Assisted Access (LAA) RSSI and channel occupancy measurements / reports. The report may include location information / sensor data.

[0107] therefore, Figure 4 Radio Access Network (RAN)-centric data collection for a UE that may be configured for NR-U operation is described. For example, the operations described herein provide for the collection, storage, reporting, or a combination thereof of NR-U specific data collection. For example, Figure 4 Describes that NR-U specific data collection may be used for or correspond to logging-type MDT for received signal strength indicator (RSSI) and channel occupancy reporting. In addition, Figure 4It is also described that NR-U specific data collection can be used for or corresponds to ad hoc MDT for RSSI and channel occupancy reporting. The data collection can be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, New Radio (NR) functions and / or features, or NR-U functions and / or features.

[0108] Figure 5-Figure 6 is a flow chart illustrating an example method for communication performed by a UE. For example, according to some aspects of the present disclosure, example blocks of the method may cause the UE to perform data collection associated with NR-U operation. Figure 8 The UE 115 shown in FIG. 1 depicts an example box. Figure 8 is a block diagram conceptually illustrating an example design of a UE configured to perform data collection associated with NR-U operation according to one aspect of the present disclosure. Figure 2 or 3- Figure 4 1. For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in a memory 282 and controls the components of the UE 115 that provide the features and functions of the UE 115. Under the control of the controller / processor 280, the UE 115 transmits and receives signals via wireless radios 801a-r and antennas 252a-r. The wireless radios 801a-r include the following: Figure 2 Various components and hardware are shown for UE 115 in FIG, including modulators / demodulators 254a-r, a MIMO detector 256, a receive processor 258, a transmit processor 264, and a TX MIMO processor 266.

[0109] As shown, the memory 282 may include measurement logic 802 and a report generator 803. The measurement logic 802 may be configured to monitor or measure data, and to generate or calculate measured data (e.g., result data). For example, the data monitored, measured, generated, or calculated by the measurement logic 802 may include or correspond to LBT information 319, MTD data 422, RSSI data 427, channel occupancy data 428, location data (e.g., GPS data), or a combination thereof. The report generator 803 may be configured to generate one or more reports, such as report 372, report 472, or a combination thereof. In some aspects, the measurement logic 802, the report generator 803, or a combination thereof may include or correspond to the processor 302. The UE 115 may receive signals from and / or send signals to one or more network entities (such as a base station 105, a network entity 350, a network or core network device), such as a base station 105, a network entity 350, a network or core network device, or a network entity 350. Figure 1 As shown in .

[0110] refer to Figure 5 , a sample flow chart illustrating a method 500 of UE operation for communication is shown. In some implementations, the method 500 may be performed by the UE 115. In other implementations, the method 500 may be performed by an apparatus configured for wireless communication. For example, the apparatus may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations of the method 500. In other implementations, the method 500 may be performed or executed using a non-transitory computer-readable medium having program code recorded thereon. The program code may be program code executable by a computer to cause the computer to perform the operations of the method 500.

[0111] As shown at block 502, the UE determines listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of the UE. The UE may be configured to perform NR-U operation during the determination of the LBT information. The LBT information may include LBT failure information. The LBT information may include or correspond to LBT information 319. For example, the UE 115 may use measurement logic 1002 to determine the LBT information.

[0112] In some implementations, the LBT information includes a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a cell identifier, an uplink (UL) transmission type, a number of bandwidth parts (BWPs), a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interface type, a channel access scheme identifier, a number of LBT failures detected before a RACH attempt, an indication of resource selection due to LBT failure, a cell ID, a tracking area identifier (TAI), an NR-U random access channel (RACH) report identifier, a new radio (NR) RACH report identifier, a RACH failure cause value for LBT failure, an indication of UL LBT failure, an indication of DL LBT failure, or a combination thereof.

[0113] At 504, the UE sends a report including the LBT information. For example, the report may include or correspond to report 372. The report may include a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report.

[0114] In some implementations, sending the report includes sending a first report and a second report. The first report includes one selected from the group consisting of a radio link failure (RLF) report, a random access channel (RACH) report, and a connection establishment failure (CEF) report, and the second report includes one selected from the group consisting of a radio link failure (RLF) report, a random access channel (RACH) report, and a connection establishment failure (CEF) report.

[0115] In some implementations, the report includes a radio link failure (RLF) report. In some such implementations, the LBT information includes a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a cell identity, an uplink (UL) transmission type, a number of bandwidth parts (BWPs), a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interface type, a channel access scheme identifier, or a combination thereof.

[0116] In some implementations, the report comprises a random access channel (RACH) report. In some such implementations, the LBT information comprises a channel access scheme identifier, a number of LBT failures detected before the RACH attempt, an indication of resource selection due to the LBT failure, a cell ID, a tracking area identity (TAI), an NR-U random access channel (RACH) report identifier, a new radio (NR) RACH report identifier, a RACH failure cause value for the LBT failure, or a combination thereof.

[0117] In some implementations, the report comprises a connection establishment failure (CEF) report. In some such implementations, the LBT information comprises a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interface type, a channel access scheme identifier, a cell ID, an indication of an UL LBT failure, an indication of a DL LBT failure, or a combination thereof.

[0118] Thus, method 500 implements radio access network (RAN)-centric data collection for a UE that may be configured for NR-U operation. For example, the operations described herein provide for the collection, storage, reporting, or a combination thereof of NR-U specific data collection. For example, method 500 describes that NR-U specific data collection may be used for or correspond to a radio link failure (RLF) report for a listen-before-talk (LBT) failure, a random access channel (RACH) report with LBT failure information, a connection establishment failure (CEF) report for supporting RACH failure with an LBT failure indication, or a combination thereof. The data collection may be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, new radio (NR) functionality and / or features, or NR-U functionality and / or features.

[0119] refer to Figure 6 , a sample flow chart illustrating a method 600 of UE operation for communication is shown. In some implementations, the method 600 may be performed by the UE 115. In other implementations, the method 600 may be performed by an apparatus configured for wireless communication. For example, the apparatus may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations of the method 600. In other implementations, the method 600 may be performed or executed using a non-transitory computer-readable medium having program code recorded thereon. The program code may be program code executable by a computer to cause the computer to perform the operations of the method 600.

[0120] As shown at block 602, the UE determines a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE. The UE is configured to perform NR-U operation during the determination of the RSSI and channel occupancy information. The RSSI and channel occupancy information may include or correspond to RSSI data 427, channel occupancy data 428, or a combination thereof. The RSSI and channel occupancy information may include measurement results of RSSI and channel occupancy, indicators of channel occupancy status (low occupancy, medium occupancy, high occupancy), occupied bandwidth, NR-U frequency / cell ID, channel occupancy time, timestamp, location information, or a combination thereof. For example, the UE 115 may use measurement logic 1002 to determine the RSSI and channel occupancy information.

[0121] At 604, the UE transmits a report including RSSI and channel occupancy information via the UE. The report may include or correspond to report 472. For example, the report may include a logged minimization of drive test (MDT) report or an ad hoc minimization of drive test (MDT) report. The ad hoc MDT report may include location information, sensor data, or a combination thereof.

[0122] In some implementations, method 600 may further include receiving, by the UE from the network entity, a configuration message for logging RSSI and channel occupancy information using logged minimization of drive tests (MDT) information, a configuration message for configuring immediate MDT measurements for RSSI and channel occupancy, or a combination thereof. The configuration message may include or correspond to configuration message 470. In some implementations, the configuration message is based on or included in an RRC measurement procedure for configuring and reporting including location information. Additionally or alternatively, the configuration message includes or indicates an NR-U frequency list / cell ID list for RSSI and channel occupancy logging, a logging area for NR-U, a logging interval for RSSI and channel occupancy measurements, or a combination thereof.

[0123] In some implementations, method 600 may include receiving, by the UE from a network entity, a configuration message for recording RSSI and channel occupancy information using logged minimization of drive tests (MDT) information. The configuration may include a list of NR-U frequencies for RSSI and channel occupancy recording, a list of NR-U cell IDs for RSSI and channel occupancy recording, a logging area for NR-U, a logging interval for RSSI and channel occupancy measurements, or a combination thereof. In addition or alternatively, method 600 may include recording RSSI and channel occupancy using logged MDT when the UE is in an inactive mode. The inactive mode may be an RRC_IDLE mode or an RRC_INACTIVE mode. In some implementations, the RSSI and channel occupancy information include measurement results of RSSI and channel occupancy, an indicator of channel occupancy status, occupied bandwidth, NR-U frequency, NR-U cell ID, channel occupancy time, timestamp, location information, or a combination thereof.

[0124] In some implementations, method 600 may include receiving, by the UE from a network entity, a configuration message for configuring an immediate MDT measurement for RSSI and channel occupancy. In some such implementations, the UE determines the immediate MDT measurement and the RSSI and channel occupancy information when the UE is in a radio resource control (RRC) connected mode. The RSSI and channel occupancy information may correspond to the UE's location information.

[0125] Thus, method 600 implements radio access network (RAN)-centric data collection for a UE that may be configured for NR-U operation. For example, the operations described herein provide for the collection, storage, reporting, or a combination thereof of NR-U specific data collection. For example, method 600 describes that NR-U specific data collection may be used for or correspond to log-type MDT for received signal strength indicator (RSSI) and channel occupancy reporting. Additionally, method 600 also describes that NR-U specific data collection may be used for or correspond to ad hoc MDT for RSSI and channel occupancy reporting. Data collection may be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, New Radio (NR) functionality and / or features, or NR-U functionality and / or features.

[0126] It should be noted that the reference Figure 5-Figure 6 One or more blocks (or operations) described herein may be combined with one or more blocks (or operations) of another diagram. Figure 5-Figure 6 One or more boxes can be combined with Figure 2-Figure 4 In addition or alternatively, the above reference Figures 1-6 and Figure 8 One or more of the operations described may be combined with reference to Figure 9 Describes a combination of one or more operations.

[0127] Figure 7 is a flow chart illustrating an example method 700 for communication performed by a network entity. For example, according to some aspects of the present disclosure, example blocks of the method 700 may cause the network entity to transmit a configuration message. Figure 9 The network entity 350 shown in FIG. 3 depicts an example block. Figure 9 is a block diagram conceptually illustrating an example design of a network entity 350 , such as base station 105 , a network, or a core network, as an illustrative, non-limiting example.

[0128] The network entity 350 includes Figure 2-Figure 4 105, 350. For example, the network entity 350 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and controls the components of the network entity 350 that provide the features and functions of the network entity 350. Under the control of the controller / processor 240, the network entity 350 sends and receives signals via wireless radios 901a-r and antennas 234a-r. The wireless radios 901a-r include the following: Figure 2105 , including the modulator / demodulators 232a-t, the transmit processor 220, the TX MIMO processor 230, the MIMO detector 236, and the receive processor 238. As shown, the memory 242 may include a configuration generator 902 and communication logic 903. The configuration generator 902 may be configured to generate one or more configurations or configuration messages, such as the measurement configuration 470. The communication logic 903 may enable the network entity 350 to perform one or more operations for wireless communication. In some aspects, the configuration generator 902, the communication logic 903, or a combination thereof may include or correspond to the processor 362. The network entity 350 may receive a UE (such as a UE) from a UE. Figure 8 UE 115) shown in FIG receives signals and / or sends signals to the UE.

[0129] refer to Figure 7 , illustrates an example flow chart of a method 700 for network entity operations for communication. In some implementations, the method 700 may be performed by an apparatus configured for wireless communication, such as the network entity 350 (e.g., 105). For example, the apparatus may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations of the method 700. In other implementations, the method 700 may be performed or executed using a non-transitory computer-readable medium having program code recorded thereon. The program code may be program code executable by a computer to cause the computer to perform the operations of the method 700.

[0130] As shown at block 702, method 700 includes sending, by a network entity, a configuration message to a user equipment (UE). The configuration message may include or correspond to configuration message 470. In some implementations, the configuration includes a NR-U frequency list for RSSI and channel occupancy logging, a NR-U cell ID list for RSSI and channel occupancy logging, a logging area for NR-U, a logging interval for RSSI and channel occupancy measurements, or a combination thereof. The UE may include or correspond to UE 115. The network generator 350 may use a configuration generator 902 to generate the configuration message. The network entity 350 may use wireless radios 1101a-t, antennas 234a-t, and communication logic 903 to send the measurement configuration message.

[0131] At 704, method 700 also includes the network entity receiving a report from the UE, the report including a received signal strength indicator (RSSI) and channel occupancy information for New Radio - Unlicensed (NR-U) operation of the UE. The report may include or correspond to report 472. The report may include a logged minimization of drive tests (MDT) report or an ad hoc minimization of drive tests (MDT) report. The network entity 350 may receive the report using wireless radios 901a-t, antennas 234a-t, and communication logic 903.

[0132] In some implementations, method 700 further includes receiving, by the network entity, an additional report. The additional report may include or correspond to report 372. For example, the additional report may include listen-before-talk (LBT) information associated with NR-U operation of the UE. In some implementations, the additional report includes a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report.

[0133] Thus, method 700 implements radio access network (RAN)-centric data collection for UEs that may be configured for NR-U operation. The data collection may be advantageously used to improve device (e.g., UE) performance, such as battery life, throughput, latency, reliability, New Radio (NR) functionality and / or features, or NR-U functionality and / or features.

[0134] It should be noted that the reference Figure 7 One or more blocks (or operations) described herein may be combined with one or more blocks (or operations) of another diagram. Figure 7 One or more boxes can be combined with Figure 2-Figure 4 In addition or alternatively, the above reference Figure 1-Figure 4 、 Figure 7 and Figure 9 One or more of the operations described may be combined with reference to Figure 8 Describes a combination of one or more operations.

[0135] In some aspects, data collection for NR-U data collection may include a wireless device, which determines, by a user equipment (UE), listen-before-talk (LBT) information associated with a New Radio - Unlicensed (NR-U) operation of the UE; and sending, by the UE, a report including the LBT information. In some implementations, the wireless device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the wireless device. In other implementations, a non-transitory computer-readable medium has program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with respect to the wireless device.

[0136] In a first aspect, the UE is configured for NR-U operation during determination of LBT information.

[0137] In a second aspect, alone or in combination with the first aspect, the LBT information includes LBT failure information.

[0138] In a third aspect, alone or in combination with one or more of the first to second aspects, the LBT information includes a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a cell identifier, an uplink (UL) transmission type, a number of bandwidth parts (BWPs), a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interface type, a channel access scheme identifier, a number of LBT failures detected before a RACH attempt, an indication of resource selection due to LBT failure, a cell ID, a tracking area identifier (TAI), an NR-U random access channel (RACH) report identifier, a new radio (NR) RACH report identifier, a RACH failure cause value for LBT failure, an indication of UL LBT failure, an indication of DL LBT failure, or a combination thereof.

[0139] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the report comprises a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report.

[0140] In the fifth aspect, alone or in combination with one or more aspects of the first to fourth aspects, it may include: sending a report includes sending a first report and a second report; the first report includes a report selected from the group including the following items: a radio link failure (RLF) report, a random access channel (RACH) report and a connection establishment failure (CEF) report; and the second report includes a report selected from the group including the following items: a radio link failure (RLF) report, a random access channel (RACH) report and a connection establishment failure (CEF) report.

[0141] In a sixth aspect, alone or in combination with one or more of aspects 1 to 4, the report comprises a radio link failure (RLF) report; and the LBT information comprises a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a cell identifier, an uplink (UL) transmission type, a number of bandwidth parts (BWPs), a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interface type, a channel access scheme identifier, or a combination thereof.

[0142] In a seventh aspect, alone or in combination with one or more of aspects 1 to 4, the report comprises a random access channel (RACH) report; and the LBT information comprises a channel access scheme identifier, a number of LBT failures detected before a RACH attempt, an indication of resource selection due to LBT failure, a cell ID, a tracking area identifier (TAI), an NR-U random access channel (RACH) report identifier, a new radio (NR) RACH report identifier, a RACH failure cause value for LBT failure, or a combination thereof.

[0143] In an eighth aspect, alone or in combination with one or more of aspects one to four, the report comprises a connection establishment failure (CEF) report; and the LBT information comprises a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interface type, a channel access scheme identifier, a cell ID, an indication of a UL LBT failure, an indication of a DL LBT failure, or a combination thereof.

[0144] In some aspects, data collection for NR-U may include a wireless device that performs the following operations: determining, by a user equipment (UE), a received signal strength indicator (RSSI) and channel occupancy information for new radio-unlicensed (NR-U) operation of the UE; and sending, by the UE, a report including the RSSI and channel occupancy information. In some implementations, the wireless device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the wireless device. In other implementations, a non-transitory computer-readable medium has program code recorded thereon, and the program code may be executable by a computer for causing the computer to perform the operations described herein with reference to the wireless device.

[0145] In a ninth aspect, the UE is configured to perform NR-U operation during determination of RSSI and channel occupancy information.

[0146] In a tenth aspect, alone or in combination with the ninth aspect, the report comprises a logged minimization of drive tests (MDT) report or an immediate minimization of drive tests (MDT) report.

[0147] In an eleventh aspect, alone or in combination with one or more of the ninth to tenth aspects, a configuration message for recording RSSI and channel occupancy information using logged Minimization of Drive Test (MDT) information is received from a network entity.

[0148] In the twelfth aspect, alone or in combination with one or more aspects of the ninth to eleventh aspects, the configuration includes: an NR-U frequency list for RSSI and channel occupancy recording, an NR-U cell ID list for RSSI and channel occupancy recording, a recording area for NR-U, a recording interval for RSSI and channel occupancy measurement, or a combination thereof.

[0149] In a thirteenth aspect, alone or in combination with one or more of the ninth to twelfth aspects, it may include: when the UE is in an inactive mode, utilizing logged MDT to record RSSI and channel occupancy.

[0150] In a fourteenth aspect, alone or in combination with the thirteenth aspect, the inactive mode includes an RRC_IDLE mode or an RRC_INACTIVE mode.

[0151] In the fifteenth aspect, alone or in combination with one or more of aspects nine to fourteen, the RSSI and channel occupancy information includes measurement results of RSSI and channel occupancy, an indicator of channel occupancy status, occupied bandwidth, NR-U frequency, NR-U cell ID, channel occupancy time, timestamp, location information, or a combination thereof.

[0152] In a sixteenth aspect, alone or in combination with one or more of the ninth to tenth aspects, it may include receiving a configuration message for configuring immediate MDT measurements for RSSI and channel occupancy from a network entity.

[0153] In a seventeenth aspect, alone or in combination with the sixteenth aspect, the UE determines immediate MDT measurements as well as RSSI and channel occupancy information when the UE is in a radio resource control (RRC) connected mode.

[0154] In an eighteenth aspect, alone or in combination with one or more of the sixteenth to seventeenth aspects, the RSSI and the channel occupancy information correspond to location information of the UE.

[0155] In some aspects, data collection for NR-U may include a wireless device, which sends a configuration message to a user equipment (UE) by a network entity; and receives a report from the UE by the network entity, the report including a received signal strength indicator (RSSI) and channel occupancy information for new radio-unlicensed (NR-U) operation of the UE. In some implementations, the wireless device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the wireless device. In other implementations, a non-transitory computer-readable medium has program code recorded thereon, and the program code may be executable by a computer for causing the computer to perform the operations described herein with reference to the wireless device.

[0156] In a nineteenth aspect, the report comprises a log-type minimization of drive testing (MDT) report.

[0157] In a twentieth aspect, alone or in combination with the nineteenth aspect, the reporting comprises an ad hoc minimization of drive tests (MDT) report.

[0158] In aspect 21, alone or in combination with one or more aspects from aspects 19 to 20, the configuration message indicates the use of log-type minimization of drive test (MDT) information to record RSSI and channel occupancy information, or configures immediate MDT measurements for RSSI and channel occupancy.

[0159] In aspect 22, alone or in combination with one or more of aspects 19 to 20, the configuration includes an NR-U frequency list for RSSI and channel occupancy recording, an NR-U cell ID list for RSSI and channel occupancy recording, a recording area for NR-U, a recording interval for RSSI and channel occupancy measurement, or a combination thereof.

[0160] In the twenty-third aspect, alone or in combination with one or more of aspects nineteen to twenty-second, it may include receiving an additional report.

[0161] In a twenty-fourth aspect, alone or in combination with the twenty-fourth aspect, the additional report includes listen-before-talk (LBT) information associated with the NR-U operation of the UE.

[0162] In a twenty-fifth aspect, alone or in combination with one or more of aspects twenty-four to twenty-fifth, the additional report comprises a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report.

[0163] Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0164] This article is in Figures 1-9 The functional blocks and modules described herein include processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof. In addition, the features discussed herein can be implemented via dedicated processor circuits, via executable instructions, and / or a combination thereof.

[0165] Those skilled in the art will also appreciate that the various illustrative logic blocks, modules, circuits and algorithmic steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits and steps have been generally described above around their functions. Whether such functions are implemented as hardware or software depends on specific applications and the design constraints imposed on the entire system. Those skilled in the art can implement the described functions in a flexible manner for each specific application, but such implementation decisions should not be interpreted as causing deviations from the scope of the present disclosure. Those skilled in the art will also readily appreciate that the components, methods or interactive order or combinations described herein are merely examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner different from those shown and described herein.

[0166] The various illustrative logic blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0167] The steps of the method or algorithm described in conjunction with the disclosure herein can be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module can be present in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative manner, the storage medium can be indispensable for the processor. The processor and the storage medium can be present in an ASIC. The ASIC can be present in a user terminal. In an alternative manner, the processor and the storage medium can be present in a user terminal as discrete components.

[0168] In one or more exemplary designs, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium as one or more instructions or codes or transmitted therethrough. Computer-readable media include both computer storage media and communication media, and the communication media include any media that facilitates the transfer of a computer program from one place to another. Computer-readable storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, disk storage, or other magnetic storage devices, or can be used to carry or store desired program code units in the form of instructions or data structures and any other medium that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. In addition, a connection can be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL), the coaxial cable, fiber optic cable, twisted pair, or DSL are included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), hard disk, solid state drive, and Blu-ray disc, wherein disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0169] As used herein, including in the claims, the term "and / or," when used in a list of two or more items, means that any one of the listed items may be taken alone, or any combination of two or more of the listed items may be taken. For example, if a composition is described as comprising components A, B, and / or C, the composition may comprise only A; only B; only C; A and B combined; A and C combined; B and C combined; or A, B, and C combined. Furthermore, as used herein, including in the claims, "or," as used in a list of items ending with "at least one of," indicates a disjunctive list, such that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any one of these items in any combination thereof.

[0170] The foregoing description of the present disclosure is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the overall principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the examples and designs described herein, but is to be given the widest scope consistent with the principles and novel features disclosed herein.

[0171] Radio Access Network (RAN)-centric data collection for New Radio (NR)-Unlicensed (U)

[0172] IDF 201504WO1

[0173] appendix Background Art

[0175] Release 16 and beyond work items on radio access network (RAN)-centric data collection and utilization for New Radio (NR) are key features of 5G big data, benchmarking Long Term Evolution (LTE) Substructured Network (SON) / Minimization of Drive Test (MDT) by incorporating new NR features such as beam management, bandwidth part (BWP), RRC_INACTIVE, Multi-Radio Access Technology (RAT) Dual Connectivity (MR-DC), and NR-U.

[0176] Data collection can be used to optimize device performance (e.g., battery life, throughput, latency, reliability), and can also reduce operators’ capital expenditures (CAPEX) and operating expenditures (OPEX), for example through more accurate base station deployment and operation with much less human resource intervention.

[0177] NR-U is a new Release 16 feature. Due to the lack of time in 3GPP, Dual Connectivity (DC) / Carrier Aggregation (CA)

[0178] Specific data collection has not yet been widely discussed. Future research is anticipated.

[0179] proposal

[0180] This disclosure proposes enhancements to the current RAN-centric data collection for NR to support NR-U specific data collection.

[0181] Set Method

[0182] ° Enhancements to Radio Link Failure (RLF) reporting for Listen Before Talk (LBT) failure

[0183] ° Enhancements to Random Access Channel (RACH) reporting with LBT failure information

[0184] ° Enhancements to Connection Establishment Failure (CEF) reporting with LBT Failure indication to support RACH failure

[0185] ° Enhancements to logged MDT for Received Signal Strength Indicator (RSSI) and channel occupancy reporting

[0186] ° Enhancements to Immediate MDT for RSSI and Channel Occupancy Reporting

[0187] Proposal: Enhancements to RLF reporting for LBT failures

[0188] Consensus reached in version 16NR-U:

[0189] °Continued LBT failures may lead to RLF, at least for uplink (UL) transmissions, for which continued failures may eventually lead to RLF

[0190] To support Mobility Robustness Optimization (MRO) for NR-U, UE RLF reporting for NR-U should also be supported in NR.

[0191] ° Using the current RLF report as a baseline, the RLF report for NR-U can also include information related to LBT failure:

[0192] RLF for NR-U - Cause: Missing RLM-RS, continuous LBT failure

[0193] RLF type: Downlink (DL) or UL LBT failure

[0194] The number of persistent LBT failures

[0195] Cell ID, Pcell / PSCell / Scell ​​where LBT failure was detected

[0196] UL transmission type: SR, RACH, physical uplink shared channel (PUSCH)

[0197] Number of "N" BWPs with UL LBT failures, BWP ID / frequency for each BWP

[0198] Interference type, such as WiFi

[0199] Channel access scheme for NR-based access to unlicensed spectrum

[0200] ° Category 1: Transmission immediately after a short switching gap

[0201] °Category 2: LBT without random backoff

[0202] ° Category 3: LBT with random backoff using a fixed-size contention window

[0203] ° Category 4: LBT with random backoff utilizing variable-sized contention windows

[0204] Proposal: Enhancement to RACH reporting with LBT failure information

[0205] Achieve consensus on RACH procedures in Release 16 NR-U

[0206] ° If LBT fails for the Msg1 transmission opportunity, the Medium Access Control (MAC) returns to the resource selection step. Automatic RACH parameter setting can be achieved by collecting RACH reports from the UE and by PRACH parameter exchange between gNBs.

[0207] In exchange for enabling proposals:

[0208] ° Using NR RACH reporting as a reference, and also including subsequent LBT failure information in the RACH report content:

[0209] Number of LBT failure detections before each RACH attempt

[0210] Indication of resource selection failure due to LBT

[0211] ° RACH reports for NR-U can be collected and stored by UE and reported to NR and vice versa

[0212] Cell ID / Tracking Area Identity (TAI) is included in each RACH report entry to facilitate cross-node RACH report retrieval and distribution

[0213] An identifier in each entry of the RACH report to identify the RACH report for NR-U and the RACH report for NR

[0214] Channel access scheme for NR-based access to unlicensed spectrum

[0215] ° Category 1: Transmission immediately after a short switching gap

[0216] °Category 2: LBT without random backoff

[0217] ° Category 3: LBT with random backoff using a fixed-size contention window

[0218] ° Category 4: LBT with random backoff utilizing variable-sized contention windows

[0219] Proposal: Enhancement to CEF reporting with LBT failure indication

[0220] Release 16 NR accessibility reporting uses LTE accessibility reporting as a benchmark

[0221] °UE records failed RRC connection establishment and RRC recovery failures for NR

[0222] °NR Connection Establishment Failure (CEF) report includes:

[0223] The failed cell id, its radio measurements and neighboring cells, including the SSB index of the downlink beams of both the serving cell and the neighbor cells, tagged with location information, if available

[0224] RACH failure information: Synchronization Signal Block (SSB) index, number of preambles sent on each attempted SSB, and a flag about detected contention. The flag can be per cell, RACH attempt, or SSB

[0225] Proposal: Enhance RACH failure information by adding LBT failure indication to CEF reporting

[0226] ° Added new RACH failure cause value for LBT failure

[0227] Indication of UL LBT failure or DL ​​LBT failure

[0228] The number of persistent LBT failures

[0229] Interference type, such as WiFi

[0230] BWP ID / frequency / cell ID where the LBT failure was detected

[0231] Channel access scheme for NR-based access to unlicensed spectrum

[0232] ° Category 1: Transmission immediately after a short switching gap

[0233] °Category 2: LBT without random backoff

[0234] ° Category 3: LBT with random backoff using fixed-size contention windows

[0235] ° Category 4: LBT with random backoff utilizing variable-sized contention windows

[0236] Enhancements to Logged MDT for RSSI and Channel Occupancy Reporting

[0237] Release 16 NR-U supports RSSI and channel occupancy configuration and reporting, specifically, measurements within an interval (at least for the CO)

[0238] and periodic reporting

[0239] Proposal: Enhance NR Logged MDT to support logging RSSI and channel occupancy in RRC_IDLE / RRC_INACTIVE modes

[0240] ° The network sends a logging measurement configuration to the UE to record RSSI and channel occupancy in RRC idle or RRC_INACTIVE mode. The configuration includes:

[0241] NR-U frequency list / cell ID list for RSSI and channel occupancy records

[0242] NR-U recording area

[0243] Logging interval for RSSI and channel occupancy measurements

[0244] ° Report content of log-based MDT for NR-U RSSI and channel occupancy reports

[0245] RSSI and channel occupancy measurement results

[0246] Indicator of channel occupancy status (low occupancy, medium occupancy, high occupancy)

[0247] Bandwidth occupied

[0248] NR-U frequency / cell ID

[0249] Channel occupancy time

[0250] Timestamp

[0251] Detailed location information

[0252] Enhancements to Immediate MDT for RSSI and Channel Occupancy Reporting

[0253] ·proposal:

[0254] ° Incorporate RSSI and channel occupancy reporting into the real-time MDT framework

[0255] ° The network configures the RRC_CONNECTED mode UE with immediate MDT measurements for RSSI and channel occupancy reporting for NR unlicensed frequencies

[0256] ° This configuration is based on the existing RRC measurement procedure for configuration and reporting with some extensions for location information

[0257] ° RSSI and channel occupancy measurements and reporting can use LTE License Assisted Access (LAA) RSSI and channel occupancy measurements / reporting as a baseline

[0258] ° Detailed location information / sensor data (if available) is included in RSSI and channel occupancy reports

Claims

1. A method for wireless communication performed by a user equipment (UE), the method comprising: determining listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of the UE; as well as Sending a report including the LBT information, wherein the report includes a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report, wherein When the report includes a radio link failure (RLF) report, the LBT information includes a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a cell identifier, an uplink (UL) transmission type, a number of bandwidth parts (BWPs), a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interference type, a channel access scheme identifier, or a combination thereof.

2. The method according to claim 1, wherein: The UE is configured to perform NR-U operation during determining the LBT information; The LBT information includes LBT failure information; or Its combination.

3. The method according to claim 1, wherein: Sending the report includes sending a first report and a second report; The first report comprises one report selected from the group consisting of: a radio link failure (RLF) report, a random access channel (RACH) report, and a connection establishment failure (CEF) report; and The second report comprises one report selected from the group consisting of: a radio link failure (RLF) report, a random access channel (RACH) report, and a connection establishment failure (CEF) report.

4. The method according to claim 1, wherein: When the report includes a random access channel (RACH) report, the LBT information includes a channel access scheme identifier, a number of LBT failures detected before the RACH attempt, an indication of resource selection due to LBT failure, a cell ID, a tracking area identifier (TAI), an NR-U random access channel (RACH) report identifier, a new radio (NR) RACH report identifier, a RACH failure cause value for LBT failure, or a combination thereof.

5. The method according to claim 1, wherein: When the report includes a connection establishment failure (CEF) report, the LBT information includes a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interference type, a channel access scheme identifier, a cell ID, an indication of UL LBT failure, an indication of DL LBT failure, or a combination thereof.

6. A user equipment configured for wireless communication, the user equipment comprising: at least one processor; as well as a memory coupled to the at least one processor, Wherein, the at least one processor is configured to: determining listen-before-talk (LBT) information associated with New Radio - Unlicensed (NR-U) operation of the user equipment; and initiating transmission of a report comprising the LBT information, wherein the report comprises a radio link failure (RLF) report, a random access channel (RACH) report, or a connection establishment failure (CEF) report, wherein When the report includes a radio link failure (RLF) report, the LBT information includes a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a cell identifier, an uplink (UL) transmission type, a number of bandwidth parts (BWPs), a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interference type, a channel access scheme identifier, or a combination thereof.

7. The user equipment according to claim 6, wherein: The user equipment is configured to perform NR-U operation during the determination of the LBT information; The LBT information includes LBT failure information; or Its combination.

8. The user equipment according to claim 6, wherein: The transmitting of the report includes transmitting a first report and a second report; The first report comprises one report selected from the group consisting of: a radio link failure (RLF) report, a random access channel (RACH) report, and a connection establishment failure (CEF) report; and The second report comprises one report selected from the group consisting of: a radio link failure (RLF) report, a random access channel (RACH) report, and a connection establishment failure (CEF) report.

9. The user equipment according to claim 6, wherein: When the report includes a random access channel (RACH) report, the LBT information includes a channel access scheme identifier, a number of LBT failures detected before the RACH attempt, an indication of resource selection due to LBT failure, a cell ID, a tracking area identifier (TAI), an NR-U random access channel (RACH) report identifier, a new radio (NR) RACH report identifier, a RACH failure cause value for LBT failure, or a combination thereof.

10. The user equipment according to claim 6, wherein: When the report includes a connection establishment failure (CEF) report, the LBT information includes a radio link failure (RLF)-cause, an RLF type, a number of persistent LBT failures, a BWP identifier for one or more BWPs, a BWP frequency for one or more BWPs, an interference type, a channel access scheme identifier, a cell ID, an indication of UL LBT failure, an indication of DL LBT failure, or a combination thereof.

Images