Implementing dynamic spatial and time domain adaptation of transmission / reception points

Abstract

A wireless transmit / receive unit (WTRU) may use the group of TCI states to determine an applicable set of TCI states. The WTRU may receive an RRC configuration for a set of TCI states, where each TCI state is identified by a TCI state identifier. The WTRU may receive signaling that associates each of the one or more TCI state groups to a TCI state identification. The WTRU may receive signaling indicating a group of TCI states suitable for the first TCI state and / or the second TCI state, and / or a group of TCI states suitable for the first and second CoresetPoolIndex values. The WTRU may activate a TCI state included in the first signaling and corresponding to any TCI state identifier associated with the TCI state group indicated by the second signaling. The WTRU may update the first and / or second TCI state to a TCI state corresponding to the applicable group of TCI states for the TCI indicator value according to the first signaling.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 531,162, filed August 7, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0002] 3GPP NR systems support an operation where a Radio Transmit / Receive Unit (WTRU) can communicate with more than one non-co-located Transmit / Receive Point (TRP). This type of operation can enhance connection throughput and robustness. Multiple TRP operations can be supported for PDCCH, PDSCH, PUCCH, and / or PUSCH channels.

[0003] TRP activation / deactivation could be a potential technology for network energy saving. This technology allows the network to enable TRP transmission and / or reception only when necessary, based on traffic conditions, thereby achieving energy savings. Summary of the Invention

[0004] The Wireless Transmit / Receive Unit (WTRU) can use TCI state groups to determine the applicable set of TCI states (e.g., as part of a unified TCI state framework). The WTRU can receive an RRC configuration for the TCI state set, where each TCI state is identified by a TCI state identifier. The WTRU can receive (first) signaling (e.g., MAC CE) that associates each(s) of TCI state group(s) (e.g., A, B, C) with a TCI state identifier for each value of a TCI indicator (e.g., 3 bits). (E.g., code point "2" corresponds to TCI state identifiers 2, 9, and 15 for TCI state groups A, B, and C, respectively.) The WTRU can receive (second) signaling (e.g., MAC CE, DCI) indicating a TCI state group applicable to a first TCI state (e.g., for a first TRP) and / or a TCI state group applicable to a second TCI state (e.g., for a second TRP) (e.g., for S-DCI M-TRP), and / or a TCI state group applicable to a first CoresetPoolIndex value (0) and a second CoresetPoolIndex value (1) (e.g., for M-DCI M-TRP). The WTRU can activate any TCI state corresponding to any TCI state identifier contained in the first signaling and associated with the TCI state group indicated by the second signaling. The WTRU can deactivate any TCI state corresponding to any TCI state identifier contained in the first signaling and not associated with a TCI state group indicated by the second signaling. For example, the second signaling can activate groups B and C, and then the WTRU activates any TCI state indicated by the first signaling for any code point as associated with group B or C.

[0005] The WTRU can receive (third) signaling (e.g., DCI), which includes a TCI indicator (e.g., a DCI for scheduling / activating PDSCH or PUSCH). The WTRU can update a first and / or second TCI state to a TCI state corresponding to the TCI state group applicable to the value of that TCI indicator, based on the first signaling. This TCI indicator can indicate whether the first TCI state (e.g., only), the second TCI state (e.g., only), or both the first and second TCI states are updated (e.g., for the S-DCI M-TRP framework). The WTRU can determine the applicable CoresetPoolIndex value from the third signaling (DCI) (e.g., based on the decoded PDCCH Coreset), determine the TCI state group associated with that CoresetPoolIndex from the second signaling, and / or update the TCI state for that applicable CoresetPoolIndex based on the TCI indicator value and the TCI state group associated with that CoresetPoolIndex (e.g., for the M-DCI M-TRP framework). The WTRU can perform one or more of the following using the updated TCI status: PDCCH monitoring; PDSCH reception; PUCCH transmission; PUSCH transmission including power control configuration (TAG); SRS transmission; (aperiodic) CSI-RS reception; and / or beam failure detection. The TCI status can be DL TCI status, UL TCI status, and / or a combination of DL / UL TCI status.

[0006] For example, the WTRU can receive RRC configurations associated with one or more TCI states from the network. These one or more (e.g., each) TCI states can be associated with their respective TCI state identifiers. The WTRU can receive a first message (e.g., via MAC CE) indicating the corresponding association between a TCI state group and a TCI state identifier for a plurality of TCI indicators (e.g., each of them). The WTRU can receive a second message (e.g., a bitmap) indicating one or more TCI state groups. The second message may include an index, and the WTRU can determine a table associated with that index. The table may include one or more entries, where each entry indicates whether the corresponding TCI state group is active or deactivated. The WTRU can determine one or more TCI states associated with each entry indicating that the corresponding TCI state group is active. The table associated with the index can be configured via RRC signaling.

[0007] The WTRU can determine a subset of one or more TCI states. Each TCI state in this subset can be associated with a TCI state identifier indicated in a first message and one or more TCI state groups indicated in a second message. The WTRU can activate each TCI state in this subset and can receive a third message indicating a TCI indicator among the plurality of TCI indicators. The WTRU can update the activated subset of one or more TCI states based on the TCI indicators received in the third message. For example, the WTRU can determine an applicable CoresetPoolIndex value based on the third message, determine the TCI state group associated with the applicable CoresetPoolIndex value based on the second message, and update the activated subset of TCI states based on the TCI indicators received in the third message and the TCI state group associated with the applicable CoresetPoolIndex value. The WTRU can use the updated subset of TCI states to perform uplink transmissions, downlink transmissions, and / or measurements. For example, the WTRU can perform one or more of the following using the updated TCI status: PDCCH monitoring; PDSCH reception; PUCCH transmission; PUSCH transmission including power control configuration (TAG); SRS transmission; (aperiodic) CSI-RS reception; and / or beam failure detection.

[0008] The WTRU can determine that one or more TCI state groups are not indicated in the second message, and then determine a second subset of those one or more TCI states. This second subset may include TCI states associated with the TCI state identifier indicated in the first message and the TCI state groups not indicated in the second message. The WTRU can deactivate (e.g., each) of the TCI states in this second subset. The WTRU can further determine a default TCI state group, determine that no TCI state group is active, and can activate that default TCI state group. Attached Figure Description

[0009] Figure 1A This is a system diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments.

[0010] Figure 1B It is shown that, according to the embodiments, it is possible to Figure 1A The system diagram shows an exemplary wireless transmit / receive unit (WTRU) used in the communication system.

[0011] Figure 1C It is shown that, according to the embodiments, it is possible to Figure 1A The system diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used in the communication system shown.

[0012] Figure 1D It is shown that, according to the embodiments, it is possible to Figure 1A The system diagram shows another exemplary RAN and another exemplary CN used in the communication system shown.

[0013] Figure 2 An example of how WTRU uses TCI state groups to determine the applicable set of TCI states is shown. Detailed Implementation

[0014] Figure 1A This is a schematic diagram illustrating an exemplary communication system 100 that can implement one or more of the disclosed embodiments. The communication system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 can 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 Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Zero-Tail Unique Word DFT Spread Spectrum OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0015] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, any one of WTRU 102a, 102b, 102c, and 102d (which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any one of WTRU 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0016] The communication system 100 may also include base station 114a and / or base station 114b. Each base station 114a, 114b may be any type of device configured to connect to at least one radio interface of WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks (e.g., CN 106 / 115, Internet 110, and / or other networks 112). For example, base stations 114a, 114b may be base transceiver stations (BTS), Node-B, eNode B, home Node B, home eNode B, gNB, NRNodeB, site controllers, access points (APs), wireless routers, etc. Although base stations 114a, 114b are each depicted as a single element, it should be understood that base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0017] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide radio service coverage for a specific geographic area, which may be relatively fixed or change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, one for each cell sector. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may 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.

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

