Configured grant channel occupancy time sharing procedure

Abstract

To provide a method and a device that include a configured grant (CG) channel occupancy time (COT) sharing procedure.SOLUTION: A method of wireless communication includes: obtaining, by user equipment (UE), a channel occupancy time (COT) in response to a detected success of a listen-before-talk (LBT) procedure of the UE on a shared communication channel; determining, by the UE, whether COT sharing is a thing to be enabled or a thing not to be enabled; identifying, by the UE, COT sharing information identified according to the determination 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.SELECTED DRAWING: Figure 3

Description

Claim of Priority

[0001] Cross - reference to Related Applications

[0001] This application claims the benefit of Indian Provisional Patent Application No. 201941045481, filed on November 8, 2019, entitled "CONFIGURED GRANT CHANNEL OCCUPANCY TIME SHARING PROCEDURE", which is hereby incorporated by reference in its entirety.

Technical Field

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication systems, and more particularly, to a configured grant channel occupancy time (COT) sharing procedure.

Background Art

[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 can be multi-connection networks capable of supporting multiple users by sharing available network resources. Such networks are typically multi-connection networks that support communication for multiple users by sharing available network resources. An 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), which is a third-generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP (registered trademark)). Examples of multi-connection 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]

[0004] A wireless communication network can include several base stations or Node Bs capable of supporting communication for several user equipments (UEs). The UE can communicate with the base station via the downlink and the 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] The base station can transmit data and control information to the UE on the downlink and / or receive data and control information from the UE on the uplink. On the downlink, transmissions from the base station may encounter interference from transmissions from neighboring base stations or from other wireless radio frequency (RF) transmitters. On the uplink, transmissions from the UE may encounter interference from uplink transmissions of other UEs communicating with neighboring base stations or from interference from other wireless RF transmitters. This interference can potentially 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 potential for interference and congested networks. Research and development to evolve wireless technology continues 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 occupancy time (COT) in response to a detected success of a listen-before-talk (LBT) procedure of the UE 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 with a serving base station in an uplink control message, wherein the COT sharing information is identified according to the determination; and transmitting, by the UE, the 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 communication includes means for a UE to obtain a COT in response to a detected success of the UE's LBT procedure on a shared communication channel, means for a UE to determine whether COT sharing is enabled or not, means for a UE to identify COT sharing information for communicating with a serving base station in an uplink control message, wherein the COT sharing information is identified according to the means for determination, and means for a UE to transmit an uplink control message having the COT sharing information to the serving base station.

[0009]

[0009] In a further aspect of the present disclosure, a non-transitory computer-readable medium recording program code. The program code further includes code for a UE to obtain a COT in response to a detected success of the UE's LBT procedure on a shared communication channel, code for a UE to determine whether COT sharing is enabled or not, code for a UE to identify COT sharing information for communicating with a serving base station in an uplink control message, wherein the COT sharing information is identified according to the execution of the code for determination, and code for a UE to transmit 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 a COT in response to a detected success of the UE's LBT procedure on a shared communication channel by the UE; determine whether COT sharing is enabled or not by the UE; identify COT sharing information for communicating with a serving base station in an uplink control message by the UE, wherein the COT sharing information is identified in response to execution of the configuration of at least one processor for determining; and transmit an uplink control message having the COT sharing information to the serving base station by the UE.

[0011]

[0011] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so as to enable a better understanding of the detailed description of the invention that follows. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be easily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent configurations 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 connection with the accompanying figures. Each of the figures is provided for purposes of illustration and description and is not intended as a definition of the limits of the claims.

[0012]

[0012] A further understanding of the nature and advantages of the present disclosure can be realized by reference to the following drawings. In the accompanying drawings, like components or features may have the same reference numerals. Further, 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. If only the 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

[0013] Block diagram showing details of the wireless communication system.

Figure 2

[0014] Block diagram showing the design of a base station and a UE configured according to an aspect of the present disclosure.

Figure 3

[0015] Block diagram showing exemplary blocks executed to implement an aspect of the present disclosure.

Figure 4

[0016] Block diagram showing a communication dialogue between a UE having channel occupancy time (COT) sharing capability and a base station configured according to an aspect of the present disclosure.

Figure 5

[0017] Block diagram showing a part of an NR-U network including a UE having COT sharing capability and a base station configured according to an aspect of the present disclosure.

Figure 6A

[0018] Block diagram showing a UE having COT sharing capability and a base station configured according to an aspect of the present disclosure.

Figure 6B

Figure 6C

Figure 7

[0019] Block diagram showing an exemplary UE configured according to an aspect of the present disclosure.

Modes for Carrying Out the Invention

[0014]

[0020] The following detailed description with reference to the accompanying drawings describes various configurations and is not intended to limit the scope of the present disclosure. Rather, this detailed description includes specific details for providing a complete understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case and that in some instances, well-known structures and components may be shown in block diagram form for clarity of presentation.

[0015]

[0021] The present disclosure generally relates to providing or participating in permitted shared access between two or more wireless communication systems, also referred to as a wireless communication network. 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 (registered trademark) networks, GSM (registered trademark) networks, fifth generation (5G) networks or new radio (NR) networks, as well as other communication networks. The terms "network" and "system" as described herein may be used interchangeably.

[0016]

[0022] An OFDMA network can implement wireless technologies such as evolved UTRA (E-UTRA), IEEE802.11, IEEE802.16, IEEE802.20, flash-OFDM, etc. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of the Universal Mobile Telecommunication 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 provided by a group called the "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from a group called the "3rd Generation Partnership Project 2" (3GPP2). These various wireless technologies and standards are known or developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration among groups of the telecommunications association aimed at defining globally applicable 3rd 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 can define specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure relates to the development of wireless technologies from LTE, 4G, 5G, NR, and beyond, involving shared access to the wireless spectrum between networks using new and different wireless access technologies or a set of wireless air interfaces.

[0017]

[0023] In particular, the 5G network contemplates diverse deployments, diverse spectrums, as well as diverse services and devices that can be implemented using an OFDM-based integrated air interface. To achieve these goals, further extensions of LTE and LTE-A are considered in addition to the development of new radio technologies for 5G NR networks. 5G NR provides coverage for (1) large-scale Internet of Things (IoT) with deep coverage having extremely high density (e.g., about 1 million nodes / km 2 ), extremely low complexity (e.g., about dozens of bits / second), extremely low energy (e.g., about battery life of more than 10 years), and the ability to reach difficult locations, (2) mission-critical control with strong security for protecting highly confidential personal information, financial information, or classified information, extremely high reliability (e.g., about 99.9999% reliability), extremely low latency (e.g., about 1 ms), and users with or without a wide range of mobility, and (3) extended mobile broadband including extremely high capacity (e.g., about 10 Tbps / km 2 ), extremely high data rates (e.g., multi-Gbps rates, user experience rate of 100 Mbps or more), and deep awareness for advanced discovery and optimization, and is scalable to provide them.

[0018]

[0024] 5G NR has a common flexible framework with scalable numerology and transmission time intervals (TTIs) to efficiently multiplex services and features with a dynamic low-latency time-division duplexing (TDD) / frequency-division duplexing (FDD) design, and is implemented to use an optimized OFDM-based waveform 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 subcarrier spacing scaling can efficiently handle operating various services across diverse spectrums and diverse deployments. For example, in various outdoor and macro coverage deployments of FDD / TDD implementations below 3 GHz, the subcarrier spacing can occur at 15 kHz over bandwidths such as 1, 5, 10, 20 MHz, etc. In various other outdoor and small cell coverage deployments of TDD above 3 GHz, the subcarrier spacing can occur at 30 kHz over 80 / 100 MHz bandwidths. In various other indoor broadband deployments using TDD on the unlicensed portion of the 5 GHz band, the subcarrier spacing can occur at 60 kHz over 160 MHz bandwidths. Finally, in various deployments transmitting using mmWave components in 28 GHz TDD, the subcarrier spacing can occur at 120 kHz over 500 MHz bandwidths.

[0019]

[0025] The scalable numerology of 5G NR 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 can be used for higher spectral efficiency. Efficient multiplexing of long TTIs and short TTIs to enable transmissions to start on symbol boundaries. 5G NR also contemplates a self - contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgments within the same subframe. The self - contained integrated subframe supports communication in adaptive uplink / downlink that can be flexibly configured per cell to switch dynamically between uplink and downlink for unlicensed or contention - based shared spectrum 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 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 should understand 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 carried out using any number of the aspects described herein. Further, in addition to or instead of one or more of the aspects described herein, such an apparatus can be implemented or such a method can be carried out using other structures, functions, or structures and functions. 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. Further, one aspect can comprise at least one element of one claim.

[0021]

[0027] FIG. 1 is a block diagram illustrating an example of a wireless communication system 100 that supports configured grant channel occupancy time (COT) sharing according to an aspect of the present disclosure. A UE such as UE 115 that shares COT may indicate, in an uplink control indicator (UCI) message, the remaining COT duration, an offset indication that identifies where 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 types of data may be included within a downlink transmission within the shared COT. If an energy detection (ED) threshold is not configured for COT sharing, UE 115 may reduce the information included within the UCI. Alternatively, base station 112 may configure what information UE 115 includes within the UCI for potential COT sharing. The COT sharing information may further be compressed by coding such information into a table of transmission characteristics or utilization knowledge, such as a configured end point. The wireless communication system 100 includes base station 105, UE 115, and core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support extended broadband communication, ultra-reliable (e.g., mission-critical) communication, low latency communication, or communication using low-cost and low-complexity devices.

[0022]

[0028] Base station 105 may wirelessly communicate with UE 115 via one or more base station antennas. The base station 105 described herein may include a base transceiver station, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B or a giga Node B (any of which may sometimes be referred to as a gNB), a home Node B, a home eNB, or some other suitable term, or may be so referred to by those skilled in the art. 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 devices, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.

