Shared channel occupancy time operation

Abstract

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

Description

Cross-references to related applications

[0001] This application is a divisional application of patent application No. 202080062022.4 entitled "Shared Channel Occupancy Time Operation", which is the Chinese national phase application of international application PCT / US2020 / 045778 filed on August 11, 2020. The international application claims the benefit of U.S. Provisional Application No. 62 / 886,170 filed on August 13, 2019, the contents of which are incorporated herein by reference. Background Technology

[0002] 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

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

[0004] 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.

[0005] 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.

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

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

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

[0009] 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.

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

[0011] The WTRU processor can be further configured with executable instructions to implement the method and further perform the following operations: receiving indications from the gNB via DCI. The channel access priority associated with the COT can be determined using the indications received via DCI.

[0012] 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 the method to further perform the following operations: determine a first channel access priority based on a first reference signal configuration; and determine a second channel access priority based on a second reference signal configuration different from the first reference signal configuration.

[0013] The WTRU processor can be further configured with executable instructions to implement the method to further perform the following operations: determine resources that occur during COT, wherein the transmit uses the resources to send.

[0014] The WTRU processor can be further configured with executable instructions to implement the method to further perform the following operations: determine the logical channel (LCH) priority associated with the logical channel; and determine 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 permitted to be included in the transmission by the WTRU during the COT period 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.

[0015] In the example, a method for sharing COT operations can be implemented. The method may be implemented (e.g., wholly or partially) by one or more devices, apparatuses, and / or systems (e.g., WTRUs, network nodes such as base stations including gNodeBs (gNBs)), which may include one or more processors configured to execute the method as computer-executable instructions that can be stored on a computer-readable medium or computer program product, which, when executed by the one or more processors, perform the method. The computer-readable medium or computer program product may include instructions that cause the one or more processors to perform the method by executing the instructions.

[0016] A Wireless Transmit / Receive Unit (WTRU) can monitor one or more LBT subbands to determine when COT is activated. The WTRU can be configured to monitor one or more (e.g., subsets) of contention-based subbands to determine if the channel is occupied. For example, the WTRU can (e.g., be configured to) monitor a set / subset of Listen-After-Speak (LBT) / unlicensed subbands to determine if the channel is occupied, which may indicate an association with COT activation. The WTRU can (e.g., be configured to) monitor one or more (e.g., some or all) LBT subbands, for example, in response to an indication associated with COT. In the example, the WTRU can be configured to monitor multiple (e.g., all) LBT subbands simultaneously.

[0017] The WTRU can receive indications of the COT structure for the channel. The WTRU can monitor one or more LBT subbands (e.g., a set of LBT subbands) within the COT based on whether the WTRU has detected, determined, or received an indication of a complete or partial COT structure. The WTRU can be configured to receive transmissions in an LBT subband that indicate the subband has been acquired. The WTRU can stop frequency hopping and / or can continue monitoring Physical Downlink Control Channel (PDCCH) candidates in the acquired LBT subbands. For example, the 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 monitoring PDCCH candidates in the acquired LBT subbands, for example, until it receives an indication of the complete set of acquired LBT subbands.

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

[0019] The WTRU can (e.g., be configured to) operate with a first (e.g., relatively large) group of configured control resource sets (CORESETs) and a second (e.g., smaller) group of active CORESETs. The WTRU can be configured to have multiple CORESETs. The WTRU can be configured to monitor (e.g., in various ways) some or all of the multiple CORESETs. The WTRU can receive a first indication at the start of the COT indicating, for example, a subset of the activity of an LBT subband.

[0020] The WTRU can determine the parameters for the LBT process used for a transmission within the COT based on the transmission priority. Priority can depend on previous transmissions or transmission type.

[0021] The WTRU can indicate the Channel Access Priority Class (CAPC) used to acquire a COT. The WTRU can monitor the presence of signals indicating the CAPC used to acquire a COT. The WTRU can receive indications of the CAPC used to initiate a COT. The WTRU can receive indications in the scheduling authorization of CAPCs used by the network (e.g., if acquiring an ongoing COT and / or when acquiring an ongoing COT). The WTRU can determine data with applicable / sufficient priority for transmission in the COT. The WTRU can determine a set of restricted logical channels that the WTRU can use to construct a Transport Block (TB) for scheduled transmissions in the COT.

[0022] The WTRU can be assigned logical channel restrictions for uplink (UL) transmissions within the COT. The WTRU can receive instructions with logical channel restrictions, such as those concerning scheduling downlink control information (DCI). The WTRU can determine the logical channels through which data can be included in uplink transmissions. For example, the WTRU can determine the logical channels through which data can be included in uplink transmissions based on these restrictions. Attached Figure Description

[0023] Figure 1A This is a system diagram illustrating an exemplary communication system that can be implemented in one or more of the disclosed embodiments.

[0024] Figure 1B It is shown in an implementation plan. Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used within the communication system shown.

[0025] Figure 1C It is shown in an implementation plan. Figure 1A The diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used within the communication system.

[0026] Figure 1DIt is shown in an implementation plan. Figure 1A The system diagram shown illustrates another exemplary RAN and another exemplary CN used within the communication system.

[0027] Figure 2 An example of a WTRU frequency hopping pattern used to monitor multiple LBT subbands is shown.

[0028] Figure 3 An example of a WTRU frequency hopping pattern used to monitor multiple LBT subbands is shown.

[0029] Figure 4 An example is shown for indicating the channel access priority (e.g., CAPC) that can be used to obtain a shared COT.

[0030] Figure 5 An example is shown of determining logical channel limits based on priorities associated with COT (e.g., as in...). Figure 6 (As shown in the example).

[0031] Figure 6 An example of a shared COT based on a CAP (e.g., CAPC) associated with the COT is shown. Detailed Implementation

[0032] Figure 1A This is a schematic diagram illustrating an exemplary communication system 100 that can be implemented in one or more of the disclosed embodiments. Communication system 100 can be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. Communication system 100 enables multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 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 Extended OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

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