[0019] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish air interfaces 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink (UL) Packet Access (HSUPA).

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

[0021] In the embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish air interface 116 using new radio (NR).

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

[0023] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Evolution Enhanced Data Rate (EDGE), GSM EDGE (GERAN), etc.

[0024] Figure 1ABase station 114b can be, for example, a wireless router, home Node B, home eNode B, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in localized areas (e.g., commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc.). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to Internet 110. Therefore, base station 114b may not need to access Internet 110 through CN 106 / 115.

[0025] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or VoIP-based voice services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data may have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, mobile location services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although Figure 1A Although not shown, it should be understood that RAN 104 / 113 and / or CN106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

[0028] Figure 1B This is a system diagram illustrating an exemplary WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0029] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated in an electronic package or chip.

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

[0031] Although Figure 1B While the transmit / receive element 122 is depicted 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 via the air interface 116.

[0032] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multimode capability. Therefore, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11).

[0033] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable memory (e.g., non-removable memory 130 and / or removable memory 132). 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. Removable memory 132 may include a user identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., a server or home computer (not shown)).

[0034] The processor 118 can receive power from the power supply 134 and can be configured to distribute power to and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device for powering the WTRU 102. For example, the power supply 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, etc.

[0035] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. As an addition to or alternative to the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method, while still remaining consistent with the embodiments.

[0036] The processor 118 can also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing one or more additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, such as one or more gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0037] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for both UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference through hardware (e.g., a choke) or through signal processing by a processor (e.g., a separate processor (not shown) or through processor 118). In embodiments, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception) may not be concurrent.

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

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

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

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

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

[0043] The SGW 164 can connect to each eNode B 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 typically routes and forwards user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when downlink data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0044] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices.

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

[0046] Despite WTRU in Figures 1A to 1D While described as a wireless terminal, it is conceivable that in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0047] In a representative embodiment, the other network 112 may be a WLAN.

[0048] A WLAN in Infrastructure Basic Services Set (BSS) mode may have an access point (AP) for that BSS and one or more stations (STAs) associated with the AP. The AP may have access to or connection to a distribution system (DS) or another type of wired / wireless network carrying traffic to and from the BSS. Traffic from outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic from a STA destined for a destination outside the BSS can be sent to the AP for delivery to its respective destination. Traffic between STAs within the BSS can be sent via the AP; for example, a source STA can send a traffic flow to the AP, and the AP can deliver the traffic flow to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent between the source and destination STAs (e.g., directly) using Direct Link Establishment (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to as the "self-organizing" communication mode in this article.

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

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

[0051] Ultra-high throughput (VHT) STAs can support 20MHz, 40MHz, 80MHz, and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels, which is referred to as an 80+80 configuration. For the 80+80 configuration, the channel-coded data can be divided into two streams by a segmented parser. Each stream can be processed separately using inverse fast Fourier transform (IFFT) and time-domain processing. The streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0052] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. In 802.11af and 802.11ah, the channel operating bandwidth and carrier are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support instrument-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including supporting (e.g., only supporting) certain and / or limited bandwidths. MTC devices may include batteries with battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0053] WLAN systems supporting multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STAs operating in the BSS that support the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, 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 sense and / or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, because a STA (supporting only the 1 MHz operating mode) is transmitting to the AP, the entire available band may be considered busy, even if most of the band remains idle and may be available.

[0054] In the United States, the available frequency bands for 802.11ah are 902 MHz to 928 MHz. In South Korea, the available frequency bands are 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are 916.5 MHz to 927.5 MHz. Depending on the country code, the total available bandwidth for 802.11ah is 6 MHz to 26 MHz.

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

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

[0057] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with a scalable set of parameters. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may differ for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) with multiple or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute time lengths).

[0058] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without simultaneously accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with another RAN (e.g., eNode-B 160a, 160b, and 160c) while simultaneously communicating / connecting with gNBs 180a, 180b, and 180c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, while gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0059] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink and / or downlink, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, and routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB180a, 180b, and 180c can communicate with each other via the Xn interface.

[0060] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0061] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can be used as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service types being utilized by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, etc. AMF 162 can provide control plane functionality for handover between RAN 113 and other RANs (not shown) that employ other radio technologies (such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi).

[0062] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure service flow routing through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0063] UPF 184a and 184b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-destination PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

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

[0065] Given Figures 1A to 1D as well as Figures 1A to 1D As described herein, one or more of the following functions (WTRU 102a to 102d, base stations 114a and 114b, eNode-B 160a to 160c, MME 162, SGW 164, PGW 166, gNB 180a to 180c, AMF 182a and 182ab, UPF 184a and 184b, SMF 183a and 183b, DN 185a and 185b, and / or any other devices described herein) can be performed by one or more emulation devices (not shown). An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0066] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more of these functions while being fully or partially implemented and / or deployed as part of a wired / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more of these functions while being temporarily implemented / deployed as part of a wired / or wireless communication network. Simulation devices can be directly coupled to another device for testing purposes and / or can perform tests using over-the-air wireless communication.

[0067] One or more simulation devices can perform one or more, including all, functions without being implemented / deployed as part of a wired / or wireless communication network. For example, simulation devices can be used in test scenarios within a test laboratory and / or an undeployed (e.g., tested) wired / or wireless communication network to perform tests on one or more components. One or more simulation devices can be test devices. Simulation devices can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0068] If the WTRU is configured to operate with one or more TRPs and the network deactivates at least one of these TRPs, WTRU transmission and / or reception may fail or become less reliable. More specifically, the following channels may be affected: PDCCH; PDSCH; PUCCH; and / or PUSCH.

[0069] PDCCH may be affected. If the TCI state for a Coreset corresponds to a deactivated TRP, PDCCH candidates not using this Coreset can be used, which may result in reduced PDCCH capacity and / or coverage. If one or more (e.g., all) Coresets correspond to deactivated TRPs, PDCCH reception may fail. Furthermore, if search space links are configured for one or more (e.g., two) search spaces, and one of the search spaces is associated with a deactivated Coreset, the WTRU may expect to transmit the same information on PDCCH candidates in both search spaces, and if one candidate is not transmitted, the WTRU may be unable to receive PDCCH.

[0070] PDSCH may be affected. If the TCI state used for PDSCH corresponds to a deactivated TRP, this PDSCH may not be received. Furthermore, if PDSCH retransmissions from a single DCI are configured, and some of these retransmissions are associated with a TCI state corresponding to a deactivated TRP, the WTRU may be unable to decode the PDSCH.

[0071] PUCCH reception may be affected. If the TCI state or spatial relationship configured or indicated for the PUCCH corresponds to a deactivated TRP, reception of this PUCCH may fail. Furthermore, if PUCCH retransmissions are configured, and some retransmissions are associated with a TCI state or spatial relationship corresponding to a deactivated TRP, reliability may be reduced.