[0023]

[0029] Each base station 105 may be associated with a specific geographic coverage area 110 in which communication with various UEs 115 is supported. Each base station 105 can provide communication coverage to its respective geographic coverage area 110 via a communication link 125, and 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 an uplink transmission from the UE 115 to the base station 105 or a downlink transmission from the base station 105 to the UE 115. Downlink transmissions may sometimes be referred to as forward link transmissions, while uplink transmissions may sometimes be referred to as reverse link transmissions.

[0024]

[0030] The geographical coverage area 110 for the base station 105 can be divided into sectors that form part of the geographical coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for macro cells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, the base station 105 is mobile and thus can provide communication coverage to a moving geographical coverage area 110. In some examples, different geographical coverage areas 110 associated with different technologies may overlap, and the overlapping geographical coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous LTE / LTE-A / LTE-A Pro or NR network where different types of base stations 105 provide coverage to various geographical 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 can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) for distinguishing neighboring cells operating via the same or different carriers. In some examples, a carrier can support multiple cells, and different cells can 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 provide access to different types of devices. In some cases, the term "cell" may refer to a part (e.g., a sector) of the geographical coverage area 110 on which the logical entity operates.

[0026]

[0032] UE 115 can be distributed throughout the wireless communication system 100, and each UE 115 can be fixed or mobile. UE 115 may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client. UE 115 may also be a personal electronic device such as a cellular phone (UE 115a), a personal digital assistant (PDA), a wearable device (UE 115d), a tablet computer, a laptop computer (UE 115g), or a personal computer. In some examples, UE 115 may also be a wireless local loop (WLL) station, an Internet of Things (IoT) device, any Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which can be implemented in various articles such as appliances, vehicles (UE 115e and UE 115f), meters (UE 115b and UE 115c).

[0027]

[0033] Some UEs 115, such as MTC devices or IoT devices, can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that enable devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC incorporates sensors or meters to measure or capture information and relays that information to a central server or application program that can utilize the information, or includes communication from a device that presents the information to a human interacting with a program or application. Some UEs 115 may be designed to collect information or enable automated operation of machines. Examples of application cases 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 can be configured to adopt an operating mode that reduces 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 can be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving "deep sleep" mode when not participating in active communication or operating on a limited bandwidth (e.g., in accordance with narrowband communication). In other cases, UEs 115 can be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 can be configured to provide ultra-reliable communication for these functions.

[0029]

[0035] In some cases, UE 115 may also be able to communicate directly with other UEs 115 (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol). One or more of the groups of UEs 115 using D2D communication may be within the geographical coverage area 110 of the base station 105. Other UEs 115 within such a group may be outside the geographical coverage area 110 of the base station 105 or may otherwise be unable 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 within the group. In some cases, the base station 105 may facilitate the 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 station 105 can communicate with the core network 130 and with each other. For example, the base station 105 can interface with the core network 130 through a backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other on a backhaul link 134 either directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130) (e.g., via X2, Xn, or other interfaces).

[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 includes 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 UE 115 served by the base station 105 associated with the EPC. User IP packets may be transferred through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to the network operator IP services. The operator IP services may include access to the Internet, intranet, IP multimedia subsystem (IMS), or packet switched (PS) streaming services.

[0032]

[0038] At least some of the network devices, such as the base station 105, may include sub-components such as an access network entity, which may be an example of an access node controller (ANC). Each access network entity may communicate with the UE 115 through several other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). In some configurations, the various functions of each access network entity or the 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] Wireless communication system 100 can typically operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band since the wavelength ranges from approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features. However, the waves can penetrate structures sufficiently for a macrocell to provide service to a UE 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to transmission 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] Wireless communication system 100 can also operate in the super-high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz, 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 opportunistically used by devices that may be able to tolerate interference from other users.

[0035]

[0041] Wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., from 30 GHz to 300 GHz). In some examples, wireless communication system 100 can support millimeter wave (mmW) communication between UE 115 and base station 105, and the EHF antennas of each device can be even smaller and more closely spaced than UHF antennas. In some cases, this can facilitate the use of an antenna array within UE 115. However, EHF transmissions can experience greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of bands across these frequency regions can vary by country or regulatory body.

[0036]

[0042] Wireless communication system 100 may include operation by different network operating entities (e.g., network operators) that can share spectrum. In some cases, a network operating entity may be configured to use the entire designated shared spectrum for at least some period of time before another network operating entity uses the entire designated shared spectrum over a different time period. Thus, to enable a network operating entity to use all of the designated shared spectrum and to reduce interference in communication between different network operating entities, certain resources (e.g., time) may be partitioned for use by a particular type of communication and allocated to different network operating entities.

[0037]

[0043] For example, a network operating entity may be allocated a particular time resource reserved for exclusive communication by a network operating entity using the entire shared spectrum. A network operating entity may be allocated other time resources in which the entity is given priority over other network operating entities for communicating using the shared spectrum. These time resources, which 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 opportunistic use.

[0038]

[0044] Access to the shared spectrum and arbitration of time resources between different network operating entities can be centrally controlled by separate entities, autonomously determined by a predefined arbitration scheme, or dynamically determined based on the interaction between wireless nodes of network operators.

[0039]

[0045] In various implementation forms, the wireless communication system 100 can use both licensed radio frequency spectrum bands and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 can adopt 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 the base station 105 of the wireless communication system 100 can operate in a shared radio frequency spectrum band that may include a licensed frequency spectrum or an unlicensed (e.g., contention-based) frequency spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or the base station 105 can perform the conventional medium sensing procedure for competing to access the frequency spectrum. For example, the UE 115 or the base station 105 can execute a listen-before-talk (LBT) procedure such as a clear channel assessment (CCA) prior to communication to determine whether the shared channel is available.

[0040]

[0046] CCA may include an energy detection procedure to determine whether there is other active transmission 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. Specifically, signal power concentrated within a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a message of a specific sequence indicating channel usage. For example, another device may transmit a specific preamble prior to transmitting a data sequence. In some cases, the LBT procedure may include a wireless node that adjusts its own backoff window based on the amount of energy detected on the channel and / or the acknowledgment / negative acknowledgment (ACK / NACK) feedback for its own transmitted packet as a proxy for collisions.

[0041]

[0047] Generally, four categories of LBT procedures for sensing a shared channel for signals that may indicate that the channel is already occupied have been suggested. In the first category (CAT1 LBT), LBT or CCA is not applied to detect occupancy of the shared channel. The second category (CAT2 LBT), also sometimes called shortened LBT, single-shot LBT, or 25 μs LBT, provides a node for performing CCA to detect energy exceeding a predetermined threshold or to detect a message or preamble occupying the shared channel. CAT2 LBT performs CCA without using a random backoff operation, which results in its shortened duration compared to the next category.

[0042]

[0048] The third category (CAT3 LBT) performs CCA to detect energy or messages on the shared channel, but still uses random backoff and a fixed contention window. Thus, when a node starts CAT3 LBT, the node performs a first CCA to detect occupancy of the shared channel. If the shared channel is idle over the duration of the first CCA, the node can proceed with transmission. However, if the first CCA detects a signal indicating that the shared channel is occupied, 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 has been decremented to zero, the node may start transmission 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 zero. If the random number reaches zero without any of the extended CCAs detecting channel occupancy, the node may transmit on the shared channel. If the node detects channel occupancy in any of the extended CCAs, the node may reselect a new random backoff based on the fixed contention window size to restart the countdown.

[0043]

[0049] A 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. The sequence of CCA detection proceeds in the same manner as the process of CAT3 LBT, except that the contention window size for the CAT4 LBT procedure is variable.

[0044]

[0050] The use of media sensing procedures to compete for access to unlicensed shared spectrum can, as a result, lead to communication outages. This can be particularly evident when multiple network operating entities (e.g., network operators) attempt to access shared resources. Within wireless communication system 100, base station 105 and UE 115 can be operated by the same or different network operating entities. In some examples, individual base stations 105 or UEs 115 can be operated by two or more network operating entities. In other examples, each base station 105 and UE 115 can be operated by a single network operating entity. Requiring base stations 105 and UEs 115 of different network operating entities to compete for shared resources can, as a result, increase signaling overhead and communication latency.

[0045]

[0051] In some cases, operation in the unlicensed band can be based on a carrier aggregation configuration, together with a component carrier operating in a licensed band (e.g., LAA). Operation in the unlicensed spectrum can include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or combinations thereof. Duplexing in the unlicensed spectrum can be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both.

[0046]

[0052] In some examples, base station 105 or UE 115 may be equipped with multiple antennas that can be used to utilize techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, wireless communication 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 communication may employ multipath signal propagation, sometimes called spatial multiplexing, to increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. The multiple signals may be transmitted by the transmitting device via, for example, different antennas or different combinations of antennas. Similarly, the multiple signals may be received by the 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 associated with 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 measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) where multiple spatial layers are transmitted to the same receiving device and multi-user MIMO (MU-MIMO) where multiple spatial layers are transmitted to multiple devices.

[0047]

[0053] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting device or a 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 can be achieved by combining signals communicated via the antenna elements of an antenna array such that signals propagating in a particular direction with respect to the antenna array experience constructive interference and other signals experience destructive interference. Adjusting the signals communicated via the antenna elements can include the transmitting device or the receiving device applying a particular amplitude and phase offset to the signals carried via each of the antenna elements associated with the device. The adjustment associated with each of the antenna elements can be defined by a set of beamforming weights associated with a particular direction (e.g., with respect to the antenna array of the transmitting device or the receiving device, or with respect to some other direction).

[0048]

