Enabling dynamic spatial and temporal domain adaptation of transmit / receive points.

Abstract

A wireless transmit / receive unit (WTRU) can use groups of TCI states to determine an applicable set of TCI states. The WTRU can receive RRC configurations for sets of TCI states, each identified by a TCI state identifier. The WTRU can receive signaling that associates each of one or more TCI state groups with a TCI state. The WTRU can receive signaling that indicates TCI state groups applicable to a first TCI and / or a second TCI state, and / or TCI state groups applicable to a first TCI and / or a second CoresetPoolIndex value. The WTRU can activate TCI states for any TCI state identifiers included in the first signaling that are associated with the TCI state groups indicated by the second signaling. The WTRU can update the first and / or second TCI states to TCI states corresponding to applicable TCI state groups for TCI indicator values, according to the first signaling.

Description

Technical Field

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

Background Art

[0002] The 3GPP NR system supports an operation in which a wireless transmit-receive unit (WTRU) can communicate with two or more transmit / receive points (TRPs) that are not co-located. This type of operation can improve the connection throughput and robustness. The multi-TRP operation can be supported for PDCCH, PDSCH, PUCCH, and / or PUSCH channels.

[0003] TRP activation / deactivation is a technique that can be taken for network energy savings. This technique can result in energy savings by enabling the network to turn on the TRP transmission and / or reception functions only when required by a given traffic situation.

Summary of the Invention

Means for Solving the Problems

[0004] A wireless transmit / receive unit (WTRU) can determine an applicable set of TCI states using a group of TCI states (for example, as part of a unified TCI state framework). The WTRU can receive an RRC configuration for a set of TCI states, each identified by a TCI state identifier. For each value of a TCI indicator (e.g., 3 bits), the WTRU can receive a (first) signaling (e.g., MAC CE) associating each of one or more TCI state groups (e.g., A, B, C) with a TCI state identifier (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 a (second) signaling (e.g., MAC CE, DCI) indicating a TCI state group applicable to a first TCI state (e.g., first TRP) and / or a TCI state group applicable to a second TCI state (e.g., second TRP) (e.g., 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., M-DCI M-TRP). The WTRU can activate the TCI state of any TCI state identifier included in the first signaling that is associated with the TCI state group indicated by the second signaling. The WTRU can deactivate the TCI state of any TCI state identifier included in the first signaling that is associated with a TCI state group not indicated by the second signaling. For example, a second signaling can activate groups B and C, and then the WTRU can activate any TCI state indicated by the first signaling so that any code point is associated with group B or C.

[0005] The WTRU may receive a (third) signaling (e.g., DCI) that includes a TCI indicator (e.g., a DCI that schedules / activates a PDSCH or PUSCH). In accordance with the first signaling, the WTRU may update the first and / or second TCI states for the value of the TCI indicator to the TCI state corresponding to the applicable TCI state group. Here, the TCI indicator may 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 an applicable CoresetPoolIndex value from a third signaling (DCI) (e.g., based on the Coreset of the decoded PDCCH), determine the TCI state group associated with the CoresetPoolIndex from the second signaling, and / or update the TCI state of the applicable CoresetPoolIndex based on the TCI indicator value and the TCI state group associated with the CoresetPoolIndex (e.g., for the M-DCI M-TRP framework). Using the updated TCI state, the WTRU can perform one or more of the following: PDCCH monitoring, PSCH reception, PUCCH transmission, PUSCH transmission including power control configuration (TAG), SRS transmission, (non-periodic) CSI-RS reception, and / or beam fault detection. The TCI state can be a DL TCI state, an UL TCI state, and / or a joint DL / UL TCI state.

[0006] For example, a WTRU can receive RRC configurations from the network associated with one or more TCI states. One or more TCI states (e.g., each) can be associated with a respective TCI state identity. For multiple TCI indicators (e.g., each), the WTRU can receive a first message (e.g., via MAC CE) indicating the respective association between the TCI state group and the TCI state identity. 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 the table associated with the index. The table may include one or more entries, each of which may indicate whether each TCI state group is activated or deactivated. For each entry indicating that each TCI state group is activated, the WTRU can determine one or more TCI states associated with each TCI state group. The table associated with the index can be configured via RRC signaling.

[0007] A WTRU can determine a subset of one or more TCI states. Each TCI state in the subset may be associated with a TCI state identifier shown in a first message and one or more TCI state groups shown in a second message. The WTRU can activate each TCI state in the subset and receive a third message indicating TCI indicators for multiple TCI indicators. Based on the TCI indicators received in the third message, the WTRU can update an activated subset of one or more TCI states. For example, the WTRU can determine an applicable CoresetPoolIndex value based on the third message, determine a TCI state group associated with the applicable CoresetPoolIndex value based on the second message, and update an 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. The WTRU can use the updated TCI state to perform one or more of the following: PDCCH monitoring, PSCH reception, PUCCH transmission, PUSCH transmission including power control configuration (TAG), SRS transmission, (non-periodic) CSI-RS reception, and / or beam fault 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 one or more TCI states. The second subset may include TCI states associated with TCI state identifiers shown in the first message and TCI state groups not shown in the second message. The WTRU can deactivate (for example, each of) TCI states in the second subset. The WTRU can further determine a default TCI state group, determine that a TCI state group is not activated, and activate the default TCI state group. [Brief explanation of the drawing]

[0009] [Figure 1A] Figure 1A shows an exemplary communication system that can implement one or more disclosed embodiments. [Figure 1B] Figure 1B shows an exemplary wireless transceiver unit (WTRU) used in the communication system shown in Figure 1A, according to one embodiment. [Figure 1C] Figure 1C is a system diagram showing an exemplary radio access network (RAN) and core network (CN) used in the communication system of Figure 1A, according to one embodiment. [Figure 1D] Figure 1D is a system diagram showing further exemplary RAN and CN used in the communication system of Figure 1A according to one embodiment. [Figure 2] Figure 2 shows an example of a WTRU that uses a group of TCI states to determine the set of applicable TCI states. [Modes for carrying out the invention]

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

[0011] As shown in Figure 1A, the communication system 100 may include radio transceiver units (WTRUs) 102a, 102b, 102c, 102d, radio access networks (RANs) 104 / 113, core networks (CNs) 106 / 115, public switched telephone networks (PSTNs) 108, the Internet 110, and other networks 112, but it will be understood that the disclosed embodiments intend any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a radio environment. For example, WTRU102a, 102b, 102c, and 102d may all be referred to as “stations” and / or “STAs” and may be configured to transmit and / or receive radio signals, and may include (or be) user equipment (UEs), 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 wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain context), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. Any of WTRU102a, 102b, 102c, and 102d may interchangeably be referred to as UEs.

[0012] The communication system 100 may also include base stations 114a and / or base stations 114b. Each of the base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or network 112. As an example, base stations 114a and 114b may be any of the following: base station transceiver station (BTS), node B (NB), e-node B (eNB), home node B (HNB), home e-node B (HeNB), g-node B (gNB), NR node B (NR NB), site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are shown as single elements, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0013] 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 a base station controller (BSC), a radio network controller (RNC), and relay nodes. 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 called cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell can provide coverage for radio services to a particular geographic area that may be relatively fixed or change over time. A cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology, which may utilize multiple transceivers for each sector of the cell or any sector. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

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

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

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

[0017] In one embodiment, base stations 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as NR radio access, which can establish an air interface 116 using New Radio (NR).

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

[0019] In one embodiment, base stations 114a and WTRUs 102a, 102b, and 102c can implement wireless technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Advanced Data Rate (EDGE), and GSM EDGE (GERAN).