[0072] PUSCH may be affected. If the TCI state or SRS resource set configured or indicated for the PUSCH corresponds to a deactivated TRP, reception of this PUSCH may fail. Furthermore, if PUSCH retransmissions are configured, and some retransmissions are associated with a TCI state or SRS resource set corresponding to a deactivated TRP, reliability may be reduced.

[0073] A WTRU can transmit or receive a physical channel or reference signal (RS) based on at least one spatial domain filter. The term "beam" can be used to refer to a spatial domain filter.

[0074] The WTRU can use the same spatial domain filter used to receive RS (e.g., CSI-RS) or SS blocks to transmit physical channels or signals. The WTRU transmission can be referred to as the "target," and the received RS or SS block can be referred to as the "reference" or "source." In this context, it can be said that the WTRU transmits the target physical channel or signal based on its spatial relationship with the reference RS or SS block.

[0075] The WTRU can transmit the first physical channel or signal based on the same spatial domain filter used for transmitting the second physical channel or signal. The first and second transmissions can be referred to as "target" and "reference" (or "source"), respectively. In this case, it can be said that the WTRU transmits the first (e.g., target) physical channel or signal based on its spatial relationship with the reference second (e.g., reference) physical channel or signal.

[0076] Spatial relationships can be implicit, configured by RRC, or indicated by MAC CE or DCI. For example, a WTRU can implicitly transmit the DM-RS of PUSCH and PUSCH according to the same spatial domain filter as the SRS indicated by the SRS Resource Indicator (SRI) specified in the DCI or configured by RRC. In another example, spatial relationships can be configured for the SRI via RRC or signaled for the PUCCH via MAC CE. Such spatial relationships can also be referred to as “beam indications”.

[0077] The WTRU can receive a first (e.g., target) downlink channel or signal based on the same spatial domain filter or spatial reception parameters as the second (e.g., reference) downlink channel or signal. For example, this association can exist between a physical channel (e.g., PDCCH or PDSCH) and its respective DM-RS. This association can exist at least when the first and second signals are reference signals, and when the WTRU is configured to have a quasi-co-location (QCL) assumption type D between the respective antenna ports. This association can be configured as a Transmission Configuration Indication (TCI) state. The WTRU can determine the association between the CSI-RS or SS block and the DM-RS by indexing the set of TCI states configured by RRC and / or indicated by MAC CE. This indication can also be referred to as a "beam indication".

[0078] A unified TCI (UTCI) (e.g., common TCI, common beam, common RS, etc.) can refer to a beam / RS intended (e.g., simultaneously) for multiple physical channels / signals. The term "TCI" can at least include a TCI state containing at least one source RS to provide a reference (e.g., WTRU assumption) for determining the QCL and / or spatial filters.

[0079] In the example, the WTRU may receive (e.g., from the gNB) an indication of a first unified TCI for use / application to the downlink control channel (PDCCH) and downlink shared channel (PDSCH) (e.g., and downlink RS). The source reference signal in the first unified TCI can provide common QCL information for at least WTRU-specific reception on the PDSCH and for all (e.g., subsets) CORESETs in the CC. In the example, the WTRU may receive (e.g., from the gNB) an indication of a second unified TCI for use / application to both the uplink control channel (PUCCH) and uplink shared channel (PUSCH) (e.g., and uplink RS). The source reference signal in the second unified TCI provides a reference for determining a common UL TX space filter for at least the PUSCH based on dynamic grant / configuration grant and for all (e.g., subsets) dedicated PUCCH resources in the CC.

[0080] WTRU can be configured for a first mode of unified TCI (e.g., SeparateDLULTCI mode), wherein the indicated unified TCI (e.g., first unified TCI or second unified TCI) can be applied to the downlink (e.g., based on the first unified TCI) or the uplink (e.g., based on the second unified TCI).

[0081] In the example, the WTRU may receive (e.g., from the gNB) an instruction for a second unified TCI to be used together for / applied to PDCCH, PDSCH, PUCCH and / or PUSCH (as well as DL RS and / or UL RS).

[0082] WTRU can be configured to use a second mode for unified TCI (e.g., JointTCI mode), where the indicated unified TCI (e.g., third unified TCI) can be applied to both downlink and uplink (e.g., based on third unified TCI).

[0083] WTRU determines the applicable TCI state for a transmission or reception by first identifying the uniform TCI state instance applicable to that transmission or reception, and then identifying the TCI state corresponding to that uniform TCI state instance. A transmission may include at least PUCCH, PUSCH, and SRS. A reception may include PDCCH, PDSCH, and / or CSI-RS. A uniform TCI state instance may also be referred to as a TCI state group, TCI state procedure, uniform TCI pool, time-domain instance / timestamp / slot / symbol set, and / or frequency-domain instance / RB / subband set, etc. A uniform TCI state instance may be equivalent to or identified as a Coreset pool identifier (e.g., CORESETPoolIndex, TRP indicator, etc.).

[0084] In this document, the term “Unified TCI” may be used interchangeably with one or more of “Unified TCI state”, “Unified TCI instance”, “TCI” and “TCI state” or “TCI status”, consistent with the embodiments disclosed herein.

[0085] In this paper, the TCI status may include downlink TCI status, uplink TCI status, and / or combined downlink / uplink TCI status.

[0086] In this document, the term "TRP" (e.g., Transmit and Receive Point) may be used interchangeably with one or more of "TP" (Transmit Point), "RP" (Receive Point), "RRH" (Radio Remote Header), "DA" (Distributed Antenna), "BS" (Base Station), "Sector" (of the BS), and / or "Cell" (e.g., a geographic cell area served by the BS), consistent with the embodiments disclosed herein. Furthermore, the term "Multiple TRP" may be used interchangeably with one or more of "MTRP," "M-TRP," and / or "Multiple TRPs," consistent with the embodiments disclosed herein.

[0087] In this document, the term "S-DCI M-TRP" can be used to refer to a scheme in which a set of transmissions (e.g., or repeated transmissions) associated with multiple TRPs are scheduled by the same DCI. When used in conjunction with a unified TCI framework, the DCI can indicate updates to the first and / or second unified TCI states.

[0088] In this document, the term "M-DCI M-TRP" can be used to refer to a scheme in which a set of transmissions (e.g., or recurring transmissions) associated with multiple TRPs are scheduled by multiple DCIs. When used in conjunction with the unified TCI framework, the DCI associated with a coresetPoolIndex value can indicate an update to the unified TCI state specific to that coresetPoolIndex value.

[0089] As used herein, the attributes of an authorization or allocation may include one or more of the following: frequency allocation; an aspect of time allocation (e.g., duration); priority; modulation and coding scheme; transport block size; number of spatial layers; number of transport blocks; TCI status, CRI, or SRI; number of retransmissions; whether the retransmission scheme is type A or type B; whether the authorization is configured as authorization type 1, configuration as authorization type 2, or dynamic authorization; whether the allocation is dynamic or semi-persistent scheduling (e.g., configured) allocation; configuration authorization index or semi-persistent allocation index; configuration authorization or allocation period; channel access priority class (CAPC); and / or any parameters provided by the DCI, MAC, or RRC used for scheduling authorization or allocation.

[0090] As used herein, DCI indications may include one or more of the following: explicit indications by DCI fields or RNTIs used for masking PDCCHCRC; and / or implicit indications by attributes (e.g., DCI format, DCI size, Coreset or search space, aggregation level, the first resource element of the received DCI (e.g., the index of the first control channel element)), wherein the mapping between attributes and values ​​may be indicated by RRC or MAC. Any signals, messages, resource allocations, and / or indications transmitted or sent by a network (e.g., gNB and / or eNB) disclosed herein may be transmitted via DCI and received by WTRU.