[0054] In one example, the base station 105 may use multiple antennas or an antenna array to perform a beamforming operation for directional communication with the UE 115. For example, several signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions, which may include the signals being transmitted according to different sets of beamforming weights associated with different directions of transmission. Transmission in different beam directions can be used to identify the beam direction (e.g., by a receiving device such as the base station 105 or 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, can be transmitted by base station 105 in a single beam direction (e.g., the direction associated with a receiving device such as UE115). In some examples, the beam direction associated with transmission along a single beam direction can be determined based at least in part on signals transmitted in different beam directions. For example, UE115 can receive one or more of the signals transmitted by base station 105 in different directions, and UE115 can report to base station 105 an indication of the signal it received with the highest signal quality or some other acceptable signal quality. These techniques have been described with respect to signals transmitted by base station 105 in one or more directions, but UE115 can employ similar techniques for transmitting signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE115) or for transmitting a signal in a single direction (e.g., to transmit data to a receiving device).

[0050]

[0056] A receiving device (e.g., UE115 which can be an example of a mmW receiving device) may attempt multiple receive beams when receiving various signals from base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, the receiving device may attempt multiple receive directions by receiving via various antenna subarrays, by processing received 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 received signals according to various receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, any of which may be referred to as "listening" according to different receive beams or receive directions. In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving data signals). 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, the highest signal-to-noise ratio, or another acceptable signal quality at least in part based on listening according to multiple beam directions).

[0051]

[0057] In certain implementations, the antennas of base station 105 or UE 115 can be located within one or more antenna arrays that can support MIMO operation, or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can be collocated in an antenna assembly such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 105 can be located in diverse geographical locations. Base station 105 can have an antenna array with several rows and columns of antenna ports that the base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 can have one or more antenna arrays that can support various MIMO or beamforming operations.

[0052]

[0058] In further cases, UE 115 and base station 105 can 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 over communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer in poor radio conditions (e.g., signal-to-noise conditions). In some cases, a wireless device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback within a particular slot for data received in a previous symbol within that slot, and in other cases, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0053]

[0059] Time intervals in LTE or NR are, for example, T sIt can be represented as a multiple of a basic time unit that may refer to a sampling period of 1 / 30,720,000 seconds. The time intervals of the communication resources can be organized according to radio frames each having a duration of 10 milliseconds (ms), where the frame period is T f = 307,200T s and can be expressed as such. The radio frame can be identified by a system frame number (SFN) in the range from 0 to 1023. Each frame can include 10 subframes numbered from 0 to 9, and each subframe can have a duration of 1 ms. The subframe can be further divided into two slots each having a duration of 0.5 ms, and each slot can include six or seven modulation symbol periods (depending on, for example, the length of the cyclic prefix added at the beginning of each symbol period). Excluding the cyclic prefix, each symbol period may include 2048 sampling periods. In some cases, the subframe can be the smallest scheduling unit of the wireless communication system 100 and may be called a transmission time interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 can be shorter than a subframe or can be dynamically selected (for example, during a burst of shortened TTI (sTTI) or in a selected component carrier using sTTI).

[0054]

[0060] In some wireless communication systems, a slot can be further divided into a plurality of minislots each including one or more symbols. In some cases, the symbols or minislots of a minislot can be the smallest unit of scheduling. The duration of each symbol can vary, for example, according to the subcarrier spacing or frequency band of the operation. Further, some wireless communication systems can implement slot aggregation where a plurality of slots or minislots are aggregated together and used for communication between the UE 115 and the base station 105.

[0055]

[0061] As used herein, the term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication over communication link 125. For example, a carrier of communication link 125 may include a portion of a radio frequency spectrum band that operates 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., evolved universal terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be arranged according to a channel raster for discovery by UE 115. A carrier may be a downlink or uplink (e.g., in FDD mode) or may be configured to carry downlink communication and uplink communication (e.g., in TDD mode). In some examples, the signal waveform transmitted via 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 spread OFDM (DFT-S-OFDM)).

[0056]

[0062] The framing structure of a carrier may vary for different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR). For example, communication via a carrier may be framed according to a transmission time interval (TTI) or slot, each of which may include user data as well as control information or signaling to support decoding of the user data. A carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling to coordinate the operation of the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers.

[0057]

[0063] Physical channels can be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, the control information transmitted within a physical control channel can be distributed in a cascaded manner between different control regions (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 can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth can be one of several predetermined 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 can be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 can be configured for operation using narrowband protocol types associated with a predefined part or range (e.g., a set of subcarriers or RBs) within the carrier (e.g., "in-band" deployment of narrowband protocol types).

[0059]

[0065] In a system adopting the MCM technique, a resource element may consist of one symbol period (for example, 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 (for example, the order of the modulation scheme). Therefore, the higher the number of resource elements received by UE115 and the higher the order of the modulation scheme, the higher the data rate for UE115 may be. In an MIMO system, the wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (for example, spatial layers), and the use of multiple spatial layers may further increase the data rate for communication with UE115.

[0060]

[0066] A device (for example, base station 105 or UE115) of the wireless communication system 100 may have a hardware configuration to support communication on a specific 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 UE115 that support simultaneous communication via carriers associated with two or more different carrier bandwidths.

[0061]

[0067] The wireless communication system 100 may support a feature sometimes called communication with UE115 on multiple cells or carriers, that is, carrier aggregation or multi-carrier operation. UE115 may be composed of a plurality of downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both FDD component carriers and TDD component carriers.

[0062]

[0068] In some cases, the wireless communication system 100 may use an extended component carrier (eCC). The 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, the eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a backhaul link that is sub-optimal or not ideal). The eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., when two or more operators are permitted to use the spectrum such as NR shared spectrum (NR-SS)). The eCC characterized by a wide carrier bandwidth may include one or more segments that can be utilized by a UE 115 configured to monitor the entire carrier bandwidth or otherwise use a limited carrier bandwidth (e.g., to conserve power).

[0063]

[0069] In a further case, the eCC may utilize a symbol duration different from that of 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 sub-carriers. A device such as a UE 115 or a base station 105 that utilizes the eCC may transmit a wideband signal (e.g., in accordance with a frequency channel or a carrier bandwidth such as 20, 40, 60, 80 MHz) at the reduced symbol duration (e.g., 16.67 microseconds). The TTI within the eCC may be composed of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods within the TTI) may be variable.

[0064]

[0070] The wireless communication system 100 can be, in particular, an NR system that can utilize any combination of an authorized spectrum band, a shared spectrum band, and an unlicensed spectrum band. The flexibility of the eCC symbol duration and subcarrier spacing can enable the use of eCC across multiple spectrums. In some examples, the NR shared spectrum can increase spectrum utilization and spectral efficiency, in particular 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 the design of a base station 105 that can be one of the base stations in FIG. 1 and a UE 115 that can be one of the UEs in FIG. 1. In the base station 105, a transmission processor 220 can receive data from a data source 212 and control information from a controller / processor 240. The control information can be for PBCH, PCFICH, PHICH, PDCCH, EPDCCH, MPDCCH, etc. The data can be for PDSCH, etc. The transmission processor 220 can process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmission processor 220 can also generate reference symbols for, e.g., PSS, SSS, and cell-specific reference signals. A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, control symbols, and / or reference symbols, if applicable, and provide an output symbol stream to modulators (MOD) 232a - 232t. Each modulator 232 can process its respective output symbol stream to obtain an output sample stream (e.g., for OFDM, etc.). Each modulator 232 can further process the output sample stream (e.g., convert to analog, amplify, filter, and up-convert) to obtain a downlink signal. The downlink signals from modulators 232a - 232t can be transmitted via antennas 234a - 234t, respectively.

[0066]

[0072] In UE 115, antennas 252a to 252r can receive a downlink signal from base station 105 and can provide the received signals to respective demodulators (DEMOD) 254a to 254r. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the respective received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 can obtain received symbols from all the demodulators 254a to 254r, and when applicable, perform MIMO detection on the received symbols and provide the detected symbols. The receive processor 258 can process the detected symbols (e.g., demodulate, de-interleave, and decode), provide the decoded data for UE 115 to the data sink 260, and provide the decoded control information to the controller / processor 280.

[0067]

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

[0068]

[0074] The controllers / processors 240 and 280 can each direct operations in the base station 105 and the UE 115, respectively. The controller / processor 240 in the base station 105 and / or other processors and modules can perform or direct the performance of various processes for the techniques described herein. The controller / processor 280 in the UE 115 and / or other processors and modules can also perform or direct the performance of the functional blocks shown in FIG. 3 and / or other processes for the techniques described herein. The memories 242 and 282 can each store data and program code for the base station 105 and the UE 115, respectively. The scheduler 244 can schedule UEs for data transmission on the downlink and / or the uplink.

[0069]

[0075] In NR-U operation, it is considered in the context of a grant (CG) resource with channel occupancy time (COT) sharing configured. Each CG resource may include periodic uplink resources and may be associated with a set of hybrid automatic repeat request (HARQ) identification information. Before each uplink transmission within a CG resource, the UE may perform Cat-4 LBT to secure access to the shared communication channel. After successful LBT, the UE may transmit multiple uplink transmissions (e.g., PUSCH) without any transmission gap until the end of the COT. The COT obtained by the UE may be shared with the serving base station to transmit or broadcast control or data to the UE. COT sharing may be useful when the UE does not perform uplink transmissions over the entire COT duration. The serving base station may share the COT by performing any short LBT (e.g., Cat-2 LBT) or without performing the LBT procedure. To enable COT sharing, the UE may provide COT sharing information within an uplink control indicator (UCI) message regarding the obtained COT. Various aspects of the present disclosure relate to the identification and use of such CG-UCI information regarding COT sharing and the manner in which the serving base station performs CG UL transmissions to enable the execution of short LBT.

[0070]

