Methods, architectures, apparatuses, and systems for channel access with channel occupancy time sharing for sidelink (SL) model-1 for unlicensed Uu and unlicensed SL

Abstract

Programs, methods, architectures, apparatuses, systems, devices, and computer program products are described herein for channel access with channel occupancy time (COT) sharing. A method implemented in a wireless transmit / receive unit (WTRU) includes transmitting to a base station first scheduling information associated with an SL transmission to be transmitted in an unlicensed spectrum to another WTRU. The method includes receiving, from the base station, second scheduling information indicating a scheduling of the SL transmission and a shared COT, wherein the shared COT may be shared between any one of uplink, downlink, and sidelink transmissions. The method includes determining that SL transmissions are scheduled in a shared COT. The method includes transmitting, to another WTRU, an SL transmission without listen before talk (LBT) or with a shorter LBT than full LBT based on a determination that the SL transmission may be scheduled in a shared channel occupancy time.

Description

[0001] Cross - reference to related applications

[0002] This application claims the benefit of U.S. Patent Application No. 63 / 425,899, filed on November 16, 2022, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, devices, and systems related to channel access involving channel occupancy time (COT) sharing for sidelink (SL) mode - 1 with unlicensed Uu (e.g., unlicensed uplink / downlink) and unlicensed SL. Background Art

[0004] Sidelink (SL) relay was introduced in the 3rd Generation Partnership Project (3GPP) Release 17 to extend network coverage. Either SL or Uu (e.g., uplink / downlink) can use an unlicensed frequency band. Before transmitting in an unlicensed frequency band, a wireless transmit / receive unit (WTRU) may perform channel sensing to determine the availability of the channel. The embodiments described herein are designed in view of the foregoing. Summary of the Invention

[0005] Methods, architectures, devices, and systems for channel access with COT sharing for SL mode - 1 with unlicensed Uu and unlicensed SL are described herein. Hereinafter, methods and devices for improving channel access using COT sharing for SL mode - 1 with unlicensed Uu and unlicensed SL are defined and described, and protection thereof is claimed according to the appended claims. Brief Description of the Drawings

[0006] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings. The figures in these drawings are examples, like the detailed description. Similarly, the drawings (figures) and the detailed description should not be considered restrictive, and other equally valid examples are possible and may occur. In addition, the same reference numerals (“reference signs”) in the figures represent the same elements, where:

[0007] Figure 1A is a system diagram illustrating an example communication system;

[0008] Figure 1B is illustrated in Figure 1A a system diagram of an example wireless transmit / receive unit (WTRU) that can be used within the illustrated communication system;

[0009] Figure 1C is illustrated in Figure 1ASystem diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system;

[0010] Figure 1D is a system diagram that illustrates another example RAN and another example CN that can be used within Figure 1A the illustrated communication system;

[0011] Figure 2 is a diagram of an example that illustrates the relationship between 5G network characteristics and LTE network characteristics;

[0012] Figure 3 is a diagram of an example that illustrates SL mode 1 operation using dynamic scheduling;

[0013] Figure 4 is a diagram of an example channel access procedure that illustrates COT sharing initiated by a Tx WTRU;

[0014] Figure 5 is a diagram of an example channel access procedure that illustrates COT sharing initiated by a Tx WTRU using assistance information from an Rx WTRU;

[0015] Figure 6 is a diagram of an example channel access procedure that illustrates COT sharing initiated by a gNB;

[0016] Figure 7 is a diagram of an example channel access procedure that illustrates COT sharing initiated by a gNB using assistance information from an Rx WTRU;

[0017] Figure 8 is a diagram of an example channel access method that illustrates COT sharing initiated by a WTRU;

[0018] Figure 9 is a diagram of an example channel access method that illustrates COT sharing initiated by a gNB;

[0019] Figure 10 is a diagram of an example method for sharing COT between a WTRU and a base station;

[0020] Figure 11 is a diagram of an example method for sharing COT between a WTRU and a base station, where the shared COT is initiated by the base station; and

[0021] Figure 12 is a diagram of an example method for sharing COT between a WTRU and a base station, where the shared COT is initiated by the WTRU. Detailed Description

[0022] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the following description. Additionally, embodiments and examples not specifically described herein may be practiced in lieu of or in combination with the embodiments and other examples explicitly, implicitly, and / or inherently described, disclosed, or otherwise provided (collectively referred to as "provided") herein. Although various embodiments are described and / or claimed herein in which a device, system, apparatus, etc. and / or any of its elements perform an operation, process, algorithm, function, etc. and / or any part thereof, it should be understood that any embodiment described and / or claimed herein assumes that any device, system, apparatus, etc. and / or any of its elements is configured to perform any operation, process, algorithm, function, etc. and / or any part thereof.

[0023] Example communication system

[0024] The methods, apparatuses, and systems provided herein are well-suited for communication involving both wired and wireless networks. Referring to Figure 1A - 1D An overview of various types of wireless devices and infrastructure is provided, where various elements of the network may utilize, execute, be arranged in accordance with, and / or be adapted for the methods, apparatuses, and systems provided herein and / or be configured for the methods, apparatuses, and systems provided herein.

[0025] Figure 1A FIG. [FIGURE NUMBER] is a system diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messaging, broadcast, etc. to a plurality of wireless users. The communication system 100 may enable a plurality of wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may 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 (ZT) unique word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), etc.

[0026] As Figure 1A Please note that the figure number in the translation of is replaced with [FIGURE NUMBER] as it seems to be a placeholder in the original text. If there is a specific figure number, it should be filled in accordingly.As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the 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, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop computer, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., a robot and / or other wireless devices operating in an industrial and / or automated processing chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

[0028] 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 wireless 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 wireless services to a specific geographical area, which may be relatively fixed or may vary over time. A cell may also be 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 or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0029] Base stations 114a, 114b may communicate with one or more of WTRUs 102a, 102b, 102c, 102d via air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) may be used to establish air interface 116.

[0030] More specifically, as described above, communication system 100 may be a multi-access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN 104 / 113 and WTRUs 102a, 102b, 102c may implement a wireless technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish air interface 116. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) and / or High Speed Uplink Packet Access (HSUPA).

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

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

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

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

[0035] For example, Figure 1AThe base station 114b therein can be a wireless router, a home Node B, a home eNode-B, or an access point, and can utilize any suitable RAT to facilitate wireless connection in a local area, such as commercial premises, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drones), roads, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d can implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any one of a small cell, a pico cell, or a femto cell. As Figure 1A shown, the base station 114b can have a direct connection to the Internet 110. Thus, it may not be required for the base station 114b to access the Internet 110 via the CN 106 / 115.

[0036] The RAN 104 / 113 can communicate with the CN 106 / 115, and the CN 106 / 115 can be any type of network configured to provide voice, data, applications, and / or voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data can have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 can provide call control, billing services, location-based services, prepaid calls, Internet connection, video distribution, etc. and / or perform advanced security functions, such as user authentication. Although not shown in Figure 1A it should be understood that the RAN 104 / 113 and / or the CN 106 / 115 can communicate directly or indirectly with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113 that may utilize the NR radio technology, the CN 106 / 115 can also communicate with another RAN (not shown) that employs any one of the GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

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

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

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

[0040] The processor 118 can be a general-purpose processor, a dedicated 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. The processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, and the transceiver 120 can be coupled to the transmit / receive element 122. Although Figure 1B the processor 118 and the transceiver 120 are depicted as separate components, it should be understood that the processor 118 and the transceiver 120 can be integrated together, such as in an electronic package or a chip.

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

[0042] Although the transmit / receive element 122 is depicted as a single element in Figure 1B the WTRU 102 can include any number of transmit / receive elements 122. For example, the WTRU 102 can employ MIMO technology. Thus, in one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interface 116.

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

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

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

[0046] The processor 118 can also be coupled to a GPS chipset 136, which can 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 can receive location information from a base station (e.g., base stations 114a, 114b) via an 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 the WTRU 102 can obtain location information by any suitable location determination method while remaining consistent with the embodiments.

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

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

[0049] Figure 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may communicate with the WTRU 102a, 102b, and 102c via the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

[0050] The RAN 104 may include eNode-Bs 160a, 160b, 160c, but it should be understood that the RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. Each of the eNode-Bs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c via the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to and receive wireless signals from the WTRU 102a.

[0051] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink (UL) and / or downlink (DL), etc. As Figure 1C shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via the X2 interface.

[0052] Figure 1C shown, the CN 106 may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. Although each of the foregoing elements is described 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.

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

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

[0055] The SGW 164 can be connected to the PGW 166, which can provide the WTRUs 102a, 102b, 102c with access to a packet switched network such as the Internet 110 to facilitate communication between the WTRUs 102a, 102b, 102c and IP enabled devices.

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

[0057] Although the WTRU is described as a wireless terminal in Figure 1A - 1D it is contemplated that in some representative embodiments, such a terminal can use (e.g., temporarily or permanently) a wired communication interface to the communication network.

[0058] In a representative embodiment, another network 112 can be a WLAN.

[0059] Infrastructure Basic Service Set (BSS) mode WLANs can have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP can have access or an interface to a Distribution System (DS) or another type of wired / wireless network that conveys traffic to and / or from the BSS. Traffic destined for an STA from outside the BSS can reach the STA through the AP and can be delivered to the STA. Traffic from an STA to a destination outside the BSS can be sent to the AP to be delivered to the corresponding destination. For example, traffic between STAs within the BSS can be sent through the AP, where the source STA can send the 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 peer traffic. Peer traffic can be sent between the source and destination STAs (e.g., directly between them) using Direct Link Setup (DLS). In some representative embodiments, DLS can use 802.11e DLS or 802.11z Tunnel DLS (TDLS). WLANs using Independent BSS (IBSS) mode may not have an AP, and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to in this document as the "ad-hoc" communication mode.

[0060] When operating in 802.11ac infrastructure mode or a similar operating mode, the AP can transmit beacons on a fixed channel such as the primary channel. The primary channel can be of a fixed width (e.g., 20 MHz wideband) or a width dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STAs to establish a connection with the AP. In some representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, such as in 802.11 systems. For CSMA / CA, STAs including the AP (e.g., each STA) can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. One STA (e.g., only one station) can transmit at any given time within a given BSS.

[0061] High Throughput (HT) STAs can communicate using 40 MHz wide channels, e.g., by combining the primary 20 MHz channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[0062] A very high throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz and / or 80 MHz channels may be formed by combining consecutive 20 MHz channels. The 160 MHz channel may be formed by combining eight consecutive 20 MHz channels or by combining two non - consecutive 80 MHz channels, which may be referred to as an 80 + 80 configuration. For the 80 + 80 configuration, after channel coding, the data may pass through a segment parser, which may split the data into two streams. The inverse fast Fourier transform (IFFT) processing and time - domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations of the above 80 + 80 configuration may be reversed, and the combined data may be sent to the media access control (MAC) layer, entity, etc.

