TW201937974A - Co-existence for new radio (NR) operation in unlicensed bands - Google Patents

Abstract

A wireless transmit/receive unit (WTRU) may perform, during a first time interval, a first listen-before-talk (LBT) process. When the first LBT is successful, a second LBT during a second time interval having grant free (GF) physical uplink shared channel (PUSCH) resources may be performed. The second LBT may be based on a selected random number of resource listen interval (RLI) symbols. The WTRU may transmit, when measured energy of reference signals (RSs) during the random number of RLI symbols is less than a threshold, second RSs up to a remaining number of RLI symbols.

Description

Coexistence of new radio (NR) operations in unlicensed bands

Cross-reference to related applications

The present application claims the benefit of U.S. Patent Application Serial No. 62/630,542, filed on Feb. 14, the entire disclosure of which is hereby incorporated by reference. this.

In a wireless communication system, the network may separately schedule WTRUs for uplink (UL) transmission or communication by assigning separate time, frequency or code resources to each of the WTRUs. As part of the assignment of resources, an authorization may be sent to the WTRU for UL transmission. In addition to the assigned resources, the network can communicate the presence of one or more time or frequency resources and allow the WTRU to use each resource for UL transmission without authorization. This unauthorized configuration is sometimes required.

The network or wireless device can be configured to compare the energy level detected on the bandwidth or frequency band of the unlicensed or unlicensed wireless channel, frequency or resource with a predetermined energy or power threshold to determine Availability, which is used for Listening to Wait (LBT) operations. If the network determines that the channel is idle for a period of time, the channel is accessed. The network or wireless device can also detect the energy level in the resource listening interval (RLI) of one or more grant-free (GF) entity uplink shared channel (PUSCH) resources and the detected energy level The LBT procedure is performed by comparing the detected energy or power threshold to determine availability.

FIG. 1A is a diagram showing an exemplary communication system 100 in which the disclosed embodiments may be implemented. The communication system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 can enable multiple wireless users to access such content via sharing system resources including wireless bandwidth. For example, communication system 100 can use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA). ), single carrier FDMA (SC-FDMA), zero-tailed unique word discrete Fourier transform extended OFDM (ZT-UW-DFT-s-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and multiple filter banks Carrier (FBMC) and so on.

As shown in FIG. 1A, communication system 100 can include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, radio access network (RAN) 104, core network CN 106, 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. For example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as "station (STA)") may be configured to transmit and/or receive wireless signals, and may include user equipment (UE) , mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, mobile phones, personal digital assistants (PDAs), smart phones, laptops, small laptops, personal computers, wireless sensors, Hotspots or Wi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head mounted displays (HMDs), vehicles, drones, medical devices and applications (eg, remote surgery), industrial equipment, and applications (eg, Robots and/or other wireless devices operating in an industrial and/or automated processing chain environment), consumer electronic devices, devices operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c, 102d may be referred to interchangeably as UEs.

Communication system 100 may also include base station 114a and/or base station 114b. Each of the base stations 114a, 114b may be configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks (eg, CN 106, Internet 110) And/or any other type of device of network 112). For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNodeB, a local Node B, a local eNodeB, a next generation Node B (gNB), a new radio (NR) Node B, Site controllers, access points (APs), wireless routers, and more. While each base station 114a, 114b is depicted as a single component, it should be understood that the base stations 114a, 114b can include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104, and the RAN may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), or Following the node and so on. Base station 114a and/or base station 114b can be configured to transmit and/or receive wireless signals on one or more carrier frequencies known as cells (not shown). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of authorized and unlicensed spectrum. Cells may provide wireless service coverage for a particular geographic area that is relatively fixed or that may change over time. Cells can be further divided into cell sectors. For example, a cell associated with base station 114a can be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, that is, one transceiver for each sector in a cell. In an embodiment, base station 114a may use multiple input multiple output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and/or receive signals in a desired spatial direction.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via the null plane 116, where the null plane may be any suitable wireless communication link (e.g., radio frequency (RF), Microwave, centimeter wave, micron wave, infrared (IR), ultraviolet (UV), visible light, etc.). The empty intermediaries 116 can be established using any suitable radio access technology (RAT).

More specifically, as described herein, communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, to name a few. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 104 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA (W- CDMA) to establish an empty intermediate plane 116. W-CDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and/or High Speed Uplink (UL) Packet Access (HSUPA).

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), where the radio technology may use Long Term Evolution (LTE) and/or Advanced LTE (LTE-A) and/or Advanced LTA Pro (LTE-A Pro) are used to establish the null intermediaries 116.

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, where the radio technology may use NR to establish null interfacing 116.

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a variety of radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together (eg, using a dual connectivity (DC) principle). Thus, the null intermediaries used by the WTRUs 102a, 102b, 102c can be characterized by various types of radio access technologies, and/or communications sent to/from multiple types of base stations (e.g., eNBs and gNBs).

In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.11 (ie, Wireless High Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)). ), cdma2000, cdma 2000 1X, cdma 2000 EV-DO, temporary standard 2000 (IS-2000), temporary standard 95 (IS-95), temporary standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced data rate (EDGE) for GSM evolution and radio technology for GSM EDGE (GERAN) and the like.

For example, base station 114b in FIG. 1A may be a wireless router, a local Node B, a local eNodeB, or an access point, and any suitable RAT may be used to facilitate, for example, a business location, home, vehicle, campus, industrial facility Wireless connections in local corridors, such as air corridors (for use by drones) and roads. In one embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In still another embodiment, base station 114b and WTRUs 102c, 102d may use a cellular based RAT (eg, W-CDMA, cdma2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a microcell Meta or femtocell. As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Therefore, the base station 114b does not need to access the Internet 110 via the CN 106.

The RAN 104 can communicate with the CN 106, which can be 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. Any type of network. This material can have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, and operational requirements. The CN 106 can provide call control, billing services, location based services, prepaid calling, internet connectivity, video distribution, etc., and/or can perform high level security functions such as user authentication. Although not shown in FIG. 1A, it should be appreciated that RAN 104 and/or CN 106 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 or use a different RAT. For example, in addition to being connected to the RAN 104 using NR radio technology, the CN 106 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106 can also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include a circuit switched telephone network that provides Plain Old Telephone Service (POTS). Internet 110 may include the use of public communication protocols (such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP Internet Protocol suite). A globally interconnected computer network device system. Other networks 112 may include wired and/or wireless communication networks that are owned and/or operated by other service providers. For example, other networks 112 may include another CN connected to one or more RANs, where one or more RANs may use the same RAT or a different RAT as RAN 104.

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

FIG. 1B is a system diagram showing an exemplary WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/trackpad 128, a non-removable memory 130, and a removable Memory 132, power source 134, global positioning system (GPS) chipset 136 and/or other peripheral devices 138, and the like. It should be appreciated that the WTRU 102 may also include any sub-combination of the aforementioned elements while remaining consistent with the embodiments.

The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with the DSP core, a controller, a microcontroller , dedicated integrated circuit (ASIC), field programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), state machine, and so on. Processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although FIG. 1B depicts processor 118 and transceiver 120 as separate components, it should be understood that processor 118 and transceiver 120 can also be integrated into one electronic component or wafer.

The transmit/receive element 122 can be configured to transmit signals to or from a base station (e.g., base station 114a) via the null plane 116. For example, in one embodiment, the transmit/receive element 122 can be an antenna configured to transmit and/or receive RF signals. For example, in an embodiment, the transmit/receive element 122 can be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals. In still another embodiment, the transmit/receive element 122 can be configured to transmit and/or receive both RF and optical signals. It should be appreciated that the transmit/receive element 122 can be configured to transmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted as a single element in FIG. 1B, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) that transmit and receive radio signals via the null intermediate plane 116.

The transceiver 120 can be configured to modulate signals to be transmitted by the transmission/reception component 122 and to demodulate signals received by the transmission/reception component 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, transceiver 120 may include multiple transceivers that enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

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

The processor 118 can receive power from the power source 134 and can be configured to distribute and/or control power for other elements in the WTRU 102. Power source 134 may be any suitable device that powers WTRU 102. For example, the power source 134 may include one or more dry battery packs (such as nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-hydrogen (NiMH), lithium-ion (Li-ion), etc.), solar cells, and Fuel cells and more.

The processor 118 can also be coupled to a GPS chipset 136 that can be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. Additionally or alternatively to the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the null plane 116 and/or from two or more nearby base stations. The received signal timing determines its position. It should be appreciated that the WTRU 102 may obtain location information using any suitable positioning method while remaining consistent with the embodiments.

The processor 118 can also be coupled to other peripheral devices 138, where the peripheral devices can include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, peripheral device 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photo and/or video), a universal serial bus (USB) port, a vibrating device, a television transceiver, a hands-free headset, Bluetooth ® modules, FM radios, digital music players, media players, video game console modules, Internet browsers, virtual reality and/or augmented reality (VR/AR) devices, and activity tracking And so on. Peripheral device 138 can include one or more sensors. The sensor can be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, a position sensor, a proximity sensor, a temperature sensor, a time sensor, a geography Position sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors or humidity sensors.

