Listen before talk signaling and channel occupancy time sharing

Abstract

This disclosure relates to techniques for performing wireless communication procedures, including those for user equipment (UE) and base stations. Techniques for signaling channel access types, channel access usage, and other channel access parameters are disclosed.

Description

Technical Field

[0001] This application relates to wireless communication, including channel access technology and related signaling. Background Technology

[0002] The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from solely voice communication to also include the transmission of data such as the internet and multimedia content.

[0003] Mobile electronic devices can take the form of smartphones or tablets that users typically carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, an example being a smartwatch. Additionally, low-cost, low-complexity wireless devices designed for static or dynamic deployment are rapidly increasing as part of the development of the “Internet of Things”. In other words, the range of required device complexity, capabilities, traffic patterns, and other characteristics is becoming increasingly broad. Generally, there is a desire to recognize and provide improved support for a wide range of desired wireless communication characteristics. One characteristic could be channel access in unlicensed spectrum communication (e.g., at frequencies above 52.6 GHz). Improvements in this field are expected. Summary of the Invention

[0004] This paper specifically proposes implementation schemes for systems, apparatuses, and methods for performing channel access and associated communications in wireless communication systems (e.g., New Radio (NR)) at frequencies above 52.6 GHz.

[0005] As mentioned above, there is a growing number of use cases for communicating with different types of user equipment (UEs) with varying capabilities and usage expectations on wireless networks. One usage expectation may include communication in unlicensed spectrum (e.g., frequencies above 52.6 GHz). Channel access technologies such as Listen-Before-Speak (LBT) can be used in unlicensed spectrum to reduce and / or avoid collisions and interference. Devices can exchange configuration information and determine appropriate technologies and parameters for channel access.

[0006] In some implementations, a User Equipment (UE) may establish communication with a base station and exchange configuration information related to channel access with the base station (BS). The BS may transmit, and the UE may receive, an uplink grant that schedules a first uplink transmission on at least a first portion of a first channel. The UE may determine a unit bandwidth based on the configuration information. The UE may use this unit bandwidth to perform an LBT procedure on the first channel and may determine that the LBT procedure is successful on at least a first portion of the first channel, wherein the first portion of the first channel has a bandwidth equal to the LBT unit bandwidth. In response to determining that the LBT procedure is successful on at least a first portion of the first channel, the UE may transmit the first uplink transmission to the base station at least partially on the first portion of the first channel.

[0007] In some implementations, a User Equipment (UE) can establish communication with a Base Station (BS) and receive configuration information from the BS. The BS can transmit, and the UE can receive, one or more Downlink Control Information (DCI) messages, which include: downlink grants; and uplink grants. The UE can determine whether the resources used for transmission based on the uplink grant and the resources used for reception based on the downlink grant occur within the same Channel Occupancy Time (COT). The UE can receive downlink transmissions from the BS based on the downlink grants. The UE can determine whether to perform a Listen-Before-Tell (LBT) procedure before performing a transmission based on the uplink grant, wherein the determination of whether to perform the LBT procedure is based on one or more of the following: determining whether the resources used for transmission based on the uplink grant and the resources used for reception based on the downlink grant occur within the same COT; configuration information; one or more indications in one of the one or more DCI messages; and the amount of time between the resources used for reception based on the downlink grant and the resources used for transmission based on the uplink grant. The UE can transmit uplink transmissions to the BS based on the uplink grants.

[0008] In some implementations, the BS can establish communication with the User Equipment (UE) and perform a Listen-Before-Speak (LBT) procedure. The BS can determine that the LBT procedure indicates that at least a first portion of the channel is idle, and in response to determining that at least a first portion of the channel is idle, transmit downlink communication to the UE on the first portion of the channel. The BS can transmit a Downlink Control Information (DCI) message to the UE that schedules uplink communication and indicates that the first portion of the channel is idle. The BS can receive uplink communication from the UE on the first portion of the channel.

[0009] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to mobile phones or smartphones (e.g., iPhones). ™ Based on Android ™ Phones), tablets (e.g., iPads) ™ Samsung Galaxy ™ ), portable gaming devices (e.g., Nintendo DS) ™ PlayStation Portable ™ Gameboy Advance ™ iPhone ™Any of the following: wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, vehicles, automobiles, unmanned aerial vehicles (e.g., drones) and unmanned flight controllers, other cellular network infrastructure equipment, servers, and various other computing devices.

[0010] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0011] A better understanding of the subject matter can be obtained by considering the following specific description of the implementation scheme in conjunction with the accompanying drawings.

[0012] Figure 1 An exemplary wireless communication system including accessory devices according to some embodiments is shown;

[0013] Figure 2 An exemplary wireless communication system is shown, according to some embodiments, in which two wireless devices are capable of performing direct device-to-device communication;

[0014] Figure 3 This is a block diagram illustrating an example wireless device according to some implementation schemes;

[0015] Figure 4 This is a block diagram illustrating an exemplary base station according to some implementation schemes;

[0016] Figure 5 This is a communication flowchart illustrating an exemplary method for channel access communication according to some implementation schemes;

[0017] Figures 6 to 19 Various aspects of channel access communication according to some implementation schemes are illustrated.

[0018] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0019] Acronyms and Abbreviations

[0020] The following acronyms and abbreviations are used in this disclosure:

[0021] 3GPP: Third Generation Partnership Project

[0022] 3GPP2: Third Generation Partnership Project 2

[0023] GSM: Global System for Mobile Communications

[0024] UMTS: Universal Mobile Telecommunication System

[0025] LTE: Long Term Evolution

[0026] RRC: Radio Resource Control

[0027] MAC: Media Access Control

[0028] CE: Control Element

[0029] Tx: Transmit (or transmit)

[0030] Rx: Accept (or receive)

[0031] RS: Reference signal

[0032] CSI: Channel State Information

[0033] PDCP: Packet Data Convergence Protocol

[0034] RLC: Radio Link Control

[0035] the term

[0036] The following are definitions of the terms used in this disclosure:

[0037] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0038] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0039] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinational logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0040] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0041] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). ™ Based on Android ™Phones), tablets (e.g., iPads) ™ Samsung Galaxy ™ ), portable gaming devices (e.g., Nintendo DS) ™ PlayStation Portable ™ Gameboy Advance ™ iPhone ™ Wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, vehicles, automobiles, unmanned aerial vehicles (e.g., drones), and unmanned flight controllers, etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily transportable by the user and capable of wireless communication.

[0042] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.

[0043] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0044] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless communication system.

[0045] Link budget constrained—encompassing the full range of its general meaning, and at least including the characteristics of a wireless device (e.g., a UE) that exhibits limited communication capabilities or limited power relative to devices that are not link budget constrained or relative to devices for which a Radio Access Technology (RAT) standard has been developed. Link budget constrained wireless devices may suffer from relatively limited receiving and / or transmitting capabilities, which may be due to one or more factors such as device design, device size, battery size, antenna size or design, transmitting power, receiving power, current transmission medium conditions, and / or other factors. Such devices may be referred to herein as “link budget constrained” (or “link budget limited”) devices. Devices may be inherently link budget constrained due to their size, battery power, and / or transmitting / receiving power. For example, a smartwatch communicating with a base station via LTE or LTE-A may be inherently link budget constrained due to its reduced transmitting / receiving power and / or reduced antenna. Wearable devices such as smartwatches are generally link budget constrained devices. Alternatively, the device may not be inherently link budget-constrained, for example, it may have sufficient size, battery power, and / or transmit / receive power for normal communication via LTE or LTE-A, but may be temporarily link budget-constrained due to current communication conditions, such as a smartphone at the cell edge. It should be noted that the term "link budget-constrained" includes or encompasses power limitations, and therefore a link-constrained device can be considered a link budget-constrained device.

[0046] A processing element (or processor) is a component or combination of components capable of performing the functions of a device (such as a user equipment device or a cellular network device). A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a single processor, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0047] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0048] "Configured as"—Various components can be described as being "configured to" perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0049] For ease of description, various components may be described as performing one or more tasks. Such descriptions shall be interpreted as including the phrase “configured to”. The statement that a component is configured to perform one or more tasks is expressly intended not to invoke the interpretation of paragraph 6 of section 112 of title 35 of the United States Code.

[0050] Figures 1 to 2 —Wireless communication system

[0051] Figure 1 An example of a wireless cellular communication system is illustrated. It should be noted that... Figure 1This represents one of many possibilities, and the features of this disclosure can be implemented in any of various systems as needed. For example, the embodiments described herein can be implemented in any type of wireless device.

[0052] As shown in the figure, an exemplary wireless communication system includes a cellular base station 102 that communicates with one or more wireless devices 106A, 106B, etc., and an accessory device 107 via a transmission medium. Wireless devices 106A, 106B, and 107 may be user equipment, which may be referred to herein as "user equipment" (UE) or UE device.

[0053] Base station 102 may be a transceiver base station (BTS) or a cell site and may include hardware and / or software to enable wireless communication with UE device 106A, UE device 106B, and UE device 107. If base station 102 is implemented in an LTE environment, it may be referred to as an "eNodeB" or "eNB". If base station 102 is implemented in a 5G NR environment, it may alternatively be referred to as a "gNodeB" or "gNB". Base station 102 may also be equipped to communicate with network 100 (e.g., the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet, and various other possible networks). Therefore, base station 102 facilitates communication between UE device 106 and UE device 107 and / or communication between UE device 106 / 107 and network 100. Also as used herein, in relation to the UE, a base station may sometimes be considered to represent the network, taking into account both uplink (UL) and downlink (DL) communication of the UE. Therefore, a UE that communicates with one or more base stations in the network can also be understood as a UE that communicates with the network.

[0054] In other specific implementations, base station 102 may be configured to provide communication via one or more other wireless technologies, such as an access point that supports one or more WLAN protocols (such as 802.11a, b, g, n, ac, ad and / or ax, or LTE in an unlicensed frequency band (LAA)).