[0076] FIG. 3 is a block diagram illustrating exemplary blocks executed to implement one aspect of the present disclosure. Also, the exemplary blocks are described with respect to UE 115 as shown in FIGS. 2 and 7. FIG. 7 is a block diagram showing UE 115 configured according to one aspect of the present disclosure. UE 115 includes a structure, hardware, and components as shown for UE 115 in FIG. 2. For example, UE 115 operates to execute logic or computer instructions stored in memory 282 and includes a controller / processor 280 that controls the components of UE 115 that provide the features and functions of UE 115. Under the control of controller / processor 280, UE 115 transmits and receives signals via wireless radios 700a - r and antennas 252a - r. Wireless radios 700a - r include various components and hardware including modulators / demodulators 254a - r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266 as shown for UE 115 in FIG. 2.

[0071]

[0077] In block 300, the UE obtains the COT in response to the detected success of the UE's LBT procedure on the shared communication channel. A UE such as UE115 obtains the configured grant configuration information and stores it in the memory 282 in the configured grant configuration 701. UE115 may receive such configured grant configuration information from the configuration signal by the serving base station via the antennas 252a - r and the wireless radios 700a - r. The configured grant configuration 701 provides UE115 with the identification information, start point, end point, etc. of the resources for UE115 to transmit uplink data without a scheduled grant when the uplink data exists in the data buffer 706 in the memory 282. With the knowledge of the configured grant uplink resources on the shared communication spectrum, UE115 may attempt to secure the COT by executing the LBT logic 702 in the memory 282. Under the control of the controller / processor 280, UE115 executes the LBT logic 702, and as a result, in addition to the wireless radios 700a - r and the antennas 252a - r, it brings commands and controls for various components of UE115 as described in more detail in FIG. 2. When executing the LBT logic 702, in the environment (the "execution environment") created within UE115 when executing the instructions and controlling various hardware and components, UE115 may monitor the common communication channel via the antennas 252a - r and the wireless radios 700a - r to detect the energy level on the shared communication channel. If an energy level exceeding the energy detection (ED) threshold is not detected, UE115 may detect the success of the LBT procedure within the execution environment of the LBT logic 702. Upon detection of a successful LBT procedure, UE115 obtains the COT on the shared communication channel.

[0072]

[0078] In block 301, the UE determines whether COT sharing is enabled or not. To support COT sharing, UE 115 executes COT sharing logic 703 stored in memory 282 under the control of controller / processor 280. The execution environment of COT sharing logic 703 determines whether COT sharing is enabled, and if so, provides UE 115 with the functions and controls of various hardware and components for monitoring its transmission to share the UE start COT with the serving base station when the UE will not transmit across the entire COT. In one exemplary aspect, within the execution environment of COT sharing logic 703, UE 115 may detect whether the ED threshold for the LBT procedure used according to LBT logic 702 to acquire the COT is configured by the serving base station for COT sharing. If not configured, UE 115 may determine that COT sharing is not enabled. Otherwise, if the ED threshold is configured by the serving base station for COT sharing, UE 115 may determine that COT sharing is enabled. In a further aspect, the execution environment of COT sharing logic 703 may operate to prompt UE 115 to detect configuration information received from the serving base station via antennas 252a - r and wireless radios 700a - r that configures which COT sharing information should be included in the uplink control message to the serving base station, or configures COT sharing as either enabled or not enabled. Based on these additional serving base station configurations, UE 115 will determine whether COT sharing is enabled or not.

[0073]

[0079] In block 302, the UE identifies COT sharing information for communicating with the serving base station within an uplink control message, where the COT sharing information is identified according to the determination. The COT sharing information 704 stored in the memory 282 can be identified as specific COT sharing information to be shared between the UE 115 and the serving base station according to whether COT sharing is enabled. The COT sharing information 704 includes the remaining COT duration or COT end point indicating how long downlink transmission can be performed by the serving base station, an offset indication indicating where UE transmission is expected to end, or at which time instance the base station can perform short LBT, and a channel access priority class (CAPC) used by the UE for COT acquisition. The CAPC enables the serving base station to determine what types of data can be included in its downlink communication within the shared COT. When the UE 115 determines that COT sharing is enabled, the UE 115 can include all of this COT sharing information within the uplink control message. Further, the COT sharing information 704 can be coded or compressed to reduce the signaling overhead of the information for inclusion within the uplink control message. When the UE 115 determines that COT sharing is not enabled, the UE 115 can 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 the CAPC or, in some cases, other COT sharing information for inclusion within 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. The execution of the UCI generator 705 provides the UE 115 with functions 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 having COT sharing information to the serving base station. By executing the UCI generator 705, when an uplink control message is generated and includes the identified COT sharing information, the UE 115 may transmit the uplink control message to the serving base station via the wireless radios 700a - r and the antennas 252a - r under the control of the controller / processor 280.

[0075]

[0081] FIG. 4 is a block diagram showing a communication interaction between a UE 115a having COT sharing capabilities configured according to one aspect of the present disclosure and a base station 105. 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 within the shared communication channel. To attempt to access the shared communication channel, the UE 115a performs Cat-4 LBT 400. If successful, the UE 115a obtains a COT 401 for uplink transmission 402.

[0076]

[0082] It is suggested that COT sharing may be affected 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 Cat-4 LBT 400 to obtain a COT 401 that can be shared with a serving base station such as the base station 105 is configured by the base station 105 via the configuration information 405, such as via RRC signaling. The base station 105 may be any of: configuring an ED threshold for COT sharing, configuring a standard ED threshold not targeted at COT sharing, or simply not configuring an ED threshold for COT sharing. If not configured, the UE 115a will be in a default state of using a standard ED threshold not targeted at COT sharing when performing the Cat-4 LBT 400 procedure to secure a COT 401 on the shared communication channel.

[0077]

[0083] When the ED threshold is not configured for COT sharing, when UE 115a stops uplink transmission 402 before the end point 404 of COT 401, base station 105 may still perform downlink transmission 407 within the remaining COT duration 403. However, in such a scenario, the downlink transmissions 407 of base station 105 within UE-initiated COT 401 may each be limited to control signals, broadcast signals, or control channel transmissions or broadcast channel transmissions of up to 2, 4, or 8 OFDM symbols in duration for subcarrier spacings of 15 kHz, 30 kHz, or 60 kHz subcarrier spacing (SCS). In such a scenario, when COT sharing is not enabled, some of the COT sharing information provided within uplink control indicator (UCI) message 406 may be redundant (e.g., CAPC duration, COT duration, etc.). Further, in some cases, base station 105 may not be interested in COT sharing. Thus, UE 115a may determine, based on configuration information 405 from base station 105, which of the fields of the COT sharing information may be included within UCI 406.

[0078]

[0084] According to one aspect of the present disclosure, the COT sharing information that will be included in the configured grant uplink control message, UCI406, may depend on whether a COT sharing ED threshold is configured. When the COT sharing ED threshold is not configured, UE115a may hold or remove the CAPC and reduce the bandwidth of the remaining COT duration within UCI406. In one exemplary implementation, UE115a may completely remove the COT duration field. However, UE115a should still ensure that there is enough space within COT401 to allow the serving base station to send the downlink transmission 407 by restricting its uplink transmission 402. In another exemplary implementation, UE115a may include a 1-bit value in UCI406 indicating whether the base station 105 is allowed to send or broadcast control signaling or data signaling using the COT401 acquired by UE115a. This may be determined based on whether the remaining COT duration 403 is sufficient for broadcast transmission or control transmission. In another exemplary implementation, UE115a may include some symbols available for broadcast transmission or control transmission within the COT401 acquired by UE115a using UCI406. This number may be based on a reference numerology (e.g., the highest SCS supported by UE115a, or 60 kHz, or the SCS of the active BWP).

[0079]

[0085] According to another aspect of the present disclosure, the base station 105 may directly configure the UE 115a using which fields for inclusion in the UCI 406. For example, the base station 105 can indicate in the configuration information 405 whether to include the CAPC, and can 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 the CAPC and the remaining COT duration 403 or the COT end 404 are excluded from the uplink control message (e.g., UCI 406), the UE 115a may assume that COT sharing is disabled. In such a case, the UE 115a will use the standard ED threshold that is not configured to share instead of the COT sharing ED threshold.

[0080]

[0086] According to another aspect of the present disclosure, the serving base station, the base station 105, may directly configure the UE 115a via the configuration information 405 as to whether COT sharing is enabled. Based on this enabling configuration, the UE 115a may determine which COT sharing information fields should be included in the UCI 406. When the base station 105 configures COT sharing as enabled in the configuration information 405, the UE 115a may use the COT sharing ED threshold, but when the base station 105 configures COT sharing as not enabled in the configuration information 405, the UE 115a may use the standard ED threshold instead of the COT sharing ED threshold.

[0081]

[0087] UE 115a may initiate configured grant transmission, uplink transmission 402, within a slot, such as when based on a mini-slot configuration and the addition of a cyclic prefix (CP). Thus, the time instance of COT end 404 can 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 when the number of PUSCH start points is large within a slot. Similarly, UE 115a may terminate configured grant transmission, uplink transmission 402, at any symbol within the slot when COT end 404 occurs within a given symbol within the slot. Thus, the number of COT sharing information bits may even be large enough to indicate the transmission end offset value within UCI 406. A further aspect of the present disclosure relates to compressing this type of COT sharing information.

[0082]

[0088] In one aspect of the present disclosure, UE115a may reduce the signaling of the remaining COT duration 403 and the remaining transmission time within UCI406. Since the transmission end time will occur earlier than the COT end 404, UE115a may code this information together and compress it into UCI406. Similarly, CAPC may also be compressed together if the transmission end point is affected based on the selected CAPC value. For different CAPCs, the COT duration may be different. Towards higher 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 CAPC. Each entry into the RIV table may provide a combination of CAPC, the remaining transmission time, and the remaining COT duration. Each of UE115a and base station 105 has a copy of this RIV table. The RIV table may further use the slot granularity, multiple symbols, or the mini-slot level. To further compress the signaling of the remaining transmission time, the signaling may utilize the fact that the uplink transmission ends at the PUSCH end boundary configured by base station 105 within the configuration information 405. The signaling of the remaining COT duration 403 may also be compressed by utilizing 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 end boundary of the PUSCH slot and the PUSCH start point for the remaining transmission time and the remaining COT duration, respectively. UE115a will include an index to the RIV table for the desired entry and a collection of COT shared information for inclusion within UCI406.