[0034] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be base transceiver stations (BTS), Node Bs, evolved Node Bs, home Node Bs, home evolved Node Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

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

[0036] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via 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.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0037] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink (UL) Packet Access (HSUPA).

[0038] In one implementation, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which can use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0039] In one implementation, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as NR radio access, which can use New Radio (NR) to establish air interface 116.

[0040] In one implementation, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for instance, use a dual connectivity (DC) principle to implement both LTE and NR radio access together. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0041] In other implementations, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rate Evolution (EDGE), and GSM EDGE (GERAN).

[0042] Figure 1ABase station 114b can be, for example, a wireless router, a home node B, a home evolution node B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for use by drones), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0043] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although not explicitly stated... Figure 1A As shown, but it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113 which can utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA2000, WiMAX, E-UTRA or WiFi radio technology.

[0044] 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.

[0045] 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, Figure 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.

[0046] Figure 1B This is a system diagram illustrating an exemplary WTRU 102. (See diagram below.) Figure 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.

[0047] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0048] Transmitting / receiving element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 may be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 may be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0049] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. More specifically, WTRU 102 may employ MIMO technology. Therefore, in one embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0050] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As noted above, WTRU 102 may have multi-mode capability. Therefore, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via various RATs such as NR and IEEE 802.11.

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

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

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

[0054] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripheral device 138 may include an accelerometer, electronic compass, satellite transceiver, digital camera (for photos and / or video), Universal Serial Bus (USB) port, vibration device, television transceiver, hands-free headset, Bluetooth.® Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0055] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference through signal processing via hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous.

[0056] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to one embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0057] RAN 104 may include evolved Nodes B 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of evolved Nodes B while remaining consistent with the implementation scheme. Evolved Nodes B 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one implementation, evolved Nodes B 160a, 160b, and 160c may implement MIMO technology. Therefore, evolved Node B 160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

[0058] Each of the evolved nodes B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the UL and / or DL, etc. Figure 1C As shown, evolution nodes B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0059] Figure 1C The CN 106 shown may 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 is depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0060] The MME 162 can connect to each of the evolved nodes B 162a, 162b, and 162c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0061] The SGW 164 can connect to each of the evolved Nodes B 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 typically routes and forwards user data packets to and from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions such as anchoring the user plane during inter-evolved Node B handovers, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0062] SGW 164 can be connected to PGW 166, which provides WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0063] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and conventional landline communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) or be able to communicate with such an IP gateway, which serves as an interface between CN 106 and PSTN 108. Additionally, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0064] Despite WTRU in Figures 1A to 1D While described as a wireless terminal, it is conceivable that in some representative implementations, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0065] In a representative implementation, the other network 112 may be a WLAN.

[0066] A WLAN in Infrastructure Basic Services Set (BSS) mode may have an access point (AP) for the BSS and one or more sites (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic out of the BSS. Traffic originating outside the BSS and destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA and destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative implementations, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this document.

[0067] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a 20 MHz wide bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative implementations, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. For CSMA / CA, each STA (including the AP) can listen to the primary channel. If the primary channel is listened to / detected and / or determined to be busy by a particular STA, that STA can back off. A single STA (e.g., only one station) can transmit in a given BSS at any given time.

[0068] High-throughput (HT) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels to form a 40MHz wide channel.

[0069] Very High Throughput (VHT) STAs support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, data can be split into two streams by a segment parser. Each stream can be processed individually using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped to two 80MHz channels, and data can be transmitted via a transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration can be reversed, and the combined data can be sent to Media Access Control (MAC).

[0070] 802.11af and 802.11ah support operating modes below 1 GHz. Compared to those used in 802.11n and 802.11ac, 802.11af and 802.11ah reduce channel operating bandwidth and carrier. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative implementations, 802.11ah may support instrument-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support (e.g., only support) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain a very long battery life).

[0071] WLAN systems supporting multiple channels, and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as primary channels. A primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by STAs operating in the BSS (each supporting a minimum bandwidth operating mode). In the 802.11ah example, for STAs supporting (e.g., only supporting) a 1MHz mode (e.g., MTC type devices), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (supporting only the 1MHz operating mode) is transmitting to the AP, the entire available band can be considered busy even if most of the band remains idle and potentially available.

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

[0073] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to one implementation scheme. As noted above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0074] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the implementation. Each of gNBs 180a, 180b, and 180c may include one or more transceivers for communication with WTRUs 102a, 102b, and 102c via air interface 116. In one implementation, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one implementation, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In one implementation, gNBs 180a, 180b, and 180c may implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a may receive cooperative transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0075] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable parameter sets. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary depending on different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).

[0076] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., evolved Node Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can use one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate or connect to gNBs 180a, 180b, and 180c, and also communicate or connect to other RANs (such as eNode-B160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more evolved Node Bs 160a, 160b, and 160c. In a non-standalone configuration, evolved Node Bs 160a, 160b, and 160c can be used as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

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

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

[0079] AMF 182a and 182b can connect to one or more of gNBs 180a, 180b, and 180c via the N2 interface in RAN 113 and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the type of service used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services that rely on Ultra-Reliable Low Latency (URLLC) access, services that rely on Enhanced Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, etc. The AMF162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0080] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure traffic routing through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0081] UPF 184a and 184b can connect via the N3 interface to one or more of the gNBs 180a, 180b, and 180c in RAN 113. These gNBs can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

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

[0083] Given Figures 1A to 1D as well as Figures 1A to 1D The corresponding descriptions herein refer to one or more of the functions described below, which may be performed by one or more emulation devices (not shown): WTRU102a-d, base station 114a-b, evolved Node B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device described herein. An emulation device may be one or more devices configured to mimic one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0084] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, the one or more simulation devices may perform 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 to test other devices within the communication network. The one or more simulation devices may perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communication to perform tests.

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