[0055] The communication area (or coverage area) of base station 102 may be referred to as a "cell". Base station 102 and UE 106 / 107 may be configured to communicate using a variety of radio access technologies (RAT) or wireless communication technologies such as GSM, UMTS (WCDMA, TDS-CDMA), LTE, LTE-A Advanced, NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, etc. via a transmission medium.

[0056] Therefore, base station 102 and other similar base stations (not shown) operating according to one or more cellular communication technologies can be provided as a cell network that can provide continuous or near-continuous overlapping services to UE devices 106A-N and UE devices 107 and similar devices within a geographical area via one or more cellular communication technologies.

[0057] It should be noted that, at least in some cases, UE devices 106 / 107 may be able to communicate using any of a variety of wireless communication technologies. For example, UE devices 106 / 107 may be configured to communicate using one or more of the following: GSM, UMTS, CDMA2000, LTE, LTE-A, NR, WLAN, Bluetooth, one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H). Other combinations of wireless communication technologies (including more than two wireless communication technologies) are also possible. Similarly, in some cases, UE devices 106 / 107 may be configured to communicate using only a single wireless communication technology.

[0058] UE 106A and UE 106B may include handheld devices such as smartphones or tablets, and / or may include any of a variety of devices with cellular communication capabilities. For example, one or more of UE 106A and UE 106B may be wireless devices designed for static or dynamic deployment, such as home appliances, measuring devices, control devices, etc. UE 106B may be configured to communicate with UE device 107, which may be referred to as accessory device 107. Accessory device 107 may be any of a variety of wireless devices, which may typically be a wearable device with a small form factor and limited battery, output power, and / or communication capabilities relative to UE 106. As a common example, UE 106B may be a smartphone carried by a user, and accessory device 107 may be a smartwatch worn by the same user. UE 106B and accessory device 107 may communicate using any of a variety of short-range communication protocols such as Bluetooth or Wi-Fi. In some cases, UE 106B and accessory device 107 may utilize ProSe technology, for example, in a manner supported by a cellular base station, to perform direct peer-to-peer communication. For instance, such ProSe communication may be performed as part of a relay link to support a radio resource control connection between accessory device 107 and BS 102, as described in the various embodiments herein.

[0059] UE 106B can also be configured to communicate with UE 106A. For example, UE 106A and UE 106B may be able to perform direct device-to-device (D2D) communication. D2D communication may be supported by cellular base station 102 (e.g., easily discovered by BS 102, and with various possible forms of assistance), or may be performed in a manner not supported by BS 102. For example, it is possible that UE 106A and UE 106B can deploy and perform D2D communication (e.g., including discovery communication) even when BS 102 and other cellular base stations have no coverage.

[0060] The BS 102 can control one or more Transmit and Receive Points (TRPs) and can use the TRPs to communicate with the UE. The TRPs can be arranged alongside the BS and / or located in separate physical locations.

[0061] Figure 2 An exemplary BS 102 is shown communicating with UE device 106, which in turn communicates with accessory device 107. UE device 106 and accessory device 107 can be any of a mobile phone, tablet or any other type of handheld device, smartwatch or other wearable device, media player, computer, laptop, unmanned aerial vehicle (UAV), unmanned flight controller, vehicle, or virtually any type of wireless device. In some embodiments, the accessory device may be a wireless device designed to have low cost and / or low power consumption and may support communication with BS 102 thanks to a relay link with UE device 106 (and / or another companion device). For example, in Figure 2 In the exemplary scenarios described herein, a device that communicates with a cellular base station using a relay link with another wireless device may also be referred to herein as a remote wireless device, a remote device, or a remote UE device, and a wireless device providing such a relay link may also be referred to herein as a relay wireless device, a relay device, or a relay UE device. According to some implementations, such BS 102, UE 106, and accessory device 107 may be configured to perform radio resource control procedures on the remote wireless device according to the various techniques described herein.

[0062] Both UE 106 and accessory device 107 may include a device or integrated circuit, referred to as a cellular modem, for facilitating cellular communication. The cellular modem may include one or more processors (processing elements) configured to execute program instructions stored in memory and / or various hardware components described herein. UE 106 and / or accessory device 107 may each perform any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, UE 106 and / or accessory device 107 may include programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays), integrated circuits, and / or various other possible hardware components, configured (e.g., individually or in combination) to perform any of or any portion of any of the method embodiments described herein. The cellular modem described herein can be used in UE devices as defined herein, wireless devices as defined herein, or communication devices as defined herein. The cellular modem described herein can also be used in base stations or other similar network-side devices.

[0063] UE 106 and / or accessory device 107 may include one or more antennas for communicating according to one or more RAT standards using one or more wireless communication protocols. In some embodiments, one or both of UE 106 or accessory device 107 may be configured to communicate using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains.

[0064] Alternatively, UE 106 and / or accessory device 107 may include two or more radio components. For example, in some embodiments, UE 106 and / or accessory device 107 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate. As another possibility, UE 106 and / or accessory device 107 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 and / or accessory device 107 may include shared radio components for communication using either LTE or CDMA2000 1xRTT (or LTE or NR, or LTE or GSM), and radio components for communication using Wi-Fi and BLUETOOTH. ™ Each component communicates with a separate radio unit. Other configurations are also possible.

[0065] Figure 3 —Block diagram of UE device

[0066] Figure 3 A possible block diagram of a UE device, such as UE device 106 or 107, is shown. As shown, UE device 106 / 107 may include a System-on-Chip (SOC) 300, which may include components for various purposes. For example, as shown, SOC 300 may include a processor 302 and display circuitry 304, the processor executing program instructions for UE device 106 / 107, and the display circuitry performing graphics processing and providing display signals to a display 360. SOC 300 may also include motion sensing circuitry 370, which may detect motion of UE 106, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. Processor 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, flash memory 310) and / or other circuitry or devices, such as display circuitry 304, radio components 330, I / F 320, and / or display 360. MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

[0067] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106 / 107. For example, the UE 106 / 107 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.).

[0068] UE device 106 / 107 may include at least one antenna and, in some embodiments, may include multiple antennas 335a and 335b for performing wireless communication with a base station and / or other devices. For example, UE device 106 / 107 may use antennas 335a and 335b to perform wireless communication. As described above, UE device 106 / 107 may be configured in some embodiments to perform wireless communication using multiple wireless communication standards or radio access technologies (RATs).

[0069] The wireless communication circuitry 330 may include a Wi-Fi logic component 332, a cellular modem 334, and a Bluetooth logic component 336. The Wi-Fi logic component 332 enables the UE device 106 / 107 to perform Wi-Fi communication over an 802.11 network. The Bluetooth logic component 336 enables the UE device 106 / 107 to perform Bluetooth communication. The cellular modem 334 may be a low-power cellular modem capable of performing cellular communication according to one or more cellular communication technologies.

[0070] As described herein, UE 106 / 107 may include hardware and software components for implementing embodiments of this disclosure. For example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium), the processor 302 of UE device 106 / 107 may be configured to implement part or all of the methods described herein. In other embodiments, processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Furthermore, processor 302 may be coupled to, for example, Figure 3Other components shown and / or interoperable with said other components are used to perform radio resource control procedures for remote wireless devices according to various embodiments disclosed herein. Processor 302 may also implement various other applications and / or end-user applications running on UE 106. Alternatively or additionally, one or more components of the wireless communication circuitry 330 (e.g., cellular modem 334) of UE device 106 / 107 may be configured, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), a processor configured as an FPGA (Field-Programmable Gate Array), and / or a processor using dedicated hardware components that may include ASICs (Application-Specific Integrated Circuits) to implement part or all of the methods described herein.

[0071] Figure 4 —Block diagram of a base station

[0072] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions for base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0073] Base station 102 may include at least one network port 470. (As mentioned above...) Figure 1 and Figure 2 As described herein, network port 470 can be configured to be coupled to a telephone network and provide access to multiple devices, such as UE devices 106 / 107, that have access to the telephone network.

[0074] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. This core network may provide mobility-related services and / or other services to multiple devices, such as UE devices 106 / 107. For example, the core network may include, for instance, a Mobility Management Entity (MME) for providing mobility management services, a Serving Gateway (SGW) and / or a Packet Data Network Gateway (PGW) for providing external data connections such as to the Internet, and so on. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide the telephone network (e.g., between other UE devices served by the cellular service provider).

[0075] Base station 102 may include at least one antenna 434 and possibly multiple antennas. One or more antennas 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 / 107 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to LTE, LTE-A, NR, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0076] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio for performing communication according to LTE and a Wi-Fi radio for performing communication according to Wi-Fi. In such a case, base station 102 may be able to operate as both an LTE base station and a Wi-Fi access point. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., LTE and NR, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0077] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. According to some embodiments, processor 404 of base station 102 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, 470, processor 404 of BS 102 may be configured to implement or support radio resource control procedures for remote wireless devices according to the various embodiments described herein, and / or any of the various other features of the features described herein.

[0078] Figure 5 —Channel Access

[0079] Channel access mechanisms such as Clear Channel Assessment (CCA), Enhanced CCA (eCCA) (e.g., based on EN 302567), and Listen-After-Talk (LBT) provide methods for orderly access to unlicensed spectrum. For example, these channel access mechanisms allow a device to determine whether another device is using the wireless medium (e.g., transmitting potential interference signals) before transmitting a signal. Channel access mechanisms may or may not incorporate beamforming techniques and can differentiate between frequencies with different levels of granularity. In other words, directional beamforming can be used to determine channel access on a frequency-specific basis, potentially including frequency-specific and / or beam-specific determinations of whether the medium is clear.