[0083]

[0089] In another aspect of the present disclosure, the transmission end point and the remaining COT duration can be coded together by using the start-length indicator value (SLIV) technique. In a first exemplary implementation, the start value and the length value of the SLIV can each have the granularity of the PUSCH end point and the PUSCH start point configured by the base station 105. In a second exemplary implementation, the SLIV table provides the end point offset and the remaining COT duration at a coarser granularity, such that both the start value and the length value are provided in sequence on the slot, or the start value has the granularity of the PUSCH transmission end point configured by the base station 105 within the configuration information 405 and the length value has the granularity of the slot, or the start value has the granularity of the slot and the length value has the granularity of the PUSCH start point. If no other information is provided, the base station 105 may operate with an approximation. Here too, the UE 115 will include an index to the SLIV table that indicates the desired set of start-length indicator values within the UCI 406. 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] It should be noted that a further aspect of the present disclosure can be realized by the UE 115a including an additional COT sharing information field within the UCI 406 to correct the values indicated by the SLIV table. For example, the exact transmission end point within the slot can be indicated in a separate field within the UCI 406, in which the bandwidth can be determined based on the PUSCH transmission end point enabled within the slot. In addition, the exact COT end 404 within the slot can be indicated based on the granularity of the PUSCH transmission start point.

[0085]

[0091] A further aspect of the present disclosure relates to individually compressing both the transmission end point and the remaining COT duration 403. The COT duration bit width can be derived based on the PUSCH start point granularity. For example, UE 115a can indicate the number of remaining slots, in addition to the end symbol within the slot in UCI 406, whose bit width can be based on the mini-slot start point configured by base station 105 within configuration information 405. The offset indicator identifying the end of the uplink transmission 402 can also be compressed, such as by enabling UE 115a to end its transmission at the base-station-configured PUSCH end point. In such an aspect, UE 115a will indicate the end slot number and the end symbol within the slot in UCI 406, whose bit width can be based on the PUSCH end point configured by base station 105 within configuration information 405. In an additional exemplary implementation, UE 115a can be enabled to end its uplink transmission 402 at the end of the slot or anywhere within the slot when the COT end 404 falls within the slot. UE 115a can indicate this end point within the number of the slot, and if the end point occurs before the COT end 404, the base station can assume an end at the slot boundary. Otherwise, base station 105 can determine the end symbol based on the remaining COT duration 403.

[0086]

[0092] FIG. 5 is a block diagram showing a portion of an NR-U network 50 including a UE 115a having COT sharing capabilities configured according to one aspect of the present disclosure and a base station 105. In a further aspect of the present disclosure, the UE 115a may be configured to signal COT sharing information at a fixed position prior to the end of an uplink transmission. For example, the UE 115a may signal COT sharing information within a UCI message within a PUSCH transmission occurring within two slots, SN-1 and SN, prior to the uplink transmission end point 503. Thus, if the UE 115a uses ten slots for its uplink transmission within the COT 500, the first eight slots may include UCI that indicates nothing about COT sharing (e.g., remaining COT duration = 0), and within the last two slots, SN-1 and SN, the UE 115a may include UCI that indicates COT sharing information and that COT sharing will occur after a certain number of slots or after the current slot. The uplink transmission end point 503 will be calculated from these last two slots, SN-1 and SN, and thus the number of bits used for such an indication may be significantly reduced. For example, if the UE 115a were reporting UCI indicating COT sharing from the first slot S0, the length to the end point 503 would be 505, and indicating COT sharing within the last two slots, SN-1 and SN, would represent 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 specific COT sharing 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 the UE startup COT occurs, the serving base station may execute a shortened LBT procedure (e.g., 25 μs or 16 μs Cat-2 LBT) or not execute any LBT before starting downlink transmission. Which LBT the base station executes can be determined based on the LBT capabilities supported by the base station. In either case of LBT type, the UE will recognize that it needs to provide a sufficient gap between the end of the uplink transmission and the end of the COT for the base station to execute the appropriate LBT procedure. For example, in the case of 25 μs Cat-2 LBT, the UE will end its uplink transmission at least 25 μs before the slot boundary or the mini-slot boundary.

[0089]

[0095] Figures 6A - 6C are block diagrams showing a UE 115a having COT sharing capabilities configured according to aspects of the present disclosure and a base station 105. The UE 115a successfully executes a Cat-4 LBT 600 to acquire a COT 601 within the shared communication channel until the COT end 605. When the UE 115a ends its uplink transmission 602 at a time earlier than the slot boundary or the mini-slot boundary or the PUSCH boundary, the UE 115a may determine the transmission block (TB) size 603 in a plurality of ways. For example, as shown in Figure 6A, the TB size 603 may be selected based on the original end point 604, such as the configured PUSCH boundary, by performing rate matching based on the pulled-in end point 608. The "pulled-in" end point 608 represents the end point selected by the UE 115a to provide the base station 105 with sufficient time to execute the 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 execute the shortened LBT procedure. This prompts the UE 115a to pull the end point of the uplink transmission 602 within the pulled-in end point 608. In addition to the gap 606, an additional time gap 607 provides the base station 105 with sufficient time to execute its LBT procedure for downlink transmission.

[0090]

[0096] In a second exemplary implementation shown in FIG. 6B, the TB size 603 performs rate matching based on the original end point 604, and the base station 105 punctures the remaining symbols 609 (between the pull-in end point 608 and the original end point 604) for performing its LBT procedure, which may be selected based on the original end point 604. In a third exemplary implementation shown in FIG. 6C, the TB size 610 performs rate matching based on the pull-in end point 608, which may be selected based on the pull-in end point 608.

[0091]

[0097] In a further aspect, assuming that a small number of symbols are used for uplink transmission, assuming that the actual number of symbols are used for uplink transmission, or assuming that a larger number of symbols are used for uplink transmission, regardless of the actual number of symbols used for uplink transmission, a grant UCI multiplexing configured in any of these ways may be performed.

[0092]

[0098] Alternatively, the base station may configure multiple configurations using different end points. The UE may then select one of the configurations and report the selection in the UCI message. In one exemplary implementation of the base station configuration, the UE selects all slots with all symbols (0 to 13). In another exemplary implementation of the base station configuration, the UE may select all slots with symbols 0 to 12 in all slots. In a further exemplary implementation of the base station configuration, the UE selects slots 0 to N-1 with all symbols, and slot N has 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 understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0094]

[0100] The functional blocks and modules of FIG. 3 can comprise a processor, an electronic device, a hardware device, an electronic component, a logic circuit, a memory, software code, firmware code, etc., or any combination thereof.

[0095]

[0101] Those skilled in the art will further appreciate that the various exemplary logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in varying 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 recognize that the order or combination of the components, methods, or interactions described herein are merely examples, and that the components, methods, or interactions of the various aspects of the present disclosure can 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 a plurality of different aspects and optional implementations. For example, a first aspect of wireless communication according to the present disclosure includes 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; identifying, by the UE, COT sharing information for communicating with a serving base station in an uplink control message, where the COT sharing information is identified according to the determining; and transmitting, by the UE, an uplink control message having the COT sharing information to the serving base station.

[0097]

[0103] A second aspect based on the first aspect, where the COT sharing information includes one or more of the remaining COT duration from the end of one of the UE uplink transmissions in the COT or the PUSCH transmission including the COT sharing information to the end point of the COT, an offset indication for identifying the end of the UE uplink transmission, and the CAPC used by the UE for obtaining the COT.

[0098]

[0104] A third aspect based on the second aspect, where the determining includes identifying the ED threshold configuration of the UE; determining that COT sharing is enabled in response to identifying that the ED threshold configuration is configured for sharing; and determining that COT sharing is not enabled in response to identifying that the ED threshold configuration is not configured for sharing.

[0099]

[0105] A fourth aspect based on the third aspect, wherein identifying the COT sharing information includes one of: identifying the remaining COT duration, an offset indication, and a CAPC for an uplink control message when COT sharing is determined to be enabled; or identifying, for an uplink control message when COT sharing is determined not to be enabled, an offset indication, removal of the CAPC, the remaining COT duration, a 1-bit flag indicating whether the serving base station is allowed to transmit during the remainder of the COT, or an indication of the number of symbols available for use by the serving base station for transmission.

[0100]

[0106] A fifth aspect based on the second aspect, wherein determining includes receiving a configuration message from the serving base station, and wherein the configuration message includes an identification of COT sharing information for inclusion within an uplink control message; and determining whether COT sharing is to be enabled or not based on the identification of the COT sharing information within the configuration message.

[0101]

[0107] A sixth aspect based on the fifth aspect, wherein determining whether COT sharing is to be enabled or not includes identifying that the configuration message indicates excluding the CAPC and the remaining COT duration from the uplink control message, and wherein the UE determines that COT sharing is not to be enabled in response to identifying the configuration message.

[0102]

[0108] A seventh aspect based on the sixth aspect, further including using an ED threshold configuration for an LBT procedure not configured for sharing in response to the UE identifying that COT sharing is not to be enabled.

[0103]

[0109] An eighth aspect based on the second aspect, wherein 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 including, by the UE, using an ED threshold configuration for an LBT procedure not configured for sharing in response to identifying COT sharing as not enabled.

