Reception of control information in NR-U

By employing multiple monitoring configurations based on channel occupancy indications, the WTRU optimizes control information reception in NR-WTRUs, addressing inefficiencies in unlicensed spectrum use and enhancing reliability and power management.

JP7588081B2Active Publication Date: 2024-11-21INTERDIGITAL PATENT HOLDINGS INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2021547362
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-11-05
Filing Date
2020-02-10
Publication Date
2024-11-21
Estimated Expiration
2040-02-10

Smart Images

  • Figure 0007588081000001
    Figure 0007588081000001
  • Figure 0007588081000002
    Figure 0007588081000002
  • Figure 0007588081000003
    Figure 0007588081000003
Patent Text Reader

Abstract

The WTRU may receive multiple monitoring configurations. The multiple monitoring configurations may be associated with multiple subbands. The WTRU may apply a monitoring configuration based on the location of a slot inside or outside the COT. For example, the WTRU may apply (e.g., use) a first monitoring configuration outside the COT. The WTRU may apply a second monitoring configuration within the first slot of the COT. The WTRU may apply a third monitoring configuration to a slot of the COT subsequent to the first slot of the COT. The WTRU may switch back to the first monitoring configuration provided that the COT has ended.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Concerning reception of control information in NR-U. [Background technology]

[0002] Cross-references to related cases This application claims the benefit of U.S. Provisional Patent Application No. 62 / 804,993, filed February 13, 2019, U.S. Provisional Patent Application No. 62 / 829,169, filed April 4, 2019, U.S. Provisional Patent Application No. 62 / 840,593, filed April 30, 2019, and U.S. Provisional Patent Application No. 62 / 930,768, filed November 5, 2019, the contents of which are incorporated by reference in their entireties.

[0003] Mobile communications is continuously evolving and is already on the doorstep of its fifth stage - 5G. Summary of the Invention [Problem to be solved by the invention]

[0004] Provided are systems, methods, and means associated with receiving control information in a New Radio (NR) wireless transmit / receive unit (WTRU). [Means for solving the problem]

[0005] Systems, methods, and means associated with receiving control information in a New Radio (NR) radio transmit / receive unit (WTRU) may be provided. The WTRU may receive a plurality of monitoring configurations. The plurality of monitoring configurations may be associated with a plurality of subbands, and the WTRU may apply a first monitoring configuration of the plurality of monitoring configurations to the plurality of subbands (e.g., outside of a channel occupancy time (COT)). The first monitoring configuration may include being configured to monitor a search space for each of the plurality of subbands (e.g., using a first periodicity). The WTRU may receive a COT indication associated with a first subband of the plurality of subbands. The COT indication may indicate a start of the COT. The COT indication may indicate a duration of the COT. The WTRU may apply a second monitoring configuration of the plurality of monitoring configurations to the first subband of the plurality of subbands (e.g., during the COT). The second monitoring configuration may include being configured to monitor the search space in each slot of the COT associated with the second monitoring configuration (e.g., using a second periodicity). The WTRU may apply a third monitoring configuration of the multiple monitoring configurations to the first subband between the received COT indication and a first slot boundary in the COT. The WTRU may switch from the second monitoring configuration to the first monitoring configuration at the end of the COT. [Brief description of the drawings]

[0006] [Figure 1A] FIG. 1 illustrates an example communication system in which one or more embodiments may be implemented. [Figure 1B]FIG. 1B illustrates an exemplary wireless transmit / receive unit (WTRU) of an embodiment that may be used within the communications system of FIG. 1A. [Figure 1C] FIG. 1B illustrates an exemplary embodiment of a radio access network (RAN) and a core network (CN) that may be used within the communications system of FIG. 1A. [Figure 1D] FIG. 1B illustrates a further exemplary RAN and CN of an embodiment that can be used within the communication system of FIG. 1A. [Diagram 2] FIG. 1 illustrates an example of switching between monitoring configurations. [Diagram 3] FIG. 13 is a diagram of an example of switching between monitoring configurations based on PDCCH type. [Figure 4] 1A-1C are diagrams of examples of wideband operation using different monitoring configurations. [Diagram 5] FIG. 1 illustrates an example of switching between monitoring configurations. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] FIG. 1A is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 may enable the multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may utilize one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-tailed Unique Word DFT Spread OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, and Filter Bank Multi-Carrier (FBMC).

[0008] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain situations), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be referred to interchangeably as UEs.

[0009] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B (eNB), a Home Node B (HNB), a Home eNode B (HeNB), a gNB, a NR Node B, a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0010] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for wireless services in a particular geographic area, which may be relatively constant or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, e.g., one for each sector of the cell. In an embodiment, the base station 114a may utilize multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell, e.g., beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0011] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0012] More specifically, as mentioned above, the communication system 100 may be a multiple access system and may utilize one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using Wideband CDMA (WCDMA). WCDMA may include communication protocols, such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

[0013] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE), and / or LTE Advanced (LTE-A), and / or LTE Advanced Pro (LTE-A Pro).

[0014] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as New Radio (NR) radio access, which may establish the air interface 116 using NR.

[0015] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, e.g., using a dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0016] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (e.g., Wireless Fidelity (WiFi)), IEEE 802.16 (e.g., Global Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), and GSM EDGE (GERAN).

[0017] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as an office, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., used by drones), and a roadway. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0018] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various Quality of Service (QoS) requirements, such as different throughput requirements, delay requirements, error resilience requirements, reliability requirements, data throughput requirements, and mobility requirements. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs that utilize the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) that utilizes GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0019] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communications protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) in the TCP / IP Internet protocol suite. The network 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs that may utilize the same RAT as the RAN 104 / 113 or a different RAT.

[0020] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a that may utilize a cellular-based wireless technology and with a base station 114b that may utilize an IEEE 802 wireless technology.

[0021] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any subcombination of the above elements while remaining consistent with an embodiment.

[0022] The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[0023] The transmit / receive element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 can be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 can be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0024] 1B, the transmit / receive element 122 is depicted as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may utilize MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0025] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.

[0026] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may obtain information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as located on a server or home computer (not shown).

[0027] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to other components within the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0028] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or may determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with an embodiment.

[0029] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0030] The processor 118 of the WTRU 102 may be in operative communication with various peripherals 138 including, for example, one or more accelerometers, one or more gyroscopes, a USB port, other communications interfaces / ports, a display and / or any of other visual / audible indicators, for implementing the representative embodiments disclosed herein.

[0031] The WTRU 102 may include a full-duplex radio where the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the UL (e.g., for transmission) and the downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing via a processor (e.g., a separate processor (not shown) or the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or the downlink (e.g., for reception).

[0032] 1C is a system diagram illustrating the RAN 104 and the CN 106, according to an embodiment. As mentioned above, the RAN 104 can communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 can also communicate with the CN 106.

[0033] The RAN 104 may include eNodeBs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNodeBs while remaining consistent with an embodiment. The eNodeBs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, the eNodeB 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0034] Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. As shown in FIG 1C, the eNodeBs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0035] 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. Although each of the above elements is depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity different from the CN operator.

[0036] The MME 162 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0037] The SGW 164 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNodeB handover, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, as well as managing and storing the context of the WTRUs 102a, 102b, 102c.

[0038] The SGW 164 may be connected to a PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0039] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional landline communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0040] Although in Figures 1A-1D the WTRU is described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may use a wired communications interface (e.g., temporarily or permanently) with the communications network.

[0041] In an exemplary embodiment, the other network 112 may be a WLAN.

[0042] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic within and / or outside the BSS. Traffic to a STA originating from outside the BSS may arrive through the AP and be delivered to the STA. Traffic originating from a STA to a destination outside the BSS may be sent to the AP for delivery to the respective destination. Traffic between STAs in the BSS may be sent through the AP, e.g., a source STA may send traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs in the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent (e.g., directly) between a source STA and a destination STA using a direct link setup (DLS). In one representative embodiment, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all of the STAs) in or using an IBSS may communicate directly with each other. IBSS mode communication is sometimes referred to herein as an "ad-hoc" mode of communication.

[0043] When using 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In one representative embodiment, for example, in an 802.11 system, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented. With CSMA / CA, STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected by a particular STA and / or determined to be busy, the particular STA may back off. Within a given BSS, one STA (e.g., only one station) may transmit at any given time.

[0044] High-throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0045] A Very High Throughput (VHT) STA can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. The 160 MHz channel can be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, can pass through a segment parser that can split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed separately for each stream. The streams can be mapped onto two 80 MHz channels and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration can be reversed and the combined data can be transmitted to the Medium Access Control (MAC).

[0046] Sub-1 GHz mode operation is supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. In accordance with a representative embodiment, 802.11ah can support meter-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices can have limited functionality, including, for example, support of (e.g., only) a certain bandwidth and / or limited bandwidth. MTC devices can include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0047] A WLAN system, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, that may support multiple channels and channel bandwidths, includes a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA that supports a minimum bandwidth operating mode among all STAs operating in the BSS. In an 802.11ah example, for a STA (e.g., an MTC type device) that supports (e.g., only supports) the 1 MHz mode, the primary channel may be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) setting may depend on the status of the primary channel. For example, if the primary channel is busy because a STA (that only supports a 1 MHz mode of operation) is transmitting to the AP, the entire available frequency band may be considered busy, even though most of the available frequency band may remain idle and available.

[0048] In the United States, the available frequency bands that can be used by 802.11ah are 902MHz to 928MHz. In South Korea, the available frequency bands are 917.5MHz to 923.5MHz. In Japan, the available frequency bands are 916.5MHz to 927.5MHz. The total available bandwidth for 802.11ah is 6MHz to 26MHz, depending on country regulations.

[0049] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As mentioned above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 utilizing NR radio technology. The RAN 113 may also communicate with the CN 115.

[0050] The RAN 113 may include gNBs 180a, 180b, 180c, although it will be understood that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may transmit wireless signals to and / or receive wireless signals from the WTRU 102a using multiple antennas, for example. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multipoint (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or gNB 180c).

[0051] The WTRUs 102a, 102b, 102c can communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can be varied for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c can communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting for different lengths of absolute time).

[0052] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect to a gNB 180a, 180b, 180c while also communicating / connecting to another RAN, such as the eNodeBs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0053] Each of the gNBs 180a, 180b, 180c can be associated with a particular cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a, 184b, and routing of control plane information to Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c can communicate with each other over the Xn interface.

[0054] The CN 115 shown in Figure 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the above elements is depicted as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity different from the CN operator.

[0055] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating non-access stratum (NAS) signaling, and mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service utilized by the WTRUs 102a, 102b, 102c. Different network slices may be established for different use cases, such as, for example, services relying on ultra-reliable low latency communications (URLLC) access, services relying on high speed mobile (e.g., large capacity mobile) broadband (eMBB) access, and / or services for machine type communications (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0056] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and assigning WTRU / UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notification. The PDU session types may be IP-based, non-IP-based, Ethernet-based, etc.

[0057] The UPFs 184a, 184b may connect to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184a, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homing PDU sessions, handling user plane QoS, buffering downlink packets, as well as providing mobility anchoring.