[0086] Unlicensed operation may include operation in an unlicensed frequency band. Operation in an unlicensed frequency band may be based on transmit power control (TPC), radio frequency (RF) output power and / or power density (e.g., subject to limitations on that TPC, output power, and / or power density) that can be given (e.g., determined) by average equivalent isotropic radiated power (EIRP) and / or average EIRP density (e.g., at the highest power level). Operation in an unlicensed frequency band may also be based on out-of-band transmitter emissions (e.g., subject to requirements for out-of-band transmitter emissions). Requirements may be band-specific and / or geographically specific.

[0087] Operation (e.g., in an unlicensed frequency band) may (e.g., also) be based on the nominal channel bandwidth (NCB) and / or occupied channel bandwidth (OCB) available for the unlicensed spectrum (e.g., in the 5 GHz region) (e.g., subject to requirements for NCB and / or OCB). The NCB (e.g., the widest bandwidth including the guard band assigned to a single channel) may, for example, always be at least 5 MHz. The OCB (e.g., the bandwidth containing 99% of the signal's power) may, for example, be between 80% and 100% of the declared NCB. A device (e.g., during established communication) may (e.g., be permitted) operate (e.g., temporarily) in a mode where the device's OCB can be reduced to, for example, as low as 40% of the device's NCB (e.g., where the minimum is 4 MHz).

[0088] Channel access in unlicensed frequency bands can utilize Listen-Before-Speak (LBT). For example, LBT can be used regardless of whether the channel is occupied.

[0089] LBT can be characterized using one or more of the following (e.g., for frame-based systems): Idle Channel Assessment (CCA) time (e.g., approximately 20 µs), channel occupancy time (e.g., minimum 1 ms, maximum 10 ms), idle period (e.g., minimum 5% of channel occupancy time), fixed frame period (e.g., equal to channel occupancy time plus idle period), short control signaling transmission time (e.g., maximum duty cycle of 5% within a 50 ms observation period), and / or CAA energy detection threshold.

[0090] For example, in a load-based system, the transmit / receive configuration may not be fixed at a particular time. The LBT can be characterized, for example, using a number N corresponding to the number of idle time slots in the extended CCA (e.g., in a load-based system) (e.g., instead of characterizing the LBT with a fixed frame period). In some examples, N can be chosen randomly within a certain range.

[0091] Operating environments and / or characteristics can be categorized into various deployment scenarios, which may include, for example, different independent New Radio (NR) based operations, different variations of dual connectivity operations (e.g., E-UTRAN NR (EN) dual connectivity (DC) with at least one carrier operating according to LTE Radio Access Technology (RAT) or NR DC with at least two sets of one or more carriers operating according to NR RAT), and / or different variations of carrier aggregation (CA) (e.g., different combinations of zero or more carriers of LTE and NR RAT).

[0092] Operational (e.g., functional) features may include one or more of the following (e.g., to support Licensed Assisted Access (LAA)): Listen-before-Speak (LBT) for Clear Channel Assessment (CCA), discontinuous transmission on a carrier with a finite maximum transmit 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).

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

[0094] Discontinuous transmissions and / or limited maximum transmission durations on a carrier can be implemented, for example, to promote fair use. Channel availability may not be guaranteed, for example, in unlicensed spectrum. Continuous transmissions may be prohibited and / or limits may be imposed on the maximum duration of transmission bursts (e.g., to promote channel availability in unlicensed spectrum in certain geographic areas).

[0095] Carrier selection can be implemented, for example, to reduce interference. There may be a relatively large available bandwidth of unlicensed spectrum. Nodes can use carrier selection to choose carriers, for example, with low interference, which can support coexistence with other unlicensed spectrum deployments.

[0096] TPC can be implemented to adjust the transmit power. The transmitting device can reduce the transmit power by, for example, 3dB or 6dB compared to the maximum nominal transmit power.

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

[0098] For example, CSI measurements (e.g., including channel and interference) can be implemented to support frequency / time estimation and / or synchronization. WTRUs operating in unlicensed carriers can support frequency / time estimation and / or synchronization, for example, to support RRM measurements and (e.g., successful) reception of information on unlicensed bands.

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

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

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

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

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

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

[0105] Some COTs may be shared by multiple WTRUs, for example. For example, if a channel for UL transmission is acquired and / or when a channel for UL transmission is acquired, such as at a COT switching point, technologies and / or methods may be used to support fairness within the WTRU (e.g., COT distribution or usage). Technologies and / or methods may be used for authorized (CG) resources falling within the COT configuration (e.g., distribution or usage of CG resources).

[0106] Channel access priority can be used, for example, to acquire the COT. Channel access priority may include a Channel Access Priority Category (CAPC). Channel access priority may determine or indicate one or more parameters (LBT parameters) associated with the LBT. LBT parameters may be used (e.g., by a base station) to acquire a subband of the COT. The base station may include a gNodeB. In this example, the COT may not be used for information or data associated with a lower priority than that associated with the selection of the CAPC (e.g., for determining the selection of the CAPC). The gNB (e.g., without determination or indication) may not know the CAPC used to acquire the COT and may not know the allowed data priority for the COT (e.g., for a COT acquired by a WTRU). The transmitting WTRU (e.g., without determination or indication) may not know the priority of data that is allowed to be included for transmission within a COT acquired by another party (e.g., not acquired by a transmitting WTRU) (e.g., UL).

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

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

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

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

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