[0080] Various types of channel access, including LBT categories, can be used. Different LBT categories describe different time series of waiting to determine whether a channel or other frequency range is idle. For example, Category 2 (CAT2) LBT can refer to a "oneshot" LBT, where the channel or range can be sensed once in various possibilities, such as a period of 5 or 8 microseconds. If the channel is idle within that time period, the device can determine that the channel is idle and transmission is possible. CAT4 LBT can also incorporate random backoff periods.

[0081] Channel access mechanisms assuming beam-based operation to comply with specification requirements applicable to unlicensed spectrum between 52.6 GHz and 71 GHz have been discussed. Physical layer procedures can specify LBT and non-LBT related procedures. In some implementations, non-LBT can be used without specifying additional sensing mechanisms. Omnidirectional channel access, directional channel access, and receiver assistance in channel access can be used. Various energy detection thresholds can be used.

[0082] For single-carrier transmission, LBT or other channel access can be performed in various ways. As one possibility, the base station or UE can perform LBT on the channel bandwidth (e.g., the bandwidth portion (BWP) bandwidth). As another possibility, a cell bandwidth (e.g., the amount of bandwidth used during channel access) can be defined, and the base station or UE can perform channel access sensing in all cells (e.g., the cells to be transmitted in) within the channel or BWP bandwidth. According to some implementations, such cell bandwidth can be determined based on various factors (e.g., discussed further below), making the cell bandwidth variable.

[0083] For multi-carrier transmission (e.g., in in-band carrier aggregation), LBT or other channel access can be performed in various ways. As one possibility, the base station or UE can (e.g., simultaneously) perform multiple LBT procedures. In other words, an LBT can be performed individually for each channel bandwidth (e.g., multiple channels / carriers), thus providing results for each test bandwidth. As another possibility, the base station or UE can perform a single LBT on all component carriers (CCs), for example, to sense interference signals on any CC. As yet another possibility, a cell bandwidth (e.g., the amount of bandwidth used in the LBT or other channel access process) can be defined. Cell bandwidth can be defined by BWP, by channel, by cell, by UE, and / or by any combination of these or other methods. The base station or UE can perform LBT in all LBT cells to be transmitted within the channel bandwidth of each CC.

[0084] It should be understood that the various possibilities described above can be combined as needed. For example, the device disclosed herein can support a variety of methods for multi-carrier transmission channel access. Furthermore, the use of LBT-based methods can be configurable and / or can be used at some times or in some situations, as discussed below.

[0085] One aspect of channel access is the amount of time the channel can be considered available after the channel access process, and how / whether that amount of time can be used by different transmission devices. For example, some standards may include a defined or maximum channel occupancy time (COT). For example, among various possibilities, Licensed Assisted Access (LAA) may include an 8ms COT.

[0086] In some implementations, the COT (Cross-Operation Time) may be shared by different devices (e.g., base station and UE). One possible rule for sharing the COT may include defining a maximum gap between transmissions, such as Y. For example, if a later transmission begins within a gap Y from the end of an earlier transmission, the later transmission may share the COT with the earlier transmission (e.g., no LBT or other channel access is performed for the later transmission). As another possible rule, a maximum gap (e.g., Y) may not be applied. Therefore, the later transmission may share the COT with the earlier transmission (e.g., no channel access procedure is performed for the later transmission), regardless of the gap between the two transmissions (e.g., as long as the later transmission is within the COT). In some implementations, the gap may be measured from the end of the earlier transmission to the beginning of the later transmission. In some implementations, the gap may be measured from the end of the earlier transmission to the end of the later transmission. In some implementations, a defined or default duration for the earlier transmission may exist (e.g., indicated in configuration information); the gap may be measured from the end of the defined / default duration (e.g., which may differ from the actual end of the earlier transmission).

[0087] In some implementations, the entire later transmission must be within the COT.

[0088] In some implementations, the fallback DCI (e.g., formats 1-0 and 0-0) may include a 2-bit field indicating the channel access type and cyclic prefix (CP) extension. For example, for operation in a cell with shared spectrum channel access, a field such as ChannelAccess-CPext may be 2 bits indicating a combination of channel access type and CP extension as shown in Tables 7.3.1.1.1-4; otherwise, it is 0 bits. In the non-fallback DCI (e.g., format 1-1), ChannelAccess-CPext may include 0, 1, 2, 3, or 4 bits in various possibilities. The bit width of this field may be determined to be log2 (I) bits, where I is the number of entries in the higher-layer parameter ul-AccessConfigListDCI-1-1 used for operation in a cell with shared spectrum channel access; otherwise, it is 0 bits. One or more entries from Table 7.3.1.2.2-6 may be configured by the higher-layer parameter ul-AccessConfigListDCI-1-1. In non-backoff DCI (e.g., format 0-1), ChannelAccess-CPext-CAPC can be 0, 1, 2, 3, 4, 5, or 6 bits. The bit width of this field can be determined to be log2(I) bits, where I is the number of entries in the higher-layer parameter ul-AccessConfigListDCI-0-1 used for operation in cells with shared spectrum channel access; otherwise, it is 0 bits. One or more entries from Table 7.3.1.1.2-35 can be configured by the higher-layer parameter ul-AccessConfigListDCI-0-1.

[0089] In some implementations, DL DCI signal channel access can be applied to PUCCH. UL DCI (e.g., DCI scheduling UL transmissions) can signal channel access for UL transmissions (e.g., Channel Access Priority Class (CAPC), CP extension, and / or LBT (CAT)).

[0090] Figure 5 This is a communication flowchart illustrating an exemplary method for performing channel access according to some embodiments. In various embodiments, some elements of the method shown may be performed simultaneously in a different order than shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed.

[0091] Figure 5Various aspects of the method can be implemented by a UE such as UE 106 or 107, a cellular network, and / or one or more BSs 102, as needed as shown in and described with reference to the figures, or more generally in combination with any of the computer systems, circuits, elements, components, or devices shown in the figures. For example, one or more processors (or processing elements) (among various possibilities, such as processors 302, 404, baseband processors, processors associated with communication circuits such as 330, 332, 334, 336, 430, or 432, processors associated with various core network elements, etc.) can cause the UE, network elements, and / or BS to perform some or all of the illustrated method elements. It should be noted that while described in a manner involving the use of communication technologies and / or features associated with LTE, NR, and / or 3GPP specification documents... Figure 5 This description describes at least some elements of the method, but it is not intended to limit this disclosure and can be used in any suitable wireless communication system as needed. Figure 5 The method can be described in several aspects. As shown in the figure, the method can be operated as follows.

[0092] According to some implementation schemes, the UE and BS can establish communication (502). The UE and BS can communicate using one or more radio access technologies (RATs), such as NR. Among various possibilities, the UE and BS can communicate using any frequency resources, such as NR operation above 52.6 GHz. The UE and BS can communicate using one or more frequency carriers, such as licensed and / or unlicensed carriers. The BS can provide one or more cells and / or cell groups, and communication between the UE and the BS can use one or more cells and / or cell groups.

[0093] The BS can exchange configuration information with the UE. For example, the BS can use Radio Resource Control (RRC) and / or other higher-layer signaling to negotiate parameters and / or configure the UE. Among various possibilities, the configuration information may include various parameters related to channel access technologies such as LBT and eCCA.

[0094] As part of configuration information exchange, the UE may provide capability information such as capability reports, for example, capability reports relating to its channel access and / or other capabilities. For instance, the UE may provide information on the frequency granularity of one or more channel access technologies it can perform. For example, the UE may indicate whether it can perform channel access at different frequencies (e.g., simultaneously) and / or what unit bandwidth the UE might be able to use for channel access technologies such as LBT (e.g., LBT unit bandwidth). Unit bandwidth can describe the bandwidth on which the device performs sensing during a channel access process such as LBT. In other words, unit bandwidth can be described as sensing bandwidth. In some embodiments, unit bandwidth may be less than or equal to the corresponding operating bandwidth, channel bandwidth, and / or BWP bandwidth.

[0095] Among various possibilities, the UE may provide capability information via UE-specific signaling such as RRC. A capability indicator may be used to indicate whether the UE supports the use of unit bandwidth for CCA (and / or other channel access) sensing.

[0096] The BS can transmit configuration information to the UE. This configuration may or may not be based on (or in response to) the UE's capability information. For example, the configuration information may indicate whether parameters provided by the UE (e.g., cell bandwidth) or other parameters (e.g., different cell bandwidths) can be used.

[0097] This configuration can be cell-specific. For example, the cell bandwidth can be cell-specific.

[0098] The BS can broadcast configuration information, such as system information. For example, cell bandwidth can be indicated in a System Information Block (SIB) transmitted by the BS. For instance, one or more Information Elements (IEs) such as ServingCellConfigCommon or servingCellConfigCommonSIB can indicate cell bandwidth or other configuration information. In various possibilities, such information can be provided in a format similar to the following:

[0099]

[0100] Therefore, when operating in idle mode, the UE can obtain this information (e.g., via one or more SIBs).

[0101] Alternatively or otherwise, such as when the UE is in connected mode, the BS may use dedicated signaling such as RRC to provide configuration information. For example, when configuring the UE using one or more secondary cells (SCells), using supplementary cell groups (e.g., secondary cell group (SCG)), or for a SpCell (e.g., primary cell group (MCG) and / or SCG), the BS may transmit configuration information to the UE. In various possibilities, the BS may transmit such information during reconfiguration and synchronization. For example, the BS may use UE-specific RRC signaling to configure the UE to support UE capabilities with a specific cell bandwidth value. The configuration information may be UE-specific.

[0102] In some implementations, one or more default configurations (e.g., for cell bandwidth, Y, under what conditions which channel access procedure is used, etc.) can be established, for example, through standards. Therefore, configuration information can indicate whether a default is in use (e.g., for a cell or for a specific connection between the UE and the BS). For example, the default cell bandwidth for channel access could be, for example, the bandwidth of a specific bandwidth portion (BWP) or channel bandwidth, such as the default BWP or the active BWP.

