RU2755825C1 - Beam indication for new 5g radio communication technology - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: invention relates to the field of wireless communication. The WTRU can receive information about the configuration of the probing Sounding Reference Signal (SRS). The WTRU can also receive beam indication information (ID) and panel ID information in the downlink control information (DCI) and determine the WTRU panel based on panel ID information or resource configuration information SRS.

EFFECT: ability to determine the swing of the uplink beam (UL) for each specific panel of the WTRU wireless transmission/reception unit based on the beam identifier using one or more swing parameters.

15 cl, 30 dwg

Description

Cross-references to related claims

This application claims advantage of Provisional U.S. Patent Application No. 62/753,679 filed October 31, 2018, U.S. Provisional Patent Application No. 62/716,044 filed August 8, 2018, and U.S. Provisional Patent Application No. 62/652 700, filed April 4, 2018, the contents of which are incorporated herein by reference.

Background of the invention

For mobile communications, downlink (DL) beam steering (BM) may be used. Beam mapping can also be configured as the capability of a wireless transmit / receive unit (WTRU) in new radio technology (NR), 5 G, and the like. The WTRU may determine a transmit (TX) beam based on a determined receive (RX) beam from the DL BM. An uplink (UL) BM may be unnecessary when optimal or ideal beam matching is met at both the TRP and the WTRU.

For imperfect WTRU beam matching, full or wide beam sweep may be used to determine the optimal or best UL TX beam from all or most of the WTRU TX beams. However, using full beam sweep can be ineffective for UL BMs due to the large heading to prepare. Preparation may be undesirable due to high latency, high power consumption, extra processing time, etc. Partial or local beam sweeping can be used as fewer resources may be required to prepare adjacent beams. However, partial or local wobbling of the beam can also sometimes be insufficient or undesirable.

Summary of the invention

Probing Reference Signal Beam Pointing (SRS) for uplink (UL) beam steering or beam sweeping, Beam Pointing for Multiple Bandwidth Portions (BWP), or Beam Pointing for Multiple Transceiver Points (TRP) can be configured to efficiently indicate a low beam beam. delay. The beam indication for a plurality of BWPs may further include a beam indication for a plurality of downlink (DL) BWPs, a beam indication for a plurality of UL BWPs, a beam indication for UL and DL BWPs, and the like.

A wireless transmit / receive unit (WTRU) may also be configured to receive an SRS configuration message indicating spatial relationship information for each SRS resource from a plurality of SRS resources. The WTRU may determine at least a spatial domain transmit filter or UL beam (s) for each SRS resource based on the spatial relationship information associated with each SRS resource, and transmit each SRS resource using a specific spatial domain transmit filter or a specific UL beam (s). The WTRU may also receive configuration information for at least one of a plurality of DL BWPs or a plurality of UL BWPs.

The WTRU may be configured to independently or jointly specify a beam for multiple TRPs. For independent beam indication, the WTRU may receive configuration information including SRS beam indication from multiple TRPs, and transmit it using the SRS resource to each of the plurality of TRPs on associated UL beam (s) based on the received configuration. For joint beam designation, the WTRU may receive configuration information from the master TRP, which includes the SRS beam designation for the master and multiple TRPs. The WTRU may transmit data using the SRS resource to each of the plurality of TRPs on the associated UL beam (s) based on the received configuration information.

Brief description of graphic materials

A more detailed explanation is provided in the following description, given by way of example, in conjunction with the accompanying drawings, in which like reference numbers in the figures indicate like elements.

FIG. 1A is a system diagram illustrating an example of a communication system in which one or more of the described embodiments may be implemented.

FIG. 1B is a system diagram illustrating an example of a wireless transmit / receive unit (WTRU) that may be used in the communication system of FIG. 1A, in accordance with an embodiment.

FIG. 1C is a system diagram illustrating an example of a radio access network (RAN) and an example of a core network (CN) that may be used in the communication system shown in FIG. 1A, in accordance with an embodiment.

FIG. 1D is a system diagram illustrating a further RAN example and a further CN example that may be used in the communication system of FIG. 1A, in accordance with an embodiment.

FIG. 2 depicts an example of a WTRU transceiver point (TRP) and antenna model.

FIG. 3 is a table showing examples of basic massive antenna configurations for dense urban areas and urban macro areas.

FIG. 4 shows an example of full swing and local swing for Procedure U-3.

FIG. 5 is a table showing examples of spatial relationships between downlink reference signal (s) (RS) and uplink sounding reference signal (s) (SRS) ( UL) for transmitting (TX) beam (s).

FIG. 6 shows an example of signaling for beam steering (BM).

FIG. 7 shows another example of signaling for a BM.

FIG. 8 shows another example of signaling for a BM.

FIG. 9 shows an example of Downlink Control Information (DCI) / Transmission Configuration Indicator (TCI) for beam indication for multiple DL BWP portions.

FIG. 10 is a table showing examples of TCI beam indication for multiple DL BWPs.

FIG. 11 is a table showing examples of hybrid beam designation for multiple DL BWPs.

FIG. 12 illustrates an example of using DCI or TCI to indicate an SRS beam for BM in multiple UL BWPs.

FIG. 13 is a table showing configuration examples based on the TCI table for specifying a beam for a plurality of DL and UL BWPs.

FIG. 14 is a table with examples of the relationship of the SRS resource with the transmit filter in the spatial domain.

FIG. 15 depicts an example of a WTRU U-3 wobble range.

FIG. 16 depicts another example of a WTRU U-3 wobble range.

FIG. 17 depicts an example of an implicit procedure for determining the swing range of a WTRU U-3.

FIG. 18 depicts an example procedure for a WTRU to determine wobble beam (s) for triggered SRS resources for BM UL.

FIG. 19 depicts an example of optimal WTRU beam indication (s).

FIG. 20 depicts another example of optimal WTRU beam indication (s).

FIG. 21 depicts another example of optimal WTRU beam indication (s).

FIG. 22 depicts an example of independent physical uplink shared channel (PUSCH) beam designation and PUSCH shared beam designation.

FIG. 23 shows an example of a communication specific to an SRS panel.

FIG. 24 illustrates an example of beam indication based on SRS resource association for PUSCH transmission.

FIG. 25 shows an example of using TCI states to indicate a beam for a Physical Uplink Control Channel (PUCCH) or PUSCH.

FIG. 26 is a table showing examples of TCI entries for beam indication for PUCCH or PUSCH with reference to FIG. 25; and

in fig. 27 shows a procedure for defining triggered WTRUs and beams for UL BMs.

Detailed description

FIG. 1A is a diagram illustrating an example of a communication system 100 in which one or more of the described embodiments may be implemented. Communication system 100 may be a multiple access system from which multiple wireless communication users obtain content such as voice, data, video, messaging, broadcast, and the like. Communication system 100 may be configured to provide multiple wireless communication users with access to such content by sharing system resources, including the bandwidth of the wireless connection. For example, communication system 100 may utilize one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), multiple access orthogonal frequency division multiplexing (OFDMA), single carrier FDMA (SC-FDMA), extended OFDM with non-redundant extended discrete Fourier transform with sync burst (ZT-UW-DFT-s-OFDM), OFDM with sync burst (UW-OFDM), OFDM with resource block filtering, multi-carrier filterbank (FBMC), etc.

As shown in FIG. 1A, communication system 100 may include wireless transmit / receive units (WTRU) 102a, 102b, 102c, 102d, radio access network (RAN) 104, core network (CN) 106, public switched telephone network (PSTN) 108, network 110 Internet and other networks 112, although it should be understood that the described embodiments assume any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device capable of operating and / or interoperating in a wireless communication environment. For example, WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and / or receive radio signals and may include a user equipment (UE), a user terminal (UT), mobile station, fixed or mobile subscriber module, subscriber module, pager, cell phone, personal digital assistant (PDA), smartphone, laptop, netbook, personal computer, wireless sensor, access point or Wi-Fi device, Internet device of physical objects (IoT ), a watch or other wearable device, a head-mounted display (HMD), a vehicle, an unmanned radio-controlled aerial vehicle, a medical device and applications (such as those used in remote surgery), an industrial device and applications (such as robotic and / or other wireless devices operating in an industrial and / or automated process chain), a device, consumer electronics, commercial and / or industrial wireless network device, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

Communication system 100 may also include base station 114a and / or base station 114b. Each of the base stations 114a, 114b may be any type of device capable of wireless communication with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as CN 106, the Internet 110 and / or other networks 112. As an example, base stations 114a, 114b may be base transceiver stations (BTSs), Node-B stations, eNode B station, Home Node B station, Home eNode B station, Node B next generation station (gNB), NodeB based on new radio access technology (NR), transceiver point (TRP), point controller, access point (AP), wireless router, etc. While each of base stations 114a, 114b is shown as a separate element, it should be understood that base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, base station 114a in RAN 104 and WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Terrestrial Access (UTRA) for Universal Mobile Telecommunications System (UMTS) in which a radio interface 116 may be installed using broadband CDMA (W-CDMA). Wideband Code Division Multiple Access (W-CDMA) technology can include communication protocols such as High Speed Packet Access (HSPA) and / or Enhanced HSPA (HSPA +). The HSPA protocol may include high speed downlink (DL) packet access (HSDPA) and / or high speed uplink (UL) packet access (HSUPA).

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as a next generation UMTS terrestrial radio access network (E-UTRA) that can establish a radio interface 116 using the Long Term Evolution (LTE) standard. , and / or LTE-Advanced (LTE-A), and / or LTE-Advanced Pro (LTE-A Pro).

In one embodiment, using base station 114a and WTRUs 102a, 102b, 102c, a radio technology such as NR Radio Access can be implemented that can provide a radio interface 116 using NR technology.

In an embodiment, a variety of radio access technologies may be implemented in base station 114a and WTRUs 102a, 102b, 102c. For example, a combination of base station 114a and WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access, for example, using two-way communication (DC) principles. Thus, the radio interface used by the WTRU 102a, 102b, 102c can be characterized by the use of many types of radio access technologies and / or transmissions sent to / from base stations belonging to many types (eg, eNB and gNB).

In other embodiments, base station 114a and WTRU 102a, 102b, 102c may implement radio technologies such as Institute of Electrical and Electronics Engineers IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), IEEE 802.16 (i.e. global compatibility for microwave access (WiMAX)), cdma2000, cdma2000 1X, cdma2000 EV-DO, interim 2000 (IS-2000), interim 95 (IS-95), interim 856 (IS-856), global system for mobile communication (GSM), development of the GSM standard with increased data transfer rate (EDGE), GSM EDGE (GERAN), etc.

Base station 114b shown in FIG. 1A can be, for example, a wireless router, Home Node B, Home eNode B, or access point, and can use any suitable RAT to facilitate wireless communication in a localized area such as a business, residential, transportation facility, educational institution, industrial facility, air corridor (for example, for use by unmanned aerial vehicles), roadway, etc. In one embodiment, radio technology such as IEEE 802.11 may be implemented in base station 114b and WTRUs 102c, 102d to create a wireless local area network (WLAN). In an embodiment, base station 114b and WTRUs 102c, 102d may implement radio technology such as IEEE 802.15 to create a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d may use cell-based RATs (e.g., W-CDMA, cdma2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) ) to create a picocell or femtocell. As shown in FIG. 1A, base station 114b may have a direct connection to Internet 110. Thus, base station 114b may not need to access Internet 110 via CN 106.

The RAN 104 can communicate with the CN 106, which can be any type of network capable of providing voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Data may have different quality of service (QoS) requirements, such as different performance requirements, latency requirements, fault tolerance requirements, reliability requirements, data rate requirements, mobility requirements, and so on. The CN 106 may provide call control, billing services, location-based mobile services, prepaid calls, Internet connectivity, video distribution, and the like. and / or high-level security functions such as user authentication are performed. While FIG. 1A is not shown, it should be understood that RAN 104 and / or CN 106 may communicate directly or indirectly with other RANs that use the same RAT as RAN 104 or a different RAT. For example, in addition to connecting to the RAN 104, which can use NR radio technology, the CN 106 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi radio technology. -Fi.