[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 identifying one or more of a remaining COT duration, an offset indication shown as a remaining transmission time, and CAPC correspondence.

[0106]

[0112] An eleventh aspect based on the tenth aspect, wherein the table uses a RIV to compress the remaining COT duration and the remaining transmission time.

[0107]

[0113] A twelfth aspect based on the eleventh aspect, wherein the RIV indicates one or more of a remaining transmission time as a PUSCH slot boundary at which the UE uplink transmission will end and a remaining COT duration having a granularity of a start 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 uses a start and length indicator value (SLIV) to code the remaining COT duration and the offset indication together.

[0109]

[0115] Based on the 13th aspect, a 14th aspect, wherein the length value of the SLIV is indicated in terms of the granularity of the PUSCH transmission start point, and wherein the PUSCH start point is configured by the serving base station.

[0110]

[0116] Based on the 13th aspect, a 15th aspect, wherein the start value of the SLIV is indicated in terms of the granularity of one of the slot or the PUSCH transmission end point, and the length value of the SLIV is indicated in terms of the granularity of one of the slot or the PUSCH transmission start point.

[0111]

[0117] A 16th aspect based on the 13th aspect, further including adding, by the UE, corrective information to the uplink control message, wherein the corrective information corrects one or more values in the table indicated by the SLIV.

[0112]

[0118] A 17th aspect based on the 2nd aspect, further including compressing the remaining COT duration in the uplink control message, wherein compressing the remaining COT duration is performed by the UE to indicate the number of remaining COT slots and the end symbol in the last slot among the number of remaining COT slots; and compressing the offset indication in the uplink control message, wherein compressing the offset indication is performed by the UE to indicate either the end slot number and the last symbol of the UE uplink transmission in the end slot number, or the number of remaining transmission slots.

[0113]

[0119] A 18th aspect based on the 2nd aspect, further including obtaining, by the UE, the reporting location, wherein the reporting location identifies the number of slots before the end of the UE uplink transmission in which the UE transmits an uplink control message having COT sharing information to the serving base station, and wherein 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.

[0114]

[0120] The UE determines a time gap between the end of UE uplink transmission and a subsequent downlink transmission start opportunity; the UE ends 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 short downlink LBT according to the LBT capability; the UE ends the UE uplink transmission at an ending point before the end of the UE uplink transmission in response to the minimum time exceeding the time gap, where an extended time gap during the ending point before the end of the UE uplink transmission is sufficient to adapt to the minimum time for the serving base station to perform short LBT; the 19th aspect based on the second aspect, further including.

[0115]

[0121] Ending of UE uplink transmission with rate matching based on an ending point before the end of UE uplink transmission; ending of UE uplink transmission with rate matching based on the end of UE uplink transmission, where the UE punctures resources related to the extended time gap; or determining a transport block size for UE uplink transmission based on one of the ending points before the end of UE uplink transmission with rate matching based on an ending point before the end of UE uplink transmission, the 20th aspect based on the 19th aspect, further including.

[0116]

[0122] The 21st aspect based on the 20th aspect, where transmitting an uplink control message includes multiplexing the uplink control message according to one of a first number of multiplexing symbols less than the 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 greater than the actual number of multiplexing symbols based on the end of the UE uplink transmission used.

[0117]

[0123] A 22nd aspect based on the first aspect, further comprising: obtaining, by a 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, where the configuration indicator identifies the transmission configuration for the serving base station.

[0118]

[0124] A 23rd aspect configured for wireless communication may comprise: means for obtaining, by a UE, a COT in response to a detected success of the UE's LBT procedure on a shared communication channel; means for determining, by the UE, whether COT sharing is enabled or not; means for identifying, by the UE, COT sharing information for communicating with a serving base station within an uplink control message, where the COT sharing information is identified according 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, where the COT sharing information includes one or more of: the remaining COT duration from the end of one of the UE uplink transmissions within the COT or a PUSCH transmission including the COT sharing information to the end point of the COT; an offset indication identifying the end of the UE uplink transmission; and a CAPC used by the UE for obtaining the COT.

[0120]

[0126] A 25th aspect based on the 24th aspect, where the means for determining includes: means for identifying a UE energy detection (ED) threshold configuration; means for determining that COT sharing is enabled in response to the identification of the ED threshold configuration being configured for sharing; and means for determining that COT sharing is not enabled in response to the identification of the ED threshold configuration not being configured for sharing.

[0121]

[0127] According to the 25th aspect, in the 26th aspect, the means for identifying COT sharing information includes means for identifying the remaining COT duration, an offset indication, and the CAPC for the uplink control message when it is determined that COT sharing is enabled, or for the uplink control message when it is determined that COT sharing is not enabled, an offset indication, removal of the CAPC, the remaining COT duration, a 1-bit flag indicating whether the serving base station can be transmitted during the remaining period of the COT, or an indication of the number of symbols available for transmission by the serving base station, including one or more of the means for identification.

[0122]

[0128] According to the 24th aspect, in the 27th aspect, the means for determining includes means for receiving a configuration message from the serving base station, where the configuration message includes identification of COT sharing information for inclusion in the uplink control message; and means for determining whether COT sharing is enabled or not based on the identification of COT sharing information in the configuration message.

[0123]

[0129] According to the 27th aspect, in the 28th aspect, the means for determining whether COT sharing is enabled or not includes means for identifying that the configuration message indicates excluding the CAPC and the remaining COT duration from the uplink control message, where the UE determines that COT sharing is not enabled in response to identifying the configuration message.

[0124]

[0130] The 29th aspect based on the 28th aspect further includes means for the UE to use an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identifying that COT sharing is not enabled.

[0125]

[0131] The 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.

[0126]

[0132] The 31st aspect based on the 30th aspect, further including means for the UE 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.

[0127]

[0133] The 32nd aspect based on the 24th aspect, wherein the COT sharing information includes an index to a table shared by the UE and the serving base station, and the table includes a plurality of entries each identifying one or more of the remaining COT duration, an offset indication shown as the remaining transmission time, and correspondence with CAPC.

[0128]

[0134] The 33rd aspect based on the 32nd aspect, wherein the table uses a resource indicator value (RIV) to compress the remaining COT duration and the remaining transmission time.

[0129]

[0135] The 34th aspect based on the 33rd aspect, wherein the RIV indicates one or more of the remaining transmission time as the PUSCH slot boundary at which the UE uplink transmission will end, and the remaining COT duration having the granularity of the start location of the UE uplink transmission configured by the serving base station.

[0130]

[0136] The 35th aspect based on the 32nd aspect, wherein the table codes the remaining COT duration and the offset indication together using a start and length indicator value (SLIV).

[0131]

[0137] Based on the 35th aspect, a 36th aspect, wherein the length value of the SLIV is indicated in terms of the granularity of the PUSCH transmission start point, and wherein the PUSCH start point is configured by the serving base station.

[0132]

[0138] Based on the 35th aspect, a 37th aspect, wherein the start value of the SLIV is indicated in terms of the granularity of one of the slot or the PUSCH transmission end point, and the length value of the SLIV is indicated in terms of the granularity of one of the slot or the PUSCH transmission start point.

[0133]

[0139] A 38th aspect based on the 35th aspect, further including means for the UE to add correction information to the uplink control message, wherein the correction information corrects one or more values in the table indicated by the SLIV.

[0134]

[0140] A 39th aspect based on the 24th aspect, further including means for compressing the remaining COT duration in the uplink control message, wherein the means for compressing the remaining COT duration includes means for the UE to indicate the number of remaining COT slots and the end symbol in the last slot of the number of remaining COT slots; and means for compressing the offset indication in the uplink control message, wherein the means for compressing the offset indication includes, for the UE, means for indicating the end slot number and the last symbol of the UE uplink transmission in the end slot number, or means for indicating the number of remaining transmission slots.

[0135]

[0141] A 40th aspect based on the 24th aspect, further comprising means for the UE to obtain a reporting location, wherein the reporting location identifies the number of slots before the end of UE uplink transmission for means for the UE to send an uplink control message having COT sharing information to a serving base station, and wherein the remaining COT duration and offset indication are calculated by the UE from the number of slots before the end of UE uplink transmission.

[0136]

[0142] A 41st aspect based on the 24th aspect, further comprising: means for the UE to determine a time gap between the end of UE uplink transmission and the subsequent downlink transmission start opportunity; means for the UE to end UE uplink transmission at the end of UE uplink transmission in response to the time gap exceeding a minimum time for the serving base station to perform short downlink LBT according to LBT capabilities; and means for the UE to end UE uplink transmission during an end period before the end of UE uplink transmission in response to the minimum time exceeding the time gap, wherein the extended time gap during the end period before the end of UE uplink transmission is sufficient to adapt to the minimum time for the serving base station to perform short LBT.

[0137]

[0143] A 42nd aspect based on the 41st aspect, further comprising: ending UE uplink transmission with rate matching based on an end period before the end of UE uplink transmission; ending UE uplink transmission with rate matching based on the end of UE uplink transmission, wherein the UE punctures resources related to an extended time gap; or means for determining a transport block size for UE uplink transmission based on one of the end periods before the end of UE uplink transmission with rate matching based on an end period before the end of UE uplink transmission.

[0138]

[0144] According to the 42nd aspect, the 43rd aspect, wherein the means for transmitting an uplink control message includes: a first number of multiplexing symbols less than the 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 greater than the actual number of multiplexing symbols based on the end of the UE uplink transmission used, and includes means for multiplexing the uplink control message according to one of them.

[0139]

[0145] According to the 23rd aspect, the 44th aspect further includes: means for the UE to obtain a set of transmission configurations from the serving base station; means for the UE to select a transmission configuration from the set of transmission configurations; and means for the UE to add a configuration indicator to the uplink control message, wherein the configuration indicator identifies the transmission configuration for the serving base station.

[0140]

[0146] The 45th aspect may include a non-transitory computer-readable medium having program code recorded thereon, the program code including program code executable by a computer to cause the computer to obtain a COT for the UE in response to a detected success of the UE's LBT procedure on a shared communication channel, program code executable by a computer to cause the computer to determine whether COT sharing is enabled or not by the UE, program code executable by a computer to cause the computer to identify COT sharing information for communicating with the serving base station within the uplink control message by the UE, wherein the COT sharing information is identified in response to the execution of the program code executable by the computer to cause the computer to determine, and program code executable by a computer to cause the computer to transmit an uplink control message having the COT sharing information to the serving base station by the UE.

[0141]

[0147] According to the 45th aspect, a 46th aspect, wherein the COT sharing information includes one or more of the remaining COT duration from the end of one of the UE uplink transmission within the COT or the PUSCH transmission including the COT sharing information to the end point of the COT, an offset indication for identifying the end of the UE uplink transmission, and a CAPC used by the UE for obtaining the COT.

[0142]

[0148] According to the 46th aspect, a 47th aspect, wherein the program code executable by a computer to cause the computer to make a determination includes program code executable by the computer to cause the computer to identify the ED threshold configuration of the UE, program code executable by the computer to cause the computer to determine that COT sharing is enabled according to the identification of the ED threshold configuration configured for sharing, and program code executable by the computer to cause the computer to determine that COT sharing is not enabled according to the identification of the ED threshold configuration not configured for sharing.

[0143]

[0149] According to the 47th aspect, a 48th aspect, wherein the program code executable by a computer to cause the computer to identify COT sharing information includes program code executable by the computer to cause the computer to identify the remaining COT duration, the offset indication, and the CAPC for the uplink control message when COT sharing is determined to be enabled, or program code executable by the computer to cause the computer to identify one or more of the offset indication, the removal of the CAPC, the remaining COT duration, a 1-bit flag indicating whether the serving base station can transmit during the remaining period 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 COT sharing is determined not to be enabled.

[0144]

[0150] Based on the 46th aspect, the 49th aspect, wherein the program code executable by a computer for causing the computer to determine includes program code executable by the computer for causing the computer to receive a configuration message from a serving base station, and wherein the configuration message includes identification of COT sharing information for inclusion in an uplink control message, and program code executable by the computer for causing the computer to determine whether COT sharing is enabled or not based on the identification of the COT sharing information in the configuration message.

[0145]

[0151] Based on the 49th aspect, the 50th aspect, wherein the program code executable by a computer for causing the computer to determine whether COT sharing is enabled or not includes program code executable by the computer for causing the computer to identify that a configuration message indicates excluding CAPC and the remaining COT duration from an uplink control message, and wherein the UE determines that COT sharing is not enabled in response to execution of the program code executable by the computer for causing the computer to identify the configuration message.

[0146]

[0152] The 51st aspect based on the 50th aspect, further including program code executable by a computer for causing the computer to cause the UE to use an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identification of COT sharing as not enabled.

[0147]

[0153] A 52nd aspect based on the 46th aspect, wherein the program code executable by a computer for causing the computer to determine includes program code executable by the computer for causing the computer to receive a configuration message from a serving base station, wherein the configuration message indicates whether COT sharing is enabled or not.

[0148]

[0154] A 53rd aspect based on the 52nd aspect, further including program code executable by a computer for causing the computer to cause a computer to use an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identification of COT sharing as not enabled by a UE.

[0149]

[0155] A 54th aspect based on the 46th aspect, wherein the COT sharing information includes an index to a table shared by a UE and a serving base station, wherein the table includes a plurality of entries each identifying one or more of a remaining COT duration, an offset indication shown as a remaining transmission time, and correspondence with a CAPC.

[0150]

[0156] A 55th aspect based on the 54th aspect, wherein the table uses a resource indicator value (RIV) to compress a remaining COT duration and a remaining transmission time.

[0151]

[0157] A 56th aspect based on the 55th aspect, wherein the RIV indicates one or more of a remaining transmission time as a PUSCH slot boundary at which a UE uplink transmission is to end and a remaining COT duration having a granularity of a start location of a UE uplink transmission configured by a serving base station.

[0152]

[0158] Aspect 57, based on Aspect 54, where the table codes together the remaining COT duration and the offset indication using start and length indicator values (SLIV).

[0153]

[0159] Aspect 58, based on Aspect 57, where the length value of the SLIV is indicated at the granularity of the PUSCH transmission start point, where the PUSCH start point is configured by the serving base station.

[0154]

[0160] Aspect 59, based on Aspect 57, where the start value of the SLIV is indicated at the granularity of one of the slot or the PUSCH transmission end point, and the length value of the SLIV is indicated at the granularity of one of the slot or the PUSCH transmission start point.

[0155]

[0161] Aspect 60, based on Aspect 57, further including program code executable by a computer to cause the UE to add correction information to an uplink control message, where the correction information modifies one or more values in a table indicated by the SLIV.

[0156]

[0162] The computer further includes program code executable by the computer to cause the remaining COT duration to be compressed within an uplink control message, wherein the program code executable by the computer to cause the remaining COT duration to be compressed includes program code executable by the computer to cause the computer, by the UE, to indicate the number of remaining COT slots and the end symbol within the last slot of the number of remaining COT slots, and program code executable by the computer to cause the computer to compress an offset indication within the uplink control message, and the program code executable by the computer to cause the computer to compress the offset indication includes program code executable by the computer to cause the computer, by the UE, to indicate the end slot number and the last symbol of the UE uplink transmission within the end slot number, or program code executable by the computer to cause the computer, by the UE, to indicate the number of remaining transmission slots, according to a 61st aspect based on a 46th aspect.

[0157]

[0163] The computer further includes program code executable by the computer to cause the UE to obtain a reporting location, wherein the reporting location identifies, during which, the number of slots before the end of a UE uplink transmission in which program code executable by the computer to cause the computer to transmit an uplink control message having COT sharing information to a serving base station is executed by the UE, and wherein 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, according to a 62nd aspect based on a 46th aspect.

[0158]

[0164] Program code executable by a computer to cause a computer, by a UE, to determine a time gap between the end of UE uplink transmission and a subsequent downlink transmission start opportunity, program code executable by a computer to cause a computer, by a UE, to end UE uplink transmission at the end of UE uplink transmission in response to the time gap exceeding a minimum time for a serving base station to perform short downlink LBT according to LBT capabilities, program code executable by a computer to cause a computer, by a UE, to end UE uplink transmission during an end period before the end of UE uplink transmission in response to the minimum time exceeding the time gap, wherein an extended time gap during the end period before the end of UE uplink transmission is sufficient to adapt to the minimum time for the serving base station to perform short LBT, a 63rd aspect based on a 46th aspect further comprising this.

[0159]

[0165] Program code executable by a computer to cause a computer, by a UE, to end UE uplink transmission with rate matching based on an end period before the end of UE uplink transmission, end UE uplink transmission with rate matching based on the end of UE uplink transmission, wherein the UE punctures resources related to an extended time gap, or determine a transport block size for UE uplink transmission based on one of the end periods before the end of UE uplink transmission with rate matching based on an end period before the end of UE uplink transmission, a 64th aspect based on a 63rd aspect further comprising this.

[0160]

[0166] Based on the 64th aspect, the 65th aspect, wherein the program code executable by a computer to cause the computer to transmit an uplink control message includes program code executable by the computer to multiplex the uplink control message according to one of a first number of multiplexing symbols less than the 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 greater than the actual number of multiplexing symbols based on the end of the UE uplink transmission used.

[0161]

[0167] The 66th aspect based on the 45th aspect, further including program code executable by a computer to cause the UE to obtain a set of transmission configurations from a serving base station, program code executable by a computer to cause the UE to select a transmission configuration from the set of transmission configurations, and program code executable by a computer to cause the UE to add a configuration indicator to an uplink control message, wherein the configuration indicator identifies the transmission configuration for the serving base station.

[0162]

[0168] A 67th aspect configured for wireless communication can include at least one processor and a memory coupled to the at least one processor, where the at least one processor is configured to: obtain a COT in response to a detected success of the UE's LBT procedure on a shared communication channel by the UE; determine whether COT sharing is enabled or not by the UE; identify COT sharing information for communicating with a serving base station in an uplink control message by the UE; and transmit, 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 execution of the configuration of the at least one processor for determining.

[0163]

[0169] A 68th aspect, based on the 67th aspect, where the COT sharing information includes one or more of: the remaining COT duration from the end of one of a UE uplink transmission within the COT or a PUSCH transmission including the COT sharing information to the end point of the COT; an offset indication identifying the end of the UE uplink transmission; and a CAPC used by the UE for obtaining the COT.

[0164]

[0170] A 69th aspect, based on the 68th aspect, where the configuration of the at least one processor for determining includes: identifying a UE ED threshold configuration; determining that COT sharing is enabled in response to identifying that the ED threshold configuration is configured for sharing; and determining that COT sharing is not enabled in response to identifying that the ED threshold configuration is not configured for sharing.

[0165]

[0171] Based on the 69th aspect, the 70th aspect, wherein the configuration of at least one processor for identifying COT sharing information includes identifying the remaining COT duration, an offset indication, and the CAPC for the uplink control message when COT sharing is determined to be enabled, or for the uplink control message when COT sharing is determined not to be enabled, removing the offset indication and CAPC, the remaining COT duration, a 1-bit flag indicating whether the serving base station is allowed to transmit during the remaining period of the COT, or indicating the number of symbols available for use by the serving base station for transmission, or including the configuration of at least one processor for performing one of identifying one or more of them.

[0166]

[0172] Based on the 68th aspect, the 71st aspect, wherein the configuration of at least one processor for making a determination includes receiving a configuration message from the serving base station, and based on the identification of COT sharing information within the configuration message, where the configuration message includes the identification of COT sharing information for inclusion within an uplink control message, determining whether COT sharing is to be enabled or not.

[0167]

[0173] Based on the 71st aspect, the 72nd aspect, wherein the configuration of at least one processor for determining whether COT sharing is to be enabled or not includes the configuration of at least one processor for identifying that the configuration message indicates excluding the CAPC and the remaining COT duration from the uplink control message, where the UE determines that COT sharing is not to be enabled in response to the execution of the configuration of at least one processor for identifying the configuration message.

[0168]

[0174] A 73rd aspect based on the 72nd aspect, further including a configuration of at least one processor for using an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identification of COT sharing as not being enabled by a UE.

[0169]

[0175] A 74th aspect based on the 68th aspect, wherein a 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.

[0170]

[0176] A 75th aspect based on the 74th aspect, further including a configuration of at least one processor for using an energy detection (ED) threshold configuration for an LBT procedure not configured for sharing in response to identification of COT sharing as not being enabled by a 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 identifying one or more of a remaining COT duration, an offset indication shown as a remaining transmission time, and correspondence to a CAPC.

[0172]

[0178] A 77th aspect based on the 76th aspect, wherein the table uses a resource indicator value (RIV) to compress the remaining COT duration and the remaining transmission time.

[0173]

[0179] Based on the 77th aspect, the 78th aspect, where RIV indicates one or more of the remaining transmission time as the PUSCH slot boundary at which UE uplink transmission will end and the remaining COT duration having the granularity of the start location of the UE uplink transmission configured by the serving base station.

[0174]

[0180] Based on the 76th aspect, the 79th aspect, where the table codes the remaining COT duration and the offset indication together using the start and length indicator values (SLIV).

[0175]

[0181] Based on the 79th aspect, the 80th aspect, where the length value of the SLIV is indicated at the granularity of the PUSCH transmission start point, where the PUSCH start point is configured by the serving base station.

[0176]

[0182] Based on the 79th aspect, the 81st aspect, where the start value of the SLIV is indicated at the granularity of one of the slot or the PUSCH transmission end point, and the length value of the SLIV is indicated at the granularity of one of the slot or the PUSCH transmission start point.

[0177]

[0183] The configuration of at least one processor for adding correction information to the uplink control message by the UE, where the correction information modifies one or more values in the table indicated by the SLIV, further including the 82nd aspect based on the 79th aspect.

[0178]

[0184] Compress the remaining COT duration within the uplink control message, where the configuration of at least one processor for compressing the remaining COT duration includes, by the UE, the configuration of at least one processor for indicating the number of remaining COT slots and the end symbol within the last slot of the number of remaining COT slots; compress the offset indication within the uplink control message, where the configuration of at least one processor for compressing the offset indication includes, by the UE, the configuration of at least one processor for performing one of indicating the end slot number and the last symbol of the UE uplink transmission within the end slot number, or indicating the number of remaining transmission slots; and further include the configuration of at least one processor for performing the above, according to the 83rd aspect based on the 68th aspect.

[0179]

[0185] The configuration of at least one processor for the UE to obtain the reporting location, where the reporting location identifies, by the UE, the number of slots before the end of the UE uplink transmission for which the configuration of at least one processor for transmitting an uplink control message having COT sharing information to the serving base station is executed by the UE, and where 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, and further include the above, according to the 84th aspect based on the 68th aspect.

[0180]

[0186] The UE determines a time gap between the end of UE uplink transmission and a subsequent downlink transmission start opportunity, and the UE ends 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 shortened downlink LBT according to LBT capabilities, and the UE ends the UE uplink transmission during an end period before the end of the UE uplink transmission in response to the minimum time exceeding the time gap, where an extended time gap during the end period before the end of the UE uplink transmission is sufficient to adapt to the minimum time for the serving base station to perform shortened LBT, and further includes a configuration of at least one processor for performing the above, an 85th aspect based on the 68th aspect.

[0181]

[0187] The UE ends the UE uplink transmission with rate matching based on an end period before the end of the UE uplink transmission, ends the UE uplink transmission with rate matching based on the end of the UE uplink transmission, where the UE punctures resources related to the extended time gap, or determines a transport block size for the UE uplink transmission based on one of the end periods before the end of the UE uplink transmission with rate matching based on an end period before the end of the UE uplink transmission, and further includes a configuration of at least one processor for performing the above, an 86th aspect based on the 85th aspect.

[0182]

[0188] An 87th aspect based on the 86th aspect, where the configuration of at least one processor for transmitting an uplink control message includes a configuration of at least one processor for multiplexing the uplink control message according to one of a first number of multiplexing symbols less than the 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 greater than the actual number of multiplexing symbols based on the end of the UE uplink transmission used.

[0183]

[0189] The UE obtains a set of transmission configurations from the serving base station, selects a transmission configuration from the set of transmission configurations, and adds a configuration indicator to an uplink control message, where the configuration indicator identifies the transmission configuration for the serving base station, and further includes a configuration of at least one processor for performing the above, an 88th aspect based on the 67th aspect.

[0184]

[0190] The various exemplary logical blocks, modules, and circuits described in connection with the disclosure herein can be implemented or executed 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 gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors used 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 of this specification may be implemented 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 (registered trademark) memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor 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. A computer-readable medium includes both a computer storage medium and a communication medium including any medium that facilitates transfer of a computer program from one place to another. A computer-readable storage medium 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 can 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 appropriately be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL), then the coaxial cable, fiber optic cable, twisted pair, or DSL is included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and blu-ray disc, where disk generally magnetically reproduces data, and disc uses lasers to optically reproduce data. The above combinations should also be included within the scope of computer-readable media.

