Method and apparatus for timeline management for unified TCI displays

Abstract

Disclosed are methods, apparatus, and procedures for timeline management for transmission configuration indication in wireless communications. For example, the method, performed by a wireless transmit / receive unit (WTRU), includes receiving configuration information indicating a set of transmission configuration indicator (TCI) states, a beam application time (BAT), and a BAT offset, receiving downlink control information (DCI) indicating scheduling of a downlink data transmission and a TCI state from the set of TCI states, and transmitting a transmission using the indicated TCI state, the transmission being transmitted at a time offset associated with at least the BAT and / or the BAT offset after transmitting hybrid automatic repeat request (HARQ) feedback associated with the downlink data transmission.

Description

[Technical Field]

[0001] The present application relates to a method and apparatus for timeline management for a unified TCI display. [Background technology]

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 411,475, filed in the U.S. Patent and Trademark Office on September 29, 2022, and U.S. Provisional Patent Application No. 63 / 465,747, filed in the U.S. Patent and Trademark Office on May 11, 2023, the entire contents of each of which are incorporated herein by reference in their entirety and for all applicable purposes as if fully set forth below.

[0003] In some cellular / wireless standards (e.g., 3GPP Release 16, Release 17, Release 18, and / or later), the ongoing evolution of 5G New Radio (NR) may continue to optimize management of wireless communications and enhance performance.

[0004] 3GPP Release 17 supports a unified transmission configuration indicator (TCI) framework. For example, a unified TCI (e.g., separate DL / UL joint or pair) may be indicated and / or maintained at a wireless transmit / receive unit (WTRU) applicable to both control and / or data channels simultaneously. This differs from individual beam control per channel (e.g., up to 3GPP Release 16).

[0005] In 3GPP Release 16 and / or 17, multiple transmit / receive points (MTRPs) are supported. As an example, multiple DCI-based MTRP (MDCI-MTRP) supports eMBB based on CORESETPoolIndex=0 or 1. As another example, single DCI-based MTRP (SDCI-MTRP) is based on associating up to two TCI states with codepoints in the TCI field of the DCI, allowing repeated transmissions across multiple TRPs to achieve improved reliability.

[0006] One relevant aspect is captured in 3GPP Release 18 by MIMO WID (Non-Patent Document 1), which specifies extensions to the Rel-17 unified TCI framework to focus on multi-TRP use cases and provide indication of multiple DL and UL TCI states using the Rel-17 unified TCI framework. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] 3GPP RP-213598 Summary of the Invention

[0008] FIELD OF THE INVENTION One or more embodiments disclosed herein relate to methods, apparatus, and procedures for timeline management for TCI indication in wireless communications (e.g., 5G NR networks).

[0009] In one embodiment, a method performed by a wireless transmit / receive unit (WTRU) for wireless communication includes receiving configuration information indicating a set of transmission configuration indicator (TCI) states, a beam application time (BAT), and a BAT offset. The method includes receiving downlink control information (DCI) indicating scheduling of a downlink data transmission and a TCI state from the set of TCI states. The method also includes transmitting a transmission using the indicated TCI state, the transmission being transmitted at a time offset associated with at least the BAT and / or the BAT offset after transmitting hybrid automatic repeat request (HARQ) feedback associated with the downlink data transmission.

[0010] In one embodiment, a method performed by a wireless transmit / receive unit (WTRU) for wireless communication includes receiving configuration information indicating a set of TCI states, a BAT, and a BAT offset. The method includes receiving a DCI indicating scheduling of a downlink data transmission and a TCI state from the set of TCI states. The method also includes receiving a transmission using the indicated TCI state, the transmission being received at a time offset associated with at least the BAT and / or the BAT offset after transmitting HARQ feedback associated with the downlink data transmission.

[0011] In one embodiment, a WTRU for wireless communication, comprising circuitry including a processor, a receiver, a transmitter, and a memory, is configured to: 1) receive configuration information indicating a set of TCI states, a BAT, and a BAT offset; 2) receive DCI indicating scheduling of a downlink data transmission and a TCI state from the set of TCI states; and 3) transmit a transmission using the indicated TCI state, wherein the transmission is transmitted at a time offset associated with at least the BAT and / or the BAT offset after transmitting HARQ feedback associated with the downlink data transmission.

[0012] In one embodiment, a WTRU for wireless communication, comprising circuitry including a processor, a receiver, a transmitter, and a memory, is configured to: 1) receive configuration information indicating a set of TCI states, a BAT, and a BAT offset; 2) receive DCI indicating scheduling of a downlink data transmission and a TCI state from the set of TCI states; and 3) receive a transmission using the indicated TCI state, wherein the transmission is received at a time offset associated with at least the BAT and / or the BAT offset after sending HARQ feedback associated with the downlink data transmission.

[0013] In a representative embodiment, a WTRU is configured with a Beam Application Time (BAT) parameter and a paired / associated “Delta” offset parameter, where the BAT and “BAT plus Delta” may each be associated with a list of channels / signals, where the list of channels / signals may be predefined, determined based on WTRU capabilities, and / or independently configurable by the network (e.g., gNB). In one example, a WTRU may be configured with a BAT associated with a first list of channels / signals and may further be configured with Delta, where the BAT plus Delta may be associated with a second list of channels / signals. In one example, in response to receiving a control command (e.g., via a DCI, via a TCI field of the DCI) at a first time instance (T1) indicating at least one unified TCI (UTCI), the WTRU may determine a second time instance (T2) based on T1 and BAT (e.g., as T1+BAT or as T1+Alpha+BAT), at which time instance the WTRU may update (and / or begin using) the indicated at least one UTCI for a first list of channels / signals, and may not update (at T2) the indicated at least one UTCI for other channels / signals not included in the first list. In one example, the WTRU may determine a third time instance (T3) based on T1, BAT, and Delta (e.g., as T1+BAT+Delta or as T1+Alpha+BAT+Delta), at which time instance the WTRU may update (and begin using) the indicated at least one UTCI for the second list of channels / signals, and may not update (at T3) the indicated at least one UTCI for other channels / signals not included in the second list.

[0014] In a representative embodiment, the WTRU determines that the time offset is BAT if (or based on) the type of the channel (or signal) is a first type of channel (or signal) or is included in a first set of channel (or signal) types. The WTRU may determine that the time offset is BAT plus BAT offset if the type of the channel or signal is a second type of channel or signal or is included in a second set of channel or signal types. In one example, the WTRU may determine that i) the first type of channel or signal is at least one of SRS or CSI-RS (e.g., for channel acquisition), or a data channel associated with a low-latency related type (e.g., URLLC), and ii) the second type of channel or signal is at least one of PUSCH, PDSCH, or control channel (e.g., CORESET, PDCCH, search space, PUCCH, etc.). [Brief explanation of the drawings]

[0015] A more detailed understanding can be had from the following detailed description, given by way of example in conjunction with the accompanying drawings, in which: Figures in such drawings, like the detailed description, are examples; therefore, the drawings (figures) and detailed description should not be considered limiting, as other equally effective examples are possible and likely. Moreover, like reference numerals in the figures indicate like elements.

[0016] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system. [Figure 1B] 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communication system shown in FIG. 1A. [Figure 1C] 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system shown in FIG. 1A. [Figure 1D]FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system shown in FIG. 1A. [Figure 2] FIG. 10 illustrates an example timeline using beam application time (BAT) or paired / associated offset parameters (Delta) for the indicated UTCI, according to one or more embodiments. [Figure 3] FIG. 1 illustrates an example timeline using BAT or paired / associated offset parameters (Delta) for coherent joint transmission (CJT) operation, according to one or more embodiments. [Figure 4] FIG. 1 illustrates a first example of a management procedure that includes determining a channel or signal type for wireless communications, according to one or more embodiments. [Figure 5] FIG. 10 illustrates a second example of a transmission / reception management procedure that includes determining and using a time offset and channel or signal type for wireless communications, according to one or more embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0017] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. It will be understood, however, that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of, or in combination with, embodiments and other examples explicitly, implicitly, and / or inherently described, disclosed, or otherwise provided herein (collectively, "provided"). Although various embodiments are described and / or claimed herein in which apparatuses, systems, devices, etc., and / or any elements thereof, perform operations, processes, algorithms, functions, etc., and / or any portions thereof, it should be understood that any embodiment described and / or claimed herein contemplates any apparatus, system, device, etc., and / or any elements thereof, configured to perform any operation, process, algorithm, function, etc., and / or any portion thereof.

[0018] Exemplary Communication Systems, Networks, and Devices

[0019] The methods, procedures, apparatus, and systems provided herein are well suited for communications involving both wired and wireless networks. With reference to Figures 1A-1D, an overview of various types of wireless devices and infrastructures is provided, and various elements of the networks may utilize, perform, be positioned, and / or adapted and / or configured accordingly with the methods, apparatus, and systems provided herein.