CN 106 may also act as a gateway for WTRUs 102a, 102b, 102c, 102d to provide access to PSTN 108, Internet 110, and / or other networks 112. PSTN 108 may include circuit switched telephone networks that provide traditional telephony services (POTS). Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) in the TCP / Internet protocol suite. IP. Other networks 112 may include wired and / or wireless communications networks that are owned and / or provided by other service providers for use. For example, other networks 112 may include a different CN connected to one or more RANs that may use the same RAT as RAN 104 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in communication system 100 may include multi-mode capabilities (e.g., WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links) ... For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with base station 114a, which can use cell-based radio technology, as well as base station 114b, which can use IEEE 802.

FIG. 1B is a system diagram illustrating an example of a WTRU 102. As shown in FIG. 1B, WTRU 102 may include, but is not limited to, processor 118, transceiver 120, transmit / receive element 122, speaker / microphone 124, keypad 126, display / touch pad 128, non-removable storage 130, removable storage 132, source 134 power supply, a global positioning system (GPS) chipset 136, and / or other peripheral devices 138. It should be appreciated that the WTRU 102 may include any subcombination of the above elements and still be in accordance with an embodiment.

Processor 118 may be a general purpose processor, a special purpose processor, a standard processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, application specific integrated circuits (ASICs), user programmable circuits gate array (FPGA), any other type of integrated circuit (IC), state machine, etc. Processor 118 may perform signal coding, data processing, power control, I / O processing, and / or any other functionality with which the WTRU 102 operates in a wireless communication environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmit / receive element 122. Although FIG. 1B, processor 118 and transceiver 120 are shown as separate components, it should be understood that processor 118 and transceiver 120 may be co-integrated into an electronic unit or microcircuit.

Transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (eg, base station 114a) over radio interface 116. For example, in one embodiment, transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmitting / receiving element 122 may be an emitter / detector configured to transmit and / or receive, for example, signals in the IR spectrum, UV spectrum, or visible light spectrum. In yet another embodiment, the transmitting / receiving element 122 may be configured to transmit and / or receive signals in both the RF spectrum and the visible light spectrum. It should be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of radio signals.

While FIG. 1B, transmit / receive unit 122 is shown as a single unit, WTRU 102 may include any number of transmit / receive units 122. More specifically, MIMO may be employed in WTRU 102. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (eg, multiple antennas) for transmitting and receiving radio signals over air interface 116.

Transceiver 120 can be configured to modulate signals to be transmitted by transmitter / receiver element 122, as well as demodulate signals that are received by transmitter / receiver element 122. As indicated above, the WTRU 102 can have multi-mode capabilities. Thus, transceiver 120 may include multiple transceivers with which the WTRU 102 is able to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.

WTRU processor 118 may be coupled to speaker / microphone 124, keyboard 126, and / or display / touch panel 128 (eg, liquid crystal display (LCD) or organic light emitting diode (OLED) display) and may receive user input from them. Processor 118 may also output user data to speaker / microphone 124, keyboard 126, and / or display / touch pad 128. In addition, processor 118 may access information from any suitable storage device, such as non-removable memory 130 and / or removable memory 132, and store data thereon. Non-removable storage device 130 may include random access memory (RAM), read only memory (ROM), hard disk, or any other type of storage device. Removable memory 132 may include a Subscriber Identity Module (SIM) card, memory card, secure digital memory card (SD), or the like. In other embodiments, the processor 118 may access and store data from a storage device that is not physically located in the WTRU 102, such as a server or home computer (not shown).

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

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) relative to the current location of the WTRU 102. Additionally, or instead of information from the GPS chipset 136, the WTRU 102 may receive information about position over the air interface 116 from a base station (eg, from base stations 114a, 114b); and / or determine a position based on the timing of signals received from two or more neighboring base stations. It should be understood that the WTRU 102 may obtain location information through any suitable positioning method and still conform to an embodiment.

Processor 118 may optionally be coupled to other peripheral devices 138 that may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless communications. For example, peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for taking photos and videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a wireless headset, a Bluetooth® module, a radio with frequency modulation (FM), digital music player, media player, video game playback device module, internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Peripheral devices 138 may include one or more sensors. The sensors can be one or more of a gyroscope, an accelerometer, a Hall sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; geographic position sensor; altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, humidity sensor, etc.