[0112] A WTRU may be configured with one or more LBT subbands (e.g., a subset of LBT subbands). A WTRU may be configured with one or more LBT subbands (e.g., a subset of LBT subbands) on which the WTRU may have one or more PDCCH monitoring opportunities (e.g., when no active COT exists). A WTRU may monitor one or more default LBT subbands (e.g., a default set of LBT subbands) (e.g., as described herein). A WTRU may (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.

[0113] A WTRU can be configured with resources in one or more (e.g., multiple) LBT subbands. A WTRU can be configured with, for example, one or more CORESETs, search spaces, and / or PDCCH candidates (e.g., a set of CORESETs, search spaces, and / or PDCCH candidates) in multiple LBT subbands. A WTRU can (e.g., in a given instance, such as in one or more time slots or time periods) actively monitor the CORESETs, search spaces, and / or PDCCH candidates in one or more LBT subbands (e.g., one or more LBT subbands are considered the default LBT subbands). For example, in any one or more time slots or time periods, a WTRU can actively monitor only the CORESETs, search spaces, and / or PDCCH candidates in the default LBT subband. The default LBT subband can be changed (e.g., over time). For example, a WTRU can be configured (e.g., and can use) with a frequency hopping pattern to change the default LBT subband (e.g., over time, such as periodically, irregularly, on a schedule, or as needed / self-organized). 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 timeslot number, time, WTRU identifier (ID), etc. The frequency hopping pattern can be (e.g., explicitly) indicated (e.g., via a bitmap in the configuration).

[0114] The WTRU can be configured to receive indications that a subband has been acquired (e.g., in a transmission within an LBT subband). The WTRU can stop frequency hopping and / or can continue monitoring PDCCH candidates in the acquired LBT subband. For example, the WTRU can stop frequency hopping and continue monitoring PDCCH candidates in the acquired LBT subband upon receiving an indication that a subband has been acquired in an LBT subband, e.g., until the WTRU receives an indication regarding the complete 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) for example, stop its non-COT monitoring and / or can monitor confirmed active LBT subbands (e.g., using a monitoring mode suitable for active COT on the LBT subband) based on receiving an indication that a subband (e.g., a confirmed active LBT subband) has been acquired (e.g., in a transmission within an LBT subband such as a confirmed active LBT subband) (e.g., upon receiving an indication that a subband has been acquired). In (e.g., additional and / or alternative) examples, the WTRU may (e.g., until further determination and / or indication) cease its non-COT monitoring and / or may, for example, monitor one or more (e.g., some or all) configured subbands (e.g., using a monitoring mode applicable to active COTs on one or more (e.g., all) LBT subbands) upon receiving an indication that a subband has been acquired (e.g., during a transmission in an LBT subband). For example, based on further determination and / or indication, the WTRU may remove one or more LBT subbands from monitoring the current COT.

[0115] Figure 2 An example of a WTRU frequency hopping pattern for monitoring multiple LBT subbands is shown. The WTRU can (e.g., as...) Figure 2 (As illustrated in the exemplary operation) For example, monitoring multiple LBT subbands (e.g., in a frequency hopping pattern) and / or being able to change the monitoring to monitor one or more acquired LBT subbands until an indication is received that the entire set of acquired LBT subbands has been acquired. For example, the WTRU can monitor configured LBT subbands (e.g., LBT subbands 1-4) (e.g., as shown in the example operation). Figure 2 (As shown in the example), thus hopping frequencies between subbands until the WTRU detects an indication on the LBT subband (e.g., LBT subband 1). The indication may be provided, for example, in the GC-PDCCH and / or DM-RS. For example, if the WTRU detects an indication (e.g., on LBT subband 1) and / or when the WTRU detects an indication, the WTRU may be or becomes aware of acquiring the LBT subband on which the indication was detected for the COT. Additional LBT subbands may or may not be acquired. For example, the WTRU may switch to micro-slot monitoring (e.g., micro-slot monitoring of the acquired LBT subband) until the next slot boundary. Figure 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. Figure 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. Figure 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... Figure 2 As shown in the example, the WTRU can switch from micro-slot monitoring of LBT subband 1 (e.g., based on the full set indication) to slot-based monitoring of acquired / active LBT subbands 1 and 3 during COT.

[0116] Figure 3 An example of a WTRU frequency hopping pattern for monitoring multiple LBT subbands is shown. For example, the WTRU can (e.g., as...) Figure 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...) Figure 3 The exemplary operation shown may (e.g., be configured to) behave similarly to another WTRU (e.g., based on...). Figure 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...) Figure 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). Figure 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). Figure 3(As shown in the example). One or more indicators of the acquired COT subbands and adaptive subband monitoring based on the indicators can support the efficient use of the acquired / active subbands during COT.

[0117] The WTRU can be configured to perform hierarchical monitoring, for example, in response to indications associated with a COT. The WTRU can monitor a subset of LBT subbands, for example, in the absence of an active COT. The WTRU can modify the monitored LBT subband set. For example, at each monitoring instance, the WTRU can (e.g., reassess or determine whether) adapt (e.g., maintain or modify / change) the monitored LBT subband set. The selection of monitored LBT subbands (e.g., at an instance) can be determined, for example, based on one or more of the following: the active LBT subband set in the previous COT; the previously monitored LBT subband set; a pre-configured monitoring pattern; indications received in the Discovery Reference Signal (DRS); the result of an LBT process or measurement; indications received in the previous COT; indications received outside the COT; and so on.

[0118] The selection of monitored LBT subbands at an instance can be determined (e.g., at least partially) based on the active LBT subband set in a previous COT. For example, the WTRU may know the previous COT that occupies the first LBT subband set. The WTRU may monitor at least one CORESET / search space / PDCCH candidate from at least one of the previously used LBT subbands. The previously used LBT subband set may be valid for a certain period of time. For example, the validity of the previously used LBT subband set may depend on the time elapsed since the COT expired. The WTRU may maintain timers for one or more LBT subbands. For example, when a timer expires, the WTRU may remove an LBT subband from the list of monitored LBT subbands. For example, when a timer expires, the WTRU may revert to the default LBT subband set.

[0119] The selection of monitored LBT subbands at an instance can be determined, for example, based on (e.g., at least partially) a previously monitored set of LBT subbands. The WTRU can monitor a first set of LBT subbands in a first time instance. The WTRU can determine a second set of LBT subbands in a second time instance (e.g., after the first time instance), for example, based on 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; wherein the WTRU detected one or more LBT subbands (e.g., a set of LBT subbands); and so on.

