How to enhance reliability in high frequency communications and support mixed priority traffic

Abstract

A method implemented by a wireless transmit / receive unit (WTRU) may comprise receiving downlink control information, DCI, the DCI including a multi-PDSCH priority indication, determining a priority for each of two or more PDSCH transmissions based on the multi-PDSCH priority indication, determining one or more scheduling parameters for each of the two or more PDSCH transmissions based on the determined priority of each of the two or more PDSCH transmissions, and receiving each of the two or more PDSCH transmissions using the respective determined scheduling parameters. The method may further comprise associating a first scheduling parameter with a first priority and associating a second scheduling parameter with a second priority, the first priority being a high priority and the second priority being a low priority.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 277,895, filed November 10, 2021, the contents of which are incorporated herein by reference. Summary of the Invention [Problem to be solved by the invention]

[0002] Higher subcarrier spacing (SCS) is used for high frequency communication, e.g., 480 kHz and 960 kHz are supported in Frequency Range 2-2 (FR2-2). These SCS result in shorter slot durations compared to the lower SCS supported for low carrier frequencies. To reduce signaling overhead and take advantage of the large channel coherence time compared to the slot duration, scheduling of up to eight physical downlink channel shared channels (PDSCHs) by a single DCI is developed. All scheduled PDSCHs share the same priority index and modulation and coding scheme (MCS). This configuration does not allow flexibility in setting the priority of each PDSCH. Also, traffic with different priorities requires different reliability and latency requirements. Transmitting different replicas of the same PDSCH, e.g., different resource blocks (RBs) using the same transmission / reception point (TRP), may provide some gains. However, multi-TRP communications are useful with these short slot duration communications because they can provide time and frequency domain diversity gains in addition to signal-to-noise ratio (SNR) gains.

[0003] A method implemented by a wireless transmit / receive unit (WTRU) may comprise receiving downlink control information (DCI), the DCI including a multiple physical downlink channel shared channel (PDSCH) priority indication, determining a priority for each of two or more PDSCH transmissions based on the multiple PDSCH priority indication, determining one or more scheduling parameters for each of the two or more PDSCH transmissions based on the determined priority of each of the two or more PDSCH transmissions, and receiving each of the two or more PDSCH transmissions using the respective determined scheduling parameters. The method may further comprise associating a first scheduling parameter with a first priority and associating a second scheduling parameter with a second priority, where the first priority is a high priority and the second priority is a low priority.

[0004] The multi-PDSCH priority indication may indicate a number of high priority PDSCH transmissions, with the high priority PDSCH being transmitted before the low priority PDSCH transmission. The DCI may include a bitmap indicating a priority of each of the two or more PDSCH transmissions. The one or more scheduling parameters may be at least one of a repetition number, a time position, a demodulation reference signal (DMRS) pattern, a DMRS density, and a modulation and coding scheme (MCS).

[0005] A method implemented by the WTRU may comprise receiving a DCI, the DCI including a multi-physical uplink shared channel (PUSCH) priority indication, determining a priority for each of two or more PUSCH transmissions based on the multi-PUSCH priority indication, determining one or more scheduling parameters for each of the two or more PUSCH transmissions based on the determined priority of each of the two or more PUSCH transmissions, and transmitting each of the two or more PUSCH transmissions using the respective determined scheduling parameters. The method may further comprise associating a first scheduling parameter with a first priority and associating a second scheduling parameter with a second priority, where the first priority is a high priority and the second priority is a low priority.

[0006] The DCI includes a bitmap indicating a priority of each of the two or more PUSCH transmissions. The one or more scheduling parameters may be at least one of a repetition number, a time position, a DMRS pattern, a DMRS density, and an MCS. [Brief description of the drawings]

[0007] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numbers indicate similar elements and in which: [Figure 1A] FIG. 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] FIG. 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A, according to one embodiment. [Figure 1C] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A, according to one embodiment. [Figure 1D]FIG. 1D is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communications system illustrated in FIG. 1A, according to one embodiment. [Diagram 2] FIG. 2 illustrates an example multi-PDSCH scheduling with a single DCI in which four PDSCH transmissions are scheduled. [Diagram 3] FIG. 3 illustrates an exemplary multi-TRP transmission using slot-level TDM. [Figure 4] FIG. 4 illustrates an example multi-PDSCH scheduling for multi-TRP transmission with different TCI state mapping patterns (TCI-MP) when the number of repetitions is equal to two. [Diagram 5] FIG. 5 is a diagram illustrating an example TCI state mapping based on TDRA. [Figure 6] FIG. 6 is a diagram illustrating an example TCI state mapping using TCI-MP1, where the number of iterations is greater than two and is an even number. [Figure 7] FIG. 7 is a diagram illustrating an example TCI state mapping using TCI-MP1, where the number of iterations is greater than 2 and is an odd number. [Figure 8] FIG. 8 illustrates an example TCI state mapping using TCI-MP3 where the number of iterations is greater than two. [Figure 9] FIG. 9 illustrates an example multi-PDSCH scheduling for multi-TRP transmission with repetition and frequency hopping. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

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

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

[0013] More specifically, as noted above, the communications system 100 may be a multiple access system, but may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a and the WTRUs 102a, 102b, 102c of the RAN 104 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communications 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).

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

[0015] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using NR.

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

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

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

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

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

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

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

[0023] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B illustrates the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

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

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

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

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

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

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

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

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

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

[0035] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are illustrated as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

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

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

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

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

[0042] A WLAN in infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic within the BSS and / or outside the BSS. Traffic originating from outside the BSS to the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs within the BSS may be sent, for example, through the AP, where the source STA may send traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between (e.g., directly between) the source STA and the destination STA using a direct link setup (DLS). In certain representative 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 (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad-hoc" communication mode.

[0043] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically configured width. The primary channel may be the operating channel of the BSS, but may be used by STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0044] A High Throughput (HT) STA may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

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

[0046] Sub-1 GHz operation modes are supported by 802.11af and 802.11ah. The channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter-type control / machine-type communications (MTC), such as MTC devices in macro coverage areas. MTC devices may have limited capabilities, including certain capabilities, for example, support for (e.g., support only for) certain and / or limited bandwidths. The MTC device may include a battery that has a battery life above a threshold (eg, to maintain a very long battery life).

[0047] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be configured and / or limited by the STAs among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. For example, if a STA (that only supports 1 MHz mode of operation) transmitting to an AP has a busy primary channel, all of the available frequency bands may be considered busy even if most of the available frequency bands are idle.

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

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

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

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

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

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

[0054] 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although the foregoing elements are illustrated as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0055] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for user authentication of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling different protocol data unit (PDU) sessions having different requirements), selection of a particular SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

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

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

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

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

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

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

[0062] The following abbreviations and acronyms may be referenced:

[0063] [Table 1-1]

[0064] [Table 1-2]

[0065] [Table 1-3]

[0066] For receiving a multi-PDSCH scheduled by a single DCI using a URLLC service, a WTRU can receive a per-slot inter-repetition type configuration for each TDRA code point for the multi-PDSCH scheduled by the single DCI. The WTRU can receive a DCI indicating a TDRA code point (indicating N time domain resource allocations for N PDSCHs) and some high-priority packets of the multi-PDSCH. The WTRU can determine the number of repetitions K for the high-priority PDSCH and the number of repetitions L for the low-priority PDSCH. If no repetition is indicated, K = 1 and L = 1. If a repetition for the high-priority PDSCH is indicated, K can be the value indicated by the TDRA information and L = 1. If repetitions for all PDSCHs are indicated, K and L can indicate values according to the TDRA information.