[0103] In some implementations, the channel access bandwidth may be indicated by the BS and / or negotiated with the UE. The channel access bandwidth may be wider than or equal to the cell bandwidth. The operational bandwidth (e.g., the operational bandwidth of a cell in unlicensed spectrum or the connection between the UE and a cell) may include any number of channel bandwidths. For example, the channel access bandwidth may be the bandwidth on which LBT or other channel access is performed. However, individual channel access determination may be based on cell bandwidth. For example, the UE or BS may determine that one cell bandwidth is idle, but another cell bandwidth within the same channel or BWP is not idle. Therefore, the channel access bandwidth may be a multiple of the cell bandwidth. For example, the channel access bandwidth may be the channel bandwidth or the BWP bandwidth.

[0104] In some implementations, channel bandwidth and / or BWP bandwidth can be broadcast as system information. For example, SIB1 can indicate BWP bandwidth.

[0105] In some implementations, a unit bandwidth may be determined (or indicated) for the BS, and a unit bandwidth may be determined or indicated (e.g., possibly differently) for the UE. In some implementations, for example, the unit bandwidth may be applied only to the BS and not to the UE. In some implementations, the same unit bandwidth may be applied to both the UE and the BS. Configuration information may indicate in which situations the UE should (and / or should not) use unit bandwidth among various possible scenarios.

[0106] For example, configuration information may instruct the UE to use BWP and / or channel bandwidth for channel access sensing, and to transmit only if channel access is successful (e.g., for the entire BWP and / or channel). In other words, the cell bandwidth may be applied to the BS but not to the UE; for example, the cell bandwidth may not be specified for the UE and / or may be the same size as the BWP and / or channel bandwidth.

[0107] Alternatively, the configuration information may indicate that unit bandwidth can be applied to both the UE and the BS. As an example, if the license for a UL transmission (e.g., PUSCH and / or PUCCH) is within one unit bandwidth (e.g., a configuration license or a dynamic license), the BS can configure the UE to apply the unit bandwidth to channel access sensing. Otherwise, for example, if the license extends to at least two unit bandwidths, the UE can use either the BWP or the channel bandwidth for sensing. As another example, the UE can be configured to perform unit bandwidth-based channel access sensing. Therefore, the UE can only transmit if / if (e.g., only if) all licensed unit bandwidths are successful during the channel access process. As another possibility, the UE can be configured to perform unit bandwidth-based channel sensing and can use any available bandwidth.

[0108] According to some implementation schemes, the application or configuration timeline for such configuration information may depend on the method of exchanging configuration information. For SIB-based signaling, the UE and BS may follow the same system information (SI) modification cycle rules as other SIs. For UE-specific RRC signaling, the UE and BS may follow the RRC signaling application time.

[0109] Configuration information may also include one or more timing values. For example, configuration information may specify the maximum gap between transmissions, such as Y, so that a second transmission can be performed without a channel access procedure. Y can be measured in time slots, milliseconds, or any other time unit. Y may depend on various parameters, such as those set by standards, negotiated in the configuration information, or established by control information (e.g., dynamically). For example, Y may depend on K2, K1, subcarrier spacing (SCS), and / or other factors. K2 may indicate the delay between scheduled and scheduled communications, such as the delay between a licensed DCI and the corresponding Physical Uplink Control Channel (PUSCH) or Physical Downlink Control Channel (PDSCH). K1 may indicate the delay between data transmission (e.g., PDSCH) and the corresponding acknowledgment (e.g., Uplink Control Information (UCI) and / or Physical Uplink Control Channel (PUCCH)). Y may be set directly by configuration information (e.g., BS may indicate the value of Y).

[0110] In some implementations, Y can be set to a fixed value. For example, Y could be 3 microseconds, similar to 802.11ad.

[0111] In some implementations, Y may depend on the maximum applicable value of K2. For example, configuration information and / or criteria may indicate the maximum value of K2, such as 32 time slots. The length of the time slots, and therefore the length of Y, may depend on the SCS. For example, for a 120kHz SCS, Y may be 4ms; for a 480kHz SCS, Y may be 1ms; and / or for a 960kHz SCS, Y may be 0.5ms in various possibilities. Therefore, the configuration information indicates one or more SCS values ​​and / or K2 values. Based on the SCS and / or K2, the UE and BS can determine the corresponding value of Y.

[0112] In some implementations, Y may depend on a default value for K2 (e.g., which may be indicated in the configuration information). In some implementations, when the field indicating the applicable value for K2 is not present, the UE may apply a value of 1 time slot to K2 when the PUSCH SCS is 15 / 30kHz; when the PUSCH SCS is 60kHz, the value of K2 is 2 time slots; and when the PUSCH SCS is 120kHz, the value of K2 is 3 time slots. Therefore, for a 120kHz SCS, Y may be equal to 3 time slots. In some implementations, for a 480kHz SCS and / or a 960kHz SCS, Y may depend on the processing timeline or delay. Such processing times may be indicated in the configuration information (e.g., based on UE capability reports and / or information from the BS). In some implementations, for SCS > 120kHz, Y may be > 3 time slots.

[0113] In some implementations, different SCS values ​​can be applied to different channels (e.g., PUSCH, PDSCH, PUCCH, etc.). Therefore, the UE and / or BS can determine different K2 and / or Y values ​​for different channels.

[0114] In some implementations, Y may depend on the maximum value of K1. Among various possibilities, the maximum K1 can be 16 time slots. The maximum K1 may be set by RRC and / or may be cell-specific.

[0115] In some implementations, Y can be cell-specific and / or UE-specific. Y can be configured by RRC and / or broadcast (e.g., as SI). In some implementations, Y can be an integer number of time slots. The integer number of time slots can depend on the SCS. For example, configuration information can indicate different Y values ​​for different SCS values.

[0116] It should be understood that the Y, K1, and K2 values ​​discussed in this article are examples. In some implementations, if the maximum value of K1 or K2 increases in future standards and / or is defined in multiple time slots, the corresponding Y value may be an updated value.

[0117] In some implementations, configuration information may indicate whether (e.g., or under what circumstances) the UE should perform channel access before transmitting to the BS (e.g., on a licensed channel). In some implementations, configuration information may specify the type of channel access procedure to be performed under various circumstances.

[0118] In some implementations, configuration information may indicate whether the UE should use a cyclic prefix (CP) extension to fill any gaps between the channel access procedure and UL transmission and / or the length of the CP extension to be used.

[0119] In some implementations, configuration information may indicate the size of the cell bandwidth (e.g., explicitly) and / or indicate information that the UE can use to determine the size of the cell bandwidth. The size of the cell bandwidth can provide a trade-off between flexibility and complexity. For example, when the cell bandwidth is small, higher accuracy requirements may be necessary. Sensing slots can be of a fixed duration (e.g., 5 microseconds, as in EN 302 567), regardless of the cell bandwidth. Narrow cell bandwidths may correspond to tighter energy detection (ED) thresholds. According to some implementations, a nested structure between cell bandwidth and BWP bandwidth or channel bandwidth may be used. In some implementations, the UE may not expect cell bandwidths spanning two BWP bandwidths or channel bandwidths. In some implementations, configuration information may explicitly indicate the cell bandwidth. In some implementations, configuration information may indicate a minimum cell bandwidth. In some implementations, multiple cell bandwidths or minimum values ​​may be indicated, allowing the UE to determine the applicable value (or multiple values) based on SCS and / or other factors.

[0120] As an option, the minimum unit bandwidth can be limited to the minimum channel bandwidth per SCS. For example, a 120kHz SCS could have a minimum bandwidth of 100MHz, a 480kHz SCS could have a minimum bandwidth of 400MHz, a 960kHz SCS could have a minimum bandwidth of 400MHz, and so on. Other values ​​can be used as needed.

[0121] As another possibility, the minimum unit bandwidth can be limited to the minimum channel bandwidth of all SCSs. For example, a minimum unit bandwidth of 100MHz could be used, corresponding to a 120kHz SCS.

[0122] As another possibility, the unit bandwidth can depend on the BWP (or channel) bandwidth. The unit bandwidth can be determined based on dividing the BWP (or channel) bandwidth by an integer (e.g., as indicated by configuration information). For example, if the channel bandwidth is 2000 MHz and the BWP bandwidth is 500 MHz, and the integer is 4, then the unit bandwidth could be 125 MHz (e.g., 500 / 4 = 125). This method can be combined with another method (e.g., based on a minimum channel bandwidth, per SCS, or other minimum unit bandwidth). For example, if the bandwidth to be divided is less than a configured minimum value, then the configured minimum value (e.g., 100 MHz) can be applied.

[0123] In some implementations, configuration information may indicate the length of time used for the channel access procedure. For example, configuration information may indicate whether a time slot and / or delay time for CAT2 LBT are used, or may specify different time lengths. Different time lengths may be indicated for different procedures and / or for use under different conditions.

[0124] In some implementations, a BS (e.g., or Transmit / Receive Point (TRP)) may exchange or provide configuration information suitable for communicating with different BSs (e.g., or TRPs). For example, a BS operating in licensed spectrum (e.g., providing a primary cell) may exchange configuration information with the UE for channel access procedures with different BSs (e.g., providing a secondary cell) operating in unlicensed spectrum.

[0125] According to some implementation schemes, the BS may perform one or more channel access procedures (504). For example, the BS may perform channel access to determine whether a channel or BWP (or a portion thereof, such as using channel access bandwidth and / or cell bandwidth) is idle before transmitting one or more DL communications to the UE, for example, on an unlicensed channel. The BS may perform any of various types of channel access procedures, such as LBT, eCCA, etc. Based on the channel access procedures, the BS may determine frequency resources that are available for transmission or not available for transmission, such as unbusy / occupied frequencies.