[0058] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may connect to local data networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.

[0059] In view of Figures 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0060] The emulation device may be designed to perform one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, the one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. The one or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for testing purposes and / or may perform the tests using over-the-air wireless communication.

[0061] The one or more emulation devices can perform one or more functions, including all functions, without being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices can be utilized in a test lab and / or in a test scenario in a non-deployed (e.g., test) wired and / or wireless communication network to perform testing of one or more components. The one or more emulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) can be used by the emulation devices to transmit and / or receive data.

[0062] Unlicensed operations may be performed. Operation in unlicensed frequency bands may be subject to certain limitations on one or more of transmit power control (TPC), RF output power, or power density (e.g., given by average EIRP and average EIRP density at the highest power level). Operation in unlicensed frequency bands may be subject to requirements on the transmitter for out-of-band emissions. The requirements may be specific to the band and / or geographic location.

[0063] Operation may be subject to requirements for a nominal channel bandwidth (NCB). For unlicensed spectrum in the 5 GHz region, an occupied channel bandwidth (OCB) may be defined. The NCB may be at least 5 MHz. The NCB may include the widest band of frequencies, including guard bands, allocated to a single channel. The OCB (e.g., the bandwidth that includes 99% of the power of the signal) may be between 80% and 100% of the declared NCB. For example, during established communication, the device may be allowed to temporarily operate in a mode in which the device's OCB may be reduced to as low as 40% of the device's NCB, with a minimum value of 4 MHz.

[0064] Channel access in unlicensed frequency bands may use a Listen Before Talk (LBT) mechanism, which may be used regardless of whether the channel is occupied or not.

[0065] For a frame-based system, the LBT may be characterized by a Clear Channel Assessment (CCA) time (e.g., approximately 20 μs), a channel occupancy time (e.g., minimum 1 ms, maximum 10 ms), an idle period (e.g., minimum 5% of the channel occupancy time), a fixed frame period (e.g., relatively equal to the channel occupancy time + idle period), a short control signaling transmission time (e.g., maximum 5% duty cycle within a 50 ms observation period), and / or a CAA energy detection threshold.

[0066] For load-based systems (e.g., where the transmit / receive structure may not be fixed in time), the LBT can be characterized by a number N (e.g., corresponding to the number of free idle slots in the extended CCA) instead of a fixed frame period. N can be chosen randomly within a range.

[0067] Deployment scenarios may include different standalone NR-based operations, different variants of dual connectivity operations, and / or different variants of carrier aggregation (CA) (e.g., possibly including different combinations of zero or more carriers for each of the LTE and NR RATs). Dual connectivity operations may include EN-DC with at least one carrier operating according to an LTE radio access technology (RAT), or NR DC with at least two sets of one or more carriers operating according to an NR RAT.

[0068] For example, one or more of the following functionalities may be considered for an LAA system:

[0069] In an LAA system, listen-before-talk (eg, clear channel determination) can be provided.

[0070] LBT may include a mechanism whereby a device applies a clear channel assessment (CCA) check before using a channel. CCA may utilize at least energy detection to determine the presence or absence of other signals on the channel, e.g., whether the channel is occupied or vacant, respectively. LBT may be used in unlicensed bands. Carrier sensing via LBT may be used for fair sharing of unlicensed spectrum. In a single global solution framework, carrier sensing via LBT may be a consideration for fair and friendly operation in unlicensed spectrum.

[0071] In an LAA system, it is possible to provide discontinuous transmission on a carrier with a limited maximum transmission duration.

[0072] In unlicensed spectrum, channel availability may not always be guaranteed. Continuous transmission may or may not be used. Restrictions on the maximum duration of a transmission burst in unlicensed spectrum may be imposed. Discontinuous transmission with a limited maximum transmission duration may be used for LAA (e.g., as a required functionality).

[0073] For LAA systems, carrier selection can be considered. The large available bandwidth of unlicensed spectrum can be used. Carrier selection can be used by LAA nodes to select carriers with low interference, for example. Good coexistence with other unlicensed spectrum deployments can be achieved.

[0074] For LAA systems, transmit power control can be considered. Transmit power control (TPC) can be used, whereby a transmitting device should be able to reduce its transmit power by a factor of 3 dB or 6 dB compared to the maximum nominal transmit power.

[0075] For LAA systems, RRM measurements including cell identification may be considered. Radio resource management (RRM) measurements (e.g., including cell identification) may enable mobility between SCells and robust operation in unlicensed bands.

[0076] For an LAA system, measurements of channel state information (CSI) (e.g., including channel and interference) may be considered. A WTRU operating in an unlicensed carrier may support frequency / time estimation and / or synchronization (e.g., required) to enable RRM measurements and / or to successfully receive information in the unlicensed band.

[0077] In NR (e.g., 3GPP R15 NR), a WTRU may operate using a bandwidth part (BWP) within a carrier. The WTRU may use an initial BWP to access a cell. The WTRU may be configured to use a set of BWPs to continue operation. At a given moment, the WTRU may have an active BWP (e.g., one active BWP). A BWP (e.g., each BWP) may be configured to use a set of CORESETs within which the WTRU may blindly decode PDCCH candidates, e.g., for scheduling, among other things.

[0078] NR may support variable transmission duration and / or feedback timing. With variable transmission duration, PDSCH and / or PUSCH transmissions may occupy a contiguous subset of symbols of a slot. With variable feedback timing, the DCI for DL ​​assignment may include an indication for the timing of feedback to the WTRU (e.g., by pointing to a specific PUCCH resource).

[0079] The WTRU may operate in unlicensed bands for NR. NR operation in unlicensed bands may be supported. For example, NR-based operation in unlicensed spectrum may be specified, including, for example, one or more of initial access, scheduling / HARQ, or mobility, along with coexistence methods with other radio access technologies (RATs) (e.g., LTE-LAA and other incumbent RATs). Deployment scenarios may include one or more of different standalone NR-based operations, different variants of dual connectivity operation (e.g., EN-DC with at least one carrier operating according to the LTE RAT, or NR DC with at least two sets of one or more carriers operating according to the NR RAT), and / or different variants of carrier aggregation (CA), including, for example, possibly different combinations of zero or more carriers for each of the LTE RAT and the NR RAT.

[0080] The LBT can be performed using clear channel determination on, for example, an LBT subband, which can be, for example, 20 MHz. The BWP can be a single LBT subband. The BWP can include multiple LBT subbands.

[0081] The time during which the channel is acquired for transmission can be considered the Channel Occupancy Time (COT) (e.g., sometimes referred to herein as active COT). The COT can be acquired by the WTRU and / or by the gNB and / or can then be shared with other nodes. The total COT duration (e.g., including any sharing) cannot exceed the maximum COT.

[0082] A WTRU may be configured to use multiple monitoring configurations (e.g., PDCCH monitoring configurations). For example, the WTRU may receive multiple monitoring configurations. The multiple monitoring configurations may be associated with multiple subbands. For example, the multiple monitoring configurations may be configured to apply to one or more of the multiple subbands. The WTRU may be triggered to switch or change the monitoring configuration of the PDCCH (e.g., based on RS detection or COT parameters). A monitoring configuration indication for wideband operation may be received by the WTRU. Hierarchical detection of the monitoring configuration indication may be performed (e.g., by the WTRU). Adaptive frequency allocation of the COT may be performed based on the timing of successful channel acquisition on different LBT subbands. For example, in wideband operation, one or more rules may be used to determine valid PDCCH candidates. A frequency allocation of the SPS in wideband operation may be determined.

[0083] The WTRU may switch between monitoring configurations. For example, the WTRU may use a first monitoring configuration until receipt of a first indication. The indication may indicate that the WTRU switches to a second monitoring configuration. For example, the WTRU may determine to switch from the first monitoring configuration to the second monitoring configuration based on the first indication. The WTRU may switch to a third monitoring configuration, for example, after receipt of a second indication to switch monitoring configurations. The WTRU may return to the first monitoring configuration, for example, at a time that depends on the timing of receipt of the first indication.

[0084] The WTRU may perform wideband operation using different monitoring configurations. For example, the WTRU may be configured to use a BWP consisting of multiple LBT subbands. The WTRU may monitor for a first set of DM-RS resources (or COT structure indication) in some (e.g., all) LBT subbands. Upon receiving DM-RS (or COT structure indication) in some LBT subbands, the WTRU may change its PDCCH monitoring configuration for those LBT subbands. The WTRU may continue monitoring for DM-RS (or COT structure indication) on other LBT subbands. At some point in the COT, the network may be able to acquire one of the other subbands. The network may send a signal in the acquired LBT subband indicating that the LBT subband has been acquired. The network may include the updated monitoring configuration for that LBT subband.

[0085] In unlicensed spectrum, the WTRU may not know when the gNB has acquired the channel and / or LBT subbands. The WTRU may use a static PDCCH monitoring pattern. The static PDCCH monitoring pattern may limit the gNB's opportunities to schedule the WTRU within the COT. For example, if the pattern is densified, the WTRU may have a maximum opportunity to be scheduled within the COT. If the pattern is densified, unnecessary battery may be wasted during times when there is no active COT (e.g., times when the network has not acquired the channel or LBT subbands). The WTRU may be able to adapt between different monitoring configurations depending, for example, on whether the channel is within an active COT (e.g., an ongoing COT). The adaptation may be dynamic, for example, to not waste time after the COT is acquired. The maximum COT duration may be 10 ms.

[0086] The appropriate monitoring configuration at a given time may be indicated to the WTRU.To support (eg, ensure) proper use of the COT, greater flexibility in PDCCH monitoring may be used.

[0087] A BWP in an unlicensed channel may consist of multiple LBT subbands (e.g., FIG. 5). The COT may be active in the BWP without requiring all LBT subbands to be acquired by the gNB. In such a case, the WTRU may be enabled to determine which LBT subbands of the COT are active and / or to determine appropriate PDCCH monitoring of some or all CORESETs and search spaces within the BWP.

[0088] The PDCCH monitoring behavior may be changed based on one or more indications.

[0089] The WTRU may be configured to use a parameter (e.g., a set of parameters) to determine when to attempt blind decoding (BD) of PDCCH candidates and / or on which PDCCH candidates to attempt BD. For example, the WTRU may be configured to use one or more of the following: one or more sets of CORESET, one or more sets of search spaces, and / or one or more sets of PDCCH candidates per search space. A CORESET may include an area in which the WTRU may receive PDCCH DM-RS. A search space may include an area in which one or more PDCCH candidates may be mapped. One or more of the set of CORESET, set of search spaces, and / or set of PDCCH candidates may be valid (e.g., at a given moment). The WTRU may perform PDCCH BD on the valid PDCCH candidates. Whether one or more of the set of CORESETs, the set of search spaces, and / or the set of PDCCH candidates are valid at a given moment may depend on at least one of the active channel occupancy time (COT) for the LBT subbands on which one or more of the CORESETs, the search spaces, and / or the PDCCH candidates are expected, the number (e.g., total number) of active LBT subbands, or the number (e.g., total number) of valid CORESETs and / or search spaces and / or PDCCH candidates. For example, the number of PDCCH candidates that the WTRU monitors in an LBT subband may depend on the total number of active LBT subbands. The WTRU may determine the set of PDCCH candidates based on the total number of search spaces, e.g., as a function of the total number of search spaces in the CORESET that are present in the active LBT subbands.