[0120] The selection of LBT subbands for monitoring at an instance can be determined, for example, based on a pre-configured monitoring pattern (e.g., at least partially). In the example, the pattern can be configured semi-statically by the network.

[0121] The selection of the LBT subband to be monitored at an instance can be determined, for example, based on the results of the LBT process and / or measurements (e.g., at least in part). In the example, the LBT process and / or measurements may be performed by the WTRU.

[0122] The selection of LBT subbands for monitoring at the instance can be determined, for example, based on indications received outside of the COT (e.g., at least partially). In the example, the indications can be received after the most recent COT has been completed.

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

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

[0125] In the example, a second monitoring mode can be determined based on one or more LBT subbands in which the WTRU receives the first indication. For example, the WTRU (e.g., having already received an indication in the first LBT subband) can adjust the WTRU's monitoring mode to allow the WTRU to be adapted in a way that increases the probability of receiving a complete COT structure indication (e.g., in the first detected LBT subband).

[0126] The WTRU can receive and / or interpret scheduling information. The 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. The WTRU can know the LBT subbands active at least at the start of the COT. For example, the WTRU can anticipate (e.g., only) scheduling in LBT subbands where the WTRU has received an indication of COT activity, until (e.g., further) indication of the entire set of active LBT subbands. For example, the WTRU can interpret scheduling grants to point to resources on LBT subbands where the WTRU has received grants, at least until further indication of the entire set of active LBT subbands. In an example, the WTRU can detect DM-RS and / or GC-PDCCH indicating activity in a first LBT subband. For example, the WTRU can anticipate any (e.g., zero or more) scheduling grants (e.g., only) associated with the indicated first active LBT subband, until the WTRU receives an indication of the entire set of active LBT subbands. Scheduling grants occurring before the indication of the entire set of active LBT subbands may include less resource allocation information. LBT subbands can be considered known, for example, based on the indication of the first active LBT subband (e.g., implicitly). This can reduce the number of bits used for resource allocation. A smaller downlink control information (DCI) payload can be achieved, for example, for transmissions occurring at the start of COT.

[0127] The WTRU's interpretation of resource allocation during scheduling authorization can be a function of the number and / or set of acquired LBT subbands. The number and / or set of acquired LBT subbands may differ at the start of the COT compared to after receiving the COT structure indication (or COT structure indication update).

[0128] The WTRU can be configured to receive indications associated with PDCCH monitoring. For example, the WTRU can be configured to receive explicit indications to modify PDCCH monitoring. The WTRU can receive indications to change its CORESET, search space, and / or PDCCH monitoring mode. The WTRU can be configured to have multiple monitoring modes and / or can be indicated to change these monitoring modes. The WTRU can receive (e.g., dynamic or semi-static) indications to change one or more monitoring modes (e.g., the configuration of the one or more monitoring modes). (e.g., each) a monitoring mode may have an index. An explicit indication to change a monitoring mode may include (e.g., a new or replacement) the index of the monitoring mode to make the change.

[0129] The WTRU can receive an instruction to change to a second PDCCH monitoring mode, for example, via a transmission received using a first PDCCH monitoring mode. For instance, the WTRU can receive a DCI in a PDCCH candidate being monitored as part of the first PDCCH monitoring mode. The DCI can, for example, indicate a change in monitoring of the WTRU from the first PDCCH monitoring mode to the second PDCCH monitoring mode. The WTRU can change its monitoring based on the instruction.

[0130] The new / replaced / changed PDCCH (e.g., second PDCCH) monitoring mode may change one or more of the following: actively monitored CORESET set, actively monitored search space set, actively monitored LBT subband set, actively monitored PDCCH candidate set, etc.

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

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

[0133] The WTRU can be configured with a maximum value y (e.g., 3) of cores. The WTRU can determine the number and / or set of cores it can monitor, for example, based on the maximum value y (e.g., y_max). The WTRU can determine the number and / or set of cores it can monitor based on one or more of the following: the set of configured cores, the set of available cores, the priority of each core (e.g., y_max), etc. Configured cores may include, for example, x semi-statically configured cores. Available cores may include, for example, cores located in active LBT subbands. The priority of a core may be determined, for example, based on its core index. The maximum value y (e.g., y_max) may be indicated by the network (e.g., in an explicit indication).

[0134] In the example, the WTRU may receive a first indication at the start of the COT indicating the activity of a subset of LBT subbands. The WTRU may, for example, determine a first active CORESET set based on the active LBT subbands. The WTRU may receive updates on the active LBT subband set. Updates may, for example, increase the number of active LBT subbands. The WTRU may, for example, modify its active CORESET set based on the updated LBT subband set. In the example, the WTRU may receive (e.g., explicit) indications of changing the monitoring mode of one or more PDCCHs, which may affect the set of y active CORESETs.

[0135] The WTRU can be configured to determine channel access priority. Channel access priority can be indicated by the channel access category (CAC). The gNB can control Category 2 (CAT2) UL transmissions (e.g., LBTs without random backoff). The gNB can control CAT2 UL transmissions, for example, if they fall within the gNB COT (e.g., including CG) and / or when they fall within the gNB COT.

[0136] The WTRU may be (pre-)configured with a set of CACs for uplink transmissions. One or more CACs may be used to determine logical channel constraints. For example, the WTRU may be pre-configured with CAC 2 and CAC 4. The WTRU may determine the applicable CAC for uplink transmissions in multiple steps (e.g., in two steps). The WTRU may (e.g., in a first step) receive an indication from the gNB. The WTRU may (e.g., in a second step) determine the CAC based on the received indication and / or other conditions. For example, the gNB may indicate (e.g., transmit) its COT to the WTRU in the cell. For example, the CAC may be selected based on the WTRU's previous transmission state. The previous transmission state may include, for example, an ACK or NACK indication. The gNB may provide an indication to the WTRU. The WTRU may determine the CAC based on the indication and / or one or more conditions.

