Shared channel occupancy time operation

Abstract

The present disclosure provides a wireless transmit / receive unit (WTRU) that can monitor LBT sub-bands to determine when a COT is activated. The WTRU can change monitoring based on whether the WTRU receives a full or partial COT structure. The WTRU can interpret a scheduling grant based on a set of acquired LBT sub-bands. The WTRU can determine a channel access priority (CAP) associated with a COT. The WTRU can indicate a CAP used to acquire the COT. The WTRU can receive an indication of a CAP used by a network to start the COT. The WTRU can determine a logical channel restriction based on a CAP associated with the COT. The WTRU can determine whether a logical channel can be included in a transmission during the COT based on the logical channel restriction. The transmission can be via a sub-band during the COT.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 886,170, filed August 13, 2019, the contents of which are incorporated herein by reference. Background Technology

[0003] Mobile communication using wireless communication continues to evolve. The fifth generation can be called 5G. The previous generation (e.g., traditional) mobile communication can be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0004] This article describes the systems, methods, and tools used for shared channel occupancy time (COT) operations.

[0005] In the example, the Wireless Transmit / Receive Unit (WTRU) may include: a processor configured (e.g., programmed with executable instructions to implement a method) to determine the Channel Access Priority (CAP) associated with the COT; to determine a logical channel restriction based on the CAP associated with the COT; to determine whether the logical channel is permitted to be included in a transmission to be sent by the WTRU during the COT using the logical channel restriction; and to transmit a transmission via a subband during the COT, wherein the transmission includes the logical channel if the logical channel restriction allows the logical channel to be included in the transmission.

[0006] Logical channel restrictions can be implemented, for example, by including logical channels if they are associated with a CAP equal to or higher than the CAP associated with the COT, and excluding logical channels if they are associated with a CAP lower than the CAP associated with the COT.

[0007] CAP can indicate, for example, the LBT parameters of the subband used by gNB to obtain COT.

[0008] The CAP associated with COT can be indicated, for example, by the Channel Access Priority Category (CAPC).

[0009] The CAP associated with COT can be received, for example, in a scheduling authorization for resources used to send transmissions during COT.

[0010] If a logical channel constraint allows a logical channel to be included in a transmission, the logical channel may be multiplexed on a TB included in the transmission, wherein the logical channel constraint allows a logical channel to be included in a transmission if the logical channel is associated with a CAP equal to or higher than the CAP associated with the COT.

[0011] The WTRU processor can be further configured with executable instructions to implement a method to further perform operations of: receiving a COT structure indication. The channel access priority associated with the COT can be determined based on the COT structure indication.

[0012] The WTRU processor can be further configured with executable instructions to implement a method to further perform operations of: receiving an indication from the gNB via DCI. The channel access priority associated with the COT can be determined using the indication received via DCI.

[0013] The channel access priority associated with the COT can be indicated by a reference signal configuration. The WTRU processor can be further configured with executable instructions to implement a method to further perform operations of: determining a first channel access priority based on a first reference signal configuration; and determining a second channel access priority based on a second reference signal configuration different from the first reference signal configuration.

[0014] The WTRU processor can be further configured with executable instructions to implement a method to further perform operations of: determining a resource occurring during the COT, wherein the transmission uses the resource for transmission.

[0015] The WTRU processor can be further configured with executable instructions to implement a method to further perform operations of: determining a logical channel (LCH) priority associated with a logical channel; and determining whether the logical channel is associated with a channel access priority equal to or higher than the channel access priority associated with the COT based on the LCH priority associated with the logical channel and the channel access priority associated with the COT. Determining whether the logical channel is allowed to be included in the transmission by the WTRU during the COT can be based on determining whether the logical channel is associated with a channel access priority equal to or higher than the channel access priority associated with the COT.

[0016] In an example, a method for shared COT operation can be implemented. The method can be implemented (e.g., in whole or in part), for example, by one or more devices, apparatuses, and / or systems (e.g., a WTRU, a network node such as a base station including a gNodeB (gNB), etc.), which can include one or more processors configured to perform the method (e.g., in whole or in part) as computer-executable instructions that can be stored on a computer-readable medium or computer program product that, when executed by the one or more processors, perform the method. The computer-readable medium or computer program product can include instructions that cause the one or more processors to perform the method by executing the instructions.

[0017] A wireless transmit / receive unit (WTRU) can monitor one or more LBT subbands to determine when a COT is activated. A WTRU can be configured to monitor one or more (e.g., a subset of) contention-based subbands to determine whether a channel is occupied. For example, a WTRU can (e.g., be configured to) monitor a set / subset of listen-before-talk (LBT) / unlicensed subbands to determine whether a channel is occupied, which can be indicative of an association with a COT being activated. A WTRU can (e.g., be configured to) monitor one or more (e.g., some or all) LBT subbands, for example, for an indication associated with a COT. In an example, a WTRU can be configured to monitor multiple (e.g., all) LBT subbands simultaneously.

[0018] A WTRU can receive an indication of a COT structure for a channel. A WTRU can monitor one or more LBT subbands (e.g., a set of LBT subbands) within a COT based on whether the WTRU has detected, determined, or received an indication of a full or partial COT structure. A WTRU can be configured to receive a transmission in an LBT subband, which can indicate that the subband has been acquired. A WTRU can stop frequency hopping and / or can continue to monitor physical downlink control channel (PDCCH) candidates in an acquired LBT subband. For example, a WTRU can (e.g., upon receiving a transmission in an LBT subband indicating that the subband has been acquired) stop frequency hopping and / or can continue to monitor PDCCH candidates in an acquired LBT subband, for example, until an indication is received regarding a full set of acquired LBT subbands.

[0019] A WTRU can interpret a scheduling grant based on a set of acquired LBT subbands. A WTRU can receive and / or interpret scheduling information. For example, a WTRU can be configured to determine scheduling information based on one or more LBT subbands associated with an active COT. A WTRU’s interpretation of resource allocation in a scheduling grant can be a function of the number and / or set of acquired LBT subbands.

[0020] A WTRU can (e.g., be configured to) operate, for example, with a first (e.g., relatively large) set of configured control resource sets (CORESETs) and a second (e.g., smaller) set of active CORESETs. A WTRU can be configured with multiple CORESETs. A WTRU can be configured to monitor (e.g., in multiple ways) some or all of the multiple CORESETs. A WTRU can receive a first indication at the start of a COT indicating that a subset of LBT subbands is active, for example.

[0021] A WTRU can determine parameters for an LBT procedure for a transmission within a COT based on a priority of the transmission. The priority can depend on a previous transmission or a type of transmission.

[0022] A WTRU can indicate a channel access priority class (CAPC) for acquiring a COT. A WTRU can monitor for the presence of a signal indicating a CAPC for acquiring a COT. A WTRU can receive an indication of a CAPC for starting a COT. A WTRU can receive an indication in a scheduled grant of a CAPC used by a network (e.g., if and / or when acquiring an ongoing COT). A WTRU can determine data having an applicable / sufficient priority to transmit in a COT. A WTRU can determine a set of restricted logical channels that the WTRU can use to construct a transport block (TB) for a scheduled transmission in a COT.

[0023] A WTRU can be given logical channel restrictions for uplink (UL) transmissions within a COT. A WTRU can receive an instruction with logical channel restrictions, e.g., in scheduling downlink control information (DCI). A WTRU can determine logical channels for which data can be included in an uplink transmission. For example, a WTRU can determine logical channels for which data can be included in an uplink transmission based on the restrictions. BRIEF DESCRIPTION OF DRAWINGS

[0024] FIG. 1A FIG. 1 is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments can be implemented.

[0025] FIG. 1B FIG. 2 is a system diagram illustrating an example radio access network (RAN) 104 and an example core network (CN) 106 that can be used within the communications system 100 shown in FIG. 1, according to an embodiment. FIG. 1A FIG. 3 is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system 100 shown in FIG. 1.

[0026] FIG. 1C FIG. 4 is a system diagram illustrating an example RAN 104 and an example CN 106 that can be used within the communications system 100 shown in FIG. 1, according to an embodiment. FIG. 1A FIG. 5 is a system diagram illustrating another example RAN 104 and another example CN 106 that can be used within the communications system 100 shown in FIG. 1, according to an embodiment.

[0027] FIG. 1D FIG. 6 is a system diagram illustrating another example RAN 104 and another example CN 106 that can be used within the communications system 100 shown in FIG. 1, according to an embodiment. FIG. 1A

[0028] FIG. 7 shows an example of a WTRU frequency hopping pattern for monitoring multiple LBT sub-bands. FIG. 2

[0029] FIG. 8 shows an example of a WTRU frequency hopping pattern for monitoring multiple LBT sub-bands. FIG. 3

[0030] FIG. 4 FIG. 9 shows an example of indicating a channel access priority (e.g., CAPC) that can be used for acquiring a shared COT.​

[0031] FIG. 5 Examples are shown of determining logical channel restrictions based on priorities associated with COTs (e.g., as shown in the examples in FIG. 6

[0032] FIG. 6 Examples are shown of sharing COTs based on CAPs (e.g., CAPC) associated with COTs. DETAILED DESCRIPTION

[0033] FIG. 1A is a schematic diagram illustrating an example communications system 100 in which one or more disclosed embodiments can be implemented. The communications system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 can employ 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-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0034] As FIG. 1A ​As shown, the communication system 100 can 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, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can 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 can be referred to as a "station" and / or a "STA") can be configured to transmit and / or receive wireless signals, and can include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot or other wireless devices operating in an industrial and / or an automated processing chain environment), a consumer electronics, a device operating on a commercial and / or industrial wireless network, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d can be interchangeably referred to as a UE.