[0090] In an example, the WTRU may be configured to use at least one monitoring configuration. The monitoring configuration may be associated with (e.g., tied to) one or more of a CORESET, a search space, or a PDCCH candidate. The monitoring configuration may indicate at least one of a timing of a monitoring instance, a number of PDCCH candidates, a number of search spaces, or an indexation of one or more of the search space, the PDCCH candidate, or the CORESET. For example, the timing of the monitoring instance may include a duration and / or an offset of the search space (e.g., a valid search space). The number of PDCCH candidates may be associated with the number of BDs that result from the search space and / or the CORESET.

[0091] In an example, the WTRU may select a CORESET, search space, PDCCH candidates, or any combination thereof associated with an active COT. The WTRU may have a first monitoring configuration for one of the combinations (e.g., for the LBT subbands and / or unlicensed channels that are within the active COT, e.g., for multiple subbands as illustrated in FIG. 5). The WTRU may have a second monitoring configuration for one of the CORESETs, search spaces, or PDCCH candidates outside the active COT (e.g., for the LBT subbands and / or unlicensed channels that are not within the active COT). The monitoring configuration for one or more of the CORESETs, search spaces, or PDCCH candidates may depend on the number (e.g., total number) of active LBT subbands and / or the monitoring configuration for one or more of the other CORESETs, other search spaces, or other PDCCH candidates.

[0092] The WTRU may determine whether an LBT subband (e.g., where the CORESET is located) is currently active. For example, the WTRU may determine whether the LBT subband is within an active COT in order to determine an associated monitoring configuration of one or more of the CORESET, search space, or PDCCH candidates.

[0093] FIG. 2 illustrates an example of switching between monitoring configurations.

[0094] FIG. 3 illustrates an example of switching between monitoring configurations based on PDCCH type.

[0095] The WTRU may receive an indication from the gNB indicating when to switch monitoring configurations. Receipt of such an indication may switch the WTRU from one monitoring configuration to another (e.g., see FIG. 2, FIG. 3, FIG. 4, and FIG. 5). For example, receipt of such an indication may switch the WTRU from a first monitoring configuration used for monitoring outside the COT (e.g., for LBT subbands and / or unlicensed channels that are not in the active COT, FIG. 5 may illustrate such multiple subbands) to a second monitoring configuration used for the start slot of the COT (e.g., as shown in FIG. 2, FIG. 3, and FIG. 5). Receipt of such an indication may switch the WTRU at a particular time (e.g., after receiving the indication, e.g., after a certain amount of time after receiving the indication). For example, the switch may be immediate upon receiving the indication. Receipt of such an indication (e.g., possibly tied to slot timing) can be used to indicate to the WTRU to switch to a third monitoring configuration (e.g., used for COT monitoring for the remainder of the COT). Receipt of such an indication can be used, for example, to indicate to the WTRU to switch to the third monitoring configuration at a second particular time (e.g., after receiving the indication, e.g., a certain amount of time after receiving the indication). For example, the second particular time can be at a first slot boundary after receiving the indication. Receipt of such an indication can indicate to the WTRU the timing (e.g., time) at which the WTRU can return to the first monitoring configuration (e.g., at the end of the active COT duration).

[0096] 2 and 5 illustrate an example of switching between monitoring configurations, with FIG. 5 illustrating multiple subbands. FIG. 2 and 5 illustrate an example of switching from a first monitoring configuration outside the COT, to a second monitoring configuration in a first slot of the COT, to a third monitoring configuration for a subsequent slot in the COT, and back to the first monitoring configuration (e.g., subject to the COT ending). In the example shown in FIG. 2 and 5, the WTRU may use the first monitoring configuration until receipt of an indication indicating to the WTRU to switch to the second monitoring configuration (e.g., the indication may indicate the start of the COT, as shown in FIG. 2 and 5). The WTRU may switch to the third monitoring configuration in such a condition (e.g., at the first slot boundary occurring after receipt of an indication indicating to switch monitoring configurations, as shown in FIG. 2 and 5). The WTRU may return to the first monitoring configuration, for example, at the time indicated in the original indication (e.g., an indication to the WTRU to switch to the second monitoring configuration), for example, at the end of the COT, as shown in Figures 2 and 5.

[0097] The indication indicating when to switch monitoring configurations may or may not be associated with an indication of the COT (e.g., an indication of an active COT, e.g., an indication of a start time and an end time of an active COT, as shown in FIG. 2 and FIG. 5). In an example, the indication indicating when to switch monitoring configurations may be the same as that used to indicate the start of a COT on an LBT subband (e.g., DM-RS). In an example, the indication indicating when to switch monitoring configurations may be a different signal. The indication indicating when to switch monitoring configurations may not need to be tied to an indication of an active COT. For example, the WTRU may receive a signal outside the COT to change the monitoring configuration of at least one of, e.g., the CORESET, the search space, or the PDCCH candidates.

[0098] FIG. 5 illustrates an example of a WTRU switching between monitoring configurations. The first monitoring configuration may be used outside the COT, as discussed herein. The first monitoring configuration may use frequent search spaces (SS) with a reduced number of PDCCH candidates (e.g., less than the second monitoring configuration), as discussed herein. The second monitoring configuration may be implemented, as discussed herein, provided that the WTRU receives an indication of the COT (e.g., acquired by the gNB). In an example such as shown in FIG. 5, the WTRU may monitor subband 1 and not monitor subband 2, provided that the WTRU receives an indication of the COT acquired by the gNB for subband 1. The second monitoring configuration may have a frequent SS with more PDCCH candidates than the first monitoring configuration, for example, as discussed herein. The second monitoring configuration may be used, as discussed herein, for example, for a first slot within the COT, as discussed herein. The WTRU may switch to a third monitoring configuration for subsequent slots of the COT, e.g., as discussed herein. The third monitoring configuration may use a less frequent search space (e.g., less than the first or second monitoring configurations, e.g., limited to a first search space in the associated slot) and a maximum amount of PDCCH candidates per slot or search space. The WTRU may switch back to the first monitoring configuration, e.g., on the condition that the COT has ended, as discussed herein.

[0099] DMRS can be detected and used to change the monitoring configuration.

[0100] The WTRU may be configured to detect the presence of at least one DM-RS transmission and / or may determine an appropriate monitoring configuration based on detecting the presence of at least one DM-RS transmission. The WTRU may be configured to use one or more DM-RS resources to attempt blind decoding (BD). The WTRU may be configured to use a set of time instances during which the WTRU may attempt BD (e.g., on one or more DM-RS resources). The DM-RS resource configuration may include the following parameters: CORESET, which may be associated with (e.g., tied to) a DM-RS resource; a PDCCH candidate or set of PDCCH candidates, for a certain monitoring occasion, which may be associated with (e.g., tied to) a DM-RS resource; a search space index, which may be associated with (e.g., to which) a DM-RS resource; a time location of a DM-RS resource (e.g., a time location of a DM-RS resource may include a symbol number and / or a slot number); a DM-RS sequence (e.g., a DM-RS sequence may include an input to a sequence generation function); a DM-RS port (e.g., a DM-RS port between 0 and 11); a DM-RS type (e.g., DM-RS configuration type 1 and / or type 2); a DM-RS maximum length (e.g., single-symbol DM-RS or double-symbol DM-RS); additional DM-RSs (e.g., configured next to a preceding DM-RS symbol); a DM-RS It may include at least one of a CDM group (eg, CDM group 0, {0,1}, {0,1,2}), a RE mapping, and a quasi-colocation with another RS.

[0101] The WTRU may use, for example, a correlation receiver and / or energy detection to detect the presence of a DM-RS. In an example, the WTRU may first attempt energy detection, and if it determines that the energy is above a possibly configurable threshold, the WTRU may use a correlation receiver.

[0102] Upon successful detection of one or many or all DM-RS configurations for an LBT subband and / or unlicensed channel, the WTRU may assume at least one of the following: COT is active in that LBT subband and / or unlicensed channel; COT is active for some (e.g., some or all) LBT subbands associated with (e.g., tied to) one or more DM-RS configurations; monitoring configurations for some (e.g., one or all) CORESETs, search spaces, or PDCCH candidates on one or more LBT subbands have changed.

[0103] The WTRU may assume that COT is active in that LBT subband and / or unlicensed channel, and may modify (e.g., change) the monitoring configuration of any one or combination of the CORESET, search space, or PDCCH candidates associated with (e.g., tied to) that LBT subband and / or unlicensed channel.

[0104] The WTRU may assume that COT is active for some (e.g., all) LBT subbands associated with (e.g., tied to) one or more DM-RS configurations. The WTRU may modify (e.g., change the monitoring configuration) of any one or combination of the CORESET, search space, or PDCCH candidates associated with (e.g., tied to) the appropriate LBT subbands and / or unlicensed channels.

[0105] The WTRU may assume that the monitoring configuration for some (eg, one or all) of the CORESETs, search spaces, or PDCCH candidates on one or more LBT subbands has changed.

[0106] The parameters of the detected DM-RS and / or the presence of the DM-RS may be used in association with (e.g., an indication of) a change in the monitoring configuration. The parameters of the detected DM-RS and / or the presence of the DM-RS may include (e.g., indicate) at least one of the following: a CORESET that may be associated with (e.g., tied to) the DM-RS resource, a PDCCH candidate or set of PDCCH candidates that may be associated with (e.g., tied to) the DM-RS resource, a search space index that may be associated with (e.g., to which) the DM-RS resource, a time location of the DM-RS resource, a DM-RS sequence, a DM-RS port (e.g., a DM-RS port between 0 and 11), a DM-RS type, a DM-RS maximum length, additional DM-RSs, a DM-RS CDM group, a RE mapping, and quasi-co-location with another RS.

[0107] The parameters of the detected DM-RS may indicate one or more sets of CORESET, search space, or PDCCH candidates for which the WTRU may change the monitoring configuration. The parameters of the DM-RS may indicate the change in monitoring configuration (e.g., a required change). As an example, if the WTRU detects a DM-RS having a first sequence, the WTRU may use the first monitoring configuration for the first search space. If the WTRU detects a DM-RS having a second sequence, the WTRU may use the second monitoring configuration for the first search space.

[0108] The DM-RS parameters may indicate the timing (e.g., time) of the next change in the monitoring configuration for one or more of the CORESET, the search space, or the PDCCH candidates. As an example, the DM-RS parameters may indicate to the WTRU the number of symbols remaining in the current COT. The WTRU may use the DM-RS parameters indicating the number of symbols remaining in the current COT to determine when the WTRU may switch from a monitoring configuration (e.g., the current monitoring configuration) to another monitoring configuration (e.g., one applicable for monitoring outside the active COT). The DM-RS parameters may indicate to the WTRU the type of LBT used to acquire a channel for the DM-RS transmission. The indication of the type of LBT used to acquire a channel for the DM-RS transmission may enable the WTRU to determine an appropriate LBT to use for an UL transmission (e.g., an upcoming UL transmission).