[0067] The WTRU can receive the scheduled multi-PDSCH based on the TDRA information associated with the TDRA code point and the number of high-priority packets. The WTRU can receive the first N high-priority packets and then the last M - N low-priority packets within one repetition. The WTRU can receive the N high-priority packets K times and the M - N low-priority packets L times. The WTRU can report ACK / NACK after X (< K and / or L) PDSCH receptions. X can be based on the indicated PUCCH resource indication within the scheduling DCI. The WTRU can receive the failed PDSCH first and skip decoding the retransmission of the PDSCH that has been successfully decoded based on the WTRU report.

[0068] The WTRU may support different PDSCH scheduling parameters for each PDSCH based on the indicated priority. The MCS codepoint may indicate two MCSs: (1) use a first MCS or lower LCS for high priority, or (2) use a second MCS or higher MSC for low priority. Other parameters include: (1) number of repetitions (e.g., only applicable to high priority PDSCH), (2) DMRS type and density (e.g., high density DMRS for high priority PDSCH), (3) rank (e.g., low rank for high priority PDSCH), (4) enable / disable frequency hopping (e.g., frequency hopping for high priority PDSCH).

[0069] The WTRU may determine a TDRA for each PDSCH repetition. The WTRU may receive a DCI indicating a TDRA code point (indicating N time domain resource allocations for the N PDSCHs). The WTRU may determine a transmission occasion (slot) for each PDSCH repetition based on the TDRA code point indicated by the DCI. If the TDRA entry for each PDSCH indicates one K0 value per repetition, the transmission occasion of the repetition may be determined by multiple K0 values. If the TDRA entry for each PDSCH indicates one K0 value and an offset for each repetition (offset(1), offset(2), etc.), the transmission occasion of the kth repetition may be determined by K0 + offset(k).

[0070] The WTRU may also determine the SLIV configuration of each PDSCH repetition based on the TDRA codepoint indicated by the DCI. If the TDRA entry for each PDSCH indicates one SLIV configuration per PDSCH, the same SLIV configuration may be applied for each repetition. If the TDRA entry for each PDSCH indicates one SLIV configuration per repetition, each repetition may be configured with the configured SLIV.

[0071] Bands above 52.6 GHz have the potential for greater spectrum allocations that are not available for bands below 52.6 GHz. However, systems operating at frequencies above 52.6 GHz face more difficult challenges compared to lower frequency bands, such as higher phase noise, extreme propagation losses due to high atmospheric absorption, lower power amplifier efficiency, and stronger regulatory requirements for power spectral density. Furthermore, the NR physical layer design was originally designed to be optimized for frequencies below 52.6 GHz. To overcome some of these challenges, in RAN#90, an updated WID agreed to extend NR operation to 71 GHz, considering operation in both licensed and unlicensed bands. As part of the new WID, it was agreed to schedule multiple PDSCHs by a single DCI.

[0072] 2 shows an example configuration of single DCI-based multi-PDSCH scheduling in which four PDSCHs are scheduled. As shown in FIG. 2, the multi-PDSCH scheduling includes slots 202a-202j. The single DCI may be located in slot 202a, while the PDSCHs may be scheduled in slots 202b, 202c, 202e, and 202f.

[0073] Several extensions to multi-PDSCH scheduling with a single DCI have been proposed. These extensions are based on multi-TRP transmission, where the same PDSCH is repeated over two TRPs using TDM, FDM or SDM to support both URLLC and eMBB use cases.

[0074] 3 shows an example multi-TRP transmission configuration with two TRPs and slot-level TDM with eight repetitions. In cyclicMapping, the WTRU may receive each successive repetition of the PDSCH from a different TRP. In sequentialMapping, the WTRU may receive two repetitions of the PDSCH from the first TRP. In the following two slots, the WTRU receives two repetitions of the PDSCH from the second TRP.

[0075] For example, supporting multi-TRP transmission for higher carrier frequencies in FR2-2 (52.6 GHz to 71 GHz) requires some new solutions. In some cases, multi-TRP transmission supports only a single PDSCH repetition. However, in other cases, multiple PDSCHs are scheduled by a single DCI. Therefore, new solutions are required to efficiently support multiple PDSCH repetitions scheduled by a single DCI.

[0076] Furthermore, in a particular FR2-2 design, all PDSCHs scheduled by a single DCI may only be configured with a single priority level and MCS. This may limit and allow PDSCHs of different priority levels to be scheduled by a single DCI, which may be important when multiple PDSCHs are scheduled by a single DCI. Also, for example, licensed spectrum, solutions for radio frequency communications, some multi-TRPs designed for FR2-2 should be able to support both licensed and unlicensed spectrum.

[0077] One embodiment may allow PDSCHs with different priority levels to be scheduled together by the same control channel signaling. Another embodiment may allow the WTRU to determine the priority level of the PDSCH. Another embodiment may allow achieving reliable transmission by using multiple repetitions on multiple TRPs. Another embodiment may improve resource utilization efficiency in repletion transmissions in multi-PDSCH scheduling. Another embodiment may allow switching modulation based on the beam pair in use.

[0078] The WTRU may transmit or receive a physical channel or a reference signal according to at least one spatial domain filter, Hereinafter, the term "beam" may be used to refer to a spatial domain filter.

[0079] The WTRU may transmit a physical channel or signal using the same spatial domain filter as that used to receive an RS (e.g., CSI-RS) or SS block. The WTRU transmission may be referred to as the "target" and the received RS or SS block may be referred to as the "reference" or "source." In such a case, the WTRU may transmit the target physical channel or signal according to a spatial relationship to such RS or SS block.

[0080] The WTRU may transmit a first physical channel or signal according to the same spatial domain filter as that used to transmit a second physical channel or signal. The first and second transmissions may be referred to as the "target" and "reference" (or "source"), respectively. In such a case, the WTRU may transmit the first (target) physical channel or signal according to a spatial relationship to the second (reference) physical channel or signal.

[0081] The spatial relationship may be implicit, configured by RRC, or signaled by MAC CE or DCI. For example, the WTRU may implicitly transmit the PUSCH and DM-RS for PUSCH according to the same spatial domain filter as the SRS indicated in the DCI or indicated by the SRI configured by RRC. In another embodiment, the spatial relationship may be configured by RRC for the SRS resource indicator (SRI) or signaled by the MAC CE for the PUCCH. Such a spatial relationship may also be referred to as "beam indication."

[0082] The WTRU may receive the first (target) downlink channel or signal according to the same spatial domain filter or spatial reception parameters as the second (reference) downlink channel or signal. For example, such an association may exist between a physical channel, such as a PDCCH or PDSCH, and its respective DM-RS. When at least the first and second signals are reference signals, such an association may exist when the WTRU is configured with a quasi-colocation (QCL) assumption type D between the corresponding antenna ports. Such an association may be configured as a transmission configuration indicator (TCI) state. The WTRU may be indicated the association between the CSI-RS or SS block and the DM-RS by an index into a set of TCI states configured by the RRC and / or signaled by the MAC CE. Such an indication may also be referred to as a "beam indication."