[0091] The term “CSI” can refer to channel state information, which may include one or more of the following: channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), L1 channel measurement (e.g., RSRP (e.g., L1-RSRP) or SINR), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSBRI), layer indicator (LI), and / or any other measurement that the WTRU measures from the configured CSI-RS or SS / PBCH (SSB) block.

[0092] The term "UCI" can refer to uplink control information, which may include: CSI, HARQ feedback for one or more HARQ processes, scheduling request (SR), link recovery request (LRR), CG-UCI, and / or other control information bits that may be transmitted on PUCCH or PUSCH.

[0093] The term “channel condition” can refer to any condition related to radio / channel state, which can be determined by the WTRU based on: WTRU measurements (e.g., L1 / SINR / RSRP, CQI / MCS, channel occupancy, RSSI, power margin, exposure margin), L3 / mobility-based measurements (e.g., RSRP, RSRQ, s-measure), RLM state, and / or channel availability in unlicensed spectrum (e.g., whether the channel is occupied (determined based on the LBT process), or whether the channel is considered to have experienced persistent LBT failures).

[0094] The term “PRACH resource” can refer to PRACH resources (e.g., in frequency), PRACH timing (RO) (e.g., in time), preamble format (e.g., in terms of total preamble duration, sequence length, guard time duration and / or cyclic prefix length), and / or a specific preamble sequence used for preamble transmission during random access.

[0095] The attributes of scheduling information (e.g., uplink grant or downlink allocation) may include one or more of the following: frequency allocation; time allocation aspects, such as duration; priority; modulation and coding scheme; transport block size; number of spatial layers; number of transport blocks to be carried; TCI status or SRI; number of repeated transmissions; whether the grant is configured as grant type 1, type 2, or dynamic grant; and so on.

[0096] Indications by DCI, or indications thereof, may include one or more of the following: explicit indications by the DCI field or the RNTI of the masked CRC for PDCCH; implicit indications by attributes (e.g., DCI format, DCI size, Coreset or search space, aggregation level, identifier of the first control channel resource for DCI (e.g., index of the first CCE)), wherein the mapping between attributes and values ​​may be indicated by RRC or MAC; and / or explicit indications by DL MAC CE.

[0097] The one or more embodiments disclosed herein can be described in the context of a unified TCI state framework used for a single or multiple TRPs, but can also be applied to non-unified TCI state frameworks.

[0098] The WTRU can use TCI state groups to determine the applicable set of TCI states. For example, when the network changes the active (e.g., or inactive) subset of TRPs within the TRP set, the WTRU can effectively address TCI states (e.g., beams). Figure 2 An example of how WTRU uses TCI state groups to determine the applicable set of TCI states is shown.

[0099] The WTRU can receive RRC configurations for a set of TCI states, where (e.g., each) TCI state is identified by a TCI state identifier. For example, an RRC configuration can be associated with a TCI state, where one or more (e.g., each) TCI states can be associated with a corresponding TCI state identifier.

[0100] The WTRU can receive (first) signaling (e.g., MAC CE) that associates one or more TCI state groups (e.g., A, B, C) (e.g., each of which) with TCI state identifiers (e.g., code point "2" corresponds to TCI state identifiers 2, 9, and 15 for TCI state groups A, B, and C, respectively). For example, the first signaling (e.g., a first message) can indicate the corresponding association between TCI state groups and TCI state identifiers for one or more of a plurality of TCI indicators (e.g., each of which).

[0101] The WTRU may receive (second) signaling (e.g., via MAC CE and / or DCI) indicating a TCI state group applicable to a first TCI state (e.g., for a first TRP) and / or a TCI state group applicable to a second TCI state (e.g., for a second TRP) (e.g., for S-DCI M-TRP), and / or a TCI state group applicable to a first CoresetPoolIndex value (0) and a second CoresetPoolIndex value (1) (e.g., for M-DCI M-TRP). For example, the second signaling (e.g., a second message) may indicate one or more TCI state groups. The second signaling may include or may be a bitmap. The second signaling may include an index, and the WTRU may determine a table associated with that index (e.g., which may be configured via RRC signaling), wherein the table includes one or more entries indicating whether a corresponding TCI state group is activated or deactivated. The WTRU may determine one or more TCI states associated with a corresponding TCI state group for (e.g., each) an entry indicating that a corresponding TCI state group is activated.

[0102] The WTRU can activate any TCI state corresponding to a TCI state identifier included in the first signaling and associated with a TCI state group indicated by the second signaling. For example, the WTRU can determine TCI states (e.g., a subset of TCI states) associated with a TCI state identifier included in the first signaling (which is associated with a TCI state group indicated by the second signaling). The WTRU can deactivate any TCI state corresponding to a TCI state identifier included in the first signaling and not associated with a TCI state group indicated by the second signaling. For example, the WTRU can determine TCI states (e.g., a second subset of TCI states) associated with a TCI state identifier included in the first signaling (which is not associated with a TCI state group indicated by the second signaling). For example, the second signaling can activate groups B and C, and the WTRU can activate any TCI state indicated by the first signaling for any code point as associated with group B or C, and / or the WTRU can deactivate any TCI state indicated by the first signaling as associated with group A.

[0103] The WTRU can receive (third) signaling (e.g., DCI), which includes TCI indicators (e.g., DCI for scheduling / activating PDSCH or PUSCH). For example, third signaling (e.g., third message) can indicate one of the multiple TCI indicators.

[0104] The WTRU can update the first and / or second TCI states to TCI states corresponding to the applicable TCI state group (e.g., an activated subset of TCI states) based on the value of the TCI indicator received in the third message, according to the first signaling, wherein the TCI indicator can indicate whether the first TCI state (e.g., only), the second TCI state (e.g., only), or both the first and second TCI states are updated (e.g., for S-DCI M-TRP).

[0105] The WTRU can determine the applicable CoresetPoolIndex value from the third signaling (DCI) (e.g., based on the Coreset used for the decoded PDCCH), determine the TCI state group associated with the applicable CoresetPoolIndex value from the second signaling, and / or update the TCI state applicable to the CoresetPoolIndex value (e.g., for M-DCI M-TRP) based on the TCI indicator value and the TCI state group associated with the CoresetPoolIndex.

[0106] The WTRU can perform one or more of the following using the updated TCI state subset: uplink transmissions (e.g., PDCCH monitoring; PDSCH reception; PUCCH transmission; PUSCH transmission including power control configuration (TAG); SRS transmission); downlink receptions (e.g., (aperiodic) CSI-RS reception); and / or measurements (e.g., beam failure detection).

[0107] The TCI status can be DL TCI status, UL TCI status, and / or a combination of DL / UL TCI status.

[0108] TCI state groups can be used. The UE can first associate a TCI state group with a TCI state using one or more solutions disclosed herein. TCI state groups can be identified by an index and / or a physical cell identifier.