[0020] In Figure 1A, base station 114b may 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 such as offices, homes, vehicles, premises, industrial facilities, aerial corridors (for use by drones, for example), and roads. In one embodiment, base station 114b and WTRU 102c, 102d can implement wireless technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRU 102c, 102d can implement wireless technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, base station 114b and WTRU 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any small cell, picocell, or femtocell. As shown in Figure 1A, base station 114b may have a direct connection to the internet 110. Therefore, base station 114b may not be required to access the internet 110 via CN 106 / 115.

[0021] RAN104 / 113 may communicate with CN106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU102a, 102b, 102c, and 102d. The data may have various Quality of Service (QoS) requirements, including different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. CN106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, internet connectivity, video distribution, and / or implement high-level security functions, such as user authentication. Although not shown in Figure 1A, it will be understood that RAN104 / 113 and / or CN106 / 115 may communicate directly or indirectly with other RANs employing the same or different RATs as RAN104 / 113. For example, in addition to being connected to RAN104 / 113, which may utilize NR radio technology, CN106 / 115 may also communicate with another RAN (not shown) employing one of the following technologies: GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0022] CN106 / 115 can also act as a gateway for WTRU102a, 102b, 102c, 102d to access the PSTN108, the Internet 110, and / or other networks 112. The PSTN108 can include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 can include a global system of interconnected computer networks and devices that use common communication protocols such as TCP, User Datagram Protocol (UDP), and / or IP in the Transmission Control Protocol / Internet Protocol (TCP / IP) Internet protocol suite. The network 112 can include wired and / or wireless communication networks that are owned and / or operated by other service providers. For example, the network 112 can include another CN connected to one or more RANs that can employ the same RAT or a different RAT as the RAN104 / 114.

[0023] Some or all of the WTRU102a, 102b, 102c, 102d in the communication system 100 can include multimode capabilities (e.g., the WTRU102a, 102b, 102c, 102d can include multiple transceivers for communicating with different wireless networks via different wireless links). For example, the WTRU102c shown in FIG. 1A can be configured to communicate with a base station 114a that can employ cellular-based wireless technology and can be configured to communicate with a base station 114b that can employ IEEE802 wireless technology.

[0024] Figure 1B is a system diagram showing an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 can include, among other things, a processor 118, a transceiver 120, a transceiver element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other elements / peripherals 138. It will be understood that the WTRU 102 can include any sub-combination of the above elements while remaining in accordance with one embodiment.

[0025] The processor 118 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of 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. The processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, can be coupled to the transceiver element 122. Although Figure 1B shows the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 can be incorporated together, for example, in an electronic package or chip.

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

[0027] Although the transmit / receive element 122 is shown as a single element in Figure 1B, the WTRU 102 can include any number of transmit / receive elements 122. For example, the WTRU 102 can employ MIMO technology. Thus, in one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving radio signals via the air interface 116.

[0028] The transceiver 120 may be configured to modulate the signal to be transmitted by the transmitting / receiving element 122 and to demodulate the signal to be received by the transmitting / receiving element 122. As described above, the WTRU 102 may have multimode capability. Therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0029] The processor 118 of the WTRU102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (for example, a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit) and may receive user input data from them. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Furthermore, the processor 118 may access information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132, and store data therein. 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 subscriber identification module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 can access information from memory not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data therein.

[0030] The processor 118 may be configured to receive power from the power supply 134 and distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device for supplying power to 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.), a solar cell, a fuel cell, etc.

[0031] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or instead of, 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 when signals are received from two or more nearby base stations. It will be understood that the WTRU 102 may acquire location information via any preferred location determination method while remaining consistent with one embodiment.

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

[0033] WTRU102 may include a full-duplex radio where the transmission and reception of some or all of a signal may be parallel and / or simultaneous, associated with a specific subframe for both an uplink (for transmission, for example) and a downlink (for reception, for example). The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing either through hardware (e.g., chokes) or through a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU102 may include a half-duplex radio, which is for the transmission and reception of some or all of a signal (e.g., associated with a specific subframe for either an uplink (for transmission, for example) or a downlink (for reception, for example).

[0034] Figure 1C is a system diagram showing RAN104 and CN106 according to one embodiment. As described above, RAN104 can employ E-UTRA radio technology to communicate with WTRU102a, 102b, and 102c via the air interface 116. RAN104 may also communicate with CN106.

[0035] RAN104 may include enodes B160a, 160b, and 160c, but it will be understood that RAN104 may include any number of enodes B while remaining consistent with one embodiment. Each of enodes B160a, 160b, and 160c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, enodes B160a, 160b, and 160c can implement MIMO technology. Thus, enode B160a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU102a.

[0036] Each of the e-nodes B160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to handle wireless resource management decisions, handover decisions, user scheduling on uplink (UL) and / or downlink (DL), etc. As shown in Figure 1C, the e-nodes B160a, 160b, and 160c can communicate with each other via the X2 interface.

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

[0038] The MME162 can be connected to each of the e-nodes B160a, 160b, and 160c in RAN104 via the S1 interface and can act as a control node. For example, the MME162 can be responsible for authenticating users of WTRU102a, 102b, and 102c, activating / deactivating bearers, and selecting a specific serving gateway during the initial attachment of WTRU102a, 102b, and 102c. The MME162 can provide control plane functionality for switching between RAN104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0039] The SGW164 can be connected to each of the e-nodes B160a, 160b, and 160c in RAN104 via the S1 interface. The SGW164 can generally route and forward user data packets to and from WTRU102a, 102b, and 102c. The SGW164 can perform other functions such as anchoring the user plane during e-node B handovers, triggering paging when DL data is available for WTRU102a, 102b, and 102c, and managing and remembering the context of WTRU102a, 102b, and 102c.

[0040] SGW164 may be connected to PGW166, which can provide WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices.

[0041] CN106 can facilitate communication with other networks. For example, CN106 can provide WTRU102a, 102b, and 102c with access to circuit-switched networks such as PSTN108, thereby facilitating communication between WTRU102a, 102b, and 102c and legacy landline communication devices. For example, CN106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN106 and PSTN108. Furthermore, CN106 can provide WTRU102a, 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.

[0042] Although the WTRU is described as a wireless terminal in Figures 1A to 1D, in certain representative embodiments, such a terminal is intended to be able to use a wired communication interface with a communication network (for example, temporarily or permanently).

[0043] In a typical embodiment, the other network 112 may be a WLAN.