[0063] 802.11af and 802.11ah support sub - 1GHz operation modes. The channel operation bandwidth and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non - TVWS spectrum. According to a representative embodiment, 802.11ah may support metering - type control / machine - type communication (MTC), such as MTC devices in a macro - coverage area. The MTC devices may have certain capabilities, for example, limited capabilities, including supporting (e.g., only supporting) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0064] WLAN systems (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) that can support multiple channels and channel bandwidths include a channel that can be designated as the primary channel. The 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 restricted by the STA that supports the minimum bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for an STA that supports (e.g., only supports) the 1MHz mode (e.g., an MTC-type device), 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 sensing and / or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy transmitting to the AP, for example, due to an STA (only supporting the 1MHz operating mode), the entire available frequency band can be considered busy, even if most of the frequency band remains idle and may be available.

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

[0066] Figure 1D is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

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

[0068] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol interval and / or the OFDM subcarrier interval may be different for different transmissions, different cells, and / or different portions of the radio transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a variable number of OFDM symbols and / or an absolute time of continuously variable length).

[0069] gNB 180a, 180b, 180c can be configured to communicate with WTRUs 102a, 102b, 102c in a stand-alone configuration and / or a non-stand-alone configuration. In a stand-alone configuration, WTRUs 102a, 102b, 102c can communicate with gNB 180a, 180b, 180c without also accessing another RAN (e.g., such as eNode-Bs 160a, 160b, 160c). In a stand-alone configuration, WTRUs 102a, 102b, 102c can utilize one or more of gNB 180a, 180b, 180c as a mobility anchor. In a stand-alone configuration, WTRUs 102a, 102b, 102c can communicate with gNB 180a, 180b, 180c using signals in an unlicensed band. In a non-stand-alone configuration, WTRUs 102a, 102b, 102c can communicate / connect with gNB 180a, 180b, 180c while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c can implement the DC principle to communicate with one or more of gNB 180a, 180b, 180c and one or more of eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-stand-alone configuration, eNode-Bs 160a, 160b, 160c can act as a mobility anchor for WTRUs 102a, 102b, 102c, and gNB 180a, 180b, 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, 102c.

[0070] Each of gNB 180a, 180b, 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 slice support, dual connectivity, interworking between NR and E-UTRA, routing user plane data to user plane functions (UPFs) 184a, 184b, routing control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As Figure 1D shown, gNB 180a, 180b, 180c can communicate with each other via the Xn interface.

[0071] 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 at least one data network (DN) 185a, 185b. Although each of the foregoing elements is described 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.

[0072] The AMF 182a, 182b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, managing the registration area, terminating NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing, for example, to customize the CN support for the WTRU 102a, 102b, 102c based on the type of service used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low-latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 182a, 182b may provide control plane functions for handover between the RAN 113 and other RANs (not shown) employing other radio technologies (such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as Wi-Fi).

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

[0074] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which can provide access to a packet switched network (such as the Internet 110) to the WTRUs 102a, 102b, 102c, for example, to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. UPF 184a, 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0075] The CN 115 can facilitate communication with other networks. For example, the CN 115 can include an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108, or can communicate with the IP gateway. In addition, the CN 115 can provide access to other networks 112 to the WTRUs 102a, 102b, 102c, and the other networks 112 can include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c can be connected to the local data network (DN) 185a, 185b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b through the UPF 184a, 184b.

[0076] In view of Figure 1A - 1D and Figure 1A - 1D In view of the corresponding descriptions of, one or more or all of the functions described herein for any one of the following: WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b and / or any other element / devices (s) described herein may be performed by one or more emulation elements / devices (not shown). The emulation devices can be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices can be used to test other devices and / or simulate network and / or WTRU functions.

[0077] A simulation device can be designed to implement one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, one or more simulation devices can 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. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. For testing purposes, a simulation device can be directly coupled to another device, and / or can perform tests using over-the-air wireless communication.

[0078] One or more simulation devices can perform one or more functions, including all functions, without being implemented / deployed as part of a wired and / or wireless communication network. For example, a simulation device can be used to test test scenarios in a laboratory and / or non-deployed (e.g., test) wired and / or wireless communication networks to implement testing of one or more components. One or more simulation devices can be test devices. A simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication via an RF circuit (e.g., which can include one or more antennas).

[0079] Throughout the embodiments described herein, the terms "serving base station", "base station", "gNB", "network", collectively referred to as "gNB", can be used interchangeably to specify any network element, such as, for example, a network element acting as a serving base station. The embodiments described herein are not limited to gNBs and apply to any other type of serving base station.

[0080] For clarity, throughout the embodiments described herein, meeting, failing to meet conditions, and "(one or more) configuration condition parameters" are described relative to a threshold (e.g., greater than or less than (e.g., threshold) value, configured (e.g., threshold) value, etc.). For example, meeting a condition can be described as being above (e.g., threshold) value, while failing to meet a condition (e.g., a performance criterion) can be described as being below (e.g., threshold) value. The embodiments described herein are not limited to threshold-based conditions. Any other kind of conditions and (one or more) parameters (such as, for example, belonging to or not belonging to a value range) can apply to the embodiments described herein.

[0081] Throughout the embodiments described herein, information (e.g., configuration) can be described as being received by the WTRU from the network, e.g., via system information or via any kind of protocol message. Although not explicitly mentioned throughout the embodiments described herein, the same (e.g., configuration) information can be pre-configured in the WTRU (e.g., via any kind of pre-configuration method, such as, e.g., via factory settings) such that this (e.g., configuration) information can be used by the WTRU without receiving it from the network.

[0082] Throughout the embodiments described herein, the phrase "the WTRU may be configured with a set of parameters" is equivalent to or may be used interchangeably with "the WTRU may receive (e.g., from another network element (e.g., gNB)) configuration information indicating a set of parameters". Throughout the embodiments described herein, the phrases "the WTRU may report something" and "the WTRU may be configured to report something" are equivalent to or may be used interchangeably with "the WTRU may transmit (e.g., report) information indicating something".

[0083] Throughout the embodiments described herein, the terms "Uu", "Uu interface", and "uplink / downlink" may be used interchangeably to refer to information (e.g., (one or more) messages) exchanged between the WTRU and the base station (e.g., in a frequency channel) via either the uplink or the downlink. Throughout the embodiments described herein, the terms "sidelink", "PC5 interface", "PC5" may be used interchangeably to refer to information (e.g., (one or more) messages) exchanged between two WTRUs (e.g., in a frequency channel) via the sidelink (SL).

[0084] Examples of services and associated network characteristics

[0085] NR vehicle-to-everything (V2X) can be applicable to a wider set of more advanced V2X use cases and can be arranged into four use case groups: vehicle platooning, extended sensors, advanced driving, and remote driving.

[0086] Vehicle platooning can enable vehicles to dynamically form a queue to travel together. For example, (e.g., all) vehicles in the queue can obtain information from the leading vehicle to manage the platoon. This information can allow the vehicles to drive closer in a coordinated manner, travel in the same direction, and move together.

[0087] Extended sensors can enable the exchange of any raw and processed data, as well as live video images, collected by any local sensors between any vehicle, roadside unit, pedestrian device, and V2X application server. A vehicle can enhance its perception of its environment beyond the range detectable by its own sensors and can have a broader and more comprehensive view of the local situation. Extended sensors can rely on high data rates.

[0088] Advanced driving can enable semi-automatic or fully automatic driving. For example, (e.g., each) vehicle and / or roadside unit (RSU) can share its own sensed (e.g., processed) data obtained from its local sensors with nearby vehicles, which can allow the vehicles to synchronize and coordinate their trajectories or maneuvers. For example, (e.g., each) vehicle can share its driving intention with nearby vehicles.

[0089] Remote driving can enable any remote driver and V2X application to operate a remote vehicle for those passengers who cannot drive themselves or to operate a remote vehicle that may be located in a hazardous environment. In situations with limited variation and predictable routes, such as, for example, public transportation, cloud-based driving can be used. Remote driving can rely on high reliability and low latency.

[0090] Figure 2 is a diagram illustrating an example of the relationship between 5G network characteristics and LTE network characteristics. For example, 5G network characteristics can include an SL range of up to 1000 m, a throughput of up to 1 Gbps, a latency of as low as 3 milliseconds, a reliability of up to 99.999%, and a transmission rate of up to 100 messages / second. Other challenging network characteristics can include relative mobility speed and positioning accuracy. There is no use case that can be expected to meet all of these bounding network characteristics. There may be network characteristics related to any one of security, integrity, authorization, and privacy.

[0091] NR V2X

[0092] The NR V2X physical layer can support any of broadcast, unicast, and multicast SL operations. The addition of unicast and multicast can be associated with the introduction of features such as SL hybrid automatic repeat request (HARQ) feedback, higher-order modulation, sidelink channel state information (SL CSI), and PC5-radio resource control (RRC).

[0093] Examples of physical SL channels and signals

[0094] NR V2X SL can use any one of the following: (i) Physical Sidelink Broadcast Channel (PSBCH) and its Demodulation Reference Signal (DMRS), (ii) Physical Sidelink Control Channel (PSCCH) and its DMRS, (iii) Physical Sidelink Shared Channel (PSSCH) and its DMRS, (iv) Physical Sidelink Feedback Channel (PSFCH), (v) Phase Tracking Reference Signal (PT-RS) in Frequency Range 2 (FR2), (vi) Channel State Information Reference Signal (CSI-RS), and (vii) Sidelink Primary Synchronization Signal and Secondary Synchronization Signal (S-PSS and S-SSS), which can be organized together with PSBCH into a Sidelink Synchronization Signal Block (S-SSB). S-PSS and S-SSS can be collectively referred to as Sidelink Synchronization Signal (SLSS).

[0095] NR-V2X SL can support a subcarrier spacing of any one of 15 kHz, 30 kHz, 60 kHz, and 120 kHz. Their association with the cyclic prefix (CP) and frequency range can be the same as that of NR uplink / downlink, based on (e.g., only based on) the CP-OFDM waveform. The modulation schemes available can include any one of Quadrature Phase Shift Keying (QPSK), 16-Quadrature Amplitude Modulation (QAM), 64-QAM, and 256-QAM.

[0096] PS BCH can transmit a Sidelink Broadcast Channel (SL-BCH) transport channel, which can carry (e.g., include) the SL V2X Master Information Block (MIB-V2X) from, for example, the RRC layer. For example, PSBCH can transmit MIB-V2X once every 160 milliseconds in 11 resource blocks (RBs) of the SL bandwidth, for example, repeated within that period. The DMRS associated with PSBCH can be transmitted in one (e.g., each) symbol of the S-SSB time slot. The Sidelink Primary Synchronization Signal (S-PSS) and Sidelink Secondary Synchronization Signal (S-SSS) can be transmitted in the S-SSB together with PSBCH. They can jointly convey (e.g., indicate) the SLSSID used by the WTRU.

[0097] The sidelink control information (SCI) in NR V2X can be transmitted in two phases. The first-phase SCI can be carried on the PSCCH and can include information enabling the sensing operation and information indicating the resource allocation of the PSSCH.

[0098] The PSSCH may transmit a second-stage SCI and a sidelink shared channel (SL-SCH) transport channel. The second-stage SCI may carry information that may be used to identify (e.g., and decode) the associated SL-SCH, control the HARQ process, and trigger channel state information (CSI) feedback, etc. The SL-SCH may carry (e.g., include) a transport block (TB) for data transmitted over the sidelink.