[0109] Association can be performed via a MAC CE. The WTRU can perform association based on the reception of MAC signaling. For example, the WTRU can receive a MAC control element (MAC CE) that indicates a TCI state identifier for at least one TCI state group (e.g., each of the groups) for (e.g., at least one) TCI code point value. For example, the WTRU can receive a MAC CE indicating that code point "1" corresponds to TCI state identifiers 3, 10, and 13 for TCI state groups A, B, and C, respectively, code point "2" corresponds to TCI state identifiers 2, 9, and 15 for TCI state groups A, B, and C, respectively, and so on. The WTRU can also activate the indicated set of TCI states upon receiving a MAC CE. Alternatively, the WTRU can activate a subset of the indicated TCI states only upon receiving subsequent signaling (e.g., as described herein).

[0110] At least for S-DCI M-TRP operations, (e.g., the same) MAC CE can also, for at least one (e.g., each) TCI code point value, instruct the WTRU whether, upon receiving a DCI containing a TCI indicator field with this TCI code point value, it updates the first unified TCI state, the second unified TCI state, or both the first and second unified TCI states.

[0111] At least for M-DCI M-TRP operations, (e.g., the same) MAC CE can also indicate the CoresetPoolIndex value associated with the indicated TCI state.

[0112] The WTRU may receive one or more MAC CEs, wherein (e.g., each) a MAC CE may indicate the association between a TCI code point and a TCI state specific to a TCI state group. For example, the WTRU may receive a first MAC CE indicating an identifier of a first TCI state group, at least one TCI state identifier, and possibly associated TCI code points. The WTRU may then receive a second MAC CE indicating an identifier of a second TCI state group, at least one TCI state identifier, and associated TCI code points.

[0113] Association can be performed via RRC. The WTRU can associate TCI state groups with TCI states based on RRC configuration. This association can be explicitly indicated. For example, the TCI state group identifier can be indicated as part of the TCI state configuration. This indication can include existing "additionalPCI" information elements (e.g., if the reference signal is an SSB) or new information elements. If the "additionalPCI" information element is not present, the indication can correspond to the PCI of the serving cell. The association can also be implicitly determined from the linked TCI states. For example, a first reference signal (e.g., CSI-RS) can be included as part of the configuration of a first TCI state. A second TCI state can be included as part of the configuration of the first reference signal (as a QCL source). In this case, the TCI state group identifier of the first TCI state can be the TCI state group identifier of the second TCI state.

[0114] The WTRU can receive indications of activated / deactivated TCI state groups. The WTRU can receive signaling indicating a subset of TCI state groups to be activated or deactivated. The WTRU can then activate or deactivate the associated TCI states and / or identify them for scheduling purposes, as described herein.

[0115] The WTRU can receive signaling that explicitly indicates a subset of TCI state groups to be activated and / or deactivated. For example, the signaling could indicate that TCI state groups A and C are activated and TCI state group B is deactivated.

[0116] For example, the indication may include a bitmap, where (e.g., each) bit corresponds to a TCI state group, and the value of the bit indicates whether the TCI state group is active or deactivated. In another example, the WTRU may receive signaling indicating (e.g., a single) whether a particular TCI state group is active or deactivated.

[0117] The indication may include an index to a reference table, where each entry in the table can indicate whether each TCI state group is active or deactivated. This table can be configured via RRC signaling. Alternatively, the table can be predefined for each possible number of configured TCI state groups.

[0118] The WTRU group common PDCCH can be used. Signaling can be included in the MAC CE or DCI. The DCI can come from the PDCCH received in the WTRU group common search space. In this case, the WTRU can first receive the configuration of the bit positions within the DCI for (e.g., each) TCI state group.

[0119] Cell / TRP DTX / DRX activation / deactivation can be performed. The WTRU can monitor the WTRU Group Common PDCCH for cell DTX / DRX activation for at least one cell or TRP. Upon receiving a PDCCH indicating cell activation (e.g., deactivation) of DTX and / or DRX for a cell or TRP, the WTRU can deactivate (e.g., activate) the TCI state group associated with that cell or TRP. For cell DTX, this deactivation or activation can apply to downlink reception; for cell DRX, it can apply to uplink transmission. The association between the TCI state group and the cell or TRP can be explicitly configured by the RRC or based on the Physical Cell Identifier (PCI) used to generate the SSB for that cell or TRP. For example, if the WTRU receives a PDCCH indicating DTX / DRX activation for a cell using a specific PCI, the WTRU can deactivate the TCI state group corresponding to that PCI (e.g., for a TCI state configured with an additional PCI set to that PCI). The activation / deactivation of the TCI state group upon receiving a cell DTX / DRX indication can (e.g., only) occur when the PCI is not the PCI of the WTRU serving cell.

[0120] WTRU-specific PDCCHs can be used. DCIs can originate from PDCCHs received within the WTRU-specific search space, such as DCIs for scheduling PDSCHs or PUSCHs, DCIs for activating semi-persistent scheduling PDSCHs, DCIs for activating PUSCHs by configuring license type 2, or DCI formats 1_1 or 1_2 without downlink assignment. Indications can be placed in new fields of the DCI. For example, when operating M-TRP using M-DCI, the DCI fields can indicate the active TCI state group associated with the CoresetPoolIndex of the PDCCH used for decoding the DCI. In another example, when operating M-TRP using S-DCI, fields (e.g., or both fields) can indicate one or more (e.g., two) active TCI state groups associated with the first and second unified TCI states.

[0121] A maximum number of active TCI state groups may exist. A WTRU may be configured with a maximum number of active TCI state groups, such as one (1) (e.g., if not configured for M-TRP operations (e.g., single TRP)) or two (2) or more (e.g., if configured for M-TRP operations). If the WTRU receives signaling that would cause the number of active TCI state groups to exceed the maximum value, the WTRU may activate the TCI state groups based on priority order. For example, the first TCI state group (A) may have the highest priority, the second TCI state group (B) may have the second highest priority, and the third TCI state group (C) may have the lowest priority. If signaling (e.g., WTRU Group Common PDCCH) indicates that TCI state groups A, B, and C should be activated, but the maximum number of active TCI state groups is 2, the WTRU may (e.g., only) activate TCI state groups A and B and deactivate TCI state group C.

[0122] For M-TRP, the association between a TCI state group and the CoresetPoolIndex or the first / second unified TCI state can be performed. The signaling can also further instruct the association between the active TCI state group and the CoresetPoolIndex value to support M-DCI M-TRP operation, or the association between the active TCI state group and the first or second unified TCI state to support S-DCI M-TRP operation.

[0123] Signaling can explicitly indicate this association. For example, signaling can indicate a first active TCI state group associated with a first value of CoresetPoolIndex (e.g., a first unified TCI state) and a second active TCI state group associated with a second value of CoresetPoolIndex (e.g., a second unified TCI state). For example, a MAC CE or DCI can contain first and second fields corresponding (respectively) to the first and second values ​​of CoresetPoolIndex (e.g., a unified TCI state). WTRU can activate the indicated TCI state group and deactivate TCI state groups not included in the signaling.

[0124] Alternatively, WTRU can implicitly determine this association based on the activation state of (e.g., each) TCI state group and the priority order defined on the TCI state groups. WTRU can associate the TCI state group with the highest priority among the active TCI state groups with the first value of CoresetPoolIndex (e.g., the first unified TCI state), and (if there is a second active TCI state group) associate the TCI state group with the second highest priority among the active TCI state groups with the second value of CoresetPoolIndex (e.g., the second unified TCI state). For example, the first TCI state group (A) can have the highest priority, the second TCI state group (B) can have the second highest priority, and the third TCI state group (C) can have the lowest priority. In a scenario where TCI state groups A and C are active, WTRU can associate TCI state group A with the first value of CoresetPoolIndex (e.g., the first unified TCI state) and TCI state group C with the second value of CoresetPoolIndex (e.g., the second unified TCI state). In a scenario where TCI state groups B and C are activated, WTRU can associate TCI state group B with a first value of CoresetPoolIndex (e.g., or a first unified TCI state) and TCI state group C with a second value of CoresetPoolIndex (e.g., or a second unified TCI state).