[0109] The presence of a DM-RS in a time instance may indicate (e.g., cause) the WTRU to use a first monitoring configuration in the associated time instance. The absence of a DM-RS (e.g., in a time instance) may indicate to the WTRU to use a second monitoring configuration in the associated time instance. The WTRU may determine the absence of a DM-RS (e.g., the absence of a DM-RS). A toggle behavior between multiple monitoring configurations may be created. For example, when the WTRU first detects the presence of a DM-RS, the WTRU may switch to the first monitoring configuration. The WTRU may maintain the first monitoring configuration until the WTRU fails to detect the presence of a DM-RS. The WTRU may switch to the second monitoring configuration when the WTRU fails to detect the presence of a DM-RS. The WTRU may maintain the second monitoring configuration until it successfully detects a DM-RS.

[0110] The association of the DM-RS with the PDCCH type may indicate the timing of the monitoring configuration. As an example, if the DM-RS is associated with (e.g., belongs to) a group-common PDCCH (e.g., transmitted primarily in a common search space), the WTRU may assume that this is an indication to switch from a first monitoring configuration to a second monitoring configuration, e.g., at the start of the COT. If the DM-RS is associated with (e.g., belongs to) a group-common PDCCH (e.g., may be transmitted in a common search space), the WTRU may assume that this is an indication to switch from a third monitoring configuration to a first monitoring configuration, e.g., at the end of the COT. This may be an implicit indication to indicate the start and end of the COT initiated by the gNB. In an example, if a DM-RS is associated with (e.g., belongs to) a PDCCH (e.g., may be transmitted within a WTRU-specific search space), the WTRU may assume that this is an indication to switch from a second monitoring configuration to a third monitoring configuration within the COT. This may be an implicit indication of a monitoring configuration change within the COT initiated by the gNB. Figure 3 illustrates an example of switching between monitoring configurations based on PDCCH type.

[0111] The WTRU may, for example, while blindly detecting a DM-RS resource, buffer some (e.g., some or all) PDCCH candidates associated with (e.g., tied to) the same CORESET as the CORESET of the DM-RS resource. The WTRU may determine that a DM-RS is present and / or that the monitoring configuration to which the WTRU is switching may include PDCCH candidates within that instance of the CORESET and / or search space. If such a determination occurs, the WTRU may attempt to perform (e.g., retroactively) a PDCCH candidate BD on the buffered values ​​(e.g., the buffered PDCCH candidates). In an example, the WTRU may buffer PDCCH candidates in one or more of other LBT subbands, other CORESETs, and / or other search spaces. Detecting a DM-RS in at least one LBT subband, at least one CORESET, and / or at least one search space may trigger blind detection on some (e.g., some or all) buffered candidates. In an example, the monitoring configuration to which the WTRU is switching may be applicable (eg, only applicable) to future occurrences of the CORESET and / or search space.

[0112] Association of the DM-RS to a DCI format may indicate the timing of the monitoring configuration. In an example, if the DM-RS is associated with (e.g., belongs to) a PDCCH carrying DCI format 1_0 (e.g., fallback DCI for DL ​​assignments), the WTRU may assume that this is an indication to switch from a first monitoring configuration to a second monitoring configuration, e.g., at the start of a COT. If the DM-RS is associated with (e.g., belongs to) a PDCCH carrying DCI format 1_0 (e.g., fallback DCI for DL ​​assignments), the WTRU may assume that this is an indication to switch from a third monitoring configuration to a first monitoring configuration, e.g., at the end of a COT. This may be an implicit indication to indicate the start and end of a gNB-initiated COT. In an example, if a DM-RS is associated with (e.g., belongs to) a PDCCH carrying DCI format 1_1, the WTRU may assume that this is an indication of, for example, switching from a second monitoring configuration to a third monitoring configuration within the COT. This may be an implicit indication of a monitoring configuration change within the COT initiated by the gNB.

[0113] CSI-RS can be detected and used to indicate monitoring configuration / monitoring configuration changes.

[0114] The WTRU may be configured to use one or more CSI-RS resource sets. A configured resource set (e.g., each configured resource set) may represent one or more CSI-RS configurations. The WTRU may determine one or more of PDCCH monitoring occasions, parameters, or behaviors based on, for example, the existence of a configured CSI-RS configuration.

[0115] A CSI-RS configuration may be characterized through its operational features (e.g., key operational features), which may include one or more of: scrambling sequence, frequency features (e.g., span across RBs and / or density within RBs), time features (e.g., periodic / aperiodic and / or repetition per frame), power (e.g., zero power vs. non-zero power), or multiplexing (e.g., number of ports and / or TDM / FDM / CDM).

[0116] The WTRU may be configured to use one or more of the CSI-RS configurations having different combinations of operational characteristics (e.g., as described herein). The WTRU may be configured to interpret the (e.g., each) combination of configured CSI-RS configurations as an implicit indication of the associated COT activity and / or a change in the WTRU's behavior. The interpretation of the (e.g., each) combination of configured CSI-RS configurations (e.g., the correspondence between each combination of configured CSI-RS configurations and the COT activity) may be configured semi-statically or dynamically, for example, according to at least one or more of the following: dimensions of the CSI-RS configuration, expected channel activity and / or COT duration, or subbands and / or unlicensed channels per LBT.

[0117] The WTRU may, for example, if the WTRU successfully detects the presence of at least one of the configured CSI-RS configurations, interpret the features and / or parameters of the detected CSI-RS configuration as an indication of at least one of the following events: an active COT in the LBT subband, an expected duration of the COT, the presence of a CORESET (e.g., an already defined CORESET or a new CORESET), or information about the search space.

[0118] In an example, a two-port CDM configuration may exhibit active COT with a first search space, and a four-port CDM may exhibit COT activity with a second search space.

[0119] In an example, the WTRU may determine the QCL characteristics between the PDCCH DMRS and the configured CSI-RS, e.g., from the TCI information included in the CORESET definition. In an example, the WTRU may assume that the PDCCH DMRS and the configured CSI-RS are quasi-co-located for the duration of the COT.

[0120] Monitoring can be performed for COT structure indications.

[0121] The WTRU may be configured to monitor for DCI indicating a COT structure and / or scheduling transmissions using the COT structure. The WTRU may be configured to use a set of PDCCH monitoring parameters or configurations for monitoring for DCI. Such parameters may be configured and / or used based on (e.g., depending on) whether an active COT exists. For example, the WTRU may detect a COT structure indication outside of the COT. The WTRU may have a first set of PDCCH monitoring configurations used to attempt to detect a COT structure indication. If (e.g., activated), the COT is activated, the WTRU may switch to a second (e.g., different) set of PDCCH monitoring configurations. The WTRU may be enabled to receive updates to the COT structure, e.g., for an ongoing COT. The updates may be received via monitoring occasions, e.g., monitoring occasions in the second set of PDCCH monitoring configurations.

[0122] CORESETs, and / or search spaces, and / or PDCCH candidates, and / or DCI types may be associated with different priorities. CORESETs, and / or search spaces, and / or PDCCH candidates, and / or DCI types through which a WTRU may expect to receive a COT indication may have different priorities over other CORESETs, and / or search spaces, and / or PDCCH candidates, and / or DCI types. For example, the WTRU may monitor (e.g., always monitor) configured PDCCH candidates that can be used for COT structure indication. In this example, if the WTRU should (e.g., is required to) drop some PDCCH candidates, the WTRU may drop other PDCCH candidates before dropping candidates that can be used for COT structure indication. For example, the WTRU may be required to drop some PDCCH candidates due to the constraints of the WTRU's blind detection.

[0123] The WTRU may expect a COT structure indication if (e.g., only if) the WTRU receives an indication that the LBT subband has been acquired. The WTRU may receive an indication that the LBT subband has been acquired, e.g., via reception of a DM-RS. The WTRU may attempt blind detection of DCI for a COT structure indication if (e.g., only if) the WTRU is triggered, e.g., by reception of a preceding signal. The WTRU may continue monitoring for a COT structure indication, e.g., for a period of time. In an example, the WTRU may monitor for COT signaling until the end of the COT. The WTRU may receive (e.g., require reception of) another signal, e.g., at or after the end of the COT, to resume monitoring for a COT structure indication.

[0124] State-based PDCCH monitoring can be performed.

[0125] The WTRU may be configured to use different PDCCH monitoring states (e.g., FIG. 2 and FIG. 5). For example, the WTRU may be configured to use a first state (e.g., state A) for out-of-COT PDCCH monitoring. The WTRU may be configured to use a second state (e.g., state B) for PDCCH monitoring at the beginning of the COT. The WTRU may be configured to use a third state (e.g., state C) for PDCCH monitoring for the remainder of the COT. The CORESET, and / or the search space, and / or the PDCCH candidates may be configured to use different sets of parameters. A given set of parameters may be applicable to a given state. For example, each given set of parameters may correspond to each possible state. For example, the search space may have different monitoring periodicities, e.g., a first monitoring period in state A, a second monitoring period in state B, and a third monitoring period in state C. In an example, the number of PDCCH candidates monitored in the search space may depend on the PDCCH monitoring state.

[0126] For example, a transition can be executed from one state to the next state (eg, FIGS. 2 and 5).

[0127] The WTRU may transition from a first state to a second state. The WTRU may be configured to use a rule for determining when to transition from a first PDCCH monitoring state to a second (e.g., next) PDCCH monitoring state. An order of transitions may be determined (e.g., fixed). For example, the order of transitions may include a transition from state A to state B, a transition from state B to state C, and a transition from state C to state A. The rule of transitions may include at least one of a timing relative to a previous transition, an absolute timing, a timing of the current COT, information in a COT structure indication, a dynamic indication, or a lack of an expected signal.

[0128] The rules for a transition may include timing relative to a preceding transition. For example, the WTRU may transition from state C to state A based on the timing of a previous (e.g., immediately preceding) transition, e.g., a transition from state A to state B. Timing values ​​between transitions (e.g., between a transition from state C to state A and a transition from state A to state B) may be fixed or may be indicated. For example, the timing may be indicated in a signal received at the transition from state A to state B. The timing may be indicated in a signal received during the preceding state B or during the current state C.

[0129] The rules for the transition may include absolute timing, for example, the WTRU may transition from state B to state C based on a slot boundary.

[0130] The rules for the transition may include the timing of the current COT. For example, the WTRU may make a different transition (e.g., transition from state B to state C or transition from state C to state A) based on the current timing of the COT. In an example, the WTRU may perform a state transition at a particular time measured from the start of the COT.

[0131] The rules for the transition may be based on information in the COT structure indication. The WTRU may determine when to transition from a first state to a second (e.g., next) state based on the information provided in the COT structure indication. The information may be implicit. For example, receipt of the COT structure indication may result in a state transition. The information may be explicit. For example, the COT structure indication may provide the timing of the next state transition.