[0099] In a first example, the resources on which the PSSCH can be transmitted may be scheduled or configured by the gNB. For example, the WTRU may receive (e.g., be scheduled or configured with) information indicating the resources for PSSCH transmission. In a second example, the resources on which the PSSCH can be transmitted may be determined by a sensing procedure performed by the transmitting WTRU (e.g., autonomously). For example, the TB may be transmitted one or more times. The DMRS associated with any rank-1 and rank-2 PSSCH may be transmitted in any two, three, and four sidelink symbols allocated by a sidelink slot. Multiplexing between the PSCCH and the PSSCH may be performed either in time or in frequency within a slot.

[0100] The PSFCH may carry (e.g., include) HARQ feedback from a WTRU (referred to herein as the RxWTRU), which may be the (e.g., expected) receiver of a PSSCH transmission, over the sidelink to a WTRU (referred to herein as the TxWTRU) that may have performed the transmission. The sidelink HARQ feedback may be in the form of either (e.g., conventional) acknowledgement (ACK) / negative acknowledgement (NACK), and (e.g., only) NACK where nothing is transmitted in case of successful decoding. The PSFCH transmission may include a Zadoff-Chu sequence in one physical resource block (PRB), which is repeated on two OFDM symbols near the end of the sidelink resources in a slot, and the first of the two OFDM symbols may be used for automatic gain control (AGC). The time resources for the PSFCH may be (e.g., pre-)configured to occur once every one, two, or four slots.

[0101] Examples of resource allocation patterns

[0102] A first mode (which may be referred to herein as "mode 1") may be used for resource allocation by the gNB. NR V2X applications may be associated with various arrangements of periodic and aperiodic message types. Resource allocation mode 1 may provide any dynamic authorization of sidelink resources from the gNB, as well as authorization of periodic sidelink resources that may be semi-statically configured, for example, by RRC.

[0103] For example, dynamic SL authorized downlink control information (DCI) may provide (e.g., indicate) resources for one or more transmissions of a transport block in order to allow control of reliability. In the case where HARQ operation is enabled, the (one or more) transmissions may be subject to the SL HARQ procedure.

[0104] For example, SL configured grant may be such that it can be configured once (e.g., by receiving configuration information indicating the configured SL grant), and can be used by the WTRU (e.g., immediately) after receiving the configuration information, e.g., until it can be released by, e.g., RRC signaling (which may be referred to herein as type 1). For example, in the case where any beam failure and physical layer problems occur in NR Uu, the WTRU may (e.g., be allowed to) continue to use such type of SL configured grant until, e.g., the radio link failure (RLF) detection timer expires before falling back to (e.g., an abnormal, fallback) resource pool (e.g., within the time period associated with the RLF detection event). Another type of SL configured grant (which may be referred to herein as type 2) may be configured (e.g., once) and may not be used until the gNB can send DCI indicating that the grant can be active to the WTRU, and can be used until another DCI indicating deactivation can be received. Either type 1 resources or type 2 resources may be a set of SL resources that recurrently appear periodically, which may match the characteristics of V2X services (e.g., by the gNB). One or more configured grants may be configured to allow provision of different services, traffic types, etc.

[0105] Modulation and coding scheme (MCS) information for any dynamic grant and configured grant may be arbitrarily provided and constrained, e.g., by RRC signaling. For example, the RRC information may indicate any one of the MCS and the MCS range to be used by the Tx WTRU. In another example, the MCS may remain unconfigured. In the case where the RRC information does not indicate (e.g., a single) MCS, the TxWTRU may select (e.g., an appropriate) MCS based on, e.g., the TB to be transmitted (e.g., knowledge of the TB) and, e.g., the SL radio conditions.

[0106] A second mode (which may be referred to herein as "mode 2") may be used for WTRU autonomous resource selection. For example, the WTRU may sense, within (e.g., a preconfigured resource pool), which resources may not be used by other (one or more) WTRUs with higher priority traffic, and may select (e.g., an appropriate) number of such resources for its own transmission. Having selected such resources, the WTRU may make multiple (e.g., a certain number of) arbitrary transmissions and retransmissions within the selected resources, or until the conditions for resource reselection can be met.

[0107] The Mode 2 sensing procedure can be used to select (e.g., and reserve) resources for various purposes of illustrating the introduction of SL HARQ in NR V2X to support unicast and multicast in the physical layer. The WTRU can reserve resources for multiple blind (re)transmissions or HARQ feedback-based (re)transmissions of transmission blocks, in which case the resources can be indicated in the (one or more) SCI(s) scheduling the transmission block. In another example, the WTRU can select resources for the initial transmission of a subsequent transmission block, in which case the resources can be indicated in the SCI scheduling the (e.g., current) transmission block. For example, the initial transmission of the transmission block can be performed after sensing and resource selection, e.g., in the absence of reservation.

[0108] The first-stage SCI transmitted by the WTRU on the PSCCH can indicate the time-frequency resources in which the WTRU can transmit the PSSCH. These SCI transmissions can be sensed by the WTRU to determine, e.g., which resources may have been reserved by other WTRUs in the recent past (e.g., maintain a record of which resources may have been reserved by other WTRUs in the recent past).

[0109] In one example, the sensing WTRU can select resources for its (one or more) (re)transmissions from a resource selection window (e.g., interval) (e.g., within the resource selection window (e.g., interval)). The window (e.g., interval) can start (e.g., soon) after the trigger for the (re)selection of resources and can not be longer than the remaining waiting time budget of the packet to be transmitted. Resources reserved in a selection window where the SL reference signal received power (RSRP) meets a condition (e.g., is above a threshold), where the condition (e.g., threshold) is set according to the priority of the traffic of any sensing and transmitting WTRU, can be excluded from the candidates by the sensing WTRU. For example, a higher-priority transmission from the sensing WTRU may occupy (e.g., use) resources that can be reserved by a transmitting WTRU with a lower sidelink reference signal received power (SL-RSRP) and lower-priority traffic.

[0110] Example of a bandwidth part

[0111] In a manner similar to uplink / downlink, bandwidth parts (BWPs) for SL can be considered in the WTRU RF hardware chain implementation. In the case where the WTRU is connected (e.g., in connected mode) to the gNB, the WTRU can be configured with an active SL BWP, which can be the same as the (e.g., single) SL BWP for any idle mode and out-of-coverage operations.

[0112] The subcarrier spacing used on SL can be provided in the SL BWP (e.g., pre-) configuration, from the same values and associated sets to the frequency ranges for the Uu interface (e.g., any 15 kHz, 30 kHz, and 60 kHz for FR1, and any 60 kHz and 120 kHz for FR2). The SL transmission and reception for the WTRU can be included within the SL BWP, and the same SL BWP can be used for any transmission and reception. For example, from the perspective of the WTRU, any resource pool and S-SSB can be included within the (e.g., appropriate) SL BWP.

[0113] Examples of NR and unlicensed NR (NR-U)

[0114] The 5G NR system can allow for connectivity expectations that meet a range of existing and future services that can be deployed in an efficient manner. For example, NR can consider supporting frequency ranges up to 100 GHz.

[0115] The NR specifications developed in Rel-15 and Rel-16 define the operation for frequencies up to 52.6 GHz, where all physical layer channels, signals, procedures, and protocols are designed for use below 52.6 GHz.

[0116] Compared to lower frequency bands, frequencies above 52.6 GHz may face more difficult challenges, such as higher phase noise, larger propagation losses due to high atmospheric absorption, lower power amplifier efficiency, and stringent power spectral density regulatory requirements in unlicensed bands. The frequency range above 52.6 GHz can contain larger spectrum allocations and larger bandwidths, which may not be available for bands below 52.6 GHz.

[0117] As a preliminary effort to enable and enhance 3GPP NR system operation above 52.6 GHz, 3GPP RAN has studied the requirements for NR up to 114.25 GHz beyond 52.6 GHz, including global spectrum availability and regulatory requirements (including channelization and licensing regimes), use cases and deployment scenarios, and NR system design considerations over and above regulatory requirements. Use cases identified in the study include high data rate eMBB, mobile data offloading, short-range high data rate device-to-device (D2D) communication, broadband distribution networks, integrated access backhaul (IAB), factory automation, industrial IoT (IIoT), wireless display transmission, augmented reality (AR) / virtual reality (VR) wearables, intelligent transport systems (ITS) and V2X, inter-rack connectivity in data centers, smart grid automation, private networks, and high positioning accuracy support. Use cases span several deployment scenarios identified in the study. Deployment scenarios include indoor hotspots, dense urban, urban micro, urban macro, rural, factory halls, and indoor D2D scenarios. The study also identified several system design attributes around waveform, MIMO operation, device power consumption, channelization, bandwidth, range, availability, connectivity, spectrum regime considerations, etc.

[0118] Frequencies between 52.6 GHz and 71 GHz may be of interest, for example, in the short term, as they are close to sub-52.6 GHz where current NR systems can be designed, and there are commercial opportunities for high data rate communication, e.g., unlicensed and licensed spectrum between 57 GHz and 71 GHz.

[0119] NR Rel-15 defines two frequency ranges for operation: a first frequency range from 410 MHz across to 7.125 GHz (which may be referred to herein as FR1); and a second frequency range from 24.25 GHz across to 52.6 GHz (which may be referred to herein as FR2).

[0120] The proximity of the 57 - 71 GHz frequency range to FR2 and the commercial opportunities for high data rate communication may make it compelling for 3GPP to address NR operation in this frequency region. FR2 operation has been extended by 3GPP up to 71 GHz, with one or more new numerologies (e.g., larger subcarrier spacing) that can be identified on the waveforms for NR above 52.6 GHz. Regarding operation in the unlicensed 60 GHz band, NR-U procedures for operation in unlicensed spectrum can be utilized. Considering licensed and unlicensed operation, NR operation can support up to 71 GHz. Similar to NR and NR-U operation below 52.6 GHz, NR / NR-U operation between 52.6 GHz and 71 GHz can be stand-alone or can be aggregated with an anchor carrier via carrier aggregation (CA) or dual connectivity (DC).

[0121] In Release-16 New Radio Unlicensed (NR-U), the supported numerologies (e.g., subcarrier spacing (SCS)) can be set to any one of 15 KHz, 30 KHz, and 60 KHz. In Release-16 NR-U, the Listen-Before-Talk (LBT) bandwidth can be set to 20 MHz. Based on the (e.g., minimum) LBT bandwidth that can be supported, for Rel-16 NR-U, the DL initial BWP can be 20 MHz. The supported channel bandwidth can be up to 100 MHz. The WTRU channel bandwidth (or the activated BWP) can be set to an integer multiple of the LBT bandwidth (e.g., 20 MHz). For example, for SCS = 30 KHz, the total allocated number of PRBs for 20 MHz, 40 MHz, and 80 MHz bandwidths can be equal to 48, 102, and 214 respectively.

[0122] In the unlicensed band, the WTRU can sense the channel before performing a transmission to determine whether the channel is available. Such a procedure is called Listen-Before-Talk (LBT). In Rel-16 NR-U, different LBT types (e.g., LBT type 1 channel access, type 2A channel access, type 2B channel access, etc.) can allow for supporting different scenarios (e.g., sensing intervals).