[0125] Alternatively, the WTRU can implicitly determine this association from the CoresetPoolIndex of the Coreset used to decode the DCI-bearing PDCCH. For example, when operating M-TRP using M-DCI, the DCI field can indicate the active TCI state group associated with the CoresetPoolIndex of the PDCCH used to decode the DCI.

[0126] A default TCI state group may be used. The WTRU may determine the default TCI state group. The default TCI state group may correspond to at least one of the following: a set of TCI states including default TCI states as defined in the existing system; a TCI state group corresponding to the serving cell PCI, or identified by a specific identifier (e.g., zero (0)); and / or a TCI state group specifically identified as the default TCI state group by signaling (e.g., MAC CE and / or DCI).

[0127] If the signaling indicates that no TCI state group is active, the WTRU may activate the default TCI state group. In the case of M-TRP operation, the WTRU may determine the default TCI state group for (e.g., each) CoresetPoolIndex value or the first and / or second unified TCI state (e.g., each of which).

[0128] A single active TCI state group can be provided in an M-TRP operation. The WTRU can receive signaling that results in fewer than the maximum number of active TCI state groups. For example, the WTRU can be configured for an M-TRP operation with a maximum of two active TCI state groups and can receive signaling that activates a single TCI state group. In this case, the WTRU can apply at least one of the following solutions.

[0129] In the first solution, if the signaling does not provide an association between the active TCI state group and the first CoresetPoolIndex value, the WTRU may associate the default TCI state group with the first CoresetPoolIndex value. Alternatively, if the active TCI state group is associated with a second CoresetPoolIndex value, the WTRU may associate this TCI state group with the first CoresetPoolIndex value. Alternatively, transmissions and / or receptions associated with the first CoresetPoolIndex value may not be supported.

[0130] In the second solution, if the signaling does not provide an association between the active TCI state group and a first (e.g., or second) unified TCI state, the WTRU may associate a default TCI state group with the first (e.g., or second) unified TCI state. Alternatively, if the active TCI state group is associated with a second (e.g., or first) unified TCI state, the WTRU may associate this TCI state group with the second (e.g., or first) unified TCI state. Alternatively, transmissions or receptions associated with the first (e.g., or second) unified TCI state may not be supported.

[0131] The WTRU can perform activation / deactivation of TCI states corresponding to TCI state groups. Upon receiving signaling to activate (e.g., deactivate) a TCI state group, the WTRU can activate (e.g., deactivate) the TCI states associated with that TCI state group and initiate (e.g., stop) monitoring of the corresponding reference signal. The WTRU can interpret subsequent DCIs based on the indicated activated TCI state group after a period of time following the receipt of signaling indicating a change in the activated TCI state group. This period can be predefined and / or received via signaling.

[0132] The WTRU can perform TCI status indication and application / update. It can receive and update at least one (e.g., unified) TCI status indication for transmission and / or reception (including, for example, PDCCH, PDSCH, PUCCH, PUSCH, SRS, and / or CSI-RS). This signaling can also modify resources applicable to beam failure detection and recovery. The signaling can include a DCI decoded from a PDCCH received within the WTRU's specific search space, such as a DCI for scheduling a PDSCH or PUSCH, a DCI for activating a semi-persistently scheduled PDSCH, a DCI for activating a PUSCH by configuring license type 2, or a DCI format 1_1 or 1_2 without downlink allocation. This DCI can include a TCI status indicator that updates at least one unified TCI status.

[0133] In a single TRP operation, the WTRU can determine a single unified TCI state. The WTRU can first determine the active TCI state group. The WTRU can then determine the identifier of the unified TCI state to be updated by looking up the TCI state identifier corresponding to the active TCI state group and the TCI code points contained in the DCI.

[0134] In the case of M-DCI M-TRP operation, the WTRU can determine the unified TCI state associated with the CoresetPoolIndex value corresponding to the DCI. The CoresetPoolIndex value can be a value configured for the Coreset (used to decode the PDCCH containing the DCI). The WTRU can first determine the TCI state group associated with this CoresetPoolIndex value based on signaling (e.g., as described herein). Then, the WTRU can determine the identifier of the unified TCI state to be updated by looking up the TCI state identifier corresponding to this TCI state group and the TCI code points contained in the DCI.

[0135] In the case of S-DCI M-TRP operation, the WTRU can update the first and / or second unified TCI state. The WTRU can determine whether to update the first unified TCI state, the second unified TCI state, or both, based on, for example, the value of the TCI code point and a mapping indicated by the MAC CE (e.g., as described herein). The WTRU can determine, based on signaling, a first (e.g., or second) TCI state group associated with the first (e.g., or second) unified TCI state (e.g., as described herein). The WTRU can then determine the identifier of the first (e.g., or second) unified TCI state to be updated by looking up the TCI state identifier corresponding to the first (e.g., or second) TCI state group and the TCI code point contained in the DCI. Single TRP, M-DCI M-TRP, and / or S-DCI M-TRP can be used concurrently and / or individually for a given WTRU.

[0136] After determining and / or updating the identifier of the unified TCI status, the WTRU can use these unified TCI statuses to perform at least one of the following actions: PDCCH monitoring; PDSCH reception; PUCCH transmission; PUSCH transmission including power control configuration and / or timing advance; SRS transmission; (e.g., non-periodic) CSI-RS reception; and / or beam failure detection.

[0137] TRP DTX / DRX can be provided. The gNB can reduce downlink transmission / uplink reception activity from a given TRP, regardless of whether explicit signaling for TRP DTX / DRX mode is present. TRP DTX / DRX can be used to inform the WTRU whether a given TRP remains inactive or active. During TRP DTX / DRX, the TRP may have no transmission / reception, or may (e.g., only) maintain limited transmission / reception (e.g., common signals and channels that may be received by a conventional WTRU or received in idle / inactive mode). For example, the TRP may or may not transmit or receive some periodic signals / channels, such as common channels / signals and / or WTRU-specific signals or channels.

[0138] TRP DTX / DRX can be applied at least to WTRUs in the RRC_CONNECTED state. Periodic TRP DTX / DRX (e.g., active and inactive periods) can be configured by the gNB for each serving cell via WTRU-specific RRC signaling. TRP DTX / DRX modes can be activated / deactivated via dynamic L1 signaling (e.g., signaling similar to that used to activate or deactivate cell DRX / DTX) and / or WTRU-specific RRC signaling. Both WTRU-specific and group common L1 signaling can be used to activate / deactivate TRP DTX / DRX modes. TRP DTX and TRP DRX modes can be configured and operated separately (e.g., one set of RRC configurations for DL ​​and another for UL). TRP DTX / DRX can also be configured and operated together. At least the following parameters can be configured for each TRP DTX / DRX configuration: periodicity, start timeslot / offset, and / or on duration. TRP DTX indication can also be part of SI update or SIB signaling. There can be a common time for one or more (e.g., all) WTRUs to determine the TRP DTX status.