[0044] In Infrastructure Basic Service Set (BSS) mode, a WLAN may have access points (APs) for the BSS and one or more stations (STAs) associated with the APs. APs may have access to or interfaces with distributed systems (DSs) or other types of wired / wireless networks that carry traffic during and / or from the BSS. Traffic originating outside the BSS to the STAs may arrive through the APs and be delivered to the STAs. Traffic originating from the STAs to destinations outside the BSS may be sent to the APs to be delivered to their respective destinations. Traffic between STAs within the BSS may be sent through the APs; for example, a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS is considered and / or sometimes referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between a source STA and a destination STA (for example, directly between them) via a direct link setup (DLS). In some typical embodiments, the DLS may be an 802.11e DLS or an 802.11z tunnel DLS (TDLS). A WLAN using Independent BSS (IBSS) mode may not have access points (APs), and STAs within or using IBSS (for example, all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to as the “ad-hoc” communication mode in this specification.

[0045] When using the 802.11ac infrastructure operating mode or a similar operating mode, an AP can transmit beacons on a fixed channel, such as a primary channel. The primary channel can be a fixed width (e.g., a 20 MHz bandwidth) or a dynamically set width via signaling. The primary channel can be the operating channel of the BSS, which can be used by STAs to establish a connection with the AP. In some typical embodiments, Carrier sense multiple access with collision avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. In CSMA / CA, an STA, including the AP (e.g., any STA), can sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, that STA can backoff. One STA (e.g., only one station) can transmit at any given time within a given BSS.

[0046] A high-throughput (HT) STA can use a 40MHz wide channel for communication, for example, via a combination of a primary 20MHz channel and adjacent or non-adjacent 20MHz channels to form a 40MHz wide channel.

[0047] Ultra-high throughput (VHT) STAs can support 20MHz, 40MHz, 80MHz, and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining consecutive 20MHz channels. 160MHz channels can be formed by combining eight consecutive 20MHz channels, or by combining two discontinuous 80MHz channels, sometimes referred to as an 80+80 configuration. In the 80+80 configuration, data can be passed through a segment parser that, after channel encoding, can split the data into two streams. Inverse fast Fourier transform (IFFT) processing and time-domain processing can be performed separately for each stream. The streams can be mapped onto two 80MHz channels, and the data can be transmitted by a transmitting STA. At the receiver of a receiving STA, the operation described above for the 80+80 configuration can be reversed, and the combined data can be sent to a media access control (MAC) layer, entities, etc.

[0048] Sub-1GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using the non-TVWS spectrum. According to a typical embodiment, 802.11ah can support meter-type control / machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have limited capabilities, including support for some and / or limited bandwidths (e.g., support only for that). MTC devices may include batteries with above-threshold battery life (e.g., to maintain very long battery life).

[0049] A WLAN system that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, includes a channel that can be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA that supports the minimum bandwidth operating mode from among all STAs operating in the BSS. In the 802.11ah example, the primary channel may be 1 MHz wide for an STA (e.g., an MTC type device) that supports (e.g., only) 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier detection and / or network allocation vector (NAV) settings may depend on the status of the primary channel. For example, if the primary channel is busy because an STA (which only supports 1MHz operating mode) is transmitting to the AP, the entire available frequency band may be considered busy, even though a large portion of the frequency band remains idle and could be available.

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

[0051] Figure 1D is a system diagram showing RAN113 and CN115 according to one embodiment. As described above, RAN113 can employ NR radio technology to communicate with WTRU102a, 102b, and 102c via the air interface 116. RAN113 may also communicate with CN115.

[0052] RAN113 may include gNB180a, 180b, and 180c, but it will be understood that RAN113 may include any number of gNBs while remaining consistent with one embodiment. Each of the gNB180a, 180b, and 180c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, the gNB180a, 180b, and 180c can implement MIMO technology. For example, the gNB180a and 180b can utilize beamforming to transmit signals to and / or receive signals from the WTRU102a, 102b, and 102c. Thus, the gNB180a can, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from the WTRU102a. In one embodiment, gNB180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB180a can transmit multiple component carriers to WTRU102a (not shown). A subset of these component carriers may be on the unlicensed spectrum, while the remaining component carriers may be on the licensed spectrum. In one embodiment, gNB180a, 180b, and 180c can implement coordinated multi-point (CoMP) technology. For example, WTRU102a can receive coordinated transmissions from gNB180a and gNB180b (and / or gNB180c).

[0053] WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using transmissions associated with scalable numerology. For example, OFDM symbol intervals and / or OFDM subcarrier intervals may differ for different transmissions, different cells, and / or different parts of the radio transmission spectrum. WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using subframes or transmit time intervals (TTIs) of varying or scalable lengths (including, for example, a varying number of OFDM symbols and / or a varying length of absolute time that persists).

[0054] gNB180a, 180b, and 180c can be configured to communicate with WTRU102a, 102b, and 102c in standalone and / or non-standalone configurations. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c without accessing other RANs (such as e-nodes B160a, 160b, and 160c). In a standalone configuration, WTRU102a, 102b, and 102c can utilize one or more of gNB180a, 180b, and 180c as mobility anchor points. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using signals in unlicensed bands. In a non-standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c while also communicating with other RANs such as enodes B160a, 160b, and 160c. For example, WTRU102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNB180a, 180b, and 180c, and one or more enodes B160a, 160b, and 160c. In a non-standalone configuration, enodes B160a, 160b, and 160c can act as mobility anchors for WTRU102a, 102b, and 102c, and gNB180a, 180b, and 180c can provide additional coverage and / or throughput to service WTRU102a, 102b, and 102c.

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

[0056] The CN115 shown in Figure 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the above elements is shown as part of the CN115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0057] AMF182a and 182b can be connected to one or more of gNB180a, 180b, and 180c in RAN113 via the N2 interface and can act as control nodes. For example, AMF182a and 182b can be responsible for user authentication of WTRU102a, 102b, and 102c, support for network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selection of specific SMF183a and 183b, management of registration areas, termination of NAS signaling, mobility management, etc. Network slicing can be used by AMF182a and 182b to customize CN support for WTRU102a, 102b, and 102c based on the type of service being utilized by WTRU102a, 102b, and 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-high reliability low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, and services for MTC access. AMF182a, 182b can provide control plane functionality for switching between RAN113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as Wi-Fi.

[0058] SMF183a and 183b can be connected to AMF182a and 182b in CN115 via the N11 interface. SMF183a and 183b can also be connected to UPF184a and 184b in CN115 via the N4 interface. SMF183a and 183b can select and control UPF184a and 184b and configure the routing of traffic through UPF184a and 184b. SMF183a 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.

[0059] UPF184a and 184b may be connected via the N3 interface to one or more of gNB180a, 180b, and 180c in RAN113, which can provide WTRU102a, 102b, and 102c with access to a packet-switched network, such as the Internet 110, to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices. UPF184a and 184b can perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0060] CN115 can facilitate communication with other networks. For example, CN115 may include or be able to communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN115 and PSTN108. Furthermore, CN115 can provide WTRU102a,102b,102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRU102a,102b,102c may be connected to DN185a,185b through UPF184a,184b via an N3 interface to UPF184a,184b, and an N6 interface between UPF184a,184b and local data networks (DN) 185a,185b.

[0061] In view of Figures 1A to 1D and their corresponding descriptions, one or more, or all, of the functions described herein with respect to any of the WTRU 102a to d, base stations 114a to b, e-nodes B160a to c, MME 162, SGW 164, PGW 166, gNB 180a to c, AMF 182a to b, UPF 184a to b, SMF 183a to b, DN 185a to b, and / or any other (one or more) elements / devices described herein may be implemented by one or more emulation elements / devices (not shown). An emulation device may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, an emulation device may be used to test other devices and / or to simulate network and / or WTRU functions.

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

[0063] One or more emulation devices can perform one or more functions, including all of the above, while not implemented / deployed as part of a wired and / or wireless communication network. For example, an emulation device may be used in a test laboratory and / or in a test scenario in a non-deployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., including one or more antennas) may be used by an emulation device to transmit and / or receive data.

[0064] If a WTRU is configured to operate on one or more TRPs, and the network deactivates at least one of these TRPs, the WTRU's transmission and / or reception may fail or have low reliability. More specifically, the following channels, PDCCH, PDSCH, PUCCH, and / or PUSCH, may be impaired:

[0065] PDCCHs can fail. If the TCI state for a Coreset corresponds to a deactivated TRP, the PDCCH candidate using this Coreset will not be used, which may result in lower PDCCH capacity and / or coverage. If one or more (e.g., all) Coresets correspond to a deactivated TRP, PDCCH reception is impossible. In addition, if a search space link is configured for one or more (e.g., two) search spaces, and one of the search spaces is associated with a deactivated Coreset, the WTRU will expect the same information to be transmitted through the PDCCH candidates in both search spaces, and if one of the candidates does not transmit, PDCCH reception may not be possible.