[0132] The rule for the transition may be based on a dynamic indication. The WTRU may be dynamically indicated to perform a state transition. For example, upon detecting and receiving a DM-RS, the WTRU may perform a state transition.

[0133] The rules for the transition may be based on the absence of an expected signal. The WTRU may expect a transmission from the network to occur on a particular resource. For example, the absence of detection and / or reception of such a signal may trigger the WTRU to perform a state transition. For example, the WTRU may expect a transmission of a signal indicating that COT is active. If the WTRU does not receive such a signal, the WTRU may transition to state A. In an example, the WTRU may transition to state A regardless of what state the WTRU was in previously.

[0134] A WTRU in DRX may operate with assumptions (e.g., fixed assumptions) regarding the monitoring state during its on-duration. The WTRU may use a PDCCH monitoring configuration that may be configured for DRX monitoring. In an example, the monitoring configuration used during the on-duration may be reused from a state (e.g., a state described above, such as state A). If the WTRU receives a transmission, the WTRU may transition to a different state. The on-duration of the WTRU may match the ongoing COT. If the on-duration of the WTRU matches the ongoing COT, the WTRU may transition (e.g., should transition), for example, from state A to state C. The WTRU may determine whether to transition to a first state or a second state (e.g., from state A to state C or from state A to state B) based on at least one of the timing of receiving the transmission, an indication from the gNB, or a COT structure indication.

[0135] The WTRU may determine whether to transition to a first state or a second state (e.g., from state A to state C, or from state A to state B) based on the timing of the received transmission. For example, based on (e.g., in response to) the CORESET, and / or search space, and / or PDCCH candidates within which the WTRU received a transmission in its on duration, the WTRU may determine the state to which it may transition. Based on (e.g., in response to) the absolute time at which the transmission was received, the WTRU may determine the state to which the WTRU may transition.

[0136] The WTRU may determine whether to transition to a first state or a second state (e.g., from state A to state C, or from state A to state B) based on an indication from the gNB. For example, the WTRU may receive an indication (e.g., in a DCI) that indicates or points to an appropriate state to transition to.

[0137] The WTRU may determine whether to transition to a first state or a second state (e.g., from state A to state C, or from state A to state B) based on the COT structure indication. The WTRU may receive the COT structure indication, which may enable the WTRU to select an appropriate state to transition to.

[0138] The monitoring can be performed outside the COT.

[0139] The WTRU may be configured to use a monitoring configuration that is used outside of an active COT (e.g., in state A). In such a state, the WTRU may assume a reduced number of PDCCH blind detections (e.g., FIG. 5).

[0140] In an example, PDCCH monitoring outside the COT may be bursty. The WTRU may conserve power. For example, the WTRU may have bursts of monitoring occasions. The WTRU may not have periodic monitoring occasions. The bursts (e.g., each burst) may occur periodically.

[0141] The WTRU may perform PDCCH monitoring within the COT. The WTRU may use a monitoring configuration for one or more of a CORESET, a search space, or a PDCCH candidate for a BD of the PDCCH candidate transmitted within the COT. The monitoring configuration may provide a periodicity and / or an offset of the monitoring occasions. In an example, some parameters of the monitoring configuration used during a COT (e.g., an active COT) may depend on parameters of the COT. The timing of the monitoring occasions of the monitoring configuration may be determined by one or more of the following: timing of the COT, true time (e.g., absolute time), LBT subbands, the number (e.g., total number) and / or number (e.g., total number) of one or more of the LBT subbands used in the COT, the CORESET, the search space, or the PDCCH candidates, the number (e.g., total number), the number (e.g., total number) of active COTs, the number (e.g., total number) of carriers without an active COT, the number (e.g., total number) of monitored PDCCH candidates in the COT, or the number (e.g., total number) of non-overlapping CCEs in the COT.

[0142] The timing of the monitoring occasion of the monitoring configuration may be determined by the timing of the COT. In an example, the starting symbol and / or slot of the COT may enable the WTRU to determine the offset of the monitoring configuration. In an example, the timing of the first full slot of the COT may enable the WTRU to determine the offset of the monitoring configuration.

[0143] The timing of the monitoring occasions of the monitoring configuration may be determined by true time (eg, absolute time). For example, a slot number may be used to determine the validity of the monitoring occasion.

[0144] The timing of the monitoring occasions of the monitoring configuration may be determined by the LBT subband. For example, the period and / or offset of the monitoring occasions in the monitoring configuration may depend on the LBT subband on which the PDCCH is blind detected.

[0145] The timing of the monitoring occasions of the monitoring configurations may be determined by the number (e.g., total number) and / or set of LBT subbands used in the COT. For example, if fewer than x LBT subbands are active in the COT, the WTRU may assume a first monitoring period for at least one monitoring configuration. If more than x LBT subbands are active in the COT, the WTRU may assume a second monitoring period for at least one monitoring configuration.

[0146] The timing of the monitoring occasion of the monitoring configuration may be determined by the number or numbers (e.g., total number) of CORESETs, search spaces, or PDCCH candidates. For example, if the COT has a single CORESET (e.g., has only a single CORESET), the WTRU may assume a first set of parameters for the monitoring configuration for the PDCCH candidates in that CORESET. If the COT has multiple CORESETs, the WTRU may assume a second set of parameters for the monitoring configuration associated (e.g., tied to) each CORESET.

[0147] The timing of the monitoring occasion for a monitoring configuration may be determined by the number (e.g., total number) of carriers. For example, depending on the total number of active carriers, the WTRU may apply a particular monitoring configuration and / or a set of parameters for the monitoring configuration to at least one of the CORESET, the search space, or the PDCCH candidates.

[0148] The timing of the monitoring occasion of the monitoring configuration may be determined by the number (e.g., total number) of active COTs. For example, the WTRU may have multiple non-contiguous COTs in a carrier. A COT may include a set of contiguous LBT subbands where the channel is acquired by either the gNB or the WTRU. In an example, the WTRU may have multiple active COTs (e.g., up to one per carrier). In an example, depending on the total number of active COTs, the WTRU may select appropriate parameters for the monitoring configuration.

[0149] The timing of the monitoring occasions of the monitoring configuration may be determined by the number (e.g., total number) of carriers that do not have an active COT. The number of carriers that do not have an active COT may affect the parameters of the monitoring configuration, for example, given that WTRU complexity may be affected due to the requirement that the WTRU continue to monitor signals (e.g., DM-RS) on carriers that do not have an active COT to determine when COT starts and / or when to switch monitoring configurations on those carriers.

[0150] The timing of the monitoring occasion of the monitoring configuration may be determined by the number (e.g., total number) of monitored PDCCH candidates in the COT. For example, the WTRU may expect to monitor PDCCH candidates up to a certain number of sizes of DCI formats in the COT. The WTRU may count the number of sizes for DCI formats in (e.g., each) COT based on the number of configured PDCCH candidates in each search space set.

[0151] The timing of the monitoring occasions of a monitoring configuration may be determined by the number (e.g., total number) of non-overlapping CCEs in the COT. For example, a WTRU may not be expected to be configured with a monitoring configuration that results in a corresponding total number of monitored PDCCH candidates and non-overlapping CCEs per COT that exceeds a corresponding maximum number per COT.

[0152] In an example, the WTRU may switch between monitoring configurations, for example, depending on the timing of the COT. For example, upon receiving an indication that the COT has started, the WTRU may use a first monitoring configuration. At a particular amount of time from the start of the COT, the WTRU may use a second monitoring configuration. The amount of time from the start of the COT may be determined as an offset from the start of the COT. In an example, switching from the first monitoring configuration to the second monitoring configuration may depend on a combination of COT timing and absolute timing. For example, the WTRU may switch monitoring configurations at a particular slot boundary (e.g., at a first slot boundary) within the COT. In an example, switching from the first monitoring configuration to the second monitoring configuration may depend on a numerology including one or more of subcarrier spacing, CP size, or slot duration.

[0153] The WTRU may perform PDCCH monitoring for wideband operation.

[0154] A WTRU may be configured to use a bandwidth part (BWP) that is composed of multiple LBT subbands. Transmission between a gNB and a WTRU and / or transmission between multiple (e.g., two) WTRUs may be possible even if the entire BWP has not been successfully acquired. The WTRU may determine whether the entire BWP has been successfully acquired, for example, by determining a free channel using an LBT per LBT subband. For a COT acquired by a gNB and / or for a COT acquired by another WTRU, the WTRU may be required to monitor for transmissions on at least one LBT subband of the BWP. Such a transmission may indicate to the WTRU at least one of a COT timing, a COT configuration in frequency, or a PDCCH monitoring configuration. The COT timing may include one or more of a starting symbol and / or slot, a duration of the COT, or a final symbol / slot of the COT. The COT configuration in frequency may include one or more of a number or identity of LBT subbands acquired for the COT, or a number of non-contiguous components of the COT. The PDCCH monitoring configuration may be associated with an indication that may be used by the WTRU to determine a monitoring configuration for PDCCH candidates in at least one CORESET and / or search space and / or at least one LBT subband.

[0155] In an example, the WTRU may be configured to monitor at least one DM-RS (or COT structure indication) in at least one LBT subband. Upon detecting the DM-RS (or COT structure indication), the WTRU may assume that the WTRU changes or modifies the monitoring configuration for at least one CORESET, at least one search space, and / or at least one PDCCH candidate. Upon detecting the DM-RSm (or COT structure indication), the WTRU may assume that at least one associated LBT subband is in the active COT. In some configurations, the WTRU may have a one-to-one mapping between the DM-RS (or COT structure indication) and the CORESET and / or search space and / or PDCCH candidate. In such a configuration, upon detecting the DM-RS resource (or COT structure indication), the WTRU may change or modify the monitoring configuration for the mapped CORESET and / or search space and / or PDCCH candidate. In an example configuration, the WTRU may have a one-to-many mapping between the DM-RS and at least two CORESETs and / or search spaces and / or PDCCH candidates. In such a configuration, upon detecting a DM-RS resource, the WTRU may change or vary the monitoring configuration of the at least two CORESETs and / or search spaces and / or PDCCH candidates. In an example configuration, the WTRU may have a many-to-one mapping between the at least two DM-RS resources and one CORESET and / or search space and / or PDCCH candidate. In such a configuration, upon detecting one, some or all DM-RS resources, the WTRU may change or vary the monitoring configuration of the CORESET and / or search space and / or PDCCH candidate.The WTRU may assume a one-to-one, one-to-many, and / or many-to-one mapping between the presence of DM-RS resources and the activation of COT for LBT subbands (e.g., as described herein).

[0156] The mapping between DM-RS resources and associated CORESETs and / or search spaces and / or PDCCH candidates may be configured (e.g., explicitly) by semi-static or dynamic signaling. The mapping between DM-RS resources and associated CORESETs and / or search spaces and / or PDCCH candidates may be done implicitly. For example, depending on the resource on which the WTRU detects a DM-RS, the WTRU may determine the set of CORESETs and / or search spaces and / or PDCCH candidates for which it should change or vary the monitoring configuration.