[0083] In one embodiment, the WTRU may receive DCI scheduling to receive one or more PDSCHs and / or transmit one or more PUSCHs. The one or more PDSCHs and / or one or more PUSCHs may include a set of low priority PDSCHs / PUSCHs and a set of high priority PDSCHs / PUSCHs. The WTRU may determine the set of low priority PDSCHs / PUSCHs and the set of high priority PDSCHs / PUSCHs based on one or more of the following: (1) an explicit indication, (2) a number of high priority PDSCHs / PUCCHs / PUSCHs, (3) a priority indication per time domain resource allocation (TDRA), (4) a priority indication per frequency domain resource allocation (FDRA), and / or (5) an indication of PUCCH resources for HARQ-ACK and PDSCH-to-HARQ-ACK delay.

[0084] The WTRU may receive an explicit indication of the priority level for one or more PDSCHs and / or associated HARQ-ACKs and / or PUCCHs and / or PUSCHs. For example, the WTRU may receive a bitmap including X bits, where X is equal to the number of PDSCHs and / or PUSCHs. Each bit of the X bits may indicate a priority level of each PDSCH / HARQ-ACK / PUCCH / PUSCH. For example, if a bit = "0", the associated PDSCH / PUCCH / PUSCH may be a low priority PDSCH / PUSCH. If a bit = "1", the associated PDSCH / PUCCH / PUSCH may be a high priority PDSCH / PUSCH. The indication may be based on one or more of RRC, MAC CE, and DCI. In case of a DCI-based indication, the WTRU may be configured with one or more bitmaps, each bitmap may be associated with a respective codepoint of the DCI field (e.g., priority indication for multiple PDSCHs / PUSCHs). The WTRU may receive the codepoint and determine the associated bitmap with the indicated codepoint to determine the priority of the multi-PDSCH / PUSCH.

[0085] The WTRU may receive an indication of the number of high priority (or low priority) PDSCH / PUCCH / PUSCHs (e.g., via DCI and / or MAC CE). For example, the WTRU may receive a first number for the number of high priority PDSCH / PUCCH / PUSCHs. Based on the first number, the WTRU may identify the high priority PDSCH / PUCCH / PUSCH. For example, the WTRU may receive an indication of scheduling of M PDSCHs / PUSCHs and N high priority PDSCHs / PUSCHs. Based on the indicated M and N, the WTRU may determine the priorities of the scheduled PDSCHs / PUSCHs.

[0086] The first (or last) N PDSCHs / PUSCHs may be high priority PDSCHs / PUSCHs, and the remaining M to N PDSCHs / PUSCHs may be low priority PDSCHs / PUSCHs. The WTRU may determine the location of the high priority PDSCHs / PUSCHs based on timeDurationForQCL. For example, if timeDurationForQCL≦PDSCH / PUSCH scheduled offset (e.g., first PDSCH / PUSCH scheduled offset), the WTRU may receive / transmit N high priority PDSCHs / PUSCHs first and M to N high priority PDSCHs / PUSCHs last. If timeDurationForQCL>PDSCH scheduled offset (e.g., first PDSCH / PUSCH scheduled offset), the WTRU may receive / transmit M to N low priority PDSCHs / PUSCHs first and N high priority PDSCHs / PUSCHs last.

[0087] The WTRU may receive a priority indication as part of a TDRA. For example, the WTRU may receive multiple TDRAs, each TDRA including information associated with one PDSCH / PUSCH of multiple scheduled PDSCHs / PUSCHs. Based on the information included in the TDRA, the WTRU may determine a priority of the associated PDSCH / PUSCH. The information included in the TDRA may include one or more of the following: (1) a priority indication, (2) a starting symbol, (3) a length, (4) a slot offset, (5) a starting symbol and length indicator (e.g., a SLIV), (6) a mapping type, (7) a number of repetitions, and / or (8) a waveform type configuration.

[0088] For example, each TDRA may include an associated number of repetitions. The WTRU may apply a different number of repetitions for each PDSCH. For example, the WTRU may receive / transmit A repetitions for a first PDSCH / PUSCH and B repetitions for a second PDSCH / PUSCH based on the associated number of repetitions in the associated TDRA.

[0089] In one embodiment, the WTRU may receive a priority indication as part of a FDRA. For example, the WTRU may receive multiple FDRAs, each FDRA including information associated with one PDSCH / PUSCH of the multiple scheduled PDSCH / PUSCHs. Based on the information, the WTRU may determine a priority of the associated PDSCH / PUSCH. The information may include one or more of the following: (1) a resource block group (RBG) bitmap, (2) a starting RB, and / or (3) a length.

[0090] In one embodiment, the WTRU may receive first and second PUCCH resource indicators for PUCCHs of the first and second priority indexes, respectively. The first indicated PUCCH may carry a HARQ-ACK for a PDSCH of the first priority index, and the second indicated PUCCH may carry a HARQ-ACK for a PDSCH of the second priority index. The WTRU may further receive first and second PDSCH-HARQ-ACK delay indications indicating timing of the first and second PUCCH transmissions in units of slots or subslots according to the respective first and second PUCCH configurations. If the first and second PUCCHs overlap in time, the WTRU may multiplex the HARQ-ACKs of the first and second priorities in one of the PUCCHs.

[0091] Alternatively, the WTRU may receive a single PUCCH resource indicator for the PUCCH. The indicated PUCCH may multiplex HARQ-ACKs for PDSCHs of the first and second priority indexes. The WTRU may encode the HARQ-ACKs of the first and second priority indexes using the maximum code rate parameters applicable to the first and second priority indexes from the PUCCH configuration corresponding to the indicated PUCCH, provided that the applicable conditions for multiplexing are met. For example, these conditions may be met if the code rates of the HARQ-ACKs of the first and second priority indexes do not exceed their respective configured maximum code rates. If the conditions are not met, the WTRU may transmit only the HARQ-ACK of the highest priority index in the PUCCH.

[0092] The WTRU may be scheduled to receive one or more downlink / uplink channels and / or signals. One or more scheduling parameter sets used in the BWP may be determined based on the determined priorities used for each PDSCH / PUSCH. The scheduling parameter sets may include at least one or more of the following: MCS level, modulation order, minimum / maximum scheduling bandwidth, DMRS density, DMRS pattern, frequency resource allocation type, time resource allocation type, number of repetitions, number of slot aggregations, number of slots for TBoMS configuration, and slot length.

[0093] In one embodiment, a first set of scheduling parameters may be used for a PDSCH / PUSCH with a first priority (e.g., low priority) and a second set of scheduling parameters may be used for a PDSCH / PUSCH with a second priority (e.g., high priority).

[0094] The first set of scheduling parameters may include a first number of repetitions and a first type of repetitions, and the second set of scheduling parameters may include a second number of repetitions and a second type of repetitions. For example, the WTRU may receive a DCI that schedules M PDSCHs / PUSCHs and N high priority PDSCHs / PUSCHs of the M PDSCHs / PUSCHs. The WTRU may determine a number of repetitions K for the high priority PDSCHs and a number of repetitions L for the low priority PDSCHs. The WTRU may receive a repetition type indication, which may indicate one or more of "no repetitions", "high priority repetitions", "low priority repetitions", and "repetitions of all PDSCHs / PUSCHs". If no repetitions are indicated, K=1 and L=1. If repetitions for the high priority PDSCHs are indicated, K is a value indicated by the gNB and L=1. If repetitions for the low priority PDSCHs are indicated, K=1 and the base station indicates a value L. If repetition for all PDSCHs is indicated, the base station indicates the values ​​K and L.

[0095] The first set of scheduling parameters may include a first subset of modulation orders (e.g., 64QAM and 256QAM), and the second set of scheduling parameters may include a second subset of modulation orders (e.g., 16QAM and 64QAM).