[0035] The communication system 100 can also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b can 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 the other networks 112. By way of example, the base stations 114a, 114b can be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b can include any number of interconnected base stations and / or network elements.

[0036] The base stations 114a can be part of the RAN 104 / 113, which can 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 stations 114a and / or the base stations 114b can be configured to transmit and / or receive wireless signals on one or more carrier frequencies (which can be referred to as a cell (not shown)). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectrums. A cell can provide wireless service to a particular geographic area that can be relatively fixed, or can change over time as users who are using the cells move throughout the network. The geographic area of a cell can be further split into cell sectors (not shown). For example, the cell associated with the base station 114a can be split into three sectors. Thus, in one embodiment, the base station 114a can include three transceivers, one for each sector of the cell. In one embodiment, the base station 114a can employ Multiple Input Multiple Output (MIMO) techniques and can utilize multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in desired spatial directions.

[0037] The base stations 114a, 114b can communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over the air interface 116, which can 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 can be established using any suitable radio access technology (RAT).

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

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

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

[0041] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, the base station 114a and WTRUs 102a, 102b, 102c can implement LTE wireless access and NR wireless access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[0042] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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), GSM EDGE (GERAN), and the like.

[0043] FIG. 1AThe base station 114b in the embodiment can be, for example, a wireless router, Home Node B, Home eNode B, or access point, and can utilize any suitable RAT for facilitating wireless connectivity access by the WTRUs 102c, 102d within a local area. In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio 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 can implement a radio 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 can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114b can not be required to access the Internet 110 via the CN 106 / 115. FIG. 1A

[0044] The RAN 104 / 113 can be in communication with the CN 106 / 115, which can be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data can have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 can provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 can be in direct or indirect communication with other RANs that employ 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 can employ a NR radio technology, the CN 106 / 115 can also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0045] ​CN 106 / 115 may also act as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

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

[0047] FIG. 1B This is a system diagram illustrating an exemplary WTRU 102. (See diagram below.) FIG. 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the implementation.

[0048] The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. 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. While FIG. 1B The processor 118 and the transceiver 120 are depicted as separate components, it is to be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[0049] The transmit / receive element 122 can be configured to transmit signals to, or receive signals from, a base station (e.g., the 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 IR, UV, or visible light signals, for example. 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.

[0050] Although the transmit / receive element 122 is depicted in the WTRU 102 FIG. 1B In one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) to enable MIMO technology. Thus, the WTRU 102 can

[0051] The transceiver 120 can be configured to modulate information to be transmitted by the transmit / receive element 122 and to demodulate information received by the transmit / receive element 122. As indicated above, the WTRU 102 can be a multi-mode device. Thus, the transceiver 120 can include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0052] The processor 118 of the WTRU 102 can be coupled to, and can receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 can access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 can include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 can 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 can access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

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

[0055] The processor 118 can further be coupled to other peripherals 138, which can 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 can include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® The peripheral device 138 can include one or more sensors, which can be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, a compass 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.

[0056] The WTRU 102 can include a full duplex radio for which transmission and reception of some or all signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and the downlink (e.g., for reception) can be concurrent and / or simultaneous. The full duplex radio can include an interference management unit to reduce and / or substantially eliminate self-interference and / or cross- interference by utilizing hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, the WTRU 102 can include a full duplex radio for which transmission and reception of some or all signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and the downlink (e.g., for reception) can be concurrent and / or simultaneous.

[0057] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 can be in communication with the WTRUs 102a, 102b, 102c over the air interface 116 and can include eNode-Bs 160a, 160b, 160c, although it will be appreciated that the RAN 104 can include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c can each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c can implement MIMO technology. Thus, the eNode-B 160a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

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

[0059] Each of the eNode-Bs 160a, 160b, 160c 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, and the like. As shown, the eNode-Bs 160a, 160b, 160c can communicate with one another over an X2 interface. FIG. 1C

[0060] FIG. 1C The CN 106 can include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements can be owned and / or operated by an entity other than the CN operator.

[0061] The MME 162 can be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an SI interface and can serve as a control node. For example, the MME 162 can be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activations / deactivations, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 can 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.

[0062] The SGW 164 can be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 can generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 can perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0063] The SGW 164 can be connected to the PGW 166, which can 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.

[0064] ​CN 106 can facilitate communications with other networks. For example, the CN 106 can 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

[0065] Although WTRUs are described in FIGS. 1A-1D representative embodiments as wireless terminals, it is contemplated that in certain representative embodiments such a terminal can (e.g., temporarily or permanently) use a wired communication interface with the communication network.

[0066] In representative embodiments, the other network 112 can be a WLAN.

[0067] A WLAN in Infrastructure Basic Service Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can have an access or an interface to a Distribution System (DS) or another type of wired / wireless network. Traffic to and from the STAs that is not addressed to the AP can be sent to and received from the AP. The AP can be responsible for managing access to the BSS, for managing scheduling of STAs to send or receive traffic, and / or responsible for assigning STAs to communication channels. STAs can communicate directly with each other using a direct link, e.g., using a Wi-Fi Direct connection or using an ad-hoc connection.

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

[0069] High Throughput (HT) STAs can use 40 MHz wide channels to communicate, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0070] Very High Throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data can be parsed by a segment parser that can divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be done on each stream separately. The streams can be mapped to the two 80 MHz channels, and the data can be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration can be reversed, and the combined data can be sent to the Medium Access Control (MAC).

[0071] 802.11af and 802.11ah support sub-1 GHz modes of operation. The channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah relative to those used in 802.11η and 802.1 lac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the television white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative implementation, 802.11ah can support meter type control / machine type communications, such as MTC devices in a macro coverage area. MTC devices can have certain capabilities, e.g., limited capabilities, including support for (e.g., only support for) certain bandwidths 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).

[0072] WLAN systems that can support multiple channels and channel bandwidths such as 802.11η, 802.1 lac, 802.11af, and 802.11ah include a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the largest common operating bandwidth supported by all STAs in a BSS. The bandwidth of the primary channel can be set and / or limited by a STA from all STAs operating in the BSS that supports the smallest bandwidth mode of operation. In the example of 802.11ah, for a STA (e.g., MTC type device) that supports (e.g., only supports) a 1 MHz mode, the primary channel can be 1 MHz wide even though other STAs in the AP and BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth modes of operation. Carrier sensing and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, e.g., due to a STA (only supporting a 1 MHz mode of operation) transmitting to the AP, the entire available frequency band can be considered busy even though most of the frequency band remains idle and can be available.

[0073] In the United States, the available frequency bands for 802.11ah to use are 902 MHz to 928 MHz. In Korea, the available frequency bands are 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are 916.5 MHz to 927.5 MHz. The total bandwidth available to 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0074] FIG. 1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 can employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 can also be in communication with the CN 115.

[0075] The RAN 113 can include gNBs 180a, 180b, 180c, although the RAN 113 can include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c can 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 can implement MIMO technology. For example, gNBs 180a, 108b can utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c can implement carrier aggregation technology. For example, the gNB 180a can transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers can be on unlicensed spectrum while the remaining component carriers can be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c can implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0076] The WTRUs 102a, 102b, 102c can use transmission associated with scalable numerology to communicate with gNBs 180a, 180b, 180c. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary from different transmissions, from different cells, and / or from different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c can use subframe or transmission time interval (TTI) of various or scalable lengths (e.g., containing different quantities of OFDM symbols and / or lasting varying lengths of absolute time) to communicate with gNBs 180a, 180b, 180c.

[0077] The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, the WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c can utilize signal s with gNBs 180a, 180b, 180c for both signaling and data transfer without the need for accessing other RANs. In the standalone configuration, WTRUs 102a, 102b, 102c can utilize signals with gNBs 180a, 180b, 180c in an unlicensed frequency spectrum. In the non-standalone configuration, the WTRUs 102a, 102b, 102c can communicate with connecting with gNBs 180a, 180b, 180c while also communicating with other RANs, such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c can implement DC principles to substantially simultaneously communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c can serve as the WTRUs' 102a, 102b, 102c mobility anchor points and gNBs 180a, 180b, 180c can provide additional coverage and / or throughput to the WTRUs 102a, 102b, 102c serving as the WTRUs 102a, 102b, 102c.

[0078] Each of the gNBs 180a, 180b, 180c can be associated with a specific 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 of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown, the gNBs 180a, 180b, 180c can communicate with one another over an Xn interface. FIG. 1D As shown, the gNBs 180a, 180b, 180c can be in communication with one another over an Xn interface.

[0079] FIG. 1DThe illustrated CN 115 can 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. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements can be owned and / or operated by an entity other than the CN operator.