[0157] The WTRU may be indicated (e.g., explicitly by the gNB) to modify or change a monitoring configuration for a particular LBT subband and / or CORESET and / or search space and / or PDCCH candidate. For example, the WTRU may monitor a first search space in a first LBT subband. The WTRU may receive a DCI indicating a change in monitoring configuration for a second LBT subband and / or CORESET and / or search space and / or PDCCH candidate.

[0158] The configuration of the DM-RS can be detected.

[0159] The WTRU may be configured to monitor a set of DM-RS resources. Such a set may allow granularity in determining which LBT subbands are within the active COT. Such a set may allow granularity in determining a number of CORESETs and / or search spaces and / or PDCCH candidates for which to vary the monitoring configuration. In an example, the WTRU may monitor several (e.g., all) DM-RS configurations simultaneously. The DM-RS configurations (e.g., each of them) may have different timing. The WTRU may monitor several of the configured DM-RS resources. One or more of the following examples may be used: The WTRU may always monitor all configured DM-RS resources. The WTRU may monitor a DM-RS configuration only if all LBT subbands are deemed to be outside the active COT. The WTRU may monitor a DM-RS configuration only if the associated LBT subband is not deemed to be within the active COT. The WTRU may monitor a DM-RS configuration only if the monitoring configuration of the associated CORESET and / or search space and / or PDCCH candidate is used for monitoring outside the active COT.

[0160] The WTRU may use hierarchical DM-RS monitoring. For example, the WTRU may monitor a first DM-RS resource, or a first set of DM-RS resources. The WTRU may begin monitoring a second set of DM-RS resources, e.g., upon successful detection of the first DM-RS resource, or the first set of DM-RS resources. The WTRU may change the monitoring configuration of at least one CORESET and / or search space and / or PDCCH candidate, e.g., upon successful detection of the first DM-RS resource, or the first set of DM-RS resources. The presence or detection of the presence of the second set of DM-RS resources may indicate (e.g., initiate) to the WTRU to attempt to detect at least one of a third set of DM-RS resources. And so on. As an example, the WTRU may have a first DM-RS resource configuration that spans one or more LBT subbands. Upon detecting a DM-RS on that resource, the WTRU may, for example, initiate a BD for a second set of DM-RS resources, each possibly spanning a single LBT subband (e.g., of one or more LBT subbands).

[0161] The WTRU may determine the order of DM-RS resource detection based on at least one of the following: channel measurements, previous LBT attempts, previous frequency composition of the COT, an indication by the gNB, measurements acquired by the WTRU in a prior DM-RS detection, semi-static configuration by the gNB, the presence or absence of a DM-RS in a particular subband of the BWP, or DM-RS indexation.

[0162] The WTRU may determine the order of DM-RS resource detection based on the channel measurement. For example, the WTRU may perform channel occupancy measurements on a set of LBT subbands (e.g., outside the COT). Based on the interference level observed by the WTRU, the WTRU may adapt the order in which the WTRU monitors the DM-RS resources.

[0163] The WTRU may determine the order of DM-RS resource detection based on previous LBT attempts. For example, the WTRU may proactively attempt to acquire one or more LBT subbands (e.g., for UL transmission). The WTRU may change the order in which it monitors DM-RS resources based on whether the WTRU succeeds in acquiring one or more LBT subbands.

[0164] The WTRU may determine the order of detection of DM-RS resources based on the previous frequency composition of the COT. For example, the WTRU may monitor the DM-RS associated with (e.g., tied to) the LBT subbands activated in the previous COT. A timer (e.g., an expiration timer) may be used. For example, the WTRU may prioritize the DM-RS for the previously used LBT subband for (e.g., only for) a configurable amount of time. The timer may be reset, for example, whenever an LBT subband is acquired for the COT. When the timer expires, the WTRU may no longer prioritize such DM-RS configuration.

[0165] The WTRU may determine an order of DM-RS resource detection based on an indication by the gNB, for example, a transmission by the gNB (e.g., in a first COT) may indicate to the WTRU an order of DM-RS detection for a second (e.g., future) COT.

[0166] The WTRU may determine the order of DM-RS resource detection based on measurements the WTRU obtained in a prior DM-RS detection. For example, the WTRU may determine measurements for a subset of the REs of the DM-RS resources. Such measurements may affect the order of DM-RS detection attempts (e.g., future DM-RS detection attempts).

[0167] The WTRU may determine the order of DM-RS resource detection based on a semi-static configuration by the gNB.

[0168] The WTRU may determine the order of DM-RS resource detection based on the presence or absence of DM-RS in a particular subband of the BWP.

[0169] The WTRU may determine an order of DM-RS resource detection based on the DM-RS indexation. The WTRU may prioritize DM-RS resources based on the index of the DM-RS. For example, if the WTRU is configured to monitor multiple DM-RSs (e.g., simultaneously), the WTRU may prioritize some DM-RS resources over others, e.g., based on the processing capability of the WTRU. The number of DM-RSs monitored by the WTRU may vary, e.g., depending on the number of carriers that currently have an active COT. The processing capability of the WTRU may be affected by the number of PDCCH candidates to be blind detected (e.g., simultaneously). For example, the WTRU may have a first set of carriers with an active COT, e.g., resulting in x PDCCH candidates to monitor in a slot. The WTRU may expect to BD (e.g., simultaneously) DM-RS resources in a second set of carriers. The second set of carriers may include those that do not have an active COT. Depending on the combination of the number (e.g., total number) of PDCCH candidates and DM-RS resources, the WTRU may prioritize (e.g., need to prioritize) blind detection of some DM-RS resources and / or possibly drop them.

[0170] In an example, a WTRU can be configured to use DM-RS resources for blind detection with a transmission in the COT. For example, the WTRU can receive a transmission in a first LBT subband and / or the transmission can change the DM-RS configuration of a second LBT subband.

[0171] COT frequency allocation can be performed adaptively.

[0172] For the CORESET and / or search space and / or PDCCH candidates, the WTRU may have multiple (e.g., three) monitoring configurations (e.g., FIG. 2, FIG. 3, and FIG. 4). A first monitoring configuration may be used for operation outside the COT. A second monitoring configuration may be used for the first symbol / slot of the COT. A third monitoring configuration may be used for the remaining symbols / slots of the COT. The COT may be active for a subset of the LBT subbands, e.g., for a wideband. The WTRU may operate with different monitoring configurations depending on, e.g., whether one or more of the CORESET and / or search space and / or PDCCH candidates are within an LBT subband that is part of the COT (see, e.g., FIG. 5).

[0173] The WTRU may be indicated or assumed the timing of switching from an active COT monitoring configuration to an active out-of-COT monitoring configuration. Such timing may be independent of the LBT subband. The WTRU may be indicated, e.g., via the DM-RS BD or via a transmission from the gNB, when to switch the monitoring configuration for the LBT subband from an active out-of-COT configuration to an active COT configuration. Adaptive and / or flexible COT frequency allocation may be enabled (e.g., by an indication described herein). The WTRU may be served by different sets of LBT subbands of the WTRU's active BWP at a given moment, e.g., using adaptive and / or flexible COT frequency allocation.

[0174] The DM-RS BD configurations and / or monitoring configurations of one or more of the CORESET and / or search space and / or PDCCH candidates may depend on whether there are currently no active LBT subbands. The DM-RS BD configurations and / or monitoring configurations of one or more of the CORESET and / or search space and / or PDCCH candidates may depend on the number and / or identity of active LBT subbands. For example, if a single LBT subband is active, the WTRU may use a first set of monitoring configurations on one or more of the CORESET and / or search space and / or PDCCH candidates (e.g., transmitted in that LBT subband). If multiple active LBT subbands exist, the WTRU may use a second set of monitoring configurations on one or more of the CORESET and / or search space and / or PDCCH candidates (e.g., transmitted in the active LBT subbands). In an example, the WTRU may monitor a PDCCH on the first LBT subband if (e.g., only if) the first LBT subband is the only active LBT subband. For example, if there are multiple active LBT subbands, including the first LBT subband, the WTRU may not monitor a PDCCH on the first LBT subband.

[0175] FIG. 4 illustrates an example of wideband operation using different monitoring configurations. FIG. 4 shows an example of a WTRU configured to use a BWP consisting of four LBT subbands. The WTRU may initially monitor for a first set of DM-RS (or COT structure indication) resources in some (e.g., some or all) LBT subbands. Upon receiving a DM-RS (or COT structure indication) in LBT subbands 3 and 4, the WTRU may change its PDCCH monitoring configuration for those two LBT subbands. In the example shown in FIG. 4, the monitoring configuration may depend on the number of active LBT subbands. After receiving a DM-RS (or COT structure indication) in LBT subbands 3 and 4, the active LBT subbands include subbands 3 and 4, as shown in FIG. 4. In this example, for this combination of active LBT subbands, the WTRU may monitor the PDCCH on LBT subband 3 (e.g., but not on subband 4). The WTRU may continue to monitor for DM-RS or COT structure indications on LBT subbands 1 and 2, e.g., possibly on DM-RS resources, with an increased period. At some future time in the COT, the network may be able to acquire LBT subband 2. The WTRU may receive, e.g., a signal (e.g., DCI) in LBT subband 3 indicating that LBT subband 2 has been acquired. The WTRU may receive a DM-RS in LBT subband 2. The WTRU may receive a signal (e.g., DCI) in LBT subband 3 and / or a DM-RS (or COT structure indication) in LBT subband 2. Receipt of either signal may indicate to the WTRU to update the monitoring configuration for LBT subband 2.

[0176] In wideband operation, state-based PDCCH monitoring can be performed.

[0177] The WTRU may maintain different sets of states for different LBT subbands or different sets of subbands. For example, the WTRU may be in state A for a first set of LBT subbands and in state C for a second set of LBT subbands (e.g., simultaneously). State transitions may occur on one or a set of LBT subbands. State transitions may occur on one or a set of CORESET and / or search space and / or PDCCH candidates. For example, the WTRU may maintain a different timer for each LBT subband or for each set of subbands.

[0178] In an example, the WTRU may be triggered to perform a state transition on multiple LBT subbands (e.g., all LBT subbands). The state transition on multiple LBT subbands may be to a particular state, e.g., regardless of the current state associated with the LBT subbands. Multiple LBT subbands may enter the same state via such a transition. For example, there may be a set of LBT subbands in state A, another set of LBT subbands in state B, and yet another set of LBT subbands in state C. The WTRU may receive an indication such that all LBT subbands may transition to state A (e.g., regardless of the state each LBT subband is currently in).

[0179] In an example, a state transition occurring in an LBT subband may result in a state transition occurring in another (e.g., associated) LBT subband. For example, if a WTRU transitions from state A to state B in a first LBT subband (e.g., based on an indication received in the first LBT subband), the WTRU may transition to state B or state C in at least one other LBT subband. The WTRU may not need to monitor (e.g., be allowed to stop monitoring) for a COT structure indication in all LBT subbands once COT is started, e.g., in the first LBT subband.

[0180] The PDCCH candidates can be blind decoded.