[0020] 1A is a system diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messaging, broadcasts, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailed (ZT) unique word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, and filter bank multicarrier (FBMC).

[0021] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, radio access networks (RANs) 104 / 113, core networks (CNs) 106 / 115, public switched telephone networks (PSTNs) 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” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include (or be) user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated processing chain), a consumer electronic device, a device operating in a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

[0022] The communications 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 communications networks, such as the CN 106 / 115, the Internet 110, and / or the network 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each shown as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0023] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, sometimes referred to as a cell (not shown). These frequencies may be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectrum. A cell may provide coverage for wireless services in 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 an embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0024] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communications 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).

[0025] More specifically, as noted above, the communication system 100 may be a multiple-access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WTRUs 102a, 102b, 102c in the RAN 104 / 113 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 communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0026] In an 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).

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

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

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), IEEE 802.16 (i.e., Global 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.

[0030] 1A may be, for example, a wireless router, a Home Node-B, a Home eNode-B, or an access point and may utilize any suitable RAT for facilitating wireless connectivity within a localized area, such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In an 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 an 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 an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish either a small cell, a picocell, or a femtocell. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0031] The RAN 104 / 113 can communicate with the CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error resilience requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 can provide call control, billing services, mobile location 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 understood that the RAN 104 / 113 and / or the CN 106 / 115 can communicate directly or indirectly with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0032] The CN 106 / 115 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 Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) in the TCP / IP Internet protocol suite. The network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs that may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0033] 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 that may employ cellular-based wireless technology and a base station 114b that may employ IEEE 802.11 wireless technology.

[0034] 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 elements / peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the above elements while remaining consistent with an embodiment.

[0035] 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 in association with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 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. While FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be incorporated together, for example, in an electronic package or chip.

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

[0037] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an 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.

[0038] The transceiver 120 may be configured to modulate signals to be 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.

[0039] The processor 118 of the WTRU 102 may be coupled to and may receive user input 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. Additionally, 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 in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and may store data in that memory.

[0040] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering 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.

[0041] 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 place of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0042] The processor 118 may further be coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the elements / 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 modulation (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, etc. The elements / peripherals 138 may include one or more sensors, which 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, and / or a humidity sensor.

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

[0044] 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an 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.

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

[0046] Each of the eNode-Bs 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 uplink (UL) and / or downlink (DL), etc. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0047] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the above elements is shown 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.

[0048] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during initial attach 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.

[0049] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions such as anchoring the user plane during inter-eNode-B handovers, 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.

[0050] 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 communication between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0051] 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 landline communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. The CN 106 may also 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.

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

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

[0054] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic within and / or outside the BSS. Traffic to a STA originating from outside the BSS may arrive and be delivered to the STA through the AP. Traffic originating from a STA to a destination outside the BSS may be sent to the AP to be delivered to the respective destination. Traffic between STAs within the BSS may be sent through the AP; for example, a source STA may send traffic to the AP, and the AP may deliver 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 (e.g., directly) between a source STA and a destination STA using 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 the STAs within or using the IBSS (e.g., all of the STAs) may communicate directly with each other. IBSS mode communication is sometimes referred to herein as an "ad hoc" mode of communication.

[0055] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, an AP can transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz bandwidth) or a width that is dynamically set by signaling. The primary channel may be the operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain exemplary embodiments, for example, in an 802.11 system, carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented. In CSMA / CA, STAs (e.g., all STAs), including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. One STA (e.g., only one station) can transmit in a given BSS at any given time.

[0056] High-throughput (HT) STAs may use 40 MHz wide channels for communication, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0057] A very high throughput (VHT) STA can 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 contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or two non-contiguous 80 MHz channels, sometimes referred to as an 80+80 configuration. In the 80+80 configuration, after channel coding, the data may be passed through a segment parser that can split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing may be performed separately for 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 above operations for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0058] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. 802.11af and 802.11ah reduce the channel operating bandwidths and carriers 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 can support meter-type control / machine-type communication (MTC), such as MTC devices, in macro coverage areas. MTC devices may have specific capabilities, including, for example, specific bandwidths and / or limited bandwidth support (e.g., support only that bandwidth). MTC devices may include batteries with above-threshold battery life (e.g., very long battery life).

[0059] WLAN systems capable of supporting 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 largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA that supports the smallest bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, the primary channel may be 1 MHz wide for a STA (e.g., an MTC-type device) that supports 1 MHz mode (e.g., only supports 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) setting may depend on the condition of the primary channel. If the primary channel is busy, for example due to a STA (that only supports 1 MHz operating mode) transmitting to the AP, the entire available frequency band may be considered busy, even though most of the frequency band may remain idle and available.

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

[0061] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 113 may also communicate with the CN 115.

[0062] The RAN 113 may include gNBs 180a, 180b, and 180c, although it will be understood that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, and 180c may implement MIMO technology. For example, the gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, and 102c. Thus, the gNB 180a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, and 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, and the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, and 180c may implement coordinated multipoint (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or 180c).

[0063] 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 various or scalable lengths (e.g., including varying numbers of OFDM symbols and / or lasting for varying lengths of absolute time).

[0064] 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 can communicate with the gNBs 180a, 180b, 180c without accessing any other RANs (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c can utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c can communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with other RANs, such as eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement a DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 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.

[0065] 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 the UL and / or DL, support for network slicing, dual connectivity, 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.

[0066] 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 at least one Data Network (DN) 185a, 185b. While each of the above elements is shown as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0067] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service being utilized by 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 High-Capacity Mobile Broadband (eMBB) access, and / or services for MTC access. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

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

[0069] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface and 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 downlink packets, and providing mobility anchoring.

[0070] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that interfaces between the CN 115 and the PSTN 108. The CN 115 may also 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 an embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (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.

[0071] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to any of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other elements / devices described herein may be performed by one or more emulation elements / 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 functionality.

[0072] 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 communications network to test other devices in the communications 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 communications network. The emulation device may be directly coupled to another device for testing and / or may perform testing using over-the-air wireless communications.

[0073] The one or more emulation devices may perform one or more functions, inclusive, without being implemented / deployed as part of a wired and / or wireless communications network. For example, the emulation devices may be utilized in test laboratories and / or test scenarios in non-deployed (e.g., test) wired and / or wireless communications networks 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, e.g., one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0074] Introduction

[0075] The 3GPP Release 17 (Rel-17) unified TCI framework supports one unified TCI that can be indicated / maintained at the WTRU (or UE) as applicable to both control / data channels simultaneously (e.g., separate DL / UL joint or pair), which differs from individual beam control per channel (e.g., up to 3GPP Rel-16).

[0076] In 3GPP Rel-16 or Rel-17, multiple transmit / receive points (MTRPs) are supported. For example, multi-DCI-based MTRP (MDCI-MTRP) supports eMBB based on CORESETPoollndex=0 or 1. In another example, single-DCI-based MTRP (SDCI-MTRP) is based on associating up to two TCI states with codepoints in the TCI field of the DCI, and achieves improved reliability through repeated transmissions across multiple TRPs.

[0077] One related aspect is captured in 3GPP Release 18 by MIMO WID (e.g., Non-Patent Document 1), which specifies extensions to the Rel-17 unified TCI framework to focus on multi-TRP use cases and provide indication of multiple DL and UL TCI states using the Rel-17 unified TCI framework.

[0078] The continued evolution of 5G New Radio (NR) may continue to optimize wireless communications management and enhance performance. Therefore, it is desirable to 1) improve the unified TCI application timeline by accounting for delay-sensitive channels / signals, 2) improve the robustness of the unified TCI updates in the event of reception errors at the WTRU receiving the unified TCI, and / or 3) improve the accuracy and performance of coherent joint transmission (CJT)-based operations in accordance with or using the unified TCI updates.

[0079] Hereinafter, "a" and "an" and similar words are to be interpreted as "one or more" and "at least one." Similarly, terms ending in the suffix "(s)" are to be interpreted as "one or more" and "at least one." The term "may" is to be interpreted as "for example, may." The forward slash " / " sign, symbol, or mark is to be interpreted as "and / or" unless otherwise noted, for example, "A / B" may mean "A and / or B."

[0080] overview

[0081] beam

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