[0123] In the case where the energy level of the channel meets the condition (e.g., is below a defined threshold, e.g., LBT is successful), the WTRU can transmit during the duration of a time period herein referred to as the Channel Occupancy Time (COT). After the COT may have expired, the WTRU can perform LBT again before any further transmission.

[0124] Overview

[0125] NR Rel-18 will cover SL communication with FR1 unlicensed channel access (without beam management) and FR2 licensed operation with beam management. For mode 1, SL operation on the unlicensed spectrum can be considered in the case where Uu operation uses licensed spectrum and SL operation uses unlicensed spectrum. For mode 1, the embodiments described herein can allow for operating SL on the unlicensed spectrum, with Uu operation using the unlicensed spectrum and SL operation using the unlicensed spectrum (e.g., both).

[0126] In the case where the uplink / downlink and sidelink (e.g., transmission) (e.g., both) operate in an unlicensed band, the WTRU may perform channel access (e.g., sensing) on the uplink / downlink and sidelink (e.g., both) for SL mode-1 operation to complete the SL transmission scheduled by the base station via the uplink / downlink. For example, channel access (e.g., sensing) may be performed independently for Uu and SL. Due to the channel uncertainty on Uu and SL, and since the scheduler at the base station cannot arbitrarily receive feedback related to communication on the SL in a timely manner (such as, for example, any of a buffer status report (BSR), a scheduling request (SR), an SL HARQ feedback), and transmit scheduling information to the Tx WTRU in a timely manner, the SL scheduling of the gNB on the SL unlicensed frequency may be inaccurate and inefficient.

[0127] The embodiments described herein may improve the latency and system performance in the unlicensed band by increasing the channel access efficiency. Several mechanisms for channel access using COT sharing are described herein.

[0128] In the embodiments described herein, a method for a channel access procedure for operation on an unlicensed spectrum with unlicensed Uu and unlicensed SL (e.g., both) for SL mode 1 is described. The described method includes a channel access procedure with COT sharing initiated by the Tx WTRU, a channel access procedure with COT sharing initiated by the Tx WTRU using auxiliary information from the Rx WTRU, a channel access procedure with COT sharing initiated by the gNB, a channel access procedure with COT sharing initiated by the gNB using auxiliary information from the TxWTRU, a channel access procedure with COT sharing initiated by the gNB using auxiliary information from the Rx WTRU, and a channel access procedure with COT sharing initiated by the gNB using auxiliary information from the TxWTRU and the Rx WTRU.

[0129] In the embodiments described herein, the terms "auxiliary information" and "auxiliary information" may be used interchangeably to refer to an additional piece of information transmitted and / or used together with another piece of information.

[0130] A method for channel access for operating SL mode 1 on an unlicensed spectrum with Uu operation and SL operation (e.g., both) using the unlicensed spectrum is described herein.

[0131] Example channel access procedure with COT sharing initiated by the TxWTRU for SL unlicensed (SL-U) mode 1

[0132] In SL mode 1, the WTRU may receive authorization information from the gNB to perform SL transmission.

[0133] Figure 3 It is a diagram illustrating an example of SL mode 1 operation using dynamic scheduling.

[0134] In the first step, when the Tx WTRU 301 has some data to transmit, the Tx WTRU 301 may send first scheduling information 31 associated with an SL transmission (e.g., to be performed in an unlicensed SL). The first scheduling information 31 may indicate any SL scheduling request (SL-SR) and SL buffer status report (SL-BSR) to obtain (e.g., receive) authorization information from the gNB 300.

[0135] In the second step, after the gNB 300 may have received the first scheduling information 31 indicating either the SL-SR or the SL-BSR, the gNB 300 may transmit second scheduling information 32 to the Tx WTRU 301 by using a DCI (e.g., DCI format 3_0) indicating any one of the resource allocation for the SL transmission and other SL authorization related information.

[0136] In the third step, after receiving the second scheduling information 32 (e.g., DCI format 3_0) indicating the scheduling resources on the SL, the TxWTRU 301 may perform a scheduled (e.g., PSCCH and PSSCH) transmission 33 to the RxWTRU 302.

[0137] In the fourth step, the Rx WTRU 302 may monitor the transmissions of the PSCCH and the corresponding PSSCH. In the case where HARQ feedback is enabled for the PSSCH transmission, the Rx WTRU 302 may send HARQ feedback 34 to the Tx WTRU301 via the PSFCH by using the enabled HARQ scheme.

[0138] In the fifth step, after receiving the HARQ feedback 34 from the Rx WTRU 302, the Tx WTRU 301 may forward the HARQ feedback result 35 of the SL transmission to the gNB 300 by using the physical uplink control channel (PUCCH). For example, the gNB 300 may schedule subsequent resources for the SL transmission based on the HARQ feedback result 35 received from the Tx WTRU 301 (e.g., make a decision and).

[0139] In the case of operating in the sidelink-unlicensed (SL-U) mode 1 in unlicensed spectrum using Uu and sidelink (e.g., both), the WTRU may access (e.g., sense) the channels on the Uu interface and the PC5 interface (e.g., both) to perform transmissions. For example, channel access (e.g., sensing) may be performed on the Uu interface to transmit any one of (i) SL scheduling request information, (ii) SL buffer status report information, (iii) scheduling DCI, (iv) PUCCH information, etc. Channel access (e.g., sensing) may be performed on the PC5 interface to transmit any one of PSCCH information, PSSCH information, PSFCH information, etc.

[0140] It may be expected by rules that a transmission network element (e.g., gNB, WTRU, TxWTRU, Rx WTRU, etc.) performs channel access before performing a transmission on unlicensed spectrum (also referred to as shared spectrum). Channel access may include performing sensing for a (e.g., certain) period of time on the channel. Such behavior may be referred to as LBT in this document. In the case where the channel is sensed to be idle for at least one (e.g., certain) sensing interval (which may be referred to as LBT success), the transmission node may perform a transmission on unlicensed spectrum. In the case where the channel is sensed to be busy (e.g., not idle) (which may be referred to as LBT failure), the transmission node may not perform a transmission on unlicensed spectrum. Throughout the embodiments described in this document, LBT is used to describe the procedure of accessing the channel performed by the transmission network element. The embodiments described in this document are not limited to using LBT to perform channel access, and any other technique for accessing the channel in shared spectrum may be applicable to the embodiments described in this document. Throughout the embodiments described in this document, the terms "LBT", "channel sensing", and other notations of the channel access scheme may be used interchangeably.

[0141] According to an embodiment, the shared channel occupancy time (COT) may allow resolving channel uncertainty. For example, the COT may be initiated and may be shared by transmissions on the Uu interface and transmissions on the sidelink. Throughout the embodiments described in this document, the shared COT may refer to the COT that may be shared among any uplink, downlink, and sidelink transmissions in unlicensed spectrum, for example. For example, in the case where the COT is initiated by a network element, other network elements that may share the COT may initiate a transmission in the COT without LBT, e.g., channel access type 2C, or may initiate a transmission in the COT using short LBT, e.g., channel access type 2A with a sensing interval of 25 μs or channel access type 2B with a sensing interval of 16 μs, etc.

[0142] The SL WTRU and the base station can adapt the timing of their transmissions so as not to exceed any (e.g., configured) time and regulatory thresholds. In the case where a transmission is about to exceed any (e.g., configured) time and regulatory thresholds, the transmission network element can initiate a new independent channel access by performing a full LBT (e.g., using more time and increasing the risk of losing scheduled resources).

[0143] In one example, (e.g., restricted) COT sharing information can be combined with the SR for transmission in the PUCCH. This information can indicate to the gNB whether the gNB can share the COT initiated by the Tx WTRU. For example, (e.g., restricted) COT sharing information can indicate that the COT may have been initiated by the Tx WTRU and that the COT can be shared by the Tx WTRU and the gNB. In one example, (e.g., restricted) COT sharing information may not include explicit information indicating when the shared COT can start. For example, the shared COT can start from the transmission including (e.g., restricted) COT sharing information. In another example, (e.g., restricted) COT sharing information can include (e.g., explicit) information indicating when the shared COT can start. For example, (e.g., restricted) COT sharing information can indicate the duration of the COT. For example, the COT sharing information can be conditional on the channel access priority class used by the SL TxWTRU to initiate the COT.

[0144] The COT sharing information can indicate additional details regarding COT sharing, which can be included in, for example, a MAC control element (MAC CE). In one embodiment, the BSR information can include additional information elements indicating the COT, such as any one of, for example, the priority class, start time, remaining time, etc. In one embodiment, a (e.g., new) MAC CE can include information indicating COT parameters and a sharing indication (e.g., information). For example, the MAC CE can be transmitted by the SL Tx WTRU that initiated the COT to the gNB.

[0145] In one embodiment, the COT can be initiated by the Tx WTRU (e.g., the Tx WTRU for SL transmission).

[0146] Figure 4 is a diagram illustrating an example channel access procedure with COT sharing initiated by the Tx WTRU for an SL-U with unlicensed Uu and unlicensed SL.

[0147] As shown at 41, the Tx WTRU may perform LBT on the Uu and sidelink to gather channel availability information (e.g., to determine if the channel is available). Based on the LBT result, e.g., if the channel is determined to be available on either the Uu or the SL, the Tx WTRU may initiate a COT that may be shared by the Uu and the SL (e.g., both). In one example, if the channel is determined to be available on the Uu (e.g., only on the Uu), e.g., based on a successful LBT on the Uu (e.g., only on the Uu), the WTRU may initiate a COT to be shared by the Uu and the SL. In another example, if the channel is determined to be available on the Uu and the SL (e.g., both), (e.g., based on a successful LBT on the Uu and the SL (e.g., both)) the WTRU may initiate a COT to be shared by the Uu and the SL. For example, the Tx WTRU may perform LBT on the Uu and the SL (e.g., both) in parallel, e.g., to access (e.g., sense) the channel. In another example, the Tx WTRU may perform separate (e.g., sequential) LBTs on the Uu and the SL (e.g., one after the other) to access (e.g., sense) the channel.

[0148] For example, the Tx WTRU may send first scheduling information 42 to the gNB in the initiated COT, which indicates any one of (i) SL-SR, (ii) SL-BSR, and (iii) COT sharing information (e.g., indicating that the COT may be shared).

[0149] As shown at 43, the gNB may receive a transmission from the Tx WTRU and may determine that the COT may have been initiated by the Tx WTRU and that the COT may be shared by the Tx WTRU and the gNB for transmission on the Uu and the SL (e.g., both). For example, the gNB may schedule sidelink transmission in response to the first scheduling information 42 indicating either SL-SR or SL-BSR from the Tx WTRU within the initiated COT.

[0150] In another example, if the WTRU is configured with configured grants, the gNB may reply to an SR / BSR request by transmitting a short indication that may (re)activate the configured grant. The short indication may be prepared in a short time and transmitted within the same COT duration to avoid the gNB performing LBT.

[0151] For example, the gNB may transmit DCI 44 carrying (e.g., including) SL scheduling information to the Tx WTRU, e.g., after LBT may succeed. For example, the gNB may (e.g., directly) send DCI 44 that schedules SL transmissions (e.g., including SL scheduling information) on the Uu interface within the COT initiated by the Tx WTRU without performing LBT. In another example, the gNB may perform a short LBT, e.g., a type 2 channel access procedure, before transmitting (e.g., scheduling) DCI 44 to the Tx WTRU.