[0139] The WTRU can be configured and / or predefined or configured with one or more of the following parameters and behaviors for each TRP DTX and / or TRP DRX configuration and / or sub-configuration: one or more beam or spatial relationships to be applied when the TRP DTX / DRX is activated and deactivated; one or more applicable configuration grant (CG) or semi-persistent scheduling (SPS) configurations; whether the WTRU should monitor the PDCCH at a given coreset, search space, or aggregation level when the TRP DRX / DTX is activated and deactivated (e.g., for dynamic grant, dynamic DL allocation, or other DL signaling, including DCI with CRC scrambled by PS-RNTI, PDCCH skip indication) and / or during TRP DTX inactivity; whether to monitor a given reference signal from a given TRP (e.g., during inactivity), including BFD, RLM, and / or CSI-RS reference signals, when the TRP DTX is activated; PRACH resources or PRACH resource configurations that may or may not be applied during TRP DRX inactivity or when the cell DRX configuration is activated; and in the TRP SR / PUCCH resources or SR / PUCCH resource configurations that may or may not be applied during DRX inactivity or when TRP DRX configuration is activated; WTRU may (e.g., only) transmit on configuration authorization if the corresponding SRS resource does not correspond to TRP shutdown or TRP DRX; CSI reporting or CSI reporting resource configurations that may or may not be applied during TRP DRX inactivity or when TRP DRX configuration is activated; and / or SRS resources or SRS resource configurations that may or may not be applied during TRP DRX inactivity or when TRP DRX configuration is activated.

[0140] The WTRU can predefine or configure PRACH resources or PRACH resource configurations that may or may not be applicable during TRP DTX and / or TRP DRX inactivity or when the cell DRX configuration is active. For example, certain PRACH resources may be associated with a given TRP, and when that TRP is active, the WTRU may expect to avoid transmitting PRACH on such PRACH resources.

[0141] WTRU can predefine or configure SR / PUCCH resources or SR / PUCCH resource configurations that may or may not be applicable during TRP DTX and / or TRP DRX inactivity or when the TRP DRX configuration is active. A subset of SR configurations or PUCCH resources can be associated with a given TRP, and WTRU can avoid sending PUCCHs to that TRP when that TRP has an active TRP DRX.

[0142] WTRU can predefine or configure CSI reporting or CSI reporting resource configurations for each TRP DTX and / or TRP DRX configuration and / or sub-configuration, which may or may not be applicable during TRP DRX inactivity or when the TRP DRX configuration is active. WTRU can pause CSI feedback associated with TRP shutdown or TRP DRX.

[0143] The WTRU can be configured with predefined or pre-defined SRS resources or SRS resource configurations for each TRP DTX and / or TRP DRX and / or sub-configuration, which may or may not be applicable during TRP DRX inactivity or when the TRP DRX configuration is active. The WTRU can avoid transmitting SRS during TRP shutdown or TRP DRX. The WTRU can be configured with a set of auxiliary SRS resources to use when the TRP is in TRP DRX, shutdown, or silent state.

[0144] The WTRU can be configured with a primary TRP and / or a secondary TRP. The WTRU can assume that the TRP DRX / DTX (e.g., only) applies to the secondary TRP. Signaling activating the TRP DRX / DTX can indicate a given TRP index (e.g., via DCI indication, according to the signaling methods described herein). The WTRU can be configured with stable and unstable TRP classifications, where stable TRPs do not disable or apply TRP DRX / DTX. The WTRU may not monitor TRP silencing signaling or DTX / DRX activation signaling for stable TRPs. The WTRU may monitor TRP DTX / DRX activation signaling (e.g., including the signaling described herein) at specific times (e.g., periodically).

[0145] When a given TRP has an active TRP DRX / DTX, the WTRU can monitor additional signals and channels on alternative TRPs. For example, the WTRU can conditionally monitor additional coreset, search space, or PDCCH resources on alternative TRPs associated with a TRP that has applied DTX or is closed. The WTRU can be configured with associations between TRPs (e.g., stable-to-unstable TRP associations) such that the WTRU can fall back to a stable TRP once an unstable TRP is silenced or closed. If one TRP (e.g., the associated TRP) is closed, the WTRU can infer that the coreset / search space of another TRP (e.g., a stable TRP) will periodically change. The WTRU can be configured with conditional search spaces and / or coresets for monitoring a given TRP (e.g., a stable TRP) when another TRP (e.g., the associated TRP) is closed, silenced, has an active TRP DTX, or is inactive during a TRP DTX.

[0146] (For example, each) Coreset can be associated with a coresetPoolIndex and TCI state corresponding to a TRP. During DTX inactivity or when a TRP is silenced or turned off, WTRU may not need to monitor the search space for the TCI state / coresetPoolIndex corresponding to these TRPs. WTRU can modify the PDCCH monitoring rules to perform additional monitoring on TRPs that remain active (e.g., stable TRPs or TRPs associated with silenced TRPs). When TRP DTX is turned off or activated, silenced TRPs can indicate whether other TRPs and their indices are not monitored (potentially for one timer period, e.g., configured, indicated, or inferred from configured DTX inactivity).

[0147] WTRU can be configured and / or associated with a secondary TCI state (e.g., or fallback to another unified TCI) for use when the primary TCI state corresponds to TRP off or TRP DTX and / or when the primary TRP is inactive.

[0148] The WTRU can determine from system information whether a subset of cell TRPs are muted, disabled, or have active DTXs. The WTRU can ignore signals from such TRPs for channel measurement purposes (e.g., for cell selection, reselection, and / or connectivity mode mobility).

[0149] If TRP activates TRP DRX or disables it, WTRU can dynamically switch to monitor different CSI-RS and / or SSB resource sets.

[0150] When a subset of TRPs is in DTX, off mode, or silent mode, WTRU can ignore the path loss reference associated with such TRPs in order to perform path loss calculations.

[0151] Adaptation of TRP antenna ports and / or elements can be performed. The WTRU can assume that a subset of antenna ports and / or elements on a given TRP are disabled, which may be based on the applied and / or indicated signaling cell spatial domain NES sub-configuration. The WTRU can be configured with spatial domain sub-configurations / assumptions for each TRP, wherein the association between which TRP is being silenced and / or reducing its number of ports / elements is inferred through the indicated spatial domain sub-configuration / assumptions associated with the TRP via RRC configuration. The WTRU can receive cell spatial domain sub-configurations / assumptions, but apply them to subsets of TRPs, wherein the subset of TRPs can be individually indicated (e.g., as described herein) and / or inferred from the sub-configuration index.

[0152] WTRU can assume that a given TRP is closed / silent / or has an active TRP DTX when it receives an indication of spatial domain subconfiguration / assumption associated with the TRP.

[0153] For a given silent TRP, the WTRU can provide an assumed CSI RS based on the transmitted signals (e.g., SSB, DRS, and / or CSI-RS from remaining ON ports / elements). The WTRU can combine the CSI report with other reports for other TRPs and / or report them separately.

[0154] The WTRU can implicitly infer the BFD, CSI, and / or RLM signals to be monitored from the indicated TCI state of the corresponding coreset (e.g., as described herein). The WTRU can trigger BFD (e.g., only) when BFD is detected on one or more (e.g., all) TRPs in a cell, one or more (e.g., all) TRPs in the same cell index, one or more (e.g., all) stable TRPs, and / or only for stable TRPs (e.g., those TRPs not employing the NES approach). The WTRU can suspend beam failure detection for BFD-RS resources corresponding to TRP shutdown (e.g., suspend RLM for RLM-RS). The WTRU can suspend beam failure detection for BFD-RS resources during the inactivity of a TRP DTX. If (e.g., a) TRP is silent, shut down, or applies a TRP DTX, the WTRU can use resources of an alternative TRP for BFD and RLM.