[0181] The WTRU may determine the number and / or identity of valid PDCCH candidates in a search space. The determination may depend on the number of search spaces in a slot. The determination may depend on the number of active carriers in a slot. The determination may depend on the number of active carriers with active COT in a slot. The determination may depend on the number of active LBT subbands in a slot. The determination may depend on the number of concurrent DM-RS resources in a slot on which the WTRU may perform BD. The determination may depend on the number of active CORESETs in a slot. The determination may depend on the number of active search spaces in a slot. The determination may depend on a monitoring configuration of a CORESET and / or search space in which the PDCCH candidate is transmitted. The determination may depend on a monitoring configuration of other CORESETs and / or search spaces and / or PDCCHs. The determination may depend on an index. For example, the index may include one or more of an LBT subband index, or a CORESET index, or a search space index, or a PDCCH candidate index, or a carrier index, or a COT index. The decision may depend on the timing of the COT, for example, whether the COT has just started (e.g., the first symbol of the COT) or whether the COT is about to expire. The decision may depend on the previous use of the PDCCH candidate within the COT. The decision may depend on channel occupancy measurements on the resources used by the PDCCH candidate. The decision may depend on the LBT category. In this specification, the time unit of a slot is used. The time unit of a slot can be generalized to any time unit.

[0182] The control signaling can be mapped in frequency.

[0183] The WTRU may be configured to use one or more CORESETs and / or search spaces and / or PDCCH candidates. The mapping of one or more CORESETs and / or search spaces and / or PDCCH candidates to resources (e.g., in frequency) may be based on the acquired set of LBT subbands. For example, the search space may be mapped to one of a number of LBT subbands. Depending on the acquired set of LBT subbands, the WTRU may determine the frequency resource to be used for that search space. In such an example, the CORSET and / or search space and / or PDCCH candidates may hop to different frequency locations (e.g., within different LBT subbands) based on (e.g., as a function of) the acquired set of LBT subbands.

[0184] The search space may have multiple instances, e.g., in the frequency domain and / or the time domain within a slot. The search space (or search space set) and / or CORESET may be mapped to multiple locations within a slot, e.g., multiple locations in frequency and time within a slot. The search space may be mapped to resources in different LBT subbands within a slot. The WTRU may expect some or all parameters of the search space (or search space set) and / or CORESET to be fixed except for certain locations. The parameters of the search space may include an associated beam (or a quasi-co-located QCL of a transmission using the associated beam). The parameters of the search space may include a periodicity (e.g., a slot when the search space exists). The parameters of the search space may include a number of PDCCH candidates for an aggregation level (e.g., each aggregation level). For example, the WTRU may expect the parameters of the search space (or search space set) or CORESET to be fixed except for the frequency and time locations of the instances of the search space within a slot.

[0185] The WTRU may be configured to use an offset in frequency. For example, the WTRU may be configured to use an offset in frequency for each instance of the search space. The offset for an instance of the search space may relate to at least one of resources of the first (or primary) instance of the search space, resources of another instance of the search space, resources of an LBT subband (e.g., each LBT subband), a center frequency of the carrier, resources used for intra-carrier guard bands, and / or resources indicated by a COT structure indication, etc.

[0186] The WTRU may be configured to use an offset for an instance of the search space relative to the resources of the first (or primary) instance of the search space.

[0187] The WTRU may be configured to use an offset for an instance of a search space relative to resources of another instance of the search space. For example, the instances of the search space may be indexed. A search space instance with index i may map to resources that are offset from a search space instance with index i-1.

[0188] The WTRU may be configured to use an offset for the instance of the search space relative to the resources of the LBT subband (e.g., each LBT subband). For example, each instance of the search space (or CORESET) may be associated with a different LBT subband. The resources associated with a search space instance may be defined with respect to the resources of the LBT subband in which the search space instance is located, e.g., using an offset.

[0189] The WTRU may be configured to use an offset for an instance of the search space relative to the center frequency of the carrier. The search space may be on the carrier.

[0190] The WTRU may be configured to use an offset for the instance of the search space that is associated with the resources used for the intra-carrier guard band. In an example, each LBT subband may include an intra-carrier guard band. The intra-carrier guard band may be at the border of the LBT subband.

[0191] The WTRU may be configured to use an offset for the instance of the search space relative to the resource indicated by the COT structure indication. The resource used to indicate the COT structure may be used to determine the location of the instance of the search space. The resource used to transmit the GC-PDCCH to indicate that the gNB has acquired the COT may be used to determine the location of the instance of the search space. In one example, the COT structure may provide a reference resource. The WTRU may determine the location of the instance of the search space based on the reference resource.

[0192] The WTRU may be configured to use multiple types of search spaces. The types of search spaces may include one or more of the following: a search space monitored, for example, all the time, a first set of search spaces, and a second set of search spaces. The first set of search spaces may be monitored outside of an active COT. The second set of search spaces may be monitored during an active COT. In an example, the WTRU may be configured to use at least three types of search spaces as described herein.

[0193] The WTRU may be configured to use a search space that is monitored at each time, e.g., all the time. For the search space that is monitored at each time, the WTRU may monitor an instance of the search space (e.g., all instances of the search space). The WTRU may attempt to blind decode a PDCCH candidate at any instance of the search space in frequency and time within a slot, for example.

[0194] The WTRU may be configured to use a search space monitored outside the active COT. For a search space monitored outside the active COT, the WTRU may monitor an instance of the search space (e.g., all instances of the search space). The WTRU may attempt to blind decode PDCCH candidates in any instance of the search space in frequency and time within a slot, for example.

[0195] The WTRU may be configured to use a search space monitored during an active COT. In cases where a search space is to be monitored during an active COT, the WTRU may not need to monitor all instances of the search space. For example, the WTRU may monitor search space instances located within LBT subbands acquired for the COT. The WTRU may determine a set of active LBT subbands based on an indication received from the gNB. The WTRU may determine a set of active LBT subbands based on the results of an LBT, e.g., an LBT performed by the WTRU to acquire the COT.

[0196] One or more of the features described herein may be used to reduce blind detection.

[0197] The number of PDCCH candidates in the search space may depend on the number of active LBT subbands in the COT. For example, the WTRU may monitor each instance (e.g., all instances) of the search space that is located on an active LBT subband. The number of PDCCH candidates in the search space (e.g., across the instances of the search space) may depend on the total amount of resources for the search space. The total amount of resources for the search space may scale linearly with the number of active LBT subbands.

[0198] The WTRU may monitor a limited number of PDCCH candidates. The WTRU may have blind detection (BD) and / or control channel element (CCE) channel estimation limitations. The BD and / or CCE channel estimation limitations may limit the number of PDCCH candidates the WTRU may monitor in a slot. If the WTRU is to monitor all available instances of a search space (or search space set), the WTRU may be limited to, for example, at most one search space (or search space set) per slot. The WTRU may monitor a subset of all PDCCH candidates in the search space. For example, the WTRU may be able to monitor only a subset of all PDCCH candidates in a search space with a large number of instances, e.g., to not exceed the BD and / or CCE channel estimation limitations of the WTRU. The WTRU may monitor a subset of available search space instances, e.g., to reduce the PDCCH candidate monitoring burden. The WTRU may monitor a subset of available search space instances in a COT (e.g., FIG. 5). The available search space instance may be one located in an active LBT subband. The WTRU may be configured to use a rule to determine a subset of the search space instances. Based on the rule, the WTRU may determine a subset of the search space instances that the WTRU should monitor.

[0199] Some instances in the search space can be dropped.

[0200] The WTRU may monitor the search space instances based on, among other criteria, a priority associated with the search space instance. In an example, the WTRU may only be expected to monitor a single instance of the search space. A priority may be assigned to the search space instances (e.g., each search space instance). In an example, the WTRU may monitor (e.g., monitor only) the search space instance that is in an active LBT subband and has the highest priority. The highest priority may be indicated by the highest or lowest search space instance index.

[0201] The WTRU may determine which search space instance to monitor based on the set of active LBT subbands in the COT. The WTRU may select a single monitored search space instance as a function of the set of active LBT subbands in the COT. The set of active LBT subbands may be associated with the search space instance monitored by the WTRU. For example, each possible set of active LBT subbands may be assigned (e.g., by the network) to a single search space instance monitored by the WTRU.

[0202] The WTRU may monitor a subset of the search space instances. For example, the WTRU may be expected to monitor a subset of the search space instances (e.g., two or more search space instances). The WTRU may determine the subset of the search space instances to be monitored based on a priority associated with the search space instances and / or the set of active LBT subbands in the COT, among other criteria. The WTRU may determine a fixed- or configurable-sized subset of the monitored search space instances based on a selection of the set with the highest priority or as a function of the set of active LBT subbands in the COT. The set with the highest priority may be the set of search space instances whose search space instance index is the highest or the lowest.

[0203] The WTRU may monitor the number of search space instances as allowed according to the BD and / or CCE channel estimation limitations (e.g., reduce the number of possible monitored search space instances to a number that adheres to the BD and / or CCE channel estimation limitations). The WTRU may monitor as many search space instances as allowed without exceeding the BD and / or CCE channel estimation limitations. The search space instances may be ordered in terms of priority. The priority may be determined based on the search space index and / or based on the set of active LBT subbands within the COT. The WTRU may start with an empty monitored set. The WTRU may add the next highest priority search space instance available to the monitored set as long as the BD and / or CCE channel estimation limitations are not exceeded.

[0204] Several instances across multiple search spaces can be dropped.

[0205] The WTRU may decide to drop a search space and / or a search space instance. For example, for cases where multiple search spaces occur in a slot, the WTRU may determine whether the WTRU monitors the entire search space based on the search space index. The WTRU may determine whether monitoring the entire search space would exceed the BD and / or CCE channel estimation limitations. If the search space has multiple possible instances, the WTRU may, for example, drop a subset of the search space instances instead of dropping the entire search space. The WTRU may be configured to use priorities for the search spaces (e.g., different priorities for each search space). The WTRU may be configured to use priorities for the search space instances (e.g., different priorities for each search space instance within each search space). The WTRU may be configured to use rules (e.g., dropping rules) to determine which search space and / or which search space instance to drop, for example, if either the BD or CCE channel estimation limitations are exceeded. The WTRU may drop the search space and / or the search space instance based on the dropping rules. For example, the dropping rules may provide that the priority of the search space is considered first and the priority of the search space instance is considered second. In one example, the dropping rules may provide that the priority of the search space instance is considered first and the priority of the search space is considered second.

[0206] The WTRU may determine the set of search spaces and / or search space instances to be monitored, e.g., by first dropping remaining instances of the lowest priority search space until either a BD restriction and / or a CCE channel estimation restriction is met or until all search space instances of the lowest priority search space have been dropped. For example, if all instances of a relatively low (e.g., lowest) priority search space have been dropped, the WTRU may continue dropping instances of the next relatively low (e.g., next lowest) priority search space until a BD restriction or a CCE channel estimation restriction is met. The instances may be dropped in order of the priority associated with the instances.