[0152] In the case where the dynamic grant DCI is used in conjunction with COT sharing, the time gap value in the DCI may refer to a new higher layer parameter (which may be referred to as sl-DCI-ToSL-Trans-unlicensed), and this new higher layer parameter may list (e.g., indicate) different series of time slot gap values, and thus may indicate a shorter time compared to the conventional sl-DCI-ToSL-Trans parameter.

[0153] As shown at 45, after receiving DCI 44, the Tx WTRU may check whether the scheduled SL transmission can be within the initiated COT. In the case where the scheduled SL transmission is determined to be within the initiated COT, the Tx WTRU may (e.g., directly) perform the SL transmission on the PC5 interface, e.g., without performing LBT. In another example, the Tx WTRU may perform a short LBT, e.g., a type 2 channel access procedure, before transmitting the scheduled (e.g., PSCCH and PSSCH) transmissions to the Rx WTRU.

[0154] For example, the Tx WTRU may transmit the scheduled (e.g., PSCCH and PSSCH) transmissions 46 to the Rx WTRU, e.g., within the COT.

[0155] In one embodiment, the Rx WTRU may transmit auxiliary information to the Tx WTRU to assist (e.g., aid) the Tx WTRU in initiating the COT.

[0156] Figure 5 FIG. illustrates an example channel access procedure with COT sharing initiated by the Tx WTRU for SL-U with unlicensed Uu and unlicensed SL using auxiliary information from the Rx WTRU.

[0157] As shown at 51, the Rx WTRU may perform LBT on the PC5 interface to collect channel availability information (e.g., to determine whether the channel can be available for SL transmission). For example, the Rx WTRU may determine whether it can send auxiliary information 52 to the Tx WTRU.

[0158] For example, in the case of successful LBT on the SL, the Rx WTRU may send auxiliary information 52 to the Tx WTRU. The auxiliary information 52 may indicate any one of (i) the start time when the channel becomes available, (ii) available candidate resources, (iii) the channel busy time, (iv) the channel available duration, (v) the channel busy ratio, and (vi) the available sub - band indicator to assist the gNB in performing SL scheduling. Throughout the embodiments described herein, the auxiliary information may be transmitted by a Tx network element (NE) (e.g., the Tx network element (NE) of the auxiliary information), which may be either the Rx WTRU of the SL transmission and the Tx WTRU of the SL transmission. Similarly, throughout the embodiments described herein, the auxiliary information may be received by an Rx NE, which may be either the Tx WTRU of the SL transmission and the gNB.

[0159] The start time when the channel becomes available may indicate the start time when the channel becomes available. For example, the Tx NE may predict when the channel may become available and may send information indicating the predicted time to the Rx NE. For example, the Tx NE may include time offset information in the auxiliary information to indicate the time offset between the start time of the available channel and the time when the auxiliary information is sent. In another example, the Tx NE may include information indicating any one of the frame index, sub - frame index, time - slot index, and symbol index in the auxiliary information to indicate the start time position of the available channel. In another example, the Tx NE may include a bitmap in the auxiliary information to indicate which time resources may be available. For example, one (e.g., each) bitmap may be associated with any one of a frame, a sub - frame, a time - slot, and a symbol. In another example, the Tx NE may send information indicating the time when the channel is available. For example, the Tx NE may send information indicating at which time within a past time window the channel is available. For example, the duration of the window may be configured by the gNB, e.g., via RRC signaling. The Tx NE may send information indicating which time resources within this window the channel is available to the Rx NE, e.g., via a bitmap, as the auxiliary information.

[0160] Available candidate resources can be indicated by the Tx NE as a set of candidate resources (e.g., subchannels with time slot indication) that can be estimated to be available for the base station. For example, an SL device (e.g., a WTRU) can listen (e.g., monitor) the SL to receive incoming transmissions that can be transmitted by other SL devices (e.g., WTRUs) operating in either mode 1 or mode 2. For example, the listening SL device (e.g., a WTRU) can derive (e.g., determine, estimate) which channel resources on the SL can become busy or available. This information can be combined with unlicensed SL channel availability to obtain available candidate resources (e.g., a list of available candidate resources) that can be expected (e.g., by the Tx WTRU) to be available for transmission. For example, channel monitoring for SL data reception can give an indication of reserved transmission time and frequency resources such that the WTRU can obtain available or unavailable times (e.g., a list of available or unavailable times) in a future time period.

[0161] The channel busy time can be indicated by the Tx NE as the time during which the channel may be continuously busy. For example, the Tx NE can indicate in the channel busy time the time during which the channel may have been continuously busy in a past time window. The duration of the window can be configured by the gNB, for example, via RRC signaling. The Tx NE can indicate to the Rx NE, for example, via a bitmap, etc., which time resources on the channel may have been continuously busy during this window as auxiliary information.

[0162] The channel available duration can be indicated by the Tx NE as the duration during which the channel (e.g., in the future) can be available. For example, the Tx NE can indicate to the Rx NE any one of a symbol duration, a time slot duration, a subframe duration, and a frame duration.

[0163] The channel busy ratio can be indicated by the Tx WTRU as the channel busy ratio in a past time window for the Rx NE, where the duration of the window can be configured by the gNB, for example, via RRC signaling. The channel busy ratio can be indicated as, for example, a percentage of the channel busy rate. For example, if the channel busy rate was X% in a past time window, then the value of X can be indicated. In another example, the channel busy ratio can be indicated as a quantized value, such as any one of 1 / 4, 2 / 4, 3 / 4, 4 / 4, etc. In yet another example, the channel busy ratio can be indicated as a channel busy level, such as any one of high, medium, low, etc., (e.g., which can be indicated by a value associated with the level).

[0164] The available sub - band indicator can be indicated by the TxNE as which frequency bands can be available for the RxNE. For example, for SL mode 1, the frequency bands (e.g., SL BWP) on which the WTRU can operate can be divided into one or more SL sub - bands. For example, one (e.g., each) SL sub - band can be associated with multiple bandwidths (e.g., 20 MHz). In another example, one (e.g., each) SL sub - band can be associated with multiple sub - channels, e.g., k sub - channels, where k can be an integer that can be configured by the gNB, e.g., via RRC signaling. The TxNE can indicate the available SL sub - bands to the RxNE. For example, a bitmap can be used to indicate which SL sub - bands among them (e.g., all of them) can be available.

[0165] In one embodiment, the transmission of (e.g., channel availability) assistance information can be triggered by (e.g., based on) the SL transmission to be performed, where the Rx WTRU is the destination WTRU or one of the destination WTRUs for the SL transmission. For example, in the case where the TxWTRU has data to be transmitted to the RxWTRU on the SL, the TxWTRU can send information indicating the trigger to the destination (e.g., Rx) WTRU to trigger the RxWTRU to transmit (e.g., channel availability) information to the TxWTRU. After receiving the information indicating the trigger from the TxWTRU, the RxWTRU can perform LBT on the SL and can transmit (e.g., channel availability) assistance information to the TxWTRU.

[0166] In one embodiment, the Rx WTRU can perform LBT on the SL periodically and can (e.g., periodically) transmit (e.g., channel availability) assistance information to the TxWTRU, e.g., regardless of whether there is an SL transmission intended for the RxWTRU. In this embodiment, the Tx WTRU may not send (e.g., to the Rx WTRU) information indicating the trigger for sending (e.g., channel availability) assistance information.

[0167] As shown at 53, the TxWTRU may use the assistance information received from the RxWTRU to initiate a COT that may be shared by Uu and SL (e.g., both). For example, the RxWTRU may initiate a COT to be shared by Uu and SL (e.g., both) based on the assistance information 52 received from the RxWTRU. For example, the TxWTRU may (e.g., only) perform sensing on Uu and may initiate a COT based on the assistance information 52 received from the RxWTRU (and e.g., based on the Uu channel sensing result). In another example, the TxWTRU may perform sensing on Uu and SL (e.g., both) and may initiate a COT based on the assistance information 52 received from the RxWTRU (and e.g., based on the Uu and SL channel sensing results). For example, the TxWTRU may perform one LBT on Uu and SL (e.g., both) in parallel, for example, to access (e.g., sense) the channel. In another example, the TxWTRU may perform separate (e.g., sequential) LBTs on Uu and SL (e.g., one after the other) to access (e.g., sense) the channel.

[0168] Figure 5 The steps labeled 55 and 57 may be similar to Figure 4 the steps labeled 43 and 45, respectively. Figure 5 The transmissions labeled 54, 56, and 58 may be similar to Figure 4 the transmissions labeled 42, 44, and 46, respectively.

[0169] Example of a channel access procedure with COT sharing initiated by the gNB for SL-U mode 1

[0170] In one embodiment, the COT can be initiated by the gNB. Based on this rule, the network element may not initiate a COT with an infinite length. Any gNB and WTRU can initiate a COT with a duration that can be up to 10 milliseconds. For example, after receiving scheduling information indicating either SL-SR or SL-BSR, the gNB may not (e.g., immediately) schedule an SL transmission. In the case of scheduling an SL transmission at a later time, e.g., at least 50 milliseconds after receiving the scheduling information, the SL transmission may fall outside of a COT that may have been initiated by the TxWTRU. The COT initiated by the gNB can allow the gNB to delay the scheduling of an SL transmission after receiving scheduling information (e.g., indicating either SL-SR or SL-BSR) and keep the SL transmission within the COT. For example, the gNB can initiate a COT when an SL transmission can be scheduled (e.g., transmitted). In another example, the gNB can initiate a COT when scheduling information (e.g., DCI) can be transmitted by the gNB to indicate when an SL transmission can be scheduled. By (e.g., appropriately) scheduling the SL transmission, e.g., keeping the gap (e.g., interval) between the scheduled SL transmission and the transmission of the DCI carrying the scheduling information below the (e.g., maximum) duration of the COT, the COT can be shared among more than one transmitting network element (e.g., gNB and WTRU).

[0171] For example, information indicating COT sharing, e.g., included in the DCI, can be transmitted from the gNB to the WTRU. For example, this information can indicate that the COT may have been initiated by the gNB and that the COT can be shared with the SL WTRU.

[0172] Figure 6 is a diagram illustrating an example channel access procedure with COT sharing initiated by the gNB for SL-U with unlicensed Uu and unlicensed SL (e.g., both).

[0173] In step 61, in the case where the Tx WTRU has data to transmit on the SL, the Tx WTRU can perform LBT on the Uu. For example, in the case of a successful LBT, the Tx WTRU can send first scheduling information 62 indicating either SL-SR or SL-BSR to the gNB.

[0174] In step 63, the gNB may perform LBT on either Uu or the sidelink to collect channel availability information (e.g., to determine whether the channel is available on either the Uu interface or the SL interface). Based on the LBT result, for example, if either the channel on Uu or the channel on SL is determined to be available, the gNB may initiate a COT that can be shared by Uu and SL (e.g., both). In one example, if the channel is determined to be available on Uu (e.g., only on Uu), for example, based on a successful LBT on Uu (e.g., only on Uu), the gNB may initiate a COT to be shared by Uu and SL. In another example, if the channel is determined to be available on both Uu and SL (e.g., both), (e.g., based on successful LBT on both Uu and SL (e.g., both)) the gNB may initiate a COT to be shared by Uu and SL.