[0083] The WTRU may transmit a physical channel or signal using the same spatial domain filter as that used to receive a reference signal (RS) (e.g., channel state information (CSI)-RS) or a synchronization signal (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 cases, the WTRU may be considered to transmit the target physical channel or signal according to a spatial relationship with reference to such RS or SS block.

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

[0085] The spatial relationship may be implicit, configured by a radio resource control (RRC) message, or signaled by a MAC control element (CE) or downlink control information (DCI). For example, the WTRU may implicitly transmit the PUSCH and DM-RS of the PUSCH according to the same spatial domain filter as the sounding reference signal (SRS) indicated by an SRS resource indicator (SRI) indicated in the DCI or configured by the RRC. In another example, the spatial relationship may be configured by the RRC for the SRI or signaled by the MAC CE for the PUCCH. Such a spatial relationship may also be referred to as a "beam indication."

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

[0087] unified TCI

[0088] A unified TCI (e.g., common TCI, common beam, common RS, etc.) may refer to a beam / RS used (simultaneously) for multiple physical channels / signals. The term “TCI” may include at least a TCI state that includes at least one source RS to provide a basis (e.g., WTRU assumptions) for determining a QCL and / or spatial filter.

[0089] In one example, the WTRU may receive (e.g., from a gNB) an indication of a first unified TCI used / applied for both the downlink control channel (PDCCH) and the downlink shared channel (PDSCH) (e.g., and further downlink RS). The source reference signal in the first unified TCI may provide common QCL information for at least WTRU-dedicated reception on the PDSCH and all (or a portion) of the CORESET in the CC. In one example, the WTRU may receive (e.g., from a gNB) an indication of a second unified TCI used / applied for both the uplink control channel (PUCCH) and the uplink shared channel (PUSCH) (e.g., and further uplink RS). The source reference signal in the second unified TCI may provide a reference for determining a common UL Tx spatial filter for at least dynamic grant / configured grant-based PUSCH and all (or a portion) of the dedicated PUCCH resources in the CC.

[0090] The WTRU may be configured in a first mode for unified TCI (e.g., SeparateDLULTCI mode), in which the indicated unified TCI (e.g., the first unified TCI or the second unified TCI) may be applicable to either the downlink (e.g., based on the first unified TCI) or the uplink (e.g., based on the second unified TCI).

[0091] In one example, the WTRU may receive (e.g., from the gNB) an indication of a second unified TCI commonly used / applied for the PDCCH, PDSCH, PUCCH, and PUSCH (and DL RS and / or UL RS).

[0092] The WTRU may be configured in a second mode (e.g., JointTCI mode) for unified TCI, in which the indicated unified TCI (e.g., third unified TCI) may be applicable to both the downlink and uplink (e.g., based on the third unified TCI).

[0093] The WTRU may determine the TCI state applicable to transmission or reception by first determining the unified TCI state instance applicable to this transmission or reception, and then determining the TCI state corresponding to the unified TCI state instance. Transmission may consist of at least PUCCH, PUSCH, and SRS. Reception may consist of at least PDCCH, PDSCH, and CSI-RS. The unified TCI state instance may also be referred to as a TCI state group, TCI state process, unified TCI pool, group of TCI states, set of time domain instances / stamps / slots / symbols, and / or set of frequency domain instances / RBs / subbands, etc. The unified TCI state instance may be equivalent to or identified by a Coreset pool identification (e.g., CORESETPoolIndex and / or TRP indicator, etc.).

[0094] Unified TCI may be used interchangeably with one or more of unified TCI state, unified TCI instance, TCI, and TCI state and still be consistent with the present invention.

[0095] TRP, MTRP, M-TRP

[0096] Transmitting and Receiving Point (TRP) may be used interchangeably with one or more of Transmission Point (TP), Receiving Point (RP), Radio Remote Head (RRH), Distributed Antenna (DA), Base Station (BS), Sector (of a BS), and Cell (e.g., a geographic cell area served by a BS) and still be consistent with the present invention. Multi-TRP may be used interchangeably with one or more of MTRP, M-TRP, and Multiple-TRP and still be consistent with the present invention.

[0097] Configuring TRP, SRI, and / or Path Loss (PL) reference signals

[0098] A WTRU may be configured (or may receive a configuration of) one or more TRPs to which the WTRU can transmit and / or from. A WTRU may be configured with one or more TRPs for one or more cells. A cell may be a serving cell or a secondary cell.

[0099] A WTRU may be configured with at least one RS for channel measurement purposes. This RS may be denoted as a channel measurement resource (CMR) and may include CSI-RS, SSB, and / or other downlink RSs transmitted from a TRP to the WTRU. A CMR may be configured in or associated with a TCI state. A WTRU may be configured with CMR groups in which CMRs transmitted from the same TRP may be configured. Each group may be identified by a CMR group index (e.g., group 1). A WTRU may be configured with one CMR group per TRP, and the WTRU may receive links between one CMR group index and another CMR group index, or between one RS index from one CMR group and another RS ​​index from another group.

[0100] The WTRU may be configured (or may receive configurations of) one or more path loss (PL) reference groups (e.g., sets), and / or one or more SRS groups, SRS resource indicators (SRIs), or SRS resource sets.

[0101] A PL reference group may correspond to or be associated with a TRP. A PL reference group may include, identify, correspond to, or be associated with one or more TCI states, SRIs, reference signal sets (e.g., CSI-RS sets, SRI sets), CORESET indices, and / or reference signals (e.g., CSI-RS, SSBs).

[0102] The WTRU may receive a configuration (e.g., any configuration described herein). The configuration may be received from a gNB or a TRP. For example, the WTRU may receive configuration for one or more TRPs, one or more PL reference groups, and / or one or more SRI sets. The WTRU may implicitly determine the association between an RS set / group and a TRP. For example, if the WTRU is configured with two SRS resource sets, the WTRU may determine to transmit on TRP1 with SRS in the first resource set and on TRP2 with SRS in the second resource set. The configuration may be via RRC signaling.

[0103] In the examples and embodiments described herein, the terms TRP, PL reference group, SRI group, and / or SRI set may be used interchangeably. The terms set and group may be used interchangeably herein.

[0104] CSI Components

[0105] The WTRU may report a subset of channel state information (CSI) components, where the CSI components may correspond to at least a CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI), an indication of the panel used for reception at the WTRU (such as panel identification or group identification), measurements such as L1-RSRP, L1-SINR obtained from the SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and other channel state information such as at least a rank indicator (RI), a channel quality indicator (CQI), a precoding matrix indicator (PMI), and / or a layer index (LI).

[0106] Grant or Allocation Characteristics

[0107] The characteristics of the grant or allocation may include at least one of the following: frequency allocation, time allocation aspect (e.g., duration), priority, modulation and coding scheme, transport block size (TBS), number of spatial layers, number of transport blocks, TCI state, CRI or SRI, number of repetitions, whether the repetition scheme is Type A or Type B, whether the grant is a configured grant type 1, type 2, or dynamic grant, whether the allocation is a dynamic allocation or a semi-persistent scheduled (configured) allocation, configured grant index or semi-persistent allocation index, configured grant or allocation periodicity, channel access priority class (CAPC), and / or any parameters provided in the DCI, MAC, or RRC for scheduling the grant or allocation.

[0108] The indication by the DCI may include at least one of the following: 1) explicit indication by a DCI field or by an RNTI used to mask the CRC of the PDCCH, and / or 2) implicit indication by properties such as DCI format, DCI size, Coreset or search space, aggregation level, first resource element of the received DCI (e.g., index of the first control channel element), and the mapping between properties and values ​​may be signaled by an RRC message or a MAC (e.g., MAC CE) message.

[0109] The signal may be used interchangeably with one or more of a sounding reference signal (SRS), a channel state information-reference signal (CSI-RS), a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and / or a synchronization signal block (SSB).

[0110] The channel may be used interchangeably with one or more of a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical random access channel (PRACH), etc.

[0111] Downlink reception may be used interchangeably with receive (Rx) opportunity, PDCCH, PDSCH, and SSB reception and still be consistent with the present invention.

[0112] Uplink transmission may be used interchangeably with transmit (Tx) opportunity, PUCCH, PUSCH, PRACH, SRS transmission and still be consistent with the present invention.

[0113] RS may be used interchangeably with one or more of RS resource, RS resource set, RS port, and / or RS port group while still being consistent with the present invention. RS may also be used interchangeably with one or more of SSB, CSI-RS, SRS, and / or DM-RS while still being consistent with the present invention.

[0114] Time instance may be used interchangeably with slot, symbol, and subframe and still be consistent with the present invention.

[0115] Typical Procedure for Channel / Signal UTCI Timeline

[0116] In one embodiment, the WTRU may be configured with one or more parameters for beam application time (BAT), each of which may be associated with a list of channels / signals, which may be predefined and / or determined based on WTRU capabilities and / or configured (e.g., independently configured) by the network (e.g., gNB).

[0117] For example, referring to FIG. 2, a timeline is provided using one or more BATs (e.g., BAT1 and / or BAT2) or paired / associated offset parameters (Delta) for the indicated UTCI. In this example, if the association is configured by the gNB, the association may be provided by higher layer signaling (e.g., RRC and / or MAC-CE). In this example, the WTRU may be configured with a first BAT (BAT1) associated with a first list of channels / signals and may be configured with a second BAT (BAT2) associated with a second list of channels / signals. One or more of the following operations may apply:

[0118] BAT1 (e.g., shorter than BAT2) may be configured for one or more delay-sensitive channels / signals (e.g., at least a portion of a first list of channels / signals). In one example, the first list of channels / signals may include a first group of CORESET, a first group of CSI-RS, a first group of PUCCH resources, a first set of PDSCHs (e.g., other than CJT-PDSCH), a first set of PUSCHs (other than STxMP PUSCH), and / or CJT-CSI-RS or SRS (e.g., for channel reciprocity), etc. The first set of one or more PDSCHs may include a PDSCH (e.g., a PDSCH scheduled by a higher layer, such as a semi-persistent scheduling (SPS)-PDSCH or a dynamic grant-based PDSCH) carrying delay-sensitive (e.g., delay-intense) packet-type data (e.g., URLLC packets). The first set of one or more PUSCHs may include PUSCHs (e.g., PUSCHs scheduled by higher layers, such as configured-grant (CG)-PUSCHs or dynamic grant-based PUSCHs) carrying delay-sensitive (e.g., delay-intense) packet-type data transmissions (e.g., for URLLC) from the WTRU.

[0119] In response to receiving a control command / message (e.g., via a DCI, via a TCI field of the DCI) at a first time instance (T1) indicating at least one unified TCI (UTCI), the WTRU may determine a second time instance (T2) based on T1 and BAT1 (e.g., as T1+BAT1 or as T1+Alpha+BAT1), at which time instance the WTRU may update (and begin using) the indicated at least one UTCI for the first list of channels / signals, and may not update (at T2) the indicated at least one UTCI for other channels / signals not included in the first list.

[0120] In one example, “Alpha” may include a first duration between T1 and a PDSCH reception time instance (wherein, when the PDSCH is scheduled by the DCI, the WTRU may receive the PDSCH using a previous (e.g., currently used, previously used) UTCI that is independent of the indicated at least one UTCI).

[0121] In one example, "Alpha" may include, in addition to the first duration, a second duration between the PDSCH reception time instance and the corresponding ACK transmission time instance, where the corresponding ACK transmission may be performed based on a PUCCH resource (e.g., for HARQ-ACK) that may carry information regarding whether the PDSCH was successfully received at the WTRU and / or whether the indicated at least one UTCI was successfully received at the WTRU.

[0122] A BAT2 (e.g., longer than BAT1) may be configured for a second set of channels / signals that are less delay-sensitive / stringent and / or may be used as a “recoverable” backup channel before a Beam Failure Recovery (BFR) procedure or a Radio Link Recovery (RLM / RLF) procedure is encountered, and / or may require more CSI acquisition time upon receiving a DCI indicating at least one UTCI. The second set of channels / signals may be at least part of a second list of channels / signals. In one example, the second list of channels / signals may include a second group of CORESET, a second group of CSI-RS, a second group of PUCCH resources, a CJT-PDSCH (e.g., for required CSI acquisition time), a second set of one or more PDSCHs, a STxMP PUSCH (for having an SRS-based acquisition time for STxMP), and / or a second set of one or more PUSCHs, etc. The second set of one or more PDSCHs may include PDSCHs (e.g., PDSCHs scheduled by higher layers such as semi-persistent scheduling (SPS)-PDSCHs or dynamic grant-based PDSCHs) carrying packet-type data that is less delay-sensitive (e.g., eMBB packets), the second set of one or more PUSCHs may include PUSCHs (e.g., PUSCHs scheduled by higher layers such as configuration grant (CG)-PUSCHs or dynamic grant-based PUSCHs) carrying packet-type data transmissions that are less delay-sensitive (e.g., for eMBB) from the WTRU, and so on.

[0123] In response to receiving a control command / message (e.g., via a DCI, via a TCI field of the DCI) at a first time instance (T1) indicating at least one unified TCI (UTCI), the WTRU may determine a third time instance (T3) based on T1 and BAT2 (e.g., as T1+BAT2 or as T1+Alpha+BAT2), at which time instance the WTRU may update (and begin using) the indicated at least one UTCI for a second list of channels / signals, and may not update (at T3) the indicated at least one UTCI for other channels / signals not included in the second list.

[0124] In one example, “Alpha” may include a first duration between T1 and a PDSCH reception time instance (wherein, when the PDSCH is scheduled by the DCI, the WTRU may receive the PDSCH using a previous (e.g., currently used, previously used) UTCI that is independent of the indicated at least one UTCI).

[0125] In one example, "Alpha" may include, in addition to the first duration, a second duration between the PDSCH reception time instance and the corresponding ACK transmission time instance, where the corresponding ACK transmission may be performed based on a PUCCH resource (e.g., for HARQ-ACK) that may carry information regarding whether the PDSCH was successfully received at the WTRU and / or whether the indicated at least one UTCI was successfully received at the WTRU.

[0126] The WTRU may transmit WTRU capability report content, which may include a WTRU capability component / element related to BAT1, where the WTRU may report its supported (e.g., implemented) application time (e.g., in terms of the duration required in a hardware / software implementation to update / apply at least one UTCI when received over a DCI). Based on receiving this WTRU capability report from the WTRU, the gNB may configure (or indicate) the parameters of BAT1 to the WTRU (e.g., for confirmation based on at least receipt of the WTRU capability report). In response to receiving the parameters / values ​​of BAT1, the WTRU may use BAT1 (e.g., shorter than BAT2) based on at least one embodiment presented in this disclosure. In one example, BAT2 may not be based on the WTRU capability report. The WTRU may receive BAT2 and decide to use / apply BAT2 for a particular set of channels / signals, which may correspond to the second list of channels / signals. Even though the WTRU may determine that BAT2 is not based on the WTRU capability report content (e.g., its supported application time for updating / applying at least one UTCI when received by DCI), the WTRU may be configured (or indicated) to use / apply BAT2.

[0127] BAT2 may be dynamically updated from the gNB to the WTRU, e.g., via MAC-CE and / or DCI, which may provide the advantage that BAT2 may be a controllable parameter for a particular set of channels / signals without being based on WTRU capabilities.

[0128] The list of channels / signals associated with BAT1 may be mutually exclusive with the list of channels / signals associated with BAT2.

[0129] The list of channels / signals associated with BAT1 and BAT2 may differ based on the availability of channel state information at the gNB for the indicated UTCI.

[0130] If the WTRU reports a CSI associated with the indicated UTCI within a time window before receiving the indicated UTCI, or if the WTRU recognizes that the gNB has CSI information associated with the indicated UTCI, BAT2 may be updated to have the same value as BAT1 (e.g., BAT2=BAT1). In some cases, the time window may be predetermined, configured, or indicated by the gNB.

[0131] In one embodiment, a WTRU may be configured with a BAT (e.g., parameters of the BAT) and a paired / associated “Delta” offset parameter, where the BAT and “BAT plus Delta” may each be associated with a list of channels / signals, where the list of channels / signals may be predefined, determined based on WTRU capabilities, and / or configured (independently) by the gNB (e.g., as shown in FIG. 2). If the association is configured by the gNB, the association may be provided by higher layer signaling (e.g., RRC and / or MAC-CE). In one example, the WTRU may be configured with a BAT associated with a first list of channels / signals and may further be configured with Delta, where the BAT plus Delta may be associated with a second list of channels / signals. One or more of the following operations may apply.

[0132] The BAT may be used / applied for one or more delay-sensitive channels / signals (e.g., at least a portion of a first list of channels / signals). In one example, the first list of channels / signals may include a first group of CORESET, a first group of CSI-RS, a first group of PUCCH resources, a first set of one or more PDSCHs (e.g., other than CJT-PDSCH), a first set of one or more PUSCHs (other than STxMP PUSCH), and / or CJT-CSI-RS or SRS (e.g., for channel reciprocity), etc. The first set of one or more PDSCHs may include a PDSCH (e.g., a PDSCH scheduled by a higher layer, such as a semi-persistent scheduling (SPS)-PDSCH or a dynamic grant-based PDSCH) carrying delay-sensitive (e.g., delay-intense) packet-type data (e.g., URLLC packets). The first set of one or more PUSCHs may include PUSCHs (e.g., PUSCHs scheduled by higher layers, such as configuration grant (CG)-PUSCHs or dynamic grant-based PUSCHs) that carry delay-sensitive (e.g., delay-intense) packet-type data transmissions (e.g., for URLLC) from the WTRU.

[0133] In response to receiving a control command / message (e.g., via a DCI, via a TCI field of the DCI) at a first time instance (T1) indicating at least one unified TCI (UTCI), the WTRU may determine a second time instance (T2) based on T1 and BAT (e.g., as T1+BAT or as T1+Alpha+BAT), at which time instance the WTRU may update (and begin using) the indicated at least one UTCI for the first list of channels / signals, and may not update (at T2) the indicated at least one UTCI for other channels / signals not included in the first list.