[0137] The WTRU can receive indications from a network node (e.g., a gNB). In this example, the WTRU can be configured to receive indications from the gNB that the WTRU can use to determine, for example, a CAC. The WTRU can use the CAC to determine channel access priority, for example. Indications may include one or more of the following (e.g., a combination) or may be transmitted / received via, for example, WTRU-specific DCI; Group Common (GC) DCI; COT indication; Reference Signal (RS); etc.

[0138] Instructions (e.g., from the gNB) can be received, for example, via a DCI (e.g., a WTRU-specific DCI). For instance, the WTRU can receive a DCI activating an uplink configured for license type 2. The WTRU can receive a DCI requesting CSI feedback. A WTRU-specific DCI can schedule downlink data transmissions. The WTRU can use the instructions received via the DCI to determine the CAP associated with the COT.

[0139] Indications may be received, for example, via a group common DCI (e.g., from a gNB). The group common DCI may include one or more of downlink feedback indicators, slot format indicators, preemption indicators, etc. The WTRU may use the indications received via the DCI to determine the CAP associated with the COT.

[0140] Indications (e.g., from gNB) may include, for example, a COT indication. A COT indication may include a COT structure and / or LBT subbands / carriers for downlink transmission. A COT structure may include, for example, DL symbols, variable symbols, UL symbols, etc. The WTRU may use a COT indication (e.g., a COT structure indication) to determine the CAP associated with the COT.

[0141] For example, indications (e.g., from the gNB) can be received via one or more reference signals (e.g., DM-RS and / or CSI-RS). The reference signal configuration can be used to determine the CAP associated with the COT. For example, the gNB can configure multiple reference signals for the WTRU. Each configuration (e.g., in multiple configurations) can be associated with a CAC. In the 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). The WTRU can determine the CAC, for example, based on the reference signal (e.g., when the reference signal is detected). The 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.

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

[0143] The WTRU may determine the CAC, for example (at least in part), based on indications from a network node (e.g., a gNB). The WTRU may be configured to determine the CAC, for example (at least in part), based on one or more conditions. The WTRU (e.g., having received gNB indications, such as those described herein) may be configured to determine the CAC based on one or more of the following conditions (e.g., combinations thereof): the start time of the uplink transmission; the duration of the uplink authorized transmission; whether the transport block (TB) to be transmitted is a retransmission; the number of retransmissions / repetitions already performed; the CAC previously used for resources; the number of failed channel access attempts; whether previous uplink transmission opportunities were preempted; and so on.

[0144] The WTRU can be configured to determine the CAC, for example, based on the start time of the uplink transmission. In an example, the start time of the uplink transmission can be based on the start time of the uplink transmission relative to the end of the DL burst. For example, the WTRU can be configured with a configured authorization type 2 in the second symbol of time slot n. The WTRU can (e.g., during the first step) receive a COT indication in time slot n-4 (e.g., from the network node) indicating that the DL burst starts in time slot n-4 and ends in time slot n-1. The WTRU can determine that the 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).

[0145] In the example, the start time of the uplink transmission can be based on the start time of the uplink transmission relative to the reception time of the group common DCI and / or the WTRU-specific DCI. The WTRU can determine the CAC, for example, based on the offset X between the end symbol of the PDCCH carrying the DCI and the 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).

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

[0147] The WTRU can be configured to determine the CAC, for example, based on the transmit duration granted for uplink transmission. The WTRU can also determine the CAC, for example, based on the time-domain resource allocation used for uplink transmission.

[0148] In the example, the time-domain resource allocation for uplink transmission can be X symbols over 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).

[0149] CAC determination can (e.g., alternatively) be based on a comparison of the duration of a time-domain resource allocation with X symbols and a DL burst with Y symbols. For example, if... X < αY ,in α If it can be configured (e.g., by the WTRU as a fixed value in the instruction to the WTRU, etc.), then the WTRU can use a second CAC (e.g., CAC 2).

[0150] CAC determination can (e.g., alternatively) be based on a comparison of the time-domain resource allocation with X symbols and the duration of the DL burst, plus the time gap between the end of the DL burst and the start of uplink transmission. For example, the duration of the DL burst may include Y symbols. The time gap between the end of the DL burst and the start of uplink transmission may include Z symbols. For example, if... X < α ( Y + Z ),in α If it can be configured (e.g., by the WTRU as a fixed value in the instruction to the WTRU, etc.), then the WTRU can use a second CAC (CAC 2).

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

[0152] 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 (e.g., for an ongoing transmission of a TB) determine the CAC based on, for example, the number of retransmissions / repetitions that have been performed (e.g., retransmissions / repetitions of a TB). For example, if the number of retransmissions performed is less than a configured threshold, the WTRU can use a first CAC (e.g., CAC4). For example, if the number of retransmissions performed is not less than a configured threshold, the WTRU can use a second CAC (e.g., CAC 2).

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

[0154] The WTRU can be configured to determine CAC, for example, based on the number of failed channel accesses. The WTRU can also be configured to determine CAC, for example, based on the number of failed channel accesses caused by, for example, LBT failures on the same resource. The same resource may include configured authorized resources.

[0155] The WTRU can be configured to determine CAC based, for example, on whether a previous uplink transmission opportunity has been preempted. For example, the WTRU can be configured with authorization for uplink configuration within the first gNB shared COT. The WTRU can receive an uplink preemption indication. The WTRU can cancel an uplink transmission. The WTRU can, for example, use CAC 2 to transmit using the configured authorized resources during the next shared gNB COT.

[0156] Determined and / or indicated CACs can be used, for example, to determine logical channel restrictions by indicating channel access priorities.

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

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

[0159] The WTRU can be configured to send an indication of the channel access priority (e.g., CAPC) for acquiring a Channel Access Priority (COT). For example, a COT can be acquired if it is initiated on a resource (e.g., a channel) that may have already been determined to be idle. The COT can be acquired, for example, based on the result of an LBT (Local Level Bypass). The WTRU can indicate to the network, for example, the CAPC used in conjunction with the LBT procedure, based on the COT acquisition for uplink transmission (e.g., at the time of acquisition). The WTRU can indicate one or more logical channels (e.g., logical channels) that can be used to determine the CAPC for channel acquisition. The indication of logical channels can be more robust than the transmitted data, for example, to support (e.g., immediate) use of information over the network.