The WTRU 102 may include a full-duplex radio for which some or all of the signals (e.g., associated with a particular subframe for UL (e.g., for transmission) and downlink (e.g., for reception) are received) Or the transmission can be parallel or simultaneous, and so on. Full-duplex radios may include reduced and/or substantially eliminated self-processing via hardware (eg, chokes) or via signal processing by a processor (eg, a separate processor (not shown) or via processor 118) Interference interference management unit. In an embodiment, the WTRU 102 may include a half-double for transmitting and receiving some or all of the signals (e.g., associated with a particular subframe for UL (e.g., for transmission) or downlink (e.g., for reception). Radio equipment.

FIG. 1C is a system diagram showing RAN 104 and CN 106, in accordance with an embodiment. As mentioned above, the RAN 104 may use E-UTRA radio technology on the null plane 116 to communicate with the WTRUs 102a, 102b, 102c. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include eNodeBs 160a, 160b, 160c, however it should be appreciated that the RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. Each eNodeB 160a, 160b, 160c may include one or more transceivers that communicate with the WTRUs 102a, 102b, 102c over the null plane 116. In one embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNodeB 160a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a.

Each eNodeB 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and/or DL, and the like. As shown in FIG. 1C, the eNodeBs 160a, 160b, 160c can communicate with each other via the X2 interface.

The CN 106 shown in FIG. 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as being part of CN 106, it should be understood that any of these elements can be owned and/or operated by entities other than the CN operator.

The MME 162 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for verifying the users of the WTRUs 102a, 102b, 102c, performing bearer activation/deactivation, and selecting a particular service gateway during the initial connection of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide control plane functionality for switching between the RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM and/or W-CDMA.

SGW 164 may be connected to each of eNodeBs 160a, 160b, 160c in RAN 104 via an S1 interface. The SGW 164 can typically route and forward user profile packets to the WTRUs 102a, 102b, 102c/user data packets from the WTRUs 102a, 102b, 102c. SGW 164 may perform other functions, such as anchoring the user plane during handover between eNBs, triggering paging when DL data is available to WTRUs 102a, 102b, 102c, and managing and storing the context of WTRUs 102a, 102b, 102c, etc. .

The SGW 164 can be coupled to the PGW 166, which can provide the WTRUs 102a, 102b, 102c with packet switched network (e.g., Internet 110) access to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. Communication.

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

Although the WTRU is described as a wireless terminal in Figures 1A through 1D, it should be appreciated that in certain exemplary embodiments such terminals may be used (e.g., temporarily or permanently) with a communication network. Wired communication interface.

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

A WLAN employing an Infrastructure Basic Service Set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface to a distributed system (DS) or another type of wired/wireless network that carries and/or carries traffic to the BSS. Traffic originating outside the BSS and to the STA may arrive via the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS can be sent to the AP for delivery to the respective destination. Traffic between STAs within the BSS may be sent via the AP, for example where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. Traffic between STAs within a BSS can be considered and/or referred to as point-to-point traffic. Point-to-point traffic can be sent between the source and destination STAs (eg, directly between them) using Direct Link Setup (DLS). In some exemplary embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within an IBSS or using an IBSS may directly communicate with each other. Here, the IBSS communication mode can sometimes also be referred to as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure operating mode or a similar mode of operation, the AP can transmit beacons on fixed channels (eg, primary channels). The main channel can have a fixed width (eg 20 MHz bandwidth) or a dynamically set width via messaging. The primary channel can be the operational channel of the BSS and can be used by the STA to establish a connection with the AP. In some exemplary embodiments, carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented (eg, in an 802.11 system). For CSMA/CA, STAs including APs (eg, each STA) can sense the primary channel. If a particular STA senses/detects and/or determines that the primary channel is busy, then a particular STA may fall back. One STA (eg, only one station) can transmit at any given time in the specified BSS.

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

Ultra High Throughput (VHT) STAs can support channels of 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide. A 40 MHz and/or 80 MHz channel can be formed by combining successive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two discrete 80 MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel encoding, the data can be passed through the segmentation parser, which splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing or time domain processing can be performed separately on each stream. This stream can be mapped on two 80 MHz channels and the data can be transmitted by a transmitting STA. At the receiver of a receiving STA, the above operations for the 80+80 configuration may be reversed and the combined material may be sent to the Media Access Control (MAC).

802.11af and 802.11ah support the next 1 GHz (GHz) mode of operation. Compared with the channel operation bandwidth and carrier used in 802.11n and 802.11ac, the channel operation bandwidth and carrier reduction in 802.11af and 802.11ah are reduced. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidth 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 an exemplary embodiment, 802.11ah may support meter type control/machine type communication (MTC), such as an MTC device in a macro coverage area. The MTC device may have certain capabilities, such as including limited capabilities to support (eg, only support) certain and/or limited bandwidth. The MTC device can include a battery and the battery life of the battery is above a threshold (eg, to maintain a very long battery life).

WLAN systems that support multiple channels and channel bandwidths (eg, 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and/or limited by STAs in all STAs operating in the BSS supporting the minimum bandwidth mode of operation. In the 802.11ah paradigm, even if the APs in the BSS and other STAs support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth modes of operation, support (eg, only support) 1 MHz mode is supported. STA (for example, an MTC type device), the main channel can be 1 MHz wide. Carrier sensing and/or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy (eg, because the STA in the 1 MHz mode of operation is transmitting to the AP), then the entire band can be considered busy even though most of the frequency bands remain space and available for use.

In the United States, the available frequency bands available for 802.11ah are from 902 MHz to 928 MHz. In Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. According to the country code, the total bandwidth available for 802.11ah is from 6 MHz to 26 MHz.

FIG. 1D is a system diagram showing RAN 104 and CN 106, in accordance with an embodiment. As described above, the RAN 104 can use the NR radio technology on the null plane 116 to communicate with the WTRUs 102a, 102b, 102c. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include gNBs 180a, 180b, 180c, but it should be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with the embodiments. Each gNB 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c via the null plane 116. In one embodiment, gNBs 180a, 180b, 180c may implement MIMO technology. Moreover, in an example, gNBs 180a, 180b, 180c may use beamforming to transmit signals to and/or receive signals from, WTRUs 102a, 102b, 102c. Thus, for example, gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a. In an embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, gNB 180a may transmit multiple CCs (not shown) to WTRU 102a. A subset of these CCs can be on the unlicensed spectrum, while the remaining CCs can be on the licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement Cooperative Multipoint (CoMP) technology. For example, the WTRU 102a may receive cooperative communications from the gNBs 180a and the gNBs 180b (and/or the gNBs 180c).

The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using communications associated with a scalable parameter numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing (SCS) may be different for different communications, different cells, and/or different portions of the wireless communication spectrum. The WTRUs 102a, 102b, 102c may use subframes or transmission time intervals (TTIs) having different or scalable lengths (eg, including different numbers of OFDM symbols and/or continuously varying absolute time lengths) to be associated with the gNBs 180a, 180b And 180c communicate.
[1]

The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c that employ independent and/or non-independent configurations. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may use signals in the unlicensed band to communicate with the gNBs 180a, 180b, 180c. In a non-independent configuration, the WTRUs 102a, 102b, 102c may communicate/connect with the gNBs 180a, 180b, 180c while communicating/connecting with another RAN (e.g., eNodeBs 160a, 160b, 160c). For example, the WTRUs 102a, 102b, 102c may implement the DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c. In a non-independent configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and/or throughput to serve the WTRU 102a, 102b, 102c.

Each gNB 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and/or DL, support network interception Cutting, implementing dual connectivity, implementing interworking between NR and E-UTRA, routing user plane data to user plane functions (UPF) 184a, 184b, and routing control plane information to access and mobility management functions (AMF) ) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, and 180c can communicate with each other via the Xn interface.

The CN 106 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possibly a data network (DN) 185a, 185b. While each of the foregoing elements is described as being part of CN 106, it should be understood that any of these elements can be owned and/or operated by other entities than the CN operator.

The AMFs 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, AMFs 182a, 182b may be responsible for authenticating users of WTRUs 102a, 102b, 102c, supporting network cuts (eg, handling different protocol data unit (PDU) conversations with different needs), selecting specific SMFs 183a, 183b, managing Registration area, termination of non-access layer (NAS) messaging, and mobility management. The AMFs 182a, 182b may use network cuts to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. For example, different network slices can be established for different usage scenarios, such as services that rely on ultra-reliable low latency communication (URLLC) access, relying on enhanced large-scale mobile broadband (eMBB) Accessed services, services for MTC access, etc. The AMFs 182a, 182b may provide non-third generation partnership project (3GPP) access technologies for use in the RAN 104 with other radio technologies (eg, LTE, LTE-A, LTE-A Pro, and/or, for example, WiFi). The control plane function that switches between other RANs (not shown).

The SMFs 183a, 183b can be connected to the AMFs 182a, 182b in the CN 106 via the N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 106 via the N4 interface. The SMFs 183a, 183b can select and control the UPFs 184a, 184b, and can configure traffic routing via the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU conversations, controlling policy enforcement and QoS, and providing downlink information notifications and the like. The PDU conversation type can be IP based, non IP based, Ethernet based and so on.

The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with a packet switched network (e.g., the Internet 110). Access to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices, the UPFs 184, 184b may perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU conversations, Handling user plane QoS, buffering DL packets, providing mobility anchoring, and more.

The CN 106 can facilitate communication with other networks. For example, CN 106 may include or may be in communication with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and/or wireless networks owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected via an N3 interface interfacing with UPFs 184a, 184b and an N6 interface between UPFs 184a, 184b and DNs 185a, 185b and via UPFs 184a, 184b Local DN185a, 185b.

In view of Figures 1A through 1D and corresponding descriptions of Figures 1A through 1D, one or more or all of the functions described herein in relation to one or more of the following may be performed by one or more emulation devices (not shown) To perform: WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b , DN 185 ab and/or any other device(s) described herein. These emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, these emulation devices can be used to test other devices and/or analog network and/or WTRU functions.

The emulation device can be designed to implement one or more tests on other devices in a laboratory environment and/or an operator network environment. For example, the one or more emulation devices may perform one or more or all of the functions to test other devices within the communication network while being implemented and/or deployed in whole or in part as part of a wired and/or wireless communication network. The one or more emulation devices may perform one or more or all of the functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device can be directly coupled to another device to perform testing, and/or can perform testing using over-the-air wireless communication.

One or more emulation devices may perform one or more functions including all functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation device can be used in a test lab and/or in a test scenario of a wired and/or wireless communication network that is not deployed (eg, tested) to perform testing of one or more components. The one or more emulation devices can be test devices. The emulation device may transmit and/or receive data using direct RF coupling and/or wireless communication via an RF circuit (eg, the circuit may include one or more antennas).

The Third Generation Partnership Project (3GPP) New Radio (NR) can be configured for URLLC, MTC, Large Scale (mMTC), eMBB, etc. communications. URLLC allows devices and machines to communicate with ultra-reliable, extremely low latency and high availability, making them suitable for vehicle communications, industrial control, factory automation, remote surgery, smart grid, security, public safety applications or emergency management, etc. . The MMTC can be applied to communications between devices that are low cost, large quantities, battery powered, etc., for applications such as smart metering, logistics, field sensors, body sensors, and the like. The eMBB can be an enhanced parameter such as data rate, delay, coverage, etc. for mobile broadband access.

In an unlicensed or unlicensed band, the gNB or WTRU may be configured for Listen-Ahead Waiting (LBT) operations prior to accessing unlicensed bands, channels, frequencies, resources(s), or codes, and the like. LBT operations may vary depending on the requirements of the unlicensed channel. In the example given here, the requirements for unlicensed channels may be set in part by entities such as regulators, governments, private, pseudo-government, military, or standard development organizations (SDOs). The LBT procedure may include a fixed or random duration interval in which the network device or WTRU listens to the medium or waits to access the medium, and if the energy level detected from the medium is greater than a threshold or limit, the gNB or WTRU will avoid transmission. Otherwise, the wireless device or network device can transmit after completing the LBT procedure.

In some configurations, the network device can infer one or more grant-free (GF) entity uplink shared channels (PUSCH) when the detected energy level is less than the detected energy or power threshold or limit. Resources are available and ready to communicate data or transport blocks (TBs) in the one or more GF PUSCH resources.

In the examples presented herein, LBT and Resource Listening Interval (RLI) sensing can be utilized together. The WTRU may also utilize a reference signal (RS) during the RLI to determine the use of another WTRU. The WTRU may also utilize the energy detected during the LBT operation or listening interval and discard the energy collected from one or more previously known resource elements or blocks.

The NR can be configured with parameter configurations with subcarrier spacing ranging from 15 kHz to 240 kHz. The basic subcarrier spacing can be 15 kHz, and other parameter configurations can have incremental subcarrier spacing multiplied by a power of two. An example of basic subcarrier spacing is provided in Table 1.
Table 1

The Physical Downlink Control Channel (PDCCH) may include one or more Control Channel Elements (CCEs). The number of CCEs may depend on the level of aggregation or predetermined parameters. The control resource set (CORESET) can be included in the frequency domain A resource block, which is given by a higher layer message or a parameter such as CORESET-freq-dom . CORESET can also include in the time domain Symbol, which is given by a higher layer message or a parameter such as CORESET-time-dur [1] . In some scenarios, a group-common (GC) PDCCH and a common PDCCH may be configured. The GC PDCCH can be configured by higher layer messages, radio resource control (RRC) messages, and the like. The common PDCCH may be used to provide system information and paging for WTRU groups, WTRU clusters or associated WTRUs within the area. The remaining system information (RMSI) and other system information (OSI) can be configured by the physical broadcast channel (PBCH).

The Physical Uplink Control Channel (PUCCH) can be configured for multiple formats. An exemplary format is provided in Table 2.
Table 2

Table 3 shows exemplary structures of symbols and time slots in various formats. The OFDM symbols in the time slot can be classified into a lower chain (denoted as D in Table 3), a variable (denoted as X in Table 3), or an upper chain (denoted as U in Table 3).
table 3

For unlicensed or unlicensed bands, channels, frequencies, resources or codes, etc., LBT may be desirable. In some configurations, Category 1 (CAT1) operations may not have a listening interval, Category 2 (CAT2) may have a fixed duration listening interval, and Category 3 (CAT3) may have a random duration listening interval with a fixed contention window. Or Category 4 (CAT4) may have a random duration listening interval of increasing contention windows, and the like. For LBT CAT4, a network device or WTRU or the like may want to transmit control information or data in an unlicensed or license-free channel. The apparatus may perform an initial clearance channel assessment (CCA), wherein the apparatus may determine whether the channel is idle for a period of time, a time interval, or a fixed period of time and a sum of pseudo-random durations, and the like. The availability of a channel or one or more resources can be determined by comparing the detected energy level (ED) across the bandwidth or frequency band of the unlicensed channel or frequency to an energy or power threshold. This energy or power threshold can be determined by an entity such as a regulatory agency, government, private, pseudo-government, military, or Standard Development Organization (SDO).

If the channel is idle or available, communication, or transmission can begin, proceed or continue. If not, the device can perform a random back-off procedure in which random numbers can be selected from a specified interval, contention window, and the like. Once the backoff countdown is obtained, the device can determine if the channel is verified to be idle and can initiate transmission when the backoff counter reaches zero or near zero. If the network device gains access to the channel, it can be allowed to transmit duration, interval or channel occupancy time (COT), and the like. Communication or transmission can then occur for a limited duration, maximum COT (MCOT) or opportunity time, and the like. A CAT4 LBT program with random fallback and variable contention window size may be the desired channel access and coexistence configuration with Wi-Fi, 802.11x, LTE, other RATs, or other LAA networks.

The carrier bandwidth portion may be a set of contiguous physical resource blocks that are selected from a contiguous subset of common resource blocks for a given parameter configuration on a given carrier or the like. In some configurations, a WTRU may be configured with up to four carrier bandwidth portions (BWPs) in a DL, where a single DL carrier BWP is active at a given time. The WTRU may not be expected to receive an entity downlink shared channel (PDSCH), PDCCH, channel state information reference signal (CSI-RS), or timing reference signal (TRS), etc., outside of the active BWP. In some configurations, the WTRU may be expected to receive PDSCH, PDCCH, CSI-RS or TRS, etc. in an active BWP.

A WTRU may be configured with up to four carrier BWPs in a UL, where a single UL carrier BWP is active at a given time. If the WTRU is configured with a secondary UL, the WTRU may be configured with up to four carrier BWPs in the secondary UL, where a single secondary UL carrier BWP is active at a given time. In some configurations, the WTRU may not transmit PUSCH or PUCCH outside of the active BWP, or the WTRU may transmit PUSCH or PUCCH in the active BWP.

Two Demodulation RS (DM-RS) configurations can be used for the OFDM waveform to multiplex multiple antennas in the downlink. For some configurations, in the uplink, each layer of each transmitting WTRU may be considered an antenna. In configuration 1, a DM-RS corresponding to one antenna 可以 can be transmitted in every other subcarrier. A DM-RS corresponding to another antenna 可以 may be transmitted on the same subcarrier, but the two DM-RSs sharing the subcarrier may be applied by applying different cyclic shifts to the same parent sequence or seed sequence produce. If there are additional OFDM symbols, a time domain extension can be used to increase the number of antenna turns to four. Another set of 4 antennas can be supported on unused subcarriers to produce 8 orthogonal antennas on 2 OFDM symbols. For example, the DM-RS coefficients corresponding to 4 antennas on 2 OFDM symbols can be:
Antenna 埠1:
Antenna 埠 2:
Antenna 埠3:
Antenna 埠 4:
among them as well as Is the kth coefficient from two different parent sequences, as well as Is a cyclic shift parameter, and Is the length of the sequence. In the case of DFT-s-OFDM waveforms, a combination of cyclic shift and time domain extension can be used for multiplex antennas.

In configuration 2, time domain and frequency domain spreading can be used to multiplex up to 4 antennas on two adjacent subcarriers and two OFDM symbols. In this configuration, cyclic shifting of the sequence may not be used. For example, the DM-RS coefficients corresponding to 2 subcarriers and 4 antennas on 2 OFDM symbols may be:
Antenna 埠1:
Antenna 埠 2:
Antenna 埠3:
Antenna 埠 4:
among them It is a DM-RS coefficient, and the first pair may represent transmission coefficients on two adjacent sub-carriers, and the second pair may represent transmission coefficients on two adjacent OFDM symbols. In configuration 2, the WTRU may use 2 of the 6 subcarriers to generate a total of 12 orthogonal antennas on 2 OFDM symbols.

For OFDM waveforms, the DM-RS can be generated by QPSK modulation of a pseudo-random (PN) sequence, which can be a Gold sequence of length 31. For different antennas, the initialization of the second m-sequence can be different, resulting in a different sequence. Thus, depending on the initialization of the shift register that generated the PN sequence, the PN sequences used by the two WTRUs may be similar or different.

When a new radio unlicensed (NR-U) device attempts to access an unlicensed or unlicensed channel, frequency, resource(s) or code, it can compete with the inter-RAT device and the intra-RAT device for access. The type and density of inter-RAT devices may depend on unlicensed channels and may be devices such as Wi-Fi, 802.11x, LTE LAA, or Bluetooth. The intra-RAT device may be other NR-U, unlicensed LTE, or a device such as a WTRU, network device, or gNB. For example, for an NR-U WTRU, the intra-RAT device may be another NR-U WTRU connected to the same gNB or NR-U gNB, or a WTRU not associated with the same gNB. Both the inter-RAT device and the intra-RAT device may be sources of interference or noise.

In attempting to access an unlicensed channel by an NR-U WTRU, gNB, or other device, fair competition or coexistence with inter-RAT devices and intra-RAT devices may be desirable. For fair competition or coexistence, the wireless device may need to perform the LBT operation for a duration before accessing the unlicensed channel, frequency, resource(s) or code, and the like. In some configurations, if the energy is less than a threshold during this time, the wireless device can be allowed to transmit in the wireless channel for a maximum duration.

The NR-U device can interact differently with inter-RAT and intra-RAT devices. For coexistence between inter-RAT devices, the presence or activity perception of inter-RAT devices can be achieved by measuring the level of energy radiated by these devices. In the LBT paradigm, the NR-U device can listen to the channel for a period of time, and if no energy exceeding the threshold is detected, the NR-U device can be allowed to transmit in the wireless channel for a maximum duration or interval. In order to coexist with the intra-RAT device, although the energy-detection-based LBT can be configured, such a program can be executed more efficiently or robustly because the competing device may also know other waveforms.
[1]

For NR-U devices, the contention devices in the unlicensed band may be classified as: inter-RAT devices; NR-U gNBs, NR-U WTRUs or intra-RAT devices belonging to the competing entity or operator; and belonging to the same entity or Operator's NR-U gNB, NR-U WTRU or intra-RAT device, etc. For inter-RAT devices, the device can primarily use energy detection to detect the use of unlicensed channels. For NR-U gNBs or WTRUs belonging to a competing entity or operator, the detection of the use of non-privileged channels can be performed by detecting some NR-U communications (eg, channel bandwidth or carrier spacing) within similar parameter configurations. Measurement. For NR-U gNBs or WTRUs belonging to the same entity or operator, the detection of the use of the unlicensed channel can be similarly performed by detecting some NR-U traffic within a similar parameter configuration. In addition, such NR-U gNBs can cooperate with each other to enhance channel sharing by exchanging some information with each other, such as the load of each NR-U gNB, the urgency of channel access, and the channel priority between these NR-U gNBs. And so on.

Figure 2 is an example of channel occupancy time (COT) for a new radio unlicensed (NR-U) operation 200. In 200, each PUSCH may be authorized (GB), configured with an authorization, or GF, etc., and the NR-U network device may access the LBT program or operation after successfully executing on the network side. aisle. A network device that establishes or configures a COT can compete with an inter-RAT device or other NR-U device. An NR-U WTRU that is connected or coupled with an NR-U gNB that has established a COT may also compete with a peer NR-U WTRU that is connected or coupled to the same gNB. Once the COT is established, the WTRU may be configured for transmission.

A PUSCH for GB access may be assigned to a particular WTRU that is notified via a previous PDCCH, short PDCCH (sPDCCH) or control channel, and the like. For this configuration, the WTRU may not compete with other WTRUs that are connected to the network device or gNB or the like. In this configuration, the WTRU may perform a persistently fixed duration of the LBT, such as a CAT2 device, or perform an LBT with a random backoff or delay, such as a CAT3 or CAT4 device. However, if the channel is not idle and the LBT is unsuccessful, the WTRU may not be able to transmit at the PUSCH resource(s) or resource block (RB) assigned to the GB access. Therefore, the resource(s) may not be used, which may be undesirable or inefficient.

The GF access may also be configured for PUSCH to which multiple WTRUs are assigned. The GF access may be notified to one or more WTRUs via RRC configuration, RRC messaging, higher layer signals, or previous PDCCH or the like. For such a configuration, since the WTRU may compete with other WTRUs that are connected or coupled to the network device, it may be necessary or desirable for the LBT to interact with external competitors (eg, inter-RAT devices and RAT devices that are not connected to the same network device) And internal competitors (eg, WTRUs that are also allowed to use GF resources) coexist. In the LBT, at least one WTRU may successfully perform LBT and take the opportunity to transmit on PUSCH resources assigned for GF communication or transmission. However, after a successful LBT procedure, more than one WTRU may also attempt to transmit on the GF or (one or more) resources configured to be authorized, resulting in collisions, collisions, contention, and the like.

The examples presented herein can balance the efficiency, collision risk, contention, or conflict of UL channel access in one or more GF resources. In some examples, a two-stage or two-step LBT program can be configured. The device may first perform an LBT that requires supervision so that fair coexistence with other RAT devices can be achieved. The WTRU may perform this portion of the LBT procedure with a fixed or predetermined listening interval. It is also possible to configure an LBT class or configuration with a variable length. When the WTRU attempts to use a GF or GB interval with a variable length listening interval, the WTRU may calculate the listening interval in advance so that the WTRU may perform an energy detection procedure basic before attempting to utilize the GF or GB uplink resource(s). The listening interval continues on.

FIG. 3 is another example of a COT for NR-U operation 300. In 300, each PUSCH can be configured as a GF. Each GF PUSCH resource may be configured with a listening interval or RLI or the like before or substantially at the beginning of the resource(s), which may be one or more OFDM symbols (OS). In one example, one of a plurality of NR-U WTRUs connected to the same network device and configured to access the same GF resource(s) may eventually access the GF resource(s) while Collision (or one or more) collisions with other WTRUs are avoided. In 300, the network device can access the channel after successfully executing the LBT program or operation.

The RLI may include one or more symbols or have a frequency duration similar to the PUSCH resource(s). The size of the RLI can vary from one resource to another and can be determined by the network device. A WTRU configured to access the GF resource(s) may also be configured with an RRC configuration, an RRC message, an RRC message, a higher layer message, a DCI indication, or a COT indicator configured before or at the beginning of the COT. The size of the RLI. The COT indicator may indicate the size of each RLI, the size of the RLI of each GF resource group, or the size of the RLI of one or more GF resources within the COT, and the like. The size of the RLI may be based on how many WTRUs are configured to attempt to use the GF resource(s), or the WTRU is configured to use the duty cycle(s) of the resource(s), and the like. In an example, since the duration of the time slot can be 14 symbols and the duration of the PUSCH resource can also be up to 14 symbols, the duration of the RLI can be adjusted or managed to keep the LBT program valid or robust.

Figure 4 is an example of GF PUSCH resources including one or more listening intervals. In 400, the listening interval can include one or more OFDM symbols. The number of OFDM symbols can be indicated by RLI 402. A WTRU configured to access GF resource(s) may attempt to perform energy or power detection at the beginning or beginning of the RLI. The initial portion of the RLI selected for sensing may substantially reach the entire duration of the RLI, such as up to X RLI OFDM symbols. The WTRU may randomly select a number from 0 to RLI, which is represented as an RLI _WTRU . In configuration, the RLI _WTRU may select from {0, 1, 2, ..., RLI}. The WTRU may detect energy or power levels within the RLI _WTRU interval and may compare the detected energy to a threshold ED _GFBW . If the detected energy is less than a threshold, the WTRU may determine that the GF resource(s) are available and are ready to transmit pending or new data or TB on the GF resource(s).

The threshold or limit can be scaled according to the bandwidth of the RLI or the bandwidth of the GF PUSCH, and the like. For example, if a symbol and the LBT threshold for the specified BW _Portion are ED _BWP , the threshold for a given RLI can be determined by Equation 1:
ED _GFBW = (L × GFBW/BW _Portion ) × ED _BWP Equation 1
Where GFBW is the bandwidth of the GF resource(s), and RLI and BW _Portion are the bandwidths of the portions configured for the WTRU. Thus, in some configurations, a WTRU performing LBT on the GF resource(s) can compare the energy or power collected from the L OFDM symbols and compare it to the ED _GFBW . If ED _BWP is expressed in dBm, Equation 2 can be:
ED _GFBW (dBm) = 10 × log ₁₀ (L × GFBW/BW _Portion ) + ED _BWP (dBm). Equation 2

In some configurations, the WTRU may use cyclic prefix detection or the like to perform resource sensing using energy or power detection across the bandwidth of the RLI for the duration of the L symbols. The WTRU may attempt to detect the presence of a cyclic prefix by performing correlation or autocorrelation of the received signal for the bandwidth of the RLI (using a delayed version of the same signal). The amount of delay can be obtained from the parameter configuration and the length of the cyclic prefix. For example, if the OFDM symbol duration is T _OFDM and the duration of the cyclic prefix is T _CP , the delay may be equal to T _OFDM + T _CP . In some configurations, the WTRU may choose to monitor multiple parameter configurations or multiple cyclic prefix lengths and compare the energy to a scaled version of ED _GFBW .

For a WTRU listening interval configured as length L, energy, power or signal detection of the beginning portion of the GF resource(s) for that duration may be performed. If the detected energy or power level is less than a threshold or limit, the WTRU may assume that the GF resource(s) are available and may be ready to transmit data or TB in the GF resource(s). The WTRU may prepare pending data or TB for the remainder of the RB and include the remaining symbols for the RLI for communication or transmission. In some configurations, due to time constraints, the WTRU may not be able to prepare pending data or TB for the remainder of the resource block, or there may be redundancy value (RV) ambiguity such that the network device may not be able to decode the data or TB. In this case, the WTRU may send signals, reserved signals, RSs, DM-RSs, etc. for the remaining symbols of the RLI. After the signal or the reserved signal, the WTRU may transmit the prepared pending data or TB during the remainder of the resource block, which may be part of the resource block excluding the RLI. The reserved signal, signal, RS or DM-RS may be a preparation symbol for the bandwidth of the GF resource(s), or it may be any signal but with the GF resource(s) with the WTRU Power similar to that that can be used during transmission.

The WTRU may be configured to select or configure a communication or transmission operation by the network after the listening interval. In some configurations, the network device may not attempt to detect any signals during RLI. In some configurations, the network device can attempt to detect signals and TBs from the first symbol of the RLI. In some configurations, the WTRU may choose a value of zero for the listening interval L, which may result in the (one or more) to-be-processed TBs being sent without any resource sensing. Here, the WTRU may randomly select the listening interval L = 0. A zero duration listening interval or no resource sensing may occur before the start of the (one or more) GF resources. In some configurations, this can occur far enough in advance so that the WTRU has time to prepare for transmission.

The WTRU may be configured to select a listening interval L = 0 due to a higher or lower priority given by the network to the WTRU, or the WTRU may be configured to use the resource(s) in GB. In this configuration, the network device or gNB can assign the resource(s) to both GB and GF operations, wherein if the WTRU configured to use the zero duration listening interval has pending data or TB and begins at Between the resource(s) being transmitted, other WTRUs configured to use the non-zero duration listening interval may defer communication or transmission. Other WTRUs configured to use a non-zero duration listening interval may have an opportunity if the WTRU is configured to use a zero duration listening interval without pending data or TB and not transmitting any signals in the resource(s) Use (one or more) resources. This may allow for GF and GB hybrid operation where a higher priority WTRU, or URLLC WTRU may be given a zero duration listening interval, L = 0, while other WTRUs with GF configuration may be allowed to select a non-zero listening interval , for example, a value from 1 to D.

The network device or gNB may configure a specific or custom listening interval for the _WTRU , assign a predetermined value for the RLI _WTRU to each WTRU, set a prioritization order between the WTRUs, and the like. A _WTRU with RLI _WTRU = 0 may be assigned the highest priority. A _WTRU configured with a smaller RLI _WTRU value may take precedence over a larger RLI _WTRU value. After a successful LBT, if other WTRUs with smaller RLI _WTRU values do not transmit during the resource(s), the WTRU may transmit during the GF PUSCH. Referring again to Figure 4, the GF can span several NR time slots. In some configurations, a single RLI may also act as a listening interval for GF UL or PUSCH resources (one or more) that span more than one time slot. This can be advantageous because the listening interval can be increased over the entire duration of the uplink resource(s).

Figure 5 is another example of GF PUSCH resources including one or more listening intervals. The listening interval can resolve contention for this resource and subsequent GF resources (which may or may not be contiguous, sequential, etc.). For example, the RLI 502 at the beginning of the GF PUSCH or the UL resource(s) may act as a listening interval for multiple consecutive GF PUSCH or UL resources 504. In K-repetition GF communication or transmission, the RLI at the beginning of the first resource may act as a listening interval for K consecutive GF PUSCH or UL resources. The WTRU performing the second step of the LBT and winning the contention may continue to transmit for the next K-1 GF resources according to the K repetition GF PUSCH or UL. This can happen within the same COT and after the first part of the LBT succeeds.

In 500, the WTRU may perform a first step of LBT (eg, a CAT 1-4 based LBT procedure) and use the RLI to perform a second step of LBT at the beginning of the first resource, and for the next K-1 The WTRU may skip the first step and/or the second step of performing the LBT. Thus, in some configurations, only the first step of the LBT according to the LBT category may be performed, which may be the same as the LBT procedure performed in the first step for the first resource, or may be, for example, CAT1 and CAT2 Fixed duration LBT program. In some configurations, for example, because the energy detected during the listening interval within the RLI is above a threshold, the WTRU may perform the second step of the LBT for the first resource without winning contention. For this scenario, the WTRU may not attempt to access the next K-1 GF resources and may wait for the next set of K GF resources for transmission. In other configurations, the WTRU may attempt the second step of the LBT before any of the K GF resources until one of the GF resources (ie, the i-th resource) succeeds, but not the remaining K-1 GFs The resource performs the second step.

In some configurations, the RLI may reduce or reduce the chance of more than one WTRU accessing the PUSCH or UL resource(s), and the more than one WTRU accessing the PUSCH or UL resource(s) may result in Collisions, collisions, contention, etc. between WTRUs. This may be due to two or more WTRUs selecting similar listening interval values. In some configurations, collisions may occur due to hidden nodes (where the WTRU does not detect signals transmitted by another WTRU that started communication or transmission earlier on the similar resource(s) during RLI) conflict. In order to reduce collision opportunities in subsequent attempts, hybrid automatic repeat request (HARQ) feedback or HARQ negative acknowledgement (NACK) feedback for data or TB transmitted on early GF PUSCH or (one or more) UL resources is not received. The WTRU may, for subsequent attempts to access the GF UL resource(s), the WTRU may select a listening interval that is greater than the listening interval of the previous PUSCH or UL transmission. The WTRU may also select a maximum listening interval equal to the RLI, skip subsequent GF PUSCH or (one or more) UL resources, skip a fixed number of subsequent GF UL resources, may skip a random number of subsequent GF PUSCHs or UL resources, etc. To prevent collisions or conflicts. In some configurations, random numbers can be drawn from the range and distribution specified or configured by the network or gNB. If the WTRU receives a HARQ-NACK for previously transmitted data or TB indicating that the network is capable of retrieving the WTRU's identification from the collision signal within the GF resource, the WTRU may also receive the GB uplink resource to resend the pending data or TB.

Figure 6 and Figure 7 are flow diagrams of a two-stage or step LBT for GF PUSCH or UL transmission during COT. As further explained herein, at 600, the WTRU may obtain attributes and RLIs to access GF resources (602). The TB may be prepared for transmission in the next (one or more) GF resources, and a first phase or step (604) of using the LBT of the LBT class may be performed. If the LBT is successfully executed (606), the listening interval RLI _WTRU may be pseudo-randomly selected from {0,..., RLI} and the ED _GFBW (610) is calculated using the GF resource(s) BW and the ED _BWP . Otherwise, the transmission (608) for the GF resource(s) may be discarded, and the TB may be prepared for transmission in the next GF resource, and the first phase or step of using the LBT of the LBT class may be performed again. (604).

Energy detection can be performed for the listening interval RLI _WTRU and determined if it is less than a threshold or limit (612). If so, the TB is transmitted or delivered after the RLI _WTRU , or the reference or reservation signal is transmitted from the RLI _WTRU up to the RLI, and the TB is transmitted after the RLI (614). Otherwise, the transmission (608) for the GF resource(s) can be discarded. In other configurations, the WTRU may still begin transmission at the fixed OFDM symbol of the GF PUSCH, whether or not the LBT fails, without abandoning the GF resources.

In some configurations, the RLI region may be configured immediately prior to the GF resource(s) such that the structure of the PUSCH or UL resource(s), RS, DM-RS signal, etc., may be unaffected by the RLI region influences. The RLI region may also have a similar bandwidth as the GF resource(s), and the number of OFDM symbols of the RLI region may include the RLI. The WTRU may pseudo-randomly select the listening interval until the RLI symbol indicated by the RLI _WTRU . After performing the first LBT, the WTRU may perform RS detection or energy detection on the RLI _WTRU 's listening interval, and if the detected energy level is less than the threshold, the WTRU may assume that the media is available, unoccupied, or not Used by another WTRU. For the remaining duration of the RLI and up to the beginning of the GF resource(s), the WTRU may be configured to transmit a reservation signal, RS, DM-RS, Sounding Reference Signal (SRS) or signal, and the like. Sending one of these signals may cause the RLI to be perceived as busy by other WTRUs or as a reservation by the WTRU.

In some configurations, each WTRU may transmit the assigned DM-RS during the interval after the RLI _WTRU and up to the beginning of the GF resource(s). Depending on the remaining duration or symbol of the RLI, the DM-RS can be repeated multiple times such that the channel is occupied to the beginning of the GF PUSCH. Other WTRUs that perform channel sensing and measure energy during their own RLI _WTRU may find that the detected power or energy level is above a threshold and avoid transmission during GF PUSCH.

The remaining symbols after the RLI _WTRU may not be used by the WTRU to obtain unlicensed channels, frequencies, resources(s), or communications until the beginning of the GF PUSCH, RS, DM-RS, DM-RS sequence, or SRS, etc. , a more reliable estimate of the frequency band or code availability. In some configurations, the WTRU may be configured to use similar PN sequence initialization parameters for DM-RS sequences transmitted by the WTRU during RLI duration. The WTRU may also be configured or signaled such that a group or cluster of WTRUs may use a similar DM-RS sequence to allow for multiplex. Multiplexing of DM-RSs for different WTRUs may be implemented with time domain spreading, frequency domain spreading, cyclic shifting, or frequency division multiplexing.

A WTRU may be configured such that some WTRUs, groups, or clusters may use different PN sequences. In this configuration, the WTRU may be provided with information regarding PN sequence groups, other types of sequences, or Zadoff-Chu sequences, and the like. This configuration can improve RS detection of other WTRUs and accurately calculate Reference Signal Received Power (RSRP) or Reference Signal Receive Quality (RSRQ) and the like.

In another configuration, the WTRU may perform RS detection or DM-RS detection, etc. for each possible base sequence and each possible RS multiplex technique. RS multiplex technology can include time domain and frequency domain extension, application cyclic shift, frequency domain multiplexing or spatial multiplexing. RS detection can be performed by any possible frequency domain, code domain, spatial domain, and the like. The WTRU may also use a subset of these multiplex techniques and a subset of the base sequences to utilize RS detection. During transmission on the GF PUSCH, the WTRU may utilize WTRU-specific sequence initialization parameters for the DM-RS.

In some configurations, it can be assumed that a network device or gNB that successfully performs LBT can transmit DL signals or channels within unlicensed channels, frequencies, or frequency bands, and the like. The network or gNB may then transmit some DL signals, such as DM-RS, CSI-RS, or SRS, during periods during which the WTRU performs LBT to access GB or (one or more) GF resources. This may make the resource busy or occupied to prevent others from preempting. For example, sending a reference signal may prevent other devices from making Wi-Fi or 802.11x communications. For LBT procedures over a wider band or BWP, etc., the WTRU may perform RS detection and estimate energy or power. This can be achieved by a matched filter that implements specific pools for DM-RS, SRS, CSI-RS or similar sequences on the RB or RE on which the gNB or network device is not transmitting the DL signal. Matching of sequences. The WTRU may be configured with RS attributes transmitted by the network device or gNB over the RB or RE.

The WTRU may compare the collected energy or power to a modified threshold. The modified threshold can be applied to capture the actual bandwidth involved in calculating the energy. For example, this can be the nominal bandwidth minus the bandwidth used by the network device or gNB to transmit the DL signal. This may also be equivalent to the energy collected by the WTRU over a wider bandwidth minus the energy collected over the bandwidth of the network device or gNB transmitting the DL signal, and then comparing the result to the modified threshold. This configuration may be desirable if the network device or gNB transmits some DL signals (eg, RS) during the period in which one or more WTRUs perform the LBT procedure, and the unlicensed channel will be retained by the network device or gNB. Time regardless of the success or failure of the LBT program on the WTRU side. The WTRU may be configured to determine that the operation of transmitting the reference signal (e.g., DM-RS) is for GF LBT rather than for authorization based communication.

As further explained herein, at 700, the WTRU may be configured to use GF resources for UL transmission (702). The WTRU may obtain a set of resources and associated attributes, such as the location and periodicity of the resource. The WTRU may also obtain an RLI for each GF resource or resource group. The RLI may be obtained from an RRC configuration, an RRC signal, an RRC message, or a higher layer message or the like as an attribute of each resource or resource group. The RLI can also be obtained in the DCI, or in the MCOT indicator declared at the beginning of the COT. The RLI can be used in the second step of the LBT.
[1]

The WTRU may prepare to transmit a pending TB in the next (one or more) GF resources and perform a first step of LBT CAT 1-4 (704). If the WTRU performs a fixed listening interval LBT (eg, in CAT1 or CAT2), the WTRU may begin performing energy detection for the specified listening interval before the time of the (one or more) GF resources. If the WTRU performs a fixed listening interval LBT (eg, in CAT2), the WTRU may first calculate a listening interval of the specified class and attempt to perform energy for the duration of the calculated listening interval before approaching the GF resource(s). Or power detection. If the remaining time before the resource(s) is less than the listening interval, the WTRU may skip the resource(s).

If the first LBT procedure is successfully performed (706), the WTRU may pseudo-randomly select the listening interval duration in units of OFDM symbols from {0, . . . , RLI}, and the WTRU may be from a pre-specified or predetermined threshold. The energy detection threshold (710) is pre-calculated. The energy detection threshold can also be scaled based on the bandwidth resource(s).

The WTRU may perform energy or power detection for the listening interval and, if the detected energy or power is less than the threshold (712), by the WTRU in the remaining RLI, and a portion of the resource(s) following the RLI Transfer or pass TB (714). The WTRU may also send a reservation signal for the remaining RLIs and transmit the TBs at some of the resource(s) after the RLI after the RLI. Otherwise, transmissions for these resources may be discarded and monitoring of the next (one or more) GF resources may be performed (708). The WTRU may then again prepare to transmit the pending TB in the next (one or more) GF resources and perform the first step of LBT CAT 1-4 (704).

Figure 8 is an example of a two-stage LBT 800. A stage can be a sub-phase, a step, a sub-step, a process or a sub-process, and the like. At 800, a configuration (802) for RLI and UL GF resources can be received. An LBT (804) using energy detection for the LBT category can be performed and a successful LBT is determined as part of the first stage LBT (806). If successful, the second stage LBT is executed. Otherwise, the transmission of the GF resource(s) may be discarded (810), and the LBT (804) using energy detection for the LBT category may be performed again.

If successful, the second stage LBT may include pseudo-randomly selecting the RLI _WTRU (812) from {0,..., RLI}, detecting reference symbols or signals (814) during the listening interval, and transmitting in the listening interval. The reference symbol performs the measurement (816) and compares the measurement to a threshold or limit (818). If greater than the threshold or limit, the transmission of the GF resource(s) may be discarded (810). If less than a threshold or limit, the reservation signal can be transmitted on the remaining symbols of the listening interval (820) and the TB (822) can be sent on the GF resource(s) after the RLI.

Figure 9 is an example 900 of a GF PUSCH resource(s) including a listening interval before or at the beginning of the resource(s). In 900, the RLI _WTRU may include randomly selected 3 symbols or up to RLI symbols 902. The listening interval RLI symbol 902 can resolve this (one or more) GF resources and contention or collision of upcoming consecutive GF resources. At 900, the WTRU may perform a reference signal or energy detection on the listening interval RLI _WTRU . If the detected energy level or sequence likelihood is less than a threshold, the WTRU may determine that the media is not being used or available. For the remaining duration of the RLI up to the start or start of the GF resource(s), the WTRU may send a reservation signal, a reference signal, a DM-RS or SRS, and the like.

In some configurations, instead of a WTRU fallback when the interference energy is above a threshold, it may be a fallback when the interference energy due to the transmission of the WTRU group is above a threshold. Interference from WTRUs other than the specified set of WTRUs configured to transmit on similar resources or GF resources may be considered for fallback. Interference from 802.11x, LTE, or other RATs on similar resources or GF resources may also be considered for fallback in this configuration.

In configuration, the WTRU may measure energy, or power, of RS, DM-RS, SRS, or similar sequences belonging to groups other than the preferred sequence set in which the WTRU is configured or associated. Based on this measurement, the WTRU may perform an action, such as considering the resource for transmission or skipping the resource. The WTRU may determine that the RS group belongs to a network device or a gNB packetized or clustered WTRU group. A group or cluster may include a WTRU configured as part of multi-user MIMO (MU-MIMO) communication or transmission, a WTRU configured to participate in non-orthogonal multiple access of the same uplink resource(s), Or configured to use WTRU(s) like GF PUSCH resources, and the like.

The network device may be able to separate interference signals configured to use WTRUs like GF resources. The network device is also capable of distinguishing between energy from a preferred set of sequences configured for the WTRU and energy from outside the preferred set of sequences. For non-orthogonal multi-user/multiple access transmissions, the base station may be able to separate non-orthogonal transmissions from WTRU groups or clusters.

In some configurations, WTRU groups or clusters may be scheduled for transmission on similar resources, similar GF resources, and the like. A group of WTRUs scheduled to be transmitted on similar GF resources may have information related to the generation of RSs for all or some of the WTRUs in the group. For example, all WTRUs in the group may be configured with or be signaled similar PN sequence initialization parameters such that all WTRUs will generate the same sequence for their DM-RS. The WTRUs in the group may also be configured with or be queried that all WTRUs will use information similar to the DM-RS sequence.

Since the WTRU can know the DM-RS sequence, the DM-RS configuration, or the available DM-RS multiplex technology, etc., it can determine the group by estimating the possibility that the DM-RS, multiplex pair or antenna 埠 is active. Whether any of the other WTRUs are active. Using DM-RS activity information or DM-RS signal strength information, etc., the WTRU may estimate the power of the received signal that may have been initiated by the network device or WTRU outside the group.

In another configuration, some or all of the WTRU-like groups may use sequences generated from different PN sequences, but may have sufficient information to infer the sequence groups used by the WTRUs in the GF group. This can be accomplished by configuring or communicating to the WTRU sufficient information about the WTRU's sequence generation parameters. For example, there may be rules or configurations for generating a PN sequence that may be known, stored, or pre-configured by all or some of the WTRUs in the group.

The initialization of the PN sequence shift register may use the number C + kL, where C and L are constants known to the WTRUs in the group, and k is a WTRU-specific parameter that may be derived by all WTRUs. For example, if k is between 1 and 12 and the WTRU is configured or routed using k = 3, the WTRU may know which other potential WTRUs can set their respective k. In addition to sequence generation, the WTRU may also need to know the mapping between sequence indexing and multiplexing techniques. This information can be configured, communicated, or derived from existing information by the WTRU. For example, k can indicate the multiplex technology.

Figure 10 is an example of (one or more) GF PUSCH resources, and includes a 7-symbol micro-slot and a 3-symbol RLI _WTRU 1002. Although 1000 shows a 7-symbol micro time slot, the RLI may include a micro time slot having 2, 5, 7, or any number of symbols. In 1000, the WTRU may perform an ED on the listening interval of the RLI _WTRU , such as on the GF resource BW. If no energy or little energy is detected, the WTRU may determine that the media is not being used or available by another WTRU. The WTRU may transmit a reservation signal, a reference signal, a DM-RS or an SRS, etc. for the remaining duration of the RLI up to the beginning of the GF resource.

Figure 11 is an example 1100 of multiple GF PUSCH resources. In 1100, the WTRU may randomly select a listening interval of up to RLI1: RLI1 _WTRU , or up to RLI2 listening interval: RLI2 _WTRU . Figure 12 is an example of multiple GF PUSCH resources, where each GF PUSCH may have a different size 1200 and an RLI of the RLI _WTRU 1202 that changes from 2-4 symbols. The network device can make multiple GF PUSCHs available on a wider bandwidth, BWP, and the like. The WTRU may monitor more than one GF PUSCH resource and perform (eg, parallel, simultaneous, parallel, etc.) separate LBTs for each GF PUSCH resource. At 1200, the WTRU may perform energy detection on the RLI1 _WTRU listening interval in RLI1 symbols and on the BW of the first GF resource, on the RLI2 _WTRU listening interval in the RLI2 symbol, and in the The BW of the second GF resource, and the listening interval of the RLI3 _WTRU in the RLI 3 symbols and on the BW of the third GF resource. If the energy or power detected on the shortest of the three listening intervals is less than the associated threshold, the WTRU may determine that the GF PUSCH resource(s) associated with the shortest listening interval are available and available The GF PUSCH resource(s) are used for transmission. The WTRU may then discard energy or signal detection for other parallel resources.

If the energy or power detected on the previously considered listening interval (eg, the shortest time interval among the three listening intervals) is greater than the threshold, the WTRU may discard, interrupt, or discard the associated GF PUSCH(s). Resources, and consider the resource(s) associated with the next shortest listening interval, such as the second shortest listening interval for the set of listening intervals. If the energy detected on the next shortest listening interval is less than the associated threshold, the WTRU may determine that the medium is not used by any other WTRU for the one or more, and may use the GF PUSCH resource(s) For communication or transmission. The WTRU may then discard energy or signal detection for other remaining parallel resources unless the WTRU is capable of making more than one TB transmission during a similar time period, in which case the WTRU may perform an energy detection assessment on the remaining resources. If the energy detected on the listening interval is greater than the associated threshold or limit, the WTRU may assume that the resource(s) are busy, taken by another WTRU, or unavailable, and the WTRU may consider the next shortest Listening interval.

If the detected energy on the shortest listening interval of the three listening intervals is less than the associated threshold, the WTRU may determine that the GF PUSCH resource(s) associated with the shortest listening interval are not from any other WTRU. The (one or more) GF PUSCH resources are available for transmission by the resource(s). The WTRU may then abandon energy or signal detection for other remaining parallel resources.

In addition, if the detected energy on the listening interval considered (eg, the shortest listening interval of the three listening intervals) is greater than the threshold, the WTRU may discard or discard the associated GF PUSCH(s). The resource also considers the resource(s) associated with the next shortest listening interval (eg, the second short listening interval of the group listening interval). If the energy detected on the listening interval is less than the relevant threshold, the WTRU assumes that the media is not used by the other WTRU for the resource(s) or is available, and may utilize the GF PUSCH resource(s) For communication or transmission. The WTRU may skip energy or signal detection for other remaining parallel resources unless the WTRU is capable of making more than one TB transmission during a similar time period. For this configuration, the WTRU may maintain an energy detection assessment of the remaining resources. If the energy detected at the listening interval is greater than the associated threshold, the WTRU may determine that the resource(s) are busy, occupied or unavailable, etc., and consider the next shortest listening interval.

Figure 13 is an exemplary process 1300 for transmitting in a set of GF resources. The WTRU may obtain attributes and associated RLIs to access each GF resource (1302). The WTRU may prepare to transmit a TB in the upcoming GF resource group simultaneously on the RB and perform a first step of using the LBT class LBT (1304). If the first phase or step of the LBT is successfully completed (1306), the listening interval RLI _WTRU {RLI1 _WTRU , RLI2 _WTRU , ... may be pseudo-randomly selected from {0,..., RLI} for each GF resource. , RLIK _WTRU }, and, for each resource, ED _GFBW (1310) is calculated from resource BW and ED _BWP . If unsuccessful, the transmission for the GF resource may be discarded (1308), and the WTRU may again prepare to transmit the TB in the upcoming GF resource group on the RB and perform the first phase or step of using the LBT class LBT ( 1304).

In 1300, energy or sequence detection (1312) may be performed on all listening intervals {RLI1 _WTRU , ..., RLIK _WTRU } in parallel. If the detected energy on the remaining shortest listening interval is less than the associated threshold (1314), then the TB may be transmitted after the RLI _WTRU , or the signal, DM-RS or reservation from the RLI _WTRU , etc. until RLI and The TB is transmitted after the RLI (1318). If the detected energy is greater than the associated threshold, the shortest listening interval can be discarded and the remaining listening interval determined (1316). If the listening interval is still maintained, the next shortest listening interval (1320) is selected and the energy is again monitored for the associated threshold (1314). Otherwise, the transmission for the (one or more) GF resources can be discarded (1308).

In some configurations, the first phase or step of the LBT can be performed over a wider bandwidth (eg, BWP), and the second phase or step of the LBT can be on the bandwidth of the GF resource(s) Execute in parallel. For this configuration, the WTRU may calculate received energy over a wider bandwidth or BWP or the like over the duration of the LBT and the GF resource(s). If the energy detected during this interval exceeds the critical value ED _BWP , then the channel is determined to be busy, unavailable, or occupied, and the LBT program fails. Otherwise, the WTRU may calculate the detected energy for the duration of the RLI _WTRU within the RLI and compare the detected energy to the adjusted threshold ED _GFBW . If the detected energy is less than the threshold, the GF resource(s) may be idle and available. For the remainder of the RLI in this configuration, the WTRU may send a reservation signal or RS or the like before starting the data or TB transmission on the PUSCH resource(s).

Figure 14 is a diagram 1400 of an NR time slot including (one or more) RLI resource sensing intervals and (one or more) GF PUSCH resources. In 1400, the WTRU may be configured to select two values for the LBT interval based on CAT3, or to extract pseudo-random intervals according to CAT4. For a resource sensing interval RLI _WTRU , the WTRU may start the LBT interval in a manner such that the end of the interval is consistent with the RLI _WTRU . At 1400, the LBT interval can include a portion of the NR time slot. The RLI1 sensing interval 1402 can include seven symbols. If the energy detection during the LBT interval indicates that the BWP may be idle and ready for use by the WTRU, the WTRU may send a reservation signal, reference signal for the remaining duration of RLI1 1404 until the beginning of the GF resource(s). , DM-RS or SRS, etc.

Figure 15 is a program 1500 for parallel operation of two sensing programs. The WTRU may obtain an attribute and associated RLI to access the GF resource(s) (1502). A TB may be prepared for transmission in the upcoming GF resource(s) (1504). The determination of the LBT procedure or interval may be performed, the listening interval RLI _WTRU selected from {0,..., RLI} pseudo-randomly, and the ED _GFBW (1506) calculated from the resource BW and the ED _BWP . At each symbol, the average detected energy (1508) can be determined. The ED _LBT can be the average detected energy during the LBT listening interval. The ED _RLI may be the average detected energy during the RLI _WTRU . The following can be determined: whether ED _LBT > ED _BWP during the symbol when LBT is applicable; or ED _RLI > ED _GFBW (1510) during the symbol when RLI is applicable. If the condition is not met and other conditions are met, the TB may be transmitted after the associated RLI _WTRU . In other configurations, if the condition is not met and other conditions are met, a reservation, reference, RS or DM-RS, etc. signal may be transmitted from the RLI _WTRU up to the RLI and the TB is transmitted after the RLI (1514). Otherwise, the transmission for the resource(s) may be discarded (1512), and the TB may be prepared again for transmission in the upcoming GF resource(s) (1504).

The WTRU may perform alternate energy detection on the RLI. In some configurations, energy detection can be based on energy collected during the interval, similar to Received Signal Strength Indication (RSSI). The WTRU may also send the DM-RS until the start or start of the GF resource(s) during the duration after the RLI _WTRU . When the WTRU does transmit a DM-RS during this interval, it may be during the RLI _WTRU of another WTRU performing resource sensing.

When a network device or gNB configures a WTRU for MU-MIMO during GF resources(s), there may be uncertainty in the DM-RS sequence in the sequence pool available to the WTRU. Such a scenario may occur because a network device or gNB may have configured multiple WTRUs to access one or more GF resources and utilize MU-MIMO technology, where a large antenna array is configured on both sides. When many WTRUs are configured for similar GF resources(s), the gNB or network device may not have configured the WTRU-specific DM-RS for the WTRU. In this configuration, the WTRU may select a sequence from a pool of DM-RS sequences either pseudo-randomly or according to a predetermined order. However, since similar sequences may be selected by more than one WTRU, DM-RS collisions are possible, which results in the network not being able to detect the communication or transmission of each WTRU.

When the WTRU performs energy detection during its own resource sensing interval RLI _WTRU , the energy of one or all of the DM-RS sequences known to the WTRU may be detected. During this operation, the WTRU may determine the likelihood that another WTRU is using the DM-RS. The WTRU is also capable of determining one or more DM-RS sequences that are underutilized by other WTRUs, and using one or more of these DM-RSs for transmission during the remainder of the RLI following the RLI _WTRU , and up to resources ( The beginning of one or more). The WTRU may also utilize these underutilized or infrequently used DM-RS sequences during the (one or more) GF resources.

In some configurations, the WTRU may be configured with a maximum number of layers or users that may operate in MU-MIMO. When the WTRU determines the detection energy of one or all DM-RS sequences and determines the likelihood that another WTRU is using the DM-RS, if the WTRU determines that the number of DM-RS sequences that are likely to be used by other WTRUs is greater than the network capable The maximum number of WTRUs or layers differentiated within MU-MIMO, and then the WTRU may determine that the resource(s) are not suitable. For this case, the transmission in any DM-RS and (one or more) GF resources can be discarded. These conditions can be specified to fail with the GF resource(s), similar to an LBT program failure.

In configuration, non-orthogonal multiple access by multiple WTRUs during the PUSCH resource(s) may result in uncertainty of DM-RS usage. For example, if a network device or gNB has many WTRUs, by using non-orthogonal multiple access to access one or more PUSCH resources capable of separating multiple transmissions, there may be uncertainty. Due to the configuration of many WTRUs for similar resources(s), the network device or gNB may not have configured the WTRU to have a WTRU-specific DM-RS. In this configuration, the WTRU may select a DM-RS from a pool of DM-RSs pseudo-randomly or according to a predetermined order or the like. However, since similar DM-RSs may be selected by more than one WTRU, DM-RS collisions or collisions are possible, making it difficult to detect communication or transmissions of the various WTRUs at the network device.

The network device or gNB may schedule the RLI for the WTRU for each or a consecutive set of PUSCH resources for non-orthogonal multiple access. In this configuration, the WTRU may select a pseudo-random listening interval for the RLI _WTRU for the PUSCH resource(s) and perform DM-RS detection, such as matched filtering, during the listening interval. When the WTRU performs energy detection or DM-RS matched filtering during the resource sensing interval RLI _WTRU , the WTRU may rank the detected energy for one or all of the DM-RSs available to the WTRU. The WTRU may also determine the likelihood that another WTRU is or has used a DM-RS sequence. The WTRU may also determine one or more DM-RS sequences that are least likely to be used by other WTRUs, and may use one or more of such DM-RS sequences during the remaining symbols of the RLI and at (one or more The PUSCH resource period is used for transmission. Once the WTRU identifies the DM-RS sequence to use, the WTRU may use the association of the DM-RS sequence with one or more other attributes of the non-orthogonal multiple access and select the associated with the particular DM-RS sequence. The value or sequence of the attribute.

In non-orthogonal multiple access, once the WTRU identifies the DM-RS sequence to use, the WTRU may select the associated signature sequence for subsequent communication or transmission. Also in non-orthogonal multiple access, once the WTRU identifies the DM-RS sequence to use, the WTRU may select an associated transmit power value or array of power values for subsequent transmission. In another configuration, once the WTRU identifies the DM-RS sequence to use, the WTRU may select the associated redundancy version value(s), coding rate(s) or HARQ ID, etc. for Subsequent transmission.

In some configurations, one or more WTRUs may be configured with a maximum number of WTRUs capable of operating within the resource(s) configured for a given non-orthogonal multiple access system. When the WTRU ranks the detected energy of one or all of the DM-RS sequences, if the WTRU determines that the number of DM-RS sequences that other WTRUs may have used exceeds a particular non-positive within the PUSCH resource(s) The maximum number of distinguishable WTRUs or layers in a multiple access may be that the WTRU may assume that the resource(s) are not suitable for communication or transmission. Therefore, it is possible to discard the selection of the DM-RS and the transmission in the corresponding resource(s).

To resolve contention or collisions and select values/sequences of one or more transmission attributes from a set of values/sequences of one or more attributes, the WTRU may use the RLI at the beginning of the uplink resource(s), Or it may be a separate resource(s) that are scheduled before the uplink resource(s). The individual resource(s) may still be within the same bandwidth as the uplink resource(s). The RLI may have a duration RLI and the WTRU may be configured with a duration of RLI that may vary for each uplink resource(s).

The WTRU may select a listening interval with a pseudo-random duration from the maximum duration of the associated resource(s), which is represented as an RLI _WTRU . During the RLI _WTRU , the WTRU may perform functions such as energy detection, sequence detection, or matched filtering. The WTRU may perform energy detection during the RLI _WTRU , such as measuring RSSI. The WTRU may perform sequence detection during the RLI _WTRU , for example by measuring RSRP or RSRQ, and the like. The WTRU may perform a matched filtering set on the sequence group during the RLI _WTRU , for example by detecting a DM-RS, SRS or CSI-RS group, or the like. The WTRU may also perform a matched filtering set on a sequence group other than the preferred RS or DM-RS sequence group configured by the _WTRU during the RLI _WTRU , for example by detecting a reference signal, a DM-RS, an SRS or a CSI-RS group, or the like. .

The WTRU may perform likelihood estimation on the sequence group during the RLI _WTRU , for example for non-orthogonal multiple access. After energy or sequence detection during the RLI _WTRU , such as by RSSI, RSRP, or RSRQ, etc., the WTRU may determine if there is any transmission within the RLI indicating whether it is within the uplink resource(s) after the RLI There will be any transmissions, etc.

After the energy, power, or sequence detection or threshold comparison of the sequence groups outside the preferred sequence group configured by the _WTRU during the RLI _WTRU , the WTRU may determine any transmissions within the RLI that indicate one or more after the RLI Whether there are any transmissions from the WTRU that are not associated with the preferred sequence group, etc. within the uplink resource. In addition, after sequence detection during the RLI _WTRU , the WTRU may derive conclusions about sequence usage during the RLI _WTRU and select one or more RSs, DM-RSs, or SRSs that are least likely to be used during the RLI duration. Wait.

In some configurations, if the number of sequences that may be used during an RLI _WTRU exceeds a pre-configured threshold, the WTRU may decide not to select any sequence. For example, in a MU-MIMO configuration, where the network device configures the WTRU with the maximum number of WTRUs or layers that the network device can distinguish within the MU-MIMO transmission, the WTRU may avoid the selection sequence and avoid participating after the RLI ( MU-MIMO transmission in one or more resources.

After an estimate of the likelihood, such as a signature or signature function, during the RLI _WTRU , the WTRU may infer which sequences or signatures are likely to be in use and select one or more signatures that have a minimum likelihood of use during the RLI duration. Additionally, if the number of signatures that may be used during the RLI _WTRU exceeds a pre-configured threshold, the WTRU may decide not to select a signature. In a non-orthogonal multiple access configuration, the network configures the WTRU with the maximum number of WTRUs or layers that can distinguish signals in the network non-orthogonal multiple access. The WTRU can avoid selecting signatures and avoid participating in the RLI. Non-orthogonal multiple access transmissions in (one or more) resources.

In addition, the WTRU may select a value or sequence based on one or more other transmission attributes given herein. In the configuration, associated with the selection of RS, DM-RS, SRS, etc., other attributes may include selecting a sequence for non-orthogonal multiple access signatures, selecting (one or more) transmission power values, selecting a redundancy version (RV) transmission or selection of HARQ ID, etc.

In some configurations, multiple levels of LBT can be performed. This configuration may include efficient coexistence of NR-U WTRUs with various types of competitors. Effective coexistence may include cooperation between NR-U network devices, gNBs, or WTRUs, and the like.

An NR-U WTRU or gNB attempting to perform an LBT can do so by performing several energy detection operations in parallel. Energy detection can be performed across the operating bandwidth and includes determining if the detected energy level is above a specified or predetermined threshold. The network device or gNB can perform energy detection simultaneously across multiple BWPs, and if the LBT is successfully completed on each BWP, then transmissions are initiated on one or more BWPs. If the WTRU is capable of operating in multiple BWPs, the WTRU may simultaneously check for the presence of network-initiated COTs in the plurality of BWPs, where the WTRU may perform the detection in the BWP in accordance with the priority sequence table. If the WTRU detects the presence of a COT in one of the BWPs, it may continue to receive on the COT within the BWP. If the WTRU detects the presence of a COT in more than one BWP, it may continue to receive on the COT with the highest priority.

The NR-U WTRU, gNB, or network device can detect the presence of LAA, 802.11x, LTE, NR-U, or other RATs by performing custom operations such as cyclic prefix detection. After detecting the specific RAT or parameter configuration of the NR-U, the NR-U device can compare the detected energy level with various pre-configured thresholds, where the detected RAT or parameter configuration can coexist. It is adaptive. To accommodate coexistence with the detected RAT or parameter configuration, the NR-U WTRU, gNB, or network device can attempt to detect the presence of a cyclic prefix by performing an autocorrelation of the received signal with a delayed version of the same signal. The amount of delay can be obtained from the parameter configuration and the length of the cyclic prefix. For example, if the OFDM symbol duration is T _OFDM and the duration of the cyclic prefix is T _CP , the delay may be T _OFDM + T _CP .

In configuration, the NR-U device may choose to monitor multiple parameter configurations or multiple cyclic prefix lengths for a given terminology and detect energy that can be compared to a scaled version of the ED _BWP . The NR-U device may also choose to monitor other RATs that also use OFDM or OFDMA techniques. For example, an NR-U device can monitor the presence of 802.11 technology by executing multiple cyclic prefix detectors, each of which configures one of the 802.11 parameters. The NR-U device can increase the tolerance for a particular NR parameter configuration by lowering the threshold value for which only the detected energy below the threshold value indicates an idle channel. This configuration of the network to the NR-U network device, or the configuration of the NR-U WTRU by the gNB, may be based on the deployment of multiple NR-U cells by the same operator. This may be desirable for operators seeking improved coexistence between NR-U cells, particularly at the edge of the cell.

The NR-U device can increase the tolerance for a particular RAT by reducing the threshold for idle or available channel detection. This configuration of the network to the NR-U network device, or the configuration of the NR-U WTRU by the gNB, may be based on the deployment of the same operator to other RATs. This may be desirable for an operator seeking better coexistence between multiple deployed technologies in a similar geographic area (eg, NR-U, 802.11x, or unlicensed LTE).

If associated with a different operator, the NR-U device may decide or be configured to de-prioritize coexistence and reduce the tolerance for a particular NR parameter configuration or for a RAT that is not identified as part of the preferred RAT group. This can be achieved by increasing the energy detection threshold. For example, if the energy detection threshold for a 20 MHz bandwidth is -72 dBm, the threshold can be increased to -77 dBm or -62 dBm for a RAT or parameter configuration that is not a preferred RAT group. In another example, a WTRU transmitting a short channel (eg, sPUCCH, HARQ-ACK feedback, or SR, etc.) may use an increased energy detection threshold, and for the remaining transmissions, a more tolerant threshold or preset may be used. value. In some configurations, the COT established by a RAT or parameter configuration outside of the preferred RAT group may be ignored or ignored.

Prioritization of coexistence between network device groups or gNBs may include forming prioritized or preferred device groups operating in the same channel or sharing at least one BWP. This can be achieved by detecting the broadcast channel(s), SSB, OSI, or SIB, etc. of all nearby network devices and obtaining information indicating that the network device belongs to the same entity as the receiving or detecting network device. achieve. Along with this information, the network device can obtain a network device group identification (eg, gNB group-RNTI) to scramble a particular downlink channel. For example, a gNB belonging to a prioritized or preferred gNB group may send a specific downlink control channel or PDCCH that is scrambled by a particular RNTI that the gNB can detect. The search space for this PDCCH may be previously known by gNB. The search space can be configured by higher layer configuration, RRC messages, RRC messaging, transmissions via any broadcast channel, and the like. The content of such a PDCCH may vary and may include, for example, the duration of the COT.

In some configurations, as long as the receiving gNB or the receiving WTRU detects a PDCCH using gNB group identification or gNB group-RNTI, etc., it can be inferred that the channel is being a member of the preferred or prioritized gNB group. use. In this configuration, the receiving gNB can apply a more tolerant energy detection threshold, or other more tolerant coexistence operations can be applied. If a receiving gNB or the receiving WTRU is unable to detect a PDCCH identified using the gNB group, the gNB may conclude that the channel is being used by a gNB that is not a member of the preferred or prioritized gNB group. In this configuration, the receiving gNB can apply a less tolerant energy detection threshold, or other less permissive coexistence operations can be applied.

In some configurations, the gNB may be part of one or more of a plurality of preferred or prioritized gNBs, where for each group there may be a group identification previously known by the gNB group and may Apply varying levels of coexistence operations for each group. For example, a gNB can associate a more tolerant energy detection threshold with a set and associate different energy detection thresholds with another set of gNBs.

Although features and elements of a particular combination are described above, those of ordinary skill in the art will recognize that each feature or element can be used alone or in any combination with other features and elements. Additionally, the methods described herein can be implemented in a computer program, software or firmware incorporated in a computer readable medium for execution by a computer or processor. Examples of computer readable media include electronic signals (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), scratchpad, cache memory, semiconductor memory device, magnetic media (eg, internal hard drive) And removable magnetic discs), magneto-optical media, and optical media (such as CD-ROM discs and digital versatile discs (DVD)). A processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

BWP‧‧‧width section

COT‧‧‧ channel occupancy time

ED‧‧ energy level

GF‧‧‧Exemption

LBT‧‧‧ listened first

N2, N3, N4, N6, N11, S1, X2, Xn‧‧ interface

NR‧‧‧New Radio

OS‧‧ OFDM symbol

PUSCH‧‧‧ physical chain shared channel

RB‧‧‧Resource Block

RLI‧‧‧Resource listening interval

TB‧‧‧Transport block

UL‧‧‧上上

WTRU, 102, 102a, 102b, 102c, 102d‧‧‧ wireless transmission/reception unit

100‧‧‧Communication system

104, 113‧‧‧ Radio Access Network (RAN)

106/115‧‧‧ Core Network (CN)

108‧‧‧Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧Intermediate mediation

118‧‧‧Processor

120‧‧‧ transceiver

122‧‧‧Transmission/receiving components

124‧‧‧Speaker/Microphone

126‧‧‧Keypad

128‧‧‧Display/Touchpad

130‧‧‧ Non-removable memory

132‧‧‧Removable memory

134‧‧‧Power supply

136‧‧‧Global Positioning System (GPS) chipset

138‧‧‧ Peripherals

160a, 160b, 160c‧‧‧e Node B

162‧‧‧Action Management Entity (MME)

164‧‧‧Service Gateway (SGW)

166‧‧‧ Packet Data Network (PDN) Gateway (or PGW)

180a, 180b, 180c‧‧‧ gNB

182a, 182b‧‧ Access and Operational Management Functions (AMF)

183a, 183b‧‧‧Dialog Management Function (SMF)

184a, 184b‧‧‧ User Plane Function (UPF)

185a, 185b‧‧‧ Data Network (DN)

In addition, the same component symbols in the drawings denote the same components, and wherein:

1A is a system diagram showing an exemplary communication system in which one or more disclosed embodiments may be implemented;

1B is a system diagram showing an exemplary wireless transmit/receive unit (WTRU) that may be used within the communication system shown in FIG. 1A, in accordance with an embodiment;

1C is a system diagram showing an exemplary Radio Access Network (RAN) and an exemplary Core Network (CN) that may be used within the communication system shown in FIG. 1A, in accordance with an embodiment;

1D is a system diagram showing another exemplary RAN and another exemplary CN that may be used within the communication system shown in FIG. 1A, in accordance with an embodiment;

Figure 2 is an example of channel occupancy time (COT) for new radio unlicensed (NR-U) operations;

Figure 3 is another example of a COT for NR-U operation;

Figure 4 is an example of one or more grant-free (GF) entity uplink shared channel (PUSCH) resources including a listening interval;

Figure 5 is another example of one or more GF PUSCH resources including a listening interval;

Figure 6 and Figure 7 are flow diagrams for two-stage or step-by-head listening (LBT) for GF UL transmission during COT;

Figure 8 is an example of a two-stage LBT;

Figure 9 is an example of one or more GF PUSCH resources including a listening interval at the beginning of a resource;

Figure 10 is an example of one or more GF PUSCH resources, and includes a micro-time slot of 7 symbols;

Figure 11 is an example of multiple GF PUSCH resources;

Figure 12 is an example of multiple GF PUSCH resources, where each GF PUSCH may have a different size resource listening interval (RLI);

Figure 13 is an exemplary procedure for transmitting in a set of GF resources;

Figure 14 is a diagram of an NR time slot including an RLI resource sensing interval and one or more GF PUSCH resources;

Figure 15 is a program for parallel operation of two sensing programs.

Claims (14)

A wireless transmit/receive unit (WTRU) comprising: a transceiver configured to receive a reference signal (RS) from a network device during a first time interval; a processor configured to perform a first Listening Waiting (LBT) during the first time interval; The processor is configured to: at a second time having a plurality of resource listening interval (RLI) symbols and a plurality of unlicensed (GF) entities uplink shared channel (PUSCH) resources, under the condition that the first LBT is successful Performing a second LBT during the interval, wherein the second LBT is based on a selected random number of the RLI symbols; The transceiver is configured to transmit one or more second RSs until a remaining number of the one of the measured values of the first RS during the selected random number of the RLI symbols is less than a threshold RLI symbol; and The transceiver is further configured to transmit a transport block on the GF PUSCH resource after the RLI symbol. The WTRU as claimed in claim 1, wherein the RS during the first time interval is for an entire bandwidth or a bandwidth portion (BWP) and prevents other WTRUs from using resources. The WTRU as claimed in claim 1, wherein the first time interval and the second time interval are part of a channel occupancy time (COT). The WTRU as claimed in claim 1, wherein the RLI symbol and the GF PUSCH resource are configured by higher layer communications received from the network device. The WTRU as claimed in claim 1, wherein the selected random number of the RLI symbols is based on an LBT class. The WTRU as claimed in claim 1, wherein the RS, the first RS or the second RS is a demodulation reference signal (DM-RS). The WTRU as claimed in claim 1, further comprising the processor configured to perform a different LBT on each of the plurality of configured GF PUSCH resources under the condition that the first LBT is successful . A method performed by a wireless transmit/receive unit (WTRU), the method comprising: Receiving, by the WTRU, a reference signal (RS) from a network device during a first time interval; Performing, by the WTRU, a first Listening Waiting (LBT) during the first time interval; Performing, by the WTRU, during a second time interval having a plurality of resource listening interval (RLI) symbols and a plurality of grant-free (GF) entity uplink shared channel (PUSCH) resources, under the condition that the first LBT is successful a second LBT, wherein the second LBT is based on a selected random number of the RLI symbols; Transmitting, by the WTRU, one or more second RSs to a remaining number of the RLI symbols under a condition that a measured energy of the first RS during the selected random number of the RLI symbols is less than a threshold; as well as A transport block is transmitted by the WTRU on the GF PUSCH resource after the RLI symbol. The method of claim 8, wherein the RS during the first time interval is for an entire bandwidth or a bandwidth portion (BWP) and prevents other WTRUs from using resources. The method of claim 8, wherein the first time interval and the second time interval are part of a channel occupancy time (COT). The method of claim 8, wherein the RLI symbol and the GF PUSCH resource are configured by higher layer communications received from the network device. The method of claim 8, wherein the selected random number of the RLI symbols is based on an LBT category. The method of claim 8, wherein the RS, the first RS or the second RS is a demodulation reference signal (DM-RS). The method of claim 8, wherein the method further comprises: performing a different LBT on each of the plurality of configured GF PUSCH resources under the condition that the first LBT is successful.