[0096] When the WTRU is within an active BWP associated with a first waveform, the WTRU expects to receive a PDSCH having one of the modulation orders (or MCS) in the subset associated with the BWP (or waveform).

[0097] The WTRU may re-receive / re-transmit the scheduled PDSCH / PUSCH (e.g., based on repetition) based on one or more of: (1) priority; and / or (2) Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) / Negative Acknowledgement (NACK).

[0098] In one embodiment, the WTRU may re-receive / re-transmit the scheduled PDSCH / PUSCH based on the determined priority. For example, the WTRU may be configured with repetitions of the scheduled PDSCH / PUSCH. Based on this configuration, the WTRU may receive M PDSCH / PUSCHs and scheduling of N high priority PDSCH / PUSCHs among the M PDSCH / PUSCHs. In a first transmission (e.g., based on a first TCI state and / or a first TRP), the WTRU may receive / transmit the scheduled PDSCH / PUSCHs in the scheduled order. In a second transmission (e.g., based on a second TCI state and / or a second TRP), the WTRU may first receive / transmit the N high priority PDSCH / PUSCHs and finally receive / transmit the M-N low priority PDSCH / PUSCHs.

[0099] In one embodiment, the WTRU may send one or more ACK / NACK reports in the middle of multiple PDSCH / PUSCHs. For example, the WTRU may receive M PDSCH / PUSCHs and DCI scheduling N high priority PDSCH / PUSCHs of the M PDSCH / PUSCHs. The WTRU may receive an indication of K repetitions for high priority packets and L repetitions for low priority packets. The WTRU may report an ACK / NACK after X.

[0100] X may be based on one or more indicated PUCCH resources (e.g., in a scheduling DC). X may also be based on a number of repetitions L or K (e.g., in a DCI field or in TDRA and / or FDRA). For example, the WTRU may determine a first number of repetitions associated with L or K (e.g., L / 2 or K / 2, min(L,K)). The WTRU may report an ACK / NACK after X repetitions. X may also be based on a number of PDSCH / PUSCH. For example, the WTRU may determine a first number of receptions / transmissions associated with L or K (e.g., N / 2). The WTRU may report an ACK / NACK after X receptions / transmissions.

[0101] If multiple ACK / NACK reports are supported in the middle of a multi-PDSCH / PUSCH, the WTRU may skip reporting ACK / NACK for PDSCH / PUSCHs that were successfully decoded / transmitted in a previous ACK / NACK report. For example, the WTRU may report a first report for a first PDSCH and a NACK for a second PDSCH. Based on this report, the WTRU may report an ACK / NACK only for the second PDSCH.

[0102] In another example, the WTRU may re-receive / re-transmit the PDSCH / PUSCH based on the WTRU report (e.g., ACK / NACK). For example, the WTRU may be configured with scheduled PDSCH / PUSCH repetitions. Based on this configuration, the WTRU may receive M PDSCH / PUSCHs and scheduling of N high priority PDSCH / PUSCHs among the M PDSCH / PUSCHs. In a first transmission (e.g., based on a first TCI state and / or a first TRP), the WTRU may receive / transmit the scheduled PDSCH / PUSCHs in the scheduled order. In a second transmission (e.g., based on a second TCI state and / or a second TRP), the WTRU may first receive / transmit the N high priority PDSCH / PUSCHs and finally receive / transmit the M-N low priority PDSCH / PUSCHs.

[0103] In another example, in a first transmission (e.g., based on a first TCI state and / or a first TRP), the WTRU may receive / transmit the scheduled PDSCH / PUSCH in the scheduled order. In a second transmission (e.g., based on a second TCI state and / or a second TRP), the WTRU may receive / transmit the failed F PDSCH / PUSCH first (based on a WTRU ACK / NACK). For the remaining MF PDSCH / PUSCH, the WTRU may support one or more of the following: (1) the WTRU may receive / transmit the remaining MF PDSCH / PUSCH last; or (2) the WTRU may not receive / transmit the remaining MF PDSCH / PUSCH, and the WTRU may receive / transmit other signals and / or channels in the time and frequency resources associated with the MF PDSCH / PUSCH.

[0104] In one embodiment, the PDSCH may be configured with different numbers of repetitions. The WTRU may be indicated the number of repetitions as part of the TDRA. For example, the WTRU may be configured with multiple TDRAs, where each TDRA may include information associated with one or more PDSCHs / PUSCHs. The multiple TDRAs may be configured by RRC signaling. Alternatively, the WTRU may be configured with multiple TDRAs by RRC signaling, where a subset of the TDRAs may be activated by the MAC-CE. The WTRU may receive a DCI indicating the codepoints of the TDRAs configured by RRC, or configured and activated by RRC and MAC-CE signaling.

[0105] In an explicit indication, the number of repetitions of each PDSCH / PUSCH may be included separately in the TDRA of each PDSCH / PUSCH. In another example, the TDRA may include a bitmap, where each bit of the bitmap may indicate the number of repetitions of each scheduled PDSCH / PUSCH (e.g., one bit with a bit value of "1" indicating N repetitions and a bit value of "0" indicating M repetitions for the corresponding PDSCH / PUSCH).

[0106] In the implicit indication, the TDRA may include one or more of the following information for each scheduled PDSCH / PUSCH: (1) a SLIV for each PDSCH / PUSCH or multiple SLIVs, each SLIV associated with each PDSCH / PUSCH and its repetition, (2) a starting symbol or multiple starting symbols for each PDSCH / PUSCH, each starting symbol associated with each PDSCH / PUSCH and its repetition, (3) a length or multiple length values ​​for each PDSCH / PUSCH, each length value associated with each PDSCH / PUSCH and its repetition. (4) a slot offset K0 / K2 or multiple K0 / K2 for each PDSCH, each K0 / K2 being associated with a respective PDSCH / PUSCH and its repetition; (5) a mapping type or multiple mapping types for each PDSCH / PUSCH, each mapping type being associated with a respective PDSCH / PUSCH and its repetition; (6) a priority level for each PDSCH / PUSCH; and / or (7) a priority level for each PDSCH / PUSCH and its repetition indicated / configured for a cancellation indication.

[0107] If the TDRA includes a priority level for each PDSCH / PUSCH, the priority level indicated for each PDSCH may implicitly indicate the number of repetitions, e.g., if two priority levels, high and low, are indicated by 1 and 0, 1 corresponds to the number of repetitions N and 0 corresponds to the number of repetitions M.

[0108] If the TDRA includes the priority level of each PDSCH / PUSCH and its repetitions indicated / configured for cancellation indication, each repetition of the PDSCH / PUSCH may be assigned a priority level as part of the TDRA to indicate the applicability of the cancellation indication (CI). For example, if the TDRA determined for multiple PDSCH / PUSCHs scheduled by a single DCI indicates N priority levels to indicate the applicability of the CI, the number of repetitions is N.

[0109] The WTRU may receive a DCI. The DCI may carry information regarding the TDRA codepoint. One or more PDSCH / PUSCHs may be repeated across time and / or frequency, and the WTRU may determine scheduling information for each of the allocated time and frequency RBs from the corresponding DCI. This scheduling information may carry TCI states that associate the scheduled PDSCH / PUSCH with one or more Transmission Reception Points (TRPs) and / or panels. Multi-TRP / panel operation may be used to repeat the PDSCH / PUSCH in the time and / or frequency domain.