[0080] The AMF 182a, 182b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and can serve as a control node. For example, the AMF 182a, 182b can be responsible for authenticating the WTRUs 102a, 102b, 102c, supporting for different PDU sessions with different requirements (for example, a PDU session for a mission-critical service requiring low latency and high reliability), selecting a particular SMF 183a, 183b, management of the WTRU 102a, 102b, 102c registration area, termination of NAS signaling, mobility management, and the like. The AMF 162 can utilize network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of service being utilized by the WTRU 102a, 102b, 102c. For example, different network slices can be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 can provide a control plane function for switching between the RAN 113 and other RANs (not illustrated) that employ other radio technologies, such as LTE, LTE- A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0081] The SMF 183a, 183b can be connected to AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b can also be connected to UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b can select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b can perform other functions, such as managing and allocating IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type can be IP-based, non-IP based, Ethernet-based, and the like.

[0082] The UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which can provide 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 UPF 184, 184b can perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering of downlink packets, providing mobility anchoring, and the like.

[0083] The CN 115 can facilitate communications with other networks. For example, the CN 115 can include, or can 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. Further, the CN 115 can provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which can include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c can be connected to a D N 185a, 185b through the UPF 184a, 184b via the N3 interface between the UPF 184a, 184b and the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the D N 185a, 185b.

[0084] In view of FIGS. 1A-1D And FIGS. 1A-1D One or more of the functions described herein with reference to one or more of the following can be performed by one or more emulation devices (not shown) in accordance with the corresponding description: WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device described herein. An emulation device can be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device can be used to test other devices and / or to simulate a network and / or WTRU functionality.

[0085] A simulation device can be designed to implement one or more tests of one or more other devices in a laboratory environment and / or operator network environment. The one or more simulation devices can perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more simulation devices can perform the one or more functions, or all functions, while temporarily being implemented / deployed as part of a wired and / or wireless communication network. The simulation devices can be directly coupled to the other device for testing purposes and / or can use over-the-air, wireless communications to perform the testing.

[0086] The one or more simulation devices can perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation devices can be used in a testing laboratory and / or a test scene in a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more simulation devices can be test equipment. Direct RF coupling and / or wireless communications, via RF circuitry (e.g., which can include one or more antennas), can be used by the simulation devices to transmit and / or receive data.

[0087] Unlicensed operation can include operation in an unlicensed band. Operation in an unlicensed band can be based on (e.g., subject to) a transmit power control (TPC), a radio frequency (RF) output power and / or power density (e.g., subject to a limit on the TPC, output power, and / or power density) that can be given (e.g., determined) by an average equivalent isotropically radiated power (EIRP) and / or average EIRP density (e.g., at a highest power level). Operation in an unlicensed band can be (e.g., also) based on (e.g., subject to) a transmitter spurious emission (e.g., subject to a requirement on transmitter spurious emission). The requirement can be specific to a band and / or geographic location.

[0088] Operation (e.g., in an unlicensed band) can be (e.g., also) based on (e.g., subject to) a nominal channel bandwidth (NCB) and / or occupied channel bandwidth (OCB) (e.g., subject to a requirement on NCB and / or OCB) that can be used for unlicensed spectrum (e.g., in a 5 GHz region). The NCB (e.g., the widest band including guard bands assigned to a single channel) can be, for example, always at least 5 MHz. The OCB (e.g., a bandwidth containing 99% of the power of a signal) can be, for example, between 80% and 100% of a declared NCB. A device can be (e.g., allowed to be) operated (e.g., temporarily) in a mode in which the device’s OCB can be reduced down to, for example, as low as 40% of the device’s NCB (e.g., with a minimum of 4 MHz) during an established communication.

[0089] Channel access in unlicensed bands can use listen before talk (LBT). For example, LBT can be utilized regardless of whether a channel is occupied or not.

[0090] LBT can be characterized (e.g., for a frame-based system) using one or more of the following: a clear channel assessment (CCA) time (e.g., about 20 μβ), a channel occupancy time (e.g., a minimum of 1 ms, a maximum of 10 ms), an idle period (e.g., a minimum of 5% of the channel occupancy time), a fixed frame period (e.g., equal to the channel occupancy time plus the idle period), a short control signaling transmission time (e.g., a maximum duty cycle of 5% over a 50 ms observation period), and / or a CCA energy detection threshold.

[0091] For example, for a load-based system, a transmit / receive structure can not be fixed at a certain time. LBT can be characterized (e.g., in a load-based system) using, for example, a number N corresponding to a number of idle idle slots in an extended CCA (e.g., rather than characterizing LBT with a fixed frame period). In some examples, N can be randomly selected within a certain range.

[0092] Operating environments and / or features can be categorized into a variety of deployment scenarios, which can include, for example, different standalone new radio (NR) based operations, different variants of dual connectivity operations (e.g., E-UTRAN NR (EN) dual connectivity (DC) with at least one carrier operating according to a LTE radio access technology (RAT) or NR DC with at least two sets of one or more carriers operating according to a NR RAT), and / or different variants of carrier aggregation (CA) (e.g., different combinations of zero or more carriers of LTE and NR RATs).

[0093] Operating (e.g., functional) features can include, for example, one or more of the following (e.g., to support license assisted access (LAA)): listen before talk (LBT) for clear channel assessment (CCA), discontinuous transmission on a carrier with a limited maximum transmission duration, carrier selection, transmit power control (TPC), radio resource management (RRM) measurements (e.g., including cell identification), and / or channel state information (CSI) measurements (e.g., including channel and interference).

[0094] An LBT procedure can include applying a CCA check before using a channel. A CCA can determine the presence or absence of other signals on a channel (e.g., at least with energy detection), for example, to determine whether a channel is occupied or free, respectively. LBT can be used for unlicensed bands. Carrier sensing via LBT can support fair sharing of unlicensed spectrum.

[0095] Discontinuous transmission and / or limited maximum transmission duration can be implemented on a carrier, e.g., to facilitate fair use. Channel availability can not be guaranteed, e.g., in unlicensed spectrum. Continuous transmission can be prohibited and / or a maximum duration of a transmission burst can be imposed (e.g., to facilitate channel availability in unlicensed spectrum in some geographical regions).

[0096] Carrier selection can be implemented, e.g., to reduce interference. There can be a relatively large available bandwidth of unlicensed spectrum. Carrier selection can be used by a node to select a carrier, e.g., with low interference, which can support coexistence with other unlicensed spectrum deployments.

[0097] TPC can be implemented to adjust transmit power. A transmitting device can reduce transmit power, e.g., 3 dB or 6 dB, compared to a maximum nominal transmit power.

[0098] RRM measurements (e.g., including cell identification) can be implemented, e.g., to support mobility. RRM measurements (e.g., including cell identification) can enable mobility between a serving cell (SCell) and / or between robust operation in unlicensed bands.

[0099] CSI measurements (e.g., including channel and interference) can be implemented, e.g., to support frequency / time estimation and / or synchronization. A WTRU operating in an unlicensed carrier can support frequency / time estimation and / or synchronization, e.g., to support RRM measurements and (e.g., successful) reception of information on unlicensed bands.

[0100] A WTRU can be configured to operate in unlicensed bands. For example, NR operation can be supported in unlicensed bands. Operation (e.g., NR operation) in unlicensed spectrum can include one or more of, e.g., initial access, scheduling / hybrid automatic repeat request (HARQ), mobility, and / or coexistence methods (e.g., with LTE and other RATs). Deployment scenarios can include, e.g., different variants of standalone NR-based operation, different variants of dual connectivity operation (e.g., EN-DC with at least one carrier operating according to LTE RAT or NR-DC with at least two sets of one or more carriers operating according to NR RAT), and / or different variants of carrier aggregation (CA) (e.g., different combinations of zero or more carriers of LTE and NR RATs).

[0101] NR-U can support multiple (e.g., four) categories of channel access schemes for NR unlicensed spectrum (e.g., for NR-U) operation. Channel access categories can include, e.g., immediate transmission after a short switching gap (e.g., Category 1), LBT without random backoff (e.g., Category 2), LBT with random backoff with fixed and variable contention window sizes (e.g., Categories 3 and 4, respectively).

[0102] In one or more examples, LBT can be performed using CCA on an LBT subband (e.g., a 20 MHz subband). A bandwidth part (BWP) can be, for example, one or more subbands (e.g., a single LBT subband or multiple LBT subbands).

[0103] Channel occupancy time (COT) can be a time that a channel has been acquired for transmission. COT can be acquired by a node (e.g., a WTRU or a gNB). COT can be shared with another node. In one or more examples, a total COT duration (e.g., including any sharing) can not exceed a maximum COT.

[0104] A node (e.g., in NR-U) can perform LBT before acquiring an unlicensed channel. For example, COT can start when an unlicensed channel is acquired. COT can last for at most a configured maximum amount of time. For example, COT can be shared between an original transmitter and receiver, e.g., enabling bidirectional transmission during COT. For example, a WTRU can acquire COT (e.g., WTRU-acquired COT) for UL transmission. WTRU-acquired COT can be shared with a gNB so that the gNB can transmit to the WTRU and / or to other WTRUs in some resources of the WTRU-acquired COT. For example, a gNB can acquire COT (e.g., gNB-acquired COT) for DL transmission. gNB-acquired COT can be shared with one or more WTRUs for (e.g., subsequent) UL transmission.