[0155] The processes and methods described herein can be applied in any combination and can be used with other wireless technologies and for other services.

[0156] WTRU can refer to the identifier of a physical device or the identifier of a user, such as a subscription-related identifier like an MSISDN or SIP URI. WTRU can also refer to an application-based identifier, such as a username used for each application.

[0157] The above processes can be implemented in computer programs, software, and / or firmware incorporated in computer-readable media for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor storage devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and / or optical media (e.g., CD-ROM disks and / or digital multifunction disks (DVDs)). The processor, combined with the software, can be used to implement radio frequency transceivers for use in WTRUs, UEs, terminals, base stations, RNCs, and / or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU) including a processor configured to: Receive radio resource control (RRC) configurations associated with one or more Transmission Configuration Indication (TCI) states from the network, each of which is associated with a corresponding TCI state identifier; Receive a first message from the network, the first message indicating a corresponding association between a TCI state group and a TCI state identifier for each of a plurality of TCI indicators; Receive a second message from the network indicating one or more TCI status groups; Determine a subset of the one or more TCI states, wherein each TCI state in the subset of the one or more TCI states is associated with a TCI state identifier indicated in the first message and the one or more TCI state groups indicated in the second message; Activate each of the subsets of the one or more TCI states; Receive a third message from the network indicating one of the plurality of TCI indicators; The activated subset of one or more TCI states is updated based on the TCI indicator received in the third message; as well as Use one or more of the updated subsets of the one or more TCI states to perform at least one of the uplink transmission, downlink transmission, and measurement.

2. The WTRU of claim 1, wherein the processor is further configured to: It is determined that one or more TCI status groups are not indicated in the second message; Determine a second subset of the one or more TCI states, wherein each TCI state in the second subset of the one or more TCI states is associated with a TCI state identifier indicated in the first message and a group of one or more TCI states not indicated in the second message; and Deactivate each of the second subset of the one or more TCI states.

3. The WTRU as claimed in claim 1 or 2, wherein the processor is further configured to: Determine the default TCI state group; It was determined that no TCI state group was activated; and Activate the default TCI state group.

4. The WTRU of any one of claims 1 to 3, wherein the processor is configured to receive the first message via a first media access control (MAC) control element (CE).

5. The WTRU of claim 4, wherein the processor is configured to receive the second message via one or more of a second MAC CE and one or more downlink control information (DCI).

6. The WTRU of any one of claims 1 to 5, wherein the processor is configured to update the activated subset of the one or more TCI states based on the TCI indicator received in the third message, comprising: The processor is configured to: The applicable CoresetPoolIndex value is determined based on the third message; Based on the second message, determine the TCI state group associated with the applicable CoresetPoolIndex value; and The activated subset of one or more TCI states is updated based on the TCI indicator received in the third message and the TCI state group associated with the applicable CoresetPoolIndex value.

7. The WTRU of any one of claims 1 to 6, wherein the processor is configured to perform at least one of uplink transmission, downlink transmission, and measurement using one or more of the updated subsets of the one or more TCI states, comprising: The processor is configured to perform at least one of the following: monitoring the physical downlink control channel (PDCCH); receiving downlink transmissions on the physical downlink shared channel (PDSCH); transmitting uplink transmissions on the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH); performing sounding reference signal (SRS) transmissions; receiving channel state information reference signal (CSI-RS) transmissions; and detecting beam failures.

8. The WTRU of any one of claims 1 to 7, wherein the second message comprises a bitmap.

9. The WTRU of any one of claims 1 to 8, wherein the second message includes an index, and wherein the processor configured to determine a subset of the one or more TCI states includes the processor configured to: Determine the table associated with the index, wherein the table comprises one or more entries, and wherein each entry indicates whether the corresponding TCI state group is activated or deactivated; and For each entry indicating that the corresponding TCI state group is activated, determine one or more TCI states associated with the corresponding TCI state group.

10. The WTRU of claim 9, wherein the table associated with the index is configured by Radio Resource Control (RRC) signaling.

11. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: Receive radio resource control (RRC) configurations associated with one or more Transmission Configuration Indication (TCI) states from the network, each of which is associated with a corresponding TCI state identifier; Receive a first message from the network, the first message indicating a corresponding association between a TCI state group and a TCI state identifier for each of a plurality of TCI indicators; Receive a second message from the network indicating one or more TCI status groups; Determine a subset of the one or more TCI states, wherein each TCI state in the subset of the one or more TCI states is associated with a TCI state identifier indicated in the first message and the one or more TCI state groups indicated in the second message; Activate each of the subsets of the one or more TCI states; Receive a third message from the network indicating one of the plurality of TCI indicators; The activated subset of one or more TCI states is updated based on the TCI indicator received in the third message; as well as Use one or more of the updated subsets of the one or more TCI states to perform at least one of the uplink transmission, downlink transmission, and measurement.

12. The method of claim 11, further comprising: It is determined that one or more TCI status groups are not indicated in the second message; Determine a second subset of the one or more TCI states, wherein each TCI state in the second subset of the one or more TCI states is associated with a TCI state identifier indicated in the first message and a group of one or more TCI states not indicated in the second message; and Deactivate each of the second subset of the one or more TCI states.

13. The method of claim 11 or 12, further comprising: Determine the default TCI state group; It was determined that no TCI state group was activated; as well as Activate the default TCI state group.

14. The method of any one of claims 11 to 13, wherein the first message is received via a first media access control (MAC) control element (CE).

15. The method of claim 14, wherein the second message is received via one or more of a second MAC CE and one or more downlink control information (DCI).

16. The method of any one of claims 11 to 15, wherein updating the activated subset of the one or more TCI states based on the TCI indicator received in the third message comprises: The applicable CoresetPoolIndex value is determined based on the third message; Based on the second message, determine the TCI state group associated with the applicable CoresetPoolIndex value; and The activated subset of one or more TCI states is updated based on the TCI indicator received in the third message and the TCI state group associated with the applicable CoresetPoolIndex value.

17. The method of any one of claims 11 to 16, wherein performing at least one of uplink transmission, downlink transmission, and measurement using one or more of the updated subsets of the one or more TCI states comprises performing at least one of: monitoring the physical downlink control channel (PDCCH); receiving downlink transmission on the physical downlink shared channel (PDSCH); transmitting uplink transmission on the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH); performing sounding reference signal (SRS) transmission; receiving channel state information reference signal (CSI-RS) transmission; and detecting beam failure.

18. The method of any one of claims 11 to 17, wherein the second message comprises a bitmap.

19. The method of any one of claims 11 to 18, wherein the second message includes an index, and wherein determining a subset of the one or more TCI states comprises: Identify a table associated with the index, wherein the table comprises one or more entries, and wherein each entry indicates whether the corresponding TCI state group is activated or deactivated; as well as For each entry indicating that the corresponding TCI state group is activated, determine one or more TCI states associated with the corresponding TCI state group.

20. The method of claim 19, wherein the table associated with the index is configured by Radio Resource Control (RRC) signaling.

Images