[0126] The BS can apply channel access parameters, such as the channel access bandwidth and / or unit bandwidth as indicated in the configuration information. For example, the BS can perform a channel access procedure on the channel access bandwidth. The BS can determine whether the medium is idle for any number of unit bandwidths (e.g., constituting the channel access bandwidth). For example, the BS can determine that one or more unit bandwidths may be idle and / or one or more (e.g., different) bandwidths may be busy.

[0127] In some implementations, the channel access process may be associated with the amount of time that the channel (or part of it) may be occupied, such as COT.

[0128] According to some implementations, the BS may determine one or more UL and / or DL ​​communications to be scheduled from the UE, and may transmit one or more messages (e.g., UL and / or DL ​​authorization) to the UE to schedule the UL and / or DL ​​communications (508). The UL and / or DL ​​communications may be scheduled in and / or outside the COT.

[0129] According to some implementation schemes, the BS may transmit one or more DL communications to the UE. DL communications may include data and / or control information (e.g., PDSCH, PDCCH, downlink control information (DCI), etc.). The BS may transmit DL communications on one or more channels or portions thereof that are determined to be idle (e.g., during the channel access process discussed with respect to 504). The BS may transmit DL communications during COT.

[0130] UL licenses may be transmitted in one or more DCI messages and / or other messages. In some implementations, UL licenses may be multiplexed with DL communications or transmitted separately.

[0131] In some implementations, messages may be transmitted on licensed and / or unlicensed spectrum that differs from the spectrum on which the BS performs the channel access procedure 504. In some implementations, messages may be transmitted before, simultaneously with, or overlapping with the channel access procedure.

[0132] In some implementations, the message may include one or more indications to the UE regarding channel access. For example, such indications may be in a DCI message that is the same as or different from a UL license. Such indications may describe information regarding the BS's channel access determination and / or what (if any) channel access procedures the UE should perform before transmitting UL communications. For example, the message may indicate what unit bandwidth the BS uses for its channel access and determine which / which unit bandwidths are idle. The message may indicate the COT used for the idle unit bandwidth.

[0133] The message may indicate channel access parameters, such as those discussed below.

[0134] In some implementations, Category (CAT) 2 LBT may not be used. The message may include an indication of whether there is no channel access (e.g., no LBT) or eCCA (e.g., 1 bit). For example, if UL communication is scheduled within the COT, the message may indicate that the UE does not need to perform any channel access procedure before transmitting the UL transmission. If the UL communication is scheduled outside the COT (e.g., wholly or partially) or is not within the Y of the DL communication, the indication may signal to the UE to perform eCCA before transmitting the UL communication. In other words, if the delay between the DL and UL communication exceeds a threshold (based on COT and / or Y), the message may indicate that a channel access procedure should be performed.

[0135] In some implementations, CAT 2 LBT can be used. The message may include an indication (e.g., 1 bit) of whether UL communication is scheduled within the COT. For example, an indication value of 0 may indicate that UL communication is within the COT. This may instruct the UE to determine whether CAT2 LBT is needed, for example, by comparing the configured Y value with the last symbol of the scheduled DCI or the last symbol of DL communication (e.g., PDSCH). If the time difference determined by the comparison is less than Y, LBT is not indicated. If the time difference determined by the comparison is greater than Y, CAT2 LBT may be indicated. Furthermore, an indication value of 1 may indicate that the UE should use eCCA and / or that UL communication is scheduled outside the COT.

[0136] In some implementations, CAT 2 LBT can be used in a more detailed context. The message may include (e.g., 2 bits) an indication of what channel access procedure the UE will use, if any. For example, a value of 00 may indicate no LBT or other channel access, a value of 01 may indicate CAT 2 LBT, a value of 10 may indicate eCCA, and a value of 11 may be reserved.

[0137] In some implementations, the message may not include instructions on what channel access procedure the UE should perform (if any). In other words, the UE may be configured to determine the channel access method based on other information such as configuration information.

[0138] In some implementations, the message may indicate whether the UE should use a CP extension and / or the length of the CP extension to be used.

[0139] In some implementations, the message may include one or more fallback DCI messages. The fallback DCI message may be a DCI format usable by a UE that is not (e.g., still or currently) in an RRC connected state. In some implementations, the message may include one or more non-fallback DCI messages, for example, for a connected UE.

[0140] In some implementations, the message (e.g., fallback DCI) may include an indication (e.g., 1 bit) of whether cross-COT scheduling is enabled (or disabled). Cross-COT scheduling may refer to UL transmissions not scheduled within the COT (e.g., determined by the BS for DL ​​communication in 504). COT sharing may refer to UL transmissions scheduled within the COT. Therefore, if COT sharing is indicated, additional channel access procedures for the UE (e.g., CAT2 LBT) may not be required.

[0141] In some implementations, messages (e.g., fallback DCI) may not include such an indication (e.g., 1 bit). This indication may be omitted if the BS ensures that the UL transmission is scheduled within the COT. In this case, the CP extension may not be used. In this case, there may be no ambiguity in core set 0 decoding.

[0142] In some implementations, depending on the configuration information, the message (e.g., non-fallback DCI) may include or exclude various parameters. For example, if CAT 2 LBT is enabled and CP extension is not enabled (e.g., via configuration information), one or two bits may be configured based on RRC to indicate whether CAT 2 LBT should be used. Furthermore, if CAT 2 LBT is enabled and CP extension is enabled, one or two bits may jointly encode whether LBT and CP extension should be used. Additionally, if CAT 2 LBT is not enabled and CP extension is not enabled, then, for example, if DCI format 2-0 is used, no additional bits may be used to indicate whether the UL transfer is during COT. A one-bit indication may be included to indicate whether the UL transfer is within or outside of COT.

[0143] In some implementations, the message may include an indication of whether the UL message is scheduled within the Y portion of the DL message. In other words, the BS can determine whether the UL message is sufficiently close to the DL message to be transmitted without further channel access procedures, and can indicate this directly to the UE.

[0144] In some implementations, for scheduling DL communications, the BS can use DCI format 2-0 or a similar format, such as a design similar to NR-U. If cell bandwidth (e.g., LBT cell) is enabled and if cell-specific frequency monitoring (e.g., availableRBsetPerCell) is enabled, any successful cell bandwidth can be signaled in the DCI (e.g., format 2-0). If directional channel access (e.g., beamforming LBT) is used, different cell bandwidths may be successful for different sensing beams. The DCI message signals the COT directivity of each successful LBT cell. In other words, the DCI can indicate which frequencies are idle (or busy) for which beams. For example, the DCI can indicate that resource block (RB) set 1 (e.g., first cell bandwidth) is idle for a first Transmission Control Indicator (TCI) status list, and a second RB set is idle for a second TCI status list. According to some implementations, omnidirectional channel access can be assumed if no TCI status list is configured. Therefore, according to some implementations, if the indicated and associated TCI status list is in the active TCI status list configured by the UE, the UE may (e.g., only) monitor the successful LBT unit bandwidth and / or RB set.

[0145] In some implementations, the message may indicate one or more Y values, for example, when the UE selects how / whether to perform channel access. Y may be indicated dynamically (e.g., in control information, for example, for a specific transmission) and / or semi-statically.

[0146] In some implementations, the message may indicate the length of time used for the channel access procedure. For example, the message may indicate whether a time slot and / or delay time for CAT2 LBT are used, or a different time length may be specified.

[0147] According to some implementation schemes, the UE can determine parameters for channel access for UL communication and / or for monitoring for DL ​​communication (510).

[0148] For example, for UL communication (e.g., scheduled in 508), the UE may determine whether to perform channel access and / or determine the relevant channel access parameters. Such channel access parameters may include the type of channel access, whether CP extension is used, what element bandwidth (if any) is used, the TCI state for channel access, etc. The UE may determine such parameters and whether to perform channel access based on: configuration information (e.g., as discussed in 502, for determining the Y value, etc.), any indications included in the control information (e.g., as discussed in 508, for determining the timing of UL communication related to the COT and / or Y value, etc.), standards, etc. For example, if the control information explicitly signals the channel access technology, or if channel access is not required (e.g., as discussed in 508), the UE may determine to perform the channel access procedure based on such indications. Furthermore, the UE may determine the type of channel access procedure to be performed, and / or may determine relevant parameters, such as what frequency range and / or beam to use. The type and / or related parameters of channel access may be determined based on explicit indications (e.g., control information from the BS) and / or other factors, possibly in combination with configuration and / or control information.

[0149] In some implementations, the control information (e.g., in 508) may not include an indication of whether to perform channel access for UL communications and / or channel access parameters. Therefore, the UE can determine the channel access parameters without such indication. For example, the control information (e.g., a DCI Format 2-0 message) may include an indication of the COT duration. When DCI 2-0 is configured with COTdurationPerCell, the UE can determine the remaining COT duration based on DCI 2-0 decoding. If a UL transmission (e.g., PUSCH / PUCCH) is within the COT, and if a relatively short channel access technique (e.g., CAT2 LBT) is enabled (e.g., based on configuration information and / or other factors), the UE can determine whether to perform a short channel access technique based on the configured Y value from the last symbol of the scheduling DCI or the last symbol of the PDSCH. In other words, the UE can compare the duration of the UL transmission with the scheduling control information and / or downlink transmissions within the COT.

[0150] Based on this comparison, the UE can determine whether to perform channel access. For example, if the UL transmission is within the control information Y of the DL transmission, the UE can determine not to perform channel access. If the UL transmission is not within the control information Y of the DL transmission, the UE can determine to perform channel access, for example, using a short channel access technique. Furthermore, if the UL transmission is within the COT and a short channel access technique is not enabled, the UE can determine not to perform channel access. If the UL transmission is outside the COT, the UE can determine to perform a longer channel access technique, such as eCCA.