[0160] The WTRU may (e.g., be configured to) explicitly or implicitly indicate the CAPC for the LBT. Explicit indication by the WTRU may include one or more of the following: uplink control information (UCI) added to the transmission; bit strings added to the data; etc. Explicit indication by the WTRU may include the UCI added to the transmission. The WTRU may indicate the CAPC as part of the UCI. The CAPC's UCI may be mapped to resources close to the DM-RS, improving decoding error performance. The CAPC's UCI may include Cyclic Redundancy Check (CRC), improving robustness. The CAPC's UCI may be transmitted by the WTRU in a predetermined resource (e.g., a symbol in a time slot). For example, the first symbol of a UL transmission may include the UCI for the CAPC, which may provide the gNB with more time to determine the CAPC in preparation for an upcoming scheduling opportunity.

[0161] The WTRU (e.g., explicit) indication may include a bit string added to the data. The WTRU may append or pre-set the bit string to a TB code block. The bit string may indicate the CAPC used for channel acquisition. The bit string may be encoded and / or may include a CRC, which improves robustness.

[0162] The (e.g., implicit) indications made by the WTRU of the CAPC for channel acquisition may include one or more of the following: interleaving for transmission; parameters of the DM-RS; transmission parameters; etc.

[0163] The (e.g., implicit) indication made by the WTRU of the CAPC may include resources (e.g., interleaving) for transmission. The WTRU may select transmission resources, for example, based on the CAPC used for accessing the channel.

[0164] The (e.g., implicit) indication made by the WTRU of the CAPC may include parameters of the DM-RS. The parameters of the DM-RS may be selected, for example, based on the CAPC used to access the channel. The parameters may include one or more of, for example, sequences or resource maps.

[0165] The (e.g., implicit) indication made by the WTRU of the CAPC may include transmission parameters. The duration of the transmission may indicate the CAPC used for channel access. For example, the duration of the first transmission may be selected based on the CAPC used for channel access. The antenna port used for the first transmission may indicate or transmit the CAPC used for channel acquisition. The WTRU can be scheduled using a set of parameters. The WTRU may be selected from the parameter set, for example, based on the CAPC used for channel acquisition. The parameter set may include, for example, a set of TB or modulation and coding scheme (MCS) values.

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

[0167] The implementations and / or features described herein can be based on the behavior (e.g., actions) of the WTRU. In the examples, the behavior may be performed by an entity such as an NW node or other device that may not include WTRU functionality. In some examples (e.g., certain use cases or certain time instances), the entity or other device may behave like a WTRU. One or more examples in this document may also apply to entities or other devices.

[0168] A WTRU can be configured to determine logical channel limits. WTRUs can be scheduled using UL transmissions within a COT (e.g., an ongoing COT). WTRUs can be instructed (e.g., can receive instructions or indications for logical channel limits) for example, in a scheduling DCI. A scheduling DCI may include granting or allocation. WTRUs can determine logical channel limits, for example, based on received instructions or indications. WTRUs can receive indications in a DCI and use those indications to determine the CAP associated with the COT. WTRUs can determine logical channels in uplink transmissions within the COT, for example, based on limits (e.g., logical channel limits). Limits can be based on priority levels (e.g., CAP) and / or can indicate logical channels. In some examples, the indication of a priority level can be equal to the indication of a logical channel (e.g., which may be associated with a priority level). Logical channels can be associated with priority levels (e.g., logical channel priorities associated with logical channels). Figure 5 As shown, WTRU can select data of appropriate priority for constructing a TB for emission. To select data of appropriate priority for constructing a TB for emission (e.g., as... Figure 5 As shown), the WTRU can determine logical channel priorities (e.g., LCH priorities), and the WTRU can determine whether a 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. Figure 5 As shown, data with appropriate priorities can be selected. For example, if a logical channel is associated with a channel access priority equal to or higher than the channel access priority associated with COT, then the logical channel can be included in a transmission performed by the WTRU during COT.

[0169] Priority determination indicates which logical channels should be included in a transmission made by the WTRU. The WTRU may include data from logical channels having the same and / or higher priorities as the priority level and / or logical channels indicated in the restrictions (e.g., associated with the priority level). The same priority may include priority levels equal to the priority level indicated in the restrictions. Figure 6 As shown, the WTRU can use defined logical channel restrictions to determine whether a logical channel is permitted to be included in a scheduled transmission. For example, the restriction may indicate a priority level (e.g., CAP), and the WTRU may include data from logical channels associated with the same and / or higher priorities as the indicated priority level (e.g., only from logical channels associated with the same and / or higher priorities as the indicated priority level) (e.g., in a UL transmission). Figure 6As shown, if the defined logical channel constraints allow logical channels to be included in the transmission, then the transmission may include logical channels.

[0170] The WTRU can monitor the presence of a signal indicating the channel access priority (e.g., CAPC) used to acquire a COT. For example, channel access priority can indicate the 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 an unlicensed or configured licensed UL transmission occurring within an active COT), the WTRU can monitor the presence of a signal indicating the CAPC used to acquire the COT (e.g., prior to the transmission of the signal). Figure 6 As shown, the WTRU can determine logical channel limitations based on indications received from a gNB including a CAPC associated with the 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 the COT structure indication). In some examples, the DCI may be different from the scheduling DCI. The WTRU can (e.g., alternatively and / or additionally) determine the CAPC, for example, based on (e.g., by receiving) a signal used to trigger CG transmission. The WTRU can (e.g., alternatively and / or additionally) determine the CAPC, for example, as part of the parameters of gNB transmissions within the COT (e.g., DM-RS or GC-PDCCH).