[0110] One or more scheduling schemes for multi-TRP PDSCH / PUSCH repetitions may be used, defined, configured, or determined. A PDSCH may be transmitted from one TRP and / or panel and repeated by another TRP and / or panel. A PUSCH may be transmitted from a WTRU to one or more TRPs and / or gNB panels. One or more repetition mappings may be used, defined, configured, or determined.

[0111] Figure 4 illustrates an example multi-PDSCH scheduling for multi-TRP transmission with different TCI state mapping patterns (TCI-MP) when the number of repetitions is equal to 2. TCI-MP1 410 in Figure 4 illustrates cyclic mapping where a first and a second TCI state are applied to a first PDCCH occasion 412 and a second PDSCH occasion 414, respectively, and the same mapping pattern is followed for the remaining PDSCH Tx occasions.

[0112] Sequential mapping is shown in TCI-MP2 430 and TCI-MP3 450. In sequential mapping, a first TCI state is applied to a number and / or group of PDSCH occasions.

[0113] In TCI-MP2 430, a first TCI is applied to a first PDSCH occasion 432 and a second PDSCH occasion 434. The second TCI state is applied to a like number and / or group of PDSCH / PUSCH occasions and the same mapping pattern is followed for the remaining PDSCH / PUSCH occasions. In TCI-MP3 450, the first TCI is applied to at least a first PDSCH occasion 452, a PDSCH occasion 454, a PDSCH occasion 456, and a PDSCH occasion 458. The second TCI state is applied to a like number and / or group of PDSCH / PUSCH occasions and the same mapping pattern is followed for the remaining PDSCH / PUSCH occasions.

[0114] For operation with shared spectrum channel access, Listen Before Talk (LBT) is mandatory in many areas. Therefore, Clear Channel Assessment (CCA) may be performed before every single transmission using energy sensing. Considering the transmission of PDSCH / PUSCH blocks, the Node B may transmit only when it successfully senses that the channel is idle. The Node B may then transmit for a duration up to the Channel Occupancy Time (COT), which is determined based on the priority class.

[0115] Delay duration T d is the duration T f = 16us, followed immediately by m p Successive slot durations follow, with each slot duration being T sl = 9us, T f is the start time T f , the idle slot duration T sl Therefore, the minimum length of the LBT is 25 μs.

[0116] During channel occupancy, transmission gaps of 25 μs or less are permitted and are counted in the channel occupancy time. Channel occupancy time may be used by the base station and the corresponding WTRU through downlink or uplink transmission bursts, respectively. A transmission burst refers to a set of transmissions without gaps greater than 16 μs. If the gap exceeds the 16 μs limit, the transmission may continue in a separate transmission burst after sensing that the channel is clear / idle.

[0117] Hereinafter, operation with or without shared spectrum channel access may be used interchangeably with unlicensed band or licensed band, respectively. The term unlicensed spectrum may be used to refer to license-exempt spectrum and lightly licensed spectrum.

[0118] When operating at high frequencies in unlicensed bands, switching between multiple TRPs during downlink transmission and sub-slot level and / or slot level repetition in the time domain may result in frequent LBT requirements. Also, COT limitations may be considered when prioritizing the scheduling of multiple PDSCH transmissions. Thus, a method may be considered that considers COT and missing PDSCH due to LBT failure.

[0119] In one embodiment, the WTRU may determine that one or more of the scheduled PDSCH / PUSCHs are not received / transmitted (e.g., due to an LBT failure) at the scheduled time and / or frequency RB. In one example, the WTRU may determine that one or more PDSCH / PUSCHs associated with a first TCI state (e.g., a first TRP and / or panel) were not received at the scheduled time and / or frequency RB. For example, in TCI-MP3 450 of FIG. 4, the WTRU may determine that PDSCH 2 454 and PDSCH K 458 (e.g., PDSCH4 for K=4) were not received in the corresponding frequency RBs of slot #2 and slot #4, respectively.

[0120] Upon successful channel access from another TCI state (e.g., a second TRP and / or panel), the WTRU may determine that the missing PDSCH / PUSCH may be prioritized to be received with a higher priority. In one example, the WTRU may determine that the order of reception of a PDSCH or transmission of a PUSCH from a second TCI state (e.g., a second TRP and / or panel) is to receive the missing PDSCH / PUSCH first, followed by a repetition of the PDSCH / PUSCH received at the time and / or frequency RB scheduled during PDSCH reception from the first TCI state, e.g., the first TRP and / or panel. For example, in TCI-MP3 450 of FIG. 4, the order may be PDSCH 2 454, PDSCH K 458 (e.g., PDSCH 4 in an example where K=4), then PDSCH 1 452 and PDSCH 3 456.

[0121] One or more TCI state mapping types may be used, defined, configured, or determined. For example, as seen in Figure 4, the WTRU may be configured with TCI-MP1 410, TCI-MP2 430, and / or TCI-MP3 450. The WTRU may receive an indication from a Node B of which TCI state mapping to use, e.g., RRC, MAC CE, and / or DCI.

[0122] In one embodiment, one or more limits and / or thresholds may be used, defined, configured, or determined for the time remaining in the COT initiated by the corresponding Node B (e.g., TRP / Panel). The limits and / or thresholds for the time remaining may be based on a number of slots, symbols, and / or (pre-)configured time periods. The limits and / or thresholds may be mutually exclusive with respect to another limit and / or threshold.

[0123] In one embodiment, the WTRU may determine a TCI state mapping based on an association with limits and / or thresholds for the time remaining in the COT. In one example, a first limit and / or threshold for the time remaining in the COT may be associated with a first TCI state mapping type, a second limit and / or threshold for the time remaining in the COT may be associated with a second TCI state mapping type, and so on.

[0124] In one example, the WTRU may determine TCI-MP3 450 of Figure 4, which has higher priority than other TCI state mappings when only a limited number of slots remain in the COT (e.g., four slots remain). In another example, the WTRU may determine TCI-MP2 430 of Figure 4, which has higher priority than other TCI state mappings when only a limited number of slots remain in the COT (e.g., two slots remain).

[0125] Alternatively, one or more priority levels and / or types may be used, defined, configured, or determined for the scheduled PDSCH. The WTRU may receive an indication from a Node B (e.g., RRC, MAC CE, and / or DCI) regarding the priority level and / or type for the PDSCH scheduled transmission.

[0126] In one embodiment, one or more limits and / or thresholds may be used, defined, configured, or determined based on the priority level and / or type of the scheduled PDSCH / PUSCH. Thus, the WTRU may determine the TCI state mapping type in relation to the limits and / or thresholds on the PDSCH / PUSCH priority level and / or type.

[0127] In one example, a first limit and / or threshold on priority level and / or type for scheduled PDSCH / PUSCH may be associated with a first TCI state mapping type, a second limit and / or threshold on priority level and / or type for scheduled PDSCH / PUSCH may be associated with a second TCI state mapping type, etc. The thresholds may be based on the priority level and / or type, the number of different priority levels and / or types scheduled, and / or the number of scheduled PDSCH / PUSCHs with higher priority levels and / or types.

[0128] In one embodiment, the WTRU may determine the TCI state mapping type based on the number of configured priority levels for multiple scheduled PDSCH / PUSCHs. For example, if the number of PDSCH / PUSCHs with different priority levels is greater than a configured threshold (e.g., 4), the WTRU may determine the TCI state mapping type associated with that threshold (e.g., TCI-MP3 450 in FIG. 4).