[0151] It should be understood that DL communications that the UE is timing for its measurement UL communications can be scheduled in 508 and / or based on other control information. For example, DL communications can occur before, simultaneously with, or after the scheduling of UL communications.

[0152] When the UE determines that it needs to perform a specific channel access procedure, the UE can further determine the bandwidth to be used for performing the channel access procedure. For example, the UE can determine whether to use the unit bandwidth, BWP bandwidth, and / or channel bandwidth for the procedure. As mentioned above, configuration information can indicate whether the unit bandwidth can be applied to the channel access procedure performed by the UE. Furthermore, the UE can determine the unit bandwidth, BWP bandwidth, and / or channel bandwidth used for the channel access procedure, for example, based on control and / or configuration information. For example, the UE can determine whether to use the unit bandwidth and what the size of the unit bandwidth (e.g., bandwidth) is. Additionally, the UE can determine the specific frequency range to be tested, such as a first unit bandwidth from frequency 1 to frequency 2 and a second unit bandwidth from frequency 3 to frequency 4, etc.

[0153] As described above, in some implementations, the UE may determine the cell bandwidth based on indications from the BS (e.g., in configuration information and / or control information). For example, the UE may provide the cell bandwidth in a capability report using static signaling. Such cell bandwidth may be greater than or less than the BWP bandwidth.

[0154] In some implementations, the UE may dynamically determine the cell bandwidth and dynamically signal the determined bandwidth to the BS. For example, the UE may dynamically determine the cell bandwidth and may use resources provided by configuration permissions for the PUSCH to report the cell bandwidth in the uplink control information (UCI). In other words, if the UE is able to transmit the UCI on any successful cell bandwidth, the UE may include an indication of the cell bandwidth used during channel access. The UE may also include an indication of which cell bandwidths are sensed and determined to be idle (and / or busy). This method may imply to the BS to perform blind decoding of UL transmissions (e.g., PUSCH and / or PUCCH including UCI and / or other UL data). In some implementations, the UE may not indicate the cell bandwidth used, for example, even if the UE dynamically determines the cell bandwidth.

[0155] In some implementations, the UE may determine the amount of time (e.g., slot time, delay time, or other time amounts) used for the channel access procedure. Similarly, the UE may determine an ED threshold for this procedure. These determinations may be based on control information, configuration information, and / or other factors.

[0156] The UE may, for example, perform a channel access procedure in response to determining that the channel access procedure is appropriate. If applicable, the UE may use the determined bandwidth, type, and other parameters.

[0157] As an example of determining parameters for receiving DL messages, the UE can determine which beam and / or frequency range (e.g., cell bandwidth) to use to monitor DL ​​transmissions. For example, as described above, the BS can perform a channel access procedure (e.g., 504) and include an indication in the control information (e.g., 508) that a frequency range and / or beam has been successfully identified as idle. Based on such an indication (e.g., in conjunction with other indications of DL permission or desired transmission), the UE can monitor the indicated beam and / or frequency range. In other words, the UE can determine the RB set and / or TCI status based on such an indication.

[0158] According to some implementation schemes, the UE and BS can exchange UL and / or DL ​​communications (512).

[0159] In order to perform any DL reception, the UE may monitor the determined beam and / or frequency range (e.g., in 510).

[0160] To perform any UL transmission, the UE may apply the results of any channel access procedures performed (e.g., performed by the UE in 510 and / or by the BS in 504, with the results indicated in 508). For example, the UE may transmit the UL transmission on frequency resources and / or beams determined to be idle. The UE may also include one or more indications of the performed channel access procedures, the results, and / or the parameters used.

[0161] As mentioned above, it should be understood that Figure 5 The components can be executed in various orders, omitted, etc. As an example, the BS can perform the channel access procedure in 504 and use the determined channel access information (e.g., what frequency and / or beam is busy or not busy) to schedule UL communication and / or provide the UE with previously scheduled UL and / or DL ​​communication.

[0162] As another example, the BS may not schedule any UL communications, and the UE may use channel access parameters, for example, indicated by the BS in 508, to assist in the reception of DL communications and / or monitoring of future transmissions from the BS. The BS may perform channel access in 504 and indicate a successful (e.g., idle) combination of beams and / or frequencies in 508. The UE may determine to use the successful beams and / or frequencies (or a subset thereof) to monitor or receive future communications from the BS. For example, the UE may use (e.g., only) successful beams to monitor the PUCCH, for example, the remainder of the COT.

[0163] As another example, the BS can schedule both DL and UL communications (e.g., in 508). The UE can (e.g., in 510) use the timing of the DL communications to determine whether the UL communications are sufficiently close to the timing of the DL communications to be transmitted without the UE performing a channel access procedure. The determination of whether to perform a channel access procedure can be performed based on the scheduling time of the DL communications and / or the actual timing of the DL communications. Therefore, the determination of whether to perform a channel access procedure can be performed before, simultaneously with, or after receiving the DL communications. The determination of whether to perform a channel access procedure can be performed with or without decoding the DL communications.

[0164] Figures 6 to 13 —Channel Access Process

[0165] Figure 6An eCCA process according to some embodiments is illustrated. The device may sense a frequency range (e.g., cell bandwidth, BWP bandwidth, channel bandwidth, etc.) while waiting for a first delay time (e.g., 8 microseconds in the illustrated example). If no transmission (or noise, etc., e.g., greater than an ED threshold) is detected in the frequency range during the delay period, the device may wait for a random and / or configurable number (e.g., N) of time slots while continuing to sense the frequency range. According to some embodiments, the time slots may include 5 microseconds (e.g., per time slot). If no transmission is detected during multiple time slots (e.g., greater than an ED threshold), the device may determine that the frequency range is available (e.g., at least for the beam used in the eCCA process) and may perform a transmission.

[0166] Figure 7 Two options for the CAT2 LBT process according to some implementations are shown. In one option, the device can use a time slot time (e.g., 5 microseconds) as the listening period. In another option, the device can use a delay time (e.g., 8 microseconds) as the listening period. If no transmission (or noise, etc., greater than the ED threshold) is detected in the frequency range during the listening period, the device can determine that the frequency range is available (e.g., at least for the beam in use) and transmission can be performed.

[0167] Figure 8 An eCCA procedure with CP extension between a DL and a UL transmission is illustrated according to some implementation schemes. The UE may receive the DL transmission prior to the scheduled UL transmission. The UE may determine to perform eCCA prior to the UL transmission (e.g., based on the UL transmission occurring outside the COT associated with the DL transmission, and / or any other reason discussed herein). The UE may perform the eCCA procedure and may determine that a frequency range is available. The UE may determine to use CP extension to reserve a frequency range between the end of the eCCA procedure and the start of the UL transmission. The determination to use CP extension may be based on configuration information, control information, and / or other factors.

[0168] Figure 9A CAT2 LBT procedure with CP extension using a delay time between DL and UL transmissions is illustrated according to some embodiments. The UE may receive the DL transmission before the scheduled UL transmission. The UE may determine to perform CAT2 LBT before the UL transmission (e.g., based on a UL transmission occurring within the COT associated with the DL transmission but after the DL transmission for a period greater than Y, and / or any other reason discussed herein). The UE may further determine to use a delay time (e.g., 8 microseconds) for the LBT procedure, for example, based on configuration information, control information, or other factors. The UE may use the delay time to perform the CAT2 LBT procedure and may determine that a frequency range is available. The UE may determine to use CP extension to reserve a frequency range between the end of the LBT procedure and the start of the UL transmission. The determination to use CP extension may be based on configuration information, control information, and / or other factors.

[0169] Figure 10 A CAT2 LBT procedure with CP extension using a time slot between a DL and UL transmission is illustrated according to some embodiments. The UE may receive the DL transmission before the scheduled UL transmission. The UE may determine to perform CAT2 LBT before the UL transmission (e.g., based on a UL transmission occurring within the COT associated with the DL transmission but after the DL transmission for a period greater than Y, and / or any other reason discussed herein). The UE may further determine, for example, based on configuration information, control information, or other factors, to use a time slot time (e.g., 5 microseconds) for the LBT procedure. The UE may use the time slot time to perform the CAT2 LBT procedure and may determine that a frequency range is available. The UE may determine to use CP extension to reserve a frequency range between the end of the LBT procedure and the start of the UL transmission. The determination to use CP extension may be based on configuration information, control information, and / or other factors.

[0170] Figure 11 This illustrates an eCCA procedure between DL and UL transmissions without CP extension, according to some implementation schemes. The UE may receive the DL transmission prior to the scheduled UL transmission. The UE may determine to perform eCCA prior to the UL transmission (e.g., based on the UL transmission occurring outside the COT associated with the DL transmission, and / or any other reason discussed herein). The UE may perform the eCCA procedure and may determine that the frequency range is available. The UE may determine not to use CP extension to reserve the frequency range between the end of the eCCA procedure and the start of the UL transmission. The determination not to use CP extension may be based on configuration information, control information, and / or other factors.

[0171] Figure 12This illustrates a CAT2 LBT procedure using a delay time between DL and UL transmissions without CP extension, according to some implementation schemes. The UE may receive the DL transmission before the scheduled UL transmission. The UE may determine to perform CAT2 LBT before the UL transmission (e.g., based on a UL transmission occurring within the COT associated with the DL transmission but after the DL transmission for a period greater than Y, and / or any other reason discussed herein). The UE may further determine to use a delay time (e.g., 8 microseconds) for the LBT procedure, for example, based on configuration information, control information, or other factors. The UE may use the delay time to perform the CAT2 LBT procedure and may determine that a frequency range is available. The UE may determine not to use CP extension to reserve a frequency range between the end of the LBT procedure and the start of the UL transmission. The determination not to use CP extension may be based on configuration information, control information, and / or other factors.

