Configured grant channel occupancy time sharing procedure
Patent Information
- Application Number
- JP2022524690
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-11-08
- Filing Date
- 2020-11-05
- Publication Date
- 2025-03-04
- Estimated Expiration
- 2040-11-05
Smart Images

Figure 0007638982000001 
Figure 0007638982000002 
Figure 0007638982000003
Abstract
Description
Claiming priority
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of Indian Provisional Patent Application No. 201941045481, entitled "CONFIGURED GRANT CHANNEL OCCUPANCY TIME SHARING PROCEDURE," filed on November 8, 2019, which is expressly incorporated herein by reference in its entirety. [Technical field]
[0002] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to configured grant channel occupancy time (COT) sharing procedures. [Background technology]
[0003]
[0003] 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 available network resources. Such networks are typically multiple access networks, supporting communication for multiple users by sharing available network resources. One example of such a network is the Universal Terrestrial Radio Access Network (UTRAN). UTRAN is a radio access network (RAN) defined as part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP). Examples of multiple access network formats include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, and Single Carrier FDMA (SC-FDMA) networks.
[0004] A wireless communication network may include a number of base stations or Node Bs that can support communication for a number of user equipments (UEs). The UEs may communicate with the base stations via a downlink and an uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station.
[0005]
[0005] A base station may transmit data and control information on the downlink to a UE and / or receive data and control information on the uplink from a UE. On the downlink, a transmission from a base station may encounter interference from transmissions from neighbor base stations or from other wireless radio frequency (RF) transmitters. On the uplink, a transmission from a UE may encounter interference from uplink transmissions of other UEs communicating with neighbor base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and the uplink.
[0006]
[0006] As the demand for mobile broadband access continues to increase, more UEs access long-range wireless communication networks and more short-range wireless systems are deployed in the community, increasing the possibility of interference and congestion networks. Research and development continues to evolve wireless technologies not only to meet the increasing demand for mobile broadband access, but also to evolve and improve the user experience of mobile communication. Summary of the Invention
[0007]
[0007] In one aspect of the present disclosure, a method of wireless communication includes: obtaining, by a user equipment (UE), a channel occupation time (COT) in response to a detected success of the UE's listen-before-talk (LBT) procedure on a shared communication channel; determining, by the UE, one of enabled or not enabled COT sharing; identifying, by the UE, COT sharing information for communication to a serving base station in an uplink control message, wherein the COT sharing information is identified in response to the determination, and transmitting, by the UE, an uplink control message having the COT sharing information to the serving base station.
[0008]
[0008] In a further aspect of the present disclosure, an apparatus configured for wireless communications includes means for obtaining, by the UE, a COT in response to a detected success of the UE's LBT procedure on a shared communications channel; means for determining, by the UE, whether COT sharing is enabled or not enabled; means for identifying, by the UE, COT sharing information for communication to a serving base station in an uplink control message, wherein the COT sharing information is identified in response to the means for determining, and means for the UE to transmit an uplink control message having the COT sharing information to the serving base station.
[0009] In a further aspect of the disclosure, a non-transitory computer-readable medium having recorded thereon program code, the program code further including: code for, by the UE, obtaining a COT in response to a detected success of the UE's LBT procedure on the shared communications channel, code for determining, by the UE, whether COT sharing is enabled or not enabled, code for identifying, by the UE, COT sharing information for communication in an uplink control message to a serving base station, where the COT sharing information is identified in response to execution of the code for determining, and code for, by the UE, transmitting an uplink control message having the COT sharing information to the serving base station.
[0010]
[0010] In a further 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: obtain, by the UE, a COT in response to a detected success of the UE's LBT procedure on the shared communication channel; determine, by the UE, whether COT sharing is enabled or not enabled; identify, by the UE, COT sharing information for communication to a serving base station in an uplink control message; where the COT sharing information is identified in response to execution of the at least one processor's configuration for determining, and transmit, by the UE, an uplink control message having the COT sharing information to the serving base station.
[0011]
[0011] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims.
[0012]
[0012] A further understanding of the nature and advantages of the present disclosure may be realized by reference to the following drawings. In the accompanying figures, similar components or features may have the same reference numerals. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between those similar components. When only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of the second reference label. [Brief description of the drawings]
[0013] [Figure 1] 1 is a block diagram showing details of a wireless communication system. [Diagram 2]
[0014] 1 illustrates a block diagram showing a design of a base station and a UE configured according to one aspect of the present disclosure. [Diagram 3]
[0015] FIG. 1 is a block diagram illustrating example blocks that can be executed to implement an aspect of the present disclosure. [Figure 4]
[0016] 1 is a block diagram illustrating a communication interaction between a UE and a base station having channel occupation time (COT) sharing capability configured in accordance with one aspect of the present disclosure. [Diagram 5]
[0017] FIG. 1 is a block diagram illustrating a portion of an NR-U network including a UE and a base station having COT sharing capability configured in accordance with one aspect of the present disclosure. [Figure 6A]
[0018] 1 is a block diagram illustrating a UE and a base station having COT sharing capability configured in accordance with one aspect of the present disclosure. [Figure 6B] 1 is a block diagram illustrating a UE and a base station having COT sharing capability configured in accordance with one aspect of the present disclosure. [Figure 6C] 1 is a block diagram illustrating a UE and a base station having COT sharing capability configured in accordance with one aspect of the present disclosure. [Figure 7]
[0019] 1 is a block diagram illustrating an example UE configured in accordance with an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0014]
[0020] The detailed description set forth below with reference to the accompanying drawings describes various configurations and is not intended to limit the scope of the present disclosure. Rather, the detailed description includes specific details for the purpose of providing a thorough understanding of the subject matter of the present invention. Those skilled in the art will appreciate that these specific details are not required in every instance, and that in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.
[0015]
[0021] The present disclosure generally relates to providing or participating in authorized shared access between two or more wireless communication systems, also referred to as wireless communication networks. In various embodiments, the techniques and apparatus may be used for 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, Fifth Generation (5G) networks or New Radio (NR) networks, as well as other communication networks. The terms "network" and "system" described herein may be used interchangeably.
[0016]
[0022] OFDMA networks may implement radio technologies such as evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are parts of the universal mobile telecommunications system (UMTS). In particular, Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or are being developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between groups of telecommunications associations aimed at 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. This disclosure pertains to the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond, which involve shared access to the wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces.
[0017]
[0023] In particular, 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified air interface. To achieve these goals, further extensions of LTE and LTE-A are considered in addition to developing new radio technologies for 5G NR networks. 5G NR is a service area that offers: (1) ultra-high density (e.g., approximately 1 million nodes / km); 2 (2) coverage for large-scale Internet of Things (IoT) with ultra-low complexity (e.g., on the order of tens of bits per second), ultra-low energy (e.g., on the order of 10+ years battery life), and deep coverage with the ability to reach difficult locations; (3) coverage for large-scale Internet of Things (IoT) with strong security to protect sensitive personal, financial, or confidential information, ultra-high reliability (e.g., on the order of 99.9999% reliability), ultra-low latency (e.g., on the order of 1 ms), and users with or without wide range mobility; and (4) extremely high capacity (e.g., on the order of 10 Tbps / km). 2 ), with enhanced mobile broadband including extreme data rates (e.g., multi-Gbps rates, user experience rates of 100 Mbps or greater), and deep awareness for advanced discovery and optimization.
[0018]
[0024] 5G NR has a common flexible framework for efficiently multiplexing services and features with dynamic low latency time division duplexing (TDD) / frequency division duplexing (FDD) designs with scalable numerology and transmission time intervals (TTIs), and may be implemented to use optimized OFDM-based waveforms with advanced wireless technologies such as massive multiple input multiple output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of numerology in 5G NR with the scaling of subcarrier spacing may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of FDD / TDD implementations below 3 GHz, subcarrier spacing may occur at 15 kHz, for example, over bandwidths of 1, 5, 10, 20 MHz, etc. In other various outdoor and small cell coverage deployments of TDD greater than 3 GHz, subcarrier spacing may occur at 30 kHz over 80 / 100 MHz bandwidths. In various other indoor wideband implementations using TDD over the unlicensed portion of the 5 GHz band, the subcarrier spacing can be 60 kHz over a 160 MHz bandwidth. Finally, in various deployments transmitting with mmWave components at 28 GHz TDD, the subcarrier spacing can be 120 kHz over a 500 MHz bandwidth.
[0019]
[0025] 5G NR's scalable numerology facilitates scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, and longer TTIs for higher spectral efficiency. Efficient multiplexing of long and short TTIs to allow transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgements in the same subframe. The self-contained integrated subframe supports communication in unlicensed or contention-based shared spectrum, adaptive uplink / downlink that can be flexibly configured per cell to dynamically switch between uplink and downlink to meet current traffic needs.
[0020]
[0026] Various other aspects and features of the present disclosure are further described below. It will be apparent that the teachings herein can be implemented in a wide variety of forms, and that the specific structures, functions, or both disclosed herein are merely representative and not limiting. Based on the teachings herein, those skilled in the art will appreciate that the aspects disclosed herein can be implemented independently of other aspects, and that two or more of these aspects can be combined in various ways. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects described herein. Furthermore, such an apparatus can be implemented or such a method can be practiced using other structures, functions, or structures and functions in addition to or other than one or more of the aspects described herein. For example, a method can be implemented as part of a system, device, apparatus, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. Furthermore, an aspect can comprise at least one element of a claim.
[0021]
[0027] FIG. 1 is a block diagram illustrating an example of a wireless communication system 100 supporting configured grant (CG) channel occupation time (COT) sharing according to an aspect of the present disclosure. A UE, such as UE 115, sharing a COT may indicate in an uplink control indicator (UCI) message the remaining COT duration and an offset indication identifying where the uplink transmission is expected to end, and a channel access priority class (CAPC) that may be used by a base station, such as base station 105, to determine what type of data may be included in a downlink transmission in the shared COT. If an energy detection (ED) threshold is not configured for COT sharing, the UE 115 may reduce the information included in the UCI. The base station 112 is alternatively configurable as to which information the UE 115 includes in the UCI for potential COT sharing. COT sharing information may further be compressed by coding such information into a table or exploitation knowledge of transmission characteristics, such as a configured end point. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, a LTE-Advanced (LTE-A) network, a LTE-A Pro network, or a NR network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, or communications with low cost and low complexity devices.
[0022]
[0028] The base station 105 may wirelessly communicate with the UE 115 via one or more base station antennas. The base station 105 described herein may include or may be referred to by one skilled in the art as a base transceiver station, radio base station, access point, radio transceiver, Node B, eNode B (eNB), next generation Node B or giganode B (any of which may be referred to as gNB), Home Node B, Home eNode B, or some other suitable terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macro base stations or small cell base stations). The UE 115 described herein may be capable of communicating with various types of base stations 105 and network equipment, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.
[0023]
[0029] Each base station 105 may be associated with a particular geographic coverage area 110 in which communication with various UEs 115 is supported. Each base station 105 may provide communication coverage to the respective geographic coverage area 110 via a communication link 125, where the communication link 125 between the base station 105 and the UE 115 may use one or more carriers. The communication link 125 shown in the wireless communication system 100 may include uplink transmissions from the UE 115 to the base station 105 or downlink transmissions from the base station 105 to the UE 115. Downlink transmissions may be referred to as forward link transmissions, while uplink transmissions may be referred to as reverse link transmissions.
[0024]
[0030] A geographic coverage area 110 for a base station 105 may be divided into sectors constituting a portion of the geographic coverage area 110, and each sector may be associated with a cell. For example, each base station 105 may provide communication coverage for a macro cell, a small cell, a hot spot, or other type of cell, or various combinations thereof. In some examples, the base station 105 may be mobile and thus provide communication coverage for a moving geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, and overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or by different base stations 105. The wireless communication system 100 may include a heterogeneous LTE / LTE-A / LTE-A Pro or NR network, for example, in which different types of base stations 105 provide coverage for various geographic coverage areas 110.
[0025]
[0031] The term "cell" refers to a logical communication entity used for communication with a base station 105 (e.g., on a carrier) and may be associated with an identifier (e.g., physical cell identifier (PCID), virtual cell identifier (VCID)) to distinguish neighboring cells operating over the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), etc.) that may provide access to different types of devices. In some cases, the term "cell" may refer to a portion (e.g., a sector) of a geographic coverage area 110 over which a logical entity operates.
[0026]
[0032] The UEs 115 may be distributed throughout the wireless communication system 100, and each UE 115 may be fixed or mobile. The UEs 115 may be referred to as mobile devices, wireless devices, remote devices, handheld devices, or subscriber devices, or some other suitable terminology, where a "device" may also be referred to as a unit, station, terminal, or client. The UEs 115 may also be personal electronic devices, such as a cellular phone (UE115a), a personal digital assistant (PDA), a wearable device (UE115d), a tablet computer, a laptop computer (UE115g), or a personal computer. In some examples, the UEs 115 may also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, which may be implemented in various articles, such as an appliance, a vehicle (UE115e and UE115f), a meter (UE115b and UE115c), or the like.
[0027]
[0033] Some UEs 115, such as MTC devices or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that incorporate sensors or meters to measure or capture information and relay that information to a central server or application program that can utilize the information or present the information to a human interacting with the program or application. Some UEs 115 may be designed to collect information or enable automated operation of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.
[0028]
[0034] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception, rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power conservation techniques for the UE 115 include entering a power-saving "deep sleep" mode when not engaged in active communication, or operating on a limited bandwidth (e.g., pursuant to narrowband communication). In other cases, the UE 115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communication for these functions.
[0029]
[0035] In some cases, the UE 115 may also be able to communicate directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more of a group of UEs 115 using D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or may not otherwise be able to receive transmissions from the base station 105. In some cases, a group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to every other UE 115 in the group. In some cases, the base station 105 may facilitate scheduling of resources for D2D communication. In other examples, D2D communication may be performed between UEs 115 without the involvement of the base station 105.
[0030]
[0036] The base stations 105 may communicate with the core network 130 and with each other. For example, the base stations 105 may interface with the core network 130 through backhaul links 132 (e.g., via an S1, N2, N3, or other interface). The base stations 105 may communicate with each other over backhaul links 134 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130).
[0031]
[0037] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) that may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the EPC. User IP packets may be forwarded through the S-GW, which may itself be connected to a P-GW. The P-GW may provide IP address allocation as well as other functions. The P-GW may be connected to network operator IP services. The operator IP services may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet-switched (PS) streaming services.
[0032]
[0038] At least some of the network devices, such as the base stations 105, may include subcomponents, such as access network entities, which may be an example of an access node controller (ANC). Each access network entity may communicate with the UE 115 through some other access network transmission entity, which may be referred to as a radio head, a smart radio head, or a transmit / receive point (TRP). In some configurations, various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or integrated into a single network device (e.g., the base station 105).
[0033]
[0039] The wireless communication system 100 may operate using one or more frequency bands typically ranging from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the 300 MHz to 3 GHz region is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately 1 decimeter to 1 meter in length. UHF waves may be blocked or redirected by buildings and environmental features. However, the waves may penetrate structures sufficiently for a macrocell to serve UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0034]
[0040] The wireless communication system 100 may also operate in the very high frequency (SHF) region using the 3 GHz to 30 GHz frequency band, also known as the centimeter band. The SHF region includes bands such as the 5 GHz Industrial, Scientific and Medical (ISM) band that may be used opportunistically by devices that may be able to tolerate interference from other users.
[0035]
[0041] The wireless communication system 100 may also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, where the EHF antennas of the respective devices may be smaller and more closely spaced than the UHF antennas. In some cases, this may facilitate the use of antenna arrays in the UE 115. However, propagation of EHF transmissions may be subject to greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of bands across these frequency regions may vary by country or regulatory body.
[0036]
[0042] The wireless communication system 100 may include operation by different network operating entities (e.g., network operators) with which each network operator may share spectrum. In some instances, a network operating entity may be configured to use its entire designated shared spectrum for at least a period of time before another network operating entity uses its entire designated shared spectrum for a different period of time. Thus, to enable a network operating entity to use all of the designated shared spectrum and to mitigate interference in communications between different network operating entities, certain resources (e.g., time) may be partitioned and allocated to different network operating entities for certain types of communications.
[0037]
[0043] For example, a network operating entity may be allocated certain time resources reserved for exclusive communication by the network operating entity using the entirety of the shared spectrum. The network operating entity may be allocated other time resources where priority is given to other network operating entities for the entity to communicate using the shared spectrum. These time resources that are prioritized for use by that network operating entity may be utilized by other network operating entities on an opportunistic basis if the prioritized network operating entity does not utilize those resources. Additional time resources may be allocated to any network operator for use on an opportunistic basis.
[0038]
[0044] Access to the shared spectrum and arbitration of time resources between different network operating entities may be centrally controlled by separate entities, may be autonomously determined by predefined arbitration schemes, or may be dynamically determined based on interactions between wireless nodes of the network operators.
[0039]
[0045] In various implementations, the wireless communication system 100 may use both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ license-assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (NR-U), such as the 5 GHz ISM band. In some cases, the UE 115 and base station 105 of the wireless communication system 100 may operate in a shared radio frequency spectrum band, which may include licensed frequency spectrum or unlicensed (e.g., contention-based) frequency spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or base station 105 may conventionally perform a medium sensing procedure to compete for access to the frequency spectrum. For example, the UE 115 or base station 105 may perform a listen-before-talk (LBT) procedure, such as clear channel assessment (CCA), prior to communication to determine whether a shared channel is available.
[0040]
[0046] CCA may include an energy detection procedure to determine whether there are other active transmissions on the shared channel. For example, a device may infer that a change in the received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. In particular, signal power concentrated in a certain bandwidth and above a predetermined noise floor may indicate another wireless transmitter. CCA may also include message detection of a particular sequence that indicates channel usage. For example, another device may transmit a particular preamble prior to transmitting a data sequence. In some cases, the LBT procedure may include a 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 its own transmitted packets as a proxy for collisions.
[0041]
[0047] In general, four categories of LBT procedures for sensing a shared channel for signals that may indicate that the channel is already occupied are suggested. In the first category (CAT1 LBT), no LBT or CCA is applied to detect occupancy of the shared channel. The second category (CAT2 LBT), sometimes called shortened LBT, single-shot LBT, or 25μs LBT, provides for nodes to perform CCA to detect energy above a predefined threshold or to detect messages or preambles occupying the shared channel. CAT2 LBT performs CCA without using a random backoff operation, which results in its shortened length for the following categories:
[0042]
[0048] The third category (CAT3 LBT) performs CCA to detect energy or messages on the shared channel, but still uses a random backoff and a fixed contention window. Thus, when a node starts CAT3 LBT, it performs a first CCA to detect occupancy of the shared channel. If the shared channel is idle for the duration of the first CCA, the node can proceed to transmit. However, if the first CCA detects a signal occupying the shared channel, the node selects a random backoff based on the fixed contention window size and performs an extended CCA. If the shared channel is detected to be idle during the extended CCA and the random number is decremented to 0, the node may start transmitting on the shared channel. Otherwise, the node decrements the random number and performs another extended CCA. The node will continue to perform the extended CCA until the random number reaches 0. If the random number reaches 0 without any of the extended CCAs detecting channel occupancy, the node may transmit on the shared channel. In any of the extended CCAs, if a node detects channel occupancy, it may reselect a new random backoff based on a fixed contention window size to start the countdown again.
[0043]
[0049] The fourth category (CAT4 LBT), sometimes called the full LBT procedure, performs CCA with energy or message detection using random backoff and a variable contention window size. Except that the contention window size for the CAT4 LBT procedure is variable, the sequence of CCA detection proceeds similarly to the process of CAT3 LBT.
[0044]
[0050] The use of medium sensing procedures to compete for access to an unlicensed shared spectrum may result in communication failure. This may be particularly evident when multiple network operating entities (e.g., network operators) are attempting to access the shared resources. Within the wireless communication system 100, the base stations 105 and UEs 115 may be operated by the same or different network operating entities. In some examples, an individual base station 105 or UE 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity. Requiring each base station 105 and UE 115 of different network operating entities to compete for the shared resources may result in increased signaling overhead and communication latency.
[0045]
[0051] In some cases, operation in the unlicensed spectrum may be based on a carrier aggregation configuration with component carriers operating in a licensed spectrum (e.g., LAA). Operation in the unlicensed spectrum may include downlink transmission, uplink transmission, peer-to-peer transmission, or a combination thereof. Duplexing in the unlicensed spectrum may be based on Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination of both.
[0046]
[0052] In some examples, the base station 105 or UE 115 may be equipped with multiple antennas that may be used to utilize techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. For example, the wireless communications system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communications may employ multipath signal propagation, sometimes referred to as spatial multiplexing, to increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. The multiple signals may be transmitted by a transmitting device, for example, via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits related to the same data stream (e.g., the same codeword) or different data streams. The different spatial layers may be associated with different antenna ports used for channel measurements and reporting. MIMO techniques include Single-User MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and Multi-User MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.
[0047]
[0053] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting or receiving device (e.g., base station 105 or UE 115) to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated through antenna elements of an antenna array such that signals propagating in a particular orientation relative to the antenna array experience constructive interference and others experience destructive interference. Adjustment of signals communicated through antenna elements may include the transmitting or receiving device applying a particular amplitude and phase offset to signals carried through each of the antenna elements associated with the device. The adjustment associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or to some other orientation).
[0048]
[0054] In one example, the base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with the UE 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by the base station 105 multiple times in different directions, which may include the signals being transmitted according to different beamforming weight sets associated with different directions of transmission. The transmissions in the different beam directions may be used to identify beam directions (e.g., by the base station 105, or a receiving device such as the UE 115) for subsequent transmission and / or reception by the base station 105.
[0049]
[0055] Some signals, such as data signals associated with a particular receiving device, may be transmitted by the base station 105 in a single beam direction (e.g., a direction associated with a receiving device, such as the UE 115). In some examples, the beam direction associated with a transmission along the single beam direction may be determined based at least in part on signals transmitted in different beam directions. For example, the UE 115 may receive one or more of the signals transmitted by the base station 105 in different directions, and the UE 115 may report to the base station 105 an indication of the signal it received with the best signal quality or an otherwise acceptable signal quality. Although these techniques have been described with respect to signals transmitted by the base station 105 in one or more directions, the UE 115 may employ similar techniques to transmit a signal multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or transmit a signal in a single direction (e.g., to transmit data to a receiving device).
[0050]
[0056] A receiving device (e.g., a UE 115, which may be an example of a mmW receiving device) may attempt multiple receive beams when receiving various signals from the base station 105, such as a synchronization signal, a reference signal, a beam selection signal, or other control signals. For example, the receiving device may attempt multiple receive directions, any of which may be referred to as "listening" according to different receive beams or receive directions, by receiving via various antenna subarrays, by processing the receive signals according to various antenna subarrays, by receiving according to various receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, or by processing the receive signals according to various receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array. In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal). The single receive beam may be aligned in a beam direction determined at least in part based on listening according to different receive beam directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality, based at least in part on listening according to multiple beam directions).
[0051]
[0057] In certain implementations, the antennas of the base station 105 or the UE 115 may be located in one or more antenna arrays that may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located in an antenna assembly such as an antenna tower. In some cases, antennas or antenna arrays associated with the base station 105 may be located in various geographic locations. The base station 105 may have an antenna array with several rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
[0052]
[0058] In further cases, the UE 115 and the base station 105 may support retransmission of data to increase the likelihood of successful reception of the data. HARQ feedback is one technique that increases the likelihood that data is accurately received on the communication link 125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., signal-to-noise conditions). In some cases, a wireless device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a particular slot for data received in a previous symbol in that slot, and in other cases the device may provide HARQ feedback in a subsequent slot or according to some other time interval.
[0053]
[0059] A time interval in LTE or NR is, for example, T sThe communication resource time intervals may be organized according to radio frames, each having a duration of 10 milliseconds (ms), where the frame period is T f =307,200T s A radio frame may be represented as: SFN = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 109, 108, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121,
[0054]
[0060] In some wireless communication systems, a slot may be further divided into multiple minislots containing one or more symbols. In some instances, a minislot's symbol or minislot may be the smallest unit of scheduling. Each symbol may vary in duration depending, for example, on the subcarrier spacing or frequency band of operation. Additionally, some wireless communication systems may implement slot aggregation, in which multiple slots or minislots are aggregated together and used for communication between the UE 115 and the base station 105.
[0055]
[0061] The term "carrier" as used herein refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over the communication link 125. For example, a carrier of the communication link 125 may include a portion of a radio frequency spectrum band operated according to a physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. A carrier may be associated with a predefined frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be arranged according to a channel raster for discovery by the UE 115. A carrier may be downlink or uplink (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode). In some examples, a signal waveform transmitted over a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)).
[0056]
[0062] The organizational structure of carriers may differ for different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR). For example, communications over carriers may be organized according to TTIs or slots, each of which may include user data as well as control information or signaling to support decoding the user data. Carriers may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling that coordinates the operation of the carriers. In some examples (e.g., in carrier aggregation configurations), carriers may also have acquisition or control signaling that coordinates the operation of other carriers.
[0057]
[0063] The physical channels may be multiplexed on the carriers according to various techniques. The physical control channel and the physical data channel may be multiplexed on the downlink carriers, for example, using a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. In some examples, the control information transmitted in the physical control channel may be distributed among different control regions in a cascaded manner (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).
[0058]
[0064] A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of several predefined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) for a carrier of a particular radio access technology. In some examples, each served UE 115 may be configured to operate on a portion or all of the carrier bandwidth. In other examples, some UEs 115 may be configured for operation using a narrowband protocol type associated with a predefined portion or range (e.g., a set of subcarriers or RBs) within the carrier (e.g., an “in-band” deployment of a narrowband protocol type).
[0059]
[0065] In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Thus, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate for the UE 115 may be. In a MIMO system, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers may further increase the data rate for communication with the UE 115.
[0060]
[0066] A device (e.g., a base station 105 or a UE 115) of the wireless communication system 100 may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 and / or a UE 115 that supports simultaneous communication over carriers associated with two or more different carrier bandwidths.
[0061]
[0067] The wireless communications system 100 may support communication with the UE 115 over multiple cells or carriers, a feature sometimes referred to as carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both FDD and TDD component carriers.
[0062]
[0068] In some cases, the wireless communication system 100 may use an enhanced component carrier (eCC). An eCC may be characterized by one or more features including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some instances, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). An eCC may also be configured for use in an unlicensed or shared spectrum (e.g., when two or more operators are authorized to use the spectrum, such as NR shared spectrum (NR-SS)). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be utilized by a UE 115 that is not capable of monitoring the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., to conserve power).
[0063]
[0069] In further cases, the eCC may utilize a different symbol duration than other component carriers, which may include the use of a reduced symbol duration compared to the symbol duration of other component carriers. The shorter symbol duration may be associated with an increased spacing between adjacent subcarriers. A device such as a UE 115 or base station 105 utilizing the eCC may transmit a wideband signal (e.g., according to a frequency channel or carrier bandwidth of 20, 40, 60, 80 MHz, etc.) at a reduced symbol duration (e.g., 16.67 microseconds). A TTI in an eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in a TTI) may be variable.
[0064]
[0070] The wireless communication system 100 may be, among other things, an NR system that may utilize any combination of licensed, shared, and unlicensed spectrum bands. Flexibility in eCC symbol duration and subcarrier spacing may enable the use of eCC across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectral efficiency, particularly through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) sharing of resources.
[0065]
[0071] FIG. 2 shows a block diagram of a design of a base station 105, which may be one of the base stations in FIG. 1, and a UE 115, which may be one of the UEs in FIG. 1. At the base station 105, a transmit processor 220 may receive data from a data source 212 and control information from a controller / processor 240. The control information may be for a PBCH, a PCFICH, a PHICH, a PDCCH, an EPDCCH, an MPDCCH, etc. The data may be for a PDSCH, etc. The transmit processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signals. A 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-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 further process (e.g., convert to analog, amplify, filter, and 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.
[0066]
[0072] At the UE 115, the antennas 252a-252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a-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 all demodulators 254a-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 and provide decoded data for the UE 115 to a data sink 260 and provide decoded control information to the controller / processor 280.
[0067]
[0073] On the uplink, at the UE 115, a transmit processor 264 may receive and process data (e.g., for a PUSCH) from a data source 262 and control information (e.g., for a PUCCH) from a controller / processor 280. 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-254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, uplink signals from the UE 115 may be received by antennas 234, processed by a demodulator 232, detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 115. The processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller / processor 240.
[0068]
[0074] The controllers / processors 240 and 280 may direct 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 may perform or direct the execution of various processes for the techniques described herein. The controller / processor 280 and / or other processors and modules at the UE 115 may also perform or direct the execution of the functional blocks shown in FIG. 3 and / or other processes for the techniques described herein. The memories 242 and 282 may store data and program codes for the base station 105 and the UE 115, respectively. The scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.
[0069]
[0075] In NR-U operation, channel occupation time (COT) sharing is considered in the context of configured grant (CG) resources. Each CG resource may include a periodic uplink resource and may be associated with a set of hybrid automatic repeat request (HARQ) identities. Before each uplink transmission in the CG resource, the UE may perform a Cat-4 LBT to ensure access to the shared communication channel. After the LBT is successful, the UE may transmit multiple uplink transmissions without any transmission gaps until the end of the COT (e.g., PUSCH). The COT acquired by the UE may be shared with the serving base station to transmit or broadcast control or data transmissions to the UE. COT sharing may be useful when the UE does not perform uplink transmissions for the entire COT duration. The serving base station may share the COT by performing any shortened LBT (e.g., Cat-2 LBT) or without performing an LBT procedure. To enable COT sharing, the UE may provide COT sharing information in an uplink control indicator (UCI) message regarding the acquired COT. Various aspects of the present disclosure relate to identifying and using such CG-UCI information for COT sharing and performing CG UL transmission in a manner that enables a serving base station to perform a shortened LBT.
[0070]
[0076] FIG. 3 is a block diagram illustrating example blocks that may be performed to implement an aspect of the present disclosure. The example blocks are also described with respect to the UE 115 as shown in FIG. 2 and FIG. 7. FIG. 7 is a block diagram illustrating the UE 115 configured according to an aspect of the present disclosure. The UE 115 includes the structure, hardware, and components as shown for the UE 115 in FIG. 2. For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in memory 282, as well as controls the components of the UE 115 that provide the features and functionality of the UE 115. The UE 115 transmits and receives signals via wireless radios 700a-r and antennas 252a-r under the control of the controller / processor 280. The wireless radios 700a-r include various components and hardware, including the modulator / demodulators 254a-r, the MIMO detector 256, the receive processor 258, the transmit processor 264, and the TX MIMO processor 266, as shown in FIG. 2 for the UE 115.
[0071]
[0077] In block 300, the UE obtains the COT in response to a detected success of the UE's LBT procedure on the shared communications channel. A UE, such as UE 115, obtains configured grant configuration information and stores it in memory 282 in configured grant configuration 701. The UE 115 may receive such configured grant configuration information from a configuration signal by a serving base station via antennas 252a-r and wireless radios 700a-r. The configured grant configuration 701 provides the UE 115 with an identity, start point, end point, etc. of resources for the UE 115 to transmit uplink data without a scheduled grant when the uplink data is present in a data buffer 706 in memory 282. With knowledge of the configured grant uplink resources on the shared communications spectrum, the UE 115 may attempt to secure the COT by executing the LBT logic 702 in memory 282. Under the control of the controller / processor 280, the UE 115 executes the LBT logic 702, resulting in instructions and control for the various components of the UE 115, as described in more detail in FIG. 2, in addition to the wireless radios 700a-r and antennas 252a-r. When executing the LBT logic 702, an environment ("execution environment") is created within the UE 115 in executing instructions and controlling various hardware and components, the UE 115 may monitor the common communications channel via the antennas 252a-r and wireless radios 700a-r to detect an energy level on the shared communications channel. If no energy level above an energy detection (ED) threshold is detected, the UE 115 may detect, within the execution environment of the LBT logic 702, a successful LBT procedure. Upon detection of a successful LBT procedure, the UE 115 acquires a COT on the shared communications channel.
[0072]
[0078] In block 301, the UE determines whether COT sharing is enabled or not enabled. To support COT sharing, the UE 115 executes the COT sharing logic 703 stored in the memory 282 under the control of the controller / processor 280. The execution environment of the COT sharing logic 703 provides the UE 115 with the functionality and control of various hardware and components to determine whether COT sharing is enabled and, if enabled, to monitor the transmission of the UE-initiated COT to share with the serving base station when the UE 115 would not transmit over the entire COT. In one exemplary aspect, within the execution environment of the COT sharing logic 703, the UE 115 may detect whether an ED threshold for the LBT procedure used according to the LBT logic 702 to obtain the COT is configured by the serving base station for COT sharing. If not, the UE 115 may determine that COT sharing is not enabled. If, instead, the ED threshold is configured by the serving base station for COT sharing, the UE 115 may determine that COT sharing is enabled. In a further aspect, the execution environment of the COT sharing logic 703 may operate to prompt the UE 115 to detect configuration information received from the serving base station via the antennas 252a-r and the wireless radios 700a-r that configures what COT sharing information should be included in uplink control messages to the serving base station or that configures the COT sharing as either enabled or not enabled. Based on these additional serving base station configurations, the UE 115 will determine whether COT sharing is enabled or not.
[0073]
[0079] In block 302, the UE identifies COT sharing information to communicate to the serving base station in an uplink control message, where the COT sharing information is identified in response to the determination. The COT sharing information 704 stored in the memory 282 may be identified as the specific COT sharing information to be shared between the UE 115 and the serving base station depending on whether COT sharing is enabled. The COT sharing information 704 may include a remaining COT duration or a COT end point that indicates to the serving base station how long the downlink transmission may be performed, an offset indication that indicates where the UE transmission is expected to end or at what time instance the base station may perform a shortened LBT, and a channel access priority class (CAPC) used by the UE for COT acquisition. The CAPC allows the serving base station to determine what type of data may be included in its downlink communication in the shared COT. When the UE 115 determines that COT sharing is enabled, the UE 115 may include all of this COT sharing information in the uplink control message. Additionally, the COT sharing information 704 may be coded or compressed to reduce the signaling overhead of the information for inclusion in the uplink control message. When the UE 115 determines that COT sharing is not enabled, the UE 115 may identify some of this COT sharing information for removal from the uplink control message. For example, when not enabled for COT sharing, the UE 115 will not identify CAPC and possibly other COT sharing information for inclusion in the uplink control message. Once the COT sharing information is identified, based on whether COT sharing is enabled or not, the UE 115 executes the UCI generator 705 in the memory 282 under the control of the controller / processor 280. Execution of the UCI generator 705 provides the UE 115 with functionality and instructions for generating an uplink control message including the identified COT sharing information.
[0074]
[0080] In block 303, the UE transmits an uplink control message with the COT sharing information to the serving base station. Once the uplink control message is generated and includes the identified COT sharing information through execution of the UCI generator 705, the UE 115, under control of the controller / processor 280, may transmit the uplink control message via the wireless radios 700a-r and the antennas 252a-r to the serving base station.
[0075]
[0081] 4 is a block diagram illustrating a communication interaction between a UE 115a and a base station 105 having a COT sharing capability configured according to one aspect of the disclosure. The UE 115a receives various configuration information 405 from the base station 105. The base station 105 may provide an indication of configured grant resources available to the UE 115a in the shared communications channel. To attempt to access the shared communications channel, the UE 115a performs a Cat-4 LBT 400. If successful, the UE 115a obtains a COT 401 for an uplink transmission 402.
[0076]
[0082] It has been suggested that COT sharing may be influenced based on the value of an energy detection (ED) threshold configured by the base station. The ED threshold applied by the UE 115a when performing a Cat-4 LBT 400 to obtain a COT 401 that may be shared with a serving base station, such as the base station 105, is configured by the base station 105 via configuration information 405, such as via RRC signaling, etc. The base station 105 may either configure an ED threshold for COT sharing, configure a standard ED threshold that does not cover COT sharing, or simply not configure an ED threshold for COT sharing. If not configured, the UE 115a defaults to using a standard ED threshold that does not cover COT sharing when performing a Cat-4 LBT 400 procedure to ensure a COT 401 on a shared communications channel.
[0077]
[0083] When the ED threshold is not configured for COT sharing, when the UE 115a stops uplink transmission 402 before the end 404 of the COT 401, the base station 105 may still perform downlink transmission 407 within the remaining COT duration 403. However, in such a scenario, the downlink transmission 407 of the base station 105 within the UE-initiated COT 401 may be limited to control signal, broadcast signal, or control channel transmission or broadcast channel transmission of up to 2, 4, or 8 OFDM symbols in duration for subcarrier spacing of 15 kHz, 30 kHz, or 60 kHz subcarrier spacing (SCS), respectively. In such a scenario, when COT sharing is not enabled, some of the COT sharing information provided in the uplink control indicator (UCI) message 406 may be redundant (e.g., CAPC duration, COT duration, etc.). Furthermore, in some cases, the base station 105 may not be interested in COT sharing. Thus, the UE 115a may determine, based on the configuration information 405 from the base station 105, which fields of the COT shared information may be included in the UCI 406.
[0078]
[0084] According to one aspect of the disclosure, the COT sharing information to be included in the configured grant uplink control message, UCI 406, may depend on whether the COT Shared ED threshold is configured. When the COT Shared ED threshold is not configured, the UE 115a may suspend or remove the CAPC and reduce the bandwidth of the remaining COT duration in the UCI 406. In one example implementation, the UE 115a may remove the COT duration field entirely. However, the UE 115a should still ensure that there is enough space in the COT 401 to allow the serving base station to send a downlink transmission 407 by limiting its uplink transmission 402. In another example implementation, the UE 115a may include in the UCI 406 a one-bit value indicating whether the base station 105 is enabled to transmit or broadcast control or data signaling using the COT 401 acquired by the UE 115a. This may be determined based on whether the remaining COT duration 403 is sufficient for a broadcast or control transmission. In another example implementation, the UE 115a may include a number of symbols available for broadcast or control transmission within the COT 401 obtained by the UE 115a using the UCI 406. This number may be based on a reference numerology (e.g., the highest SCS supported by the UE 115a, or 60 kHz, or the SCS of an active BWP).
[0079]
[0085] According to another aspect of the disclosure, the base station 105 may directly configure the UE 115a with which fields to include in the UCI 406. For example, the base station 105 may indicate in the configuration information 405 whether to include CAPC and may also indicate the granularity of the remaining COT duration 403. Based on such information, the UE 115 may determine whether COT sharing is enabled by the base station 105. For example, if CAPC and the remaining COT duration 403 or the COT end 404 are omitted from the uplink control message (e.g., the UCI 406), the UE 115a may assume that COT sharing is disabled. In such a case, the UE 115a will use the standard ED thresholds not configured for sharing instead of the COT sharing ED thresholds.
[0080]
[0086] According to another aspect of the disclosure, the serving base station, base station 105, may directly configure UE 115a whether COT sharing is enabled or not via configuration information 405. Based on this enabling configuration, UE 115a may determine which COT sharing information fields should be included in UCI 406. When base station 105 configures COT sharing enabled in configuration information 405, UE 115a may use the COT sharing ED threshold, but when base station 105 configures COT sharing as not enabled in configuration information 405, UE 115a may use the standard ED threshold instead of the COT sharing ED threshold.
[0081]
[0087] The UE 115a may start the configured grant transmission, uplink transmission 402, in a slot, such as based on the minislot configuration and the addition of a cyclic prefix (CP). Thus, the time instance of the COT end 404 may also use the same granularity as the PUSCH transmission start point. This may result in a higher signaling overhead for the remaining COT duration field if the number of PUSCH start points is large in a slot. Similarly, the UE 115a may end the configured grant transmission, uplink transmission 402, in any symbol in a slot if the COT end 404 occurs in a given symbol in the slot. Thus, the number of COT shared information bits may be large even to indicate a transmission end offset value in the UCI 406. Further aspects of the present disclosure relate to compressing this type of COT shared information.
[0082]
[0088] In one aspect of the disclosure, the UE 115a may reduce the signaling of the remaining COT duration 403 and the remaining transmission time in the UCI 406. Since the transmission end time will occur earlier than the COT end 404, the UE 115a may jointly code and compress this information in the UCI 406. Similarly, the CAPC may also be jointly compressed when the transmission end point is affected based on the selected CAPC value. For different CAPCs, the COT duration may be different. For greater flexibility, a resource indicator value (RIV) table may be used to compress the signaling information for the transmission end time, the end of the COT, and the CAPC. Each entry in the RIV table may provide a combination of CAPC, remaining transmission time, and remaining COT duration. Each of the UE 115a and the base station 105 has a copy of this RIV table. The RIV table may further use slot granularity, multiple symbols, or minislot level. To further compress the remaining transmission time signaling, the signaling may take advantage of the fact that uplink transmission ends at a PUSCH end boundary configured by the base station 105 in the configuration information 405. The remaining COT duration 403 signaling may also be compressed by taking advantage of the fact that the PUSCH start location is restricted by the base station configuration. For example, the RIV table entry may have the granularity of the PUSCH slot end boundary and the PUSCH start point for the remaining transmission time and remaining COT duration, respectively. The UE 115a will include an index to the RIV table associated with the desired entry and a collection of COT sharing information for inclusion in the UCI 406.
[0083]
[0089] In another aspect of the disclosure, the transmission end point and remaining COT duration may be coded together by using a start-length indicator value (SLIV) approach. In a first exemplary implementation, the SLIV start and length values may have the granularity of the PUSCH end point and PUSCH start point configured by the base station 105, respectively. In a second exemplary implementation, the SLIV table may provide the end offset and remaining COT duration with a coarser granularity, with both start and length values provided in order on a slot, or with the start value having the granularity of the PUSCH transmission end point configured by the base station 105 in the configuration information 405 and the length value having the granularity of a slot, or with the start value having the granularity of a slot and the length value having the granularity of a PUSCH start point, etc. If no other information is provided, the base station 105 may operate with approximations. Again, the UE 115 will include in the UCI 406 an index to the SLIV table that points to the desired set of start-length indicator values. The base station 105 will use the received index to identify the correct entry in the SLIV table at the base station 105 .
[0084]
[0090] Note that further aspects of the disclosure may provide for the UE 115a to include additional COT shared information fields in the UCI 406 to make corrections to the values indicated by the SLIV table. For example, the exact transmission end point within a slot may be indicated in a separate field in the UCI 406, within which the bandwidth may be determined based on the PUSCH transmission end point allowed within the slot. In addition, the exact COT end 404 within a slot may be indicated based on the granularity of the PUSCH transmission start point.
[0085]
[0091] Further aspects of the disclosure relate to compressing both the transmission end point and the remaining COT duration 403 individually. The COT duration bit width may be derived based on the PUSCH starting point granularity. For example, the UE 115a may indicate the number of slots left in addition to the ending symbol in the slot in the UCI 406, whose bit width may be based on the minislot starting point configured by the base station 105 in the configuration information 405. The offset indicator identifying the end of the uplink transmission 402 may also be compressed, such as by enabling the UE 115a to end its transmission at the base station configured PUSCH ending point. In such an aspect, the UE 115a would indicate the ending slot number and ending symbol in the slot in the UCI 406, whose bit width may be based on the PUSCH ending point configured by the base station 105 in the configuration information 405. In additional example implementations, the UE 115a may be enabled to end its uplink transmission 402 either at the slot end or within the slot when the COT end 404 falls within the slot. The UE 115a may indicate this end in the number of the slot, and the base station may assume a slot boundary end if the end occurs before the COT end 404. Otherwise, the base station 105 may determine the end symbol based on the remaining COT duration 403.
[0086]
[0092] 5 is a block diagram illustrating a portion of an NR-U network 50 including a UE 115a and a base station 105 having COT sharing capability configured according to one aspect of the disclosure. In a further aspect of the disclosure, the UE 115a may be configured to signal COT sharing information at a fixed location before the end of the uplink transmission. For example, the UE 115a may signal COT sharing information in a UCI message in a PUSCH transmission that occurs in two slots, SN-1 and SN, before the end point 503 of the uplink transmission. Thus, if the UE 115a uses 10 slots for its uplink transmission in the COT 500, the first 8 slots may include a UCI that does not indicate any COT sharing (e.g., COT duration remaining=0), and in the last two slots, SN-1 and SN, the UE 115a may include a UCI that indicates COT sharing information and that COT sharing will occur after a certain number of slots or after the current slot, respectively. The end point 503 of the uplink transmission will be calculated from these last two slots, SN-1 and SN, and therefore the number of bits used for such indication may be significantly reduced. For example, if UE 115a has reported UCI indicating COT sharing from the first slot S0, the length to end point 503 is 505, and indicating COT sharing in the last two slots, SN-1 and SN, represents lengths 501 and 502, respectively, which are significantly shorter than length 505. This method may be used to reduce the bit width for indicating remaining COT duration signaling.
[0087]
[0093] Note that this method of reducing the bit-width of certain COT shared information may imply blind decoding from the network, since the base station 105 does not know the specific format of the UCI used by the UE 115a for a given slot.
[0088]
[0094] When an opportunity to share a UE-initiated COT occurs, the serving base station may perform an abbreviated LBT procedure (e.g., 25 μs or 16 μs Cat-2 LBT) or no LBT before starting downlink transmission. Which LBT the base station performs may be determined based on the LBT capabilities supported by the base station. For either LBT type, the UE will know to provide a sufficient gap between the end of the uplink transmission and the end of the COT for the base station to perform the appropriate LBT procedure. For example, for a 25 μs Cat-2 LBT, the UE will end its uplink transmission at least 25 μs before a slot or minislot boundary.
[0089]
[0095] 6A-6C are block diagrams illustrating a UE 115a and a base station 105 having a COT sharing capability configured according to an aspect of the disclosure. The UE 115a successfully performs a Cat-4 LBT 600 to obtain a COT 601 in the shared communication channel until the COT end 605. When the UE 115a ends an uplink transmission 602 earlier than a slot or minislot boundary or a PUSCH boundary, the UE 115a may determine a transmission block (TB) size 603 in a number of ways. For example, as shown in FIG. 6A, the TB size 603 may be selected based on an original end point 604, such as a configured PUSCH boundary, by performing rate matching based on a pulled-in end point 608. The "pulled-in" end point 608 represents an end point selected by the UE 115a to provide the base station 105 with enough time to perform a base station LBT procedure. The gap 606 between the original end point 604 and the next available downlink opportunity (not shown) is insufficient for the base station 105 to perform an abbreviated LBT procedure, which prompts the UE 115a to pull the end point of the uplink transmission 602 to within the pull-in end point 608. An additional time gap 607 in addition to the gap 606 provides the base station 105 with enough time to perform its LBT procedure for the downlink transmission.
[0090]
[0096] In a second example implementation shown in Figure 6B, the TB size 603 may be selected based on the original end point 604 by performing rate matching based on the original end point 604 and puncturing the remaining symbols 609 (between the pull-in end point 608 and the original end point 604) for the base station 105 to perform its LBT procedure. In a third example implementation shown in Figure 6C, the TB size 610 may be selected based on the pull-in end point 608 by performing rate matching based on the pull-in end point 608.
[0091]
[0097] In further aspects, grant UCI multiplexing may be performed regardless of the actual number of symbols used for uplink transmission, either assuming a small number of symbols are used for uplink transmission, assuming the actual number of symbols are used for uplink transmission, or assuming a larger number of symbols are used for uplink transmission.
[0092]
[0098] Alternatively, the base station may configure multiple configurations with different end points. The UE may then select one of the configurations and report its selection in the UCI message. In one exemplary implementation of base station configuration, the UE selects all slots with all symbols (0 to 13). In another exemplary implementation of base station configuration, the UE may select all slots with symbols 0 to 12 in all slots. In a further exemplary implementation of base station configuration, the UE selects slots 0 to N-1 with all symbols, with slot N comprising symbols 0 to 12 (where N is the last transmission slot used by the UE for uplink transmission).
[0093]
[0099] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0094]
[0100] The functional blocks and modules of FIG. 3 may comprise processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software code, firmware code, etc., or any combination thereof.
[0095]
[0101] Those skilled in the art will further appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. Those skilled in the art will also readily appreciate that the order or combination of components, methods, or interactions described herein are merely examples, and that the components, methods, or interactions of various aspects of the present disclosure may be combined or performed in ways other than those illustrated and described herein.
[0096]
[0102] Various aspects of the present disclosure may be implemented in multiple different manners and optional implementations. For example, a first aspect of wireless communication according to the present disclosure may include: obtaining, by a UE, a COT in response to a detected success of the UE's LBT procedure on a shared communication channel; determining, by the UE, whether COT sharing is enabled or not enabled; identifying, by the UE, COT sharing information for communicating to a serving base station in an uplink control message; and transmitting, by the UE, an uplink control message having the COT sharing information to the serving base station, where the COT sharing information is identified in response to the determining.
[0097]
[0103] A second aspect based on the first aspect, wherein the COT shared information includes one or more of a remaining COT duration from an end of one of the UE uplink transmissions in the COT or the PUSCH transmission including the COT shared information to an end point of the COT, an offset indication identifying an end of the UE uplink transmission, and a CAPC used by the UE to obtain the COT.
[0098]
[0104] A third aspect based on the second aspect, wherein the determining includes identifying an ED threshold configuration of the UE, and in response to identifying the ED threshold configuration as configured for sharing, determining that COT sharing is enabled, and in response to identifying the ED threshold configuration as not configured for sharing, determining that COT sharing is not enabled.
[0099]
[0105] A fourth aspect based on the third aspect, wherein identifying the COT sharing information includes one of identifying a remaining COT duration, an offset indication, and a CAPC for the uplink control message when it is determined that COT sharing is enabled, or identifying an offset indication and one or more of removal of CAPC, the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit during the remainder of the COT, or an indication of the number of symbols available for transmission by the serving base station for the uplink control message when it is determined that COT sharing is not enabled.
[0100]
[0106] A fifth aspect based on the second aspect, wherein the determining includes receiving a configuration message from a serving base station, wherein the configuration message includes an identification of COT sharing information for inclusion in the uplink control message; and determining whether COT sharing is enabled or not enabled based on the identification of the COT sharing information in the configuration message.
[0101]
[0107] A sixth aspect based on the fifth aspect, wherein determining whether COT sharing is enabled or not enabled includes identifying that a configuration message indicates to exclude CAPC and remaining COT duration from the uplink control message, wherein the UE determines that COT sharing is not enabled in response to identifying the configuration message.
[0102]
[0108] A seventh aspect based on the sixth aspect, further comprising, in response to identifying, by the UE, COT sharing as not enabled, using an ED threshold configuration for an LBT procedure that is not configured for sharing.
[0103]
[0109] An eighth aspect based on the second aspect, wherein the determining includes receiving a configuration message from a serving base station, wherein the configuration message indicates whether COT sharing is enabled or not enabled.
[0104]
[0110] A ninth aspect based on the eighth aspect, further comprising, in response to identifying, by the UE, COT sharing as not enabled, using an ED threshold configuration for an LBT procedure that is not configured for sharing.
[0105]
[0111] A tenth aspect based on the second aspect, wherein the COT sharing information includes an index to a table shared by the UE and the serving base station, wherein the table includes a plurality of entries, each of which identifies one or more of a remaining COT duration, an offset indication indicated as remaining transmission time, and a CAPC correspondence.
[0106]
[0112] An eleventh aspect based on the tenth aspect, wherein the table compresses the remaining COT duration and the remaining transmission time using the RIV.
[0107]
[0113] A twelfth aspect based on the eleventh aspect, wherein the RIV indicates one or more of: the remaining transmission time as a PUSCH slot boundary at which the UE uplink transmission will end; and the remaining COT duration has a granularity of a starting location of the UE uplink transmission configured by the serving base station.
[0108]
[0114] A thirteenth aspect based on the tenth aspect, wherein the table jointly codes the remaining COT duration and the offset indication using a start and length indicator value (SLIV).
[0109]
[0115] A fourteenth aspect based on the thirteenth aspect, wherein the SLIV length value is indicated at a granularity of a PUSCH transmission start point, wherein the PUSCH start point is configured by a serving base station.
[0110]
[0116] A fifteenth aspect based on the thirteenth aspect, wherein the SLIV start value is indicated at a granularity of one of a slot or a PUSCH transmission end point, and the SLIV length value is indicated at a granularity of one of a slot or a PUSCH transmission start point.
[0111]
[0117] A sixteenth aspect based on the thirteenth aspect, further comprising: adding, by the UE, corrective information to the uplink control message, wherein the corrective information modifies one or more values in a table indicated by the SLIV.
[0112]
[0118] A seventeenth aspect based on the second aspect, further including: compressing a remaining COT duration into an uplink control message, where compressing the remaining COT duration includes indicating, by the UE, a number of remaining COT slots and an ending symbol in a last slot of the number of remaining COT slots; compressing an offset indication into the uplink control message, where compressing the offset indication includes one of indicating, by the UE, an ending slot number and a last symbol of the UE uplink transmission within the ending slot number, or indicating, by the UE, the number of remaining transmission slots.
[0113]
[0119] An 18th aspect based on the second aspect, further comprising: obtaining, by the UE, a reporting location, wherein the reporting location identifies a number of slots before an end of the UE uplink transmission at which the UE performs transmitting an uplink control message having COT sharing information to a serving base station, wherein a remaining COT duration and offset indication are calculated by the UE from the number of slots before the end of the UE uplink transmission.
[0114]
[0120] A nineteenth aspect based on the second aspect, further comprising: determining, by the UE, a time gap between an end of the UE uplink transmission and a subsequent downlink transmission start opportunity; terminating, by the UE, the UE uplink transmission at the end of the UE uplink transmission in response to the time gap exceeding a minimum time for the serving base station to perform a shortened downlink LBT according to the LBT capability; and terminating, by the UE, the UE uplink transmission at an ending point before the end of the UE uplink transmission in response to the time gap exceeding the minimum time, wherein the extended time gap between the ending points before the end of the UE uplink transmission is sufficient for the serving base station to accommodate the minimum time for performing the shortened LBT.
[0115]
[0121] A twentieth aspect based on the nineteenth aspect, further including determining, by the UE, a transport block size for the UE uplink transmission based on one of: termination of UE uplink transmission with rate matching based on an end period before the end of the UE uplink transmission; termination of UE uplink transmission with rate matching based on the end of the UE uplink transmission, where the UE punctures resources associated with the extended time gap; or an end period before the end of UE uplink transmission with rate matching based on an end period before the end of the UE uplink transmission.
[0116]
[0122] A twenty-first aspect based on the twentieth aspect, wherein transmitting the uplink control message includes multiplexing the uplink control message according to one of: a first number of multiplexing symbols that is less than an actual number of multiplexing symbols based on an end of the UE uplink transmission used; an actual number of multiplexing symbols based on an end of the UE uplink transmission used; or a second number of multiplexing symbols that is more than the actual number of multiplexing symbols based on an end of the UE uplink transmission used.
[0117]
[0123] A 22nd aspect based on the first aspect, further comprising: obtaining, by the UE, a set of transmission configurations from a serving base station; selecting, by the UE, a transmission configuration from the set of transmission configurations; and adding, by the UE, a configuration indicator to an uplink control message, wherein the configuration indicator identifies a transmission configuration for the serving base station.
[0118]
[0124] A twenty-third aspect configured for wireless communication may comprise means for, by the UE, obtaining a COT in response to detected success of the UE's LBT procedure on the shared communications channel; means for determining, by the UE, whether COT sharing is enabled or not enabled; means for identifying, by the UE, COT sharing information for communication to a serving base station in an uplink control message, where the COT sharing information is identified in response to the means for determining; and means for transmitting, by the UE, an uplink control message having the COT sharing information to the serving base station.
[0119]
[0125] A 24th aspect based on the 23rd aspect, wherein the COT shared information includes one or more of a remaining COT duration from an end of one of the UE uplink transmissions in the COT or the PUSCH transmission including the COT shared information to an end point of the COT, an offset indication identifying an end of the UE uplink transmission, and a CAPC used by the UE to obtain the COT.
[0120]
[0126] A 25th aspect based on the 24th aspect, wherein the means for determining includes means for identifying an energy detection (ED) threshold configuration of the UE, and in response to identifying the ED threshold configuration as configured for sharing, determining that COT sharing is enabled, and in response to identifying the ED threshold configuration as not configured for sharing, determining that COT sharing is not enabled.
[0121]
[0127] A 26th aspect based on the 25th aspect, wherein the means for identifying COT sharing information includes one of means for identifying a remaining COT duration, an offset indication, and a CAPC for the uplink control message when it is determined that COT sharing is enabled, or means for identifying an offset indication and one or more of removal of CAPC, the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit during the remainder of the COT, or an indication of the number of symbols available for transmission by the serving base station for the uplink control message when it is determined that COT sharing is not enabled.
[0122]
[0128] A 27th aspect, based on the 24th aspect, wherein the means for determining includes means for receiving a configuration message from a serving base station, wherein the configuration message includes an identification of COT sharing information for inclusion in the uplink control message; and means for determining, based on the identification of the COT sharing information in the configuration message, whether COT sharing is enabled or not enabled.
[0123]
[0129] A 28th aspect, based on the 27th aspect, wherein the means for determining whether COT sharing is enabled or not enabled includes means for identifying that a configuration message indicates to exclude CAPC and remaining COT duration from the uplink control message, wherein the UE determines that COT sharing is not enabled in response to identifying the configuration message.
[0124]
[0130] A 29th aspect based on the 28th aspect, further including means for using an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identifying, by the UE, COT sharing as not enabled.
[0125]
[0131] A 30th aspect, based on the 24th aspect, wherein the means for determining includes means for receiving a configuration message from a serving base station, wherein the configuration message indicates whether COT sharing is enabled or not enabled.
[0126]
[0132] A thirty-first aspect based on the thirty-first aspect, further comprising means for using an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identifying, by the UE, COT sharing as not enabled.
[0127]
[0133] A thirty-second aspect based on the twenty-fourth aspect, wherein the COT sharing information includes an index to a table shared by the UE and the serving base station, wherein the table includes a plurality of entries, each of which identifies one or more of a remaining COT duration, an offset indication indicated as remaining transmission time, and a CAPC correspondence.
[0128]
[0134] A thirty-third aspect based on the thirty-second aspect, wherein the table compresses the remaining COT duration and the remaining transmission time using a resource indicator value (RIV).
[0129]
[0135] A thirty-fourth aspect, based on the thirty-third aspect, wherein the RIV indicates one or more of the remaining transmission time as a PUSCH slot boundary at which the UE uplink transmission will end, and the remaining COT duration has a granularity of a starting location of the UE uplink transmission configured by the serving base station.
[0130]
[0136] A thirty-fifth aspect based on the thirty-second aspect, wherein the table jointly codes the remaining COT duration and the offset indication using a start and length indicator value (SLIV).
[0131]
[0137] A thirty-sixth aspect based on the thirty-fifth aspect, wherein the SLIV length value is indicated at a granularity of a PUSCH transmission start point, wherein the PUSCH start point is configured by a serving base station.
[0132]
[0138] A 37th aspect based on the 35th aspect, wherein the SLIV start value is indicated at a granularity of one of a slot or a PUSCH transmission end point, and the SLIV length value is indicated at a granularity of one of a slot or a PUSCH transmission start point.
[0133]
[0139] A 38th aspect based on the 35th aspect, further comprising means for adding correction information to an uplink control message, by the UE, wherein the correction information modifies one or more values in a table indicated by the SLIV.
[0134]
[0140] A 39th aspect based on the 24th aspect, further including means for compressing a remaining COT duration into an uplink control message, where the means for compressing the remaining COT duration includes: means for indicating, by the UE, a number of remaining COT slots and an ending symbol in a last slot of the number of remaining COT slots; and means for compressing an offset indication into the uplink control message, where the means for compressing the offset indication includes one of: means for indicating, by the UE, an ending slot number and a last symbol of the UE uplink transmission within the ending slot number, or means for indicating, by the UE, the number of remaining transmission slots.
[0135]
[0141] A fortieth aspect based on the twenty-fourth aspect, further comprising: means for obtaining, by the UE, a reporting location, wherein the reporting location identifies a number of slots before an end of the UE uplink transmission at which the means for transmitting an uplink control message having COT sharing information to a serving base station is performed by the UE, and wherein a remaining COT duration and offset indication are calculated by the UE from the number of slots before the end of the UE uplink transmission.
[0136]
[0142] A forty-first aspect based on the twenty-fourth aspect, further comprising: means for determining, by the UE, a time gap between an end of the UE uplink transmission and a subsequent downlink transmission start opportunity; means for terminating, by the UE, the UE uplink transmission at the end of the UE uplink transmission in response to the time gap exceeding a minimum time for the serving base station to perform a shortened downlink LBT in accordance with the LBT capability; and means for terminating, by the UE, the UE uplink transmission at a termination period before the end of the UE uplink transmission in response to the time gap exceeding the minimum time, wherein the extended time gap between the termination period before the end of the UE uplink transmission is sufficient for the serving base station to accommodate the minimum time for the serving base station to perform the shortened LBT.
[0137]
[0143] A forty-second aspect based on the forty-first aspect, further including means for determining, by the UE, a transport block size for the UE uplink transmission based on one of: a termination of UE uplink transmission with rate matching based on an end period before an end of the UE uplink transmission; a termination of UE uplink transmission with rate matching based on an end period before an end of the UE uplink transmission, where the UE punctures resources associated with the extended time gap; or a termination period before an end of the UE uplink transmission with rate matching based on an end period before an end of the UE uplink transmission.
[0138]
[0144] A forty-third aspect, based on the forty-second aspect, wherein the means for transmitting the uplink control message includes means for multiplexing the uplink control message according to one of: a first number of multiplexing symbols less than an actual number of multiplexing symbols based on an end of the UE uplink transmission used; an actual number of multiplexing symbols based on an end of the UE uplink transmission used; or a second number of multiplexing symbols more than the actual number of multiplexing symbols based on an end of the UE uplink transmission used.
[0139]
[0145] A forty-fourth aspect based on the twenty-third aspect, further comprising: means for obtaining, by the UE, a set of transmission configurations from a serving base station; means for selecting, by the UE, a transmission configuration from the set of transmission configurations; and means for adding, by the UE, a configuration indicator to an uplink control message, wherein the configuration indicator identifies a transmission configuration for the serving base station.
[0140]
[0146] A forty-fifth aspect may include a non-transitory computer-readable medium having program code recorded thereon, the program code may comprise: program code executable by a computer to cause a computer, by the UE, to obtain a COT in response to a detected success of the UE's LBT procedure on the shared communications channel; program code executable by a computer to cause a computer to determine, by the UE, whether COT sharing is enabled or not enabled; program code executable by a computer to cause a computer to identify, by the UE, COT sharing information for communication in an uplink control message to a serving base station; and program code executable by a computer to cause a computer to send, by the UE, an uplink control message having the COT sharing information to the serving base station, wherein the COT sharing information is identified in response to execution of the program code executable by the computer to cause the computer to determine.
[0141]
[0147] A 46th aspect based on the 45th aspect, wherein the COT sharing information includes one or more of a remaining COT duration from an end of one of the UE uplink transmissions in the COT or the PUSCH transmission including the COT sharing information to an end point of the COT, an offset indication identifying an end of the UE uplink transmission, and a CAPC used by the UE to obtain the COT.
[0142]
[0148] A 47th aspect, based on the 46th aspect, wherein the program code executable by the computer to cause the computer to make a determination includes program code executable by the computer to cause the computer to identify an ED threshold configuration of the UE, program code executable by the computer to cause the computer to determine that COT sharing is enabled in response to identifying the ED threshold configuration as configured for sharing, and program code executable by the computer to cause the computer to determine that COT sharing is not enabled in response to identifying the ED threshold configuration as not configured for sharing.
[0143]
[0149] A 48th aspect, based on the 47th aspect, wherein the program code executable by a computer to cause a computer to identify COT sharing information includes one of program code executable by a computer to cause a computer to identify a remaining COT duration, an offset indication, and a CAPC for an uplink control message when it is determined that COT sharing is enabled, or program code executable by a computer to cause a computer to identify an offset indication and one or more of removal of CAPC, the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit during the remainder of the COT, or an indication of the number of symbols available for transmission by the serving base station, for an uplink control message when it is determined that COT sharing is not enabled.
[0144]
[0150] A 49th aspect, based on the 46th aspect, wherein the program code executable by the computer to cause a computer to make a determination includes program code executable by the computer to cause a computer to receive a configuration message from a serving base station, wherein the configuration message includes an identification of COT sharing information for inclusion in an uplink control message, and program code executable by the computer to cause the computer to determine, based on the identification of the COT sharing information in the configuration message, whether COT sharing is enabled or not enabled.
[0145]
[0151] A 50th aspect based on the 49th aspect, wherein the program code executable by the computer to cause the computer to determine whether COT sharing is enabled or not enabled includes program code executable by the computer to cause the computer to identify that a configuration message indicates to exclude CAPC and the remaining COT duration from the uplink control message, wherein the UE determines that COT sharing is not enabled in response to execution of the program code executable by the computer to cause the computer to identify the configuration message.
[0146]
[0152] A 51st aspect based on the 50th aspect, further including program code executable by a computer to cause the computer to use an energy detection (ED) threshold configuration for an LBT procedure that is not configured for sharing in response to identifying COT sharing as not enabled by the UE.
[0147]
[0153] A 52nd aspect, based on the 46th aspect, wherein the program code executable by the computer to cause the computer to make a determination includes program code executable by the computer to cause the computer to receive a configuration message from a serving base station, wherein the configuration message indicates whether COT sharing is enabled or not enabled.
[0148]
[0154] A 53rd aspect based on the 52nd aspect, further including program code executable by a computer to cause the computer to use an energy detection (ED) threshold configuration for an LBT procedure that is not configured for sharing in response to identifying COT sharing as not enabled by the UE.
[0149]
[0155] A 54th aspect based on the 46th aspect, wherein the COT sharing information includes an index to a table shared by the UE and the serving base station, wherein the table includes a plurality of entries, each of which identifies one or more of a remaining COT duration, an offset indication indicated as remaining transmission time, and a CAPC correspondence.
[0150]
[0156] A fifty-fifth aspect based on the fifty-fourth aspect, wherein the table compresses the remaining COT duration and the remaining transmission time using a resource indicator value (RIV).
[0151]
[0157] A 56th aspect, based on the 55th aspect, wherein the RIV indicates one or more of the remaining transmission time as a PUSCH slot boundary at which the UE uplink transmission will end, and the remaining COT duration has a granularity of a starting location of the UE uplink transmission configured by the serving base station.
[0152]
[0158] A fifty-seventh aspect based on the fifty-fourth aspect, wherein the table jointly codes the remaining COT duration and the offset indication using a start and length indicator value (SLIV).
[0153]
[0159] A fifty-eighth aspect based on the fifty-seventh aspect, wherein the SLIV length value is indicated at a granularity of a PUSCH transmission start point, wherein the PUSCH start point is configured by a serving base station.
[0154]
[0160] A 59th aspect based on the 57th aspect, wherein the SLIV start value is indicated at a granularity of one of a slot or a PUSCH transmission end point, and the SLIV length value is indicated at a granularity of one of a slot or a PUSCH transmission start point.
[0155]
[0161] A 60th aspect based on the 57th aspect, further comprising program code executable by a computer to cause a computer to add correction information, by a UE, to an uplink control message, wherein the correction information modifies one or more values in a table indicated by the SLIV.
[0156]
[0162] A 61st aspect based on the 46th aspect, further including program code executable by the computer to cause the computer to compress the remaining COT duration into the uplink control message, where the program code executable by the computer to cause the computer to compress the remaining COT duration includes program code executable by the computer to cause the computer to indicate, by the UE, a number of remaining COT slots and an ending symbol in a last slot of the number of remaining COT slots, and program code executable by the computer to cause the computer to compress the offset indication into the uplink control message, where the program code executable by the computer to cause the computer to compress the offset indication includes one of program code executable by the computer to cause the computer to indicate, by the UE, an ending slot number and a last symbol of the UE uplink transmission within the ending slot number, or program code executable by the computer to cause the computer to indicate, by the UE, the number of remaining transmission slots.
[0157]
[0163] A 62nd aspect based on the 46th aspect, further comprising computer-executable program code for causing a computer to obtain, by the UE, a reporting location, wherein the reporting location identifies a number of slots before an end of the UE uplink transmission, during which computer-executable program code is executed by the UE to cause the computer to send an uplink control message having COT sharing information to a serving base station, wherein a remaining COT duration and offset indication is calculated by the UE from the number of slots before the end of the UE uplink transmission.
[0158]
[0164] A 63rd aspect based on the 46th aspect, further comprising: program code executable by a computer to cause a computer to determine, by the UE, a time gap between an end of a UE uplink transmission and a subsequent downlink transmission start opportunity; program code executable by a computer to cause, by the UE, to terminate the UE uplink transmission at the end of the UE uplink transmission in response to the time gap exceeding a minimum time for the serving base station to perform a shortened downlink LBT according to the LBT capability; and program code executable by a computer to cause, by the UE, to terminate the UE uplink transmission at a termination period before the end of the UE uplink transmission in response to the minimum time exceeding the time gap, wherein the extended time gap between the termination periods before the end of the UE uplink transmission is sufficient for the serving base station to accommodate the minimum time for performing the shortened LBT.
[0159]
[0165] A 64th aspect based on the 63rd aspect, further including program code executable by a computer to cause a computer to determine, by the UE, a transport block size for a UE uplink transmission based on one of: a termination of a UE uplink transmission with rate matching based on an end period before a termination of the UE uplink transmission, a termination of a UE uplink transmission with rate matching based on an end period before a termination of the UE uplink transmission, where the UE punctures resources associated with an extended time gap, or a termination period before a termination of a UE uplink transmission with rate matching based on an end period before a termination of the UE uplink transmission.
[0160]
[0166] A sixty-fifth aspect, based on the sixty-fourth aspect, wherein the program code executable by the computer to cause a computer to transmit an uplink control message includes program code executable by the computer to cause the computer to multiplex the uplink control message according to one of a first number of multiplexing symbols less than an actual number of multiplexing symbols based on an end of the UE uplink transmission used, an actual number of multiplexing symbols based on an end of the UE uplink transmission used, or a second number of multiplexing symbols more than the actual number of multiplexing symbols based on an end of the UE uplink transmission used.
[0161]
[0167] A 66th aspect based on the 45th aspect, further including program code executable by a computer to cause a computer to obtain, by the UE, a set of transmission configurations from a serving base station; program code executable by a computer to cause the computer to select, by the UE, a transmission configuration from the set of transmission configurations; and program code executable by a computer to cause the computer to add, by the UE, a configuration indicator to an uplink control message, wherein the configuration indicator identifies a transmission configuration for the serving base station.
[0162]
[0168] A 67th aspect configured for wireless communication may include at least one processor and a memory coupled to the at least one processor, wherein the at least one processor may be configured to: obtain, by the UE, a COT in response to a detected success of the UE's LBT procedure on the shared communications channel; determine, by the UE, whether COT sharing is enabled or not enabled; identify, by the UE, COT sharing information for communication to a serving base station in an uplink control message; and transmit, by the UE, an uplink control message having the COT sharing information to the serving base station, wherein the COT sharing information is identified in response to execution of a configuration of the at least one processor for determining.
[0163]
[0169] A 68th aspect based on the 67th aspect, wherein the COT sharing information includes one or more of a remaining COT duration from an end of one of the UE uplink transmissions in the COT or the PUSCH transmission including the COT sharing information to an end point of the COT, an offset indication identifying an end of the UE uplink transmission, and a CAPC used by the UE to obtain the COT.
[0164]
[0170] A 69th aspect based on the 68th aspect, wherein the configuration of the at least one processor for determining includes a configuration of the at least one processor for identifying an ED threshold configuration of the UE, and in response to identifying the ED threshold configuration as configured for sharing, determining that COT sharing is enabled, and in response to identifying the ED threshold configuration as not configured for sharing, determining that COT sharing is not enabled.
[0165]
[0171] A seventieth aspect based on the sixty-ninth aspect, wherein the configuration of at least one processor for identifying COT sharing information includes a configuration of at least one processor for one of identifying a remaining COT duration, an offset indication, and a CAPC for the uplink control message when it is determined that COT sharing is enabled, or identifying one or more of an offset indication and removal of the CAPC, the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit during the remainder of the COT, or an indication of the number of symbols available for transmission by the serving base station for the uplink control message when it is determined that COT sharing is not enabled.
[0166]
[0172] A 71st aspect based on the 68th aspect, wherein the configuration of at least one processor for determining includes a configuration of at least one processor for receiving a configuration message from a serving base station and determining whether COT sharing is enabled or not enabled based on an identification of COT sharing information in the configuration message, wherein the configuration message includes an identification of COT sharing information for inclusion in an uplink control message.
[0167]
[0173] A 72nd aspect based on the 71st aspect, wherein the configuration of at least one processor for determining whether COT sharing is enabled or not enabled includes a configuration of at least one processor for identifying that a configuration message indicates to exclude CAPC and the remaining COT duration from the uplink control message, wherein the UE determines that COT sharing is not enabled in response to execution of the configuration of the at least one processor for identifying the configuration message.
[0168]
[0174] A 73rd aspect based on the 72nd aspect, further including, in response to identifying COT sharing as not enabled by the UE, configuring at least one processor to use an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing.
[0169]
[0175] A 74th aspect based on the 68th aspect, wherein the configuration of at least one processor for determining includes a configuration of at least one processor for receiving a configuration message from a serving base station, wherein the configuration message indicates whether COT sharing is enabled or not enabled.
[0170]
[0176] A 75th aspect based on the 74th aspect, further including configuring at least one processor to use an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identifying COT sharing as not enabled by the UE.
[0171]
[0177] A 76th aspect based on the 68th aspect, wherein the COT sharing information includes an index to a table shared by the UE and the serving base station, wherein the table includes a plurality of entries, each of which identifies one or more of a remaining COT duration, an offset indication indicated as remaining transmission time, and a CAPC correspondence.
[0172]
[0178] A 77th aspect based on the 76th aspect, wherein the table compresses the remaining COT duration and the remaining transmission time using a resource indicator value (RIV).
[0173]
[0179] A 78th aspect based on the 77th aspect, wherein the RIV indicates one or more of the remaining transmission time as a PUSCH slot boundary at which the UE uplink transmission will end, and the remaining COT duration has a granularity of a starting location of the UE uplink transmission configured by the serving base station.
[0174]
[0180] A 79th aspect based on the 76th aspect, wherein the table jointly codes the remaining COT duration and offset indication using a start and length indicator value (SLIV).
[0175]
[0181] An 80th aspect based on the 79th aspect, wherein the SLIV length value is indicated at a granularity of a PUSCH transmission start point, wherein the PUSCH start point is configured by a serving base station.
[0176]
[0182] An 81st aspect based on the 79th aspect, wherein the SLIV start value is indicated at a granularity of one of a slot or a PUSCH transmission end point, and the SLIV length value is indicated at a granularity of one of a slot or a PUSCH transmission start point.
[0177]
[0183] An 82nd aspect based on the 79th aspect, further including a configuration of at least one processor for adding correction information to an uplink control message, by the UE, wherein the correction information modifies one or more values in a table indicated by the SLIV.
[0178]
[0184] An 83rd aspect based on the 68th aspect, further including a configuration of at least one processor for compressing a remaining COT duration into an uplink control message, where the configuration of the at least one processor for compressing the remaining COT duration includes a configuration of at least one processor for indicating, by the UE, a number of remaining COT slots and an ending symbol in a last slot of the number of remaining COT slots; and compressing an offset indication into an uplink control message, where the configuration of the at least one processor for compressing the offset indication includes a configuration of at least one processor for one of indicating, by the UE, an ending slot number and a last symbol of the UE uplink transmission within the ending slot number, or indicating, by the UE, the number of remaining transmission slots.
[0179]
[0185] An 84th aspect based on the 68th aspect, further including: configuration of at least one processor for obtaining, by the UE, a reporting location, wherein the reporting location identifies a number of slots before an end of the UE uplink transmission during which configuration of at least one processor for transmitting an uplink control message having COT sharing information to a serving base station is performed by the UE, wherein a remaining COT duration and offset indication are calculated by the UE from the number of slots before the end of the UE uplink transmission.
[0180]
[0186] An 85th aspect based on the 68th aspect, further including configuration of at least one processor to: determine, by the UE, a time gap between an end of the UE uplink transmission and a subsequent downlink transmission start opportunity; terminate, by the UE, the UE uplink transmission at the end of the UE uplink transmission in response to the time gap exceeding a minimum time for the serving base station to perform a shortened downlink LBT in accordance with the LBT capability; and terminate, by the UE, the UE uplink transmission at an end period before the end of the UE uplink transmission in response to the time gap exceeding the minimum time, wherein the extended time gap between the end period before the end of the UE uplink transmission is sufficient for the serving base station to accommodate the minimum time for performing the shortened LBT.
[0181]
[0187] An 86th aspect based on the 85th aspect, further including configuring at least one processor to determine, by the UE, a transport block size for the UE uplink transmission based on one of: a termination of the UE uplink transmission with rate matching based on an end period before the end of the UE uplink transmission, a termination of the UE uplink transmission with rate matching based on the end of the UE uplink transmission, where the UE punctures resources associated with an extended time gap, or a termination period before the end of the UE uplink transmission with rate matching based on an end period before the end of the UE uplink transmission.
[0182]
[0188] An 87th aspect based on the 86th aspect, wherein the configuration of the at least one processor for transmitting the uplink control message includes a configuration of the at least one processor for multiplexing the uplink control message according to one of a first number of multiplexing symbols less than an actual number of multiplexing symbols based on an end of the UE uplink transmission used, the actual number of multiplexing symbols based on an end of the UE uplink transmission used, or a second number of multiplexing symbols more than the actual number of multiplexing symbols based on an end of the UE uplink transmission used.
[0183]
[0189] An 88th aspect based on the 67th aspect, further including configuration of at least one processor for: obtaining, by the UE, a set of transmission configurations from a serving base station; selecting, by the UE, a transmission configuration from the set of transmission configurations; and adding, by the UE, a configuration indicator to an uplink control message, wherein the configuration indicator identifies a transmission configuration for the serving base station.
[0184]
[0190] The various example logic blocks, modules, and circuits described in connection 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 alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0185]
[0191] The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.
[0186]
[0192] In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Computer-readable storage media may 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 may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, a connection may be properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, or a digital subscriber line (DSL), the coaxial cable, the fiber optic cable, the twisted pair, or the DSL are included in the definition of the medium. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0187]
[0193] As used herein, including 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 employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as including components A, B, and / or C, the composition may include only A, only B, only C, a combination of A and B, a combination of A and C, a combination of B and C, or a combination of A, B and C. Also, as used herein, including the claims, "or" used in a list of items ending with "at least one of" indicates a disjunctive list, such as, for example, a list of "at least one of A, B, or C" means any of A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any of these in any combination thereof.
[0188]
[0194] The above description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. The invention as described in the claims of the original application is set forth below. [C1] A method of wireless communication, comprising: obtaining, by a user equipment (UE), a channel occupation time (COT) in response to a detected success of a listen-before-talk (LBT) procedure of the UE on the shared communication channel; Determining, by the UE, whether COT sharing is enabled or not enabled; identifying, by the UE, COT sharing information for communication in an uplink control message to a serving base station, wherein the COT sharing information is identified in response to the determination; sending, by the UE, the uplink control message carrying the COT sharing information to the serving base station; A method comprising: [C2] The COT shared information is: the remaining COT duration from the end of one of the UE uplink transmissions in the COT or a physical uplink shared channel (PUSCH) transmission containing the COT shared information to an end point of the COT; an offset indication identifying the end of the UE uplink transmission; and A channel access priority class (CAPC) used by the UE to obtain the COT; and The method according to C1, comprising one or more of: [C3] The determination is Identifying an energy detection (ED) threshold configuration for the UE; and determining that the COT sharing is enabled in response to identifying the ED threshold configuration as configured for sharing; determining that the COT sharing is not enabled in response to identifying the ED threshold configuration as not configured for sharing; The method according to C2, comprising: [C4] The identifying of the COT shared information includes: Identifying the remaining COT duration, the offset indication, and the CAPC for the uplink control message when it is determined that the COT sharing is enabled; or the offset indication for the uplink control message when it is determined that the COT sharing is not enabled; and Removal of the CAPC; the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit during the remainder of the COT; or an indication of a number of symbols available for transmission by the serving base station; and identifying one or more of: The method according to C3, comprising one of the following: [C5] The determination is receiving a configuration message from the serving base station, wherein the configuration message includes an identification of the COT sharing information for inclusion in the uplink control message; determining whether the COT sharing is enabled or not enabled based on the identification of the COT sharing information in the configuration message; The method according to C2, comprising: [C6] The determining whether the COT share is to be enabled or not enabled comprises: identifying that the configuration message indicates to exclude the CAPC and the remaining COT duration from the uplink control message, wherein the UE determines that the COT sharing is not enabled in response to the identifying the configuration message; The method according to C5, comprising: [C7] in response to identifying, by the UE, the COT sharing as not enabled, using an energy detection (ED) threshold configuration for the LBT procedure that is not configured for sharing. The method of C6, further comprising: [C8] The determination is receiving a configuration message from the serving base station, where the configuration message indicates whether the COT sharing is enabled or not enabled; The method according to C2, comprising: [C9] in response to identifying, by the UE, the COT sharing as not enabled, using an energy detection (ED) threshold configuration for the LBT procedure that is not configured for sharing. The method of C8, further comprising: [C10] The method of C2, wherein the COT sharing information includes an index to a table shared by the UE and the serving base station, wherein the table includes a plurality of entries, each of which identifies one or more of the remaining COT duration, the offset indication indicated as remaining transmission time, and the CAPC corresponding. [C11] The method according to C10, wherein the table compresses the remaining COT duration and the remaining transmission time using a resource indicator value (RIV). [C12] RIV is the remaining transmission time as a Physical Uplink Shared Channel (PUSCH) slot boundary at which the UE uplink transmission will end; The remaining COT duration has a granularity of a starting location of the UE uplink transmission configured by the serving base station; The method according to claim 11, wherein the method further comprises: [C13] The method of C10, wherein the table jointly codes the remaining COT duration and the offset indication using a start and length indicator value (SLIV). [C14] The method according to C13, wherein the length value of the SLIV is indicated at a granularity of a physical uplink shared channel (PUSCH) transmission start point, where the PUSCH start point is configured by the serving base station. [C15] The method according to C13, wherein the start value of the SLIV is indicated at a granularity of one of a slot or a PUSCH transmission end point, and the length value of the SLIV is indicated at a granularity of one of a slot or a PUSCH transmission start point. [C16] adding, by the UE, correction information to the uplink control message, wherein the correction information modifies one or more values in the table indicated by the SLIV. The method of C13, further comprising: [C17] compressing the remaining COT duration into the uplink control message, wherein the compressing the remaining COT duration includes indicating, by the UE, a number of remaining COT slots and a termination symbol in a last slot of the number of remaining COT slots; compressing the offset indication into the uplink control message, wherein the compressing the offset indication comprises: indicating, by the UE, an end slot number and a last symbol of the UE uplink transmission within the end slot number; or indicating, by the UE, a number of remaining transmission slots; Contains one of the following: The method of C2, further comprising: [C18] obtaining, by the UE, a reporting location, where the reporting location identifies a number of slots before the end of the UE uplink transmission at which the transmitting of the uplink control message having the COT shared information to the serving base station is performed by the UE, and the remaining COT duration and the offset indication are calculated by the UE from the number of slots before the end of the UE uplink transmission. The method of C2, further comprising: determining, by the UE, a time gap between the end of the UE uplink transmission and a subsequent downlink transmission start opportunity; and terminating, by the UE, the UE uplink transmission at the end of the UE uplink transmission in response to the time gap exceeding a minimum time for the serving base station to perform a shortened downlink LBT according to the LBT capability. and terminating, by the UE, the UE uplink transmission at a termination period prior to the termination of the UE uplink transmission in response to the minimum time exceeding the time gap, wherein the extended time gap during the termination period prior to the termination of the UE uplink transmission is sufficient for the serving base station to accommodate the minimum time for performing the shortened LBT. The method of C2, further comprising: [C20] by said UE, the termination of the UE uplink transmission with rate matching based on the termination period prior to the termination of the UE uplink transmission; the termination of the UE uplink transmission with the rate matching based on the termination of the UE uplink transmission, where the UE punctures resources associated with the extended time gap; or The end period before the end of the UE uplink transmission with the rate matching based on the end period before the end of the UE uplink transmission. determining a transport block size for the UE uplink transmission based on one of: The method of C19, further comprising: [C21] The transmitting of the uplink control message comprises: a first number of multiplexing symbols that is less than an actual number of multiplexing symbols based on the end of the UE uplink transmission used; the actual number of multiplexing symbols based on the end of the UE uplink transmission used; or a second number of multiplexing symbols that is greater than the actual number of multiplexing symbols based on the end of the UE uplink transmission used; multiplexing the uplink control message according to one of The method according to C20, comprising: [C22] obtaining, by the UE, a set of transmission configurations from the serving base station; and selecting, by the UE, a transmission configuration from the set of transmission configurations; adding, by the UE, a configuration indicator to the uplink control message, wherein the configuration indicator identifies the transmission configuration for the serving base station. The method of C1, further comprising: [C23] Apparatus configured for wireless communication, comprising: At least one processor; a memory coupled to the at least one processor; and Equipped with The at least one processor: obtaining, by a user equipment (UE), a channel occupation time (COT) in response to a detected success of a listen-before-talk (LBT) procedure of the UE on the shared communication channel; Determining, by the UE, whether COT sharing is enabled or not enabled; identifying, by the UE, COT sharing information for communication in an uplink control message to a serving base station, wherein the COT sharing information is identified in response to execution of a configuration of the at least one processor performing the determining; sending, by the UE, the uplink control message carrying the COT sharing information to the serving base station; An apparatus configured to: [C24] The COT shared information is: the remaining COT duration from the end of one of the UE uplink transmissions in the COT or a physical uplink shared channel (PUSCH) transmission containing the COT shared information to an end point of the COT; an offset indication identifying the end of the UE uplink transmission; and A channel access priority class (CAPC) used by the UE to obtain the COT; and The apparatus of C23, comprising one or more of: [C25] The configuration of the at least one processor for performing the determining comprises: Identifying an energy detection (ED) threshold configuration for the UE; determining that the COT sharing is enabled in response to identifying the ED threshold configuration as configured for sharing; responsive to identifying the ED threshold configuration as not configured for sharing, determining that the COT sharing is not enabled. The apparatus of C24, comprising a configuration of the at least one processor. [C26] The configuration of the at least one processor for identifying the COT sharing information further comprises: Identifying the remaining COT duration, the offset indication, and the CAPC for the uplink control message when it is determined that the COT sharing is enabled; or the offset indication for the uplink control message when it is determined that the COT sharing is not enabled; and Removal of the CAPC; the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit during the remainder of the COT; or an indication of a number of symbols available for transmission by the serving base station; and identifying one or more of: 4. The apparatus of claim 3, further comprising: [C27] The configuration of the at least one processor for performing the determining comprises: receiving a configuration message from the serving base station, wherein the configuration message includes an identification of the COT sharing information for inclusion in the uplink control message; determining whether the COT sharing is enabled or not enabled based on the identification of the COT sharing information in the configuration message; The apparatus of C24, comprising a configuration of the at least one processor to perform the following: [C28] The configuration of the at least one processor for determining whether COT sharing is enabled or not enabled comprises: and a configuration of the at least one processor for identifying that the configuration message indicates to exclude the CAPC and the remaining COT duration from the uplink control message, wherein the UE determines that the COT sharing is not enabled in response to execution of the configuration of the at least one processor for identifying the configuration message. The apparatus described in C27. [C29] The apparatus of C28, further comprising: configuring the at least one processor to use an energy detection (ED) threshold configuration for the LBT procedure that is not configured for sharing in response to identifying the COT sharing as not enabled by the UE. [C30] The apparatus of C24, wherein the configuration of the at least one processor to determine includes a configuration of the at least one processor to receive a configuration message from the serving base station, wherein the configuration message indicates whether the COT sharing is enabled or not enabled. [C31] The apparatus of C30, further comprising: configuring the at least one processor to use an energy detection (ED) threshold configuration for the LBT procedure that is not configured for sharing in response to identifying the COT sharing as not enabled by the UE. [C32] The apparatus of C24, wherein the COT sharing information includes an index to a table shared by the UE and the serving base station, wherein the table includes a plurality of entries, each of which identifies one or more of the remaining COT duration, the offset indication indicated as remaining transmission time, and the CAPC corresponding. [C33] The apparatus of C32, wherein the table compresses the remaining COT duration and the remaining transmission time using a resource indicator value (RIV). [C34] RIV is the remaining transmission time as a Physical Uplink Shared Channel (PUSCH) slot boundary at which the UE uplink transmission will end; the remaining COT duration has a granularity of a starting location of the UE uplink transmission configured by the serving base station; 5. The apparatus of claim 33, further comprising one or more of: [C35] The apparatus of C32, wherein the table jointly codes the remaining COT duration and the offset indication using a start and length indicator value (SLIV). [C36] The apparatus of C35, wherein the SLIV length value is indicated at a granularity of a physical uplink shared channel (PUSCH) transmission start point, wherein the PUSCH start point is configured by the serving base station. [C37] The apparatus according to C35, wherein the start value of the SLIV is indicated at a granularity of one of a slot or a PUSCH transmission end point, and the length value of the SLIV is indicated at a granularity of one of a slot or a PUSCH transmission start point. [C38] The apparatus of C35, further comprising configuring the at least one processor to add correction information to the uplink control message by the UE, wherein the correction information modifies one or more values in the table indicated by the SLIV. [C39] compressing the remaining COT duration into the uplink control message, wherein the at least one processor configuration for compressing the remaining COT duration includes the at least one processor configuration for indicating, by the UE, a number of remaining COT slots and a termination symbol in a last slot of the number of remaining COT slots; compressing the offset indication into the uplink control message, wherein the configuration of the at least one processor for compressing the offset indication comprises: indicating, by the UE, an end slot number and a last symbol of the UE uplink transmission within the end slot number; or indicating, by the UE, a number of remaining transmission slots; a configuration of the at least one processor to perform one of the following: 25. The apparatus of claim 24, further comprising a configuration of the at least one processor to: [C40] The method further includes configuring the at least one processor to obtain, by the UE, a reporting location; Wherein the reporting location identifies a number of slots prior to the end of the UE uplink transmission during which the configuration of the at least one processor to transmit the uplink control message with the COT sharing information to the serving base station is performed by the UE, and wherein the remaining COT duration and the offset indication are calculated by the UE from the number of slots prior to the end of the UE uplink transmission. The apparatus described in C24. determining, by the UE, a time gap between the end of the UE uplink transmission and a subsequent downlink transmission start opportunity; and terminating, by the UE, the UE uplink transmission at the end of the UE uplink transmission in response to the time gap exceeding a minimum time for the serving base station to perform a shortened downlink LBT according to the LBT capability. and terminating, by the UE, the UE uplink transmission at a termination period prior to the termination of the UE uplink transmission in response to the minimum time exceeding the time gap, wherein the extended time gap during the termination period prior to the termination of the UE uplink transmission is sufficient for the serving base station to accommodate the minimum time for performing the shortened LBT. 25. The apparatus of claim 24, further comprising a configuration of the at least one processor to: [C42] by said UE, the termination of the UE uplink transmission with rate matching based on the termination period prior to the termination of the UE uplink transmission; the termination of the UE uplink transmission with the rate matching based on the termination of the UE uplink transmission, where the UE punctures resources associated with the extended time gap; or The end period before the end of the UE uplink transmission with the rate matching based on the end period before the end of the UE uplink transmission. determining a transport block size for the UE uplink transmission based on one of: The apparatus of C41, further comprising a configuration of the at least one processor to perform the following: [C43] The configuration of the at least one processor for transmitting the uplink control message further comprises: a first number of multiplexing symbols that is less than an actual number of multiplexing symbols based on the end of the UE uplink transmission used; the actual number of multiplexing symbols based on the end of the UE uplink transmission used; or a second number of multiplexing symbols that is greater than the actual number of multiplexing symbols based on the end of the UE uplink transmission used; The apparatus of claim 42, further comprising: a configuration of the at least one processor for multiplexing the uplink control message according to one of: [C44] obtaining, by the UE, a set of transmission configurations from the serving base station; and selecting, by the UE, a transmission configuration from the set of transmission configurations; adding, by the UE, a configuration indicator to the uplink control message, wherein the configuration indicator identifies the transmission configuration for the serving base station. 23. The apparatus of claim 22, further comprising:
Claims
1. 1. A method of wireless communication, comprising: obtaining, by a user equipment (UE), a channel occupation time (COT) in response to a detected success of a listen-before-talk (LBT) procedure of the UE on a shared communications channel; determining, by the UE, whether COT sharing is enabled or not enabled; identifying, by the UE, COT sharing information for communication in an uplink control message to a serving base station, wherein the COT sharing information is identified in response to the determination; sending, by the UE, the uplink control message carrying the COT sharing information to the serving base station; Equipped with the determining comprises determining whether the COT sharing is enabled or not enabled based on at least one of an energy detection (ED) threshold configured by the serving base station and an identification of the COT sharing information for inclusion in the uplink control message. method.
2. The COT shared information is a remaining COT duration from the end of one of a UE uplink transmission in the COT or a physical uplink shared channel (PUSCH) transmission containing the COT shared information to an end point of the COT; an offset indication identifying the end of the UE uplink transmission; and A Channel Access Priority Class (CAPC) used by the UE for obtaining the COT; and The method of claim 1 , comprising one or more of:
3. The determining step comprises: identifying the ED threshold; determining that the COT sharing is enabled in response to identifying the ED threshold as configured for sharing; determining that the COT sharing is not enabled in response to identifying the ED threshold as not configured for sharing; The method of claim 2 , comprising:
4. The determining step comprises: receiving a configuration message from the serving base station, wherein the configuration message includes the identification of the COT sharing information for inclusion in the uplink control message; determining whether the COT sharing is to be enabled or not enabled based on the identification of the COT sharing information in the configuration message; The method of claim 2 , comprising:
5. The determining whether the COT sharing is to be enabled or not enabled includes: identifying that the configuration message indicates to exclude the CAPC and the remaining COT duration from the uplink control message, wherein the UE determines that the COT sharing is not enabled in response to the identifying the configuration message. The method of claim 4 , comprising:
6. in response to an identification by the UE of the COT sharing as not enabled, using an energy detection (ED) threshold configuration for the LBT procedure that is not configured for sharing; The method of claim 1 further comprising:
7. 3. The method of claim 2, wherein the COT shared information includes an index to a table shared by the UE and the serving base station, where the table includes a plurality of entries, each of which identifies one or more of the remaining COT duration, the offset indication, denoted as remaining transmission time, and the CAPC correspondence.
8. The method of claim 7 , wherein the table jointly codes the remaining COT duration and the offset indication using a Start and Length Indicator Value (SLIV).
9. 9. The method of claim 8, wherein the SLIV length value is indicated with a granularity of a physical uplink shared channel (PUSCH) transmission start point, where a PUSCH start point is configured by the serving base station.
10. 9. The method of claim 8, wherein the SLIV start value is indicated with a granularity of one of a slot or a PUSCH transmission end point, and the SLIV length value is indicated with a granularity of one of a slot or a PUSCH transmission start point.
11. adding, by the UE, correction information to the uplink control message, wherein the correction information modifies one or more values in the table indicated by the SLIV. The method of claim 8 further comprising:
12. compressing the remaining COT duration into the uplink control message, wherein the compressing the remaining COT duration includes indicating, by the UE, a number of remaining COT slots and a termination symbol within a last slot of the number of remaining COT slots; compressing the offset indication into the uplink control message, wherein the compressing the offset indication comprises: indicating, by the UE, an end slot number and a last symbol of the UE uplink transmission within the end slot number; or indicating, by the UE, a number of remaining transmission slots; including one of The method of claim 2 , further comprising:
13. obtaining, by the UE, a reporting location, where the reporting location identifies a number of slots before the end of the UE uplink transmission at which the transmitting of the uplink control message having the COT sharing information to the serving base station is performed by the UE as a location where the COT sharing information is signaled in the uplink control message; the COT shared information in the uplink control message is transmitted by the UE to the serving base station in the number of slots prior to the end of the UE uplink transmission; the remaining COT duration and the offset indication are calculated by the UE from the number of slots before the end of the UE uplink transmission. The method of claim 2 , further comprising:
14. 1. An apparatus configured for wireless communication, comprising: At least one processor; a memory coupled to the at least one processor; Equipped with The at least one processor obtaining, by a user equipment (UE), a channel occupation time (COT) in response to a detected success of a listen-before-talk (LBT) procedure of the UE on a shared communications channel; determining, by the UE, whether COT sharing is enabled or not enabled; identifying, by the UE, COT sharing information for communication in an uplink control message to a serving base station, wherein the COT sharing information is identified in response to execution of a configuration of the at least one processor performing a determining step; sending, by the UE, the uplink control message carrying the COT sharing information to the serving base station; configured to: the determining comprises determining whether the COT sharing is enabled or not enabled based on at least one of an energy detection (ED) threshold configured by the serving base station and an identification of the COT sharing information for inclusion in the uplink control message. Device.