[0105] COT can span multiple LBT subbands. Techniques and / or methods can be used to determine and / or indicate (e.g., to a WTRU) a set of LBT subbands of COT activity. At the start of COT, a gNB can not know (e.g., without determination or indication) the set of acquired LBT subbands before building, for example, an indication of a COT structure to be transmitted. For example, at least at the start of COT, a WTRU can not be informed (e.g., without determination or indication) of the set of LBT subbands. The LBT subbands can not be known or determined (e.g., without determination or indication), for example, in the case of an indication that acquired COT can be transmitted. COT duration can be limited. Efficient use of one or more (e.g., some or all) subbands during a limited COT duration (e.g., including at the start of COT) can depend on techniques and / or methods that determine and / or indicate a set of LBT subbands of COT activity.

[0106] Some COTs can be shared, for example, by multiple WTRUs. For example, if and / or when a channel is acquired for UL transmission, techniques and / or methods can be used to support fairness (e.g., COT distribution or usage) among WTRUs, for example, at a COT switching point. Techniques and / or methods can be used for configured grant (CG) resources (e.g., distribution or usage of CG resources) falling within a COT.

[0107] A COT can be acquired, for example, using a channel access priority. The channel access priority can comprise a channel access priority class (CAPC). The channel access priority can determine or indicate one or more parameters (LBT parameters) associated with LBT. The LBT parameters can be used (e.g., by a base station) to acquire a subband of a COT. The base station can comprise a gNodeB. In an example, a COT can not be used for information or data associated with a lower priority than a priority associated with (e.g., used to determine a selection of) a CAPC. A gNB (e.g., without determination or indication) can not be aware of a CAPC used to acquire a COT, and can not be aware of allowed data priorities for a COT (e.g., for a COT acquired by a WTRU). A transmitting WTRU (e.g., without determination or indication) can not be aware of a priority of data allowed to be included for a (e.g., UL) transmission within a COT acquired by another (e.g., not acquired by the transmitting WTRU).

[0108] A WTRU can be configured to operate in a wideband (e.g., based on a determination or indication of a COT structure). The WTRU can determine or receive an indication associated with a COT. The determination or indication can indicate a COT structure. For example, the WTRU can receive a COT structure indication for wideband operation. The determination and indication can be used interchangeably. The WTRU can receive a COT structure indication, and determine a channel access priority associated with a COT based on the COT structure indication.

[0109] A WTRU can be configured to monitor multiple (e.g., some or all) LBT subbands (e.g., simultaneously / in parallel), for example, for one or more indications associated with one or more COTs. In an example, a WTRU can be configured to monitor (e.g., all) LBT subbands of a carrier simultaneously. A WTRU can be configured with multiple sets of physical downlink control channel (PDCCH) monitoring occasions. A WTRU can be (e.g., additionally and / or alternatively) configured with multiple control resource sets (CORESETs) or search spaces. In an example, a WTRU can be configured with multiple PDCCH monitoring occasions (e.g., or CORESETs or search spaces) (e.g., multiple sets of PDCCH monitoring occasions). In an example, there can be one set of PDCCH monitoring occasions (e.g., or CORESETs or search spaces) per LBT subband. A WTRU can determine a set of active LBT subbands, for example, based on one or more LBT subbands. A WTRU can determine a set of active LBT subbands, for example, based on LBT subbands in which the WTRU has (e.g., successfully) received a demodulation reference signal (DM-RS) and / or a PDCCH (e.g., group common PDCCH (GC-PDCCH)). The set of active LBT subbands can be active, for example, during a portion of (e.g., an existing) COT or for an entire duration of (e.g., an existing) COT.

[0110] A WTRU can receive a COT indication in one or more (e.g., multiple) LBT subbands associated with a COT. For example, a WTRU can receive a COT structure indication in one or more LBT subbands in which the WTRU has detected an active COT. A COT structure indication can or can not include an indication of a set of acquired LBT subbands. A WTRU can (e.g., expect) to receive a (e.g., different, additional, subsequent, or future) COT structure indication that (e.g., explicitly) indicates a set of acquired LBT subbands. A different, additional, subsequent, or future COT structure indication (e.g., relative to an earlier or first COT structure indication) can include a COT structure indication transmitted, for example, within the same COT (e.g., as the earlier or first COT structure indication). Multiple COT structure indications can enable or otherwise support redundancy.

[0111] For example, a WTRU can receive one or more COT indications in one or more (e.g., multiple) LBT subbands in which (e.g., in which one or more of which) the WTRU has detected a COT. In an example, a WTRU can receive a COT structure indication in multiple LBT subbands (e.g., each of the multiple LBT subbands). Each of the multiple COT structure indications can include the same or different information. In an example, (e.g., a WTRU can assume) that multiple (e.g., some or all) COT structure indications can have the same information, which can enable or otherwise support one or more of the following: energy accumulation, additional combining, and / or improved demodulation of COT structure indications.

[0112] A WTRU can (e.g., be configured to) monitor one or more (e.g., a subset of LBT subbands) of LBT subbands (e.g., for indications associated with a COT), for example.

[0113] A WTRU can be configured with one or more LBT subbands (e.g., a subset of LBT subbands). A WTRU can be configured with one or more LBT subbands (e.g., a subset of LBT subbands) on which the WTRU can have one or more PDCCH monitoring occasions (e.g., when there is no active COT). A WTRU can monitor one or more default LBT subbands (e.g., a set of default LBT subbands) (e.g., as described herein). A WTRU can (e.g., be configured to) monitor one or more default LBT subbands, for example, to (e.g., attempt to) detect DM-RS and / or PDCCH transmissions.

[0114] A WTRU can be configured with resources in one or more (e.g., multiple) LBT subbands. A WTRU can be configured with one or more CORESETs, search spaces, and / or PDCCH candidates (e.g., a set of CORESETs, search spaces, and / or PDCCH candidates) in the multiple LBT subbands, for example. A WTRU can (e.g., in a certain / any given instance, such as in one or more slots or time periods) actively monitor (e.g., only) the CORESETs, search spaces, and / or PDCCH candidates in one or more LBT subbands (e.g., the one or more LBT subbands are considered to be default LBT subbands). For example, in any one or more slots or time periods, a WTRU can actively monitor only the CORESETs, search spaces, and / or PDCCH candidates in the default LBT subbands. The default LBT subbands can change (e.g., over time). For example, a WTRU can be configured with (e.g., and can use) a frequency hopping pattern to change the default LBT subbands (e.g., over time, such as periodically, aperiodically, on a schedule, or as needed / autonomously). The frequency hopping pattern can be determined and / or indicated. The frequency hopping pattern can be a function of one or more of, for example, a slot number, a time, a WTRU identifier (ID), and / or the like. The frequency hopping pattern can be indicated (e.g., explicitly) (e.g., via a bitmap in a configuration).

[0115] A WTRU can be configured to receive an indication that a subband has been acquired (e.g., in a transmission in the LBT subband). The WTRU can stop frequency hopping and / or can continue to monitor PDCCH candidates in the acquired LBT subband. For example, the WTRU can stop frequency hopping and can continue to monitor PDCCH candidates in the acquired LBT subband upon receiving a transmission in the LBT subband indicating that the subband has been acquired, e.g., until the WTRU receives an indication of the full set of acquired / active LBT subbands. In (e.g., additional and / or alternative) examples, the WTRU can (e.g., until further determination and / or indication) stop its non-COT monitoring and / or can monitor the confirmed active LBT subband (e.g., using a monitoring pattern applicable for active COT on the LBT subband) based on receiving an indication (e.g., in a transmission in the LBT subband such as the confirmed active LBT subband) indicating that the subband (e.g., the confirmed active LBT subband) has been acquired (e.g., upon receiving the indication that the subband has been acquired). In (e.g., additional and / or alternative) examples, the WTRU can (e.g., until further determination and / or indication) stop its non-COT monitoring and / or can monitor one or more (e.g., some or all) configured subbands (e.g., using a monitoring pattern applicable for active COT on the one or more (e.g., all) LBT subbands), e.g., upon receiving an indication (e.g., in a transmission in the LBT subband) that the subband has been acquired. For example, based on further determination and / or indication, the WTRU can remove one or more LBT subbands from monitoring for the current COT.

