ASYMMETRIC DL/UL-TRPS UNDER UTCI FRAMEWORK CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefit of U.S. Provisional Application No.63/553,393, filed February 14, 2024, the contents of which are incorporated herein by reference. BACKGROUND [0002] In Third Generation Partnership Project (3GPP) technical specifications up to Release 18, for New Radio Multi-Input-Multiple Output (NR-MIMO) operation, unified transmission configuration indication (UTCI) frameworks have been extended to support multi-transmit/receive point (TRP) scenarios (e.g., up to 2 TRPs), where: up to 2 joint-UTCIs are to be maintained by a WTRU (when configured with a joint-UTCI mode), and up to 4 separate-UTCIs are to be maintained by a wireless transmit/receive unit (WTRU) (e.g., when configured with a separate-DL-UL-UTCI mode). [0003] There is a need to consider an asymmetric DL/UL TRP deployment scenario, where a WTRU communicates with a macro-TRP (TRP1) for both DL reception and UL transmission, while the WTRU communicates with a pico-TRP (TRP2, as a UL-only-TRP) for UL transmission. The pico-TRP (TRP2, as a UL- only-TRP) may not transmit a DL signal or channel, so that pathloss (PL) estimation at the WTRU may be performed based on other DL signals transmitted from a TRP (e.g., TRP1) other than the TRP2. SUMMARY [0004] Methods supporting the operation of asymmetric downlink/uplink transmit/receive points (TRPs) are provided. Information is received indicating first and second sets of transmission configuration indication (TCI) states for use in downlink (DL) and uplink (UL) directions. The second set of TCI states is associated with UL power control (PC) parameters. A first medium access control control element (MAC-CE) is received indicating a set of specifically-ordered TCI states that are mapped to one or more codepoints. A second MAC-CE is received indicating an association between one or more additional UL PC parameters and the set of specifically-ordered TCI states, receiving DCI indicating one of the codepoints associated with a TCI state, and receiving a UL grant. The method includes determining that the set of specifically-ordered TCI states comprises the TCI state, and transmitting a PUSCH transmission, based on the determination, using the TCI state and a determined UL power level. BRIEF DESCRIPTION OF THE DRAWINGS [0005] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein: - 1 - 8902562.1
[0006] FIG.1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented; [0007] FIG.1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0008] FIG.1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0009] FIG.1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG.1A according to an embodiment; [0010] FIG.2 is a table illustrating an example of a mapping between codepoints that may be indicated by a field carried in DCI (e.g., a TCI field) and unified TCI-state indications; [0011] FIG.3 is a diagram illustrating one example of a TCI-activation command; [0012] FIG.4 is a diagram illustrating an example of a UTCI update timeline and UTCI selection procedure for data reception; [0013] FIG.5 is a diagram illustrating an one example of a TCI-activation command; [0014] FIG. 6 is a table illustrating a mapping of a TPC Command Field in a DCI format to absolute and accumulated ^^PUSCH,^^,^^,^^ values or ^^SRS,^^,^^,^^ values; [0015] FIG. 7 is a table illustrating a mapping of a TPC Command Field in a DCI format to accumulated ^^PUCCH,^^,^^,^^ values; [0016] FIG.8 is a diagram illustrating one example of a mapping between codepoints that may be indicated by a field carried in DCI (e.g., a TCI field) and unified TCI-state indications; [0017] FIG.9 is a diagram illustrating one example of a mapping between codepoints that may be indicated by a field carried in DCI (e.g., a TCI field) and unified TCI-state indications; and [0018] FIG.10 is a flow diagram illustrating an example procedure according to one solution. DETAILED DESCRIPTION [0019] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single- carrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- - 2 - 8902562.1
OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like. [0020] As shown in FIG.1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and/or receive wireless signals and may include a user equipment (WTRU), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, 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 applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a WTRU. [0021] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (base station), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted 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. [0022] The base station 114a may be part of the RAN 104, 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, and the like. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may - 3 - 8902562.1
utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions. [0023] 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 communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT). [0024] More specifically, as noted above, the communications 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, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c 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 (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA). [0025] 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). [0026] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using NR. [0027] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by 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., an eNB and a base station). [0028] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, 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), and the like. [0029] The base station 114b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In - 4 - 8902562.1
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 yet another 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 a picocell or femtocell. As shown in FIG.1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106. [0030] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG.1A, it will be appreciated that the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. [0031] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT. [0032] 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 the base station 114a, which may employ a cellular- based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology. [0033] FIG.1B is a system diagram illustrating an example WTRU 102. As shown in FIG.1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will - 5 - 8902562.1
be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. [0034] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. 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 appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip. [0035] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals. [0036] Although the transmit/receive element 122 is depicted in FIG. 1B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116. [0037] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example. [0038] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the 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 - 6 - 8902562.1
removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown). [0039] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the 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 cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li- ion), etc.), solar cells, fuel cells, and the like. [0040] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being 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. [0041] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors. The sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like. [0042] 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 particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via 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 particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)). - 7 - 8902562.1
[0043] FIG.1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106. [0044] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. [0045] 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 UL and/or DL, and the like. As shown in FIG.1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0046] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0047] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve 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 an initial attach of the WTRUs 102a, 102b, 102c, and the like. 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. [0048] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the 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 user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like. [0049] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. [0050] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP - 8 - 8902562.1
multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. [0051] Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. [0052] In representative embodiments, the other network 112 may be a WLAN. [0053] 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 an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication. [0054] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS. [0055] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel. [0056] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non- - 9 - 8902562.1
contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC). [0057] Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control/Machine- Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life). [0058] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the 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 a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle. [0059] In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code. [0060] FIG.1D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106. - 10 - 8902562.1
[0061] The RAN 104 may include base stations 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of base stations while remaining consistent with an embodiment. The base stations 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. For example, base stations 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the base stations 180a, 180b, 180c. Thus, the base station 180a, for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a. In an embodiment, the base stations 180a, 180b, 180c may implement carrier aggregation technology. For example, the base station 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the base stations 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from base station 180a and base station 180b (and/or base station 180c). [0062] The WTRUs 102a, 102b, 102c may communicate with base stations 180a, 180b, 180c using transmissions associated with a 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 base stations 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time). [0063] The base stations 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 the standalone configuration, WTRUs 102a, 102b, 102c may communicate with base stations 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of base stations 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with base stations 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to base stations 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more base stations 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and base stations 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c. [0064] Each of the base stations 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 of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards - 11 - 8902562.1
Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG.1D, the base stations 180a, 180b, 180c may communicate with one another over an Xn interface. [0065] The CN 106 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a,184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0066] The AMF 182a, 182b may be connected to one or more of the base stations 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi. [0067] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like. [0068] The UPF 184a, 184b may be connected to one or more of the base stations 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like. [0069] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c - 12 - 8902562.1
may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b. [0070] In view of FIGs. 1A-1D, and the corresponding description of FIGs. 1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, base station 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions. [0071] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications. [0072] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data. [0073] Various terminology and acronyms as used herein may be defined as follows. The acronym CG may be used to refer to the term "Configured Grant". The acronym DG may be used to refer to the term "Dynamic Grant". The acronym MAC CE may be used to refer to the term "MAC Control Element". The acronym ACK may be used to refer to the term "Acknowledgement". The acronym BLER may be used to refer to the term "Block Error Rate". The acronym BWP may be used to refer to the term "Bandwidth Part". The acronym C-JT may be used to refer to the term "Coherent Joint Transmission". The acronym CP may be used to refer to the term "Cyclic Prefix". The acronym CP-OFDM may be used to refer to the term "Conventional OFDM (relying on cyclic prefix)". The acronym CQI may be used to refer to the term "Channel Quality Indicator". The acronym CRC may be used to refer to the term "Cyclic Redundancy Check". The acronym CSI may be used to refer to the term "Channel State Information". The acronym DAI may be used to refer to the term "Downlink Assignment Index". The acronym DCI may be used to refer to the term "Downlink Control Information". The acronym DL may be used to refer to the term "Downlink". The acronym DM-RS may be used to refer to the term - 13 - 8902562.1
"Demodulation Reference Signal". The acronym DRB may be used to refer to the term "Data Radio Bearer". The acronym HARQ may be used to refer to the term "Hybrid Automatic Repeat Request". The acronym LTE may be used to refer to the term "Long Term Evolution (e.g., from 3GPP LTE R8 and up)". The acronym NACK may be used to refer to the term "Negative ACK". The acronym mTRP may be used to refer to the term "Multiple TRP". The acronym MCS may be used to refer to the term "Modulation and Coding Scheme". The acronym MIMO may be used to refer to the term "Multiple Input Multiple Output". The acronym NC-JT may be used to refer to the term "Non-Coherent Joint Transmission". The acronym NR may be used to refer to the term "New Radio". The acronym OFDM may be used to refer to the term "Orthogonal Frequency-Division Multiplexing". The acronym PHY may be used to refer to the term "Physical Layer". The acronym PMI may be used to refer to the term "Precoding Matrix Indicator". The acronym PRACH may be used to refer to the term "Physical Random Access Channel". The acronym PSS may be used to refer to the term "Primary Synchronization Signal". The acronym RACH may be used to refer to the term "Random Access Channel (or procedure)". The acronym RAR may be used to refer to the term "Random Access Response". The acronym RF may be used to refer to the term "Radio Front End". The acronym RLF may be used to refer to the term "Radio Link Failure". The acronym RLM may be used to refer to the term "Radio Link Monitoring". The acronym RNTI may be used to refer to the term "Radio Network Identifier". The acronym RRC may be used to refer to the term "Radio Resource Control". The acronym RRM may be used to refer to the term "Radio Resource Management". The acronym RS may be used to refer to the term "Reference Signal". The acronym RSRP may be used to refer to the term "Reference Signal Received Power". The acronym RSSI may be used to refer to the term "Received Signal Strength Indicator". The acronym SDU may be used to refer to the term "Service Data Unit". The acronym SRS may be used to refer to the term "Sounding Reference Signal". The acronym SS may be used to refer to the term "Synchronization Signal". The acronym SSS may be used to refer to the term "Secondary Synchronization Signal". The acronym SPS may be used to refer to the term "Semi-Persistent Scheduling". The acronym SUL may be used to refer to the term "Supplemental Uplink". The acronym TB may be used to refer to the term "Transport Block". The acronym TBS may be used to refer to the term "Transport Block Size". The acronym TRP may be used to refer to the term "Transmission / Reception Point". The acronym UL may be used to refer to the term "Uplink". The acronym URLLC may be used to refer to the term "Ultra-Reliable and Low Latency Communications". The acronym WLAN may be used to refer to the term “Wireless Local Area Networks” and related technologies (e.g., in an IEEE 802.xx domain). [0074] Various solutions are proposed herein to address the problem of how to improve beam management efficiency (under UTCI framework) and UL Tx power control, when a UL-TRP does not transmit any DL signal. [0075] Notations and nomenclature as used throughout the following paragraphs are discussed herein. Hereinafter, ‘a’ and ‘an’ and similar phrases are to be interpreted as ‘one or more’ and ‘at least one’. Similarly, any term which ends with the suffix ‘(s)’ is to be interpreted as ‘one or more’ and ‘at least one’. The term ‘may’ is to be interpreted as ‘may, for example’. A symbol ‘/’ (e.g., forward slash) may be used herein to represent ‘and/or’, where for example, ‘A/B’ may imply ‘A and/or B’. Herein, the terms prediction and estimation may be - 14 - 8902562.1
used interchangeably, but still consistent with this invention. Herein, the terms candidate cell, neighbor cell, and target cell may be used interchangeably, but still consistent with this invention. Herein, the terms source cell, current cell, and serving cell may be used interchangeably, but still consistent with this invention. [0076] A definition of a beam is provided herein. A WTRU may transmit or receive using a physical channel or transmit or receive a reference signal according to at least one spatial domain filter. The term “beam” may be used to refer to a spatial domain filter. [0077] The WTRU may transmit using a physical channel or transmit a signal using the same spatial domain filter as the spatial domain filter used for receiving an RS (such as an CSI-RS) or an SS block. The WTRU transmission may be referred to as “target”, and the received RS or SS block may be referred to as “reference” or “source”. In such case, the WTRU may be said to transmit the target physical channel or signal according to a spatial relation with a reference to such RS or SS block. [0078] A WTRU may transmit a first physical channel transmission or signal according to the same spatial domain filter as the spatial domain filter used for transmitting a second physical channel transmission or signal. The first and second transmissions may be referred to as “target” and “reference” (or “source”), respectively. In such case, the WTRU may be said to transmit the first (target) physical channel transmission or signal according to a spatial relation with reference to the second (reference) physical channel transmission or signal. [0079] A spatial relation may be implicit, configured by RRC, signaled by MAC CE or DCI, or by other logically equivalent signaling. For example, a WTRU may implicitly transmit a PUSCH transmission and a DM- RS of the PUSCH according to the same spatial domain filter as an SRS indicated by an SRS resource indicator (SRI) indicated in DCI or configured by RRC. In another example, a spatial relation may be configured by RRC for an SRI or signaled by a MAC CE for a PUCCH. Such spatial relation may also be referred to as a “beam indication”. [0080] The WTRU may receive a first (e.g., target) downlink channel transmission or signal according to the same spatial domain filter or spatial reception parameter as a second (e.g., reference) downlink channel transmission or signal. For example, such association may exist between a physical channel such as PDCCH or PDSCH and its respective DM-RS. At least when the first and second signals are reference signals, such association may exist when the WTRU is configured with a quasi-colocation (QCL) assumption type D between corresponding antenna ports. Such association may be configured as a transmission configuration indicator (TCI) state. A WTRU may be configured with an association between a CSI-RS or SS block and a DM-RS by an index to a set of TCI states, which may be configured by RRC and/or signaled by MAC CE. Such indication may also be referred to as a “beam indication”. [0081] A unified TCI (UTCI) is described herein. A unified TCI (e.g., a common TCI, a common beam, a common RS, etc.) may refer to a beam/RS to be (e.g., simultaneously or substantially simultaneously) used or applied for multiple physical channels/signals. The term “TCI” may at least refer to a TCI state that includes or - 15 - 8902562.1
corresponds to at least one source RS to provide a reference (e.g., WTRU assumption) for determining a QCL assumption or relationship and/or spatial filter. [0082] In some examples, a WTRU may receive (e.g., from a base station) an indication of a first unified TCI to be used/applied for both downlink control channel (PDCCH) and downlink shared channel (PDSCH) transmissions (e.g., and a downlink RS). The source reference signal(s) in the first unified TCI may provide common QCL information at least for WTRU-dedicated reception on the PDSCH and all (or subset of) CORESETs in a CC. In an example, a WTRU may receive (e.g., from a base station) an indication of a second unified TCI to be used/applied for both an uplink control channel (PUCCH) and an uplink shared channel (PUSCH) (e.g., and an uplink RS). The source reference signal(s) in the second unified TCI may provide a reference for determining common UL TX spatial filter(s) at least for dynamic-grant/configured-grant based PUSCH and all (or a subset of) dedicated PUCCH resources in a CC. [0083] The WTRU may be configured with a first mode for unified TCI (e.g., SeparateDLULTCI mode) where an indicated unified TCI (e.g., the first unified TCI or the second unified TCI) may be applicable for downlink (e.g., based on the first unified TCI) or uplink (e.g., based on the second unified TCI). [0084] In some examples, a WTRU may receive (e.g., from a base station) an indication of a second unified TCI to be used/applied commonly for a PDCCH, a PDSCH, a PUCCH, and a PUSCH (and a DL RS and/or a UL RS). [0085] The WTRU may be configured with a second mode for unified TCI (e.g., JointTCI mode) where an indicated unified TCI (e.g., the third unified TCI) may be applicable for both downlink and uplink (e.g., based on the third unified TCI). [0086] The WTRU may determine a TCI state applicable to a transmission or reception by first determining a Unified TCI state instance applicable to this transmission or reception, then determining a TCI state corresponding to the Unified TCI state instance. A transmission may consist of at least PUCCH, PUSCH, SRS. A reception may consist of at least PDCCH, PDSCH, CSI-RS. A Unified TCI state instance may also be referred to as a TCI state group, TCI state process, unified TCI pool, a group of TCI states, a set of time-domain instances/stamps/slots/symbols, and/or a set of frequency-domain instances/RBs/subbands, etc. A Unified TCI state instance may be equivalent with or identified by a CORESET Pool identity (e.g., CORESETPoolIndex, a TRP indicator, and/or the like). [0087] Hereafter, the term unified TCI may be interchangeably used with one or more of the terms unified TCI-states, unified TCI instance, TCI, and TCI-state, but may remain consistent with the solutions proposed herein. [0088] TRPs, MTRPs, and M-TRPs are discussed herein. Hereafter, the term TRP (e.g., transmission and reception point) may be interchangeably used with one or more of TP (transmission point), RP (reception point), RRH (radio remote head), network node, DA (distributed antenna), BS (base station), a sector (of a BS), and a cell (e.g., a geographical cell area served by a BS), but still consistent with this invention. Hereafter, Multi- - 16 - 8902562.1
TRP may be interchangeably used with one or more of MTRP, M-TRP, or multiple TRPs, but still consistent with the solutions proposed herein. [0089] Configurations for TRPs, SRIs, and PL reference RS(s) are described herein. A WTRU may be configured with (or may receive configuration information for) one or more TRPs to which the WTRU may transmit and/or from which the WTRU may receive. The WTRU may be configured with one or more TRPs for one or more cells. A cell may be a serving cell, and/or a secondary cell. [0090] A WTRU may be configured with at least one RS for the purpose of channel measurement. This RS may be denoted as a Channel Measurement Resource (CMR) and may include a CSI-RS, SSB, or other downlink RS transmitted from the TRP to a WTRU. A CMR may be configured or associated with a TCI state. A WTRU may be configured with a CMR group where CMRs transmitted from the same TRP may be configured. Each group may be identified by a CMR group index (e.g. group 1). In some examples, a WTRU may be configured with one CMR group per TRP, and the WTRU may receive a linkage 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. [0091] A WTRU may be configured with (or receive configuration information for) one or more pathloss (PL) reference groups (e.g., sets) and/or one or more SRS groups, SRS resource indicator (SRI) or SRS resource sets. [0092] A PL reference group may correspond to or may 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 set, SRI sets), CORESET index, and or reference signals (e.g. CSI-RS, SSB). [0093] A WTRU may receive a configuration (e.g., any configuration described herein) or configuration information. The configuration or configuration information may be received from a base station or TRP. For example, the WTRU may receive configuration information for, associated with, or concerning one or more TRPs, one or more PL reference groups and/or one or more SRI sets. A WTRU may implicitly determine an association between a RS set/group and a TRP. For example, if the WTRU is configured with two SRS resource sets, then the WTRU may determine to transmit to TRP1 with SRS in the first resource set, and to TRP2 with SRS in the second resource set. The configuration may be provided, sent, or received via RRC signaling or via other logically equivalent signaling. [0094] 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. [0095] CSI components are described herein. A WTRU may report a subset of channel state information (CSI) components, where one or more CSI components may correspond to at least a CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI), an indication of a panel used for reception at the WTRU (such as a panel identity or group identity), measurements such as L1-RSRP, L1-SINR taken from 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 - 17 - 8902562.1
rank indicator (RI), channel quality indicator (CQI), precoding matrix indicator (PMI), Layer Index (LI), and/or the like. [0096] Properties of a grant or assignment are described herein. In the following, a property of a grant or assignment may include one or more of the following: a frequency allocation; an aspect of time allocation, such as a duration; a priority; a modulation and coding scheme; a transport block size; a number of spatial layers; a number of transport blocks; a TCI state, CRI or SRI; a number of repetitions; whether a repetition scheme is Type A or Type B; whether the grant is a configured grant type 1, type 2 or a dynamic grant; whether the assignment is a dynamic assignment or a semi-persistent scheduling (configured) assignment; a configured grant index or a semi-persistent assignment index; a periodicity of a configured grant or assignment; a channel access priority class (CAPC); or any parameter provided in a DCI, by MAC, by RRC, or by other logically equivalent signaling for the scheduling the grant or assignment. [0097] In the following, an indication provided by DCI may include one or more of the following: an explicit indication by a DCI field or by RNTI used to mask CRC of the PDCCH; or an implicit indication by a property such as DCI format, DCI size, CORESET or search space, aggregation level, first resource element of the received DCI (e.g., index of first Control Channel Element), where the mapping between the property and the value may be signaled by RRC or MAC, or by other logically equivalent signaling. [0098] As used herein, the term signal may be interchangeably used with one or more of following while remaining consistent with specific solutions proposed herein: sounding reference signal (SRS); channel state information – reference signal (CSI-RS); demodulation reference signal (DM-RS); phase tracking reference signal (PT-RS); or synchronization signal block (SSB). [0099] As used herein, the term channel may be interchangeably used with one or more of following terms while remaining consistent with specific solutions proposed herein: physical downlink control channel (PDCCH); physical downlink shared channel (PDSCH); physical uplink control channel (PUCCH); physical uplink shared channel (PUSCH); physical random access channel (PRACH); or other types of channels. Hereafter, the term downlink reception may be used interchangeably with Rx occasion, PDCCH, PDSCH, and/or SSB reception, but may remain consistent with solutions proposed herein. Hereafter, the term uplink transmission may be used interchangeably with Tx occasion, PUCCH, PUSCH, PRACH, and/or SRS transmission, while remaining consistent with specific solutions proposed herein. Hereafter, the term RS may be interchangeably used with one or more of RS resource, RS resource set, RS port and/or RS port group, while remaining consistent with specific solutions proposed herein. Hereafter, the term RS may be interchangeably used with one or more of SSB, CSI-RS, SRS and/or DM-RS, but may remain consistent with solutions proposed herein. As used herein, the term time instance may be interchangeably used with the terms slot, symbol, and/or subframe while remaining consistent with specific solutions proposed herein. Hereafter, the term UTCI may be interchangeably used with the terms TCI, UTCI state, and/or TCI state, but may remain consistent with specific solutions proposed herein. - 18 - 8902562.1
[0100] Aspects common to some or all solutions are discussed herein. [0101] A WTRU may be configured with a plurality of transmission configuration indicator (TCI) states (e.g., configured by a (RRC) parameter ‘TCI-State’ IE or by other logically equivalent parameters or signaling), e.g., unified TCI (UTCI) states, each applicable for multiple channel(s)/signal(s). The multiple channel(s)/signal(s) may be configured at the WTRU (or pre-determined or defined), e.g., in a form of a list, by a higher-layer signaling (e.g., RRC, and/or MAC-CE, or other logically equivalent signaling) which may include at least one of following (e.g., as a combination): one or more CORESETs; one or more PDCCH candidates; one or more search spaces; one or more PDSCHs (e.g., PDSCH occasions/configurations/instances, etc.); one or more RSs (e.g., CSI-RSs, DMRSs, SSB indexes, PRSs, PTRSs, and/or SRSs); one or more PUSCHs (e.g., PUSCH occasions/configurations/instances, etc.); one or more PUCCH resources (e.g., PUCCH resource sets/groups); or one or more PRACH occasions/resources/RSs. [0102] The plurality of TCI states may be configured via RRC signaling (e.g., and/or via a MAC-CE signaling, indication or activation, or other logically equivalent signaling). The WTRU may receive, e.g., via the MAC-CE or a separate signaling, an information content comprising mapping between one or more codepoints of a DCI field (e.g., TCI field, and/or TCI selection field) and at least one TCI state of the plurality of TCI states. The WTRU may receive DCI that includes the DCI field. The WTRU may be indicated with one or more TCI states, of the plurality of TCI states, mapped to a codepoint of the one or more codepoints of the DCI field, where each of the one or more TCI states is applicable after a time duration determined based on a beam application time (BAT) parameter. [0103] FIG.2 is a table illustrating an example of a mapping between codepoints that may be indicated by a field carried in DCI (e.g., a TCI field) and unified TCI-state indications. The WTRU may receive, e.g., via a MAC-CE or other logically equivalent signaling, a mapping between codepoints (any one of which may be indicated by the DCI field) and one or more TCI states {X, Y}. In an example, the list of the multiple channel(s)/signal(s) may be given per UTCI instance, where the UTCI instance may correspond to each column of the mapping table, illustrated in FIG.2, between a codepoint and the one or more TCI states. A list of the multiple channel(s)/signal(s) (or alternatively multiple lists/sets of channel(s)/signal(s)) may be configured at the WTRU by signaling (e.g., higher layer signaling) received from a base station. [0104] Specifically, in the example shown in FIG.2, a first UTCI instance X, if present for a given codepoint, may be applied for a first list or set of channel(s) or signal(s), and a second UTCI instance Y, if present for a given codepoint may be applied for a second list or set of channel(s) or signal(s). For example, a DCI may include a 3-bit TCI field that carries a value indicating or associated with Codepoint 2, as shown at 210. As shown at 210 in FIG.2, Codepoint 2 is mapped to {UTCI3, UTCI7}. Upon receiving DCI indicating Codepoint 2, the WTRU may apply at least one of {UTCI3, UTCI7} to the multiple channel(s)/signal(s), e.g., based on one or more configured lists of the multiple channel(s)/signal(s). Additionally, as shown at 220 in FIG.2, Codepoint 7 is mapped to {UTCI5, UTCI8}. Upon receiving DCI indicating Codepoint 7, the WTRU may apply at least one of {UTCI5, UTCI8} to the multiple channel(s)/signal(s), e.g., based on one or more configured lists of the - 19 - 8902562.1
multiple channel(s)/signal(s). The example shown in FIG.2 may represent an example case in which the WTRU is configured with a “joint DL/UL UTCI mode”, e.g., when configured with a parameter such as ‘unifiedTCI- StateType’ set to ‘joint’, where for the joint DL/UL UTCI mode, an indicated UTCI from the plurality of TCI-states (e.g., including TCI-state#0, #1, #2, …, #127) may be used for not only for receiving a (e.g., DL) channel or signal but also for transmitting a (e.g., UL) channel or signal. In an example, a MAC-CE command (e.g., a TCI- state activation command, such as an “Enhanced UTCI States Activation/Deactivation MAC CE for Joint TCI states”) may provide necessary information for the WTRU to determine a mapping between one or more codepoints of a DCI field (e.g., TCI field) and one or more TCI states of the plurality of TCI states, which may be illustrated based on examples shown in FIG.3, introduced and described in further detail in paragraphs below. [0105] FIG. 3 is a diagram illustrating one example of a TCI-activation command. A TCI-activation command 300, may have the format shown in FIG.3, may be provided, e.g., via a MAC-CE, ‘Enhanced UTCI state activation/deactivation MAC CE for Joint TCI States’ or via other logically equivalent signaling. [0106] Examples that relate to or involve the use of an ‘Enhanced UTCI state activation/deactivation MAC CE for Joint TCI States’ are described herein. In accordance with the example shown in FIG.3, a WTRU that receives the TCI-activation command may identify (e.g., determine) the TCI-activation command 300 (e.g., via a MAC-CE, such as an ‘Enhanced UTCI state activation/deactivation MAC CE for Joint TCI States’) based on a MAC subheader that includes an eLCID (which may indicate a type of the MAC-CE message for the TCI- activation command). The TCI-activation command 300 may have a variable size and may include one or more fields. [0107] One field that may be included in the TCI-activation command 300, as shown in FIG.3, may be a ‘Serving Cell ID’. This field may indicate the identity of a Serving Cell for which the MAC CE (e.g., the TCI- activation command) applies. The length of the field may be, for example, 5 bits. [0108] One field that may be included in the TCI-activation command 300, as shown in FIG.3, may be a ‘DL BWP ID’. This field may indicate a DL BWP for which the MAC CE (e.g., the TCI-activation command) applies, where the DL BWP may be associated with a codepoint of a ‘bandwidth part indicator field’ in a DCI. The length of the BWP ID field may be, for example, 2 bits. [0109] One field that may be included in the TCI-activation command 300, as shown in FIG.3, may be a ‘Fi,j’ field. This field may indicate, for the ‘TCI state ID’ fields (shown below) associated with the codepoint i of the DCI ‘TCI field’, whether the j-th joint TCI state is present or not, where j=1, 2. For example, the parameter ‘j’ may correspond to a column (e.g., a UTCI instance, pointing to a particular TRP, and/or pointing to a set of specifically-ordered TCI-states (positioned in one column) for example as either of a “first indicated TCI-state (e.g., corresponding to the first column)” or a “second indicated TCI-state (e.g., corresponding to the first column)”, etc.) mentioned in paragraphs above or as illustrated in FIG.2. If the Fi,j field is set to 1, the field may indicate that the j-th joint TCI state for codepoint i is present. If the Fi,j field is set to 0, it may indicate that - 20 - 8902562.1
the j-th joint TCI state for codepoint i is absent. The codepoint to which a TCI state is mapped may be determined by its ordinal position (e.g., column, UTCI instance, etc., which may be illustrated by way of example in FIG.2) among all the ‘TCI state ID’ fields. [0110] One field that may be included in the TCI-activation command 300, as shown in FIG.3, may be a ‘TCI state ID’ field. This field may indicate a TCI-state (e.g., a 7-bit-length TCI state ID, TCI-state#X), e.g., of the plurality of TCI-states. The WTRU may determine that the TCI-state indicated by the field ‘TCI state ID’ is now being activated, where the TCI-state becomes an activated TCI-state, e.g., which may be a deactivated TCI-state before receiving the ‘TCI state ID’ field of the TCI-activation command 300. The maximum number of activated TCI states may be N_activated (e.g., N_activated = 16), where the WTRU may maintain (e.g., keep tracking, keep tracking one or more QCL properties on) only up to N_activated TCI-states out of the plurality of TCI-states. [0111] One field that may be included in the TCI-activation command 300, as shown in FIG.3, may be an ‘R’ field. This field may include a reserved bit, which may be set to 0. [0112] FIG.4 is a diagram illustrating an example of a UTCI update timeline and UTCI selection procedure for data reception. Specifically the timeline illustrated in FIG.4 may pertain to actions by a WTRU for receiving DCI, updating or applying a beam configuration based on the received DCI, and receiving downlink transmissions or signals based on the applied beam configuration. In the example shown in FIG. 4, at a reference time instance t0, it may be assumed that the WTRU may currently use and/or apply {TCI3, TCI7}, e.g., based on having received an indication to apply ‘Codepoint 2’, as illustrated in the example of FIG.2, for communication with a base station. For example, the WTRU may apply TCI3 for communication with TRP1 (which may be associated with the base station) and TCI7 for communication with TRP2 (which may also be associated with the base station). [0113] As is further shown in FIG.4, subsequent to t0 , at 401, the WTRU may receive DCI1 indicating a set of TCI states (i.e., {TCI3, TCI7}) which may be the same TCI states already in use by the WTRU. The indication of {TCI3, TCI7} may be provided via a 3-bit TCI field of the DCI1 having a value of ‘010’. DCI1 may also schedule PDSCH1 (e.g., a data packet) which may be transmitted at a scheduling offset (also referred to herein as a time offset or time instance) k0, after the DCI1 is transmitted. The value of k0 may be indicated in the same DCI1, or it may be provided via separate signaling. [0114] The DCI1 may further indicate a selector, e.g., via a TCI-selection field, where the selector may select at least one of the currently used TCI states, e.g., {TCI3, TCI7}. The TCI states already in use may be determined with respect to a time instance corresponding to the reception of DCI1, or with respect to a time instance corresponding to the reception of PDSCH1 scheduled by the DCI1. The TCI-selection field may include at least one codepoint as follows. In the case the TCI-selection field indicates a value of ‘00’ (i.e., indicating Codepoint ‘00’), the WTRU may apply a first TCI state. In the case the TCI-selection field indicates a value of ‘01’, (i.e., indicating Codepoint ‘01’), the WTRU may apply a second TCI state. In the case the TCI- - 21 - 8902562.1
selection field indicates a value of ‘10’, (i.e., indicating Codepoint ‘10’), the WTRU may apply both TCI states. In the case the TCI-selection field indicates a value of ‘11’ (i.e., indicating Codepoint ‘11’), the selection may be reserved. [0115] In some examples, the WTRU may determine that the TCI-selection field of the DCI1 indicates a value (e.g., Codepoint ‘00’) which corresponds to applying 1st TCI state, that is {TCI3}, e.g., among the currently used TCI states {TCI3, TCI7}. The WTRU may determine that the indicated scheduling offset k0 is greater than a threshold, denoted as ‘Th’. The threshold may be based on the WTRU’s capability or configuration, which may be reported by the WTRU. If the scheduling offset k0 is greater than (or equal to) the threshold, as is shown in FIG.4 at 411, the WTRU may (be able to) decode the contents of DCI1, e.g., due to having a sufficient decoding time necessary for the WTRU to interpret DCI1. In an alternative scenario not depicted, the WTRU may be unable to apply the contents of DCI1 due to having insufficient decoding time before receiving the PDSCH1. In such a scenario, the WTRU may need to receive the PDSCH1 by using a default TCI state(s). This may be necessary because, once the WTRU receives the PDSCH1, there may be at least one parameter or component, e.g., a spatial-domain (receive) filter or analog-filter coefficient(s), etc., that cannot be changed or adjusted by a post-processing on the received PDSCH1 (after receiving the PDSCH1). [0116] As shown at 421, the WTRU may receive the scheduled PDSCH1 based on {TCI3} indicated by the selector (e.g., by the TCI-selection field). Specifically, the WTRU may apply the set of TCI states {TCI3, TCI7} indicated by the TCI field of DCI1 after (1) receiving the scheduled PDSCH1, (2) transmitting a corresponding acknowledgement (e.g., HARQ-ACK), and (3) acting in accordance with a BAT parameter, where the BAT parameter may be pre-configured at the WTRU, or indicated to the WTRU (e.g., by the base station). In the example shown in FIG.4 at 431, the WTRU determines, based on the TCI field, that the set of TCI states to be applied is not changed., Accordingly, applying the indicated set of TCI states {TCI3, TCI7} in response to the DCI1 may be equivalent to maintaining the currently used ones because the same set of TCI states {TCI3, TCI7} have been used. [0117] In a subsequent time interval, as shown at 402, the WTRU may receive DCI2 indicating a set of TCI states{TCI5, TCI8}, e.g., via a TCI field. Notably, the indicated set of TCI states {TCI5, TCI8} is different from the currently applied set of TCI states {TCI3, TCI7}. DCI2 schedules PDSCH2 (e.g., data packet) which is transmitted k0 after the DCI2 is transmitted. The value of k0 may be indicated in the same DCI2 (or via a separate signaling). The DCI2 may further indicate a selector, e.g., a TCI-selection field, that selects at least one TCI states from among the currently applied TCI states. Because the currently applied TCI states may be determined at the time DCI2 is received, the WTRU may select from among the set of TCI states {TCI3, TCI7}, and not from among the newly indicated set of TCI states {TCI5, TCI8}. [0118] In some examples, the WTRU may determine that the TCI-selection field of the DCI2 indicates a value (e.g., Codepoint ‘01’) which corresponds to applying 2nd TCI state, that is {TCI7}, not yet {TCI8}, e.g., among the currently applied TCI states {TCI3, TCI7}. As shown at 412, the WTRU may determine that the indicated scheduling offset k0 is greater than a threshold, denoted as ‘Th’, where the threshold may be based - 22 - 8902562.1
on the WTRU’s capability which may be reported by the WTRU. As shown at 422, the WTRU may receive the scheduled PDSCH2 based on the selected TCI state, {TCI7}, indicated by the selector (e.g., by the TCI- selection field). The threshold ‘Th’ may be the same threshold as described above in the previous example. [0119] The WTRU may apply the set of TCI states {TCI5, TCI8} indicated by the TCI field of DCI2 after (1) receiving the scheduled PDSCH2, (2) transmitting a corresponding acknowledgement (e.g., HARQ-ACK), and/or (3) a BAT parameter, where the BAT parameter may be pre-configured (or indicated) to the WTRU (from the base station). In an example, applying the indicated {TCI5, TCI8} in response to the DCI2 may be interpreted as a “beam or TCI update” because the indicated set of TCI states {TCI5, TCI8} is different from the currently applied set of TCI states {TCI3, TCI7}. The WTRU may determine that a “first indicated TCI state (e.g., corresponding to the first column)” becomes {TCI5} when updated from the previous TCI state {TCI3}. The WTRU may determine that a “second indicated TCI state (e.g., corresponding to the second column)” becomes {TCI8} when updated from the previous TCI state {TCI7}. [0120] In a subsequent time interval, as shown at 403, the WTRU may receive DCI3 indicating {TCI5, TCI8}, e.g., via a TCI field of the DCI3, which may be the same as the currently applied set of TCI states {TCI5, TCI8}. DCI3 may scheduling a PDSCH transmission, PDSCH3 (e.g., data packet) which is transmitted k0 after the DCI3 is transmitted. The value of k0 may be indicated in the same DCI3 (or via a separate signaling). The DCI3 may further indicate a selector, e.g., via a TCI-selection field, where the selector may select at least one TCI state from among the currently applied set of TCI states {TCI5, TCI8}. The currently applied set of TCI states may be determined by the WTRU when receiving DCI3. [0121] In some examples, as illustrated at 413, the WTRU may determine, Th after receiving the DCI3 (e.g., Th[msec] after receiving the DCI3), that the TCI-selection field of the DCI3 indicates a value (e.g., Codepoint ‘11’) which corresponds to the selection of TCI states, that is {TCI5, TCI8} among the currently used ones {TCI5, TCI8}. However, the WTRU may receive the PDSCH3 transmission before it is able to determine some or all of the contents of DCI3, because the scheduling offset k0 indicated by the DCI3 is less than the threshold Th (e.g., a parameter of WTRU capability on DCI decoding and/or processing time (or latency), etc.). The WTRU may receive the scheduled PDSCH3 transmission, as shown at 423, before determining that the k0 is less than the Th, which means the WTRU may determine at least one default beam (or TCI) to store a (e.g., any) downlink signal (including the actual PDSCH3 packet) until identifying (or decoding) contents carried by DCI3. The default beam may be a specifically-ordered position of a configured set of TCI states (e.g., the “first indicated TCI-state”, which may correspond to a first column of a table, such as the table illustrated in FIG.2). [0122] At 431, the WTRU determines, based on the TCI field, that the set of TCI states to be applied is not changed. For example, the WTRU may maintain the set of TCI states {TCI5, TCI8} as indicated by the TCI field of DCI3 after (1) receiving the scheduled PDSCH3 transmission, (2) transmitting a corresponding acknowledgement (e.g., HARQ-ACK), and/or (3) a BAT parameter, where the BAT parameter may be pre- configured (or indicated) to the WTRU (from the base station). - 23 - 8902562.1
[0123] Examples based on or involving the use of MAC CEs (e.g., enhanced UTCI state activation/deactivation MAC CEs) for separate TCI states are described herein. [0124] In some examples (e.g., examples based on an extension from FIG.2), an example case in which the WTRU is configured with a “separate DL/UL UTCI mode” may be considered, e.g., when configured with a parameter such as ‘unifiedTCI-StateType’ is set to ‘separate’. For the separate DL/UL UTCI mode, the WTRU may be configured with a first plurality of TCI-states (e.g., a first TCI-state pool, a joint-DL-TCI-states pool, e.g. comprising TCI-state#0, #1, #2, …, #127) and a second plurality of TCI-states (e.g., a second TCI-state pool, a UL-TCI-state pool, e.g. comprising UL-TCI-state#0, #1, #2, …, #63). The first plurality of TCI-states may be used for receiving a (e.g., DL) channel or signal, and separately, the second plurality of TCI-states may be used for transmitting a (e.g., UL) channel or signal. [0125] In some examples, a MAC-CE command (e.g., TCI-state activation command, e.g., “Enhanced UTCI States Activation/Deactivation MAC CE for Separate TCI states”) may provide necessary information for the WTRU to determine a mapping between one or more codepoints of a DCI field (e.g., TCI field) and one or more TCI states of the first and/or second plurality of TCI states, for example, as illustrated in FIG.5. [0126] FIG. 5 is a diagram illustrating one example of a TCI-activation command. A TCI-activation command 500 may have the format illustrated in FIG.5 and may be provided, for example, via a MAC-CE, such as an ‘Enhanced UTCI state activation/deactivation MAC CE for Separate TCI States’, or via other logically equivalent signaling). [0127] In some solutions, , a WTRU may identify (e.g., determine) a TCI-activation command 500 having a format such as that shown in FIG.5 (which may be included, for example, in a MAC-CE such as an ‘Enhanced UTCI state activation/deactivation MAC CE for Separate TCI States’) based on a MAC subheader that includes an eLCID (which may indicate a type of the MAC-CE message for the TCI-activation command 500). The TCI- activation command 500 may have a variable size and include one or more fields, as may be described in the following paragraphs. [0128] A ‘Serving Cell ID’ field may be included in the TCI-activation command 500, as shown in FIG. 5, and may indicate the identity of a Serving Cell for which the MAC CE (e.g., the TCI-activation command) applies. The length of the field may be, for example, 5 bits. [0129] A ‘DL BWP ID’ field may be included in the TCI-activation command 500, as shown in FIG.5, and may indicate a DL BWP for which the MAC CE (e.g., the TCI-activation command 500) applies, where the DL BWP may be associated with a codepoint of a ‘bandwidth part indicator field’ in a DCI. The length of the BWP ID field may be, for example, 2 bits. [0130] A ‘UL BWP ID’ field may be included in the TCI-activation command 500, as shown in FIG.5, and may indicate a UL BWP for which the MAC CE (e.g., the TCI-activation command 500) applies, where the UL BWP may be associated with a codepoint of a ‘bandwidth part indicator field’ in a DCI. The length of the BWP ID field may be, for example, 2 bits. - 24 - 8902562.1
[0131] A ‘Fi,j’ field may be included in the TCI-activation command 500, as shown in FIG. 5, and may indicate for the ‘TCI state ID’ fields (shown below) associated with the codepoint i of the DCI ‘TCI field’ whether the j-th DL TCI state is present or not, where j=1, 2. For example, the parameter ‘j’ may correspond to a column (e.g., a UTCI instance, pointing to a particular TRP, and/or pointing to a set of specifically-ordered TCI-states (positioned in one column) as illustrated, for example, in FIG.2). If the Fi,j field is set to 1, it may indicate the j-th DL TCI state for codepoint i is present. If Fi,j field is set to 0, it may indicates the j-th DL TCI state for codepoint i is absent. [0132] An ‘Si,j’ field may be included in the TCI-activation command 500, as shown in FIG. 5, and may indicate for the ‘TCI state ID’ fields (shown below) associated with the codepoint i of the DCI ‘TCI field’ whether the j-th UL TCI state is present or not, where j=1, 2. For example, the parameter ‘j’ may correspond to a column (e.g., a UTCI instance, pointing to a particular TRP, and/or pointing to a set of specifically-ordered TCI-states (positioned in one column) as illustrated, for example, in FIG.2). In some examples, if the Si,j field is set to 1, it may indicate the j-th UL TCI state for codepoint i is present. If the Si,j field is set to 0, it may indicate the j-th UL TCI state for codepoint i is absent. [0133] A ‘TCI state ID’ field may be included in the TCI-activation command 500, as shown in FIG.5, and may indicate a TCI-state (e.g., a 7-bit-length TCI state ID, TCI-state#X or UL-TCI-state#Y), e.g., of either the first or second plurality of TCI-states. If the indicated TCI state ID is a DL-TCI state (e.g., by the ‘Fi,j’ field), the indicated TCI state ID may be one of TCI-state#0, #1, #2, …, #127 (from the first plurality of TCI-states). If the indicated TCI state ID is an UL TCI state, the most significant bit of the TCI state ID may be considered as the reserved bit and/or a bit-length (e.g., the remainder 6 bits) of the TCI state ID may indicate one of UL-TCI- state#0, #1, #2, …, #63 (from the second plurality of TCI-states). TCI state IDs may be in the order of indication of Fi,j and Si,j fields. The WTRU may determine that the TCI-state indicated by the field ‘TCI state ID’ is now being activated, where the TCI-state becomes an activated TCI-state. The TCI state that is being activated may be a deactivated TCI-state before receiving the ‘TCI state ID’ field of the TCI-activation command. The maximum number of activated TCI states may be N_activated (e.g., N_activated = 32), where the WTRU may maintain (e.g., keep tracking, keep tracking one or more QCL properties on) only up to N_activated TCI-states out of the first and/or second plurality of TCI-states. An ‘R’ field may indicate a reserved bit, which may be set to 0. [0134] Examples relating to PUSCH power control are described herein. [0135] Eq. 1 is an equation for calculation of PUSCH transmission power in a PUSCH transmission occasion ^^. If a WTRU transmits a PUSCH on active UL BWP ^^ of carrier ^^ of serving cell ^^ using a parameter set configuration with index ^^ and PUSCH power control adjustment state (e.g., a closed-loop(CL)-power- control index) with index ^^, the WTRU may determine the PUSCH transmission power ^^PUSCH,^^,^^,^^(^^, ^^, ^^^^ , ^^) in PUSCH transmission occasion ^^ from the equation shown in Eq.1. - 25 - 8902562.1
^^PUSCH,^^,^^,^^(^^, ^^, ^^^^ , ^^) = ^^CMAX,^^,^^(^^), ^^)}
[0137] ^^O_PUSCH,^^,^^,^^(^^) may represent a nominal power level, e.g., a parameter composed of the sum of a component ^^O_NOMINAL,PUSCH,^^,^^(^^) and a component ^^O_WTRU_PUSCH,^^,^^,^^(^^) where ^^ ∈ {0,1, … , ^^ − 1}. Each value of to a different PUSCH transmission type that may enable a different UL power level setting
transmissions. For example, j=0 may be for supporting RACH procedure, e.g., a msg3 PUSCH transmission. For example, j=1 may be for a different type of PUSCH transmission, e.g., in relation to SRS transmissions, etc. [0138] ^^^^,^^,^^(^^) (e.g, ‘alpha’) may be a nominal PL-compensation-ratio parameter, which is multiplied by the PL term (^^^^^^,^^,^^(^^^^)). [0139] ^^R P BU ,S ^^ C ,^ H ^,^^ (^^) may be the bandwidth of the PUSCH resource assignment expressed by a number of resource transmission occasion ^^ on active UL BWP ^^ of carrier ^^ of serving cell ^^, and ^^
may an configuration. [0140] ^^^^^^,^^,^^(^^^^) may be a downlink pathloss estimate in dB calculated by the WTRU using the reference signal (RS) index ^^^^ for the active DL BWP of carrier ^^ of serving cell ^^. [0141] ∆TF,^^,^^,^^(^^) may be an additional power adjustment parameter. [0142] For the PUSCH power control adjustment state ^^^^,^^,^^(^^, ^^), e.g., a closed-loop (CL) PC index, CLPC-index, CL-index, for active UL BWP ^^ of carrier ^^ of serving cell ^^ in PUSCH transmission occasion ^^, ^^PUSCH,^^,^^,^^(^^, ^^) may represent a TPC command value included in a DCI format that schedules the PUSCH transmission occasion ^^ on active UL BWP ^^ of carrier ^^ of serving cell ^^ or ir may be jointly coded with other TPC commands in a DCI format 2_2 (e.g., a group-common DCI which may be transmitted to multiple WTRUs as broadcast or multicast signaling) with CRC scrambled by TPC-PUSCH-RNTI. ^^ ∈ {0,1}, e.g., CL-index l = 0 or 1, if the WTRU is configured with twoPUSCH-PC-AdjustmentStates and ^^ = 0 if the WTRU is not configured with twoPUSCH-PC-AdjustmentStates or if the PUSCH transmission is scheduled by a RAR UL grant. [0143] ^^^^,^^,^^(^^, ^^) = ^^^^,^^,^^(^^ − ^^0, ^^) + ∑ C(^^^^)−1 ^^=0 ^^PUSCH,^^,^^,^^(^^, ^^) may represent the PUSCH power control adjustment
process with index l (e.g for PUSCH)) for active UL BWP ^^ of carrier ^^ of serving cell ^^ and PUSCH transmission occasion ^^ if the WTRU - 26 - 8902562.1
is not provided tpc-Accumulation, where ∑ C ^^ ( =^^ ^^ 0 )−1 ^^PUSCH,^^,^^,^^(^^, ^^) may represent a sum of TPC command values in a set ^^^^ of TPC command values with cardinality C(^^^^) that the WTRU receives between ^^PUSCH(^^ − ^^0) − 1 symbols before PUSCH transmission occasion ^^ − ^^0 and ^^PUSCH(^^) symbols before PUSCH transmission occasion ^^ on active UL BWP ^^ of carrier ^^ of serving cell ^^ for PUSCH power control adjustment state ^^, where ^^0 > 0 is the smallest integer for which ^^PUSCH(^^ − ^^0) symbols before PUSCH transmission occasion ^^ − ^^0 is earlier than ^^PUSCH(^^) symbols before PUSCH transmission occasion ^^. [0144] If a PUSCH transmission is scheduled by a DCI format, ^^PUSCH(^^) may represent a number of symbols for active UL BWP ^^ of carrier ^^ of serving cell ^^ after a last symbol of a corresponding PDCCH reception and before a first symbol of the PUSCH transmission. [0145] ^^^^,^^,^^(^^, ^^) = ^^PUSCH,^^,^^,^^(^^, ^^) may represent the PUSCH power control adjustment state for active UL BWP ^^ of carrier ^^ of serving cell ^^ and PUSCH transmission occasion i if the WTRU is provided tpc-Accumulation, where the ^^PUSCH,^^,^^,^^ absolute values may be given in FIG.6. [0146] FIG. 6 is a table illustrating a mapping of a TPC Command Field in a DCI format to absolute and accumulated ^^PUSCH,^^,^^,^^ values or ^^SRS,^^,^^,^^ values. A WTRU may be configured to receive a DCI format that includes TPC Command Field with one of the values shown in table 600. The DCI format that may carry a TPC Command Field with a value as shown in table 600 may be, for example, a DCI format scheduling a PUSCH transmission, or a DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, or a DCI format 2_3. [0147] Examples for PUCCH power control are described herein. [0148] Eq.2 is an equation for calculation of the PUCCH transmit power (in dBm) in a PUCCH transmission occasion ^^. If a WTRU transmits a PUCCH on active UL BWP ^^ of carrier ^^ in the primary cell ^^ using PUCCH power control adjustment state (e.g., a CL-index) with index ^^ , the WTRU may determine the PUCCH transmission power ^^PUCCH,^^,^^,^^(^^, ^^^^ , ^^^^ , ^^) in PUCCH transmission occasion ^^ as shown in Eq.2. ^^PUCCH,^^,^^,^^(^^, ^^^^, ^^^^ , ^^) =
^^)}
configured maximum output power for carrier ^^ of primary cell ^^ in PUCCH transmission occasion ^^ . ^^O_PUCCH,^^,^^,^^(^^^^) may represent a nominal power level, e.g., a parameter composed of the sum of a component ^^O_NOMINAL,PUCCH , provided by p0-nominal, or ^^O_NOMINAL,PUCCH = 0 dBm if p0-nominal is not provided, for carrier ^^ of primary cell ^^ and, if provided, a component ^^O_WTRU_PUCCH(^^^^) provided by p0- PUCCH-Value in P0-PUCCH for active UL BWP ^^ of carrier ^^ of primary cell ^^, where 0 ≤ ^^^^ < ^^^^. ^^^^ is a size for a set of ^^O_WTRU_PUCCH values provided by maxNrofPUCCH-P0-PerSet. The set of ^^O_WTRU_PUCCH - 27 - 8902562.1
values may be provided by the parameter p0-Set. If the parameter p0-Set is not provided to the WTRU, ^^O_PUCCH,^^,^^,^^(^^^^) = 0, 0 ≤ ^^^^ < ^^^^. [0150] ^^ PUCCH (^^) a bandwidth of the PUCCH resource assignment expressed by a occasion ^^ on active UL BWP ^^ of carrier ^^ of primary cell
[0151] ^^^^^^,^^,^^(^^^^) may represent a downlink pathloss estimate in dB calculated by the WTRU using RS resource index ^^^^ for the active DL BWP ^^ of carrier ^^ of the primary cell ^^. If the WTRU is not provided with parameters such as pathlossReferenceRSs and enableDefaultBeamPL-ForPUCCH, or before the WTRU is provided with dedicated higher layer parameters, the WTRU calculates ^^^^^^,^^,^^(^^^^) using a RS resource obtained from an SS/PBCH block with the same SS/PBCH block index as the one the WTRU uses to obtain MIB, or using a SS/PBCH block by which the WTRU acquired time and frequency synchronization for a secondary cell. [0152] If the WTRU is provided with a number of RS resource indexes, the WTRU may calculate ^^^^^^,^^,^^(^^^^) using a RS resource with index ^^^^, where 0 ≤ ^^^^ < ^^^^. ^^^^ is a size for a set of RS resources provided by the parameter maxNrofPUCCH-PathlossReferenceRSs. The set of RS resources may be provided by a parameter such as pathlossReferenceRSs. The set of RS resources may include one or both of a set of SS/PBCH block indexes, each provided by the parameter ssb-Index in PUCCH-PathlossReferenceRS when a value of a corresponding pucch-PathlossReferenceRS-Id maps to a SS/PBCH block index, and a set of CSI- RS resource indexes, each provided by csi-RS-Index when a value of a corresponding pucch- PathlossReferenceRS-Id maps to a CSI-RS resource index. The WTRU may identify a RS resource in the set of RS resources that corresponds either to a SS/PBCH block index or to a CSI-RS resource index as provided by pucch-PathlossReferenceRS-Id in PUCCH-PathlossReferenceRS. [0153] If the WTRU is provided with the parameters pathlossReferenceRSs and PUCCH- SpatialRelationInfo, the WTRU may obtain a mapping, by indexes provided by corresponding values of pucch- PathlossReferenceRS-Id, between a set of pucch-SpatialRelationInfoId values and a set of referenceSignal values provided by PUCCH-PathlossReferenceRS. If the WTRU is provided with more than one value for pucch-SpatialRelationInfoId and the WTRU receives an activation command (e.g., via a MAC-CE) indicating a value of pucch-SpatialRelationInfoId, the WTRU may determine the referenceSignal value in PUCCH- PathlossReferenceRS through the link to a corresponding pucch-PathlossReferenceRS-Id index. The WTRU may apply the activation command (e.g., provided via the MAC-CE) in the first slot that is after slot ^^ + 3 ⋅ ^^ subframe,^^ slot where ^^ represents the slot where the WTRU would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the activation command and ^^ represents the SCS configuration for the PUCCH. - 28 - 8902562.1
[0154] ΔF_PUCCH(^^) may represent an additional power adjustment parameter. ∆TF,^^,^^,^^(^^) may represent an additional power adjustment parameter, e.g., a PUCCH transmission power adjustment component on active UL BWP ^^ of carrier ^^ of primary cell ^^. [0155] For the PUCCH power control adjustment state ^^^^,^^,^^(^^, ^^), e.g., CL-index (for PUCCH), for active UL BWP ^^ of carrier ^^ of primary cell ^^ and PUCCH transmission occasion ^^ , ^^PUCCH,^^,^^,^^(^^, ^^) may represent a TPC command value included in a DCI format associated with the PUCCH transmission for active UL BWP ^^ of carrier ^^ of the primary cell ^^ that the WTRU detects for PUCCH transmission occasion ^^, or is jointly coded with other TPC commands in a DCI format 2_2 (e.g., a group-common DCI which may be transmitted to multiple WTRUs, e.g., as a broadcast or multicast signaling) with CRC scrambled by TPC- PUCCH-RNTI. ^^ ∈ {0,1} if the WTRU is provided twoPUCCH-PC-AdjustmentStates and PUCCH- SpatialRelationInfo, or more than one set of power control parameters for operation in FR1, ^^ = 0 if the WTRU is not provided twoPUCCH-PC-AdjustmentStates or PUCCH-SpatialRelationInfo and more than one sets of power control parameters, and ^^ = 0 if the PUCCH transmission provides only multicast HARQ-ACK information. [0156] FIG. 7 is a table illustrating a mapping of a TPC Command Field in a DCI format to accumulated ^^PUCCH,^^,^^,^^ values. A WTRU may be configured to receive a DCI format that includes TPC Command Field with one of the values shown in table 700. [0157] ^^^^,^^,^^(^^, ^^) = ^^^^,^^,^^(^^ − ^^0, ^^) + ∑ C ^^ (^^^^ =0 )−1 ^^PUCCH,^^,^^,^^(^^, ^^) may represent the current PUCCH power ^^ (e.g., the current status of a CLPC accumulation process with index
l e.g for PUCCH) for UL BWP ^^ ^^ of primary cell ^^ and PUCCH transmission occasion ^^, where the ^^PUCCH,^^,^^,^^ values may be given by the table shown in FIG.7. [0158] ∑ C ^^ (^^^^ =0 )−1 ^^PUCCH,^^,^^,^^(^^, ^^) may represent a sum of TPC command values in a set ^^^^ of TPC command values with cardinality C(^^^^) that the WTRU receives between ^^PUCCH(^^ − ^^0) − 1 symbols before PUCCH transmission occasion ^^ − ^^0 and ^^PUCCH(^^) symbols before PUCCH transmission occasion ^^ on active UL BWP ^^ of carrier ^^ of primary cell ^^ for PUCCH power control adjustment state. ^^0 > 0 may be the smallest integer for which ^^PUCCH(^^ − ^^0) symbols before PUCCH transmission occasion ^^ − ^^0 is earlier than ^^PUCCH(^^) symbols before PUCCH transmission occasion ^^. [0159] Examples of methods for SRS power control are described herein. [0160] Eq. 3 is an equation for calculation of SRS transmission power (in dBm) in an SRS transmission occasion ^^. If a WTRU transmits an SRS based on a configuration by SRS-ResourceSet on active UL BWP ^^ of carrier ^^ of serving cell ^^ using SRS power control adjustment state with index ^^, the WTRU may determine the SRS transmission power ^^SRS,^^,^^,^^(^^, ^^^^, ^^) in SRS transmission occasion ^^ as shown in Eq.3. - 29 - 8902562.1
^^SRS,^^,^^,^^(^^, ^^^^ , ^^) = ^^CMAX,^^,^^(^^) } a
defined in technical specifications (such as 3GPP TS 38.101-1, TS 38.101-2 and/or TS 38.101-3) for carrier ^^ of serving cell ^^ in SRS transmission occasion ^^. ^^O_SRS,^^,^^,^^(^^^^) may represent a nominal power level, e.g., provided by p0 for active UL BWP ^^ of carrier ^^ of serving cell ^^ and SRS resource set ^^^^ provided by SRS- ResourceSet and SRS-ResourceSetId. ^^SRS,^^,^^,^^(^^) may represent a SRS bandwidth expressed by a number of resource blocks for SRS transmission occasion ^^ on active UL BWP ^^ of carrier ^^ of serving cell ^^ and ^^ may represent a SCS configuration. ^^SRS,^^,^^,^^(^^^^) (e.g, ‘alpha’) may represent a nominal PL-compensation- ratio parameter, which may be multiplied by the PL term (^^^^^^,^^,^^(^^^^)), e.g., provided by alpha for active UL BWP ^^ of carrier ^^ of serving cell ^^ and SRS resource set ^^^^. [0162] ^^^^^^,^^,^^(^^^^) may represent a downlink pathloss estimate in dB calculated by the WTRU using a RS resource index ^^^^ for the active DL BWP of serving cell ^^ and SRS resource set ^^^^. The RS resource index ^^^^ may be provided by pathlossReferenceRS associated with the SRS resource set ^^^^ and may be, for example, an ssb-Index providing a SS/PBCH block index or a csi-RS-Index providing a CSI-RS resource index. If the WTRU is provided with the parameter enablePL-RS-UpdateForPUSCH-SRS, a MAC CE may provide by SRS-PathlossReferenceRS-Id a corresponding RS resource index ^^^^ for aperiodic or semi-persistent SRS resource set ^^^^. If the WTRU is not provided pathlossReferenceRS or SRS-PathlossReferenceRS-Id and if the WTRU is not provided with the parameter enableDefaultBeamPL-ForSRS, or before the WTRU is provided dedicated higher layer parameters, the WTRU may calculate ^^^^^^,^^,^^(^^^^) using a RS resource obtained from an SS/PBCH block with same SS/PBCH block index as the one the WTRU uses to obtain MIB, or using the SS/PBCH block that the WTRU acquired by time and frequency synchronization for a secondary cell. The WTRU may determine a RS resource index ^^^^ providing a periodic RS resource configured with qcl-Type set to 'typeD' in the TCI state (e.g., via ‘TCI-State’ IE or via ‘TCI-UL-State’ IE) or the QCL assumption of a CORESET with the lowest index in the active DL BWP, if CORESETs are provided in the active DL BWP of serving cell ^^. [0163] For the SRS power control adjustment state (e.g., CL-index for example for SRS) for active UL BWP ^^ of carrier ^^ of serving cell ^^ and SRS transmission occasion ^^. ℎ^^,^^,^^(^^, ^^) = ^^^^,^^,^^(^^, ^^), where ^^^^,^^,^^(^^, ^^) may represent the current PUSCH power control adjustment state as described in this document, if srs- PowerControlAdjustmentStates indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions; or ℎ (^^) = ℎ (^^ ) ∑ C(^^^^)−1 ^^,^^,^^ ^^,^^,^^ − ^^0 + ^^=0 ^^SRS,^^,^^,^^(^^) (e.g., as a current status of
- - 8902562.1
a CLPC accumulation process e.g. for SRS, separately from PUSCH) if the WTRU is not configured for PUSCH transmissions on active UL BWP ^^ of carrier ^^ of serving cell ^^. If srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmissions and PUSCH transmissions, and if tpc- Accumulation is not provided, the ^^SRS,^^,^^,^^ values may be as those given in the table of FIG.7. In some examples, ^^SRS,^^,^^,^^(^^) may be jointly coded with other TPC commands in a PDCCH with DCI format 2_3 (e.g., a group-common DCI format to be received at multiple WTRUs, e.g., as broadcast or multicast signaling). ∑ C ^^ ( =^^ ^^ 0 )−1 ^^SRS,^^,^^,^^(^^) may represent a sum of TPC command values in a set ^^^^ of TPC command values with cardinality C(^^^^) that the WTRU receives between ^^SRS(^^ − ^^0) − 1 symbols before SRS transmission occasion ^^ − ^^0 and ^^SRS(^^) symbols before SRS transmission occasion ^^ on active UL BWP ^^ of carrier ^^ of serving cell ^^ for SRS power control adjustment state, where ^^0 > 0 is the smallest integer for which ^^SRS(^^) symbols before SRS transmission occasion ^^ − ^^0 is earlier than ^^SRS(^^ − ^^0) symbols before SRS transmission occasion ^^. [0164] In some scenarios, ℎ^^,^^,^^(^^) = ^^SRS,^^,^^,^^(^^) if the WTRU is not configured for PUSCH transmissions on an active UL BWP ^^ of carrier ^^ of serving cell ^^ . If srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmissions and PUSCH transmissions, and tpc-Accumulation is provided, and the WTRU detects a DCI format 2_3 ^^SRS,min symbols before a first symbol of SRS transmission occasion ^^, the absolute values of ^^SRS,^^,^^,^^ may be as those provided in the table of FIG.7. [0165] If srs-PowerControlAdjustmentStates indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions, the update of the power control adjustment state for SRS transmission occasion ^^ may occur at the beginning of each SRS resource in the SRS resource set ^^^^ ; otherwise, the update of the power control adjustment state SRS transmission occasion ^^ may occur at the beginning of the first transmitted SRS resource in the SRS resource set ^^^^. [0166] Solutions involving additional UL PC parameter set associations with specifically-ordered TCI-states based on a flag dynamically indicating the ordinal positions are described herein. [0167] In one or more solutions, a WTRU may do one or more of the following actions. For example, a WTRU may receive configuration information for a DL-TCI-state pool (first TCI-state pool) and a UL-TCI-state pool (second TCI-state pool), where each UL-TCI-state of the UL-TCI-state pool may be associated (e.g., as an initial setting) with one or more UL power control (PC) parameters such as P0, alpha, pathloss(PL)-RS (e.g., a DL-RS), and/or a closed-loop(CL)-index (e.g., l = 0 or 1). [0168] The WTRU may receive a first indication (e.g., via a MAC-CE, TCI-activation command), indicating a set of specifically-ordered TCI-states where the indication may include one or more flag parameters (e.g., ‘Fi,j’ and/or ‘Si,j’) that the WTRU may use to determine an association between codepoints (e.g., of a DCI) and one or more TCI states (e.g., DL and/or UL TCI states). - 31 - 8902562.1
[0169] For example, a flag ‘Fi,j’ may indicate whether j-th DL TCI state is present or not. If present (e.g., flag set to ‘1’), the j-th DL TCI state ID is indicated and is associated with the codepoint i of a DCI ‘TCI field’. [0170] For example, a flag ‘Si,j’ may indicate whether j-th UL TCI state is present or not. If present (e.g., flag set to ‘1’), the j-th UL TCI state ID is indicated and is associated with the codepoint i of a DCI ‘TCI field’. [0171] The WTRU may receive a second indication associating a set of (additional) UL PC parameters, e.g., one or more power offset (e.g., Poff) parameters and/or one or more CL-index parameters, with the set of specifically-ordered TCI-states from the UL-TCI-state pool. [0172] For instance, the WTRU may determine that Poff1 (e.g., a value in dB) and/or CL-index1 (e.g., l = 3) is/are associated with a first set of TCI-states that are all having the flag ‘Si,j’ set to ‘1’ with j being a particular index value (e.g., j = 1). [0173] For instance, the WTRU may determine that Poff2 (e.g., a value in dB) and/or CL-index2 (e.g., l = 2) is/are associated with a second set of TCI-states that are all having the flag ‘Si,j’ set to ‘1’ with j being a particular index value (e.g., j = 2). [0174] In some examples, the WTRU may use the indicated one or more CL-index parameters to update or override the current or configured CL-index for one or more UL TCI states. [0175] For each UL-TCI-state of the set of specifically-ordered TCI-states for which the second indication indicated an association with a CL-index parameter, the WTRU may override (e.g., replace, or update) the current, initial, or configured CL-index for that UL TCI state with the corresponding CL-index provided by the second indication. [0176] In some cases, if a CL-index provided by the second indication for ‘Si,j’ (where j=1) is l = 3, the WTRU may update (e.g., override) the CL-index (e.g., l = 2, which may be provided by an RRC configuration, or other logically equivalent messaging or signaling, or a previous update/override indication) of a first UL-TCI-state (having flag ‘Si,j’ where j=1) to be the indicated CL-index l = 3. [0177] The WTRU may update (e.g., override) the CL-index (e.g., l = 1, which may be provided by an RRC configuration, or other logically equivalent messaging or signaling or a previous update/override indication) of a second UL-TCI-state (having flag ‘Si,j’ where j=1) with the indicated CL-index l = 3. When the WTRU updates (e.g., overrides) a CL-index with the indicated CL-index (e.g., l = 3) provided by the second indication, the WTRU may reset (e.g., start over) a closed-loop TPC accumulation process associated with the CL-index (e.g., l = 3). [0178] The WTRU may receive a scheduling grant for transmitting a UL signal or transmitting on a UL channel (e.g., PUSCH, PUCCH, and/or SRS, or other types of signals or channels). [0179] If the UL signal or channel is associated with a TCI-state of the specifically-ordered TCI-states that are associated with the set of (additional) UL PC parameters, the WTRU may determine a UL power level for the transmission of the UL signal or the transmission on the UL channel by applying at least one of following: - 32 - 8902562.1
[0180] The UL power level may be determined as P = min{Pmax, f(OLPC, CLPC)}, where f(.) is a power control formula for the UL signal or channel, open-loop-PC (OLPC) is determined at least based on a nominal power (P0), adjusting ratio parameter (alpha), PL calculation by using a (e.g., configured) PL-RS (e.g., the DL RS configured for the TCI-state), and/or the indicated power offset (e.g., Poff1, or Poff2, etc.), where a PL term of f(.) may be calculated by the PL-RS and by applying (e.g., adding in dB scale) the power offset (e.g., Poff1, positive or negative value), and closed-loop-PC(CLPC) is determined based on one or more transmit-PC (TPC) commands being received (e.g., from a base station) within a period of time, where the OLPC accumulation process to be applied may be determined based on the indicated CL-index (e.g., l = 3, updated, overridden, replaced) of or associated with the set of UL PC parameters (e.g., additional UL PC parameters). [0181] The WTRU may transmit the UL signal or it may transmit on an UL channel by using the TCI-state and the determined UL power level. [0182] Examples relating to the configuration of TCI-states are described herein. A WTRU may receive configuration information for (e.g., indicating) a first plurality of TCI-states (e.g., a first TCI-state pool, a joint- DL-TCI-states pool, etc.) and a second plurality of TCI-states (e.g., a second TCI-state pool, a UL-TCI-state pool, etc.). In some examples, the first plurality of TCI-states may be used (e.g., be configured, be configured when a parameter for example ‘unifiedTCI-StateType’ set to ‘joint’) for receiving on a (e.g., DL) channel or receiving a (e.g., DL) signal and/or transmitting on a (e.g., UL) channel or transmitting a (e.g., UL) signal. In some examples, the first plurality of TCI-states may be used (e.g., be configured, be configured when a parameter for example ‘unifiedTCI-StateType’ set to ‘separate’) for receiving a (e.g., DL) channel or signal, where the WTRU may be configured with a paired UL-TCI state (of the second plurality of TCI-states) that is paired with a DL-TCI state (of the first plurality of TCI-states). The second plurality of TCI-states may be used (e.g., be configured, be configured when a parameter such as ‘unifiedTCI-StateType’ is set to or indicates ‘separate’) for transmitting a (e.g., UL) signal or channel (e.g., as a separate UL-TCI-state indication). In such cases, for receiving on a (e.g., DL) channel or receiving a (e.g., DL) signal, a TCI-state (e.g., the DL-TCI state) of the first plurality of TCI-states may be used or indicated (e.g., as a separate DL-TCI-state indication). [0183] The WTRU may receive configuration information for or indicating at least one UL power control (PC) parameter associated with a TCI-state(s) of the first plurality of TCI-states or of the second plurality of TCI-states. The at least one UL PC parameter may include a nominal power-level e.g. ‘p0’, a PL-compensation- ratio parameter e.g. ‘alpha’, pathloss(PL)-compensation amount calculated based on a PL-RS e.g. set by ‘pathlossReferenceRS-Id’, and/or a closed-loop-PC(CLPC) index e.g. set by ‘closedLoopIndex’. The WTRU may be configured with a set of UL PC parameters, for example, such that at least one UL PC parameter is configured per TCI-state or per group of TCI-states (of the first plurality of TCI-states or of the second plurality of TCI-states). [0184] UL PC parameter(s), e.g., for asymmetric DL/UL TRPs, are described herein. - 33 - 8902562.1
[0185] In some solutions, the WTRU may receive an indication that a set of (additional) UL PC parameters (e.g., a power offset parameter(s) (e.g., Poff1, Poff2, etc.) and/or a CL-index(s)) is associated with a set of TCI- states, e.g., a set of specifically-ordered TCI-states, corresponding to a column, by its ordinal position, pointing to a particular TRP, pointing to a group of rows within the column, and/or based on ‘Fi,j’ and/or ‘Si,j’ illustrated in FIGs.3, 4, and/or 5, from the first plurality of TCI-states and/or the second plurality of TCI-states. The WTRU may determine the set of (specifically-ordered) TCI-states based on a second indication (e.g., provided by RRC, and/or via a MAC-CE for example TCI-activation command, illustrated as example of FIG.8, introduced and described in further detail below, or via other logically equivalent signaling or messages). The second indication by which the WTRU may determine the set of TCI-states may include the indication that the set of UL PC parameters is associated with a set of TCI-states, or vice versa (e.g., the indication may include the second indication). [0186] FIG.8 is a diagram illustrating an example of a mapping between codepoints that may be indicated by a field carried in DCI (e.g., a TCI field) and unified TCI-state indications, e.g., when a separate-UL/DL UTCI mode is configured. The mapping shown in FIG.8 may be applicable for scenarios involving three TRPs: TRP1, TRP2, and TRP3, illustrated in the inset figure 850. As shown in FIG.8, the table 800 shows a mapping between codepoints 0-7 as may be indicated by a 3-bit TCI field of a DCI and ordered sets of TCI-states associated with each of TRP1, TRP2, and TRP3. As is further illustrated in table 800, a set of specifically-ordered DL TCI states and a set of specifically-ordered UL TCI states are provided for TRP1. By contrast, only a set of specifically ordered UL TCI states is provided for TRP2 and TRP3. [0187] In some examples, the WTRU may determine (e.g., as in the example shown in FIG. 8, by the indication) that a first set of UL PC parameters (Poff1 and/or CL-index1) is associated with a first set of specifically-ordered TCI-states (e.g., with Order#2,2) which are UL-TCI#32, 27, 24, 16, 30 of the second plurality of TCI-states. The WTRU may determine that a second set of UL PC parameters (Poff2 and/or CL- index2) is associated with a second set of specifically-ordered TCI-states (e.g., with Order#3,2) which are UL- TCI#7, 11, 19, 22, 15 of the (same) second plurality of TCI-states. The WTRU may identify (e.g., determine, or be configured with) that Order#A,B is identified (e.g., is determined, corresponds, or is mapped) based on one or more flag parameters and/or fields (e.g., ‘Fi,j’ and/or ‘Si,j’, via a MAC-CE, such as a TCI-activation command, illustrated in FIGs.3, 4, and/or 5), e.g., via the indication. [0188] In some examples, the WTRU may determine that the parameter ‘A’ (of Order#A,B) corresponds to (e.g., is mapped to, is associated with, is equivalent to, or is identified based on) the parameter ‘j’ (of ‘Fi,j’ and/or ‘Si,j’), where j (or A) = 1, 2, or 3 (based on FIG.8), e.g., the parameter ‘j’ (or ‘A’) may correspond to a column (e.g., a UTCI instance, pointing to a particular TRP (e.g., one of the three TRPs: TRP1, TRP2, or TRP3), and/or pointing to a set of specifically-ordered TCI-states (positioned in one column). The WTRU may determine that the parameter ‘B’ (of Order#A,B) corresponds to (e.g., is mapped to, is associated with, is equivalent to, is identified based on, is determined based on, selectively) either the field ‘Fi,j’ or ‘Si,j’, where B=1 may correspond to the field ‘Fi,j’ indicating whether the j-th DL TCI state is present or not, and B=2 may correspond to the field - 34 - 8902562.1
‘Si,j’ indicating whether the j-th UL TCI state is present or not. The parameter ‘i’ may represent (e.g., indicate) the Codepoint i (e.g., i=0,1,…,7) indicated by or associated with the DCI ‘TCI field’, as illustrated in FIG.8. [0189] In some solutions, the WTRU may receive an indication of at least one signaling component (e.g., power offset(s) and/or CL-index(es)) via a DCI (e.g., a WTRU-specific DCI, DCI format 0_x, 1_y, where x = 0, 1, or 2,… y = 0, 1, or 2,… , or a group-common DCI, DCI format 2_z, where z may be 0, 1, 2, or 3,… etc.). The DCI delivering the information indicating the at least one signaling component may be associated with a new or additional RNTI that is different (e.g., separated) from an existing RNTI to decode the DCI. In some examples, the at least one signaling component (e.g., power offset(s) and/or CL-index(es)) may be indicated via an explicit DCI field or value of the DCI, e.g., 2-bit indicator indicating which CL-index (e.g., l = 1, 2, 3, or 4, etc.) to apply for a TPC accumulation (for CLPC) for a PUSCH, PUCCH, and/or SRS transmission(s). In some examples, the at least one signaling component (e.g., power offset(s) and/or CL-index(es)) of the indication may be indicated implicitly based on a parameter (e.g., the value of RNTI). For example, a new RNTI (e.g., CL- RNTI) may implicitly inform the WTRU of a particular value of CL-index (e.g., l = 3) to apply for a TPC accumulation (for CLPC) for PUSCH, PUCCH, and/or SRS transmission(s). [0190] WTRU behaviors after receiving the indication, e.g., overriding and/or resetting a CLPC process, are described herein. A WTRU may determine (e.g., may be configured to determine), per UL-TCI-state of the set of (specifically-ordered) TCI-states, to override (e.g., replace) a pre-configured CL-index (e.g., which may have been configured by RRC or both other logically equivalent signaling, along with the configuration of the second plurality of TCI-states) with the CL-index provided by the indication. [0191] For example, if the CL-index (for Order#2,2) provided by the indication is l = 3, the WTRU may determine to override (e.g., replace) CL-indices as follows: for UL-TCI#32, a pre-configured CL-index (e.g., l = 1, which may have been configured by RRC or both other logically equivalent signaling) with l = 3 provided by the indication; for UL-TCI#27, a pre-configured CL-index (e.g., l = 2, which may have been configured by RRC or both other logically equivalent signaling) with l = 3 provided by the indication; for UL-TCI#24, a pre-configured CL-index (e.g., l = 2, which may have been configured by RRC or both other logically equivalent signaling ) with l = 3 provided by the indication; for UL-TCI#16, a pre-configured CL-index (e.g., l = 1, which may have been configured by RRC or both other logically equivalent signaling) with l = 3 provided by the indication; and/or for UL-TCI#30, a pre-configured CL-index (e.g., l = 2, which may have been configured by RRC or both other logically equivalent signaling) with l = 3 provided by the indication. [0192] For example, if the CL-index (for Order#3,2) provided by the indication is l = 2, the WTRU may determine to override (e.g., replace) CL-indices as follows: for UL-TCI#7, a pre-configured CL-index (e.g., l = 2, which may have been configured by RRC or both other logically equivalent signaling) with l = 2 provided by the indication; for UL-TCI#11, a pre-configured CL-index (e.g., l = 1, which may have been configured by RRC or both other logically equivalent signaling) with l = 2 provided by the indication; for UL-TCI#19, a pre-configured CL-index (e.g., l = 2, which may have been configured by RRC or both other logically equivalent signaling) with l = 2 provided by the indication; for UL-TCI#22, a pre-configured CL-index (e.g., l = 1, which may have been - 35 - 8902562.1
configured by RRC or both other logically equivalent signaling) with l = 2 provided by the indication; and/or for UL-TCI#15, a pre-configured CL-index (e.g., l = 1, which may have been configured by RRC or both other logically equivalent signaling) with l = 2 provided by the indication. [0193] For a TCI-state (or a group of TCI-states) associated with a set of (additional) UL PC parameters (e.g., a power offset parameter(s) (e.g., Poff1, Poff2, etc.) and/or a CL-index(s)) based on the indication, e.g., as illustrated in the example of Order#2,2, the WTRU may override (e.g., replace) a pre-configured CL-index (e.g., l = 1, or l = 2, etc., which may have been configured by RRC or both other logically equivalent signaling, for example by ‘TCI-UL-State’ IE) with an indicated CL-index (a value of l) provided by the indication (e.g., l = 3 which may be a new or additional value of l that may not be within a supported value range when configured by RRC or other logically equivalent signaling, for example by ‘TCI-UL-State’ IE). This may provide benefits in that the new or additional closed-loop power accumulation process associated with the new index of l = 3 may be separately used for a proper power control targeting a UL-only TRP (e.g., TRP2 or TRP3 in FIG.8). In an example, since the activated UL-TCI#X shown in FIG.8 that are UL-TCI#6, 1, 14, 20 (for Order#1,1), #32, 27, 24, 16, 30 (for Order#2,2), #7, 11, 19, 22, 15 (for Order#3,2) may be indicated from one common UL-TCI-state pool (e.g., the second plurality of TCI-states), the WTRU may not know which one or more UL-TCI-states are to be used with particular TRPs for UL transmissions before receiving the indication. Based on the indication, the WTRU may identify (e.g., determine) that a TCI-state (or a group of TCI-states) associated with the set of (additional) UL PC parameters may be used with a particular a TRP for (a particular type of) UL communications (e.g., UL-only-TRP which does not transmit a DL signal or channel). [0194] For a TCI-state (or a group of TCI-states) associated with a set of (additional) UL PC parameters (e.g., a power offset parameter(s) (e.g., Poff1, Poff2, etc.) and/or a CL-index(s)) based on the indication, e.g., as illustrated in the example of Order#3,2, the WTRU may override (e.g., replace) a pre-configured CL-index (e.g., l = 1, or l = 2, etc. by RRC or other logically equivalent signaling, for example by ‘TCI-UL-State’ IE) with an indicated CL-index (a value of l) provided by the indication (e.g., l = 2 which may be within the supported value range value when configured by RRC or other logically equivalent signaling, for example by ‘TCI-UL- State’ IE). This may provide benefits in terms of WTRU complexity reduction in that one of current closed-loop power accumulation processes associated with the index of l = 2 is replaced (e.g., reused) by a proper power control targeting a UL-only TRP (e.g., TRP2 or TRP3 in FIG.8). The WTRU may determine to (e.g., may be configured to) reset the currently maintained closed-loop power accumulation process, e.g., resetting whatever the current status of a CLPC accumulation process with index l, e.g, for PUSCH ^^^^,^^,^^(^^, ^^) , for PUCCH ^^^^,^^,^^(^^, ^^) , and/or for SRS ℎ^^,^^,^^(^^, ^^), and starting over to apply the corresponding accumulation formula within a time window based on the time occasion i. In an example, the WTRU may be configured with more than one CLPC accumulation processes for SRS, e.g., having ℎ^^,^^,^^(^^, ^^), with l = 1, 2, …, etc., on condition that (e.g., only on condition that) the WTRU receives the indication or a configuration of the set of (additional) UL PC parameters (e.g., a power offset parameter(s) (e.g., Poff1, Poff2, etc.) and/or a CL-index(s)). - 36 - 8902562.1
[0195] Enhanced UL-PC mechanisms, e.g., for asymmetric DL/UL TRPs, are described herein. A WTRU may receive a scheduling grant for transmitting a UL signal or for transmitting on an UL channel (e.g., PUSCH, PUCCH, and/or SRS). If the UL signal or channel is associated with a TCI-state of the specifically-ordered TCI- states being associated with the set of (additional) UL PC parameters, the WTRU may determine a UL power level for the transmission of the UL signal or for the transmission of the UL channel by applying at least one of following. The UL power level may be determined as P = min{Pmax, f(OLPC, CLPC)}, where f(.) is a power control formula for the UL signal or channel (e.g., which may be a different formula for PUSCH, PUCCH, SRS, as described in various examples herein). [0196] In some solutions, open-loop-PC(OLPC) may be determined at least based on a nominal power (P0), adjusting ratio parameter (alpha), PL calculation by using a (pre-configured) PL-RS (e.g., the DL RS pre- configured for the TCI-state), and/or the indicated power offset (e.g., Poff1, or Poff2, etc.), where a PL term of f(.) may be calculated by the PL-RS and by applying (e.g., adding in dB scale) the power offset (e.g., positive or negative value). [0197] In some solutions, closed-loop-PC(CLPC) may be determined based on one or more transmit-PC (TPC) commands being received (e.g., from a base station) within a period of time, where which CLPC accumulation process (out of multiple processes, e.g., l = 0, 1, …) to apply may be determined by the indicated CL-index (e.g., l = 3) of the set of (additional) UL PC parameters. The WTRU may transmit the UL signal or may transmit on an UL channel by using the TCI-state and the determined UL power level. [0198] In some solutions, the PL term of f(.) may be based on (only) the power offset (e.g., positive or negative value) without calculation by the PL-RS (e.g., which may be interpreted as “turn-off of PL calculation”), where the WTRU may receive a configuration or indication to perform this operation. For example, once the WTRU receives the configuration or indication for the turn-off of PL calculation (e.g., for the specifically-ordered TCI-states), the WTRU may determine the OLPC terms based on at least combining (e.g., adding) P0 and the power offset, e.g., without PL estimate based on the PL-RS. This operation may be associated with a value of CL-index. For example, the WTRU may receive a configuration or indication that (or may determine that) the WTRU applies or performs this behavior (e.g., turn-off or disabling of PL calculation) if a scheduled UL transmission is associated with CL-index l = 3 (e.g., associated with a UL-TCI-state (e.g., of the specifically- ordered TCI-states) that is associated with CL-index l = 3). The WTRU may not apply or perform this behavior (e.g., the turn-off of PL calculation) if a scheduled UL transmission is associated with a second CL-index (e.g., l = 1 or 2, etc.) other than CL-index l = 3 (e.g., associated with a UL-TCI-state (e.g., of the specifically-ordered TCI-states) that is associated with CL-index l = 1 or 2), which means the WTRU applies the PL estimate based on the PL-RS. The WTRU may transmit the UL signal or UL channel transmission by using the TCI-state and the determined UL power level. [0199] In some examples, the UL signal or UL channel transmission may be a PUSCH transmission, where the WTRU may determine that the PUSCH is scheduled (e.g., via a dynamic grant e.g by a DCI, or via a semi- static scheduling e.g configured-grant) for the WTRU to transmit by using a TCI-state (e.g., UL-TCI-state#32 - 37 - 8902562.1
by Codepoint 0) of the specifically-ordered TCI-states being associated with the set of (additional) UL PC parameters (e.g., Poff1, and/or CL-index1) as illustrated in FIG.8. The WTRU may determine that Poff1 and CL-index1 as l = 3 is associated with a flag parameter(s) (e.g., ‘Fi,j’ and/or ‘Si,j’, via a MAC-CE, TCI-activation command, illustrated in FIGs.3, 4, and/or 5) where the flag parameter(s) may (e.g. equivalently) indicate Order#2,2, as illustrated in FIG.8. The WTRU may determine a PL-RS (e.g., ^^^^) to derive the DL pathloss estimate (e.g., in dB), e.g., ^^^^^^,^^,^^(^^^^), where the PL-RS (e.g., an SSB index or a CSI-RS resource ID) may be determined by the TCI-state (e.g., a PL-RS may be preconfigured as a sub-parameter of the TCI-state). The WTRU may combine the derived ^^^^^^,^^,^^(^^^^) and the provided Poff1, e.g., where for example the combining may include an addition (in dB), e.g., ^^^^^^,^^,^^(^^^^) + Poff1 (e.g., in dB). The WTRU may apply the CLPC term (e.g., ^^^^,^^,^^(^^, ^^)) where the index l here is based on the provided CL-index1 (e.g., as l = 3) instead of a different l l = 1 pre-configured by RRC or other logically equivalent signaling or messaging in association
state). This may imply the WTRU may maintain different CLPC accumulation process, e.g., one with l = 1 (e.g. being accumulated by received TPC commands associated with l = 1), and another with l = 3 (e.g. being accumulated by received TPC commands associated with l = 3, e.g., being separately received). [0200] In some solutions, the WTRU may receive a power offset (e.g., Poff1, or Poff2, etc.) separately, e.g., not associated with the specifically-ordered TCI-states, where (only) CL-index (e.g., l = 3) may be associated with the specifically-ordered TCI-states, e.g., a set of specifically-ordered TCI-states, corresponding to a column, by its ordinal position, pointing to a particular TRP, pointing to a group of rows within the column, and/or based on ‘Fi,j’ and/or ‘Si,j’ illustrated in FIGs.3, 4, and/or 5, from the first plurality of TCI-states and/or the second plurality of TCI-states. In an example, a common power offset (e.g., Poff_common, which may be one of Poff1, Poff2, etc.) may be applied for both the first set of specifically-ordered TCI-states (e.g., with Order#2,2) and the second set of specifically-ordered TCI-states (e.g., with Order#3,2), but CL-PC calculations (e.g., based on CL-index l) may be different, e.g., by using l = 3 (associated with Order#2,2) and l = 2 (associated with Order#3,2), respectively. [0201] Methods for deactivating a paired DL-TCI-state are described herein. In some solutions, the WTRU may determine to deactivate a paired DL-TCI-state, if the WTRU receives the set of (additional) UL PC parameters for the paired counterpart (UL-TCI-state). In some examples, the WTRU may determine (or may be configured to determine) that TCI-state(s) corresponding to Order #A,1(e.g., DL TCI-states) are deactivated (e.g., released, no longer QCL-tracked), if the WTRU determines or receives an indication that the set of (additional) UL PC parameters is associated with Order #A,2(e.g., UL TCI-states). This deactivation may imply to the WTRU to release all of (or some of) DL signals or channels (for reception) that were associated with the paired DL-TCI-state, e.g., (only) if the WTRU determines the set of (additional) UL PC parameters is associated with a UL-TCI-state that is paired with a DL-TCI-state to be used for receiving the DL signals or transmissions on the DL channels. This may mean that deactivating the paired DL-TCI-state does not occur when the condition is not fulfilled, and for such case, the WTRU may maintain the DL-TCI-state (being QCL-tracked) instead of deactivating or releasing it. This may mean only the UL-TCI-state is updated in accordance with a - 38 - 8902562.1
DCI ‘TCI field’ indicating a Codepoint associated mapped with the pair of the DL-TCI-state and the UL-TCI- state (e.g., in a separate-DL/UL-UTCI mode). This may provide benefits in reducing WTRU complexity in terms of QCL-tracking complexity, in that once the set of UL PC related parameters is associated with Order #A,2(e.g., UL TCI-states), e.g., for TRP2, this may imply that the TRP2 starts to operate as “UL-only TRP”. Then, a paired DL-TCI state for TRP2 is no longer being used, but kept tracked if no deactivation behavior described herein is carried out. [0202] Methods for updating a power offset (Poff) value itself are described herein. In some solutions, the WTRU may receive an exact value of power offset (e.g., Poff1, Poff2,…, or Poff_common, etc.) by RRC or by other logically equivalent signaling. In a solution, the WTRU may receive an exact value of a power offset (e.g., Poff1, Poff2,…, or Poff_common, etc.) that may be updated by the indication (e.g., via a MAC-CE, TCI- activation command, or other logically equivalent signaling). [0203] In some solutions, for a (e.g., every) TCI-activation command by MAC-CE, the WTRU may receive an updated value of the power offset (e.g., -15dB, -5dB, +9dB, etc.). This may provide benefits in that a base station may determine the updated value of Poff, e.g., depending on WTRU position (location) based on the location of a macro-TRP (e.g., TRP1) and a micro-TRP (e.g., TRP2), which may provide improved efficiency of a CLPC process by sending multiple TPC commands, e.g., which may provide overhead saving of the number of necessary transmissions of TPC commands. The WTRU may determine an exact timing (e.g., based on a time offset) to apply the updated value of the power offset, e.g., after receiving the MAC-CE. [0204] Solutions relating to hybrid unified TCI (UTCI) modes for dynamic TRP selection for DL/UL communications are described herein. [0205] In some solutions a WTRU may carry out one or more of the following steps. A WTRU may receive configuration information for a joint-DL-TCI-state pool (first TCI-state pool), where each TCI-state of the joint- DL-TCI-state pool may be associated (as pre-setting) with one or more UL power control(PC) parameters such as P0, alpha, pathloss(PL)-RS (e.g., a DL-RS), and/or a closed-loop(CL)-index (e.g., l = 0 or 1). A WTRU may receive configuration information for a UL-TCI-state pool (second TCI-state pool), where each UL-TCI-state of the UL-TCI-state pool may be associated (as pre-setting) with one or more UL power control(PC) parameters such as P0, alpha, pathloss(PL)-RS (e.g., a DL-RS), and/or a closed-loop(CL)-index (e.g., l = 0 or 1). [0206] The WTRU may receive an indication that a first one or more TCI-states, of the joint-DL-TCI-state pool, are associated with a joint UTCI mode, by a flag (e.g., set to ‘joint’) indicated per TCI-state of the first one or more TCI-states. The WTRU may receive an indication that a second one or more TCI-states, of the (same) joint-DL-TCI-state pool, are associated with a separate-DL/UL UTCI mode, by a flag (e.g., set to ‘separate’) indicated per TCI-state of the second one or more TCI-states. One benefit may be an overhead reduction in DL/UL communications with TRP1 (e.g., a macro-TRP) in that the WTRU may communicate with TRP1 for both DL reception and UL transmission with a same joint TCI-state (e.g., based on beam correspondence), while for example, the WTRU may communicate with TRP3 only in terms of UL transmission. - 39 - 8902562.1
[0207] Additional UL PC parameter configurations for UL-only-TRPs are described herein. The WTRU may receive an indication that a set of (additional) UL PC parameters (e.g., power offset (Poff1, or Poff2, etc.) and/or a CL-index) is associated with the second one or more TCI-states (that are based on the separate-DL/UL UTCI mode, e.g., by the flag being set to ‘separate’). This may apply to solutions presented in paragraphs immediately above. The WTRU may not expect that the set of (additional) UL PC parameters is associated with the first one or more TCI-states (being associated with the flag, set to ‘joint’). [0208] PL calculation for UL-only-TRP by using a PL-RS linked to a macro TRP (joint UTCI) is described herein. The WTRU may determine (or be configured to determine) that a pathloss(PL)-RS associated with a TCI-state of the first one or more TCI-states (e.g., which are associated with the joint UTCI mode) is used for PL calculation in conjunction with the power offset (e.g., Poff1, or Poff2, etc.) of the set of (additional) UL PC parameters, e.g., for communication with TRP3 which is UL-only TRP that does not transmit a DL RS. [0209] For example, a PL-RS to be used for all UL-TCI-states for TRP3 may be associated with a lowest codepoint i of the codepoints corresponding to the first one or more TCI-states. The WTRU may determine that the PL-RS for determining a UL Tx power level for a UL transmission scheduled with a UL-TCI-state, is a DL- RS as a QCL source (e.g., beam reference) of a TCI-state with the lowest codepoint among the first one or more TCI-states. [0210] Examples of WTRU behavior for determining UL Tx power are described herein. The WTRU may receive a first scheduling grant for transmitting a first UL signal or channel (e.g., PUSCH, PUCCH, and/or SRS, etc.), where the first scheduling grant may indicate a first TCI-state being associated with a joint UTCI mode (e.g., for transmission toward TRP1 (macro-TRP)). [0211] Based on the first scheduling grant and the first TCI-state, the WTRU may determine a first UL power level based on PC parameter(s) associated with the first TCI-state (without applying the set of (additional) UL PC parameters), and may transmit the first UL signal or channel by using the first TCI-state and the first UL power level. [0212] The WTRU may receive a second scheduling grant for transmitting a second UL signal or channel (e.g., PUSCH, PUCCH, and/or SRS, etc.), where the second scheduling grant may indicate a UL-TCI-state being associated with a separate-DL/UL UTCI mode (e.g., for transmission toward TRP3 (UL-only-TRP). [0213] Based on the second scheduling grant and the second TCI-state, the WTRU may determine a second UL power level by applying the set of (additional) UL PC parameters in conjunction with a PL-RS associated with the first TCI-state (of the joint UTCI mode). For example, the second UL power level may be determined as P = min{Pmax, f(OLPC, CLPC)}, where: f(.) is a power control formula for the second UL signal or channel; open-loop-PC(OLPC) is determined at least based on a nominal power (P0), adjusting ratio parameter (alpha), and/or pathloss(PL) calculation by using the PL-RS (associated with the first TCI-state of the joint UTCI mode) and/or the one or more power offset (Poff1, Poff2, etc.) of the set of (additional) UL PC parameters; and closed-loop-PC(CLPC) is determined based on one or more transmit-PC (TPC) commands - 40 - 8902562.1
being received (e.g., from a base station) within a period of time, where which CLPC accumulation process to apply may be determined by the indicated CL-index of the set of (additional) UL PC parameters. [0214] The WTRU may transmit the second UL signal or channel by using the second TCI-state and the determined second UL power level. [0215] Examples for configuration of TCI-states are described herein. A WTRU may receive configuration information for a first plurality of TCI-states (e.g., a first TCI-state pool, a joint-DL-TCI-states pool, etc.) where each TCI-state of the first plurality of TCI-states may be associated (as pre-setting) with one or more UL power control(PC) parameters such as P0, alpha, pathloss(PL)-RS (e.g., a DL-RS), and/or a closed-loop(CL)-index (e.g., l = 0 or 1), e.g., configured in a ‘TCI-State’ IE by RRC or other logically equivalent signaling. [0216] The WTRU may receive configuration information for a second plurality of TCI-states (e.g., a second TCI-state pool, a UL-TCI-state pool, etc.) where each UL-TCI-state of the second plurality of TCI-states may be associated (as pre-setting) with one or more UL power control(PC) parameters such as P0, alpha, pathloss(PL)-RS (e.g., a DL-RS), and/or a closed-loop(CL)-index (e.g., l = 0 or 1), e.g., configured in a ‘TCI- UL-State’ IE e.g. ‘TCI-UL-State-r17’ IE by RRC. [0217] In some solutions, the WTRU may receive an indication that first one or more TCI-states, of the first plurality of TCI-states, are associated with a joint UTCI mode, e.g., by a flag or parameter (e.g., ‘unifiedTCI- StateType’ set to ‘joint’) indicated per TCI-state (or per group of TCI-states) of the first one or more TCI-states, and second one or more TCI-states, of the (same) first plurality of TCI-states are associated with a separate- DL/UL UTCI mode, e.g., by a flag or parameter (e.g., ‘unifiedTCI-StateType’ set to ‘separate’) indicated per TCI-state (or per group of TCI-states) of the second one or more TCI-states. This may provide benefits in terms of overhead reduction in DL/UL communications with e.g. TRP1 (e.g., macro) in that the WTRU may communicate with TRP1 for both DL reception and UL transmission with a same joint TCI-state (e.g., based on beam correspondence), while for example, the WTRU may communicate with e.g. TRP3 only in terms of UL transmission, which are illustrated in FIG.9, introduced and described in paragraphs below. This may be denoted, indicated, configured as “hybrid UTCI mode”. [0218] FIG.9 is a diagram illustrating an example of a mapping between codepoints that may be indicated by a field carried in DCI (e.g., a TCI field) and unified TCI-state indications, e.g., when a mixed ‘joint’ and ‘separate’ UTCI mode (e.g., “Hybrid UTCI mode”) is configured. The mapping shown in FIG. 9 may be applicable for scenarios involving three TRPs: TRP1, TRP2, and TRP3, illustrated in the inset figure 950. As shown in FIG.9, the table 900 shows a mapping between codepoints 0-7 as may be indicated by a 3-bit TCI field of a DCI and ordered sets of TCI-states associated with each of TRP1, TRP2, and TRP3. As is further illustrated in table 800, a set of specifically-ordered joint TCI states is provided for TRP1. By contrast, separate sets of specifically ordered DL TCI states and UL TCI states are provided for TRP2. Only a set of specifically ordered UL TCI states is provided for TRP3. [0219] Associations of (additional) UL PC parameter(s), e.g., for UL-only-TRP, are described herein. - 41 - 8902562.1
[0220] In some solutions, the WTRU may receive an indication that a set of (additional) UL PC parameters (e.g., power offset (Poff1, or Poff2, etc.) and/or a CL-index) is associated with the second one or more TCI- states (that are based on the separate-DL/UL UTCI mode, e.g., by the flag being set to ‘separate’). In some examples, the WTRU does not expect that the set of (additional) UL PC parameters is associated with the first one or more TCI-states (being associated with the flag, set to ‘joint’). [0221] This may imply that the base station may indicate the set of (additional) UL PC parameters associated with a TCI-state of (e.g., only of) the second one or more TCI-states that are associated with the flag being set to ‘separate’. This may provide benefits in terms of WTRU complexity reduction in that the WTRU may implement at least one enhanced UL-PC mechanism, described herein, only for a particular set of TCI- state(s) that is associated with the flag being set to ‘separate’, while provide benefits a dynamic UL point selection in UL scheduling (e.g., either toward TRP1 (e.g., macro) or toward TRP3 (e.g., pico) illustrated in FIG. 9, based on a dynamic indication of a TCI-state of either the first one or more TCI-states or the second one or more TCI-states, e.g., via a DCI scheduling the UL transmission. [0222] PL calculation for an UL-only-TRP by using a PL-RS linked to a macro TRP (joint UTCI) is described herein. In some solutions, the WTRU may determine (or be configured to determine) that a pathloss(PL)-RS associated with a TCI-state of the first one or more TCI-states that are associated with a joint UTCI mode, e.g., by a flag or parameter (e.g., ‘unifiedTCI-StateType’ set to ‘joint’) indicated per TCI-state (or per group of TCI- states) is used for PL calculation for a UL transmission scheduled based on an indicated UL-TCI-state in conjunction with the power offset (e.g., Poff1, or Poff2, etc.) of the set of (additional) UL PC parameters associated with the indicated UL-TCI-state, e.g., for communication with TRP3 which is UL-only TRP that does not transmit a DL RS. Based on the determination, the WTRU may calculate an UL power level (based on a UL power control formula for PUSCH, PUCCH, and/or SRS) by using the PL-RS associated with the TCI-state (e.g., instead of a second RS associated with or configured in the UL-TCI-state), where the TCI-state may be one of the jointTCI#2, #23, #3, #26, #4, or #5, based on examples of in FIG.9. [0223] In some examples, the WTRU may determine (or be configured with) that a PL-RS to be used for all UL-TCI-states for TRP3 may be associated with a lowest codepoint of the first column, e.g., corresponding to Order#1,1 (which is jointTCI#2 in FIG.9), or with a pre-determined or pre-configured codepoint. For example, the WTRU may determine that the PL-RS (e.g., ^^^^) with the lowest codepoint is a DL-RS as a QCL source (e.g., as a beam reference, spatial-domain reference) of the jointTCI#2. In some examples, the WTRU may determine (or be configured with) that the PL-RS is a second DL-RS as a configured PL-RS (e.g., as a reference for PL estimation) of the joint TCI#2. [0224] In some examples, the WTRU may determine (or be configured with) that a PL-RS to be used for each UL-TCI-state for TRP3 may be associated by an explicit linkage parameter pointing to which codepoint of the first column, e.g., corresponding to Order#1,1 (in FIG.9), where the explicit linkage parameter (e.g., pointing to one of jointTCI#2, #23, #3, #26, #4, or #5) is indicated per activated UL-TCI-state (or per group of UL-TCI-states) by the MAC-CE (TCI-activation command). The PL-RS may be determined as a DL-RS as a - 42 - 8902562.1
QCL source (e.g., as a beam reference, spatial-domain reference) or a second DL-RS as a configured PL-RS (e.g., as a reference for PL estimation) of one of the jointTCI#2, #23, #3, #26, #4, or #5 (in this example, based on FIG.9). [0225] Advanced UL power control mechanisms based on a linked DL-RS as a PL-RS, e.g., for UL-only TRP, are described herein. In some examples, the WTRU may receive a first scheduling grant for transmitting a first UL signal or channel (e.g., PUSCH, PUCCH, and/or SRS, etc.), where the first scheduling grant may indicate a first TCI-state being associated with a joint UTCI mode (e.g., corresponding to Order #1,1 for TRP1). Based on the first scheduling grant and the first TCI-state, the WTRU may determine a first UL power level based on PC parameter(s) associated with the first TCI-state (without applying the set of (additional) UL PC parameters), and may transmit the first UL signal or channel by using the first TCI-state and the first UL power level. [0226] In some solutions, the WTRU may receive a second scheduling grant for transmitting a second UL signal or an UL channel transmission (e.g., PUSCH, PUCCH, and/or SRS, etc.), where the second scheduling grant may indicate a second TCI-state being associated with a separate-DL/UL UTCI mode (e.g., corresponding to Order #3,2 for TRP3). Based on the second scheduling grant and the second TCI-state, the WTRU may determine a second UL power level by applying the set of (additional) UL PC parameters in conjunction with a PL-RS associated with the first TCI-state (of the joint UTCI mode), where the PL-RS may be determined as a DL-RS as a QCL source (e.g., as a beam reference, spatial-domain reference) of the first TCI- state or a second DL-RS as a configured PL-RS (e.g., as a reference for PL estimation) of the first TCI-state. [0227] In some solutions, the second UL power level may be determined as P = min{Pmax, f(OLPC, CLPC)}, where f(.) may be a power control formula for the second UL signal or channel (e.g., PUSCH, PUCCH, or SRS, etc.). An open-loop-PC(OLPC) may be determined at least based on a nominal power (P0), adjusting ratio parameter (alpha), PL calculation by using the PL-RS associated with the first TCI-state and/or the one or more power offset (Poff1, Poff2, etc.) of the set of (additional) UL PC parameters, where a PL term of f(.) may be calculated by the PL-RS and by applying (e.g., adding in dB scale) the power offset (e.g., positive or negative value), and the PL-RS may be determined as a DL-RS as a QCL source or a second DL-RS as a configured PL-RS (e.g., as a reference for PL estimation) of the first TCI-state. A closed-loop-PC(CLPC) may be determined based on one or more transmit-PC (TPC) commands being received (e.g., from a base station) within a period of time, where which CLPC accumulation process (out of multiple processes, e.g., l = 0, 1, …) to apply may be determined by the indicated CL-index2 (e.g., associated with Order#3,2 in FIG.9) of the set of (additional) UL PC parameters. The WTRU may transmit the UL signal or channel by using the TCI-state and the determined UL power level. [0228] Examples of WTRU behavior on UL transmissions based on the determined UL Tx power using a linked DL-RS are described herein. In some examples, the UL signal or channel may be a PUSCH, where the WTRU may determine that the PUSCH is scheduled (e.g., via a dynamic grant e.g by a DCI, or via a semi- static scheduling e.g configured-grant) for the WTRU to transmit by using a TCI-state (e.g., UL-TCI-state#15 - 43 - 8902562.1
by Codepoint 7 in FIG.9) of the specifically-ordered TCI-states being associated with the set of (additional) UL PC parameters (e.g., Poff1, and/or CL-index1) as illustrated in FIG.9. The WTRU may determine Poff2 and/or CL-index2 being associated with a flag parameter(s) (e.g., ‘Fi,j’ and/or ‘Si,j’, via a MAC-CE, TCI-activation command, illustrated in FIGs.3, 4, and/or 5) where the flag parameter(s) may (e.g. equivalently) indicate Order#3,2, as illustrated in FIG.9. [0229] The WTRU may determine a PL-RS (e.g., ^^^^ ) based on a linkage to a first TCI-state being associated with (e.g., on condition that the first TCI-state is associated with) a joint UTCI mode, e.g., by a flag or parameter (e.g., ‘unifiedTCI-StateType’ set to ‘joint’) indicated per TCI-state (or per group of TCI-states), where the linked first TCI-state may be used for deriving the DL pathloss estimate (e.g., in dB), e.g., ^^^^^^,^^,^^(^^^^), e.g., instead of using a pre-configured PL-RS e.g. as a sub-parameter of the TCI-state (e.g., UL- TCI-state#15). The PL-RS may be an SSB index, or a CSI-RS resource ID, etc. The WTRU may combine the derived ^^^^^^,^^,^^(^^^^) by using the linked first TCI-state and the provided Poff1, e.g., where for example the combining may comprise an addition (in dB), e.g., ^^^^^^,^^,^^(^^^^) + Poff1 (e.g., in dB). The WTRU may apply the CLPC term (e.g., ^^^^,^^,^^(^^, ^^)) where the index l here is based on the provided CL-index2 instead of a pre- configured l value by RRC in association with the TCI-state).
[0230] This may benefits in that the WTRU may not need to track additional PL-RS(s) configured in a UL-TCI-state (e.g., pre-configured as a sub-parameter of ‘TCI-UL-State’ IE) and may only track a level of pathloss over time only measuring a linked DL-RS associated with a first TCI-state being associated with a joint UTCI mode, e.g., by a flag or parameter (e.g., ‘unifiedTCI-StateType’ set to ‘joint’) indicated per TCI-state (or per group of TCI-states) because the linked DL-RS is an active (e.g., activated) RS (e.g., as a part of the active first TCI-state for communications with TRP1 (macro-TRP)) so that reusing the linked DL-RS as a PL- RS for communications with TRP3 (pico, e.g UL-only TRP) may provide benefits in terms of overhead saving, WTRU complexity reduction, and so on. [0231] A summary of solutions is provided herein, wherein such solutions relate to additional UL PC parameter set associations with specifically-ordered TCI-states based on a flag dynamically indicating the ordinal positions. [0232] FIG.10 is a flow diagram illustrating an example procedure according to one solution. As shown at 1010, a WTRU may receive configuration information for a DL-TCI-state pool (first TCI-state pool) and a UL- TCI-state pool (second TCI-state pool). Each UL-TCI-state of the UL-TCI-state pool may be associated (e.g., as an initial setting) with one or more UL power control (PC) parameters such as P0, alpha, pathloss(PL)-RS (e.g., a DL-RS), and/or a closed-loop(CL)-index (e.g., l = 0 or 1). [0233] As shown at 1020, the WTRU may receive a first indication (e.g., via a MAC-CE, TCI-activation command, or other logically equivalent signaling), indicating a set of specifically-ordered TCI-states where the indication may include one or more flag parameters (e.g., ‘Fi,j’ and/or ‘Si,j’) that the WTRU may use to determine an association between codepoints (e.g., of a DCI) and one or more TCI states (e.g., DL and/or UL TCI states). - 44 - 8902562.1
For example, a flag ‘Fi,j’ may indicate whether j-th DL TCI state is present or not. If present (e.g., flag set to ‘1’), the j-th DL TCI state ID is indicated and is associated with the codepoint i of a DCI ‘TCI field’. In some examples, a flag ‘Si,j’ may indicate whether j-th UL TCI state is present or not. If present (e.g., flag set to ‘1’), the j-th UL TCI state ID is indicated and is associated with the codepoint i of a DCI ‘TCI field’. [0234] As shown at 1030, the WTRU may receive a second indication associating a set of (additional) UL PC parameters, such as one or more power offset (e.g., Poff) parameters and/or one or more CL-index parameters, with the set of specifically-ordered TCI-states from the UL-TCI-state pool. [0235] The WTRU may determine that Poff1 (e.g., a value in dB) and/or CL-index1 (e.g., l = 3) is/are associated with a first set of TCI-states that are all having the flag ‘Si,j’ set to ‘1’ with j being a particular index value (e.g., j = 1). The WTRU may determine that Poff2 (e.g., a value in dB) and/or CL-index2 (e.g., l = 2) is/are associated with a second set of TCI-states that are all having the flag ‘Si,j’ set to ‘1’ with j being a particular index value (e.g., j = 2). [0236] In some examples, the WTRU may use the indicated one or more CL-index parameters to update or override the current or configured CL-index for one or more UL TCI states. [0237] For each UL-TCI-state of the set of specifically-ordered TCI-states for which the second indication indicated an association with a CL-index parameter, the WTRU overrides (e.g., replaces, updates) the current, initial, or configured CL-index for that UL TCI state with the corresponding CL-index provided by the second indication. [0238] For example, if a CL-index provided by the second indication for ‘Si,j’ (where j=1) is l = 3, the WTRU may update (e.g., override) the CL-index (e.g., l = 2 provided by RRC configuration or a previously indicated update/override) of a first UL-TCI-state (having flag ‘Si,j’ where j=1) to be the indicated CL-index l = 3. The WTRU may update (e.g., override) the CL-index (e.g., l = 1 provided by RRC configuration or a previously indicated update/override) of a second UL-TCI-state (having flag ‘Si,j’ where j=1) with the indicated CL-index l = 3. [0239] When the WTRU updates (e.g., overrides) a CL-index with the indicated CL-index (e.g., l = 3) provided by the second indication, the WTRU may reset (e.g., start over) a closed-loop TPC accumulation process associated with the CL-index (e.g., l = 3). [0240] As shown at 1040, the WTRU may receive a scheduling grant for transmitting a UL signal or transmitting on a a UL channel (e.g., PUSCH, PUCCH, and/or SRS, etc.). If the UL signal or channel is associated with a TCI-state (e.g., of the specifically-ordered TCI-states) that is associated with the set of (additional) UL PC parameters, the WTRU may determine a UL power level for the transmission of the UL signal or the transmission on the UL channel. [0241] In some examples, the UL power level may be determined as P = min{Pmax, f(OLPC, CLPC)}, where: f(.) is a power control formula for the UL signal or channel; open-loop-PC(OLPC) is determined at least based on a nominal power (P0), adjusting ratio parameter (alpha), PL calculation by using a (e.g., configured) - 45 - 8902562.1
PL-RS (e.g., the DL RS configured for the TCI-state), and/or the indicated power offset (e.g., Poff1, or Poff2, etc.), where a PL term of f(.) may be calculated by the PL-RS and by applying (e.g., adding in dB scale) the power offset (e.g., Poff1, positive or negative value); and closed-loop-PC(CLPC) is determined based on one or more transmit-PC (TPC) commands being received (e.g., from a gNB) within a period of time, where which OLPC accumulation process to apply may be determined by the indicated CL-index (e.g., l = 3, updated, overridden, replaced) of the set of (additional) UL PC parameters. [0242] As shown at 1050, the WTRU may transmit the UL signal or the transmission on the UL channel by using the TCI-state and the determined UL power level. [0243] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto- optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. - 46 - 8902562.1