[0129] In one embodiment, the WTRU may determine the TCI state mapping type based on the number of scheduled PDSCH / PUSCHs configured with higher priority levels. For example, if the number of PDSCHs with higher priority is greater than a threshold, e.g., 4, the WTRU may determine the TCI state mapping type associated with that threshold (e.g., TCI-MP3 450 in FIG. 4).

[0130] In another embodiment, one or more priority levels and / or types may be used, defined, configured, or determined for PDSCH reception / PUSCH transmission from a second TCI state (e.g., a second TRP and / or panel) when a respective PDSCH reception / PUSCH transmission from a first TCI state (e.g., for a first TRP and / or panel) is missed (e.g., due to an LBT failure). In one example, the WTRU may determine that one or more PDSCHs associated with a first TCI state, e.g., for a first TRP and / or panel, were not received at a scheduled time and / or frequency RB.

[0131] Upon successful channel access from another TCI state (e.g., for a second TRP and / or panel), the WTRU may determine that there are one or more priority types and / or levels associated with the missing PDSCH / PUSCH. Thus, for example, the order of transmission of the missing PDSCH / PUSCH from the second TCI state for the second TRP and / or panel may be based on the respective priority types and / or levels. In one example, the WTRU may determine that the order of PDSCH reception or PUSCH transmission from the second TCI state (e.g., for the second TRP and / or panel) is to first receive the missing PDSCH / PUSCH with the highest priority type and / or level, then receive other missing PDSCH / PUSCH with lower priority type and / or level, and then repeat the PDSCH / PUSCH received at the scheduled time and / or frequency RB during the PDSCH reception / PUSCH transmission from the first TCI state, e.g., the first TRP and / or panel.

[0132] For example, the WTRU may determine that PDSCH2 and PDSCH4 were not received from a first TCI state (e.g., a first TRP and / or panel) in corresponding frequency RBs in slot #2 and slot #4, respectively, of TCI-MP3 of Figure 4. In one example, the WTRU may determine that PDSCH4 has a higher priority type and / or level compared to PDSCH2. Thus, the WTRU may determine that the order of receiving PDSCHs from a second TCI state, e.g., a second TRP and / or panel, may be a repetition of PDSCH4, PDSCH2, then PDSCH1 and PDSCH3 in TCI-MP3 of Figure 4.

[0133] In another embodiment, one or more TDRA configuration types may be used, defined, configured, or determined. In a first TDRA configuration, the WTRU may be configured with consecutive PDSCH slots without a slot-level gap. In a second TDRA configuration, the WTRU may be configured with a slot-level gap between scheduled PDSCH slots. In one example, the WTRU may receive an indication from a Node B, e.g., RRC, MAC CE, and / or DCI, of which TDRA configuration to use.

[0134] In one embodiment, the WTRU may receive one or more configurations to use, transmit, and / or occupy gap slots for uplink transmissions without LBT, e.g., SRS, PUSCH, and / or PUCCH. The transmission and / or channel occupancy duration may be limited in time. One or more of the following may apply: (1) MCOT duration, (2) scheduled time resource, (3) preconfigured time period, and / or (4) frame duration.

[0135] In the case of an MCOT duration, the WTRU may transmit and / or occupy a channel up to the extent of an available COT, which is initiated by a first or second TRP and / or panel associated with the first or second TCI state, respectively.

[0136] In the case of scheduled time resources, the WTRU may transmit and / or occupy the channel up to the extent of gap slots between scheduled PDSCH transmissions and / or repetitions from the first or second TRP and / or panel associated with the first or second TCI state, respectively.

[0137] For preconfigured time periods, the WTRU may be configured to transmit and / or occupy a channel based on a predefined and / or configured period.

[0138] For frame duration, the WTRU may transmit and / or occupy the channel up to a range of number of slots and / or symbols and / or number of slots until the next Fixed Frame Period (FFP) LBT opportunity / idle period in a Frame Based Equipment (FBE) frame configuration.

[0139] In another embodiment, the WTRU may transmit and / or occupy a gap slot without an LBT after successfully detecting PDSCH occupancy from a TRP and / or panel with a corresponding QCL index. The WTRU may determine to use a spatial filter for uplink transmission in association with the QCL index of the corresponding TRP and / or panel.

[0140] The transmission and / or channel occupancy may be conditional on one or more of the following: (1) MCOT duration, (2) scheduled PDSCH, and (3) frame configuration.

[0141] For the MCOT duration, the WTRU may determine that the remaining time in the COT initiated by the corresponding TRP / panel for PDSCH transmission is greater than a (pre-)configured time threshold.

[0142] In the case of a scheduled PDSCH, the WTRU may determine that the remaining time in number of slots and / or symbols until the next scheduled PDSCH transmission from the corresponding TRP / panel is greater than a (pre-) configured time threshold.

[0143] For a frame configuration, the WTRU may determine that the remaining time in number of slots and / or symbols and / or number of slots until the next fixed frame period (FFP) LBT opportunity / idle period in a frame-based equipment (FBE) frame configuration is greater than a (pre-) configured time threshold.

[0144] The WTRU may receive a DCI that may include scheduling information for one or more PDSCHs, where each PDSCH may carry a transport block (TB). The scheduling information may include a TCI state associated with one or more PDSCHs. When the scheduling offset of a PDSCH among the one or more PDSCHs is less than timeDurationForQCL, a default beam (e.g., the TCI state of the CORESET with the lowest CORESET-id in the slot) may be used for the PDSCH. Otherwise, an indicated beam (e.g., the TCI state in the DCI) may be used for the PDSCH.

[0145] One or more PDSCHs scheduled by a DCI may be associated with different TCI states, for example, a first set of PDSCHs may be associated with a default beam and a second set of PDSCHs may be associated with an indicated beam in the DCI.

[0146] In one embodiment, different MCS levels may be used for a first set of PDSCHs (e.g., associated with a default beam) and a second set of PDSCHs (e.g., associated with an indicated beam in the DCI). For example, a first MCS level may be used for the first set of PDSCHs and a second MCS level may be used for the second set of PDSCHs, where the first MCS level and the second MCS level may be determined based on one or more of the following, as described below:

[0147] The first MCS level may be indicated in the associated DCI, and the second MCS level may be determined based on an offset from the first MCS level. The offset may be indicated via higher layer signaling (e.g., RRC, MAC-CE) or L1 signaling (e.g., within the associated DCI). The offset may be implicitly indicated by an RNTI scrambled on the CRC of the associated DCI. The offset may be determined based on a scheduling parameter (e.g., allocated frequency resources).

[0148] The codepoint of the MCS indication field may indicate a first MCS level and a second MCS level.

[0149] Two stages of DCI may be used. For example, a first stage DCI may include scheduling information for one or more scheduled PDSCHs and an MCS level for a first set of PDSCHs, and a second stage DCI may include an MCS level for a second set of PDSCHs. The first stage DCI may be monitored in an associated search space, and the second stage DCI may be monitored or received in one of the first set of PDSCHs. For example, the second stage DCI may be a portion of the PDSCH resources in the first set of PDSCHs.