[0172] Figure 13 The diagram illustrates a CAT2 LBT procedure using the time slot between the DL and UL transmissions without CP extension, according to some implementation schemes. The UE may receive the DL transmission before the scheduled UL transmission. The UE may determine to perform CAT2 LBT before the UL transmission (e.g., based on a UL transmission occurring within the COT associated with the DL transmission but after the DL transmission for a period greater than Y, and / or any other reason discussed herein). The UE may further determine to use the time slot (e.g., 5 microseconds) for the LBT procedure, for example, based on configuration information, control information, or other factors. The UE may use the time slot to perform the CAT2 LBT procedure and may determine that the frequency range is available. The UE may determine not to use CP extension to reserve the frequency range between the end of the LBT procedure and the start of the UL transmission. The determination not to use CP extension may be based on configuration information, control information, and / or other factors.

[0173] Figures 14 to 18 —Unit bandwidth example

[0174] Figure 14 A channel access procedure for DL ​​transmission using unit bandwidth is illustrated according to some embodiments. As shown, the channel bandwidth or BWP bandwidth 1401 can be divided into four unit bandwidths: 0, 1, 2, and 3 (1402). The BS can sense the four unit bandwidths (e.g., individually; simultaneously) and can determine that unit bandwidths 0 and 2 are idle while bandwidths 1 and 3 are busy (1403). The determination that unit bandwidths 1 and 3 are busy can be based on the detection of transmissions and / or noise on these unit bandwidths. Transmissions and / or noise can be detected at any frequency (or multiple frequencies) within the respective unit bandwidths. Transmissions and / or noise may exceed the energy detection (ED) threshold. Therefore, the BS can schedule DL transmissions on bandwidths 0 and 2 and transmit them to the UE.

[0175] Figure 15 A channel access procedure for UL transmission using a channel or BWP bandwidth is illustrated according to some embodiments. As shown, the channel bandwidth or BWP bandwidth 1401 may not be divided (for the purposes of the illustrated UL transmission and / or channel access procedure) into smaller unit bandwidths. For example, the UE may not be configured to use unit bandwidth, or the unit bandwidth may be the same as the channel or BWP bandwidth. The UE may sense the channel or BWP bandwidth and determine that the channel or BWP bandwidth is idle (1503). Therefore, the UE may transmit the UL transmission to the BS on the channel or BWP bandwidth. The UE may use the entire channel or BWP bandwidth, or any subset of the bandwidth (1505). For example, the UE may use a subset of the bandwidth as indicated in the UL license corresponding to the UL transmission.

[0176] Figure 16 An unsuccessful channel access procedure for UL transmission using a channel or BWP bandwidth is illustrated according to some embodiments. As shown, the channel bandwidth or BWP bandwidth 1401 may not be divided (for the purposes of the illustrated UL transmission and / or channel access procedure) into smaller unit bandwidths. For example, the UE may not be configured to use unit bandwidth, or the unit bandwidth may be the same as the channel or BWP bandwidth. The UE may sense the channel or BWP bandwidth and may determine that the channel or BWP bandwidth is not idle (1603). For example, the UE may detect transmissions and / or noise at any frequency within the channel or BWP bandwidth and may determine that the channel or BWP bandwidth is busy based on this detection. Therefore, the UE may not transmit the UL transmission to the BS on the channel or BWP bandwidth, for example, at the illustrated time. For example, the UE may perform a subsequent, successful channel access procedure before transmitting the UL transmission.

[0177] Figure 17A channel access procedure for UL transmissions using unit bandwidths is illustrated according to some embodiments. As shown, the channel bandwidth or BWP bandwidth 1401 can be divided into four unit bandwidths: 0, 1, 2, and 3 (1402). The UE can determine that it senses the four unit bandwidths (e.g., individually; simultaneously). For example, if a UL license indicates that resources are entirely within a single unit bandwidth, the UE can be configured (e.g., via configuration information 502) to use the unit bandwidth. In the illustrated example, the UL license can schedule UL transmissions entirely within unit bandwidth 1, and in response, the UE can determine that it will use that unit bandwidth for the channel access procedure. In some embodiments, the UE can sense all unit bandwidths (e.g., the four unit bandwidths). In some embodiments, the UE can sense only the unit bandwidth associated with the license, such as unit bandwidth 1. The UE can determine that unit bandwidths 0 and 2 are idle while bandwidths 1 and 3 are busy (1703). The determination that unit bandwidths 1 and 3 are busy can be based on the detection of transmissions and / or noise on these unit bandwidths. Transmissions and / or noise can be detected at any frequency (or multiple frequencies) within the respective unit bandwidths. Transmission and / or noise may exceed the ED threshold. In response to determining the cell bandwidth associated with this permission (e.g., cell bandwidth 1), the UE may, for example, not transmit the UL transmission to the BS at the illustrated time. For example, the UE may perform a subsequent, successful channel access procedure before transmitting the UL transmission.

[0178] Figure 18A channel access procedure for UL transmissions using unit bandwidths is illustrated according to some embodiments. As shown, the channel bandwidth or BWP bandwidth 1401 can be divided into four unit bandwidths: 0, 1, 2, and 3 (1402). The UE can be configured (e.g., via configuration information 502) to use the unit bandwidths for UL transmissions. In the illustrated example, the UL license can be scheduled to extend to UL transmissions across multiple unit bandwidths (e.g., 1 and 2). In response, the UE can determine that the unit bandwidth is used for the channel access procedure. In some embodiments, the UE can sense all unit bandwidths (e.g., the four unit bandwidths). In some embodiments, the UE can sense only the unit bandwidths associated with the license, such as unit bandwidths 1 and 2. In the illustrated example, the UE can sense all four unit bandwidths (e.g., individually; simultaneously) and can determine that unit bandwidths 0 and 2 are idle while bandwidths 1 and 3 are busy (1803). The determination that unit bandwidths 1 and 3 are busy can be based on the detection of transmissions and / or noise on these unit bandwidths. Transmissions and / or noise can be detected at any frequency (or multiple frequencies) within the respective unit bandwidths. Transmission and / or noise may exceed the ED threshold. According to some implementations, if all unit bandwidths (e.g., 1 and 2) scheduled for the UL transmission are idle, the UE can be configured (e.g., via configuration information 502) to transmit the UL transmission. Therefore, the UE may, for example, not transmit the UL transmission to the BS at the illustrated time. For example, the UE may perform a subsequent, successful channel access procedure before transmitting the UL transmission.

[0179] Figure 19 A channel access procedure for UL transmissions using unit bandwidths with specific transmissions of unit bandwidth is illustrated according to some embodiments. As shown, the channel bandwidth or BWP bandwidth 1401 can be divided into four unit bandwidths: 0, 1, 2, and 3 (1402). The UE can be configured (e.g., via configuration information 502) to use the unit bandwidths for UL transmissions. In the illustrated example, the UL license can be scheduled to extend to UL transmissions across multiple unit bandwidths (e.g., 1 and 2). In response, the UE can determine that the unit bandwidth is used for the channel access procedure. In some embodiments, the UE can sense all unit bandwidths (e.g., the four unit bandwidths). In some embodiments, the UE can sense only the unit bandwidths associated with the license, such as unit bandwidths 1 and 2. In the illustrated example, the UE can sense all four unit bandwidths (e.g., individually; simultaneously) and can determine that unit bandwidths 0 and 2 are idle while bandwidths 1 and 3 are busy (1903). According to some implementation schemes, the UE can be configured (e.g., via configuration information 502) to transmit UL transmissions on any combination or subset of the idle cell bandwidth on which the UL transmission is scheduled. Therefore, the UE can transmit UL transmissions to the BS using cell bandwidth 2.

[0180] Additional Information and Implementation Plan