[0134] In one example, “Alpha” may include a first duration between T1 and a PDSCH reception time instance (wherein, when the PDSCH is scheduled by the DCI, the WTRU may receive the PDSCH using a previous (e.g., currently used, previously used) UTCI that is independent of the indicated at least one UTCI).

[0135] In one example, "Alpha" may include, in addition to the first duration, a second duration between the PDSCH reception time instance and the corresponding ACK transmission time instance, where the corresponding ACK transmission may be performed based on a PUCCH resource (e.g., for HARQ-ACK) that may carry information regarding whether the PDSCH was successfully received at the WTRU and / or whether the indicated at least one UTCI was successfully received at the WTRU.

[0136] The BAT plus Delta may be used / applied to a second set of channels / signals that are less delay-sensitive / stringent, and / or that may be used as a “recoverable” backup channel before engaging in a beam failure recovery (BFR) or radio link restoration (RLM) procedure, and / or that require more CSI acquisition time upon receiving a DCI indicating at least one UTCI. The second set of channels / signals may be at least a part of a second list of channels / signals. In one example, the second list of channels / signals may include a second group of CORESET, a second group of CSI-RS, a second group of PUCCH resources, a CJT-PDSCH (e.g., for required CSI acquisition time), a second set of one or more PDSCHs, a STxMP PUSCH (for having an SRS-based acquisition time for STxMP), and / or a second set of one or more PUSCHs, etc. The second set of one or more PDSCHs may include PDSCHs (e.g., PDSCHs scheduled by higher layers such as semi-persistent scheduling (SPS)-PDSCHs or dynamic grant-based PDSCHs) carrying packet-type data that is less delay-sensitive (e.g., eMBB packets), the second set of one or more PDSCHs may include PUSCHs (e.g., PUSCHs scheduled by higher layers such as configuration grant (CG)-PUSCHs or dynamic grant-based PUSCHs) carrying packet-type data transmissions that are less delay-sensitive (e.g., for eMBB) from the WTRU, and so on.

[0137] In response to receiving a control command / message (e.g., via a DCI, via the TCI field of the DCI) at a first time instance (T1) indicating at least one unified TCI (UTCI), the WTRU may determine a third time instance (T3) based on T1, BAT, and Delta (e.g., as T1+BAT+Delta, or as T1+Alpha+BAT+Delta), at which time instance the WTRU may update (and begin using) the indicated at least one UTCI for a second list of channels / signals, and may not update (at T3) the indicated at least one UTCI for other channels / signals not included in the second list.

[0138] In one example, “Alpha” may include a first duration between T1 and a PDSCH reception time instance (wherein, when the PDSCH is scheduled by the DCI, the WTRU may receive the PDSCH using a previous (e.g., currently used, previously used) UTCI that is independent of the indicated at least one UTCI).

[0139] In one example, "Alpha" may include, in addition to the first duration, a second duration between the PDSCH reception time instance and the corresponding ACK transmission time instance, where the corresponding ACK transmission may be performed based on a PUCCH resource (e.g., for HARQ-ACK) that may carry information regarding whether the PDSCH was successfully received at the WTRU and / or whether the indicated at least one UTCI was successfully received at the WTRU.

[0140] The WTRU may transmit WTRU capability report content, which may include WTRU capability components / elements related to the BAT, where the WTRU may report its supported (e.g., implemented) application time (e.g., in terms of the duration required in a hardware / software implementation to update / apply at least one UTCI when received over a DCI). Based on receiving this WTRU capability report from the WTRU, the gNB may configure (or indicate) parameters of the BAT to the WTRU (e.g., for confirmation based on receiving at least the WTRU capability report). In response to receiving the parameters / values ​​of the BAT, the WTRU may use the BAT based on at least one embodiment presented in this disclosure. In one example, Delta may not be based on the WTRU capability report. The WTRU may receive the value of Delta and decide to use / apply the BAT plus Delta for a particular set of channels / signals, which may correspond to the second list of channels / signals. The WTRU may be configured (or indicated) to use / apply BAT plus Delta, even though the WTRU may determine that Delta is not based on the WTRU capability report (e.g., its supported application time for updating / applying at least one UTCI when received by DCI).

[0141] Delta may be dynamically updated from the gNB to the WTRU, e.g., via MAC-CE and / or DCI, which may provide the advantage that Delta may be a controllable parameter for a particular set of channels / signals without being based on WTRU capabilities.

[0142] The list of channels / signals associated with BAT may be mutually exclusive with the list of channels / signals associated with BAT plus Delta.

[0143] The list of channels / signals associated with BAT and BAT plus Delta may differ based on the availability of channel state information at the gNB for the indicated UTCI.

[0144] Delta may be updated to have a value of '0' (e.g., Delta=0) if the WTRU reports a CSI associated with the indicated UTCI within a time window prior to receiving the indicated UTCI, or if the WTRU recognizes that the gNB has CSI information associated with the indicated UTCI. In some cases, the time window may be predetermined, configured, or indicated by the gNB.

[0145] In one embodiment, referring to FIG. 3, a timeline is provided using a BAT (e.g., BAT1 and / or BAT2) or paired / associated offset parameter (Delta) for coherent joint transmit (CJT) operation.

[0146] For example, the first list of channels / signals may include at least one CSI-RS resource (e.g., tagged for use in coherent joint transmission (CJT) operation, e.g., enabled for the WTRU), which may be indicated by a CJT-CSI-RS resource, and the second list of channels / signals may include at least a PDSCH scheduled for CJT operation, which may be indicated by a CJT-PDSCH. This may provide an advantage of improving the accuracy and performance of CJT operation in that the CSI acquisition time duration may be obtained between a first time instance indicated by BAT1 (or BAT) and a second time instance indicated by BAT2 (or BAT plus Delta). In one example, up to Q TRPs may be taken into account for CJT operation, e.g., Q=4. The WTRU may receive a DCI indicating at least one UTCI (e.g., in the case of two UTCIs, UTCI1 corresponds to the first TRP of the Q TRPs and UTCI2 corresponds to the second TRP of the Q TRPs). The first TRP may be one of TRP indices 1, 2, 3, and 4, and the second TRP may be one of TRP indices 1, 2, 3, and 4 and may be different from the first TRP. This TRP selection mechanism may be accommodated in a DCI-based indication that indicates at least one UTCI from the perspective of CJT operation. The WTRU may determine that, at a first time instance, UTCI1 applies on the first CSI-RS resource (for CJT operation) and UTCI2 applies on the second CSI-RS resource (for CJT operation). Based on this determination, the WTRU may measure the first CSI-RS resource using UTCI1 and the second CSI-RS resource using UTCI2, and may transmit one or more CSI reports (for CJT operation) based on the measurements.The WTRU may receive a PDSCH (e.g., a CJT-PDSCH) at or after the second time instance, and the PDSCH (e.g., a CJT-PDSCH) may be scheduled based on one or more CSI reports received at the gNB (e.g., as shown in FIG. 3).

[0147] In one embodiment, an example of a timeline management procedure is provided as shown in Figure 4. In this example, the timeline management procedure may include determining the type of channel (or signal) for wireless communication (e.g., using a TCI indication).

[0148] 4, for example, a WTRU may receive configuration information (e.g., from a gNB, a second WTRU, another WTRU for sidelink communications, or another transmitter or node) indicating a set of TCI states, a BAT, and / or a BAT offset (e.g., Delta). The WTRU may receive a first DCI that schedules a PDSCH and indicates a first TCI state from the set of TCI states. After transmitting an ACK associated with receiving the PDSCH transmission, the WTRU may apply the indicated first TCI state to the transmission (or reception) of a channel or signal (e.g., a scheduled, configured, or indicated channel or signal) if the channel or signal is transmitted (or received) at a time offset (or using at least a time offset, or one or more time offsets).

[0149] In one example, the WTRU may determine that the time offset is BAT if the type of the channel or signal is a first type of channel or signal (or is included in a first set of channel or signal types). The WTRU may determine that the time offset is BAT plus BAT offset (e.g., BAT + BAT offset) if the type of the channel or signal is a second type of channel or signal (or is included in a second set of channel or signal types). In one example, the WTRU may transmit (or receive) a channel or signal using the indicated first TCI state based on (or using) the determined time offset (e.g., BAT, or BAT plus BAT offset), provided that the channel or signal is transmitted (or received) at least the determined time offset after transmitting an ACK associated with receiving the PDSCH.

[0150] In one example, the WTRU may determine that i) the first type of channel or signal is at least one of SRS or CSI-RS (e.g., for channel acquisition), or a data channel associated with a low-latency related type (e.g., URLLC), and ii) the second type of channel or signal is at least one of PUSCH, or PDSCH, or a control channel associated with recovery purposes as described herein (e.g., CORESET, PDCCH, search space, or PUCCH).