The WTRU 102 may include a full duplex radio unit in which transmission and reception of some or all of the signals (eg, associated with specific subframes) for both UL (eg, for transmission) and DL (eg, for reception) can be jointly performed, at the same time, etc. The full duplex radio may include an interference control unit to reduce and / or substantially eliminate self-interference using any hardware (eg, choke) or signal processing with a processor (eg, a separate processor (not shown) or processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for transmitting and receiving some or all of the signals (eg, associated with specific subframes) for both UL (eg, transmit) and DL (eg, receive).

FIG. 1C is a system diagram illustrating RAN 104 and CN 106 in accordance with an embodiment. As noted above, RAN 104 can use E-UTRA radio technology to communicate with WTRUs 102a, 102b, 102c over air interface 116. RAN 104 can also communicate with CN 106.

RAN 104 may include eNode-Bs 160a, 160b, 160c, although it should be understood that RAN 104 may include any number of eNode-Bs and still follow an embodiment. Each eNode-B 160a, 160b, 160c may include one or more transceivers for communicating with the WTRU 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode B 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from the WTRU 102a.

Each eNode-B 160a, 160b, 160c may be associated with a specific cell (not shown) and may be configured to make radio resource management decisions, handover decisions, UL and / or DL user scheduling, and the like. As shown in FIG. 1C, eNode-B 160a, 160b, 160c can communicate with each other via the X2 interface.

CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway 166 (or PGW). While each of the above elements is shown as part 106, it should be understood that any of these elements may be owned by, and / or made available to, an entity other than the CN operator.

The MME 162 can be connected to each eNode-B 162a, 162b, 162c in the RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating a channel, selecting a particular serving gateway during the initial connection of the WTRUs 102a, 102b, 102c, and the like. MME 162 can provide a control plane function for switching between RAN 104 and other RANs (not shown) that use other radio technologies such as GSM and / or W-CDMA.

The SGW 164 can be connected to each eNode B 160a, 160b, 160c in the RAN 104 via the S1 interface. SGW 164 can essentially route and forward user data packets to and from WTRUs 102a, 102b, 102c. The SGW 164 can perform other functions, such as binding user planes during handover between eNode Bs, initiating paging when DL data is available to the WTRUs 102a, 102b, 102c, managing and storing the WTRU context 102a, 102b, 102c, etc. ...

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

CN 106 can facilitate interoperability with other networks. For example, CN 106 may provide WTRUs 102a, 102b, 102c with access to CS networks, such as PSTN 108, to facilitate communication between WTRUs 102a, 102b, 102c and legacy landline communication devices. For example, CN 106 may include an IP gateway (eg, IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108, or may communicate with it. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks that are owned and / or provided by other service providers for use.

Although the WTRU is described in FIG. 1A-1D as a wireless terminal, it is contemplated that, in certain exemplary embodiments, such a terminal may be used (eg, temporarily or permanently) with a wired communications interface to a communications network.

In typical embodiments, the other networks 112 may be WLANs.

An infrastructure BSS WLAN may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may access or interface with a Distribution System (DS), or communicate over another type of wired / wireless network that carries traffic to the BSS and / or outside the BSS. Traffic to the STA formed outside the BSS can enter through the AP and can be delivered to the STA. Traffic originating from the STA to recipients outside the BSS can be sent to the AP for delivery to the appropriate recipients. Traffic between STAs within the BSS can be sent via the AP, for example, if the source STA can send traffic to the AP and the AP can deliver traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be carried between (eg, directly between) a source STA and a destination STA by establishing a forward link (DLS). In certain exemplary embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using IBSS may communicate directly with each other. IBSS mode can also be referred to as a direct connect communication mode.

When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons over a fixed channel, such as the primary channel. The primary channel can have a fixed bandwidth (eg, 20 megahertz (MHz) bandwidth) or dynamically set through signaling. The primary channel can be the working channel of the BSS and can be used by the STA to establish a connection with the AP. In certain exemplary embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in 802.11 systems. STAs (eg, each STA), including the AP, can discover the primary channel for the CSMA / CA. Upon recognizing / detecting and / or determining whether the primary channel of a particular STA is busy, that particular STA may be disabled. One STA (eg, only one station) can transmit at any given time in a given BSS.

High bandwidth (HT) STAs can use a 40 MHz channel to communicate, for example by combining a 20 MHz primary channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz channel.

Ultra high bandwidth (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz and / or 160 MHz channels. 40 MHz and / or 80 MHz channels can be formed by combining continuous 20 MHz channels. A 160 MHz channel can be formed by combining 8 continuous 20 MHz channels or by combining two non-continuous 80 MHz channels, which can be called an 80 + 80 configuration. For an 80 + 80 configuration, the data after channel coding can pass through a segment analyzer that can split the data into two streams. Inverse Fast Fourier Transform (IFFT) or time domain processing can be performed separately for each stream. These streams can be mapped to two 80 MHz channels, and data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80 + 80 configuration can be inverted and the combined data can be sent to a medium access control (MAC) device.

802.11af and 802.11ah support 1 gigahertz (GHz) sub-modes. Channel bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the unused television frequency spectrum (TVWS), and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using spectrum. other than TVWS. In an exemplary embodiment, 802.11ah can support metered control / machine-to-machine communications (MTC), such as machine-to-machine communications (MTC) devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities, including support (for example, support only) certain and / or limited bandwidths. MTC devices may include a battery that has a battery life exceeding a threshold value (for example, to provide a very long battery life).

WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the largest total operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA from among all STAs operating in the BSS that supports the lowest bandwidth mode of operation. In the 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g. MTC type devices) that support (e.g. only support) 1 MHz mode even though APs and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz , 16 MHz and / or modes of operation with other values of the channel bandwidth. Carrier sensing and / or network assignment vector (NAV) parameters may be dependent on the state of the primary channel. If the primary channel is busy, for example, due to an STA such as a 1 MHz STA transmitting to an AP, all frequency bands may be considered occupied even though most of the frequency bands are still unoccupied and may be available.

In the United States, the available frequency bands that can be used by 802.11ah range from 902 MHz to 928 MHz. Available frequency bands in Korea are from 917.5 MHz to 923.5 MHz. Available frequency bands in Japan are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah ranges from 6 MHz to 26 MHz depending on the country code.

FIG. 1D is a system diagram illustrating RAN 104 and CN 106 in accordance with an embodiment. As noted above, RAN 104 can use NR radio technology to communicate with WTRUs 102a, 102b, 102c over air interface 116. RAN 104 can also communicate with CN 106.

RAN 104 may include gNBs 180a, 180b, 180c, although it should be appreciated that RAN 104 may include any number of gNBs and still follow an embodiment. Each gNB 180a, 180b, 180c may include one or more transceivers for communicating with the WTRU 102a, 102b, 102c over an air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. Also, in one example, gNBs 180a, 180b, 180c may use beamforming to transmit signals and / or receive signals from WTRUs 102a, 102b, 102c. Thus, the gNB 180a, for example, can use multiple antennas to transmit radio signals to and / or receive radio signals from the WTRU 102a. In an embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a can transmit multiple CCs (not shown) to the WTRU 102a. A subset of these CCs may be in the unlicensed spectrum, while the rest of the CCs may be in the licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement CoMP technology. For example, the WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using scalable numerical value transmissions. For example, OFDM symbol spacing and / or OFDM subcarrier spacing (SCS) may be different for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) with different or scalable durations (e.g., containing different numbers of OFDM symbols and / or having constant different absolute time durations) ...

gNBs 180a, 180b, 180c may be configured to communicate with WTRUs 102a, 102b, 102c in a stand-alone configuration and / or in a non-standalone configuration. In a stand-alone configuration, WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c without concurrently accessing other RANs (eg, such as eNode-B 160a, 160b, 160c). In a stand-alone configuration, WTRUs 102a, 102b, 102c may use one or more gNBs 180a, 180b, 180c as a reference point for mobility. In a stand-alone configuration, WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using signals in the unlicensed band. In an offline configuration, the WTRUs 102a, 102b, 102c can communicate / establish a connection with gNBs 180a, 180b, 180c while simultaneously communicating / establishing a connection with another RAN, such as eNode-B 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement Dual Connect (DC) principles for substantially simultaneous communication with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c. In an online configuration, eNode-Bs 160a, 160b, 160c can act as a mobility reference point for WTRUs 102a, 102b, 102c, and gNBs 180a, 180b, 180c can provide additional coverage and / or bandwidth to serve WTRUs 102a, 102b, 102s.

Each of the gNBs 180a, 180b, 180c can be associated with a specific cell (not shown) and can be configured to make radio resource control decisions, handover decisions, UL and / or DL user scheduling, support for network sharding, dual connect , interaction between NR and E-UTRA, routing user plane data to user plane functional block (UPF) 184a, 184b, routing control plane information to access and mobility management (AMF) functional block 182a, 182b, and the like. As shown in FIG. 1D, gNB 180a, 180b, 180c can communicate with each other via the Xn interface.

CN 106 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management functional block (SMF) 183a, 183b, and optionally a communication network 185a, 185b (DN ). While each of the above elements is shown as part 106, it should be understood that any of these elements may be owned by, and / or made available to, an entity other than the CN operator.

AMF 182a, 182b can be connected to one or more gNBs 180a, 180b, 180c in RAN 104 via N2 interface and can act as a control node. For example, AMF 182a, 182b can authenticate users of WTRUs 102a, 102b, 102c, support network sharding (e.g., handle different PDU sessions with different requirements), select a specific SMF 183a, 183b, manage registration area, terminate non-access stratum signaling (NAS), mobility management, etc. Network sharding can be used in AMFs 182a, 182b when configuring CN support for WTRUs 102a, 102b, 102c based on the types of services used by WTRUs 102a, 102b, 102c. For example, different network slicers can be set for different use cases, for example, URLLC based services, advanced mobile broadband (eMBB) access based services, access services to MTC, etc. AMF 182a, 182b may provide a control plane function for switching between RAN 104 and other RANs (not shown) that use other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-design access technologies third generation partnerships (3GPP) such as Wi-Fi.

SMF 183a, 183b can be connected to AMF 182a, 182b in CN 106 via N11 interface. SMF 183a, 183b can also be connected to UPF 184a, 184b in CN 106 via N4 interface. SMFs 183a, 183b can select and manage UPFs 184a, 184b, and configure traffic routing using UPFs 184a, 184b. SMFs 183a, 183b may perform other functions such as WTRU IP address management and allocation, PDU session management, policy and QoS management, UL data notifications, and the like. The PDU session type can be IP-based, non-IP-based, Ethernet-based, etc.

UPFs 184a, 184b may be connected to one or more gNBs 180a, 180b, 180c in RAN 104 via an N3 interface, which may provide WTRU 102a, 102b, 102c with access to packet-switched networks such as Internet 110 to facilitate communication. between WTRUs 102a, 102b, 102c and IP devices. UPF 184, 184b may perform other functions such as routing and forwarding packets, user plane policing, support for multipath PDU sessions, QoS processing in the user plane, DL packet buffering, binding for mobility, and the like.

CN 106 can facilitate interoperability with other networks. For example, CN 106 may include an IP gateway (eg, IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108, or may communicate with it. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks that are owned and / or provided by other service providers for use. In one embodiment, WTRUs 102a, 102b, 102c may be connected to local DN 185a, 185b via UPFs 184a, 184b via an N3 interface to UPFs 184a, 184b and an N6 interface between UPFs 184a, 184b and DN 185a, 185b.

With reference to FIG. 1A-1D and the corresponding descriptions of FIGS. 1A-1D one or more or all of the functions described herein in connection with one or more of: WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device (s) described herein can be implemented by one or more emulation devices (not shown). Emulation devices can be one or more devices configured to emulate one or more of the functions or all of the functions described herein. For example, emulation devices can be used to test other devices and / or to simulate network and / or WTRU functions.

Emulation devices can be configured to perform one or more tests of other devices in a laboratory environment and / or in an operator's network environment. For example, one or more emulation devices may perform one or more functions or all functions, and they are fully or partially implemented and / or deployed as part of a wired and / or wireless communication network for testing other devices in the communication network. One or more emulation devices may perform one or more functions or all functions, while they are temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device can be directly connected to another test device and / or can perform tests using wireless communication via a wireless communication channel.

One or more emulation devices may perform one or more functions, including all functions, and not be implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices can be used in a test scenario in a test laboratory and / or in a non-deployed (eg, test) wired and / or wireless communications network to test one or more components. One or more emulation devices can be test equipment. Emulation devices may use direct RF connection and / or wireless communications via RF circuitry (which may include one or more antennas, for example) to transmit and / or receive data.

In next generation mobile communications, eMBB, machine type streaming (mMTC), URLLC, and the like. are possible deployments in spectrum bands ranging from 700 MHz to 80 GHz. Next generation mobile communications may use one or both of the licensed and unlicensed spectrum.

For transmission below 6 GHz, multi-antenna techniques such as Multiple Input Multiple Output (MIMO), Single Input Multiple Output (SIMO), Multiple Input Single Output (MISO), etc. ... are possible deployment options. Multiple antenna techniques can provide diversity gain, multiplex gain, beamforming, array gain, and the like. In addition, if multiple WTRUs communicate with a single hub, Multi-User MIMO (MU-MIMO) can improve system throughput by facilitating transmission of multiple data streams to different WTRUs simultaneously on the same and / or overlapping set of resources over time. and / or frequency. For a single user MIMO (SU-MIMO) system, the same hub can transmit multiple data streams to the same WTRU, rather than multiple WTRUs as in a MU-MIMO system.

Multi-antenna transmission at millimeter-wave (MMW) frequencies may differ slightly from multi-antenna techniques operating below 6 GHz. This may be due to different propagation characteristics at millimeter wave frequencies and the possibility that a network node or WTRU has fewer RF circuits than antenna elements.

FIG. 2 shows an example of a TRP model and a WTRU antenna. The multi-element antenna model can be made in the form of Mg antenna panels in the vertical dimension and Ng antenna panels in the horizontal dimension. Each antenna panel can be made with or without polarization. Each panel can contain a separate array of elements or have one or more rays. Timing and phase may not be calibrated across all panels, although multiple panels may be equipped with the same network device, host, base station, etc. The basic configuration of a multi-element antenna may differ according to the operating frequency band, as shown in the examples in FIGS. 3.

Precoding at millimeter wave frequencies can be digital, analog, hybrid (digital and analog), etc. Digital precoding is accurate and can be combined with equalization. Digital coding can be configured as SU, MU, multi-cell precoding, etc. at frequencies below 6 GHz. At millimeter wave frequencies, the limited number of RF circuits compared to antenna elements and loose channel placement can pose problems for digital beamforming. Analog beamforming overcomes the problem of the limited number of RF circuits by using analog phase shifters on each antenna element. It can be used in the IEEE 802.11ad standard during a sector-level sweep to determine the optimal sector, refine the beam to refine the sector relative to the antenna beam, and track the beam to correct sub-beams over time based on channel changes.

In hybrid beamforming, the precoding device can use the analog and digital domains. In each area, you can use precoding and combine matrices with different structural constraints, for example, constant modulus constraint for combining matrices in the analog domain. As a result, there can be a trade-off between hardware complexity and system performance. Hybrid beamforming may be able to achieve digital pre-coding performance due to channel sparseness and use multi-user or multi-stream multiplexing. However, with a limited number of RF circuits, it may not be desirable to use configurations beyond millimeter waves.

In LTE, the SRS may be a reference signal (RS) transmitted by the WTRU in the UL direction for a network node, such as an eNodeB, to estimate the quality of the UL channel over a wider bandwidth. The network node can use this information for UL frequency selective scheduling, UL timing estimation, and the like. Single SRS, periodic SRS, aperiodic SRS, etc. can be used. Single and periodic SRS transmissions can be classified as originating type 0 SRS transmissions, which can be configured through higher layer signaling, radio resource control (RRC) signaling, or the like. Aperiodic SRS transmission can be classified as Trigger Type 1 SRS transmission, which can be configured with RRC but triggered by Downlink Control Information (DCI). The network may configure the WTRU using the WTRU-specific SRS configuration. A WTRU-specific SRS configuration may provide time domain resources, subframe resources, frequency domain resources, and the like, specified with broadband SRS across the entire bandwidth of interest, narrowband SRS allowing the WTRU to hop between transmissions, and the like. ...

Different WTRUs may have different SRS bandwidths. Each SRS bandwidth can be a multiple of four resource blocks (RBs). Different WTRUs may be configured with the same comb, but with different cyclic shifts or phase rotations, whereby SRS transmissions are orthogonal to each other over the same frequency range. Different WTRUs may use different combs to provide frequency multiplexing with a different frequency band.

In LTE, SRS power control can be defined as follows:

.

...

Lvl. 1

where M _SRS is the SRS transmission bandwidth expressed as the number of RBs, and P _SRS at the end of the equation is the tunable offset. Thus, the SRS transmit power may be based on the SRS transmit bandwidth and have additional power offset.

Frequencies of higher bands can be used in BM. At higher channel frequencies, higher path losses and more abrupt changes can be observed in the channel. At high frequencies, a large-scale antenna array can be used to achieve high beamforming gain to compensate for high propagation losses. The resulting crosstalk loss can be kept high to provide the desired data throughput or coverage. Communication configurations based on directional beam (s) require precise beam matching. The optimal direction of the beam (s) can be related to the actual channel in terms of entry and exit angles in both azimuth and elevation. The optimal direction of the beam (s) can be dynamically adjusted using a variable channel.

DL and UL BM procedures may include P-1, P-2, P-3, U-1, U-2, and U-3. For P-1, the WTRU may measure different TRP TX beams to select the TX TRP beam (s) and RX of the WTRU beam (s). For beamforming in the TRP, a TX beam sweep may be performed within the TRP or between them from a set of different beams. For beamforming, the WTRU may be swept RX beam of the WTRU from a set of different beams to the WTRU. The TX TRP beam (s) and the RX beam (s) of the WTRU can be defined jointly or sequentially.

For P-2, the WTRU may measure on the other TX beam (s) of the TRP to possibly change the TX beam (s) within or between the TRP. This configuration can be used from a potentially smaller set of beams for beam refinement than P-1. In addition, for certain configurations, P-2 may represent a special case or subclass P-1. For P-3, the WTRU may measure on the same TX TRP beam (s) to change the RX beam (s) of the WTRU during beamforming.

Procedure U-1 may use the TRP measurement on different WTRU TX beams to select the WTRU TX beam (s) or the RX TRP beam (s). Procedure U-2 can use the TRP measurement on different RX beams of the TRP to optionally change or select the RX beam (s) within or between TRPs. Procedure U-3 may use TRP measurement on the same RX TRP beam (s) to change the TX beam (s) of the WTRU in case the WTRU is using beamforming.

The bandwidth fraction (BWP) may indicate a contiguous set of physical RBs (PRBs) selected from a contiguous subset of common RBs for a given numerical value (u) on a given carrier. In a DL, a WTRU may be configured with a maximum of four BWPs, with one carrier or DL BWP being active at a given time from the point of view of the WTRU. The WTRU may not wait to receive the Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Channel Status Information RS (CSI-RS), Tracking Reference Signal (TRS), and the like. outside the active BWP.

In the UL, the WTRU can be configured with a maximum of four BWP carriers with one BWP carrier active at a given time or in this case. If the WTRU is configured with an additional UL, the WTRU can be configured with a maximum of four additional carriers in the additional UL. In a configuration, one BWP carrier may be active at a given time, for example an active UL BWP, from the point of view of the WTRU. The WTRU may not transmit the Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH) outside the active BWP.

For each BWP, the following parameters can be configured for control resource sets (CORESETs) for search space types for DL BWPs in the primary cell (Pcell): the BWP indicator field in the 1_1 DCI format can be used to indicate the active DL BWP, and the BWP indicator field in 0_1 DCI format can be used to indicate the active UL BWP. For Pcell, the WTRU may be provided with a higher layer parameter, DL BWP by default, DL BWP by default among the configured DL BWPs. If the WTRU is not provided with a default DL BWP parameter by a higher layer, the default BWP may be the initial active DL BWP. In some configurations, the SRS may be transmitted within the BWP even when frequency hopping is activated.

FIG. 4 shows an example of a full or global wobble 402 and a partial or local wobble 404 for procedure U-3. Full or global beam sweep can be used to determine the optimal UL TX beam (s) from all or most of the WTRU TX beams, and can be used in the absence of beam matching at the WTRU. If partial beam alignment is known so that the WTRU knows the optimal TX beam subset based on the determined RX beam, the partial or local beam sweep may be used to determine the optimal UL TX beam (s) within the optimal beam subset.

The SRS Beam TX indication can be transmitted via the SRS or DL RS resource. DL RS may be CSI-RS, Synchronization Signal Blocks (SSB), or the like. FIG. 5 is a table showing examples of spatial relationships between DL RS and UL SRS for a TX beam. In certain configurations, an indicator or indication to the WTRU may be a command from the WTRU to perform a task, operation, procedure, or the like. In certain configurations, the received command may also be an indication.

The configuration of the spatial relationship between the reference RS, which may be SSB, SS / Physical Broadcast Channel (PBCH) block, CSI-RS, SRS, etc., and the target SRS may be indicated by a higher layer parameter. For example, SRS-SpatialRelationInfo (SRS spatial relationship information) can be used. For details of UL BM SRS Beam Designation, a similar or different message may be required. It may also be desirable to perform beam sweeping for U-1, U-2, U-3, and the like. based on the configured SRS-SpatialRelationInfo. The WTRU may determine an SRS beam indication for a wide or local TX beam sweep, may be configured to efficiently indicate a low latency UL BM SRS beam indication, and the like.

In addition, it may be desirable to indicate the beam for multiple BWPs. To provide robustness to blocking of beam pair communication (BPL) at high frequencies, the WTRU may be configured with one or more DL beams to receive a PDCCH or PDSCH. Each DL beam may be represented or associated with DL RSs such as SSB, SS / PBCH block, CSI-RS, SRS, etc. Associated DL RSs can (can) be configured and transmitted on each BWP, or on a composite carrier or component carrier (CC).

The WTRU can be configured with one or multiple BWPs for DL or UL. Only one BWP can be active at a given time for each WTRU for DL and UL, respectively. The active BWP can change dynamically based on available frequency / time domain (F / T) resources, additional bandwidth required, radio degradation, interference, path loss, and the like. Before switching or transitioning to a new active BWP, the WTRU may consider potential BWPs based on QoS and then select a target BWP. The WTRU can be configured, indicated, or initiated by a higher layer, RRC, layer 2, MAC control element (MAC-CE), L1 control, DCI, and the like. for an explicit or implicit BWP measurement outside the active BWP. Likewise, the WTRU can also perform beam measurement on a per BWP basis, dynamic reporting, and associated beam indication. If the WTRU is configured with one or more beams for multiple BWPs, an efficient beam pointing mechanism is required to support various cases with small signaling headers.

Beam guidance for multiple TRPs can be configured. In certain configurations, the maximum supported number of NR-PDCCHs corresponding to scheduled NR-PDSCHs that a WTRU may expect to receive may be two per CC for one BWP for a CC. Multiple panels in a WTRU may not be quasi-co-located (QCL) because panel orientations differ from one another. For example, two panels may face opposite sides. Efficient low latency beam indication may also include SRS beam indication for BM UL, beam indication for multiple BWPs, and beam indication for multiple TRPs / multiple panels. The beam designation for multiple BWPs may further include beam designation for multiple DL BWPs, beam designation for multiple UL BWPs, and beam designation for UL and DL BWPs.

Also, activation of DL BWPs and UL BWPs from a plurality of BWPs may be performed based on the configuration information. To achieve the target performance, at least one potential DL BWP and at least one potential UL BWP from the plurality of BWPs may also be estimated based on the configuration information. Dynamically changing the DL BWP and UL BWP based on at least one estimated DL candidate BWP and at least one estimated UL candidate BWP can also be implemented in certain configurations.

The index of a particular ray can be specified using a high level parameter such as SRS-SpatialRelationInfo. The UL beam for the transmission of the SRS resource may also be indicated by associating the target SRS resource or the SRS resource to be transmitted with the reference RS resource indicated by the SRS-SpatialRelationInfo. In certain configurations, the SRS-SpatialRelationInfo may be set to a CSI-RS resource or an SS / PBCH resource if full or partial beam alignment is maintained. The SRS-SpatialRelationInfo can also be set to the SRS resource if full or partial ray matching is maintained, or if the ray matching is not preserved. Based on the specified SRS-SpatialRelationInfo high level parameter, the WTRU may determine a spatial domain transmit filter or beam (s) to transmit the SRS resource.

Each SRS resource can be configured with a high level parameter such as SRS-SpatialRelationInfo, or to reduce the configuration header, the SRS resources in the SRS resource set can be divided into multiple groups or subsets, and a parameter can be provided for each SRS resource group or subset high-level SRS-SpatialRelationInfo at the level of one group or subset. The configurations can include N groups or subsets of SRS resources in the SRS resource set. The value of N can be equal to or greater than 1. If N is 1, the SRS resources in the SRS resource set can be configured with one high level parameter and can be considered as a set level parameter.

If none of the SRS resources in the set are tuned with a high layer parameter or set to indicate the index of specific beam (s), the WTRU may transmit using these SRS resources with different spatial domain transmit filters or directions. TX beam UL. This operation can be based on WTRU beamforming capabilities, multiple configured UL TX beamforming directions, dynamic network indications, L1 messages, DCI messages, higher layer configurations, RRC configurations, Layer 2 controls, MAC-CE, full or partial compliance beams, transmission of SRS resources with spatial domain transmit filters corresponding to the RX DL beam directions based on WTRU DL beam measurements, and the like. In certain configurations, the various spatial domain filters may cover all WTRU UL TX beamforming directions or the global UL TX beam sweep for a UL BM procedure such as U-1. The various filters in the spatial domain may also cover a portion of the UL TX beamforming directions or a partial or local UL TX beam sweep for a UL BM procedure such as U-3.

If none of the SRS resources in the set are tuned using the high layer parameter, the WTRU may also transmit fixed TX beam (s), such as U-2, or local UL TX sweep, such as U- 3. With dynamic gNB indications to initiate SRS Beam Sweep, the SRS-ResourceRep information element may be included and configured at a higher layer, RRC, Layer 2, in a message or initiating MAC-CE message or DCI element, or DCI entry. or SRS-ResourceRep in the DCI field. The SRS-ResourceRep Information Element may be used to initiate L1 signaling, aperiodic SRS trigger message, SRS request, or the like with the DCI. This information associated with the SRS resource set may indicate whether the repetition related to the spatial domain transmit filter is enabled / disabled at the WTRU side. In this configuration, the WTRU can transmit using different SRS resources within the SRS resource set by using the same beam or different beams. If repetition is enabled, a single beam index can be explicitly included or implicitly specified and can use or refer to the optimal or best RX beam (s) that are measured or used. (s) WTRUs in recent DL beam measurement procedures in this trigger message, whereby the WTRU transmits SRS resource utilization with the same spatial domain transmit filter indicated by one beam index. If repetition is disabled, then a set of beams may be specified for the WTRU to perform the TX UL beam sweep.

The WTRU can autonomously determine the beam set based on the beam correspondence and DL beam measurement. For example, one beam index may be indicated in the trigger message, and the WTRU may employ a number of RX DL beams corresponding to the associated TX DL beams that are identified during the last or previous DL beam measurements. The range of beams can be determined based on the measured value of the receive power of the level 1 reference signal (L1-RSRP), an offset of N dB, or beams geographically close to the specified one beam. For example, if the specified one beam is X and the specified beam range is five, the WTRU may sweep five beams centered on the X beam, for example, two beams on the left side of the X beam and two beams on the right side of the X beam.

FIG. 15 depicts an example of a WTRU U-3 wobble range. FIG. 16 depicts another example of a WTRU U-3 wobble range. FIG. 15, a beam indication or identifier (ID) field or a beam indication or identifier (ID) may include a start identifier, a start beam identifier, an end identifier, or an end beam identifier with a step size of 1502. In another configuration, a center beam can be used to determine the beam swing. beam and half range at 1504. FIG. 16, the range of beams can be based on both the higher layer configuration and the lower layer initiating message (s). The beam identifier can be used to reduce wireless signaling to identify the beam. The rule can be specified or configured in the WTRU, for example, taking into account the optimal X beams, where X is a configurable value. When the WTRU receives a trigger DCI message that contains a beam identifier with a value of 3 in 1602, the WTRU may acquire or determine the optimal or best X = 4 beams around said beam 3 in 1604 as the range of beams to swing in the U-3 procedure. This can be done based on the last or previous DL measurement.

The WTRU may transmit using SRS resources with spatial domain transmit filters indicated by each configured SRS-SpatialRelationInfo for each SRS resource. The WTRU may also sweep the TX UL beam by transmitting over all SRS resources using beams indicated by the SRS-SpatialRelationInfo high level parameter configured for each SRS resource or groups, with the group number N> = 1 of the SRS resources in the set.

If the SRS-SpatialRelationInfo high level parameter (s), where the SRS resource group shares the same parameter, or each resource has its own parameter configured for all SRS resources, is set to the same content, the WTRU can transmit with using all SRS resources with the same spatial domain transmit filter or beam (s). In this configuration, for U-2, the network device, gNB, or TRP can sweep the RX beam of the UL while the WTRU transmits SRS resources using the same TX beam (s).

In another embodiment, if the high-level parameter (s), such as SRS-SpatialRelationInfo, for all SRS resources is set (s) to the same content or the same RS resource identifier, or All SRS resources are configured with a high level SRS-SpatialRelationInfo at a single set level, the WTRU can perform local or partial TX beamforming of the UL and transmit using these SRS resources using different beams. This configuration can be applied to U-3 procedures, and different beams can be spatially close to the beamforming direction indicated by the high level parameter SRS-SpatialRelationInfo.

Additional or supplementary information may be required for the WTRU to decide whether to transmit SRS resources with the same or different spatial domain transmit filter (s) when the SRS resources in the resource set are configured with multiple high-level parameters such as SRS-SpatialRelationInfo, but the parameters of each resource have the same content or the same RS-ID or high-level parameter at the level of the same SRS-SpatialRelationInfo set. Additional or supplementary information at a higher layer, RRC, or similar configuration may indicate whether the WTRU is wobbling a TX on a UL beam or whether a fixed TX is using a UL beam.

The SRS-ResourceRep high parameter may indicate the UL beam sweep type or the UL BM procedure such as U-1, U-2, or U-3. The SRS-ResourceRep parameter can be set and tuned using the RRC, and this parameter associated with the SRS resource set can determine whether repetition is enabled or disabled in conjunction with a spatial domain transmit filter at the WTRU. The WTRU may transmit using different SRS resources in the SRS resource set by using the same beam or different beams. For example, if the SRS-ResourceRep parameter is enabled, this may instruct the WTRU to perform procedure U-2, or indicate to the network device, gNB, TRP, or the like. perform UL beam RX sweep. If SRS-ResourceRep is disabled, this may instruct the WTRU to perform U-1 procedure, U-3 procedure, UL TX sweep, and the like.

In addition, this indication information may be transmitted by dynamic signaling, higher layer message, RRC message, layer 2 message, MAC-CE, L1 control message, DCI, and the like. Dynamic signaling can be sent from network device, gNB, TRP, etc. the WTRU to activate one or a subset of the configured SRS sets for execution by the WTRU UL BM. For example, a set of aperiodic SRS resources may be activated or triggered by DCI, with the flag information indicating whether the WTRU transmits the set of SRS resources with a TX UL beam sweep or fixed TX UL beam (s). In certain configurations, dynamic signaling may also be dedicated to indicate when or if the WTRU is wobbling a TX on the UL beam.

FIG. 6 shows an example of signaling for a BM. As shown in FIG. 6, the WTRU may receive an SRS configuration message and an SRS trigger message, such as an RRC or DCI trigger message. Beam indication information cannot be included in the initiating SRS message. In this configuration, the WTRU may follow the SRS configuration, SRS-Resource-Rep, SRS-SpatialRelationInfo, and the like. Without beam designation information in the initiating SRS message, the WTRU may use SRS resources with the spatial domain transmit filter (s) indicated in the SRS configuration information, which may indicate which WTRU is performing UL beam TX sweeping, for example, the SRS-ResourceRep parameter set to disabled, with transmission filters specified by high-level parameters such as SRS-SpatialRelationInfo.

If a subset of all SRS resources of the SRS are not configured using the SRS-SpatialRelationInfo high level parameter and no other SRS resources are configured, the WTRU may only transmit on those configured SRS resources with the spatial domain transmit filter (s) specified via SRS-SpatialRelationInfo. Transmissions on SRS resources may use the same transmission filter or different transmission filters. On other SRS resources that are not configured with SRS-SpatialRelationInfo, the WTRU may not transmit.

If an SRS resource in an SRS resource set is configured using the SRS-SpatialRelationInfo high level parameter, or if multiple SRS resources in an SRS resource set share a group level or set level using the SRS-SpatialRelationInfo high level parameter, the WTRU can determine that the link in the activation command activates the SRS resource set to be used for the UL BM and that the RS resource has a higher priority than the SRS-SpatialRelationInfo. For example, an SRS resource in an SRS resource set may be configured to transmit on beam X. When the SRS resource set is activated, the activation command may indicate Y beam for the SRS resource set. The WTRU may then transmit using all SRS resources on the Y-beam instead of the X-beam. The wake-up command may be included in a higher layer, RRC, layer 2, MAC-CE, layer 1, or DCI signal.

To activate or initiate an aperiodic SRS, the DCI may include a resource set activation, a resource repeat flag, a UL beam indication, and the like. With regard to resource set activation, a plurality of SRS aperiodic (AP) resource sets can be configured using RRC or RRC + MAC-CE, but triggered or activated using L1 control or DCI. A DCI field, such as an SRS request field, may be used to indicate which SRS set (s) was initiated. If only one SRS set is configured, this DCI field may or may not be required.

The resource repetition flag may be a 1-bit DCI field for indicating whether SRS resources are transmitted in activated SRS resource sets with the same transmission filter in the UL spatial domain. The SRS resources in the resource set can be transmitted in different OFDM symbols. The resource repetition flag may contain similar information as the high level parameter SRS-ResourceRep, and may or may not be present in the L1 or DCI control. If the resource repetition flag is not present in the DCI where the SRS resource set is initiated, the WTRU may transmit the SRS resource set in accordance with the high level parameter SRS-ResourceRep. This can be viewed as a hybrid SRS beam indication that combines the DCI indication and the higher layer configuration (s) or RRC. As an example, the DCI may indicate resource set activation or beam direction (s) for a UL Rx sweep with a fixed beam transmission, such as U-2, or a UL Tx sweep with another beam transmission, such as U-3, and RRC configurations may specify the transmission type or repetition type of SRS resources in this resource set, for example U-2 or U-3.

FIG. 7 shows another example of signaling for a BM. FIG. 7 shows an SRS beam indication with combined triggering and configuration for a BM where the WTRU uses higher layer or RRC configurations to determine the SRS resource repetition type and an SRS trigger message to determine the spatial domain transmit filter (s). The WTRU may receive an SRS configuration message and an SRS trigger message. The trigger SRS message may contain the Y index of one beam, and the WTRU follows the SRS configuration to determine the type of repetition, eg, settling to an activated state, and may then use a fixed TX UL Y beam.

For certain configurations, if the resource repetition flag is present in the DCI, regardless of the SRS-ResourceRep high parameter information, the WTRU may transmit this SRS resource set in accordance with the DCI flag. In this configuration, the flag can take precedence over the high-level parameter SRS-ResourceRep. In this configuration, the SRS beam indication can only be in the L1 signaling, or be transmitted only through the L1 signaling, for example, if the UL beam indication is in the DCI. In addition, if a trigger message, such as a DCI, contains SRS Beam Indication information, it may have a higher priority than the Beam Indication information configured in high layer SRS configurations.

UL Beam Designation information may or may not be present in the DCI. This beam indication information may be conveyed in one or more SRS Resource Indicator (SRI) fields in the DCI. In certain configurations, the SRI field may be the same SRI field as the SRI field used for PUSCH transmission, or a different field.

If there is no beam indication information in the DCI, the WTRU may use the SRS resources within the triggered or activated SRS resource set with the spatial domain transmit filter indicated by the SRS-SpatialRelationInfo high level parameter. In this case, the SRS beam indication scheme may be a hybrid solution in which DCI indication and higher RRC layer or configuration (s) may be combined. If N> 1 SRS resources are configured with a different SRS-SpatialRelationInfo parameter, the WTRU can sweep the TX UL beam, such as in U-1 or U-3. If N> SRS 1 resources are configured with the same value as SRS-SpatialRelationInfo, the WTRU may perform fixed beam transmission such as U-2.

If the SRS-SpatialRelationInfo parameter is not configured, or the configured SRS-SpatialRelationInfo parameter does not contain a valid or proper RS resource identifier, the WTRU may determine that the network device, gNB, TRP, etc. does not indicate the TX information of the UL beam. Then, in certain configurations, the WTRU may perform global beam sweeping for a BM procedure such as U-1. For example, the WTRU may perform initial UL beam preparation when the WTRU is tuned with a higher layer or RRC connection from the initial access.

If the SRS-SpatialRelationInfo is not configured, the WTRU may perform the U-2 procedure or the U-3 procedure. For example, if repetition is enabled, the single beam index can be explicitly included or implicitly indicated, for example, if the WTRU is using the optimal RX beam that the WTRU has measured or used in the last DL beam measurement procedure in the trigger message. In this configuration, the WTRU can transmit using SRS resources with the same spatial domain transmit filter indicated by one beam index.

If repetition is disabled, it may be necessary to specify a set of beams to each WTRU from the network to perform the TX UL beam sweep. The WTRU may also autonomously determine the beam set based on the beam mapping and DL beam (s) measurement. For example, one beam index may be indicated in the trigger message, and the WTRU may employ a number of RX DL beams corresponding to the associated TX DL beams that are identified during the last or previous DL beam measurements. The range of beams can be based on the measured L1-RSRP (eg, N dB offset) or beams that are geographically close to a specified single beam. For example, if the specified one beam is X and the specified beam range is 5, the WTRU may sweep five beams centered on the X beam, for example, two beams on the left side of the X beam and two beams on the right side of the X beam.

If beam indication information is present in the DCI or L1 signal, the WTRU may transmit using SRS resources. If the beam indication information is present in the DCI, and the beam indication information specifies one beam, the WTRU may perform a UL beam TX sweep or fixed beam transmission by checking for the existence of a resource repetition flag in the current DCI. If the resource repetition flag indicates a TX UL beam wobble, the WTRU may determine that the single beam indication contains inaccurate information for a TX UL beam, which may be refined. In this configuration, the WTRU can sweep the beam locally or partially around or centered on this one beam. The number and directions of the swept local beams may be determined by the WTRU based on previous DL beam measurements and reports. If the resource repetition indicates a fixed beam transmission, the WTRU may use the SRS resources with the beam indicated in the beam designation information in the DCI. If the DCI does not include a resource repetition flag, the WTRU may check if the SRS-ResourceRep high level parameter is configured for the activated SRS resource set.

If the beam indication information is present in the DCI and the beam indication information indicates no beam, the WTRU may check the resource repetition flag in the DCI. If the resource repetition flag is present, the WTRU may perform TX beam sweep if the resource repetition flag is set to the disabled state and the sweep beams are indicated by the high level parameter SRS-SpatialRelationInfo. If the resource repetition flag is set to the activated state, the WTRU may use the fixed-beam SRS resources, which is also indicated by the SRS-SpatialRelationInfo high level parameter received in the SRS configuration message.

If the beam designation information is present in the DCI and the beam designation information indicates multiple beams, the WTRU may select one beam to transmit a fixed beam of the SRS resource set if indicated by the resource repetition flag or high level parameter SRS-ResourceRep. Otherwise, the WTRU sweeps the TX beams indicated in the beam indication information to the DCI.

FIG. 8 shows another example of signaling for a BM. The WTRU may use the trigger SRS message to determine the SRS resource repetition types and spatial domain transmit filter (s) when the WTRU is not using the SRS configuration. As shown in FIG. 8, the WTRU may receive an SRS configuration message and an SRS trigger message. The Trigger SRS message may contain an SRS repetition type field and a beam identifier field. In certain configurations, the beam identifier field may have a higher priority than the configured SRS-SpatialRelationInfo received in the SRS configuration message.

In examples 802 and 804, the SRS repetition type field may indicate a deactivated state. In example 802, the beam identifier may contain blank information that indicates a network device, gNB, TRP, and the like. has no specified imprecise direction, and the WTRU may perform a full U-3 wobble procedure. In example 804, the beam identifier may indicate a specific beam, such as beam 3, for the WTRU to perform partial beam sweeping around an imprecise beam direction centered on beam 3. The WTRU may sweep the TX beam (s) according to previous measurements of the UL beam (s) , previous TX beams of the UL beam, previous measurements of the DL beam, match beams and output or generate multiple TX beams around the specified beam 3. In this example, the WTRU can sweep beams 2, 3, 4, and 5 because during the last or previous beam measurement DL The WTRU supported multiple RX DL beams, some of which correspond to these four beams.

In example 804, the beam ID field may contain more than one RS ID. FIG. 17 depicts an example of an implicit procedure for determining the swing range of a WTRU U-3. At 1702, the beam identifier field may include a list of beams for implicitly defining a U-3 sweep range. In certain configurations, the hybrid method may be configured to combine FIG. 17 with a different definition of the swing range given in this document. For example, the beam field may contain a start beam identifier and an end beam identifier, with beams selected between the start and end beam identifiers being determined by a higher layer rule, eg, the X beams with the highest L1-RSRP instead of the stage field.

FIG. 18 depicts an example procedure for a WTRU to determine beam swing for triggered SRS resources for UL BM. The WTRU may receive an SRS trigger message in the DCI (1802). For triggered (1804) SRS resources, a repetition field or a beam identifier field may be derived from the received DCI. The repetition field may indicate whether the WTRU is performing the U-2 or U-3 procedure. The beam identifier field can contain one or more DL RS identifiers such as SSBI or CRI (1806), or UL RS identifiers such as SRI.

If the beam identifier field contains a DL RS identifier, the beam range can be obtained based on the last or previous DL beam measurements (1808) and the UL beam swept performed (1812). If the beam identifier field contains a UL RS identifier, the range of beams can be obtained based on the last or previous UL beam measurements (1810) and the UL beam swept performed (1812). The swing range of the beam can be obtained by an explicit operation 1814 using different parameters, an implicit operation 1816 using different parameters, or a rule-based operation 1818. In explicit operation, the WTRU may determine the range based on the geographic location to the specified beam. In an implicit operation, the WTRU may determine the range from the beam list. In a rules-based approach, the WTRU can autonomously determine the beam sweep range based on recent or previous DL or UL beam measurements. In addition, the hybrid procedure may use a higher layer or RRC configuration in which two fields, which may be partially or completely present in the DCI, may be partially or all configured in the RRC message. One or both of the fields can be part of the DCI fields or configured as RRC parameters. In configurations in which the same field (s) are present in both the RRC configuration and the DCI, the SRS Beam Indication field in the DCI may have a higher priority than the same field configured in the RRC.

Beam indication can be configured for multiple BWPs. To provide robustness to blocking of high frequency beam pair communications, the WTRU may be configured with one or more DL beams to receive a PDCCH or PDSCH. Each DL beam may be represented or associated with DL RSs such as SSB, SS / PBCH block, CSI-RS, SRS, etc. Associated DL RSs can (can) be configured and transmitted per BWP or per CC.

A WTRU may be configured with one or multiple BWPs for DL or UL, with only one BWP for DL and UL being active at a given time for each WTRU, respectively. This single active BWP can change dynamically as the available frequency or time resources change, the need for increased bandwidth, radio degradation, interference, path loss, and the like. Before switching or transitioning to a new active BWP, the WTRU can estimate potential BWPs based on QoS and then select the target BWP correctly. Thus, the WTRU can be configured, specified, or specified by a higher layer, RRC, layer 2, MAC-CE, L1 control, DCI, and the like. for explicit or implicit measurement of some BWP outside the active BWP. In other words, the WTRU can be configured or initiated by RRC, MAC-CE, DCI, and the like. to dynamically perform beam measurements on a per BWP basis and send reports.

Since multiple beams can be configured for a WTRU across multiple BWPs, efficient beam indication can be configured on a per BWP basis. Various configurations may include beam-indicating for multiple DL BWPs, beam-indicating for multiple UL BWPs, and beam-indicating for UL and DL BWPs. DCI, transmission configuration indication (TCI), DCI table, or TCI table may be used to indicate a beam for multiple DL BWPs. A hybrid procedure with a combined DCI / TCI and TCI table can also be configured.

FIG. 9 shows an example DCI or TCI for beam indication for multiple DL BWPs. FIG. 9, a plurality of TCI fields may be part of a DCI to indicate a beam of a plurality of DL BWPs. At 902, each TCI field may represent the indicated TCI state for one BWP for independent beam indication. For example, in 902, TCI field 1 contains only the TCI status for DL BWP 1. In 904, one TCI field may contain the specified TCI status value for more than one DL BWP for joint beam indication. For example, TCI field 1 in 904 may contain the specified TCI status value for 3 DL BWPs, including DL BWP 1, DL BWP 2, and DL BWP 3.

One or any combination of the two configurations may be configured to indicate the TCI status for each TCI field, with independent beam designation or joint beam designation for multiple DL BWPs. In the first configuration, the normal beam indication may be represented by the absolute TCI status value for each TCI field. In the second configuration, the differential beam indication can be represented by the absolute value of the TCI state for the TCI reference field and can use the differential value for the remaining TCI fields relative to the TCI reference field. For example, in FIG. 9, each TCI field may contain an absolute TCI status value such as 902 or 904 when normal beam indication is used or adjusted by RRC. In another example, in FIG. 9, when differential beam indication is used or adjusted by RRC, the reference TCI field may select the TCI field with the TCI status with the highest or lowest index from all TCI fields in the same DCI. For example, at 904, the K TCI field may indicate S TCI states, and S may be the highest index of the TCI states signaled by all TCI fields in the same DCI. In another configuration, the TCI reference field may select the TCI field with the lowest or highest field index, such as TCI field 1 or N in 902.

FIG. 10 is a table showing examples of beam indication based on the TCI table for a plurality of DL BWPs. FIG. 10, the TCI state may contain a set of RSs with multiple RS identifiers for multiple BWPs. For example, TCI state 0 indicates CRI # 0 and SSB # 3 for BWP1 and BWP2, respectively. In this configuration, cross-carrier or cross-BWP beam indication can use TCI state or table. When the WTRU receives one TCI field in the DCI, which beam is indicated to the WTRU for subsequent PDSCH reception may be based on the WTRU's current active BWP. For example, if the WTRU receives a TCI field of 1, the WTRU may apply CRI beam # 4 if the WTRU's current active BWP is BWP2. When the WTRUs dynamically switch active BWPs by DCI-based or timer-based switching, the corresponding beam used to receive the PDSCH for the target BWP may change accordingly. For example, if the target BWP is BWP1 or BWP3, the WTRU can use CRI beam # 2 or SSB # 5 to receive the PDSCH, respectively.

To implicitly indicate a DL beam with a TCI table, each TCI state may explicitly indicate an RS identifier in one RS set for the BWP. The TCI state may implicitly indicate the beam (s) for receiving the PDSCH or PDCCH for multiple BWPs. The default TCI state can also be predetermined to receive a PDSCH or PDCCH when switching the BWP. For example, a TCI state with a specific identifier or lowest identifier of the currently tuned TCI state may be used by the WTRU prior to reconfiguration or reactivation to receive a PDCCH, reconfigure, reactivate, or initiate a DCI to receive a PDSCH. The default TCI state can be BWP specific or CC specific.

TCI state currently used for a specific BWP, such as old BWP before BWP handoff or standard / initial BWP configured for WTRU when WTRU switches to target or new BWP may be used by WTRU prior to reconfiguration or reactivation to receive PDCCH or change configuring, reactivating or initiating DCI to receive the PDSCH. To receive a PDSCH in a new BWP, the WTRU may use the TCI state activated to receive a PDCCH in the same BWP or a specific BWP. For example, the original BWP used by the WTRU prior to the BWP handoff, or the standard or initial BWP configured for the WTRU can be used.

The WTRU can be configured to receive the assigned DCI to indicate the PDSCH beam and receive X TCI fields (X> = 1) in the DCI. If the TCI table maintained by the WTRU contains some TCI states associated with multiple BWPs, X TCI fields may indicate beam (s) to receive PDSCH for Y BWPs, with Y> = X.

FIG. 11 is a table showing examples of hybrid beam designation for multiple DL BWPs. FIG. 11, if the WTRU receives two TCI fields that indicate TCI status 0 and 1, the WTRU may be configured to identify the proper beam (s) used for subsequent PDSCH reception if the WTRU uses any one from BWP 1, BWP 2 or BWP 3.

In configurations in which the WTRU receives a TCI field indicating a TCI status that does not contain beam (s) for the currently active BWP, the WTRU may switch to the BWP based on predefined rules. For example, the WTRU may switch to a common BWP that is available to all WTRUs within a network device, gNB, TRP, or similar area, or to a specific BWP that has the lowest TCI table identifier.

For PDSCH reception, if the time offset between DL DCI reception and the corresponding PDSCH is less than a threshold such as Threshold-Sched-Offset, the WTRU may determine that the antenna ports of one DM-RS PDSCH port group of the serving cell are quasi-jointly placed based on the default TCI state used to indicate the PDCCH QCL of the lowest CORESET identifier in the last interval in which one or more CORESETs were configured for the WTRU. The WTRU can be configured with one or multiple CORESETs and can also be configured with one or multiple BWPs. The default TCI state corresponding to the PDCCH TCI state with the lowest CORESET identifier may be BWP specific, CC specific, etc. For certain configurations, if the temporal offset is less than the Threshold-Sched-Offset, the WTRU may determine the beam indicated by the default TCI state in the active BWP. The default TCI state can be reused for multiple BWPs if the TCI default state corresponding to the PDCCH with the lowest CORESET identifier is configured for the multiple BWPs, for example, TCI state 0 in FIG. eleven.

With regard to the lowest CORESET identifier, it should be noted that CORESET 0 of all CORESETs configured for the WTRU may be configured during the initial WTRU access. For example CORESET 0 can be configured via PBCH. After the WTRU enters RRC connected mode, the WTRU may configure or update the TCI state for CORESET 0. When the WTRU determines the lowest CORESET identifier for receiving PDSCH in case the time offset is less than the Threshold-Sched-Offset, the WTRU may use the TCI state. corresponding CORESET 0.

If the SS / PBCH identified during initial access is the beam (s) used by the WTRU to receive the PDSCH, and the TCI state for CORESET 0 is configured, then the TCI state for CORESET 0 can be considered the TCI state by default. If the TCI state corresponding to CORESET 0 is updated for beams in an RRC connected state or mode, for example during initial access, the TCI state for CORESET 0 can also be used. When the WTRU is in the beam failure recovery procedure, the dedicated CORESET-BFR can be configured to monitor the network response to a beam failure recovery request. In this case, when the WTRU determines the default beam / QCL indication for PDSCH reception in case the time offset is less than the Threshold-Sched-Offset, the CORESET should not be considered the CORESET with the lowest identifier unless the WTRU is in beam failure recovery mode. ... This lowest CORESET identifier can be identified based on the most recent interval. When the WTRU is configured with multiple CORESET / search spaces, the CORESET / search space (s) may be configured to have slot information to determine the most recent slot.

If PDSCH and PDCCH reception for the WTRU is over multiple BWPs or CCs, the QCL spatial indication may be used. As an example for this configuration, the PDCCH can be scheduled or transmitted to BWP1 / CC1, for example, at a frequency below 6 GHz for higher reliability, and the PDSCH can be scheduled or transmitted to BWP2 / CC2, for example, at a frequency above 6 GHz for higher throughput. capabilities.

FIG. 10 TCI state 0 may contain two RSs for two different BWPs. For PDCCH and PDSCH reception, the same TCI state 0 may be activated (for PDCCH) / Specified (for PDSCH), but different beams may be specified for PDCCH and PDSCH, such as corresponding to different RS IDs, respectively. Regardless of whether the scheduling offset between DL DCI and PDSCH is less than or greater than Threshold-Sched-Offset, the default TCI state corresponding to the lowest identifier PDCCH / CORESET may be TCI state 0 shown in FIG. 10. The WTRU can also be configured with different TCI states to receive the PDCCH and PDSCH, respectively, with one TCI state being configured in one BWP / CC or multiple BWP / CCs. In this configuration, when the scheduling offset between DL DCI and PDSCH is less than Threshold-Sched-Offset, the WTRU should find a default TCI state, which may be different from the TCI state indicated in the DCI field.

UL BM SRS Beam Indication can be used for one BWP. FIG. 12 illustrates an example of using DCI or TCI to indicate an SRS beam for BM in multiple UL BWPs. For independent beam designation in 1202, each SRS field may contain beam designation information for one UL BWP. For joint beam indication in 1204, one SRS field may contain a beam indication applied to multiple UL BWPs.

As shown in FIG. 12, the SRS field may contain multiple parameters or subfields. At 1206, the parameters or subfields may be an SRS resource set field, an SRS resource repetition field, and a beam indication field, which may include a center RS identifier field and a beam range field. The SRS Resource Set field can be used to activate the SRS Resource Set. For example, this could be an SRS request field.

The SRS resource repetition field may be a flag field used to indicate whether the WTRU transmits SRS resources in the activated SRS resource set using the same or different spatial domain transmit filter (s) or using a fixed TX beam. UL, or UL beam TX swing. The field can be set to "activated" or "deactivated" to indicate that the WTRU is using different SRS resources in the SRS resource set using the same beam (s) or different ray (s). The beam indication field can be used to indicate beam information for transmissions of different SRS resources.

The central RS identifier field may be an RS identifier, a DL RS identifier, an SS / PBCH unit identifier, a CSI-RS resource identifier, an SRS resource identifier, and the like. If the SRS resource repetition field indicates that the WTRU is performing a fixed beam transmission, such as procedure U-2, the RS identifier may indicate one fixed beam for U-2. If the SRS resource repetition field indicates that the WTRU is performing a fixed beam transmission, such as procedure U-2, the RS identifier may also indicate an imprecise beam direction. If the field is empty, the WTRU may perform a global TX UL beam sweep within the associated BWP.

The beam range field may be used when the RS identifier in the center RS identifier field indicates an imprecise beam direction. For example, the WTRU may receive or generate multiple TX beams around the specified non-precise beam. The WTRU may sweep the TX beams in accordance with previous UL beam measurements, such as a previous TX UL beam, or previous DL beam measurements, such as a beam mapping, and determine the local TX sweep of the UL beam. The beam range field can be used to limit the number of beams or the range of beams that the WTRU can generate or receive based on the previous UL or DL BM.

FIG. 13 is a table showing configuration examples based on the TCI table for specifying a beam for a plurality of DL and UL BWPs. FIG. 13 shows that beam indication for both UL and DL BWP can be performed together. The WTRU may be configured with a TCI table, where some TCI states may contain RS sets that are applicable to multiple UL and DL BWPs, such as TCI state 0. In this configuration, this may indicate that the associated DL BWP and UL BWP are co-located in such a way that the two frequency bands are close enough to each other or completely overlap.

For multiple DL BWPs, multiple UL BWPs, or both UL and DL BWPs, if the WTRU receives a beam indication that indicates that the beam is not intended for the currently active BWP, this may indicate that the network may initiate and initiate a BWP handoff. The target BWP for the WTRU can be matched based on the specified beam. For example, if the WTRU receives a TCI field indicating TCI state 1 as shown in FIG. 11, the WTRU may switch to BWP 3. If multiple potential target BWPs exist based on the specified beam indication, the WTRU may switch to the default BWP. The default BWP may be the BWP that the WTRU is initially configured with. The WTRU can also switch to the BWP based on predefined rules. For example, the WTRU may switch to a common BWP that is available to all WTRUs within the scope of the network device, or to a specific BWP that has the lowest TCI table identifier.

In the example provided herein, the WTRU may also be configured to have one or more active UL or DL BWPs, which may indicate simultaneous transmissions on one or multiple UL or DL BWPs. The examples provided herein may apply to single carrier transmissions, multi-carrier transmissions, multi-BWP transmissions, and the like. In certain configurations, the maximum supported number of NR-PDCCHs corresponding to scheduled NR-PDSCHs that the WTRU can expect to receive may be two per CC in the case of one BWP per CC.

For multiple TRP configurations, separate high level signaling or DCI may be sent to the same WTRU. For UL BMs, the SRS beam indication may be in a separate DCI or high signaling from each TRP. For example, the SRI field or the SRS-ResourceRep field, which can be extended, in the DCI can indicate the TX UL beam (s). In addition, the SRS-SpatialRelationInfo and SRS-ResourceRep in high-level configurations may indicate the TX UL beam (s).

In addition, for multiple TRP configurations, to conserve signaling headers, shared beam designation for TX UL beam (s) with multiple TRPs may be used. The WTRU can connect to two or more TRPs at the same time. One of the TRPs may send SRS resource configurations to the WTRUs for both TRPs. This TRP can be configured as a master, primary or serving TRP, and the other TRP (s) can (can) be configured as a member or secondary TRP. In addition, two or more TRPs may share the same link between SRS resources and beams or spatial domain transmit filter. The SRS spatial relationship information can also indicate a general relationship.

It is possible that two or more TRPs do not use the same link between SRS resources and beams, or use different pairs of SRS resources and beams. In this configuration, the master TRP sends an SRS-SpatialRelationInfo that contains the association of SRS resources with different beams. FIG. 14 is a table showing examples of the relationship of an SRS resource with transmit filters in the spatial domain for a plurality of TRPs. The spatial relationship information for the SRS resource is shown in FIG. 14. The spatialRelationInfo in each SRS Resource Information Element (IE) may contain more than one ray information item. Spatial information in the spatialRelationInfo field can be specified or customized using TCI states. In this case, if more than one spatial relationship or more than 1 RS identifier is specified using the spatialRelationInfo field, the corresponding TCI state associated with the spatialRelationInfo field may include more than one spatial information or more than 1 RS identifier.

The SRS Resource Set IE may indicate whether the SRS-ResourceRep parameter is enabled or disabled. In the case of multiple TRPs, two or more TRPs may have the same SRS-ResourceRep setting or configuration. It is possible that two or more TRPs may have different settings in the SRS-ResourceRep. This can be used to apply two different BM processes in TRP. For example, one TRP may use the WTRU to apply fixed TX beam transmissions, for example, for U-2, while another TRP may use the WTRU to apply multiple TX beam transmissions, for example, for U-1 or U-3. In addition, one TRP can set the SRS-ResourceRep parameter to an activated state, and another TRP can set the SRS-ResourceRep parameter to a deactivated state. The SRS-ResourceRep element in the SRS Resource Set can be configured for two Boolean values, each corresponding to a TRP.

To activate or initiate an aperiodic SRS, the DCI indication may include a resource set activation, a resource repetition flag, and may include a UL beam indication. If there are two or more TRPs with a leading TRP representing both TRPs transmitting DCI to the WTRU, the resource set activation can be applied to either one of the TRPs or both TRPs. The resource repeat flag can be extended to either TRP or both TRPs. A resource repeat flag with 2 bits can be configured, one for each TRP. In addition, the SRS request fields in the DCI can be extended from two bits to four bits, where every two bits represent the activation of the SRS resource set for the TRP.

When the SRS-ResourceRep parameter is disabled by higher layer signaling, RRC or L1, the TX set of UL beams may be specified so that the WTRUs know how to sweep the TX of the UL beam. In the configuration, one beam index is indicated in the trigger message, and the WTRU may use beams geographically close to the indicated one beam index or one beam. The WTRU TX beam sweep range may be predefined, configured, or optionally specified. For example, 1 bit may be used to indicate a different WTRU TX beam sweep range, with a bit with a value of 0 indicating X beams for a WTRU TX beam sweep centered on that one beam, and a bit with a value of 1 indicating Y beams for a WTRU TX beam sweep. centered on the specified one beam. In the case of multiple TRPs, separate beam sweep range information for each TRP can also be applied. These configurations can be viewed as TRP specific beam selection for UL BM provisioning or TRP specific beam, where SRS resource set (s) initiation and SRS resource set (s) indication in configured / initiated SRS resource sets can be performed independently or jointly between multiple TRPs. as needed.

In addition to selecting TRP-specific beam for UL BM beam preparation or TRP-specific beam, panel-specific beam selection for UL BM or panel-specific beam preparation can be configured. The implicit panel UL specific beam preparation may provide that the network, jointly or separately, via one or multiple gNBs or TRPs, initiates the launch of N (N> 1) WTRUs by initiating N SRS resource sets. Each set of SRS resources can also be associated with a specific WTRU.

FIG. 23 shows an example of a communication specific to an SRS panel. SRS resource set 1 can be associated with WTRU board 1 and SRS resource set 2 can be associated with WTRU board 2 at 2302. When initiating either one of the two resource sets or both, for example by L1 or DCI signaling, or activation, for example by Layer 2, MAC-CE, higher layer, or RRC signaling, the associated WTRU panel (s) may (may) be used for beam preparation.

The network can initiate the launch of N> 1 panels by initiating 1 <= M <N SRS resource sets. Each SRS resource can be associated with a specific WTRU. At 2304, SRS resource set 1 may include SRS resources 1 and 2, which may be associated with WTRU board 1, and SRS resources 3 and 4, which may be associated with WTRU board 2. When SRS resource set 1 is initiated, for example, by L1 or DCI signaling, or activated, for example, by layer 2, MAC-CE, higher layer, or RRC signaling, both WTRU panels 1 and 2 can perform beam preparation. If the total number of SRS resources in one SRS resource set cannot cover the total number of TX UL beams to be provisioned by all relevant WTRUs, the number of initiated SRS resource sets may be increased or M may be in the range [1, N].

The network can initiate the launch of N> 1 panels by following the identifier or order of the initiated N SRS resource sets. Instead of each triggered set of SRS resources associated with a particular WTRU, the triggered set order or identifier of each triggered set may represent associated WTRUs. For example, if SRS resource sets 1 and 2 are triggered and there is no board communication in a higher parameter or trigger message, SRS resource set 1 can be applied to WTRU board 1 and SRS resource set 2 can be applied to WTRU board 2. When initiating SRS resource sets 2 and 3, first set 2 can be applied to WTRU panel 1 and second set 3 can be applied to WTRU panel 2. For order differentiation or panel selection based on Dial ID, a higher level message or lower level alarm message can be configured or specified with an additional field or flag to indicate whether the panel order or selection is based on Dial ID. You can also use the default rule. For example, in the absence of flag information, the WTRU may determine that the order of triggered SRS resource sets is used to select the default pane.

When preparing a UL-specific explicit panel beam, the network may initiate the launch of N> 1 WTRUs by specifying panel pointers or identifiers (IDs) along with the initiated SRS resource sets. The panel ID (s) can (s) be configured in the higher level parameters associated with each configured SRS resource set, or dynamically included in each triggering SRS message, for example in one or multiple fields in within DCI.

If multiple WTRUs are configured or triggered to perform UL beam preparation, the panel ID associated with each triggered or configured SRS resource set may be specified jointly or independently. FIG. 22 depicts an example of independent physical uplink shared channel (PUSCH) beam indication and PUSCH joint beam indication, where the SRS field to indicate an SRS resource identifier may be replaced with an extended SRS request field to indicate one or more SRS resource set identifiers.

After explicitly or implicitly determining the selection of WTRU panels, beams to be provisioned within each selected panel may be determined using any of the examples provided herein. High layer parameters, spatialRelationInfo field, TCI state associated with each SRS resource, which can be configured RRC, specified L1, specified DCI, activated layer 2, or activated MAC-CE, resource identifier order or the range of the beam to prepare the beam.

FIG. 27 shows a procedure for defining triggered WTRUs and beams for UL BMs. The WTRU may receive SRS resource configuration and association with panel identifier (s). The WTRU may receive an SRS trigger message in the DCI (2702), triggering one or more SRS resource sets. Triggered SRS resource sets can trigger one or multiple WTRUs to trigger for one TRP or multiple TRPs and one beam, for example, for U-2 procedure, or multiple beams, for example, for U-3, within each triggered WTRU. The DCI of the trigger SRS may contain additional fields such as repetition, beam identifier or panel identifier (s) (2704) for the WTRU panel or beam definition.

To identify triggered panels (2706), the WTRU in an explicit DCI operation may contain a list of triggered WTRU IDs. In an implicit operation during SRS configuration, the WTRU may be configured with one or multiple SRS resource sets, where each resource set may be associated with one WTRU, or each resource may be associated with one WTRU. In any event, upon triggering any one SRS resource set, the WTRU may determine triggered WTRUs from the relationships of each triggered resource set or resource.

The WTRU may determine the triggered WTRUs by following the order of the triggered SRS resource sets. For example, a first triggered SRS resource set X may indicate a triggered WTRU board 1, and a second triggered SRS resource set Y indicates a triggered WTRU board 2. In another example, the SRS Initiated Resource Set ID indicates the WTRU panel ID, eg, set 1 indicates WTRU panel 1 and set 3 indicates WTRU panel 3.

To determine the swept beams for each triggered WTRU panel (2708), the repetition field may indicate whether the WTRU is performing a U-2 or a U-3 procedure. The beam identifier field may contain one or more DL RS identifiers such as SSBI or CRI, or UL RS identifiers such as SRI. If the beam identifier field contains a DL RS identifier, the beam range can be obtained based on the latest or previous DL beam measurements. If the beam identifier field contains a UL RS identifier, the range of beams can be derived from recent or previous measurements of the UL beam.

The sweep range of a beam can be determined explicitly based on geographic location relative to the specified beam. For implicit definition, the range can be determined from the list of rays. The WTRU may autonomously determine based on recent or prior DL or UL beam measurements using a set of beam range rules. In hybrid operation, RRC signaling can be used. The repetition and beam identifier fields may be present in whole or in part in the DCI. For example, both fields can be part of the DCI or configured as RRC parameters. When defining both WTRU panels and beams, the WTRU may perform UL beam sweeping (2710).

Network device, gNB, TRP, etc. can perform UL BM and estimate optimal beams based on beam quality metrics such as higher SINR, RSRP, Reference Reception Quality (RSRQ), L1-RSRP, L1-RSRQ, L1- SINR etc. The network element can then send the selected beam index to the WTRU by means of a beam indication such as SRI. The SRI can contain multiple SRI fields or an extension of an existing SRI field. The SRI may also include an explicit indication of the selected WTRU panel (s) or the transmitted single SRS resource associated with multiple panels. Once the WTRU receives one or more beam indications, such as SRIs, from the network, the WTRU may perform PUSCH transmission through multiple panels (2712).

In the examples provided in this document, TRP-specific beam preparation and panel-specific beam preparation can be performed together or separately. For example, when the WTRU is connected to two or more TRPs, any of the TRPs can separately perform panel-specific beam preparation, or even perform beam preparation on only one WTRU panel. Both TRPs can be configured to jointly perform UL beam preparation with one or multiple WTRUs.

The antenna or panel capabilities for each WTRU may be different and dynamic. To prevent interference, save power, or manage congestion, the network or WTRU may activate, deactivate, disable, or enable some of the WTRUs. If necessary, the information about the capabilities of the WTRU can be updated or synchronized with the network.

After the WTRU uses one or multiple SRS resource sets, one or multiple neighboring gNBs or TRPs may perform UL beam measurements. After measuring the SRS resource in each neighboring TRP, it may be necessary to indicate the optimal beam (s) for the WTRU. Independent indication, joint indication with maximum overall quality, or joint indication with minimum interference can be configured to determine the optimal TX UL beam (s). FIG. 19 neighboring TRPs with independent indication can independently measure SRS transmissions and indicate the optimal beam for each TRP independently in 1902.

For joint indication with the highest overall quality (case 2), neighboring TRPs may jointly measure SRS transmissions. As shown in FIG. 20, the network may indicate the best beam (s) for both TRPs so that the beam (s) are (are) reasonably reliable due to fast recovery or simultaneous transmission in 2002. For joint indication with minimal interference (case 3), neighboring TRPs can jointly measure SRS transmissions. As shown in FIG. 21, the network may indicate different optimal beams for different TRPs or different panels of the same TRP. The optimal beam (s) can (s) be selected so that the optimal beam (s) for one TRP or panel is (are) the worst, or least optimal beam (s) for another TRP or panels 2102 and 2104.

Independent indication and co-indication with minimal interference can be used for higher communication throughput, and associated beam pairs between the WTRU and one or multiple TRPs can be spatially separated enough to avoid interference. The joint indication with the maximum overall quality can be used for higher reliability and availability of the communication, and one common beam can be indicated by the WTRU, since the associated beam pairs between the WTRU and one or multiple TRPs can belong to the same TX UL beam.

One or more PUCCH-Spatial-relation-info lists may be configured for PUCCH links for the WTRU. For each configured PUCCH-Spatial-relation-info, new parameter (s) can be entered to differentiate the TX of the UL beam used for UL transmission from different WTRUs and to different TRPs of the same TRP or different TRPs. For example, a high level parameter such as PUCCH-TRP may be introduced to distinguish between associated beam pairs between the WTRU and different TRPs. In another example, one high level parameter, PUCCH ID, may be entered to indicate the beam used for the PUCCH transmitted from each WTRU.

One or more parameters can be configured for the WTRU. For example, if the mapping information between a particular WTRU and its associated TRP is known to the WTRU based on other configurations or signaling, one parameter may be sufficient to implement beam indication for PUCCH transmission for multiple TRPs or multiple panels transmissions.

One or more SpatialRelationInfo IEs can be included for each PUCCH-Spatial-relation-info. Each SpatialRelationInfo IE can be configured for a different WTRU or TRP, or for the same WTRU or TRP. When there are multiple PUCCH-Spatial-relation-info lists configured for the WTRU, only one SpatialRelationInfo IE in each PUCCH-Spatial-relation-info can be used to transmit UL at one time, and multiple SpatialRelationInfo IEs from different PUCCH-Spatial lists -relation-info can be used simultaneously for UL transmission. If a set of SpatialRelationInfo IEs are included in one PUCCH-Spatial-relation-info list, additional activation signaling such as MAC-CE or DCI can be used to specify spatial relationship information for a PUCCH resource for one of the entries in the PUCCH-Spatial-relation-relation list. -info. If only one of the PUCCH-Spatial-relation-info lists is configured for the WTRU, this may indicate that multiple WTRUs may share the same spatial relationship information. The SpatialRelationInfo IE in only one PUCCH-Spatial-relation-info can be specific to the WTRU.

A single SRI field may be used to indicate PUSCH when transmitting PUSCH transmissions from multiple WTRU antenna panels from the same spatial domain TX filter or UL beam TX. If PUSCH transmissions from multiple WTRU antenna panels are transmitted from different transmit filters in the spatial domain or TX UL beams, the PUSCH beam indication can be configured in different ways.

As shown in FIG. 22, to independently indicate the PUSCH beam for different WTRUs associated with a single TRP or multiple TRPs, separate SRS fields are part of the DCI signaling to independently indicate the beam used for PUSCH transmission for transmission 2202 via multiple TRPs or multiple panels. When PUSCH 2204 is shared, a single SRS field may be used to indicate one or more RSs or SRIs associated with the WTRU or UL list. In certain configurations, the WTRU panel, UL panel, or UL WTRU panel may be interchangeable. For PUSCH scheduled using 0_0 DCI format, etc. in a cell, the WTRU may transmit the PUSCH in accordance with the spatial relationship corresponding to the lowest identifier PUCCH resource in the active UL BWP with respect to each WTRU.

UL BM or UL beam preparation can be performed by associating the SRS resource set with the WTRU. In this configuration, an explicit panel indication may be required for the SRI because the network-measured SRS beam may have the same SRI from different SRS resource sets. If UL BM or UL beam preparation is performed by associating the SRS resource with the WTRU board, the board information may not be required. For example, at 2304, if the WTRU receives a beam indication with SRI # 2 and SRI # 3, the WTRU may simultaneously send a PUSCH from WTRU panel 1 and panel 2 in the following intervals. The specific beams from panel 1 and panel 2 may be known to the WTRU, and also since the WTRU itself determines which beam (s) are wobbled in the previous beam preparation process.

FIG. 24 illustrates an example of an SRS-based Beam Indication for PUSCH transmission via multiple panels. At 2402, four SRS resources may be associated with 2 WTRUs. At 2404, in accordance with higher layer parameters such as SRS-SpatialRelationInfo or DCI fields, each SRS resource may be associated with a specific beam within each WTRU. At 2406, when the WTRU receives the extended SRI fields (SRI # 2 and SRI # 3) from the network, it may be known that beam 3 from WTRU panel 1 and beam 1 from WTRU panel 2 are selected for future PUSCH transmissions. For simultaneous transmissions from multiple WTRUs, these fields may indicate one of two different configurations: where different data is transmitted from different panels; or where the same data is transmitted from different panels. FIG. 24, the WTRU can independently identify a panel or beam with limited information.

FIG. 25 shows an example of using TCI states to indicate a beam for PUCCH or PUSCH. Panel-specific UL beam selection for PUCCH or PUSCH can be based on DL RS. TCI states can also be used for selection. This avoids the use of SRS-based UL BMs, which can include significant beam swing delay, power consumption, and signaling overhead. This configuration can also reduce the number of active WTRUs at a given time, or reduce the header or signaling to achieve the minimum number of active WTRUs at a given time. At 2502, an active BPL can be configured for DL transmission between TRP1 and the WTRU and an active BPL for UL transmission between TRP2 and the WTRU. If simultaneous transmission from both WTRU panel 1 and panel 2 is not required, the WTRU can use one active panel at a given time to save power.

In 2502, track 2 of WTRU panel 2 may be specified for UL TX, while track 2 of WTRU panel 1 may be specified for DL RX. As shown in FIG. 26 with a table of examples of TCI entries for beam indication for PUCCH or PUSCH with respect to FIG. 25, if TCI state 3 is used to indicate a UL beam, CRI # 3 at TCI state 3 may indicate that WTRU board 1 beam 4 can be used for UL TX, which means that both UL TX and DL RX can be obtained from one WTRU panel 1. As a result, the WTRU board 2 can be turned off or deactivated for power saving purposes. At 2504, when the WTRU turns, both a TX UL beam and an RX DL indication may be required. If TCI state 4 is used to indicate a UL beam, the corresponding TX UL beam can be automatically updated upon completion of the DL beam indication.

Although the features and elements have been described above in specific combinations, it will be apparent to those skilled in the art that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein may be embodied in a computer program, software, or firmware embedded in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable media. Examples of computer-readable media include, but are not limited to, read only memory (ROM), random access memory (RAM), register, cache memory, semiconductor storage devices, magnetic media such as internal hard drives and removable disks, magneto-optical media. and optical media such as CD-ROMs and digital versatile discs (DVDs). The processor in combination with software can be used to implement an RF transceiver for use with a WTRU, UE, terminal, base station, RNC, and / or any host computer.

Claims (32)

1. Wireless transmit / receive module (WTRU), containing: transceiver; and CPU; moreover: the transceiver is configured to receive SRS resource configuration information; the transceiver is further configured to receive a trigger SRS message, beam indication information (beam ID), and panel identification (panel ID) in downlink control information (DCI), the trigger SRS message being for one or more SRS resource sets; the processor is configured to determine at least one WTRU panel based on the panel ID or SRS resource configuration information; the processor is further configured to determine at least one wobble beam for a specific at least one WTRU based on the beam ID information, the beam ID information including a start beam ID, a step size, an end beam ID, or a list of beam IDs, or the beam ID information indicates center and half range parameters; the processor is further configured to perform an uplink (UL) beam sweep using the defined at least one WTRU and the defined at least one swept beam; and the transceiver is further configured to receive one or more SRS resource indicators (SRIs) for at least two WTRUs related to physical uplink shared channel (PUSCH) transmission. 2. The WTRU of claim 1, wherein the at least one wobble beam is further determined based on the repetition field in the initiating SRS message in the DCI, or the last or previous downlink (DL) of the WTRU, or a UL beam measurement. 3. The WTRU of claim 2, wherein the repetition field indicates that the spatial domain transmit filter is enabled or disabled at the WTRU with respect to the WTRU performing U-2 or U-3 procedures. 4. The WTRU of claim 1, wherein the SRS resource configuration information includes information indicating the association of an SRS resource set from one or more SRS resource sets or an SRS resource with the WTRU. 5. The WTRU of claim 1, wherein the at least one WTRU is associated with a transceiver point (TRP) for multi-TRP operation, and the SRI is defined for a physical uplink shared channel (PUSCH). 6. The WTRU of claim 1, further comprising the following: the processor is configured to determine at least one wobble beam for a specific at least one WTRU based on beam ID information for one or more TRPs. 7. The WTRU of claim 1, further comprising the following: the transceiver is further configured to receive SRS field information for each portion of the uplink (UL) bandwidth (BWP) or multiple UL BWPs, wherein the SRS field information includes a plurality of subfields including SRS resource set field, SRS resource repetition field and a beam indication field that includes a center RS identifier field and a beam range field. 8. A communication method performed by a wireless transmit / receive unit (WTRU), including: receiving, by the WTRU, SRS resource configuration information; receiving, by the WTRU, a trigger SRS message, beam designation information (beam identifier) and panel identification (panel identifier) in downlink control information (DCI), the trigger SRS message for one or more SRS resource sets; determining, by the WTRU, at least one WTRU panel based on the panel identifier or SRS resource configuration information; determination by the WTRU of at least one wobbling beam for a specific at least one WTRU based on the beam ID information, the beam ID information including a start beam ID, a step size, an end beam ID or a list of beam IDs, or the beam identifier indicates the center and half range parameters; performing, by the WTRU, an uplink (UL) beam sweep using the at least one WTRU specific panel and the at least one specific swept beam; and receiving, by the WTRU, one or more SRS resource indicators (SRIs) for at least two WTRUs related to physical uplink shared channel (PUSCH) transmission. 9. The method of claim 8, wherein the at least one wobble beam is further determined based on a repetition field in the initiating SRS message in the DCI, or the last or previous downlink (DL) of the WTRU, or a UL beam measurement. 10. The method of claim 9, wherein the repetition field indicates that the spatial domain transmit filter is enabled or disabled at the WTRU with respect to the WTRU performing U-2 or U-3 procedures. 11. The method of claim 8, wherein the SRS resource configuration information includes information indicating the association of an SRS resource set from one or more SRS resource sets or an SRS resource with the WTRU. 12. The method of claim 8, wherein the at least one WTRU is associated with a transceiver point (TRP) for multi-TRP operation, and the SRI is determined for a physical uplink shared channel (PUSCH). 13. The method of claim 8, further comprising determining, by the WTRU, at least one swing beam for the specified at least one WTRU based on the beam ID information for the one or more TRPs. 14. The method of claim 8, further comprising receiving, by the WTRU, SRS field information for each portion of the uplink (UL) bandwidth (BWP) or multiple UL BWPs, wherein the SRS field information includes a plurality of subfields including a set field SRS resources, an SRS resource repetition field, and a beam indication field, which includes a center RS identifier field and a beam range field. 15. The method of claim 8, wherein sweeping the beam includes transmitting beams in a plurality of predetermined directions during an interval to determine at least one optimal UL transmission beam.

Images