[0171] Figure 5 Examples are shown, such as Figure 6 The example shown illustrates how logical channel limits are determined based on priorities associated with the COT (e.g., channel access priority). Figure 5 As shown, the WTRU can receive and / or use indications of priorities (e.g., CAPC) to select what to transmit in a shared COT. The WTRU can receive (e.g., by the network) indications of CAPCs used to acquire / start a COT. The WTRU can, for example, receive the CAPC indications in a scheduling grant for UL transmissions. The scheduling grant can schedule resources for transmissions to be sent during the COT. Resources can occur during the COT. The scheduling grant may include CAPCs used by the network if the COT is acquired (e.g., an ongoing COT) and / or when the COT is acquired. The WTRU can determine the priorities associated with the COT. The WTRU can determine the data that the WTRU can transmit during the COT (e.g., determining data with applicable / sufficient priorities and / or compliant with restrictions) based on the priorities included in the scheduling grant (e.g., allowed priorities). The WTRU can determine the restricted logical channel set (e.g., such as...) that the WTRU can use to construct a TB for scheduled transmissions. Figure 6 (As shown in the example). Figure 5As 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).

[0172] 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.

[0173] Figure 6 An example of a shared COT based on a CAP (e.g., CAPC) associated with the COT is shown. Figure 6 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.

[0174] 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 the 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...), Figure 6As shown), the WTRU can use data from the LCH set, where the associated CAPC has a priority equal to or higher than that of the CAPC used by the gNB (e.g., CAPC 2) (e.g., CAPC 2, CAPC 1). The WTRU can transmit during the COT (e.g., via a subband). The WTRU can instruct actions. In the example, for instance, when using a Type 4 LBT procedure to acquire a channel within an active COT, the WTRU can instruct actions including the use of a Type 4 LBT. The WTRU can, for example, instruct the use of a Type 4 LBT and / or different CAPCs to indicate the CAPC used for the COT acquired by the WTRU using a method similar to that described herein. Using a Type 4 LBT can re-initiate the COT and / or affect the COT duration. The WTRU can, for example, monitor the COT structure indication to determine the updated COT duration.

[0175] Although features and elements have been described above in specific combinations, those skilled in the art will understand that each feature or element may be used alone or in any combination with other features and elements. Furthermore, the methods described herein may 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 (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile optical discs (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), comprising: Processor, the processor being configured to: Determine the channel access priority associated with Channel Occupancy Time (COT); Logical channel restrictions are determined based on the channel access priority associated with the COT; Determining whether a logical channel is permitted will be included in transmissions that will be restricted by the logical channel during the COT period by the WTRU. as well as The transmission is sent 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.

2. A method performed by a wireless transmit / receive unit (WTRU), comprising: Determine the channel access priority associated with Channel Occupancy Time (COT); Logical channel restrictions are determined based on the channel access priority associated with the COT; Determining whether a logical channel is permitted will be included in transmissions that will be restricted by the logical channel during the COT period by the WTRU. as well as The transmission is sent 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.

3. The WTRU of claim 1 or the method of claim 2, wherein the logical channel restriction is performed in such a way that the logical channel is included if it is associated with a channel access priority equal to or higher than the channel access priority associated with the COT, and is excluded if it is associated with a channel access priority lower than the channel access priority associated with the COT.

4. The WTRU of claim 1 or the method of claim 2, wherein the channel access priority indication is used by the base station to obtain the Listen-Before-Speak (LBT) parameter for the subband of the COT.

5. The WTRU of claim 1 or the method of claim 2, wherein the channel access priority associated with the COT is indicated by a Channel Access Priority Category (CAPC).

6. The WTRU of claim 1 or the method of claim 2, wherein the channel access priority associated with the COT is received in a scheduling grant for resources to be used for transmissions during the COT or is received in downlink control information for COT structure indication.

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

8. The WTRU of claim 1, wherein the processor is further configured to: Receive downlink control information (DCI) including a COT structure indication, wherein the channel access priority associated with the COT is determined based on the COT structure indication.

9. The WTRU of claim 1, wherein the processor is further configured to: An indication is received from the base station via downlink control information (DCI), wherein the channel access priority associated with the COT is determined using the indication received via the DCI.

10. The WTRU of claim 1, wherein the channel access priority associated with the COT is indicated by a reference signal configuration, wherein the processor is further configured to: The access priority of the first channel is determined based on the configuration of the first reference signal; and The access priority of the second channel is determined based on a second reference signal configuration that is different from the configuration of the first reference signal.

11. The WTRU of claim 1, wherein the processor is further configured to: Determine the resources that occur during the COT, wherein the transmission uses the resources to send.

12. The WTRU of claim 1, wherein the processor is further configured to: Determine the logical channel (LCH) priority associated with the logical channel; and The determination of whether the logical channel is associated with a channel access priority equal to or higher than the channel access priority associated with the COT is based on the LCH priority associated with the logical channel and the channel access priority associated with the COT, wherein the determination of whether the logical channel is permitted will be included in the transmission by the WTRU during the COT based on the determination of whether the logical channel is associated with a channel access priority equal to or higher than the channel access priority associated with the COT.

13. The method according to claim 2, further comprising: Receive instructions from the base station via downlink control information (DCI); as well as The channel access priority associated with the COT is determined based on the indication received via the DCI.

14. The method according to claim 2, further comprising: Determine the resources that occur during the COT, wherein the transmission uses the resources to send.

15. The method according to claim 2, further comprising: Receive a COT structure indication, wherein the channel access priority associated with the COT is determined based on the COT structure indication.

16. The method according to claim 2, further comprising: Determine the logical channel (LCH) priority associated with the logical channel; as well as The determination of whether the logical channel is associated with a channel access priority equal to or higher than the channel access priority associated with the COT is based on the LCH priority associated with the logical channel and the channel access priority associated with the COT, wherein the determination of whether the logical channel is permitted will be included in the transmission by the WTRU during the COT based on the determination of whether the logical channel is associated with a channel access priority equal to or higher than the channel access priority associated with the COT.

Images