[0066] PDSCHs can fail. If the TCI state for a PDSCH corresponds to a deactivated TRP, it may become impossible to receive this PDSCH. In addition, if PDSCH repetitions are configured from a single DCI, and some of these repetitions are associated with TCI states corresponding to deactivated TRPs, the WTRU may fail to decode the PDSCH.

[0067] PUCCH can fail. If a TCI state or spatial relation configured or directed to a PUCCH corresponds to a deactivated TRP, the reception of this PUCCH may fail. Furthermore, reliability may be reduced if a PUCCH iteration is configured and some iterations are associated with TCI states or spatial relations corresponding to deactivated TRPs.

[0068] PUSCH can fail. If the TCI state or SRS resource set configured or directed to a PUSCH corresponds to a deactivated TRP, the reception of this PUSCH may fail. In addition, reliability may be reduced if PUSCH iterations are configured and some iterations are associated with TCI states or SRS resource sets corresponding to deactivated TRPs.

[0069] A WTRU may transmit or receive a physical channel or reference signal (RS) according to at least one spatial domain filter. The term “beam” may be used to refer to a spatial domain filter.

[0070] A WTRU can transmit a physical channel or signal using the same spatial domain filter used to receive an RS (e.g., CSI-RS) or SS block. The WTRU transmission can be called a “target,” and the received RS or SS block can be called a “reference” or “source.” In this example, the WTRU is transmitting a target physical channel and / or signal according to a spatial relationship with respect to such an RS and / or SS block.

[0071] The WTRU can transmit the first physical channel and / or signal according to the same spatial domain filter used to transmit the second physical channel and / or signal. The first and second transmits may be called the target and reference (reference) or source, respectively. In this example, the WTRU can be said to be transmitting the first (e.g., target) physical channel and / or signal according to the spatial relationship with respect to the second (e.g., reference) physical channel and / or signal.

[0072] Spatial relationships may be implicit, configured (set up) by the RRC, or signaled by the MAC CE or DCI. For example, a WTRU may implicitly transmit the PUSCH and / or demodulated reference signal (DM-RS) of the PUSCH according to the same spatial domain filter as the SRS indicated by the SRS resource indicator (SRI) indicated by the DCI and / or configured by the RRC. In another example, the spatial relationship may be configured by the RRC in the case of the SRI, or signaled by the MAC CE in the case of the PUSCH. Such a spatial relationship may also be called a "beam indication."

[0073] A WTRU can receive a first (e.g., target) downlink channel or signal according to the same spatial domain filter or spatial receive parameters as a second (e.g., reference) downlink channel or signal. For example, such an association can exist between a physical channel such as a PDCCH or PDSCH and its respective DM-RS. Such an association can exist, for example, when the WTRU is configured with quasi-collocation (QCL) assumption type D between corresponding antenna ports, provided that at least the first and second signals are reference signals. Such an association can be configured as a transmission configuration indicator (TCI) state. The WTRU can indicate the association between a CSI-RS or SS block and a DM-RS by indexing a set of TCI states configured by the RRC and / or signaled by the MAC CE. Such an indication is also called a "beam indication".

[0074] Unified TCI (UTCI) (e.g., Common TCI, Common Beam, Common RS, etc.) refers to a beam / RS used for multiple physical channels / signals (e.g., simultaneously). The term "TCI" may include at least a TCI state that includes at least one source RS to provide a criterion (e.g., WTRU assumption) for determining the QCL and / or spatial filter.

[0075] In one example, a WTRU may receive an indication of a first unified TCI (Transaction Control Interface) to be used / applied to both downlink control channels (PDCCHs) and downlink shared channels (PDSCHs) (e.g., and downlink RS) (e.g., from a gNB). The source reference signal in the first unified TCI can provide common QCL information for at least WTRU-dedicated receivers on PDSCHs and all (e.g., subsets thereof) of CORESETs in CC. In another example, a WTRU may receive an indication of a second unified TCI (Transaction Control Interface) to be used / applied to both uplink control channels (PUCCHs) and uplink shared channels (PUSCHs) (e.g., and uplink RS) (e.g., from a gNB). The source reference signal in the second unified TCI can provide a criterion for determining a common UL TX spatial filter for at least dynamic-grant / configuration-grant based PUSCHs and all (e.g., subsets thereof) dedicated PUCCH resources in CC.

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

[0077] For example, a WTRU could receive an indication (e.g., from a gNB) of a second unified TCI that would be used / applied in common to PDCCH, PDSCH, PUCCH and / or PUSCH (and DL RS and / or UL RS).

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

[0079] A WTRU can determine the TCI states applicable to a transmit or receive by first determining the unified TCI state instance applicable to the transmit or receive, and then determining the TCI states corresponding to the unified TCI state instance. A transmit may consist of at least PUCCH, PUSCH, and SRS. A receive may consist of PDCCH, PDSCH, and / or CSI-RS. A unified TCI state instance may also be referred to as a TCI state group, a TCI state process, a unified TCI pool, a group of TCI states, a set of time-domain instances / stamps / slots / symbols, and / or a set of frequency-domain instances / RBs / subbands, etc. A unified TCI state instance may be equivalent to, or identified by, a Coreset pool identifier (e.g., CORESETPolIndex, TRP indicator, etc.).

[0080] In this specification, the term “Unified TCI” may be used interchangeably with one or more of the following terms: “Unified TCI state,” “Unified TCI instance,” “TCI,” and “TCI-state” or “TCI state,” as is consistent with the embodiments disclosed herein.

[0081] In this specification, TCI states may consist of downlink TCI states, uplink TCI states, and / or joint downlink / uplink TCI states.

[0082] In this specification, 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 Head), “DA” (Distributed Antenna), “BS” (Base Station), “Sector” (of a BS), and / or “Cell” (e.g., Geographic Cell Area provided by a BS), as consistent with the embodiments disclosed herein. The term “Multi-TRP” may also be used interchangeably with one or more of “MTRP,” “M-TRP,” and / or “Multiple TRPs,” as consistent with the embodiments disclosed herein.

[0083] In this specification, the term “S-DCI M-TRP” may be used to refer to a scheme in which a set of transmissions (e.g., or iterations) associated with multiple TRPs are scheduled from the same DCI. When used in conjunction with an integrated TCI framework, a DCI may indicate an update to a first and / or second integrated TCI state.

[0084] In this specification, the term “M-DCI M-TRP” may be used to refer to a scheme in which a set of transmissions (e.g., or iterations) associated with multiple TRPs is scheduled from two or more DCIs. When used in conjunction with an integrated TCI framework, a DCI associated with a coresetPolIndex value may indicate an update to the integrated TCI state specific to that coresetPolIndex value.

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

[0086] DCI indications may include one or more of the following: explicit indications by DCI fields or RNTI used to mask the DCI's CRC; and / or implicit indications by properties such as DCI format, DCI size, Coreset or search space, aggregation level, and a first resource element of the received DCI (e.g., the index of a first control channel element), where the mapping between properties and values ​​may be signaled by RRC or MAC. Any signals, messages, resource allocations, and / or indications disclosed herein to be transmitted or sent by a network (e.g., gNB and / or eNB) may be transmitted via DCI and received by a WTRU.

[0087] The term "CSI" can refer to channel status information, which includes one or more of the following: channel quality index (CQI), rank indicator (RI), precoding matrix index (PMI), L1 channel measurement (e.g., RSRP such as L1-RSRP, or SINR), CSI-RS resource indicator (CRI), SS / PBCH block resource indicator (SSBRI), layer indicator (LI), and / or any other measurement measured by WTRU from a configured SSI-RS or SS / PBCH (SSB) block.