[0150] In another embodiment, different DM-RS patterns and / or densities may be used for the first set of PDSCHs and the second set of PDSCHs. In one example, a WTRU may be indicated with a first DM-RS configuration (e.g., pattern, density, number of DM-RS symbols, DMRS type) that may be associated with the first set of PDSCHs and a second DM-RS configuration that may be associated with the second set of PDSCHs. When the WTRU receives and / or decodes one or more PDSCHs scheduled by the DCI, the WTRU may determine a DMRS for the first set of PDSCHs based on the first DM-RS configuration, and the WTRU may determine a DMRS for the second set of PDSCHs based on the second DM-RS configuration. In another example, the first DMRS for the first set of PDSCHs may be configured via higher layer signaling for BWP, and the second DMRS for the second set of PDSCHs may be determined in response to the DM-RS configuration of the first DMRS. The first DM-RS configuration may have a higher DM-RS density than the second DM-RS configuration, or vice versa.

[0151] In another embodiment, a different number of layers (e.g., ranks) may be used for the first set of PDSCHs and the second set of PDSCHs. For example, a first rank may be used for the first set of PDSCHs and a second rank may be used for the second set of PDSCHs. One or more of the following may apply: (1) the first rank may be predefined as rank=1, (2) the first rank may be determined based on an offset from the second rank (e.g., first rank=max(1, second rank−1)), and / or (3) the first rank may be determined based on the rank of the CORESET for which the TCI state is determined as the default beam.

[0152] In one embodiment, the WTRU may receive a configuration of one or more code points for a TCI state indication, where each code point may be associated with one or more TCI states. The WTRU may receive the code points for the TCI state indication (e.g., based on one or more of RRC, MAC CE, and DCI) for transmitting / receiving signals and / or channels (e.g., PDSCH / PUSCH / RS). The TCI state indication may be used to indicate one or more TCI states for multiple channels (e.g., PDSCH / PUSCH) scheduled by a single DCI.

[0153] When one TCI state is associated with the indicated code point, the WTRU may transmit / receive multiple signals and / or channels with the indicated TCI state. When more than one TCI state is associated with the indicated code point (e.g., for multi-TRP transmission) and inter-slot repetition is configured (e.g., by configuring RRC parameters repetitionNumber and tdmSchemeA), the WTRU may receive / transmit multiple PDSCH / PUSCH scheduled by a single DCI with inter-slot repetition. For example, the WTRU may transmit / receive multiple PUSCH / PDSCH by using a TCI state per slot based on one or a combination of TCI state mapping patterns (TCI-MP) 1, 2, or 3 in FIG. 4.

[0154] In TCI-MP1, the first TCI state and the second TCI state are rotated and assigned to the scheduled slot PDSCH / PUSCH. Furthermore, TDRA schedules the first and second reception / transmission of PDSCH / PUSCH in adjacent slots as shown in the figure. TCI-MP2 rotates the TCI state every two slots. However, TDRA schedules PDSCH / PUSCH with one slot gap as shown in Figure 4. In TCI-MP3, the TCI state switching is done from one iteration to another, and TDRA schedules all scheduled PDSCH / PUSCH in adjacent slots as shown in Figure 4.

[0155] The WTRU may determine a TCI state mapping pattern for multiple channels (e.g., PDSCH / PUSCH) and / or signals scheduled by a single DCI based on one or more of the following embodiments as described below.

[0156] In one example, the TCI state mapping pattern may be configured by RRC signaling. For example, the WTRU may receive the configuration of one or more of TCI-MP1, TCI-MP2, and TCI-MP3 via an RRC message.

[0157] In another example, the TCI state mapping pattern may be indicated by a MAC-CE or a DCI, for example, the WTRU may receive an indication of one or more of TCI-MP1, TCI-MP2, and TCI-MP3 via a MAC CE and / or a DCI.

[0158] In another example, the WTRU may determine a TCI state mapping pattern based on the TDRA, For example, each TDRA may be associated with a TCI state mapping pattern.

[0159] In another example, the WTRU may determine a TCI state mapping pattern for multiple channels (e.g., PDSCH / PUSCH) and / or signals scheduled by a single DCI based on the number of scheduled channels (e.g., PDSCH / PUSCH) and / or signals. For example, when the number of scheduled PDSCHs is smaller, the WTRU may use TCI-MP3 rather than TCI-MP1 to obtain additional time diversity.

[0160] In another example, the WTRU may determine a TCI state mapping pattern for multiple channels (e.g., PDSCH / PUSCH) and / or signals scheduled by a single DCI based on the maximum number of beam changes the WTRU can perform within a slot (maxNumberRxTxBeamSwitchDL). For example, if the maxNumberRxTxBeamSwitchDL reported by the WTRU is lower than a threshold, the WTRU may use TCI-MP3 or TCI-MP2 instead of TCI-MP1, which requires one TCI state switch (beam switch) after each slot.

[0161] In another example, the WTRU may determine a TCI state mapping pattern for multiple channels (e.g., PDSCH / PUSCH) and / or signals scheduled by a single DCI based on timeDurationForQCL and a scheduling offset. The WTRU may unify the impact of using a default beam for PDSCH / PUSCH received / transmitted before timeDurationForQCL by selecting an appropriate TCI state mapping pattern and TDRA. For example, consider the case where K=4, N=2, K0=1 for the first PDSCH, and no slot-level gap is allowed between PDSCH transmissions and repetitions. If timeDurationForQCL expires at slot #4, TCI-MP3 is preferred over TCI-MP1 because in TCI-MP1, two repetitions of PDSCH1 and PDSCH2 are received by the WTRU with the default TCI state. Also, two repetitions of PDSCH3 and PDSCH4 are received by the WTRU with the indicated TCI state. However, in TCI-MP3, one repetition of every scheduled PDSCH is received by the WTRU with the default TCI state, and the remaining repetitions are received by the WTRU with the indicated TCI state, which can avoid performance loss due to using the default QCL assumption before timeDurationForQCL significantly impacts some PDSCHs.

[0162] Figure 5 shows an example TCI state mapping based on TDRA. If slot level gaps are configured by TDRA for multiple scheduled PDSCH / PUSCH, these slots are skipped by the TCI state mapping pattern. For example, as shown in Figure 5, in the case of TCI-MP3, the number of scheduled PDSCHs is 4 (i.e., K=4), and the number of repetitions is 2 (i.e., N=2), if TDRA configures a one-slot gap in slot 3 502, the TCI state mapping pattern also skips slot 3 502.

[0163] When a subslot-level TDM replenishment scheme is configured, the WTRU may use TCI state mapping patterns 1, 2, and 3, but with multiple PDSCHs in each slot based on TDRA. For example, if two PDSCHs are scheduled in each slot and the WTRU is configured with TCI-MP3, PDSCH1 and PDSCH2 are received by the WTRU on the first subslot of slot 1 with the first TCI state and the second subslot of slot 1 with the second TCI state, respectively. The third and fourth PDSCHs are then scheduled in slot 2 following the same pattern adopted in scheduling PDSCH1 and PDSCH2 in slot 1. This pattern continues until all scheduled PDSCHs are assigned.

[0164] If the WTRU is scheduled with more than two repetitions (N>2), the WTRU may receive K PDSCH schedules in N repetitions by repeatedly using TCI state mapping pattern 1 and TCI state mapping pattern 3.

[0165] 6 is a diagram illustrating an example TCI state mapping using TCI-MP1, where N>2 and is an even number. As shown in FIG. 6, when N=4, the same TCI state mapping pattern can be continued continuously until the required number of iterations is achieved.