[0187]

[0193] As used herein, including in the claims, the term "and / or" when used in a listing of two or more items means that any one of the listed items can be employed alone or any combination of two or more of the listed items can be employed. For example, if a composition is described as including components A, B, and / or C, the composition can include A only, B only, C only, 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 in the claims, "or" when used in a listing of items that ends with "at least one of" indicates a disjunctive listing such that, for example, the listing "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 combination thereof.

[0188]

[0194] The foregoing description of the disclosure has been 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.

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; A method comprising:

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 an energy detection (ED) threshold configuration of 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 of claim 2 , comprising:

4. The identifying 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 CAPCs; the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit for 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 of claim 3 , comprising one of:

5. The determining step 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 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:

6. 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 5 , comprising:

7. 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 6 further comprising:

8. The determining step comprises: receiving a configuration message from the serving base station, wherein the configuration message indicates whether the COT sharing is to be enabled or not; The method of claim 2 , comprising:

9. 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 8 further comprising:

10. 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.

11. The method of claim 10 , wherein the table compresses the remaining COT duration and the remaining transmission time using a resource indicator value (RIV).

12. 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 of claim 11 , wherein the method further comprises one or more of:

13. The method of claim 10 , wherein the table jointly codes the remaining COT duration and the offset indication using a Start and Length Indicator Value (SLIV).