[0088] The term "UCI" can refer to uplink control information and may include CSI, HARQ feedback to one or more HARQ processes, scheduling requests (SR), link recovery requests (LRR), CG-UCI, and / or other control information bits that may be transmitted over PUCCH or PUSH.

[0089] The term "channel conditions" can refer to any conditions related to the state of the radio / channel. These may be determined by the WTRU from WTRU measurements (e.g., L1 / SINR / RSRP, CQI / MCS, channel occupancy, RSSI, power headroom, exposure headroom), L3 / mobility-based measurements (e.g., RSRP, RSRQ, s measurements), RLM status, and / or channel availability in the unlicensed spectrum (e.g., whether the channel is occupied based on LBT procedure decisions, or whether the channel is considered to have experienced a consistent LBT failure).

[0090] The term "PRACH resource" can refer to a RACH resource (e.g., in frequency), a PRACH opportunity (RO) (e.g., in time), a preamble format (e.g., in terms of total preamble duration, sequence length, guard duration and / or cyclic prefix length), and / or a specific preamble sequence used to transmit a preamble in a random access procedure.

[0091] The characteristics of scheduling information (e.g., uplink grant or downlink allocation) may include one or more of the following: frequency allocation, time allocation mode such as duration, priority, modulation and coding scheme, transport block size, number of spatial layers, number of transport blocks carried, TCI state or SRI, number of repetitions, and whether the grant is configured as grant type 1, type 2, or dynamic grant.

[0092] DCI indications or representations may include one or more of the following: explicit indications by DCI fields or RNTI used to mask the CRC of PDCCH; implicit indications by properties such as DCI format, DCI size, Coreset or search space, aggregation level, and identification of a first control channel resource for DCI (e.g., an index of the first CCE), where the mapping between properties and values ​​may be signaled by RRC or MAC; and / or explicit indications by DL MAC CE.

[0093] One or more embodiments disclosed herein may be described within the context of a unified TCI state framework for one or more TRPs, but may also be applicable to non-unified TCI state frameworks.

[0094] A WTRU can use a group of TCI states to determine the set of applicable TCI states. For example, a WTRU can efficiently address TCI states (e.g., beams) when a network modifies a subset of active (e.g., or inactive) TRPs within a set of TRPs. Figure 2 shows an example of a WTRU that uses a group of TCI states to determine the set of applicable TCI states.

[0095] A WTRU can receive RRC configurations for a set of TCI states (e.g., each) identified by a TCI state identity. For example, an RRC configuration can be associated with a TCI state, and one or more of these (e.g., each) can be associated with a respective TCI state identity.

[0096] A WTRU can receive a first signaling (e.g., MAC CE) that associates one or more TCI state groups (e.g., A, B, C) with a TCI state identity for each of the values ​​of a TCI indicator (e.g., 3 bits) (e.g., code point "2" corresponds to TCI state identities 2, 9, and 15 for TCI state groups A, B, and C, respectively). For example, the first signaling (e.g., the first message) may indicate the respective associations between a TCI state group and a TCI state identity for one or more of the multiple TCI indicators (e.g., each of them).

[0097] 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., first TRP) and / or a TCI state group applicable to a second TCI state (e.g., second TRP), a TCI state group applicable to (e.g., 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., M-DCI M-TRP). For example, the second signaling (e.g., 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 the table associated with the index (which may be constructed by, for example, RRC signaling). The table contains one or more entries indicating whether each TCI state group is activated or deactivated. For each entry indicating that each TCI state group is activated, the WTRU can determine one or more TCI states associated with each TCI state group.

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

[0099] A WTRU may receive a (third) signaling (e.g., DCI) that includes a TCI indicator (e.g., DCI scheduling / activation PDSCH or PUSCH). For example, the third signaling (e.g., the third message) may indicate a TCI indicator among several TCI indicators.

[0100] The WTRU can update the first and / or second TCI states to TCI states (e.g., an activated subset of TCI states) that correspond to a group of TCI states applicable to the value of the TCI indicator received in the third message according to the first signaling. Here, the TCI indicator can indicate whether only 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., S-DCI M-TRP).

[0101] The WTRU can determine an applicable CoresetPoolIndex value from a third signaling (DCI) (for example, based on the Coreset of the decoded PDCCH), determine the TCI state group associated with the CoresetPoolIndex from the second signaling, and / or update the TCI state for the applicable CoresetPoolIndex (for example, for M-DCI M-TRP) based on the TCI indicator value and the TCI state group associated with the CoresetPoolIndex.

[0102] The WTRU can use an updated subset of TCI states to perform one or more of the following: uplink transmissions (e.g., PDCCH monitoring, PSCH 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 fault detection).

[0103] The TCI state can be DL TCI state, UL TCI state, and / or joint DL / UL TCI state.

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

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

[0106] The MAC CE may also indicate, for at least one value of a TCI code point (e.g., each of them), whether the WTRU updates the first unified TCI state, the second unified TCI state, or both the first and second unified TCI states for at least S-DCI M-TRP operation upon receiving a DCI that includes a TCI indicator field having this value of the TCI code point.

[0107] (For example, the same) MAC CE can also indicate the CoresetPoolIndex value associated with the indicated TCI state, at least for M-DCI M-TRP operation.

[0108] A WTRU may receive one or more MAC CEs, each of which may indicate an association between a TCI code point and a TCI state specific to a TCI state group. For example, a WTRU may receive a first MAC CE indicating the identification of a first TCI state group and at least one TCI state identification and possibly an associated TCI code point. The WTRU may then receive a second MAC CE indicating the identification of a second TCI state group and at least one TCI state identification and an associated TCI code point.

[0109] Associations may be performed by RRC. WTRUs can associate TCI state groups with TCI states based on the RRC configuration. Associations can be explicitly indicated. For example, a TCI state group identifier may be indicated as part of the TCI state configuration. Such an indication may consist of existing “additional PCI” information elements (e.g., if the reference signal is SSB) or new information elements. If no “additional PCI” information elements exist, the indication may correspond to the PCI of the serving cell. Associations can be implicitly determined from linked TCI states. For example, a first reference signal (such as CSI-RS) may be included as part of the configuration of a first TCI state. A second TCI state may 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 may be the TCI state group identifier of the second TCI state.

[0110] 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 and / or identify the associated TCI states in a manner applicable to scheduling, as described herein.

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

[0112] For example, an indication could consist of 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 activated or deactivated. In another example, a WTRU could receive signaling indicating whether a particular TCI state group (e.g., a single one) is activated or deactivated.

[0113] The indication can consist of an index that references a table, where each entry in the table can indicate whether each TCI state group is activated or deactivated. Such a table can be configured (set up) by RRC signaling. The table can also be predefined for each possible number of configured TCI state groups.

[0114] A WTRU group common PDCCH may be used. Signaling may be included in MAC CE or DCI. DCI may be from a PDCCH received in the WTRU group common search space. In this case, the WTRU may first receive the configuration (setting) of bit positions in the DCI for (for example) each TCI state group.

[0115] Cell / TRP DTX / DRX activation / deactivation may be performed. A WTRU may monitor a WTRU group common PDCCH for cell DTX / DRX activation of at least one cell or TRP. When a WTRU receives a PDCCH indicating that a cell DTX and / or DRX is being activated (e.g., or deactivated) for a cell or TRP, it may deactivate (e.g., or activate) the TCI state group associated with the cell or TRP. Deactivation or activation may apply to downlink reception in the case of cell DTX and to uplink transmission in the case of cell DRX. The association between a TCI state group and a cell or TRP may be explicitly configured by the RRC or may be based on the physical cell identification (PCI) used to generate the SSB of the cell or TRP. For example, if a WTRU receives a PDCCH indicating DTX / DRX activation for a cell using a particular PCI, the WTRU may deactivate the TCI state group corresponding to this PCI (e.g., for TCI states configured with additional PCIs set on this PCI). Activation / deactivation of the TCI state group upon reception of cell DTX / DRX indication may occur only if the PCI is not the PCI of the WTRU serving cell (for example, only).