[0175] For example, the gNB may transmit second scheduling information 64 (e.g., in DCI) to the Tx WTRU, where the second scheduling information 64 indicates either SL scheduling information or COT sharing information (e.g., indicates the shared COT). For example, the COT sharing information may indicate any one of a priority class, a start time of the shared COT, and a remaining time of the shared COT.

[0176] In step 65, the Tx WTRU may receive the second scheduling information 64 from the gNB. The Tx WTRU may determine that a COT may have been initiated by the gNB and that the scheduling of the sidelink transmission may be within the initiated COT (e.g., the TxWTRU may determine based on the second scheduling information 64 that the sidelink transmission can be scheduled in the initiated COT). The TxWTRU may determine that the COT initiated by the gNB can be shared by the TxWTRU and the gNB for transmissions on both Uu and SL (e.g., both). For example, the Tx WTRU may (e.g., directly) send the scheduled sidelink transmission to the Rx WTRU without performing LBT, for example, based on determining that the sidelink transmission may have been scheduled in the shared COT. In another example, the Tx WTRU may perform a short LBT, such as, for example, a type 2 channel access procedure, before transmitting the scheduled sidelink transmission to the Rx WTRU, for example, based on determining that the sidelink transmission may have been scheduled in the shared COT. For example, the TxWTRU may transmit the scheduled (e.g., PSCCH and PSSCH) transmission 66 to the Rx WTRU, for example, based on determining that the sidelink transmission may have been scheduled in the shared COT.

[0177] In one embodiment, the Tx WTRU may transmit assistance information to the gNB to assist the gNB in initiating a COT. For example, the following procedure (not illustrated) may be added to Figure 6 the steps described in

[0178] In step 61, the Tx WTRU (e.g., also) may perform LBT on the SL to collect channel availability information (e.g., to determine whether the channel is available on the SL). For example, the Tx WTRU may send auxiliary information to the gNB. For example, the auxiliary information may be included in the first scheduling information 62 (e.g., indicated by the first scheduling information 62). According to the embodiments described herein, the auxiliary information may indicate any one of, for example, channel available time, channel busy time, channel available duration, channel busy ratio, channel occupancy rate, and available sub - band indicator, etc. In step 63, the gNB may initiate COT based on (e.g., also based on) the channel availability (e.g., auxiliary) information reported by the Tx WTRU.

[0179] In one embodiment, the Rx WTRU may transmit (e.g., further) auxiliary information.

[0180] Figure 7 FIG. is a diagram illustrating an example channel access procedure with COT sharing initiated by the gNB for SL - U with unlicensed Uu and unlicensed SL using auxiliary information from the Rx WTRU.

[0181] In step 71, the Rx WTRU may perform LBT on the PC5 interface, e.g., to collect channel availability information. For example, the Rx WTRU may determine at which time it can transmit the first (e.g., channel availability) auxiliary information 72 to the Tx WTRU. For example, based on successful LBT on the SL, the Rx WTRU may send the first (e.g., channel availability) auxiliary information 72 to the Tx WTRU. For example, according to any of the embodiments described herein, the first (e.g., channel availability) auxiliary information 72 may indicate any one of the following information, such as, for example, channel available time, channel busy time, channel available duration, channel busy ratio, available sub - band indicator, etc. For example, the Rx WTRU may be triggered (e.g., requested) by the Tx WTRU (e.g., by receiving an indication information) to sense the SL and report the first (e.g., channel availability) auxiliary information 72 to the Tx WTRU. In another example, the Rx WTRU may periodically report the first (e.g., channel availability) auxiliary information 72 to the Tx WTRU.

[0182] In step 73, after receiving the first (e.g., channel availability) assistance information 72 from the Rx WTRU, the Tx WTRU may (e.g., directly) use it as assistance information and may send second (e.g., channel availability) assistance information to the gNB. For example, the Tx WTRU may not perform LBT on the SL to add additional assistance information. The Tx WTRU may (e.g., only) perform LBT on the Uu and may send second (e.g., channel availability) assistance information to the gNB based on the first (e.g., channel availability) assistance information 72 received from the Rx WTRU. In another example, the Tx WTRU may perform LBT on the Uu and SL (e.g., both). The Tx WTRU (e.g., also) may perform LBT on the SL and may update the first (e.g., channel availability) assistance information based on the SL LBT result. The Tx WTRU may send the updated first (e.g., channel availability) assistance information to the gNB based on successful LBT on the Uu interface. For example, the Tx WTRU may send information 74 indicating any one of SL-SR, SL-BSR, and second assistance information to the gNB based on successful LBT on the Uu interface.

[0183] In step 75, the gNB may perform LBT on the Uu and SL to collect channel availability information on the Uu and SL respectively. Based on either the LBT result reported by the Tx WTRU or the channel availability information, the gNB may initiate a COT that can be shared by the Uu and SL (e.g., both).

[0184] Figure 7 The step labeled 77 may be similar to Figure 6 the step labeled 65. Figure 7 The transmissions labeled 76 and 78 may be similar to Figure 6 the transmissions labeled 64 and 66 respectively.

[0185] Figure 8 is a diagram illustrating an example of SL-U mode 1 channel access with a WTRU-initiated Uu and SL shared COT. For example, as shown at 80, the WTRU may operate in SL mode 1 with a Uu in unlicensed spectrum and an SL in unlicensed spectrum (e.g., both).

[0186] In one example, as shown at 81, the Tx WTRU may have data to transmit on the SL. The Tx WTRU may perform channel access (e.g., sensing) on Uu and the SL. For example, the Tx WTRU may initiate a COT that can be shared on Uu and the sidelink (e.g., both), and may share the COT with the gNB. As shown at 82, the Tx WTRU may send scheduling information to the gNB, the scheduling information indicating any one of SL-SR, SL-BSR, and COT sharing information. As shown at 83, the Tx WTRU may monitor DCI. As shown at 84, the Tx WTRU may receive DCI indicating scheduling of one or more SL transmissions. As shown at 85, the Tx WTRU may determine whether the DCI indicates that one or more SL transmissions are scheduled within the COT. In the case where at least one SL transmission is scheduled within the COT, as shown at 861, the Tx WTRU may perform at least one SL transmission without LBT or with short LBT, otherwise, as shown at 862, the Tx WTRU may perform one or more SL transmissions with regular LBT.

[0187] In another example, the Tx WTRU may have data to transmit on the SL. The Tx WTRU may perform channel access (e.g., sensing) on Uu and the SL. For example, the Tx WTRU may initiate a COT that can be shared on Uu and the SL (e.g., both), and may share the COT with the gNB. The Tx WTRU may initiate the COT, for example, using (e.g., based on) assistance information received from the Rx WTRU. The Tx WTRU may send information indicating any one of SL-SR, SL-BSR, and COT sharing information to the gNB. The Tx WTRU may monitor and may detect DCI indicating, for example, scheduling of one or more SL transmissions within the COT. In the case where the DCI indicates that at least one SL transmission is scheduled within the COT, the Tx WTRU may perform an SL transmission without LBT or with short LBT.

[0188] Figure 9 is a diagram illustrating an example of SL-U mode 1 channel access with a gNB-initiated Uu and SL shared COT. For example, as shown at 90, the WTRU may operate in SL mode 1 with Uu and the SL (e.g., both) in unlicensed spectrum.

[0189] In one example, as shown at 92, the Tx WTRU may have data to transmit on the SL. For example, the Tx WTRU may perform channel access (e.g., sensing) on the Uu. The Tx WTRU may send first scheduling information indicating either the SL-SR or the SL-BSR to the gNB. As shown at 93, the Tx WTRU may monitor second scheduling information (e.g., DCI) transmitted, for example, by the gNB. As shown at 94, the Tx WTRU may detect (e.g., receive) the second scheduling information (e.g., DCI) that indicates either scheduling of the SL transmission or the COT sharing information. The Tx WTRU may check whether the SL transmission is scheduled within the COT shared by the gNB. In the case where the second scheduling information (e.g., DCI) indicates that the SL transmission is scheduled within the COT, as shown at 961, the Tx WTRU may perform the SL transmission without LBT or with short LBT. In the case where the second scheduling information (e.g., DCI) indicates that the SL transmission is scheduled after the COT, as shown at 962, the Tx WTRU may perform the SL transmission with regular (e.g., full) LBT.

[0190] In another example, the Tx WTRU may have data to transmit on the SL. For example, the Tx WTRU may perform channel access (e.g., sensing) on the Uu and on the sidelink. The Tx WTRU may send first scheduling information indicating any one of the SL-SR, the SL-BSR, and the auxiliary information to the gNB, and the first scheduling information may be used to assist the gNB in initiating the COT. For example, the Tx WTRU may monitor and detect (e.g., receive) second scheduling information (e.g., DCI) transmitted, for example, by the gNB, that indicates either scheduling of the SL transmission or the COT sharing information. For example, the Tx WTRU may check whether the second scheduling information (e.g., DCI) indicates an SL transmission scheduled within the COT shared by the gNB. In the case where the second scheduling information (e.g., DCI) indicates an SL transmission scheduled within the COT, the Tx WTRU may perform the SL transmission without LBT or with short LBT.

[0191] In yet another example, the Tx WTRU may have data to transmit on the SL. For example, the Tx WTRU may perform channel access (e.g., sensing) on the Uu. For example, the Tx WTRU may collect (e.g., receive) assistance information from the Rx WTRU. For example, the Tx WTRU may send first scheduling information indicating any one of the SL-SR, SL-BSR, and assistance information to the gNB, and this first scheduling information may be used to assist the gNB in initiating the COT. The assistance information sent to the gNB may be, for example, a combination of the assistance information received from the Rx WTRU and the sensing result of the Tx WTRU (e.g., based on the aggregation of the assistance information received from the Rx WTRU and the sensing result of the Tx WTRU). In another example, the assistance information sent to the gNB may be (e.g., purely) the assistance information received from the Rx WTRU and forwarded by the Tx WTRU to the gNB. For example, the Tx WTRU may monitor and detect second scheduling information (e.g., DCI) transmitted by the gNB, and this second scheduling information (e.g., DCI) indicates scheduling of either the SL transmission or the COT sharing information. The Tx WTRU may check whether the second scheduling information (e.g., DCI) indicates an SL transmission scheduled within the COT shared by the gNB. In the case where the second scheduling information (e.g., DCI) indicates an SL transmission scheduled within the COT shared by the gNB, the Tx WTRU may perform an SL transmission without LBT or with a short LBT.

[0192] Figure 10 FIG. is a diagram illustrating an example method 1000 for sharing a COT between a WTRU and a base station. Method 1000 may be implemented in the WTRU. As shown at 1010, the WTRU may transmit first scheduling information associated with an SL transmission to be transmitted in the unlicensed spectrum to another WTRU to the base station. As shown at 1020, the WTRU may receive second scheduling information from the base station indicating the scheduling of the SL transmission. As shown at 1030, the WTRU may determine whether an SL transmission can be scheduled in a channel occupancy time shared with any one of the uplink, downlink, and SL in the unlicensed spectrum. As shown at 1040, in the case where the SL transmission is scheduled in the shared channel occupancy time, the WTRU may transmit an SL transmission without listen-before-talk (LBT) or with an LBT shorter than a full LBT to another WTRU.