14. 14. The method of claim 13, 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.

15. 14. The method of claim 13, 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.

16. 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 13 further comprising:

17. 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:

18. 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 claim 2 , further comprising:

19. determining, by the UE, a time gap between the 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 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 claim 2 , further comprising:

20. By the 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:

20. The method of claim 19, further comprising:

21. 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 21. The method of claim 20, comprising:

22. obtaining, by the UE, a set of transmission configurations from the serving base station; 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 claim 1 further comprising:

23. 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; An apparatus configured to:

24. 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 24. The apparatus of claim 23, comprising one or more of:

25. The configuration of the at least one processor to perform the determining step includes: 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.

25. The apparatus of claim 24, comprising a configuration of the at least one processor.

26. The configuration of the at least one processor for identifying the COT sharing information 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 CAPCs; the remaining COT duration, a one-bit flag indicating whether the serving base station is enabled to transmit for 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:

26. The apparatus of claim 25, further comprising a configuration of the at least one processor to perform one of the following:

27. The configuration of the at least one processor to perform the determining step includes: 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 to be enabled or not enabled based on the identification of the COT sharing information in the configuration message; 25. The apparatus of claim 24, comprising a configuration of the at least one processor to:

28. The configuration of the at least one processor for determining whether the 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.

28. The apparatus of claim 27.

29. 30. The apparatus of claim 28, further comprising: a configuration of 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 an identification by the UE of the COT sharing as not enabled.

30. 25. The apparatus of claim 24, wherein the configuration of the at least one processor for determining includes a configuration of the at least one processor for receiving a configuration message from the serving base station, wherein the configuration message indicates whether the COT sharing is enabled or not enabled.

31. 31. The apparatus of claim 30, further comprising: a configuration of 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 an identification by the UE of the COT sharing as not enabled.

32. 25. The apparatus of claim 24, 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 identifying one or more of the remaining COT duration, the offset indication denoted as remaining transmission time, and the CAPC correspondence.

33. 33. The apparatus of claim 32, wherein the table compresses the remaining COT duration and the remaining transmission time using a resource indicator value (RIV).

34. 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; 34. The apparatus of claim 33, exhibiting one or more of:

35. 33. The apparatus of claim 32, wherein the table jointly codes the remaining COT duration and the offset indication using a Start and Length Indicator Value (SLIV).

36. 36. The apparatus of claim 35, 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.

37. 36. The apparatus of claim 35, 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.

38. 36. The apparatus of claim 35, further comprising a configuration of the at least one processor for 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.

39. 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 configuration of the at least one processor to:

40. and further comprising a configuration of the at least one processor for performing, by the UE, obtaining 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 shared 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.

25. The apparatus of claim 24.

41. determining, by the UE, a time gap between the 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 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 configuration of the at least one processor to:

42. By the 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:

42. The apparatus of claim 41, further comprising configuration of the at least one processor to:

43. 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; 43. The apparatus of claim 42, comprising a configuration of the at least one processor to multiplex the uplink control message according to one of:

44. obtaining, by the UE, a set of transmission configurations from the serving base station; 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.

24. The apparatus of claim 23, further comprising a configuration of the at least one processor to:

Images