[0166] FIG. 7 illustrates an example TCI state mapping with TCI-MP1, where N>2 and odd. As shown in FIG. 7, when N>2 and odd, the first N-1 iterations may follow the TCI state mapping pattern described in case 1 (TCI-MP1, N>2 and even). The WTRU may follow one of the following two options shown in FIG. 7 for the Nth iteration of the PDSCH / PUSCH. In option 710, the TCI state mapping pattern continues by changing between the first TCI state and the second TCI state until all scheduled PDSCH / PUSCH repetitions / transmissions are assigned a TCI state. In option 730, the Nth iteration of the PDSCH / PUSCH selects either the first TCI state or the second TCI state for all PDSCH / PUSCH.

[0167] 8 is a diagram illustrating an example TCI state mapping using TCI-MP3, where N>2. As shown in FIG. 8, when N>2, the alternating TCI states from one iteration to the next can continue for N=3 and N=4.

[0168] The WTRU may receive / transmit multiple PDSCH / PUSCHs scheduled by a single DCI with repetition using the TCI state for each PDSCH / PUSCH based on one of a mapping pattern and frequency hopping to obtain frequency diversity.

[0169] For example, Figure 9 illustrates an example multi-PDSCH scheduling for multi-TRP transmission with repetition and frequency hopping. As shown in Figure 9, frequency hopping may be performed when K=2 and N=4.

[0170] In one embodiment, the WTRU may determine a time domain resource allocation for transmitting / receiving multiple channels (e.g., PUSCH / PDSCH) and / or signals via a single DCI with repetition. The operation mode may be based on one or more of the following: (1) SLIV, (2) the length of each channel (e.g., PDSCH / PUSCH), and / or (3) a channel (e.g., PDSCH / PUSCH) scheduling offset (e.g., K0).

[0171] If the WTRU makes a decision based on the SLIV, the WTRU may receive an indication of only one SLIV for each PDSCH as part of the TDRA when the MCS of all repetitions of the PDSCH is the same, and the WTRU may decide to use the indicated SLIV for receiving all repetitions of the PDSCH. The WTRU may receive an indication of the SLIV for each repetition of the PDSCH as part of the TDRA when each repetition is configured with a different MCS.

[0172] If the WTRU makes its decision based on the length of each channel, then the WTRU may be indicated only one length value for each PDSCH as part of the TDRA when all repetitions of the PDSCH have the same MCS, and the WTRU may receive all repetitions of the PDSCH using this length value. The WTRU may be indicated one length value per repetition of the PDSCH as part of the TDRA when each repetition is configured with a different MCS.

[0173] If the WTRU makes the decision based on the channel scheduling offset, a slot level gap may be allowed between PDSCHs. The WTRU may be indicated one K0 value for each repetition of the PDSCH as part of the TDRA. The reference slot for the subsequent transmission of the PDSCH may be the slot where the DCI is received to schedule the PDSCH (one of the PDSCHs in the case of multiple DCI based multiple TRPs) or one of the PDSCHs transmitted in the previous repetition (e.g., the last PDSCH transmitted in the previous repetition when TCI-MP3 is used). The WTRU may determine the slot in which the PDSCH repetition is transmitted based on the reference to K0 and the K0 indicated for each repetition as part of the TDRA.

[0174] If the WTRU makes a decision based on a channel scheduling offset, slot level gaps may not be allowed between PDSCHs. Slot level gaps are not allowed between all slots of a given iteration (first transmission, second transmission, etc.) in which a PDSCH is transmitted. The WTRU may receive one K0 value per PDSCH as part of the TDRA indicating the slot in which the first transmission of the corresponding PDSCH is scheduled. The WTRU may determine the slot in which a subsequent transmission of the PDSCH is scheduled based on the number of scheduled PDSCHs and the K0 indicated by the TDRA.

[0175] Any of the above embodiments described for PDSCH transmission are also applicable to PUSCH transmission. Any of the above embodiments described for PUSCH transmission are also applicable to PDSCH transmission.

[0176] Although the features and elements are described above in certain combinations, one skilled in the art will understand that each feature or element may be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a UE, a WTRU, a terminal, a base station, an RNC, or any host computer.

Claims

1. 1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving downlink control information (DCI), the DCI including a multi-physical downlink shared channel (PDSCH) priority indication; determining a priority for each of two or more PDSCH transmissions based on the multi-PDSCH priority indication; determining one or more scheduling parameters for each of the two or more PDSCH transmissions based on the determined priority of each of the two or more PDSCH transmissions; and receiving each of the two or more PDSCH transmissions using the respective determined scheduling parameters.

2. 2. The method of claim 1, wherein the multi-PDSCH priority indication indicates a number of high priority PDSCH transmissions, the high priority PDSCH being transmitted before a low priority PDSCH transmission.

3. 2. The method of claim 1, wherein the DCI includes a bitmap indicating the priority of each of the two or more PDSCH transmissions.

4. 2. The method of claim 1, wherein the one or more scheduling parameters are at least one of a repetition number, a time position, a demodulation reference signal (DMRS) pattern, a DMRS density, and a modulation and coding scheme (MCS).

5. The method of claim 1 , further comprising associating a first scheduling parameter with a first priority and associating a second scheduling parameter with a second priority.

6. The method of claim 5 , wherein the first priority is a high priority and the second priority is a low priority.

7. 1. A wireless transmit / receive unit (WTRU), comprising: A transceiver; A processor, The transceiver and the processor receiving downlink control information (DCI), the DCI including a multi-PDSCH priority indication; determining a priority for each of two or more PDSCH transmissions based on the multi-PDSCH priority indication; determining one or more scheduling parameters for each of the two or more PDSCH transmissions based on the determined priority of each of the two or more PDSCH transmissions; The WTRU is configured to receive each of the two or more PDSCH transmissions using a respective one of the determined scheduling parameters.

8. 8. The WTRU of claim 7, wherein the multi-PDSCH priority indication indicates a number of high priority PDSCH transmissions, the high priority PDSCH transmissions being transmitted before low priority PDSCH transmissions.

9. The WTRU of claim 7, wherein the DCI includes a bitmap indicating the priority of each of the two or more PDSCH transmissions.

10. 8. The WTRU of claim 7, wherein the one or more scheduling parameters are at least one of a repetition number, a time position, a demodulation reference signal (DMRS) pattern, a DMRS density, and a modulation and coding scheme (MCS).

11. The WTRU of claim 7, further comprising associating a first scheduling parameter with a first priority and associating a second scheduling parameter with a second priority.

12. The WTRU of claim 11 , wherein the first priority is a high priority and the second priority is a low priority.

13. 1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving downlink control information (DCI), the DCI including a multi-physical uplink shared channel (PUSCH) priority indication; determining a priority for each of two or more PUSCH transmissions based on the multi-PUSCH priority indication; determining one or more scheduling parameters for each of the two or more PUSCH transmissions based on the determined priority of each of the two or more PUSCH transmissions; transmitting each of the two or more PUSCH transmissions using a respective one of the determined scheduling parameters.

14. 14. The method of claim 13, wherein the multi-PUSCH priority indication indicates a number of high priority PUSCH transmissions, the high priority PUSCH transmissions being transmitted before a low priority PUSCH.

15. The method of claim 13 , wherein the DCI includes a bitmap indicating the priority of each of the two or more PUSCH transmissions.

16. 14. The method of claim 13, wherein the one or more scheduling parameters are at least one of a repetition number, a time position, a demodulation reference signal (DMRS) pattern, a DMRS density, and a modulation and coding scheme (MCS).

17. 14. The method of claim 13, further comprising associating a first scheduling parameter with a first priority and associating a second scheduling parameter with a second priority.

18. 20. The method of claim 17, wherein the first priority is a high priority and the second priority is a low priority.

Images