[0116] WTRU-specific PDCCHs may be used. The DCI may be from a PDCCH received in a WTRU-specific search space, such as a DCI that schedules a PDSCH or PUSCH, activates a semi-permanently scheduled PDSCH, activates a PUSCH by configured grant type 2, or a DCI format 1_1 or 1_2 without downlink assignment. Indications may be in a new field of the DCI. For example, when operating an M-TRP with an M-DCI, a field of the DCI may indicate an activated TCI state group associated with the CoresetPoolIndex of the PDCCH from which the DCI is decoded. In another example, when operating an M-TRP with an S-DCI, a field (e.g., one or two fields) may indicate one or more (e.g., two) activated TCI state groups associated with a first and second unified TCI state.

[0117] There may be a maximum number of TCI state groups that can be activated. A WTRU may consist of a maximum number of activated TCI state groups, for example, 1(1) (e.g., not configured for M-TRP operation (e.g., single TRP)) or 2(2) or more (e.g., configured for M-TRP operation). If a WTRU receives a signaling that the number of activated TCI state groups exceeds the maximum value, the WTRU may activate TCI state groups based on priority. 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 a signaling (e.g., WTRU group common PDCCH) indicates that TCI state groups A, B, and C should be activated, but the maximum number of TCI state groups to be activated is 2, the WTRU may activate TCI state groups A and B (e.g., only A and B) and deactivate TCI state group C.

[0118] An association may be made between a TCI state group and a CoresetPolIndex or a first / second unified TCI state for M-TRP. Signaling may further indicate an association between the activated TCI state group and a CoresetPolIndex value to support M-DCI M-TRP operation, or between the activated TCI state group and a first or second unified TCI state to support S-DCI M-TRP operation.

[0119] Signaling can explicitly indicate associations. For example, signaling can indicate a first activated TCI state group associated with a first value of CoresetPolIndex (e.g., or a first unified TCI state), and a second activated TCI state group associated with a second value of CoresetPolIndex (e.g., or a second unified TCI state). For example, MAC CE or DCI may include first and second fields corresponding to the first and second values ​​of CoresetPoolIndex (e.g., or unified TCI states), respectively. WTRU can activate the indicated TCI state groups and deactivate TCI state groups not included in the signaling.

[0120] Alternatively, WTRU can implicitly determine associations based on the activation state of each TCI state group and the priority defined across the TCI state groups. If a second activated TCI state group exists, WTRU may associate the TCI state group with the highest priority among the activated TCI state groups with the first value of CoresetPolIndex (e.g., the first unified TCI state), and the TCI state group with the second highest priority among the activated TCI state groups with the second value of CoresetPoolIndex (e.g., the second unified TCI state). 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. In scenarios where TCI state groups A and C are activated, the WTRU may associate TCI state group A with the first value of CoresetPolIndex (e.g., or the first unified TCI state) and TCI state group C with the second value of CoresetPolIndex (e.g., or the second unified TCI state). In scenarios where TCI state groups B and C are activated, the WTRU may associate TCI state group B with the first value of CoresetPolIndex (e.g., or the first unified TCI state) and TCI state group C with the second value of CoresetPolIndex (e.g., or the second unified TCI state).

[0121] Alternatively, the WTRU can implicitly determine the association from the CoresetPoolIndex of the Coreset from which the PDCCH carrying the DCI is decoded. For example, when operating an M-TRP with an M-DCI, the DCI's fields may indicate the activated TCI state group associated with the CoresetPoolIndex of the PDCCH from which the DCI is decoded.

[0122] A default TCI state group may be used. The WTRU can 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 the default TCI states defined in an existing system; a TCI state group corresponding to the PCI of a service cell; or a TCI state group 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).

[0123] The WTRU can activate a default TCI state group if the signaling indicates that the TCI state group will not be activated. In M-TRP operation, the WTRU can determine the default TCI state group for the CoresetPoolIndex value (e.g., each one) or for the first and / or second unified TCI state (e.g., each one).

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

[0125] In the first solution, if an association between the TCI state group to which signaling is activated and the first CoresetPoolIndex value is not provided, the WTRU can associate the default TCI state group with the first CoresetPoolIndex value. Alternatively, if the active TCI state group is associated with the second CoresetPoolIndex value, the WTRU can associate this TCI state group with the first CoresetPoolIndex value. Alternatively, the transmit and / or receive associated with the first CoresetPoolIndex value may not be supported.

[0126] In the second solution, if signaling does not provide an association between the activated TCI state group and the first (e.g., or second) unified TCI state, the WTRU may associate the default TCI state group with the first (e.g., or second) unified TCI state. Alternatively, if the activated TCI state group is associated with the 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, transmits or receives associated with the first (e.g., or second) unified TCI state may not be supported.

[0127] Activation / deactivation of TCI states corresponding to TCI state groups may be performed. Upon receiving a signaling that activates (e.g., deactivates) a TCI state group, the WTRU may activate (e.g., deactivate) the TCI states associated with the TCI state group and begin (e.g., stop) monitoring the corresponding reference signal. After a certain period following the receipt of a signaling indicating a change in the activated TCI state group, the WTRU may interpret subsequent DCIs according to the indicated activated TCI state group. This period may be predefined and / or received via the signaling.

[0128] The indication and application / update of TCI status may be performed. The WTRU may receive signaling that indicates and updates at least one (e.g., unified) TCI status for transmission and / or reception, including, for example, PDCCH, PDSCH, PUCCH, PUSCH, SRS and / or CSI-RS. Such signaling may also modify resources applicable to beam fault detection and recovery. The signaling may consist of a DCI decoded from a PDCCH received in a WTRU-specific search space, such as a DCI that schedules a PDSCH or PUSCH, activates a semi-permanently scheduled PDSCH, and activates a PUSCH by a configured grant type 2, or a DCI format 1_1 or 1_2 without downlink allocation. Such a DCI may include a TCI status indicator that updates at least one unified TCI status.

[0129] For a single TRP operation, the WTRU can determine a single unified TCI state. The WTRU can determine the initially activated TCI state group. The WTRU can determine the unified TCI state identification to update by looking up the TCI state identifications of the activated TCI state group and TCI code points contained in the DCI.

[0130] In the case of M-DCI M-TRP operation, the WTRU can determine a unified TCI state associated with the CoresetPoolIndex value corresponding to the DCI. The CoresetPoolIndex value may be a value configured for the Coreset into which the PDCCH containing the DCI is decoded. The WTRU can first determine the TCI state group associated with the CoresetPoolIndex value based on signaling (for example, as described herein). The WTRU can then determine the identification of a unified TCI state for updating the TCI state identification of the TCI state group and TCI code point contained in the DCI by looking up.

[0131] In S-DCI M-TRP operation, the WTRU can update the first and / or second unified TCI states. The WTRU can determine whether to update the first unified TCI state, the second unified TCI state, or both the first and second unified TCI states, based, for example, on the TCI code point values ​​and the mapping signaled by MAC CE (as described herein, for example). The WTRU can determine the first (e.g., or second) TCI state group associated with the first (e.g., or second) unified TCI state based on the signaling (as described herein, for example). The WTRU can then determine the identification of the first (e.g., or second) unified TCI state for updating by looking up the TCI state identification for the first (e.g., or second) TCI state group and TCI code point included in the DCI. A single TRP, M-DCI M-TRP, and / or S-DCI M-TRP may be used simultaneously and / or separately for a given WTRU.