[0207] The WTRU may determine the set of search spaces and / or search space instances to be monitored by first dropping relatively low priority search space instances (e.g., the lowest priority search space instances across all search spaces). For example, the WTRU may first drop the lowest priority search space instance of the lowest priority search space. If the BD or CCE channel estimation limitations are not met, the WTRU may continue to drop the lowest priority search space instance of the next lowest priority search space. This may continue until all lowest priority search space instances are dropped or until the BD and / or CCE channel estimation limitations are met. The WTRU may drop the second lowest priority search space instances of some or all search spaces until the BD and / or CCE channel estimation limitations are met. The WTRU may continue to drop higher priority search space instances, e.g., in the same or similar manner. For example, a portion (e.g., an instance) of a number of search spaces may be dropped rather than completely dropping the entire search space.

[0208] One or more of the preceding examples may be performed by first ranking the search space instances of a search space. For example, all search space instances of all search spaces may be ranked or ordered by priority before the WTRU performs each example herein. The ranking or ordering may be determined by ordering the search space instances first or by ordering the search spaces first.

[0209] The WTRU may drop search space instances based on the LBT subband in which they are placed. In an example, the WTRU may drop search space instances as a function of the LBT subband in which they are placed based on the CCE channel estimation limitation. For example, to achieve the CCE channel estimation limitation, the WTRU may drop all search space instances in a first LBT subband. If the limitation is not achieved, the WTRU may drop some or all search space instances in a second LBT subband, and so on, to achieve the limitation. In this case, the LBT subbands may be associated with a priority (e.g., an assigned priority). The priority may depend on the set of acquired LBT subbands.

[0210] For example, DCI can be repeated in multiple search space instances.

[0211] The WTRU may expect that DCI will be repeated in multiple search space instances. The WTRU may combine received signals, for example, to help improve DCI robustness. In an example, a hash function may be used to determine PDCCH candidates in each search space instance. For example, a hash function may be used to ensure that candidate positions in each search space instance have parity in other search space instances.

[0212] The WTRU may be configured to use a subset of the search space instances over which the WTRU may expect the PDCCH transmission to be repeated. The WTRU may not expect the DCI to be transmitted and / or repeated in sets other than the subset.

[0213] The WTRU may expect that the PDCCH candidates are mapped to multiple search space instances. The mapping of the PDCCH candidates to multiple search space instances may support increased aggregation levels. A higher aggregation level may improve robustness.

[0214] The CORESET can span multiple LBT subbands.

[0215] In an example, a WTRU may be configured to use one or more CORESETs. A CORESET (e.g., each CORESET) of the one or more CORESETs may span multiple LBT subbands. Such a CORESET may be considered activated if at least one of the following (e.g., of the following conditions) occurs: CORESET is mapped to it, at least one LBT subband is determined to be within the active COT, CORESET is mapped to it, all LBT subbands are determined to be within the active COT, CORESET is mapped to it, more than x LBT subbands are determined to be within the active COT. For example, x may be configurable (e.g., by semi-static or static signaling) and less than y CORESETs are determined to be activated simultaneously (e.g., for the same COT), e.g., y may be configurable (e.g., by semi-static or static signaling). For example, (e.g., each) CORESET may have an index and the WTRU may consider up to y CORESETs to be activated, e.g., only the y CORESETs having the lowest or highest index values, or the WTRU may receive an explicit indication that a CORESET has been activated or deactivated. For example, the WTRU may receive signaling indicating the set of active CORESETs at a given moment.

[0216] For example, it may be determined (e.g., by the WTRU) that the LBT subband is within the active COT based on detection of at least one of a DM-RS, or reception of a PDCCH (e.g., a group-common PDCCH), or a DCI, or a payload associated with the DCI.

[0217] The search space may be associated with (e.g., tied to) a CORESET. For example, the CORESET may span multiple LBT subbands. The search space may be limited to a (e.g., single) LBT subband. The search space may span multiple LBT subbands. The WTRU may determine, for example, for the case where the search space spans multiple LBT subbands, that the set of PDCCH candidates to blind decode corresponds (e.g., completely) to resource elements located in the activated LBT subbands. The resource elements may include CCEs. The search space may be repeated in multiple LBT subbands. The PDCCH candidates may be repeated in multiple LBT subbands. The CCEs of the PDCCH candidates may be repeated in multiple LBT subbands. In examples, the repetition of the search space in multiple LBT subbands, the repetition of the PDCCH candidates in multiple LBT subbands, and / or the repetition of the CCEs of the PDCCH candidates in multiple LBT subbands may be used to, for example, improve robustness to channel access. The WTRU may consider a PDCCH candidate valid if each CCE is present at least once in an active LBT subband, e.g., for the case where the search space is repeated in multiple LBT subbands. In an example, the WTRU may monitor a PDCCH candidate only if each CCE is present at least once in an active LBT subband.

[0218] For example, for the case where the search space is limited to a single LBT subband, the WTRU may consider some (e.g., some or all) PDCCH candidates in the search space as valid if the LBT subband is active.

[0219] The WTRU may be configured to use multiple search spaces (e.g., search spaces tied to a CORESET), for example, when the WTRU is configured to use a CORESET that spans multiple LBT subbands. The WTRU may be configured to use at least one search space per LBT subband. The WTRU may determine that a set of search spaces (e.g., a subset of all search spaces) is valid for PDCCH monitoring, for example, when multiple LBT subbands are activated. The WTRU may determine the set of search spaces and / or PDCCH candidates to blind decode based on a priority rule (e.g., search space index), for example, as described herein.

[0220] In an example, the WTRU may determine a set of CCEs that make up the search space based on (e.g., as a function of) a subset of active LBT subbands. The subset of LBT subbands may be a subset of all LBT subbands spanned by a CORESET (e.g., the CORESET to which the search space is associated). The WTRU may determine a set of PDCCH candidates, for example, based on a hash function. The hash function may consider a set of CCEs that are associated with (e.g., associated with) the search space. For example, if the CORESET includes (e.g., consists of) a single active LBT subband, the search space may include (e.g., be defined to consist of) CCEs that are located within the active LBT subband. If the CORESET includes (e.g., consists of) a single active LBT subband, the set of PDCCH candidates associated with (e.g., that make up) the search space may be determined by the hash function, for example, by considering the CCEs (e.g., only the CCEs of the active LBT subband). A different set of LBT subbands may be active, for example, at another time instance. At this other time instance, the search space may include (e.g., consist of) a different set of CCEs that are located in the active LBT subbands. The different sets of CCEs that are located in the active LBT subbands may overlap. At this other time instance, the set of PDCCH candidates may be determined by a hash function, for example, by considering a different (e.g., new) set of CCEs that make up the search space.

[0221] Semi-persistent scheduling (SPS) may be performed in wideband. The WTRU may be provided with multiple sets of LBT subbands in which the WTRU may receive SPS PDSCH transmissions. The WTRU may blindly detect the appropriate set at a given moment (e.g., any). The WTRU may determine the appropriate set of LBT subbands on which the WTRU may expect SPS PDSCH transmissions. The WTRU may monitor one or more DM-RS resources to make the determination. (e.g., each) DM-RS resource may be associated (e.g., tied to) a set of LBT subbands on which the WTRU may expect SPS PDSCH. Upon successful detection of a DM-RS resource at a configurable time, the WTRU may expect an SPS PDSCH transmission on the associated resource. The configurable time may be related to the timing of the SPS PDSCH transmission. The WTRU may be provided with a priority rule to determine the order of DM-RS resources or LBT subbands on which the WTRU should attempt BD. Depending on the timing and / or COT duration of the previous transmission, the WTRU may anticipate an SPS PDSCH transmission in a set of LBT subbands (eg, without having to perform BD).

[0222] In examples, the approaches and implementations described herein may be applied to NR, e.g., in NR licensed spectrum, NR unlicensed spectrum, and / or to other scenarios.

[0223] Although the features and elements of the invention are described in specific combinations in the preferred embodiments, each feature or element can be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without other features and elements of the invention.

[0224] Although the solutions described herein discuss LTE, LTE-A, New Radio (NR), or 5G specific protocols, it is understood that the solutions described herein are not limited to this scenario and are applicable to other wireless systems as well.

Claims

1. 1. A wireless transmit / receive unit (WTRU) associated with an unlicensed band, determining a plurality of subbands for the cell; monitoring a first search space in a first subband subset associated with the plurality of subbands according to a first monitoring configuration, the first monitoring configuration including an indication of the subbands belonging to the first subband subset; receiving downlink control information (DCI) indicating a channel occupancy time (COT) and a second subband subset associated with the plurality of subbands, the indicated COT indicating a COT period; monitoring the first search space in the indicated second subband subset for the remainder of the COT; switching from monitoring the first search space in the second subband subset to monitoring the first search space in the first subband subset based on completion of the COT; Processor configured to A WTRU equipped with

2. The WTRU of claim 1 , wherein the first subband subset includes each of the subbands in the plurality of subbands and the second subband subset includes a portion of the subbands in the plurality of subbands.

3. 2. The WTRU of claim 1, wherein the DCI indicates when to switch from monitoring the first search space in the indicated second subband subset to monitoring the first search space in the first subband subset.

4. The WTRU of claim 1 , wherein the processor is further configured to monitor for physical downlink control channel (PDCCH) candidates according to the first monitoring configuration. determining a plurality of subbands for a cell; monitoring a first search space in a first subband subset associated with the plurality of subbands according to a first monitoring configuration, the first monitoring configuration including an indication of the subbands belonging to the first subband subset; receiving downlink control information (DCI) indicating a channel occupancy time (COT) and a second subband subset associated with the plurality of subbands, the indicated COT indicating a COT period; monitoring the first search space in the indicated second subband subset for the remainder of the COT; switching from monitoring the first search space in the second subband subset to monitoring the first search space in the first subband subset based on completion of the COT; A method for providing the above.

6. The method of claim 5 , wherein the first subband subset includes each of the subbands in the plurality of subbands, and the second subband subset includes a portion of the subbands in the plurality of subbands.

7. 6. The method of claim 5, wherein the DCI indicates when to switch from monitoring the first search space in the indicated second subband subset to monitoring the first search space in the first subband subset.

8. monitoring for physical downlink control channel (PDCCH) candidates according to the first monitoring configuration; The method of claim 5 further comprising:

9. The WTRU of claim 1, wherein the processor is further configured to receive a plurality of monitoring configurations associated with the plurality of subbands.

10. The method of claim 1, further comprising: receiving a plurality of monitoring configurations associated with the plurality of subbands. The method of claim 5 further comprising:

11. A wireless transmit / receive unit (WTRU) associated with an unlicensed band, comprising: determining a plurality of subbands for the cell; monitoring a first search space in a first subband subset associated with the plurality of subbands according to a first monitoring configuration, the first monitoring configuration including an indication of the subbands belonging to the first subband subset; receiving downlink control information (DCI) indicating a channel occupancy time (COT) and a second subband subset associated with the plurality of subbands, the indicated COT indicating a COT period; monitoring the first search space in the indicated second subband subset for the remainder of the COT; Processor configured to A WTRU equipped with

Citation Information

Patent Citations

  • Method for transmitting signal on basis of clear channel assessment in unlicensed band channel, and mobile communication system

    US20180220459A1