[0193] In various embodiments, the first scheduling information may indicate that the WTRU may have started a shared channel occupancy time.

[0194] In various embodiments, the first scheduling information associated with the SL transmission may indicate any one of an SL scheduling request, an SL buffer status report, and channel occupancy time sharing information.

[0195] In various embodiments, the channel occupancy time sharing information may indicate any one of a priority class, a start time of the shared channel occupancy time, and a remaining time of the shared channel occupancy time.

[0196] In various embodiments, the WTRU may further perform channel sensing on an unlicensed Uu (e.g., uplink) channel and an unlicensed SL channel, wherein, if the unlicensed Uu (e.g., uplink) channel and the unlicensed SL channel are determined to be available, first scheduling information may be transmitted (e.g., to a base station).

[0197] In various embodiments, before transmitting the first scheduling information, the WTRU may further receive auxiliary information indicating the availability of the SL channel from another WTRU.

[0198] In various embodiments, the shared channel occupancy time may be started based on the auxiliary information.

[0199] In various embodiments, the auxiliary information may indicate any one of (i) a channel available start time, (ii) available candidate resources, (iii) a channel busy time, (iv) a channel available duration, (v) a channel busy ratio, and (vi) an available sub-band indicator.

[0200] In various embodiments, the second scheduling information may indicate that the base station may have started the shared channel occupancy time.

[0201] In various embodiments, the second scheduling information may indicate any one of a priority class, a start time of the shared channel occupancy time, and a remaining time of the shared channel occupancy time.

[0202] In various embodiments, the WTRU may further perform a first SL channel sensing on an unlicensed SL channel to be used for SL transmission, wherein the first SL channel sensing may be performed before transmitting the first scheduling information (e.g., to a base station).

[0203] In various embodiments, the first scheduling information may indicate a first SL channel availability result obtained through the first SL channel sensing.

[0204] In various embodiments, the WTRU may further receive auxiliary information indicating a second SL channel availability result of a second SL channel sensing performed by another WTRU.

[0205] In various embodiments, the first scheduling information may further indicate the second SL channel availability result of the second SL channel sensing.

[0206] In various embodiments, the first scheduling information may indicate any one of (i) the start time when the channel is available, (ii) available candidate resources, (iii) the busy time of the channel, (iv) the duration for which the channel is available, (v) the channel busy ratio, and (vi) the available sub - band indicator.

[0207] In various embodiments, in the case where the SL transmission is scheduled after the shared channel occupancy time, the WTRU may further transmit an SL transmission with full LBT to another WTRU.

[0208] In various embodiments, the shorter LBT may include sensing over a sensing interval of 16 or 25 microseconds.

[0209] Figure 11 FIG. is a diagram illustrating an example method 1100 for sharing a COT between a WTRU and a base station, where the shared COT is initiated by the base station. Method 1100 may be implemented in the WTRU. As shown at 1110, the WTRU may transmit first scheduling information associated with a sidelink transmission to be transmitted to another WTRU in unlicensed spectrum to the base station. As shown at 1120, the WTRU may receive second scheduling information from the base station indicating the scheduling of the sidelink transmission and the shared channel occupancy time, where the shared channel occupancy time may be shared among any of the uplink, downlink, and sidelink transmissions in unlicensed spectrum. As shown at 1130, the WTRU may determine, based on the second scheduling information, that the sidelink transmission may be scheduled within the shared channel occupancy time. As shown at 1140, based on the determination that the sidelink transmission may be scheduled within the shared channel occupancy time, the WTRU may transmit a sidelink transmission to another WTRU without listen - before - talk or with a listen - before - talk shorter than full listen - before - talk.

[0210] In various embodiments, the first scheduling information associated with the sidelink transmission may indicate either a sidelink scheduling request or a sidelink buffer status report.

[0211] In various embodiments, the second scheduling information may indicate that the base station may have started the shared channel occupancy time.

[0212] In various embodiments, the second scheduling information indicating the shared channel occupancy time may indicate any one of a priority class, the start time of the shared channel occupancy time, and the remaining time of the shared channel occupancy time.

[0213] In various embodiments, the WTRU may perform a first sidelink channel sensing on an unlicensed channel to be used for sidelink transmission, where the first sidelink channel sensing may be performed before transmitting the first scheduling information to the base station.

[0214] In various embodiments, the first scheduling information may indicate a first sidelink channel availability result obtained based on a first sidelink channel sensing.

[0215] In various embodiments, before transmitting the first scheduling information, the WTRU may receive information indicating a second sidelink channel availability result of a second sidelink channel sensing from another WTRU.

[0216] In various embodiments, the first scheduling information may include auxiliary information based on either the first sidelink channel availability result or the second sidelink channel availability result.

[0217] In various embodiments, the auxiliary information may indicate any one of (i) a channel available start time, (ii) available candidate resources, (iii) a channel busy time, (iv) a channel available duration, (v) a channel busy ratio, and (vi) an available subband indicator.

[0218] In various embodiments, in a case where the sidelink transmission is scheduled after a shared channel occupancy time, the WTRU may transmit a sidelink transmission with full listen-before-talk to another WTRU.

[0219] Figure 12 FIG. 1200 is a diagram illustrating an example method 1200 for sharing a COT between a WTRU and a base station, the shared COT being initiated by the WTRU. Method 1200 may be implemented in the WTRU. As shown at 1210, the WTRU may transmit first scheduling information associated with a sidelink transmission to be transmitted to another WTRU in an unlicensed spectrum to the base station. The first scheduling information may indicate, for example, a shared channel occupancy time, which may be shared among any one of uplink, downlink, and sidelink transmissions in the unlicensed spectrum. As shown at 1220, the WTRU may receive second scheduling information from the base station, the second scheduling information indicating a scheduling of the sidelink transmission. As shown at 1230, the WTRU may determine, based on the second scheduling information, that the sidelink transmission may be scheduled in the shared channel occupancy time. As shown at 1240, based on determining that the sidelink transmission may be scheduled in the shared channel occupancy time, the WTRU may transmit a sidelink transmission without listen-before-talk or with a listen-before-talk shorter than full listen-before-talk to another WTRU.

[0220] In various embodiments, the first scheduling information associated with the sidelink transmission may indicate either a sidelink scheduling request or a sidelink buffer status report.

[0221] In various embodiments, the first scheduling information may indicate that the WTRU may have started a shared channel occupancy time.

[0222] In various embodiments, the first scheduling information indicating the shared channel occupancy time may indicate any one of a priority class, a start time of the shared channel occupancy time, and a remaining time of the shared channel occupancy time.

[0223] In various embodiments, the WTRU may perform a first sidelink channel sensing on an unlicensed channel for sidelink transmission, wherein the first sidelink channel sensing may be performed before transmitting the first scheduling information to the base station.

[0224] In various embodiments, the first scheduling information may indicate a first sidelink channel availability result obtained based on the first sidelink channel sensing.

[0225] In various embodiments, before transmitting the first scheduling information, the WTRU may receive information indicating a second sidelink channel availability result of a second sidelink channel sensing from another WTRU.

[0226] In various embodiments, the first scheduling information may include auxiliary information based on any one of the first sidelink channel availability result and the second sidelink channel availability result.

[0227] In various embodiments, the auxiliary information may indicate any one of (i) a channel available start time, (ii) available candidate resources, (iii) a channel busy time, (iv) a channel available duration, (v) a channel busy ratio, and (vi) an available sub-band indicator.

[0228] In various embodiments, in a case where the sidelink transmission is scheduled after the shared channel occupancy time, the WTRU may transmit a sidelink transmission with full listen-before-talk to another WTRU.

[0229] Any feature, variant, or embodiment described for the method is compatible with an apparatus device including an apparatus for processing the disclosed method; compatible with a device including a circuit including any one of a transmitter, a receiver, a processor, and a memory, the circuit being configured to process the disclosed method; compatible with a computer program product including program code instructions; and compatible with a non-transitory computer-readable storage medium storing the program instructions.

[0230] Although the features and elements are provided above in particular combinations, one of ordinary skill in the art will understand that each feature or element can be used alone or in combination with other features and elements. The present disclosure is not limited to the specific embodiments described in this application, which are intended to illustrate various aspects. Many modifications and variations can be made without departing from the spirit and scope of the invention, as will be apparent to those skilled in the art. Any element, act, or instruction used in the description of this application should not be construed as critical or essential to the invention unless expressly provided as such. Based on the foregoing description, functional equivalent methods and apparatuses within the scope of the present disclosure, in addition to the methods and apparatuses enumerated herein, will be apparent to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only by the terms of the appended claims and the full scope of equivalents thereto. It should be understood that the present disclosure is not limited to a particular method or system.

[0231] For simplicity, the foregoing embodiments have been discussed in terms of the terminology and structure of a device having infrared capabilities (i.e., an infrared transmitter and receiver). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic or non-electromagnetic waves (such as sound waves).

[0232] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "image" can refer to any one of a snapshot, a single image, and / or multiple images displayed on a time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote", and / or the term "head-mounted display" and its abbreviation "HMD" can represent or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any one of multiple embodiments of a WTRU; (iii) a device having wireless capabilities and / or wired capabilities (e.g., tetherable), which is particularly configured with some or all of the structure and functions of a WTRU; (iii) a device having wireless capabilities and / or wired capabilities that is configured with less than all of the structure and functions of a WTRU; or (iv) the like. Details of an example WTRU that can represent any WTRU described herein are provided. As another example, the various embodiments disclosed above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than a head-mounted display can be utilized and that the present disclosure and some or all of the various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other devices can include drones or other devices configured to stream information to provide an augmented reality experience. Figure 1A - 1D Details of an example WTRU that can represent any WTRU described herein are provided. As another example, the various embodiments disclosed above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than a head-mounted display can be utilized and that the present disclosure and some or all of the various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other devices can include drones or other devices configured to stream information to provide an augmented reality experience.

[0233] In addition, the methods provided herein can be implemented in a computer program, software, or firmware that is included in a computer-readable medium for execution by a computer or a processor. Examples of computer-readable media include electrical signals (transmitted via 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 disks (DVDs). A processor associated with the software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0234] Variations of the methods, apparatuses, and systems provided above are possible without departing from the scope of the present invention. Given the various embodiments that can be applied, it should be understood that the illustrated embodiments are merely examples and should not be regarded as limiting the scope of the appended claims. For example, the embodiments provided herein include a handheld device that can include or be used in conjunction with any suitable voltage source that provides any suitable voltage, such as a battery, etc.

[0235] In addition, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include a processor are mentioned. These devices can include at least one central processing unit (“CPU”) and a memory. In accordance with the practice of those skilled in the computer programming art, references to symbolic representations of actions and operations or instructions can be performed by various CPUs and memories. Such actions and operations or instructions can be referred to as being “executed,” “computer-executed,” or “CPU-executed.”