[0151] In one example, the WTRU may receive configuration information indicating that i) a first set of channels or signal types includes at least one of SRS, or CSI-RS (e.g., for channel acquisition), or data channels associated with a low-latency related type (e.g., URLLC), and ii) a second set of channels or signal types includes at least one of PUSCH, or PDSCH, or control channels associated with recovery purposes as described herein (e.g., CORESET, PDCCH, search space, or PUCCH).

[0152] In one embodiment, an example of a transmit / receive management procedure is provided as shown in Figure 5. In this example, the timeline management procedure may include determining the channel or signal type (e.g., using a TCI indication) and using a time offset for wireless communication.

[0153] 4, for example, a WTRU may receive configuration information (e.g., from a gNB, a second WTRU, another WTRU for sidelink communications, or another transmitter or node) indicating a set of TCI states, a BAT, and / or a BAT offset (e.g., Delta). The WTRU may receive a first DCI that schedules a PDSCH and indicates a first TCI state from the set of TCI states. After transmitting HARQ feedback (e.g., HARQ-ACK) associated with receiving the PDSCH transmission, the WTRU may apply the indicated first TCI state to the transmission (or reception) of a channel or signal (e.g., a scheduled, configured, or indicated channel or signal) if the channel or signal is transmitted (or received) with a time offset (or at least with a time offset, or using one or more time offsets).

[0154] The WTRU may determine a time offset for a channel or signal (e.g., when to apply the first TCI state) as either the BAT or the BAT plus the BAT offset. The decision to use 1) the BAT or 2) the BAT plus the BAT offset is based on the type of the channel or signal, or on the set of channel / signal types to which the channel or signal belongs. For example, the decision is based on the channel / signal type, where the first type is at least SRS or CSI-RS and the second type is at least PUSCH or PDSCH. In another example, the decision is based on the set of channel / signal types to which the channel or signal belongs, i.e., the first set of channel / signal types (e.g., including at least SRS or CSI-RS) or the second set of channel / signal types (e.g., including at least PUSCH or PDSCH).

[0155] In one example, the WTRU may transmit a channel (or signal) of a first type (or a type in a first set) using a first TCI state if the transmission time is at least BAT after sending HARQ feedback (e.g., HARQ-ACK) for a first PDSCH. In this example, the signal of the first type (or a type in the first set) may be SRS or CSI-RS.

[0156] In another example, the WTRU may receive a channel (or signal) of a first type (or a type in a first set) using a first TCI state if the reception time is at least BAT after sending HARQ feedback (e.g., HARQ-ACK) for a first PDSCH. In this example, the signal of the first type (or a type in the first set) may be SRS or CSI-RS.

[0157] In one example, after sending HARQ feedback (e.g., HARQ-ACK) for the first PDSCH, the WTRU may transmit a channel (or signal) of a second type (or a type in the second set) using the first TCI state if the transmission time is at least BAT plus a BAT offset. In this example, the channel of the second type (or a type in the second set) may be a PUSCH or a second PDSCH.

[0158] In another example, the WTRU may receive a channel (or signal) of a second type (or a type in a second set) using the first TCI state if the reception time is at least BAT plus a BAT offset after sending HARQ feedback (e.g., HARQ-ACK) for the first PDSCH. In this example, the channel of the second type (or a type in the second set) may be a PUSCH or a second PDSCH.

[0159] In one embodiment, a WTRU may receive configuration information indicating a set of transmission configuration indicator (TCI) states, a beam application time (BAT), and / or a BAT offset. The WTRU may receive downlink control information (DCI) indicating 1) scheduling of a downlink data transmission and 2) a TCI state from a set of TCI states. The WTRU may determine a time offset associated with a time instance for applying the indicated TCI state based on a type of channel that will be used after transmitting HARQ feedback associated with the downlink data transmission. The WTRU may also transmit or receive a signal using the indicated TCI state on a channel of that type based on the determined time offset.

[0160] In one example, the WTRU may determine that the time offset is the BAT based on whether the type of the channel is either an SRS, a CSI-RS, or a data channel associated with a low-latency association type. In another example, the WTRU may determine that the time offset is the BAT plus the BAT offset based on whether the type of the channel is either a PUSCH, a PDSCH, or a control channel.

[0161] Typical procedures for UTCI timelines based on UTCI mode, TRP, and WTRU panels

[0162] In one embodiment, a WTRU may be configured with multiple sets of BAT values, each set configured with multiple BATs (or, for example, BAT plus Delta). To define the overall structure of the BAT configuration, hierarchical configuration levels may be considered and used for configuration for the WTRU.

[0163] For example, a multi-stage or hierarchical BAT configuration may include one or more of the following steps or actions:

[0164] Per-UTCI mode configuration: The first step in the configuration is to define whether the UTCI mode is joint (e.g., joint UTCI for DL ​​and UL) or separate (e.g., separate UTCI for each of DL or UL). In a joint UTCI configuration, the WTRU may be configured with the same beam reference for all uplink and downlink channels or signals. Alternatively, separate UTCI configurations may be configured for downlink and uplink transmissions. UTCI-based operation may be configured per TRP, such that the WTRU assumes a separate UTCI mode of operation for a first TRP, e.g., the serving TRP, and a joint UTCI mode of operation for a second TRP. Depending on the UTCI configuration mode, the WTRU may receive multiple sets of BAT values.

[0165] BAT configuration per TRP / panel: Depending on the gNB and WTRU implementation, the WTRU may receive multiple sets of BAT values.

[0166] In one embodiment, when a WTRU is configured for multi-TRP transmission, it can receive multiple sets of BAT values. The same set of BAT values ​​can be used for multiple TRPs. For example, BAT_set1 can be used for TRP1, while BAT_set2 can be used for TRP2 and TRP3.

[0167] In another embodiment, the WTRU may receive multiple sets of BAT values ​​when it indicates multi-panel transmission capability. The same set of BAT values ​​may be used for multiple panels (e.g., WTRU panels). For example, BAT_set1 may be used for the first panel, and BAT_set2 may be used for the second and third panels. A similar concept may be employed for each WTRU antenna group.

[0168] In one embodiment, when a WTRU is configured to operate in a multi-TRP scenario and configured with multiple BAT values, the WTRU may apply the larger BAT value for CJT operation. For example, if the WTRU is configured with BAT1 for PDSCH transmission from TRP1 and BAT2 for PDSCH transmission from TRP2, and BAT2 > BAT1, the WTRU may assume BAT2 for CJT transmission (e.g., CJT-PDSCH).

[0169] In one embodiment, if a WTRU is configured to operate in a multi-TRP scenario and configured with one BAT plus Delta, the WTRU may apply BAT plus Delta for CJT operation. For example, if the WTRU is configured with BAT for PDSCH transmissions from TRP1 and BAT plus Delta for PDSCH transmissions from TRP2, based on Delta (e.g., a positive value), the WTRU may assume BAT plus Delta for CJT transmissions (e.g., CJT-PDSCH).

[0170] Similarly, if a multi-panel WTRU is configured to operate with STxMP and configured with multiple BAT values, the WTRU may apply the larger BAT value to the STxMP operation. For example, if a multi-panel WTRU is configured with BAT1 for PUSCH transmission from a first panel and BAT2 for PUSCH transmission from a second panel, and BAT2 > BAT1, the WTRU may assume (and use / apply) BAT2 for STxMP transmission. If a multi-panel WTRU is configured to operate with STxMP and configured with one BAT plus Delta, the WTRU may apply BAT plus Delta for STxMP operation. For example, if a multi-panel WTRU is configured with BAT for PUSCH transmission from a first panel and BAT plus Delta for PUSCH transmission from a second panel, based on Delta (e.g., a positive value), the WTRU may assume (and use / apply) BAT plus Delta for STxMP transmission.

[0171] Per-Channel Configuration: Once a WTRU is configured with at least one set of BAT values, for example according to a TRP or WTRU panel, the configured set of values ​​may then be divided into multiple subsets depending on the channel and / or signal.

[0172] In one embodiment, a WTRU configured with BAT_set1 for TRP1 may receive multiple subsets of BAT values, where each subset of BAT values ​​may be used for multiple channels and / or signals. For example, in a multi-DCI TRP transmission, two different BAT values, e.g., BAT11 and BAT21, may be considered for the same channel, e.g., PDCCH, where the BAT11 and BAT21 values ​​are the BAT values ​​corresponding to TRP1 and TRP2.

[0173] In one embodiment, for a given channel / signal, the BAT value corresponding to a TRP associated with a serving cell may be shorter than the BAT values ​​associated with other TRPs.