[0116] FIG. 2 An example of a WTRU frequency hopping pattern for monitoring multiple LBT subbands is shown. The WTRU can (e.g., as shown in the example operations of FIG. 2 monitor multiple LBT subbands (e.g., in a frequency hopping pattern) and / or can change the monitoring to monitor one or more acquired LBT subbands until an indication of the full set of acquired LBT subbands is received. For example, the WTRU can monitor configured LBT subbands (e.g., LBT subbands 1-4) (e.g., as shown in the example of FIG. 2 monitoring, e.g., micro-slot monitoring of the acquired LBT subband, until the next slot boundary. As shown in FIG. 2As shown, the WTRU can switch to micro-slot monitoring of LBT subband 1. The WTRU can (e.g., at a certain point) receive an instruction informing the WTRU of the complete set of acquired LBT subbands from the COT. FIG. 2 As shown in the example, the WTRU can receive an indication of the complete set of LBT subbands for COT acquisition at the beginning of the next time slot after starting micro-slot monitoring. FIG. 2 As shown in the example, the WTRU can receive a COT structure indication informing it that LBT subbands 1 and 3 are acquired LBT subbands of COT (e.g., the entire set of acquired LBT subbands). The WTRU can switch from micro-slot monitoring to, for example, slot-based monitoring (e.g., in some or all of the acquired LBT subbands). For example, as... FIG. 2 As shown in the example, the WTRU can switch from micro-slot monitoring of LBT subband 1 (e.g., based on full set indication) to slot-based monitoring of acquired / active LBT subbands 1 and 3 during COT.

[0117] FIG. 3 An example of a WTRU frequency hopping pattern used to monitor multiple LBT subbands is shown. For example, the WTRU can (e.g., as...) FIG. 3 As illustrated in the exemplary operation, monitoring of multiple LBT subbands (e.g., subbands 1-4 in a frequency hopping pattern) and / or monitorable LBT subbands (e.g., including one or more unacquired subbands) based on indications of one or more acquired subbands (e.g., from frequency hopping pattern to micro-slot monitoring) continues until an indication of the complete set of LBT subbands is received. For example, WTRU (e.g., based on...) FIG. 3 The exemplary operation shown may (e.g., be configured to) behave similarly to another WTRU (e.g., based on...). FIG. 2 (Exemplary operation shown) until the WTRU detects an indication that one or more LBT subbands have been acquired on at least one LBT subband (e.g., LBT subband 1). In the example (e.g., as... FIG. 3 As shown), the WTRU can switch or change monitoring based on indications of monitoring some or all LBT subbands (e.g., using micro-slot-based monitoring) until further notification (e.g., until a full COT structure indication is detected). This can be done, for example, at the beginning of the next time slot (e.g., as shown). FIG. 2 The WTRU is informed of the received instruction (e.g., a complete COT structure instruction) as shown in the example. The instruction may, for example, indicate the acquisition / activation of LBT subbands 1 and 3 for the COT. The WTRU may accordingly modify its PDCCH monitoring activity (e.g., based on the instruction) (e.g., from micro-slot-based monitoring of subbands 1-4 to slot-based monitoring of active subbands 1 and 3, as shown in the example). FIG. 3One or more indications of acquired COT subbands and adaptive subband monitoring based on the indications can support efficient use of acquired / active subbands during COT (as shown in examples in FIG. 6).

[0118] A WTRU can be configured to perform hierarchical monitoring, e.g., for indications associated with COT. A WTRU can monitor a subset of LBT subbands, e.g., without an active COT. A WTRU can modify a set of monitored LBT subbands. For example, at (e.g., each) monitoring instance, a WTRU can (e.g., reevaluate or make a determination whether to) adapt (e.g., maintain or modify / change) a set of monitored LBT subbands. A selection of monitored LBT subbands (e.g., at an instance) can be determined, e.g., based on one or more of: a set of active LBT subbands in a previous COT; a previously monitored set of LBT subbands; a preconfigured monitoring pattern; an indication received in a discovery reference signal (DRS); a result of an LBT procedure or measurement; an indication received in a previous COT; an indication received outside of a COT; and / or the like.

[0119] A selection of monitored LBT subbands at an instance can be determined (e.g., at least in part) based on a set of active LBT subbands in a previous COT, e.g. A WTRU can be aware of a previous COT that occupied a first set of LBT subbands. A WTRU can monitor at least one CORESET / search space / PDCCH candidate from at least one of the previously used LBT subbands. A previously used set of LBT subbands can be valid for a certain time. For example, a validity of a previously used set of LBT subbands can depend on a time elapsed since a COT expiration. A WTRU can maintain a timer for one or more LBT subbands. For example, upon expiration of a timer, a WTRU can remove an LBT subband from a list of monitored LBT subbands. For example, upon expiration of a timer, a WTRU can return to a default set of LBT subbands.

[0120] A selection of monitored LBT subbands at an instance can be determined (e.g., at least in part) based on a previously monitored set of LBT subbands. A WTRU can monitor a first set of LBT subbands in a first time instance. A WTRU can determine a second set of LBT subbands in a second time instance (e.g., after the first time instance), e.g., from one or more of the first set of LBT subbands; whether the WTRU detected a transmission in any of the LBT subbands monitored in the first time instance; one or more LBT subbands (e.g., a set of LBT subbands) in which the WTRU detected a transmission; and / or the like.

[0121] A selection of monitored LBT subbands at an instance can be determined (e.g., at least in part) based on a preconfigured monitoring pattern. In an example, a pattern can be semi-statically configured by a network.

[0122] The selection of monitored LBT subbands at an instance can be determined (e.g., at least in part) based on, for example, a result of an LBT procedure and / or a measurement. In an example, the LBT procedure and / or measurement can be performed by the WTRU.

[0123] The selection of monitored LBT subbands at an instance can be determined (e.g., at least in part) based on, for example, an indication received outside of a COT. In an example, the indication can be received after completion of a most recent COT.

[0124] A WTRU can be configured to perform wideband monitoring, for example, for an indication associated with a COT. A WTRU can be configured to monitor for a wideband transmission. A WTRU can be configured to monitor for a wideband transmission for an indication of a COT acquired by a gNB. For example, a WTRU can monitor for a wideband DM-RS and / or GC-PDCCH that can be transmitted on multiple LBT subbands. For example, if a wideband transmission exists in at least one LBT subband, a WTRU can determine that an active COT exists in the at least one LBT subband. For example, a WTRU can detect the presence of a component of a wideband DM-RS. A WTRU can determine (e.g., be capable of determining) a set of LBT subbands, for example, in which a wideband DM-RS has been transmitted. A WTRU can (e.g., be configured to) consider a subband in which a wideband DM-RS (or GC-PDCCH) has been received as part of a COT. In an example, a WTRU can consider (e.g., any) subband in which a wideband DM-RS (e.g., and / or GC-PDCCH) has been received as part of an acquired COT (e.g., a newly acquired COT).

[0125] A WTRU can (e.g., be configured to) perform monitoring based on, for example, a multi-step (e.g., two-step) indication of a set of LBT subbands. A WTRU can monitor one or more LBT subbands to determine the use of at least one LBT subband of a COT, for example, using one or more methods described herein. A WTRU can modify its CORESET, search space, and / or PDCCH candidate monitoring, for example, based on determining that at least one LBT subband has been acquired for a COT. A WTRU can modify its CORESET, search space, and / or PDCCH candidate monitoring, for example, in a manner that determines a full set of active LBT subbands upon determining that at least one LBT subband has been acquired for a COT. For example, a WTRU can receive a first indication that at least one LBT subband has been acquired using a first monitoring mode on one or more LBT subbands. A WTRU can use a second monitoring mode (e.g., to receive a second indication) on one or more LBT subbands (e.g., upon receiving the first indication). The second indication can indicate or provide more information to the WTRU about the full set of active LBT subbands.

[0126] In an example, a second monitoring pattern can be determined in accordance with one or more LBT subbands in which the WTRU receives a first indication. For example, a WTRU (e.g., that has received an indication in a first LBT subband) can adapt the WTRU’s monitoring pattern in a manner that enables the WTRU to have a greater probability of receiving a full COT structure indication (e.g., in the first detected LBT subband).

[0127] A WTRU can receive and / or interpret scheduling information. A WTRU can (e.g., be configured to) determine scheduling information, for example, based on one or more LBT subbands that can be associated with an active COT. A WTRU can know the LBT subbands that are active at least at the beginning of a COT. For example, a WTRU can expect (e.g., only) to be scheduled in LBT subbands in which the WTRU has received an indication of COT activity until a (e.g., further) indication of a full set of active LBT subbands. For example, a WTRU can interpret a scheduling grant to point to resources on the LBT subband in which the WTRU received the grant, at least until a further indication of a full set of active LBT subbands. In an example, a WTRU can detect a DM-RS and / or GC-PDCCH indicating first LBT subband activity. For example, a WTRU can expect any (e.g., zero or more) scheduling grants to be related (e.g., only) to the indicated first active LBT subband until the WTRU receives an indication of a full set of active LBT subbands. Scheduling grants that occur before an indication of a full set of active LBT subbands can include less resource allocation information. An LBT subband can be considered known (e.g., implicitly) based on the first active LBT subband indication, for example. The number of bits used for resource allocation can be reduced. A smaller downlink control information (DCI) payload can be implemented, for example, for transmissions that occur at the beginning of a COT.

[0128] A WTRU’s interpretation of resource allocation in a scheduling grant can be a function of the number and / or set of acquired LBT subbands. The number and / or set of acquired LBT subbands can be different at the beginning of a COT compared to after receiving a COT structure indication (or COT structure indication update).

[0129] A WTRU can be configured to receive an indication associated with PDCCH monitoring. For example, a WTRU can be configured to receive an explicit indication to modify PDCCH monitoring. A WTRU can receive an indication to change its CORESET, search space, and / or PDCCH monitoring pattern. A WTRU can be configured with multiple monitoring patterns and / or can be instructed to change the monitoring patterns. A WTRU can receive an indication (e.g., dynamic or semi-static) to change one or more monitoring patterns (e.g., configuration of the one or more monitoring patterns). Each monitoring pattern can have an index. An (e.g., explicit) indication to change a monitoring pattern can include an index of the (e.g., new or alternative) monitoring pattern to change to.

[0130] A WTRU can receive an indication to change to a second PDCCH monitoring pattern, for example, via a transmission received using a first PDCCH monitoring pattern. For example, a WTRU can receive a DCI in a PDCCH candidate monitored as part of a first PDCCH monitoring pattern. The DCI can indicate, for example, a change in monitoring for the WTRU, from the first PDCCH monitoring pattern to a second PDCCH monitoring pattern. The WTRU can change monitoring based on the indication.

[0131] A new / alternative / changed PDCCH (e.g., second PDCCH) monitoring pattern can change one or more of the following: a set of CORESETs actively monitored, a set of search spaces actively monitored, a set of LBT subbands actively monitored, a set of PDCCH candidates actively monitored, etc.

[0132] An (e.g., explicit) indication to use a PDCCH monitoring pattern can include or can be associated with a duration in which the PDCCH monitoring pattern is valid. For example, a WTRU can be in an active COT with a fixed duration. The WTRU can (e.g., be configured to) assume that an indication to switch to a different PDCCH monitoring pattern, for example, is valid until the end of the active COT. For example, the WTRU can assume that any indication to switch to a different PDCCH monitoring pattern is valid until the end of the current COT. An (e.g., explicit) indication to use a PDCCH monitoring pattern can be associated with a validity timer. For example, upon expiration of the validity timer, the WTRU can (e.g., without another indication) return to a default PDCCH monitoring pattern. The default PDCCH monitoring pattern can be, for example, a non-COT monitoring pattern or (e.g., first) monitoring pattern determined or indicated (e.g., based on a first detected LBT subband) at the start of a COT. An (e.g., explicit) indication to use and / or modify a PDCCH monitoring pattern can be received, for example, on one or more of a WTRU-specific, cell-specific, or group-common PDCCH.

[0133] A WTRU can be configured with multiple CORESETs. A WTRU can be configured to monitor some or all of the multiple CORESETs. For example, a WTRU can maintain a separate list of configured and / or active CORESETs to reduce blind detection and / or channel estimation complexity in monitoring multiple (e.g., a relatively large number of) CORESETs. A WTRU can attempt (e.g., at a given time instance) blind detection of PDCCH candidates on a subset of CORESETs. For example, a WTRU can be configured with a set of x CORESETs. A WTRU can attempt (e.g., at any given time instance) blind detection of (e.g., only) PDCCH candidates on a subset of CORESETs (e.g., y CORESETs, where y can be less than or equal to x). The subset of CORESETs can be considered as active CORESETs.

[0134] A WTRU can be configured with a maximum of y (e.g., 3) CORESETs. A WTRU can determine a number and / or a set of CORESETs that the WTRU can monitor, e.g., based on a maximum of y (e.g., y_max). A WTRU can determine a number and / or a set of CORESETs that the WTRU can monitor according to one or more of: a set of configured CORESETs, a set of available CORESETs, a priority of (e.g., each) CORESET, y_max, etc. Configured CORESETs can include, e.g., x semi-statically configured CORESETs. Available CORESETs can include, e.g., CORESETs located in active LBT sub-bands. A priority of a CORESET can be determined, e.g., according to a CORESET index. A maximum of y (e.g., y_max) can be indicated by a network (e.g., in an explicit indication).

[0135] In an example, a WTRU can receive a first indication at the beginning of a COT indicating a subset of LBT sub-bands that are active. A WTRU can determine a first set of active CORESETs, e.g., according to the active LBT sub-bands. A WTRU can receive an update on the set of active LBT sub-bands. The update can, e.g., increase the number of active LBT sub-bands. A WTRU can modify its set of active CORESETs, e.g., based on the updated set of LBT sub-bands. In an example, a WTRU can receive an (e.g., explicit) indication to change one or more PDCCH monitoring modes, which can affect the set of y active CORESETs.

[0136] A WTRU can be configured to determine a channel access priority. A channel access priority can be indicated by a channel access category (CAC). A gNB can control category 2 (CAT2) UL transmissions (e.g., LBT without random backoff). A gNB can control CAT2 UL transmissions, e.g., if they fall into a gNB COT (e.g., including a CG) and / or when they fall into a gNB COT.

[0137] A WTRU can be (pre)configured with a set of CACs for uplink transmissions. One or more CACs can be used to determine logical channel restrictions. For example, a WTRU can be preconfigured with CAC 2 and CAC 4. A WTRU can determine an applicable CAC for uplink transmissions in multiple steps (e.g., in two steps). A WTRU can receive an indication from a gNB (e.g., in a first step). A WTRU can determine a CAC based on the received indication and / or other conditions (e.g., in a second step). For example, a gNB can indicate (e.g., transmit) a COT of the gNB to WTRUs in a cell. For example, a CAC can be selected based on a previous transmission status of a WTRU. The previous transmission status can include, for example, no acknowledgement (ACK) or no negative acknowledgement (NACK) indication received. A gNB can provide an indication to a WTRU. A WTRU can determine a CAC based on the indication and / or one or more conditions.

[0138] A WTRU can receive an indication from a network node (e.g., a gNB). In an example, a WTRU can be configured to receive an indication from a gNB that the WTRU can use, for example, to determine a CAC. A WTRU can determine a channel access priority, for example, using a CAC. An indication can include one or more of (e.g., in combination with) the following or can be transmitted / received, for example, via: a WTRU-specific DCI; a group common (GC) DCI; a COT indication; a reference signal (RS); and / or the like.

[0139] An indication (e.g., from a gNB) can be received, for example, via a DCI (e.g., a WTRU-specific DCI). For example, a WTRU can receive a DCI that activates an uplink configured as a grant Type 2. A WTRU can receive a DCI that requests CSI feedback. A WTRU-specific DCI can schedule a downlink data transmission. A WTRU can use an indication received via a DCI to determine a CAP associated with a COT.

[0140] An indication (e.g., from a gNB) can be received, for example, via a group common DCI. A group common DCI can include one or more of a downlink feedback indication, a slot format indication, a pre-emption indication, and / or the like. A WTRU can use an indication received via a DCI to determine a CAP associated with a COT.

[0141] An indication (e.g., from a gNB) can include, for example, a COT indication. A COT indication can include a COT structure and / or an LBT sub-band / carrier for downlink transmissions. A COT structure can include, for example, DL symbols, variable symbols, UL symbols, and / or the like. A WTRU can use a COT indication (e.g., a COT structure indication) to determine a CAP associated with a COT.

[0142] For example, an indication (e.g., from a gNB) can be received via one or more reference signals (e.g., DM-RS and / or CSI-RS). A reference signal configuration can be used to determine a CAP associated with a COT. For example, a gNB can configure a WTRU with multiple reference signals. Each (e.g., of the multiple) configuration (e.g., of the multiple configurations) can be associated with a CAC. In an example, a first (e.g., RS) configuration can be associated with a first CAP (e.g., associated with LBT cat2), and a second (e.g., RS) configuration can be associated with a second CAP (e.g., associated with LBT cat4). A WTRU can determine a CAC, for example, based on a reference signal (e.g., upon detecting a reference signal). A WTRU can determine a first channel access priority based on a first reference signal configuration, and a second channel access priority based on a second reference signal configuration different from the first reference signal configuration.

[0143] A WTRU can change (e.g., reduce) a set of allowed CACs to consider (e.g., during a next step), for example, based on a gNB indication (e.g., as a triggering event operation). For example, a WTRU can be preconfigured with four CACs: CAC 1, 2, 3, and 4. A gNB indication can trigger a WTRU to reduce the four CACs to two CACs (e.g., CAC 2 and 4) to consider during a next step. A WTRU can select applicable CACs during a second step, for example, based on a gNB indication (e.g., provided / received as described herein).

[0144] A WTRU can determine a CAC, for example, based (e.g., at least in part) on an indication from a network node (e.g., gNB). A WTRU can be configured to determine a CAC, for example, based (e.g., at least in part) on one or more conditions. A WTRU (e.g., having received a gNB indication, such as in a form described herein) can be configured to determine a CAC based on one or more (e.g., in combination) of one or more conditions including, for example, one or more of: a start time of an uplink transmission; a transmission duration of an uplink grant; whether a transport block (TB) to be transmitted is a retransmission; a number of retransmissions / repetitions already performed; a CAC of a previous use of a resource; a number of failed channel access attempts; whether a previous uplink transmission opportunity was pre-empted; and / or the like.

[0145] A WTRU can be configured to determine a CAC, for example, based on a start time of an uplink transmission. In an example, the start time of the uplink transmission can be based on a start time of the uplink transmission relative to an end of a DL burst. For example, a WTRU can be configured with a configured grant Type 2 in the second symbol of slot n. The WTRU can receive (e.g., during a first step) a COT indication (e.g., from a network node) indicating that a DL burst starts in slot n-4 and ends in slot n-1. The WTRU can determine that a gap between the DL burst and the start time is less than X symbols. For example, if the offset X is between X1 and X2, the WTRU can use a first CAC (e.g., CAC 1). For example, if the offset X is between X2 and X3, the WTRU can use a second CAC (e.g., CAC 2).

[0146] In an example, the start time of the uplink transmission can be based on a start time of the uplink transmission relative to a reception time of a group common DCI and / or a WTRU-specific DCI. A WTRU can determine a CAC, for example, based on an offset X between an end symbol of a PDCCH carrying the DCI to a start of the uplink transmission. For example, if the offset X is between X1 and X2, the WTRU can use a first CAC (e.g., CAC 1). For example, if the offset X is between X2 and X3, the WTRU can use a second CAC (e.g., CAC 2).

[0147] In an example, the start time of the uplink transmission can be based on a start time of the uplink transmission relative to a reception time of a reference signal (e.g., DM-RS and / or CSI-RS).

[0148] A WTRU can be configured to determine a CAC, for example, based on a transmission duration of an uplink grant. A WTRU can determine a CAC, for example, based on a time domain resource allocation for an uplink transmission.

[0149] In an example, the time domain resource allocation for the uplink transmission can be X symbols in a duration. For example, if X is between X1 and X2, the WTRU can use a first CAC (e.g., CAC 1). For example, if X is between X2 and X3, the WTRU can use a second CAC (e.g., CAC 2).

[0150] A CAC determination can be (e.g., alternatively) based on a comparison of a time domain resource allocation with X symbols and a duration of a DL burst with Y symbols. For example, if X < aY, where a can be configured (e.g., by a WTRU in an indication to the WTRU as a fixed value, etc.), the WTRU can use a second CAC (e.g., CAC 2).

[0151] The CAC can determine that (e.g., alternatively) based on a comparison of the time domain resource allocation with X symbols to the duration of the DL burst plus the time gap between the end of the DL burst to the start of the uplink transmission. For example, the duration of the DL burst can include Y symbols. The time gap between the end of the DL burst and the start of the uplink transmission can include Z symbols. For example, if X < a (Y + Z), where a can be configured (e.g., by the WTRU as a fixed value in an indication to the WTRU, etc.), the WTRU can use a second CAC (CAC 2).

[0152] The WTRU can be configured to determine the CAC, for example, based on whether the TB to be transmitted is a retransmission or a first / different transmission. For example, the WTRU can use CAC 2 for retransmissions and CAC 4 for first / different transmissions, and vice versa.

[0153] The WTRU can be configured to determine the CAC, for example, based on the number of retransmissions / repetitions that have been performed. The WTRU can determine the CAC (e.g., for an ongoing transmission of a TB), for example, based on the number of retransmissions / repetitions that have been performed (e.g., of the TB). For example, if the number of retransmissions performed is below a configured threshold, the WTRU can use a first CAC (e.g., CAC 4). For example, if the number of retransmissions performed is not below the configured threshold, the WTRU can use a second CAC (e.g., CAC 2).

[0154] The WTRU can be configured to determine the CAC, for example, based on a previous CAC used for (e.g., same) resources (e.g., configured grant resources). In an example, for example, if the WTRU used CAC 4 during a previous gNB shared COT, the WTRU can use CAC 2 within a current gNB shared COT. In an example, the WTRU can use CAC 2 in a current gNB shared COT, for example, based on a number of consecutive uses of CAC 4 in a previous gNB shared COT.

[0155] The WTRU can be configured to determine the CAC, for example, based on a number of failed channel accesses. The WTRU can be configured to determine the CAC, for example, based on a number of failed channel accesses due to LBT failures on (e.g., same) resources. The same resources can include configured grant resources.

[0156] The WTRU can be configured to determine the CAC, for example, based on whether a previous uplink transmission opportunity was pre-empted. For example, the WTRU can be configured with an uplink configured grant within a first gNB shared COT. The WTRU can receive an uplink pre-emption indication. The WTRU can cancel the uplink transmission. The WTRU can use the configured grant resources for transmission, for example, using CAC 2 during a next shared gNB COT.

[0157] The determined and / or indicated CAC can be used to determine logical channel restrictions, e.g., by indicating channel access priority.

[0158] For example, the WTRU can be configured to use a default CAC, e.g., if conditions are not met (e.g., as described herein) and / or if a gNB indication is not received.

[0159] The WTRU can be configured to receive an LBT type / priority indication. The WTRU and / or network (e.g., network node) can be configured to use signaling support for LBT type / priority indication. The priority indication can indicate channel access priority. The channel access priority can be indicated by CAPC.

[0160] The WTRU can be configured to send an indication of channel access priority (e.g., CAPC) used to acquire COT. COT can be acquired, e.g., if COT is initiated on a resource (e.g., channel) that can have been determined to be idle. COT can be acquired, e.g., according to a result of LBT. The WTRU can indicate to the network the CAPC used with the LBT procedure, e.g., based on COT acquisition (e.g., at acquisition) for uplink transmission. The WTRU can indicate one or more logical channels for which the CAPC can be used to determine channel acquisition. The indication of (e.g., logical channel) can be more robust than the transmitted data, e.g., to support (e.g., immediate) immediate use of the information by the network.

[0161] The WTRU can (e.g., be configured to) explicitly or implicitly indicate CAPC for LBT. The (e.g., explicit) indication by the WTRU can include one or more of the following: addition to transmitted uplink control information (UCI); addition to a bit string of data; and / or the like. The (e.g., explicit) indication by the WTRU can include addition to transmitted UCI. The WTRU can indicate CAPC as part of UCI. The UCI for CAPC can be mapped to resources close to DM-RS. Decoding error performance can be improved. The UCI for CAPC can include a cyclic redundancy check (CRC). Robustness can be improved. The UCI for CAPC can be transmitted by the WTRU in a predetermined resource (e.g., symbol of a slot). For example, the first symbol of UL transmission can include UCI for CAPC, which can provide more time for the gNB to determine CAPC in preparation for upcoming scheduling opportunities.

[0162] The (e.g., explicit) indication by the WTRU can include addition to a bit string of data. The WTRU can append or preset the bit string to a TB code block. The bit string can indicate CAPC used for channel acquisition. The bit string can be encoded and / or the bit string can include a CRC, which can improve robustness.

[0163] The (e.g., implicit) indication by the WTRU of the CAPC for channel acquisition can include one or more of the following: an interlace for transmission; a parameter of a DM-RS; a parameter of a transmission; and / or the like.

[0164] The (e.g., implicit) indication by the WTRU of the CAPC can include a resource (e.g., interlace) for transmission. The WTRU can select the transmission resource, for example, based on the CAPC for accessing the channel.

[0165] The (e.g., implicit) indication by the WTRU of the CAPC can include a parameter of a DM-RS. The parameter of the DM-RS can be selected, for example, based on the CAPC for accessing the channel. The parameter can include one or more of, for example, a sequence or a resource mapping.

[0166] The (e.g., implicit) indication by the WTRU of the CAPC can include a parameter of a transmission. A duration of the transmission can indicate the CAPC for accessing the channel. For example, a duration of a first transmission can be selected according to the CAPC for accessing the channel. An antenna port for the first transmission can indicate or convey the CAPC for channel acquisition. The WTRU can be scheduled with a numerology. The WTRU can select from the numerologies, for example, according to the CAPC for channel acquisition. The numerologies can include, for example, a set of TB or modulation and coding scheme (MCS) values.

[0167] FIG. 4 An example is shown indicating a channel access priority (e.g., CAPC) that can be used to acquire a shared COT. As shown in the example of FIG. 4 As shown in the example of FIG. 6, the WTRU can select a CAPC, for example, based on data transmitted by the WTRU in the UL. The WTRU can acquire an unlicensed channel using LBT CAT4 with the appropriate CAPC, for example. The WTRU can indicate the CAPC used to the network. The network can (e.g., effectively) share the COT with the WTRU.

[0168] Implementations and / or features herein can be described in terms of behavior (e.g., actions) of a WTRU. In examples, the behavior can be performed by an entity such as a NW node or other device that can not include WTRU functionality. In some examples (e.g., certain use cases or certain time instances), the entity or other device can behave like a WTRU. One or more examples herein can be equally applicable to the entity or other device.

[0169] A WTRU can be configured with or configured to determine a logical channel restriction. The WTRU can be scheduled with a UL transmission within a COT (e.g., an ongoing COT). The WTRU can be indicated (e.g., can receive an instruction or indication for a logical channel restriction), e.g., a logical channel restriction in a scheduling DCI. The scheduling DCI can comprise a grant or an allocation. The WTRU can determine a logical channel restriction, e.g., based on the received instruction or indication. The WTRU can receive an indication in the DCI and use the indication to determine a CAP associated with the COT. The WTRU can determine logical channels for which data can be included in an uplink transmission within the COT, e.g., based on the restriction (e.g., the logical channel restriction). The restriction can be based on a priority level (e.g., a CAP) and / or can indicate logical channels. In some examples, an indication of a priority level can be equal to an indication of a logical channel (e.g., which can be associated with the priority level). A logical channel can be associated with a priority level (e.g., a logical channel priority associated with the logical channel). As FIG. 5 shown, the WTRU can select appropriate priority data to construct a TB for transmission. To select appropriate priority data to construct a TB for transmission (e.g., as FIG. 5 shown), the WTRU can determine a logical channel priority (e.g., a LCH priority), and the WTRU can determine whether a logical channel is associated with a channel access priority that is equal to or higher than a channel access priority associated with a COT based on the LCH priority associated with the logical channel and the channel access priority associated with the COT. As FIG. 5 shown, appropriate priority data can be selected. For example, if a logical channel is associated with a channel access priority that is equal to or higher than a channel access priority associated with a COT, the logical channel can be allowed to be included in a transmission by the WTRU during the COT.

[0170] The determination of the priority can indicate which logical channels are to be included in a transmission by the WTRU. The WTRU can include data from logical channels that have a same priority as the priority level and / or a higher priority and / or logical channels indicated in the restriction (e.g., associated with the priority level). The same priority can comprise a priority level that is equal to the priority level indicated in the restriction. As FIG. 6 shown, the WTRU can use the determined logical channel restriction to determine whether a logical channel is allowed to be included in a scheduled transmission. For example, the restriction can indicate a priority level (e.g., a CAP), and the WTRU can include data (e.g., in a UL transmission) from logical channels that are associated with a same and / or higher priority as the indicated priority level (e.g., only from logical channels that are associated with a same and / or higher priority as the indicated priority level). As FIG. 6As shown, the transmission can include the logical channel if the determined logical channel restrictions allow the logical channel to be included in the transmission.

[0171] The WTRU can monitor for presence of a signal indicating a channel access priority (e.g., CAPC) for acquiring a COT. For example, the channel access priority can indicate a priority used by the WTRU or base station to acquire a COT to access a channel. A higher CAPC number / value can indicate a lower priority (e.g., for acquiring a COT). In an example (e.g., for grant-free or configured grant UL transmissions occurring within an active COT), the WTRU can monitor for presence of a signal indicating a CAPC for acquiring a COT (e.g., prior to transmission of the signal). As FIG. 6 As shown, the WTRU can determine logical channel restrictions based on an indication received from a gNB including a CAPC associated with a COT. The WTRU can determine the CAPC, for example, based on (e.g., by receiving) a COT structure indication. The COT structure indication can be received via a DCI (e.g., a DCI for a COT structure indication). In some examples, the DCI can be different from a scheduling DCI. The WTRU can determine the CAPC, for example, based on (e.g., by receiving) a signal triggering a CG transmission, for example, alternatively and / or additionally. The WTRU can determine the CAPC, for example, alternatively and / or additionally, as part of a parameter of a gNB transmission (e.g., DM-RS or GC-PDCCH) within a COT.

[0172] FIG. 5 Examples of determining logical channel restrictions based on a priority (e.g., channel access priority) associated with a COT are shown, for example, as in the examples of FIG. 6 FIG. 5 As shown, an indication of a priority (e.g., CAPC) can be received and / or used to select content for transmission in a shared COT. The WTRU can receive an indication of a CAPC used by the network to acquire / start a COT. The WTRU can receive the indication of the CAPC, for example, in a scheduling grant for an UL transmission. The scheduling grant can schedule resources for a transmission sent during a COT. The resources can occur during the COT. The scheduling grant can include the CAPC used by the network if / and / or when a COT is acquired (e.g., an ongoing COT). The WTRU can determine a priority associated with the COT. The WTRU can determine data that the WTRU can transmit during the COT (e.g., determine data with an applicable / sufficient priority and / or in compliance with restrictions) based on the priority (e.g., allowed priority) included in the scheduling grant. The WTRU can determine a set of restricted logical channels that the WTRU can use to construct a TB for the scheduled transmission (e.g., as shown in the examples of FIG. 6 FIG. 6 ​​As shown, for example, if logical channel constraints allow logical channels to be included in a transmission, a TB can be constructed to include data of appropriate priority (e.g., data associated with logical channels) by multiplexing logical channels associated with data on the TB. In the example, the set of logical channels used by the WTRU for transmission can be restricted. The WTRU can select data from logical channels (e.g., any logical channel) within the set of logical channels (e.g., a restricted set).

[0173] In the example, the WTRU can determine whether to transmit data associated with a priority lower than that allowed according to logical channel limitations. The WTRU can, for example, abort a Type 1 or Type 2 LBT procedure (e.g., a procedure that can be used for COT sharing) and / or execute a Type 4 LBT procedure with acceptable CAPC transmission requirements. The WTRU can be configured to switch from a Type 1 or Type 2 LBT procedure to a Type 4 LBT procedure.

[0174] FIG. 6 An example of a shared COT based on a CAP (e.g., CAPC) associated with the COT is shown. ​ As shown, the WTRU can receive and use network indications of a shared COT and associated CAP (e.g., CAPC) to transmit in shared COT data from a logical channel consistent with the CAP (e.g., CAPC). The WTRU can receive (e.g., from the network) indications regarding (e.g., network-acquired) the COT. The indications can indicate information associated with the COT, such as one or more of the following: start time, duration, acquiring node (e.g., gNB), priority (e.g., CAP or CAPC), scheduling, etc. UL resources can be used to schedule the WTRU within the COT.

[0175] The WTRU can prepare for a transmission (e.g., a TB) in a COT. The WTRU can determine the CAP (e.g., CAPC) associated with the COT acquired by the network (e.g., as described herein). The WTRU can determine, based on the CAP associated with the COT, whether there are any restrictions on logical channels that can be used in a scheduled transmission within the COT (e.g., as described herein). The WTRU can use the determined logical channel restrictions to determine whether a logical channel is permitted to be included in a scheduled transmission (e.g., as described herein). If the determined logical channel restrictions allow the logical channel to be included in the transmission, the transmission may include the logical channel. The WTRU can construct and transmit the TB based on the foregoing determination. In the example (e.g., as...), ​As shown, the WTRU can use data from the LCH set where the associated CAPC has equal or higher priority (e.g., CAPC 2, CAPC 1) than the CAPC used by the gNB (e.g., CAPC 2). The WTRU can transmit a transmission during the COT (e.g., via a sub-band). The WTRU can indicate a behavior. In an example, the WTRU can indicate a behavior including use of Type 4 LBT, for example, when using a Type 4 LBT procedure to acquire the channel within an active COT. The WTRU can indicate Type 4 LBT and / or use of a different CAPC, for example, using a method similar to the methods described herein to indicate the CAPC for the COT acquired by the WTRU. Use of Type 4 LBT can reinitiate the COT and / or can affect the COT duration. The WTRU can monitor, for example, a COT structure indication to determine an updated COT duration.

[0176] While features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein can be implemented in a computer program, software, or firmware incorporated in a computer- readable medium for execution by a computer or processor. Examples of computer- readable media include electronic signals (optical, electrical or electromagnetic) that are transmittable through a wired or wireless communication means. Examples of computer-readable media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, for example, a hard disk, a floppy disk, or a magnetic strip, magneto-optical media such as, for example, a floptical disk, and optical media such as, for example, a compact disc (CD) or a digital versatile disc (DVD). A processor in association with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), comprising: a processor configured to: receive a channel occupancy time (COT) structure indication; determine a channel access priority associated with a COT based on the COT structure indication, wherein the COT structure indication is to indicate one or more sub-bands that have been acquired and the channel access priority is associated with a base station’s COT acquisition; determine a logical channel restriction based on the channel access priority associated with the COT; determine whether data associated with a logical channel is allowed to be included in a transmission based on the logical channel restriction, wherein the transmission is to be transmitted during the COT; and transmit the transmission via a sub-band of the one or more sub-bands during the COT, wherein the transmission includes the data associated with the logical channel if the logical channel restriction allows the data associated with the logical channel to be included in the transmission.

2. The WTRU of claim 1, wherein the logical channel restriction is applied by including the data associated with the logical channel if the logical channel is associated with a channel access priority that is equal to or higher than the channel access priority associated with the COT or not including the data associated with the logical channel if the logical channel is associated with a channel access priority that is lower than the channel access priority associated with the COT.

3. The WTRU of claim 1, wherein the channel access priority is a channel access priority for acquiring the sub-band via which the transmission is transmitted.

4. The WTRU of claim 1, wherein the channel access priority associated with the COT is indicated by a channel access priority class (CAPC).

5. The WTRU of claim 1, wherein the logical channel is multiplexed on a transport block (TB) if the logical channel is associated with a channel access priority that is equal to or higher than the channel access priority associated with the COT, wherein the TB is included in the transmission.

6. The WTRU of claim 1, wherein the COT structure indication is received in downlink control information (DCI), wherein the one or more sub-bands are acquired for the COT.

7. The WTRU of claim 6, wherein the one or more sub-bands are associated with a listen before talk (LBT) operation.

8. A method comprising: receiving a channel occupancy time (COT) structure indication; determining a channel access priority associated with a COT based on the COT structure indication, wherein the COT structure indication is to indicate one or more sub-bands that have been acquired and the channel access priority is associated with a base station’s COT acquisition; determining a logical channel restriction based on the channel access priority associated with the COT; determine, based on the logical channel restriction, whether data associated with a logical channel is allowed to be included in a transmission that is to be transmitted during the COT; and transmit, during the COT, the transmission via a sub-band of the one or more sub-bands, wherein the transmission includes the data associated with the logical channel if the logical channel restriction allows the data associated with the logical channel to be included in the transmission.

9. The method of claim 8, wherein the logical channel restriction is applied by including the data associated with the logical channel if the logical channel is associated with a channel access priority that is equal to or higher than the channel access priority associated with the COT, or not including the data associated with the logical channel if the logical channel is associated with a channel access priority that is lower than the channel access priority associated with the COT.

10. The method of claim 8, wherein the channel access priority is a channel access priority for acquiring the sub-band via which the transmission is transmitted.

11. The method of claim 8, wherein the logical channel is multiplexed on a transport block (TB) if the logical channel is associated with a channel access priority that is equal to or higher than the channel access priority associated with the COT, wherein the TB is included in the transmission.

12. The method of claim 8, wherein the COT structure indication is received via downlink control information (DCI), wherein the one or more sub-bands are acquired for the COT.

13. The method of claim 12, wherein the one or more sub-bands are associated with a listen-before-talk (LBT) operation.

14. The method of claim 8, wherein the channel access priority associated with the COT is indicated by a channel access priority class (CAPC).

Images