[0181] In some implementations, the BS may receive indications of one or more successful unit bandwidths from the UE (e.g., based on the UE's channel access procedure). The BS may use the successful unit bandwidths for subsequent DL transmissions (e.g., with or without further channel access procedures).

[0182] In a first set of embodiments, an apparatus may include a processor configured to cause a User Equipment (UE) to establish communication with a base station. The processor enables the UE to exchange configuration information with the base station and receive from the base station an uplink grant to schedule a first uplink transmission on at least a first portion of a first channel. The processor enables the UE to determine a Listen-After-Speak (LBT) unit bandwidth based on the configuration information and perform an LBT procedure using the LBT unit bandwidth on the first channel. The processor enables the UE to determine that the LBT procedure is successful on at least a first portion of the first channel, wherein the first portion of the first channel has a bandwidth equal to the LBT unit bandwidth; and in response to determining that the LBT procedure is successful on at least a first portion of the first channel, transmit the first uplink transmission to the base station at least partially on the first portion of the first channel.

[0183] In some implementations, the processor is further configured such that the UE determines that the LBT process is unsuccessful at least on the second portion of the first channel, wherein the first uplink transmission is not transmitted on the second portion of the first channel, wherein the second portion of the first channel has a bandwidth equal to the LBT unit bandwidth.

[0184] In some implementations, the LBT unit bandwidth is determined based on the minimum channel bandwidth associated with the subcarrier spacing indicated in the configuration information.

[0185] In some implementations, the LBT unit bandwidth is determined based on the bandwidth portion indicated in the configuration information.

[0186] In some implementations, in order to exchange configuration information, the processor is further configured to enable the UE to transmit a capability report to the base station, which includes an indication of the LBT unit bandwidth.

[0187] In some implementations, the processor is further configured to cause the UE to transmit an indication of LBT unit bandwidth to the base station, wherein the indication of LBT unit bandwidth includes uplink control information and is multiplexed with a first uplink transmission.

[0188] In some implementations, the processor is further configured to cause the UE to determine whether a first portion of the first channel has bandwidth within a single unit of the LBT unit bandwidth, wherein in response to determining that the first portion of the first channel has bandwidth within a single unit of the LBT unit bandwidth, an LBT procedure is performed on the first channel using the LBT unit bandwidth.

[0189] In some implementations, the processor is further configured to: in response to determining that a first portion of the first channel has bandwidth not within a single cell of the LBT cell bandwidth, cause the UE to use the bandwidth of the first channel to perform the LBT procedure.

[0190] In some implementations, the first portion of the first channel includes bandwidth within at least two units of the LBT unit bandwidth, wherein determining that the LBT process is successful on at least the first portion of the first channel includes determining that the LBT process is successful on each of at least two units of the LBT unit bandwidth in the first portion of the first channel.

[0191] In some implementations, the first portion of the first channel includes the bandwidth within at least two units of the LBT unit bandwidth.

[0192] In some implementations, the first portion of the first channel includes the first unit of at least two units of the LBT unit bandwidth.

[0193] In some implementations, the LBT process fails on the second of at least two units of the LBT unit bandwidth.

[0194] In some implementations, in order to transmit the first uplink transmission to the base station, the processor is configured to, in response to the LBT process failing on the second of at least two units of the LBT unit bandwidth, cause the UE not to transmit on the second of at least two units of the LBT unit bandwidth.

[0195] In some implementations, the LBT unit bandwidth is determined based on cell-specific signaling included in the configuration information.

[0196] In a second set of embodiments, a user equipment (UE) may include a radio component and a processor operatively connected to the radio component and configured to enable the UE to establish communication with a base station. The processor may be further configured to enable the UE to receive configuration information from the base station. The processor may be further configured to enable the UE to receive one or more downlink control information (DCI) messages from the base station. The one or more DCI messages may include downlink grants and uplink grants. The processor may be further configured to enable the UE to determine whether resources used for transmission according to the uplink grant and resources used for reception according to the downlink grant occur within the same channel occupancy time (COT). The processor may be further configured to enable the UE to receive downlink transmissions from the base station according to the downlink grant. The processor may be further configured to enable the UE to determine whether to perform a listen-before-tell (LBT) procedure before performing a transmission according to the uplink grant. The determination of whether to perform the LBT procedure may be based on one or more of the following: determining whether the resources used for transmission under uplink permission and the resources used for reception under downlink permission occur within the same COT; configuration information; one or more indications in one of the one or more DCI messages; and the amount of time between the resources used for reception under downlink permission and the resources used for transmission under uplink permission. The processor may be further configured to cause the UE to transmit uplink transmissions to the base station under uplink permission.

[0197] In some implementations, the UE determines to perform an LBT procedure before transmitting uplink transmission to the base station in accordance with uplink permission, wherein the processor is further configured to cause the UE to select the type of LBT procedure based on one or more indications in one of one or more DCI messages.

[0198] In some implementations, to determine whether to perform an LBT procedure before performing a transmission under an uplink license based on the amount of time between resources used for receiving under a downlink license and resources used for transmitting under an uplink license, the processor is further configured to cause the UE to determine a maximum amount of time Y between the resources used for receiving under a downlink license and resources used for transmitting under an uplink license. The processor may be further configured to cause the UE to compare the maximum amount of time Y with the amount of time between the resources used for receiving under a downlink license and resources used for transmitting under an uplink license. If the amount of time between the resources used for receiving under a downlink license and resources used for transmitting under an uplink license is greater than the maximum amount of time Y, the processor may be configured to cause the UE to perform the LBT procedure. If the amount of time between the resources used for receiving under a downlink license and resources used for transmitting under an uplink license is less than or equal to the maximum amount of time Y, the processor is configured to cause the UE to determine not to perform the LBT procedure.

[0199] In some implementations, the maximum time amount Y is determined based on one of the following: the maximum value of K2, where K2 describes the delay between the first DCI message and the first uplink transmission scheduled by the first DCI message; the default value of K2; the maximum value of K1, where K1 describes the delay between the first downlink transmission and the first uplink transmission including an acknowledgment of the first downlink transmission; a cell-specific value of K1; and a value indicated in the configuration information.

[0200] In some implementations, the UE determines to perform an LBT procedure before transmitting uplink transmission to the base station in accordance with uplink permission, wherein the processor is further configured to enable the UE to determine whether to transmit cyclic prefix extension before uplink transmission.

[0201] In a third set of embodiments, an apparatus may include a processor configured to cause a base station to establish communication with a user equipment (UE). The processor may be further configured to cause the base station to perform a Listen-Before-Speak (LBT) procedure and determine that the LBT procedure indicates that at least a first portion of the channel is idle. In response to determining that at least a first portion of the channel is idle, the base station may transmit downlink communication to the UE on the first portion of the channel. The processor may be further configured to cause the base station to transmit a downlink control information (DCI) message to the UE that schedules uplink communication and indicates that the first portion of the channel is idle. The processor may be further configured to cause the base station to receive uplink communication from the UE on the first portion of the channel.

[0202] In some implementations, multiple beams are used to perform the LBT process.

[0203] In some implementations, the first portion of the channel is determined to be idle by the first beam of a plurality of beams.

[0204] In some implementations, the first portion of the channel is determined to be non-idle by the second beam of a plurality of beams.

[0205] In some implementations, the second beam determines that the second portion of the channel is idle.

[0206] In some implementations, the DCI message indicates that the first portion of the channel is idle with respect to a first Transmission Control Indication (TCI) state associated with a first beam, but does not indicate that the first portion of the channel is idle with respect to a second TCI state associated with a second beam. The DCI message may further indicate that the second portion of the channel is idle with respect to a second TCI state.

[0207] In some implementations, downlink communication is transmitted during the channel occupancy time associated with the LBT process, and the DCI message includes an indication of whether uplink communication is scheduled during the channel occupancy time associated with the LBT process.

[0208] In some implementations, the DCI message includes an indication of the type of LBT procedure performed by the UE before transmitting uplink communication.

[0209] In some implementations, the processor is further configured to enable the base station to broadcast system information, including an indication of bandwidth associated with the LBT process.

[0210] In various implementation schemes, various combinations of the above implementation schemes can be combined together.

[0211] Another exemplary implementation may include a method comprising: a wireless device performing any or all of the foregoing examples.

[0212] Another exemplary embodiment may include a wireless device comprising: an antenna; a radio component coupled to the antenna; and a processing element operatively coupled to the radio component, wherein the device is configured to implement any or all of the foregoing examples.

[0213] Another exemplary embodiment may include an apparatus comprising a processing element configured to cause a wireless device to implement any or all of the foregoing examples.

[0214] Another set of exemplary embodiments may include a non-transitory computer-accessible memory medium comprising program instructions that, when executed at a device, cause the device to implement any or all of the portions of any of the foregoing examples.

[0215] Another exemplary set of implementations may include a computer program that includes instructions for performing any or all of the portions of any of the examples described above.

[0216] Another exemplary set of embodiments may include an apparatus that includes means for performing any or all elements of any of the examples described above.

[0217] By interpreting each message / signal X received by the user equipment (UE) in the DL as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the UL as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station. Furthermore, methods described relative to the base station can be interpreted as methods used for the UE in a similar manner.

[0218] In addition to the exemplary embodiments described above, further embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0219] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0220] In some implementations, a device (e.g., UE 106 or 107) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from the memory medium and execute the program instructions, wherein the program instructions can be executed to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset or combination of any such subset of any method implementations described herein). The device may be implemented in any of a variety of forms.

[0221] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0222] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A method for wireless communication, comprising: At the User Equipment (UE): Establish communication with the base station; Exchange configuration information with the base station; Receive from the base station an uplink permission to schedule a first uplink transmission on at least a first part of the first channel; The Listen-Before-Speak (LBT) unit bandwidth is determined based on the configuration information, wherein the LBT unit bandwidth is the larger of the following: The bandwidth of the bandwidth portion indicated in the configuration information is divided by an integer; or Minimum unit bandwidth based on minimum channel bandwidth per subcarrier spacing (SCS); The LBT process is performed using the LBT unit bandwidth on the first channel; The LBT process is determined to be successful on at least a first portion of the first channel, wherein the first portion of the first channel has a bandwidth equal to the bandwidth of the LBT unit; as well as In response to the determination that the LBT process was successful on at least the first portion of the first channel, the first uplink transmission is transmitted to the base station on at least part of the first portion of the first channel.

2. The method according to claim 1, further comprising: The LBT process is determined to be unsuccessful at least on the second portion of the first channel, wherein the first uplink transmission is not transmitted on the second portion of the first channel, wherein the second portion of the first channel has a bandwidth equal to the LBT unit bandwidth.

3. The method according to claim 1, further comprising: The LBT unit bandwidth indication is transmitted to the base station, wherein the LBT unit bandwidth indication includes uplink control information and is multiplexed with the first uplink transmission.

4. The method of claim 1, wherein the first portion of the first channel includes bandwidth within at least two units of the LBT unit bandwidth, wherein determining that the LBT process is successful on at least the first portion of the first channel includes determining that the LBT process is successful on each of the at least two units of the LBT unit bandwidth of the first portion of the first channel.

5. The method according to claim 1, wherein: The first portion of the first channel includes the bandwidth within at least two units of the LBT unit bandwidth; The first portion of the first channel includes a first unit among the at least two units of the LBT unit bandwidth; The LBT process failed in the second of the at least two units of the LBT unit bandwidth; and In order to transmit the first uplink transmission to the base station, the method further includes responding to the failure of the LBT process on the second unit of the at least two units of the LBT unit bandwidth, such that the UE does not transmit on the second unit of the at least two units of the LBT unit bandwidth.

6. An apparatus comprising: A processor configured to cause a user equipment (UE) to perform the method according to any one of claims 1-5.

7. The apparatus of claim 6 further includes a radio component operatively coupled to the processor.

8. A computer program product comprising program instructions configured to cause a device to perform the method according to any one of claims 1-5.

Images