[0132] After determining and / or updating the identification of unified TCI states, the WTRU can use these unified TCI states 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 timing, SRS transmission, (e.g., aperiodic) CSI-RS reception, and / or beam fault detection.

[0133] TRP DTX / DRX may be provided. A gNB can reduce downlink transmit / uplink receive activity from a given TRP, with or without explicit signaling of the TRP DTX / DRX pattern. TRP DTX / DRX may be used to inform a WTRU whether a given TRP is inactive or remains active. During TRP DTX / DRX, the TRP may have no transmit / receive, or maintain limited transmit / receive (e.g., common signals and channels received by legacy WTRUs or during idle / inactive modes). For example, the TRP may transmit or receive some periodic signals / channels, such as common channels / signals and / or WTRU-specific signals or channels, or not.

[0134] TRP DTX / DRX can be applied to at least WTRUs in the RRC_CONNECTED state. Periodic TRP DTX / DRX (e.g., active and inactive periods) can be configured by gNBs via WTRU-specific RRC signaling per serving cell. TRP DTX / DRX modes can be activated / deactivated via dynamic L1 signaling (e.g., similar to the signaling 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 may be configured and operated separately (e.g., one RRC configuration set up for DL ​​and another RRC configuration set up for UL). TRP DTX / DRX can also be configured and operated together. At least the following parameters may be configured for each TRP DTX / DRX configuration: periodicity, start slot / offset, and / or on-duration. TRP DTX indication may also be part of SI update or SIB signaling. There may be a common time for one or more (e.g., all) WTRUs to determine the TRP DTX status.

[0135] For each TRP DTX and / or TRP DRX configuration and / or subconfiguration, the WTRU can be predefined or configured using one or more of the following parameters and behaviors: one or more beam or spatial relationships applied when the TRP DTX / DRX is activated versus deactivated; one or more applicable configured grant (CG) or semi-persistent scheduling (SPS) configurations; whether the WTRU should monitor PDCCH at a given Coreset, search space, or aggregate level when the TRP DRX / DTX is activated versus deactivated (e.g., dynamic grant, dynamic DL assignment, or other DL signaling including PS-RNTI, PDCCH skip display, or DCI with scrambled CRC) and / or during TRP DTX inactivity; whether to monitor a given reference signal from a given TRP (e.g., during inactivity) when the TRP DTX is activated, including BFD, RLM, and / or CSI-RS reference signals; TRP PRACH resources or PRACH resource configurations applicable or not applicable during the DRX inactive period, or when the cell DRX configuration is activated; SR / PUCCH resources or SR / PUCCH resource configurations applicable or not applicable during the TRP DRX inactive period, or when the TRP DRX configuration is activated; WTRUs may be transmitted with configured authorizations (e.g., only) when the corresponding SRS resource is TRP off or does not support TRP DRX; CSI reporting or CSI reporting resource configurations applicable or not applicable during the TRP DRX inactive period, or when the TRP DRX configuration is activated; and / or; SRS resources or SRS resource configurations applicable or not applicable during the TRP DRX inactive period, or when the TRP DRX configuration is activated.

[0136] WTRUs can be predefined or configured for each TRP DTX configuration and / or TRP DRX configuration and / or subconfiguration, using PRACH resources or PRACH resource configurations that are applicable or not applicable during TRP DRX inactivity periods, or when the TRP DRX configuration is activated. For example, a particular PRACH resource can be associated with a given TRP, and when such a TRP is activated, the WTRU is expected to refrain from sending PRACHs on such PRACH resources.

[0137] WTRUs can be predefined or configured for each TRP DTX configuration and / or TRP DRX configuration and / or subconfiguration, using SR / PUCCH resources or SR / PUCCH resource configurations, which may or may not be applicable during periods of TRP DRX inactivity, or when the TRP DRX configuration is activated. A subset of SR configurations or PUCCH resources can be associated with a given TRP, and when such a TRP activates TRP DRX, the WTRU may refrain from sending PUCCHs to such TRP.

[0138] WTRUs can be predefined or configured per TRP DTX configuration and / or per TRP DRX configuration and / or per subconfiguration, using CSI reporting or CSI reporting resource configurations, which may or may not be applicable during TRP DRX inactivity periods, or when the TRP DRX configuration is activated. WTRUs can suspend CSI feedback related to TRPoff or TRP DRX.

[0139] WTRUs can be predefined or configured per TRP DTX configuration and / or per TRP DRX configuration and / or per subconfiguration using SR / PUCCH resources or SR / PUCCH resource configurations, applicable or not applicable during TRP DRX inactivity periods, or when the TRP DRX configuration is activated. WTRUs can refrain from transmitting SRS when the TRP is powered off or in TRP DRX mode. WTRUs can be configured using secondary SRS resources configured for use when the TRP is in TRP DRX mode, when it is turned off or muted.

[0140] A WTRU may consist of a primary TRP and / or a secondary TRP. A WTRU may assume that TRP DRX / DTX is applicable only to the secondary TRP (e.g., only). Signaling to activate TRP DRX / DTX may indicate a given TRP index (e.g., by DCI indication, according to the signaling method described herein). A WTRU may consist of stable TRP classifications versus unstable TRP classifications, thereby preventing stable TRPs from being turned off or TRP DRX / DTX from being applied. A WTRU may not monitor TRP mute signaling or DTX / DRX activation signaling for stable TRPs. A WTRU may monitor TRP DTX / DRX activation signaling (e.g., including the signaling described herein) on specific occasions, for example, periodically.

[0141] When a given TRP activates 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 the TRP to which DTX is applied or turned off. A WTRU can be configured in associations between TRPs (e.g., from a stable TRP association to an unstable TRP association) so that if an unstable TRP is muted or turned off, the WTRU can fall back to a stable TRP. A WTRU can anticipate changes in the Coreset / search space periodicity of a TRP (e.g., a stable TRP) when another TRP (e.g., an associated TRP) is off. A WTRU can be configured in a conditional search space and / or Coreset and monitored on a given TRP (e.g., a stable TRP) when another TRP (e.g., an associated TRP) turns off, mutes, activates, or during periods of inactivity of the TRP DTX.

[0142] For example, each Coreset can be associated with a coresetpoolindex and TCI state corresponding to a TRP. WTRUs may not need to monitor the search space corresponding to a TRP's TCI state / coresetPoolIndex during DTX inactivity periods or when a TRP is muted or turned off. WTRUs can modify PDCCH monitoring rules for additional monitoring on TRPs that remain on (e.g., TRPs associated with stable or muted TRPs). Turning off or activating a TRP DTX can indicate whether a muted TRP will not monitor other TRPs along with its TRP index for a timer period (e.g., consisting of a configured DTX inactivity period and either indicated or inferred).

[0143] WTRU can be configured and / or associated with a secondary TCI state (e.g., or a fallback to another integrated TCI) to be used when the primary TCI state corresponds to TRP off or TRP DTX, and / or when the primary TRP is in an inactive period.

[0144] The WTRU can determine from system information whether a subset of the cell's TRPs are muted, turned off, or whether DTX is activated. For channel measurement purposes (e.g., for cell selection, reselection, and / or connection mode mobility purposes), the WTRU may omit signals from such TRPs.

[0145] WTRU can dynamically switch to monitoring different CSI-RS and / or SSB resource sets when TRP activates or deactivates TRP DRX.

[0146] When a subset of TRPs is in DTX, off mode, or muted, the WTRU may omit the path loss references associated with such TRPs for the purpose of path loss calculation.

[0147] Adaptation of TRP antenna ports and / or elements can be performed. A WTRU can assume that a subset of antenna ports and / or elements on a given TRP are muted as a function of the signaling cell spatial domain NES subconfiguration applied and / or signaled. A WTRU can consist of spatial domain subconfigurations / hypotheses per TRP. Thereafter, the association of which TRPs are muted and / or reducing the number of their ports / elements is inferred from the indicated spatial domain subconfigurations / hypotheses associated with the TRPs by the RRC configuration. A WTRU can receive cell spatial domain subconfigurations / hypotheses and apply them to subsets of TRPs. Thereafter, TRP subsets can be inferred from separately indicated and / or subconfiguration indices (as described herein, for example).

[0148] WTRU can assume that a given TRP is turned off / muted / TRP DTX is active upon receiving an indication associated with a spatial domain subconfiguration / hypothesis associated with the TRP.

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

[0150] The WTRU can implicitly infer BFD, CSI, and / or RLM signals to monitor from the indicated TCI state of each Coreset (as described herein, for example). The WTRU can trigger a BFD (e.g., only) if a BFD is detected only for one or more (e.g., all) TRPs of a cell, one or more (e.g., all) TRPs of the same cell index, one or more (e.g., all) stable TRPs, and / or stable TRPs (e.g., those not employing the NES method). The WTRU can suspend beam fault detection for BFD-RS resources corresponding to TRP off (e.g., suspend RLM for RLM-RS). The WTRU can suspend beam fault detection for BFD-RS resources corresponding to TRP off (e.g., suspend RLM for RLM-RS). If (e.g., one) TRP mutes, turns off, or applies TRP DTX, the WTRU can use the resources of an alternative TRP for BFD, RLM.

[0151] The processes and means described herein can be applied in any combination, to other wireless technologies, and to other services. WTRUs may refer to physical device identification or subscription-related identification, such as user identification like MSISDN or SIP URI. WTRUs may refer to application-based identification, such as usernames that may be used on an application-by-application basis.

[0152] A WTRU can refer to the physical device's identity, such as subscriber relationship identification like MSISDN or SIP URI. A WTRU can also refer to application-based identification, such as a username used for each application.

[0153] Furthermore, the methods provided herein may be implemented in computer programs, software, or firmware embedded in computer-readable media for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital multi-purpose disks (DVDs). A software-related processor may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A wireless transceiver unit (WTRU), The network receives a Radio Resource Control (RRC) configuration associated with one or more Transmit Configuration Indicator (TCI) states, each of which is associated with its respective TCI state identifier. From the aforementioned network, a first message is received indicating the respective association between the TCI state group and the TCI state identifier for each of the multiple TCI indicators. A second message indicating one or more TCI state groups is received from the aforementioned network. Determine a subset of one or more TCI states, and each TCI state in the subset of the one or more TCI states is associated with a TCI state identifier shown in the first message and a group of one or more TCI states shown in the second message. Activate each of the subsets of the one or more TCI states, A third message is received from the network, indicating a TCI indicator among the plurality of TCI indicators. Based on the TCI indicator received in the third message, update the activated subset of the one or more TCI states. Using one or more of the updated subsets of the one or more TCI states, perform at least one uplink transmit, downlink transmit, or measurement. Processor configured in such a way WTRU equipped with.

2. The aforementioned processor, It is determined that the second message does not indicate one or more TCI state groups. A second subset of the one or more TCI states is determined, and each TCI state in the second subset of the one or more TCI states is associated with a TCI state identifier shown in the first message and one or more TCI state groups shown in the second message. Deactivate each of the second subsets of the one or more TCI states. A further configured WTRU according to claim 1.

3. The aforementioned processor, Determine the default TCI state group, The TCI status group was determined to be not activated. Activate the default TCI state group. A further configured WTRU according to claim 1.

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

5. The aforementioned processor, The WTRU of claim 4, further configured to receive the second message via one or more second MAC CEs or one or more Dynelink Control Information (DCIs).

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

7. The processor, configured to perform at least one uplink transmit, downlink transmit, or measure using one or more updated subsets of the one or more TCI states, Transmits a physical downlink control channel (PDCCH), Receive downlink transmissions on a physical downlink shared channel (PDSCH). On the physical uplink control channel (PUCCH), an uplink transmission is sent. Perform a sounding reference signal (SRS) transmission. Upon receiving a Channel Status Information Reference Signal (CSI-RS) transmission, or Detecting beam interference A WTRU in any one of claims 1 to 6, further comprising the processor configured to perform at least one of the following.

8. The second message is a WTRU of any one of claims 1 to 7, which includes a bitmap.

9. The second message mentioned above includes an index, The processor, configured to determine one or more subsets of TCI states, Determine the table associated with the aforementioned index, the table containing one or more entries, each entry indicating whether the respective TCI state group is activated or deactivated. For each entry indicating that each TCI state group is activated, determine one or more TCI states associated with each TCI state group. A WTRU, any one of claims 1 to 8, further comprising the processor configured as described above.

10. The table associated with the index is configured by wireless resource control (RRC) signaling in the WTRU of claim 9.

11. A method implemented by a wireless transceiver unit (WTRU), A step of receiving a radio resource control (RRC) configuration from a network, associated with one or more transmit configuration indicator (TCI) states, each of which TCIs is associated with its respective TCI state identifier. From the aforementioned network, a first message is received indicating the respective association between the TCI state group and the TCI state identifier for each of the multiple TCI indicators. The steps include receiving a second message from the aforementioned network that indicates one or more TCI state groups, A step of determining a subset of one or more TCI states, wherein each TCI state of the subset of the one or more TCI states is associated with a TCI state identifier shown in the first message and one or more TCI state groups shown in the second message. The steps include activating each of the subsets of the one or more TCI states, The steps include receiving a third message from the network indicating a TCI indicator among the plurality of TCI indicators, The steps of updating the activated subset of one or more TCI states based on the TCI indicator received in the third message, The steps include performing at least one uplink transmission, downlink transmission, or measurement using one or more of the updated subsets of the one or more TCI states. A method for providing this.

12. The step of determining that the second message does not indicate one or more TCI state groups, A step of determining 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 shown in the first message and the one or more TCI state groups shown in the second message. The steps of deactivating each of the second subsets of the one or more TCI states and The method of claim 11, further comprising the above.

13. The steps include determining the default TCI state group, The step of determining that the TCI status group is not activated, The steps of activating the default TCI state group and The method of claim 11 or 12, further comprising the above.

14. The method according to 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 according to any one of claims 11 to 13, wherein the second message is received via one or more second MAC CEs or one or more Dynelink control information (DCIs).

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

17. The step of performing at least one uplink transmission, downlink transmission, or measurement using one or more of the updated subsets of the one or more TCI states is: Transmitting a physical downlink control channel (PDCCH), Receiving downlink transmissions on a physical downlink shared channel (PDSCH), Transmitting an uplink transmission over the physical uplink control channel (PUCCH), Performing a sounding reference signal (SRS) transmission, Receiving a Channel Status Information Reference Signal (CSI-RS) transmission, or Detecting beam interference A method of any one of claims 11 to 16, comprising the step of performing at least one of the following.

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

19. The second message mentioned above includes an index, step of determining a subset of one or more TCI states Determine the table associated with the aforementioned index, the table containing one or more entries, each entry indicating whether the respective TCI state group is activated or deactivated. For each entry indicating that each TCI state group is activated, determine one or more TCI states associated with each TCI state group. A method of any one of claims 11 to 18, including the method of any one of claims.

20. The method of claim 19, wherein the table associated with the index is configured by radio resource control (RRC) signaling.

Images