[0174] In one embodiment, a hierarchical BAT configuration for a multi-panel WTRU configured with a multi-TRP deployment may be based on a combination of semi-static and dynamic signaling.

[0175] In one embodiment, the configuration of the general UTCI mode, either the split TCI mode or the joint TCI mode, may be done through RRC signaling. In one embodiment, the joint TCI configuration may be considered as a fallback mode.

[0176] A combination of semi-static and dynamic signaling may be used for per-TRP / panel BAT configuration. In one embodiment, a WTRU may be configured with multiple per-TRP and / or per-panel BAT configurations, where the specific selection may be made by dynamic signaling, e.g., MAC CE or DCI.

[0177] Similar to per-TRP / per-panel configuration, per-channel configuration may use a combination of semi-static and dynamic signaling. In one embodiment, a WTRU may be configured with multiple per-channel / signal configurations, where the particular selection may be made by dynamic signaling, e.g., MAC CE or DCI.

[0178] Representative Procedures for Timeline Management for Unified TCI Display

[0179] In a representative embodiment, a WTRU may be configured with a Beam Application Time (BAT) parameter and a paired / associated “Delta” offset parameter, where the BAT and “BAT plus Delta” may each be associated with a list of channels / signals, where the list of channels / signals may be predefined, determined based on WTRU capabilities, and / or independently configured by the network (e.g., gNB). In one example, a WTRU may be configured with a BAT associated with a first list of channels / signals and may further be configured with Delta, where the BAT plus Delta may be associated with a second list of channels / signals.

[0180] In one example, in response to receiving a control message (e.g., via a DCI, via a TCI field of the DCI) at a first time instance (T1) indicating at least one unified TCI (UTCI), the WTRU may determine a second time instance (T2) based on T1 and BAT (e.g., as T1+BAT or as T1+Alpha+BAT), at which time instance the WTRU may update (e.g., configure and / or start using) the indicated at least one UTCI for a first list of channels / signals, and may not update (at T2) the indicated at least one UTCI for other channels / signals not included in the first list.

[0181] In one example, the WTRU may determine a third time instance (T3) based on T1, BAT, and Delta (e.g., as T1+BAT+Delta or as T1+Alpha+BAT+Delta), at which time instance the WTRU may update (e.g., configure and / or begin using) at least one UTCI indicated for the second list of channels / signals, and may not update (at T3) at least one UTCI indicated for other channels / signals not included in the second list.

[0182] In a representative embodiment, the WTRU determines that the time offset is the BAT if the type of the channel (or signal) is a first type of channel (or signal) or is included in a first set of channel (or signal) types. The WTRU may determine that the time offset is the BAT plus the BAT offset if the type of the channel or signal is a second type of channel or signal or is included in a second set of channel or signal types. In one example, the WTRU may determine that i) the first type of channel or signal is at least one of SRS or CSI-RS (e.g., for channel acquisition), or a data channel associated with a low-latency related type (e.g., URLLC), and (ii) the second type of channel or signal is at least one of PUSCH, PDSCH, or a control channel (e.g., CORESET, PDCCH, search space, PUCCH, etc.).

[0183] conclusion

[0184] While features and elements have been presented above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in this application, which are intended as illustrations of various aspects. It will be apparent to those skilled in the art that many modifications and variations can be made without departing from the spirit and scope of the present disclosure. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly stated as such. Functionally equivalent methods and apparatuses within the scope of the present disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only by the language of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is understood that the present disclosure is not limited to any particular method or system.

[0185] The above embodiments are discussed for simplicity with respect to the terminology and structure of infrared-enabled devices, i.e., infrared emitters and receivers. However, the discussed embodiments are not limited to these systems and may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves, such as sound waves.

[0186] It should also be understood that the terms used herein are merely for the purpose of describing particular embodiments and are not intended to be limiting. As used herein, the term “video” or “image” can refer to either a snapshot, a single image, and / or multiple images displayed on a time basis. As another example, when referred to herein, the term “user equipment” and its abbreviation “UE,” the term “remote,” and / or the term “head-mounted display” and its abbreviation “HMD” can mean or include (i) a wireless transmit and / or receive unit (WTRU), (ii) any of multiple embodiments of a WTRU, (iii) a wireless-enabled and / or wired-enabled (e.g., tetherable) device specifically configured with some or all of the structure and functionality of a WTRU, (iii) a wireless-enabled and / or wired-enabled device configured with less than all of the structure and functionality of a WTRU, or (iv) the like. Details of an exemplary WTRU that may represent any WTRU described herein are presented herein in connection with FIGS. 1A-1D . As another example, various disclosed embodiments described above and below herein are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than head-mounted displays may be utilized, and that some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0187] In addition, the methods provided 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 via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). The software and associated processor may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0188] Modifications to the methods, apparatus, and systems provided above are possible without departing from the scope of the present invention. In view of the wide variety of possible embodiments, it is understood that the illustrated embodiments are examples only and should not be taken as limiting the scope of the appended claims. For example, the embodiments provided herein include handheld devices, which may include or be utilized with any suitable voltage source, such as a battery providing any suitable voltage.

[0189] Furthermore, in the embodiments provided above, reference is made to processing platforms, computing systems, controllers, and other devices that include processors. These devices may include at least one central processing unit ("CPU") and memory. In accordance with the practices of those skilled in the art of computer programming, references to symbolic representations of acts and operations or instructions may be performed by various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer-executed," or "CPU-executed."

[0190] Those skilled in the art will appreciate that the operations and symbolically represented operations or instructions include the manipulation of electrical signals by a CPU. The electrical system represents data bits that can result in a transformation or reduction of the electrical signals, and maintains the data bits in memory locations in a memory system, thereby reconfiguring or otherwise altering the operation of the CPU and the processing of other signals. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that embodiments are not limited to the platforms or CPUs described above, and that other platforms and CPUs may support the provided methods.

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

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

[0193] There is little difference between hardware and software implementations of aspects of the system. The use of hardware or software is generally a design choice representing a trade-off between cost and efficiency (although this is not always the case, in that the choice between hardware and software can be significant in certain contexts). There may be various means (e.g., hardware, software, and / or firmware) by which the processes and / or systems and / or other techniques described herein may be effective, and the preferred means may vary depending on the context in which the processes and / or systems and / or other techniques are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may select a primarily hardware and / or firmware means. If flexibility is paramount, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0194] The foregoing detailed description illustrates various embodiments of devices and / or processes through the use of block diagrams, flowcharts, and / or examples. To the extent that such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation in such block diagrams, flowcharts, or examples may be individually and / or collectively implemented by a wide range of hardware, software, firmware, or substantially any combination thereof. In embodiments, portions of the subject matter described herein may be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that certain aspects of the embodiments disclosed herein may be equivalently implemented, in whole or in part, in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as substantially any combination thereof, and that designing circuitry and / or writing software and / or firmware code is well within the skills of those skilled in the art in light of this disclosure. Additionally, those skilled in the art will understand that the mechanisms of the subject matter described herein may be distributed as program products in various forms, and that exemplary embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effect the distribution.Examples of signal-bearing media include, but are not limited to, recordable-type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, and transmission-type media such as digital and / or analog communications media (e.g., fiber optic cables, wave guides, wired communications links, wireless communications links, etc.).

[0195] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner described herein and then use engineering techniques to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system may generally include one or more of the following: a system unit housing; a video display device; memory, such as volatile and non-volatile memory; a processor, such as a microprocessor and a digital signal processor; computational entities, such as an operating system, drivers, a graphical user interface, and application programs; one or more interaction devices, such as a touchpad or screen; and / or a control system, including feedback loops and control motors (e.g., feedback for sensing position and / or velocity, control motors for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communications and / or network computing / communications systems.

[0196] The subject matter described herein may depict different components contained within or connected to different other components. It should be understood that such illustrated architectures are merely examples, and that in fact many other architectures that achieve the same functionality may be implemented. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality may be achieved. Thus, any two components combined herein to achieve a particular functionality may be considered “associated” with each other such that the desired functionality is achieved, regardless of the architecture or intermediate components. Similarly, any two components so associated may be considered “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components capable of being so associated may be considered “operably coupleable” to each other to achieve the desired functionality. Examples of operably coupleable include, but are not limited to, physically matable and / or physically interacting components, wirelessly interacting and / or wirelessly interacting components, and / or logically interacting and / or logically interacting components.

[0197] With respect to the use of virtually any plural and / or singular term herein, those skilled in the art can convert from plural to singular and / or from singular to plural as appropriate to the context and / or application. Various singular / plural permutations may be expressly set forth herein for the purposes of clarity.

[0198] Those skilled in the art will understand that the terms used in this specification, in general, and in the appended claims in particular (e.g., the body of the appended claims), are generally intended as "open" terms (e.g., the term "comprises" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "comprises" should be interpreted as "including but not limited to," etc.). Furthermore, those skilled in the art will understand that where a specific number is intended in the introduced claim recitation, such intention will be explicitly set forth in the claim; in the absence of such recitation, no such intention exists. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to mean that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim containing such an introduced claim recitation to embodiments containing only one such recitation, and the same applies when the same claim includes the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. Additionally, those skilled in the art will recognize that even when a specific number of introduced claim recitations is explicitly recited, such recitation should be interpreted to mean at least the recited number (e.g., the mere recitation of "two recitations" without other modifiers means at least two recitations or more than two recitations).Furthermore, when a convention similar to "such as at least one of A, B, and C" is used, generally such a structure is intended in the sense that one of ordinary skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having A only, B only, C only, A and B together, A and C together, B and C together, and / or A, B, and C together). When a convention similar to "such as at least one of A, B, or C" is used, generally such a structure is intended in the sense that one of ordinary skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having A only, B only, C only, A and B together, A and C together, B and C together, and / or A, B, and C together). Furthermore, those skilled in the art will understand that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Furthermore, as used herein, the term "any of" following a list of multiple items and / or a list of multiple categories of items is intended to include "any of," "any combination of," "any plurality of," and / or "any combination of a plurality of" the items and / or categories of items, individually or in conjunction with other items and / or other categories of items. Furthermore, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "number" is intended to include any number, including zero. Also, as used herein, the term "multiple" is intended to be synonymous with "plurality."