[0236] Those of ordinary skill in the art will understand that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a final transformation or reduction of the electrical signals and maintain the data bits in a memory location in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU and other processing of the signals. The memory location that maintains the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the above platforms or CPUs, and other platforms and CPUs can support the methods provided.

[0237] The data bits can also be maintained on a computer-readable medium, including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system readable by a CPU. The computer-readable medium can include cooperative or interconnected computer-readable media that are specifically present on a processing system or distributed among multiple interconnected processing systems, which can be local or remote to the processing system. It should be understood that the embodiments are not limited to the above memories, and other platforms and memories can support the provided methods.

[0238] In an illustrative embodiment, any operations, processes, etc. described herein can be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions can be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0239] There is little difference between the hardware and software implementations of aspects of the system. The use of hardware or software is generally (but not always, as in some cases the choice between hardware and software may become important) a design choice representing a cost-versus-efficiency tradeoff. There can be various means to implement the processes and / or systems and / or other technologies described herein (e.g., hardware, software, and / or firmware), and the preferred means can vary with the environment in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are of utmost importance, the implementer can choose a tool that is primarily hardware and / or firmware. If flexibility is of utmost importance, the implementer might choose a primarily software implementation. Alternatively, the implementer can choose some combination of hardware, software, and / or firmware.

[0240] The foregoing detailed description has set forth various embodiments of devices and / or processes using block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will recognize that each function and / or operation in such block diagrams, flowcharts, or examples can be implemented, individually and / or collectively, by a variety of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several parts of the subject matter described herein may be implemented by application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein may be equivalently implemented, in whole or in part, in integrated circuits as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and / or writing the code for the software and / or firmware would be well within the skill of one of ordinary skill in the art in light of this disclosure. Additionally, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed in a variety of forms as a program product, and that illustrative embodiments of the subject matter described herein apply regardless of the particular type of signal bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, etc., and transmission type media such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0241] Those skilled in the art will recognize that in the art, it is common to describe devices and / or processes in the manner set forth herein and then integrate the devices and / or processes so described into a data processing system using engineering practices. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally may include one or more of the following: a system unit enclosure, a video display device, memories such as volatile and non-volatile memories, processors such as microprocessors and digital signal processors, computing entities such as operating systems, drivers, graphical user interfaces, and applications, one or more interactive devices such as touchpads or screens, and / or a control system including feedback loops and control motors (e.g., feedback for sensing position and / or speed, control motors for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0242] The subject matter described herein is sometimes illustrated with different components included within or connected to different other components. It should be understood that such described architectures are merely examples and that in fact many other architectures can be implemented that achieve the same functionality. In a conceptual sense, any arrangement of components that achieve the same functionality is effectively "associated" such that the desired functionality can be achieved. Thus, any two components that are combined to achieve a particular functionality can be considered to be "associated" with each other such that the desired functionality is achieved, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered to be "operably connected" or "operably coupled" to each other to achieve the desired functionality, and any two components that can be so associated can also be considered to be "operably coupled" to each other to achieve the desired functionality. Specific examples of operable coupling include, but are not limited to, components that physically mate and / or physically interact and / or components that wirelessly interact and / or wirelessly communicate and / or components that logically interact and / or can logically interact.

[0243] Regarding the use of substantially any plural and / or singular terms herein, those skilled in the art can appropriately translate from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be set forth herein.

[0244] Those skilled in the art will understand that, generally, the terms used herein, particularly the terms used in the appended claims (e.g., the subject matter of the appended claims), are generally intended to be "open" terms (e.g., the term "comprising" should be interpreted as "comprising but not limited to", the term "having" should be interpreted as "having at least", the term "including" should be interpreted as "including but not limited to", etc.). Those skilled in the art will further understand that if the intention is to introduce a specific number of elements recited in the claim, such intention will be expressly recited in the claim, and if there is no such recitation, there is no such intention. For example, in a case where only one item is intended, the term "single" or similar language may be used. To aid understanding, the appended claims and / or the description herein may include the use of introductory phrases "at least one" and "one or more" to introduce the elements recited in the claim. However, the use of such phrases should not be construed as implying that the introduction of an element recited in a claim by the indefinite article "a" or "an" limits any particular claim containing such introduced element to embodiments including only one such recited element, even when the same claim includes an introductory phrase "one or more" or "at least one" as well as an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). This also applies to the use of definite articles to introduce elements recited in the claim. Further, even if a specific number of the introduced elements recited in the claim is expressly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited number (e.g., a bare recitation of "two recited elements" without further modifiers means at least two recited elements, or two or more recited elements). Additionally, in those cases where a convention similar to "at least one of A, B, and C, etc." is used, generally, such construction is intended to make those skilled in the art understand the convention (e.g., "a system having at least one of A, B, and C" will include, but not be limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In cases where a convention similar to "at least one of A, B, or C, etc." is used, generally, such construction is intended to make those skilled in the art understand the convention (e.g., "a system having at least one of A, B, or C" will include, but not be limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Those skilled in the art will further understand that any disjunctive word and / or phrase that actually represents two or more alternative terms, whether in the specification, claims, or drawings, should be understood as contemplating the possibility of including one of the terms, either term, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B".Furthermore, as used herein, the term "any" followed by a listing of multiple items and / or multiple categories of items is intended to include "any one," "any combination," "any plurality," and / or "any combination of a plurality" of the items and / or categories of items, either alone or in combination with other items and / or other categories of items. Furthermore, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "number" is intended to include any number, including zero. And the term "plurality" as used herein is intended to be synonymous with "multiple."

[0245] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0246] As will be understood by those skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also include any and all possible sub-ranges and combinations of sub-ranges thereof. Any listed range can be easily considered to fully describe and be able to divide the same range into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed here can be easily decomposed into a lower third, a middle third, and an upper third, etc. It will also be understood by those skilled in the art that all languages, such as "up to", "at least", "greater than", "less than", etc., include the recorded numbers and refer to the ranges that can be subsequently decomposed into sub-ranges as described above. Finally, as will be understood by those skilled in the art, the range includes each individual member. Therefore, for example, a group with 1-3 cells refers to a group with 1, 2 or 3 cells. Similarly, a group with 1-5 cells refers to a group with 1, 2, 3, 4 or 5 cells, etc.

[0247] Furthermore, the claims should not be read as limited to the order or elements provided unless so stated. Furthermore, the use of the term "means for..." in any claim is intended to refer to 35 USC ξ 112, 6 or means-plus-function claim format, and any claim without the term “means for…” is not so.

Claims

1. A wireless transmit / receive unit (WTRU) including a circuit, the circuit including any one of a transmitter, a receiver, a processor, and a memory, wherein, The circuit is configured to: transmit to a base station first scheduling information associated with a sidelink transmission to be transmitted in an unlicensed spectrum to another WTRU; receive from the base station second scheduling information indicating scheduling of the sidelink transmission and a channel occupancy time for sharing, wherein the shared channel occupancy time is shared among any of uplink, downlink, and sidelink transmissions in the unlicensed spectrum; determine, based on the second scheduling information, that the sidelink transmission is scheduled during the shared channel occupancy time; and transmit, based on determining that the sidelink transmission is scheduled during the shared channel occupancy time, a sidelink transmission to another WTRU that does not have listen-before-talk or has a listen-before-talk shorter than full listen-before-talk.

2. The WTRU according to claim 1, wherein The first scheduling information associated with the sidelink transmission indicates either a sidelink scheduling request or a sidelink buffer status report.

3. The WTRU according to any one of claims 1 and 2, wherein, The second scheduling information indicates that the base station has started the shared channel occupancy time.

4. The WTRU according to any one of claims 1 to 3, wherein The second scheduling information indicating the shared channel occupancy time further indicates any of a priority class, a start time of the shared channel occupancy time, and a remaining time of the shared channel occupancy time.

5. The WTRU according to any one of claims 1 to 4, wherein The circuit is configured to perform a first sidelink channel sensing on an unlicensed SL channel to be used for the sidelink transmission, wherein the circuit is configured to perform the first sidelink channel sensing before transmission of the first scheduling information to the base station.

6. The WTRU according to claim 5, wherein, The first scheduling information indicates a first sidelink channel availability result obtained based on the first sidelink channel sensing.

7. The WTRU according to any one of claims 1 to 6, wherein, The circuit is configured to receive, before transmission of the first scheduling information, information from another WTRU indicating a second sidelink channel availability result of a second sidelink channel sensing.

8. The WTRU according to claims 6 and 7, wherein, The first scheduling information includes auxiliary information based on any of the first sidelink channel availability result and the second sidelink channel availability result.

9. The WTRU according to claim 8, wherein The auxiliary information indicates any of (i) a channel available start time, (ii) available candidate resources, (iii) a channel busy time, (iv) a channel available duration, (v) a channel busy ratio, and (vi) an available subband indicator.

10. The WTRU according to any one of claims 1 to 19, wherein, The circuit is configured to transmit, in a case where the sidelink transmission is scheduled after the shared channel occupancy time, a sidelink transmission with full listen-before-talk to another WTRU.

11. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: transmitting to a base station first scheduling information associated with a sidelink transmission to be transmitted in an unlicensed spectrum to another WTRU; receiving from the base station second scheduling information indicating scheduling of the sidelink transmission and a shared channel occupancy time, wherein the shared channel occupancy time is shared among any of uplink, downlink, and sidelink transmissions in the unlicensed spectrum; determining, based on the second scheduling information, that the sidelink transmission is scheduled during the shared channel occupancy time; and Transmit a sidelink transmission to another WTRU without listen-before-talk or with a listen-before-talk shorter than full listen-before-talk based on determining that the sidelink transmission is scheduled during the shared channel occupancy time.

12. The method according to claim 11, wherein, The first scheduling information associated with the sidelink transmission indicates either a sidelink scheduling request or a sidelink buffer status report.

13. The method according to any one of claims 11 and 12, wherein, The second scheduling information indicates that the base station has started the shared channel occupancy time.

14. The method according to any one of claims 11 to 13, wherein, The second scheduling information indicating the shared channel occupancy time further indicates any one of a priority class, a start time of the shared channel occupancy time, and a remaining time of the shared channel occupancy time.

15. The method according to any one of claims 11 to 14, comprising performing a first sidelink channel sensing on an unlicensed channel to be used for the sidelink transmission, wherein, Perform the first sidelink channel sensing before transmitting the first scheduling information to the base station.

16. The method according to claim 15, wherein, The first scheduling information indicates a first sidelink channel availability result obtained based on the first sidelink channel sensing.

17. The method according to any one of claims 11 to 16, comprising receiving, from another WTRU, information indicating a second sidelink channel availability result of a second sidelink channel sensing before transmitting the first scheduling information.

18. The method according to claims 16 and 17, wherein, The first scheduling information includes auxiliary information based on any one of the first sidelink channel availability result and the second sidelink channel availability result.

19. The method according to claim 18, wherein, The auxiliary information indicates any one of (i) a channel available start time, (ii) available candidate resources, (iii) a channel busy time, (iv) a channel available duration, (v) a channel busy ratio, and (vi) an available subband indicator.

20. The method according to any one of claims 11 to 19, comprising transmitting, to another WTRU, a sidelink transmission with full listen-before-talk in the case where the sidelink transmission is scheduled after the shared channel occupancy time.

Images