[0199] Additionally, those skilled in the art will recognize that when features or aspects of the disclosure are described in terms of a Markush group, the disclosure is also thereby described in terms of any individual element or subgroup of elements of the Markush group.

[0200] As will be understood by those skilled in the art, for all purposes, including in terms of providing a written description, all ranges disclosed herein encompass all possible subranges and combinations of subranges. Any recited range can be readily recognized as fully descriptive, allowing the same range to be broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range described herein can be easily broken down into a lower third, middle third, and upper third, etc. As will also be understood by those skilled in the art, all terms such as "up to," "at least," "greater than," and "less than" are inclusive of the recited number and refer to ranges that can be further broken down into subranges as described above. Finally, as will be understood by those skilled in the art, ranges include each individual element. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to a group having 1, 2, 3, 4, or 5 cells, and so on.

[0201] Furthermore, the claims should not be read as limited to the presented order or elements unless expressly stated to that effect. Moreover, the use of the term "means for" in any claim is intended to be a means-plus-function claim using 35 U.S.C. 112, paragraph 6 or means-plus-function claim format, and any claim without the term "means for" is not so intended.

[0202] A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit / receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME) or evolved packet core (EPC), or any host computer. The WTRU may be used in conjunction with modules implemented in hardware and / or software, including, for example, a software defined radio (SDR), and may also be used in conjunction with other components, such as a camera, a video camera module, a video phone, a speaker phone, a vibration device, a speaker, a microphone, a television transceiver, a hands-free headset, a keyboard, a Bluetooth module, a frequency modulation (FM) radio unit, a near field communication (NFC) module, a liquid crystal display (LCD) display unit, an organic light emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an internet browser, and / or a wireless local area network (WLAN) or ultra-wideband (UWB) module.

[0203] Although the present invention is described in terms of a communications system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In particular embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.

Claims

1. 1. A method implemented by a wireless transmit / receive unit (WTRU) for wireless communication, comprising: receiving configuration information indicating a set of transmission configuration indicator (TCI) states, a beam application time (BAT), and a BAT offset; 1) scheduling a downlink data transmission; and 2) receiving downlink control information (DCI) indicating a TCI state from the set of TCI states; transmitting a transmission using the indicated TCI state, the transmission being transmitted at a time offset associated with at least the BAT and / or the BAT offset after transmitting hybrid automatic repeat request (HARQ) feedback associated with the downlink data transmission; and A method comprising:

2. 1. A method implemented by a wireless transmit / receive unit (WTRU) for wireless communication, comprising: receiving configuration information indicating a set of transmission configuration indicator (TCI) states, a beam application time (BAT), and a BAT offset; 1) scheduling a downlink data transmission; and 2) receiving downlink control information (DCI) indicating a TCI state from the set of TCI states; receiving a transmission using the indicated TCI state, the transmission being received at a time offset associated with at least the BAT and / or the BAT offset after sending hybrid automatic repeat request (HARQ) feedback associated with the downlink data transmission; and A method comprising:

3. The method of claim 1 or 2, wherein the time offset is associated with a time instance at which the indicated TCI state applies.

4. The method of claim 1 , further comprising: determining that the time offset is the BAT based on the transmission including a first type of signal or channel.

5. 5. The method of claim 4, wherein the first type of signal or channel comprises any of a sounding reference signal (SRS), a channel state information - reference signal (CSI-RS), a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and / or a synchronization signal block (SSB).

6. 6. The method of claim 1, further comprising: determining that the time offset is a combination of the BAT and the BAT offset based on the transmission including a second type of signal or channel that is different from the first type of signal or channel.

7. 7. The method of claim 6, wherein the second type of signal or channel comprises any of a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), and / or a Physical Random Access Channel (PRACH).

8. The method of claim 1 , wherein the configuration information is received via a Radio Resource Control (RRC) signal or a MAC Control Element (CE).

9. The method of claim 1 , wherein the control information indicates a set of channel or signal types.

10. 10. The method of claim 9, wherein the set of channel or signal types includes any of a sounding reference signal (SRS), a channel state information-reference signal (CSI-RS), a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and / or a synchronization signal block (SSB).

11. 10. The method of claim 9, wherein the set of channel or signal types includes any of a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), and / or a Physical Random Access Channel (PRACH).

12. 1. A method implemented by a wireless transmit / receive unit (WTRU) for wireless communication, comprising: receiving configuration information indicating 1) a unified transmission configuration indicator (UTCI), 2) a beam application time (BAT) and parameters associated with a first set of channels, and / or 3) an offset parameter associated with the BAT and a second set of channels; determining a first time instance based on the parameters associated with the BAT; determining a second time instance based on the first time instance and the offset parameter associated with the BAT; applying the UTCI for a first set of the channels at the first time instance; applying the UTCI for a second set of the channels at the second time instance; A method comprising:

13. The method of claim 12 , wherein the configuration information is received via a radio resource control (RRC) signal, a MAC control element (CE), and / or a downlink control information (DCI).

14. The method of claim 12 , wherein the configuration information is configured by a network based on a WTRU's capabilities and / or configuration.

15. The method of claim 12 , further comprising transmitting information indicating WTRU capabilities associated with the BAT, wherein the parameters associated with the BAT are determined based on the indicated WTRU capabilities.

16. 1. A wireless transmit / receive unit (WTRU) for wireless communication, comprising: receiving configuration information indicating a set of transmit configuration indicator (TCI) states, a beam application time (BAT), and a BAT offset; 1) scheduling a downlink data transmission; and 2) receiving downlink control information (DCI) indicating a TCI state from the set of TCI states; sending a transmission using the indicated TCI state, the transmission being sent at a time offset associated with at least the BAT and / or the BAT offset after sending hybrid automatic repeat request (HARQ) feedback associated with the downlink data transmission. A WTRU comprising a circuit including a processor, a receiver, a transmitter, and a memory configured to:

17. 1. A wireless transmit / receive unit (WTRU) for wireless communication, comprising: receiving configuration information indicating a set of transmit configuration indicator (TCI) states, a beam application time (BAT), and a BAT offset; 1) scheduling a downlink data transmission; and 2) receiving downlink control information (DCI) indicating a TCI state from the set of TCI states; receiving a transmission using the indicated TCI state, the transmission being received at a time offset associated with at least the BAT and / or the BAT offset after sending hybrid automatic repeat request (HARQ) feedback associated with the downlink data transmission; A WTRU comprising a circuit including a processor, a receiver, a transmitter, and a memory configured to:

18. The WTRU of claim 16 or 17, wherein the time offset is associated with a time instance at which the indicated TCI state applies.

19. 20. The WTRU of claim 18, wherein the processor is further configured to determine the time offset to be the BAT based on the transmission including a first type of signal or channel.

20. 20. The WTRU of claim 19, wherein the first type of signal or channel comprises any of a sounding reference signal (SRS), a channel state information-reference signal (CSI-RS), a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and / or a synchronization signal block (SSB).

21. 20. The WTRU of claim 18, wherein the processor is further configured to determine the time offset is a combination of the BAT and the BAT offset based on the transmission including a second type of signal or channel that is different from the first type of signal or channel.

22. 22. The WTRU of claim 21, wherein the second type of signal or channel comprises any of a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), and / or a Physical Random Access Channel (PRACH).

23. A wireless transmit / receive unit (WTRU) comprising circuitry including a processor, a receiver, a transmitter, and a memory for implementing the method of any one of claims 1 to 15.

Images