TW201907680A - Unified beam management in a wireless network - Google Patents

Abstract

A wireless/transmit receive unit (WTRU) may receive configuration information that includes a reporting setting for beam measurement of multiple reference signals (RSs) and a transmission power offset between RSs. The WTRU may send a unified beam report when measured L1-RSRP of the RSs is above a threshold value and based on the transmission power offset.

Description

Unified beam management in wireless networks

CROSS- REFERENCE TO RELATED APPLICATIONS This application claims the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of the benefit of US Provisional Application No. 62/615,725 filed on Jan. 10, 2018, U.S. Provisional Application No. 62/565,341, filed on September 8, 2017, U.S. Provisional Application No. 62/555,755, U.S. Provisional Application No. 62/543,136, filed on August 9, 2017, and U.S. Provisional Application, filed on June 14, 2017 The contents of this application are hereby incorporated by reference herein.

Next-generation mobile communications include new radio (NR), enhanced mobile broadband (eMBB), massive machine type communication (mMTC) or ultra-reliable low-latency communication (URLLC). Both licensed and unlicensed spectrum bands are considered for next-generation mobile communications. NR communication can use channel status information-reference signals (CSI-RS) for beam management (BM). The NR may also use other RSs (e.g., synchronization signal (SS) blocks (SSB or SS blocks) or demodulation RSs (DMRS) associated with data and control channels, etc. for communication management and control.

The SS block and/or DMRS associated with the data and control channel can be used for Layer 1 (L1) / Layer 2 (L2) BM, because with periodic CSI-RS, the WTRU may not be able to detect A fast or sudden beam change caused by the motion or rotation of the WTRU or the like is detected. It would be desirable to configure a uniform BM for beam discovery, beam tracking and refinement or beam recovery, and the like.

A method and apparatus for performing unified beam management (BM) is provided. A unified BM can be implemented using multiple reference signals (RS). A unified BM framework can include unified configuration, beam management, and reporting and beam steering. A unified BM for multiple transmission/reception points (TRP), measurement and reporting, and beam report prioritization is also executable.

FIG. 1A is a diagram showing an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 can be a multiple access system that provides content for a plurality of wireless users, such as voice, data, video, messaging, broadcast, and the like. The communication system 100 can enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, communication system 100 can use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA). ), single-carrier FDMA (SC-FDMA), zero-tailed unique word discrete Fourier transform extended orthogonal frequency division multiple access (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filtering Multi-carrier group (FBMC) and so on.

As shown in FIG. 1A, communication system 100 can include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, radio access network RAN 104, core network CN 106, public switched telephone network (PSTN). 108. Internet 110 and other networks 112, however, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. For example, any of the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as "station" and/or "STA") may be configured to transmit and/or receive wireless signals and may include a user Equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, mobile phone, personal digital assistant (PDA), smart phone, laptop, small laptop, personal computer, wireless Sensors, hotspots or Wi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head mounted displays (HMDs), vehicles, drones, medical devices and applications (eg remote surgery), industrial devices and Applications (such as robotics and/or other wireless devices operating in industrial and/or automated processing chain environments), consumer electronic devices, and devices operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c, 102d may be referred to interchangeably as a UE.

Communication system 100 may also include base station 114a and/or base station 114b. Each of the base stations 114a, 114b can be configured to facilitate access to one or more communication networks (e.g., CN 106, Internet) through a wireless interface with at least one of the WTRUs 102a, 102b, 102c, 102d Any type of device of way 110 and/or other network 112). For example, the base stations 114a, 114b may be base transceiver stations (BTS), node B, eNodeB, local node B, local eNodeB, next generation node b (gNB), new radio (NR) node B, website control Site controller, access point (AP), wireless router, and so on. While each base station 114a, 114b is depicted as a single component, it should be understood that the base stations 114a, 114b can include any number of interconnected base stations and/or network elements.

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

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via an empty intermediation plane 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave , centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The empty intermediaries 116 can be established using any suitable radio access technology (RAT).

More specifically, as noted above, communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, to name a few. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 104 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA (WCDMA) to establish airborne Interface 116. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and/or High Speed Uplink (UL) Packet Access (HSUPA).

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and/or Advanced LTE (LTE) -A) and/or Advanced LTA Pro (LTE-A Pro) to establish an empty mediation plane 116.

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, where the radio technology may use a new radio (NR) to establish an empty intermediation plane 116.

In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a variety of radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c may collectively implement LTE radio access and NR radio access (e.g., using a dual connectivity (DC) principle). Thus, the null intermediaries used by WTURs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or communications to/from multiple types of base stations (e.g., eNBs and gNBs).

In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement the following radio technologies, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (ie, Wireless Fidelity (WiFi)), IEEE 802.16 (Global Interoperable Microwave Memory) Take (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM) Enhanced Data Rate (EDGE) for GSM Evolution, GSM EDGE (GERAN), and more.

The base station 114b in FIG. 1A may be a wireless router, a local Node B, a local eNodeB or an access point, and may use any suitable RAT to facilitate operations such as business premises, homes, vehicles, campuses, industrial facilities, air Wireless connections in local areas of corridors (such as for drones) and roads, etc. In an embodiment, base station 114b and WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In an embodiment, base station 114b and WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In still another embodiment, base station 114b and WTRUs 102c, 102d may establish picocells by using a cellular based RAT (eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) Or a femto cell. As shown in FIG. 1A, the base station 114b can be directly connected to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106.

The RAN 104 can communicate with the CN 106, wherein the CN can be configured to provide voice, data, applications, and/or Voice over Internet Protocol (VoIP) to one or more of the WTRUs 102a, 102b, 102c, 102d. Any type of network that serves. The data can have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. The CN 106 can provide call control, billing services, mobile location based services, prepaid calling, internet connectivity, video distribution, and the like, and/or can perform advanced security functions such as user authentication. Although not shown in FIG. 1A, it should be understood that RAN 104 and/or CN 106 may communicate directly or indirectly with other RANs that use the same RAT or a different RAT as RAN 104. For example, in addition to being connected to the RAN 104 using NR radio technology, the CN 106 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106 can also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include a circuit switched telephone network that provides Plain Old Telephone Service (POTS). Internet 110 may include the use of public communication protocols (e.g., Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP Internet Protocol suite). A system of globally connected computer networks and devices. The other network 112 may include a wired or wireless communication network that is owned and/or operated by other service providers. For example, the other network 112 can include another CN connected to one or more RANs, where the one or more RANs can use the same RAT or a different RAT as the RAN 104.

Some or all of the WTRUs 102a, 102b, 102c, 102d within the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple communications with different wireless networks over different wireless links) transceiver). For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with a base station 114a that uses a cellular-based radio technology, and with a base station 114b that can use an IEEE 802 radio technology.

FIG. 1B is a system diagram showing an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/trackpad 128, a non-removable memory 130, and a removable Memory 132, power source 134, Global Positioning System (GPS) chipset 136, and other peripheral devices 138, and the like. It should be appreciated that the WTRU 102 may also include any sub-combination of the aforementioned elements while remaining consistent with the embodiments.

The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with the DSP core, a controller, a microcontroller , Dedicated Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), and state machine. Processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although FIG. 1B depicts processor 118 and transceiver 120 as separate components, it should be understood that processor 118 and transceiver 120 can also be integrated into an electronic component or wafer.

The transmit/receive element 122 can be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the null intermediate plane 116. For example, in an embodiment, the transmit/receive element 122 can be an antenna configured to transmit and/or receive RF signals. As an example, in an embodiment, the transmit/receive element 122 can be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals. In still another embodiment, the transmit/receive element 122 can be configured to transmit and/or receive both RF and optical signals. It should be understood that the transmit/receive element 122 can be configured to transmit and/or receive any combination of wireless signals.

Although the transmission/reception element 122 is depicted as a single element in FIG. 1B, the WTRU 102 may include any number of transmission/reception elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmission/reception elements 122 (e.g., multiple antennas) that transmit and receive wireless signals over the null plane 116.

The transceiver 120 can be configured to modulate signals to be transmitted by the transmission/reception component 122 and to demodulate signals received by the transmission/reception component 122. As noted above, the WTRU 102 may have multi-mode capabilities. Accordingly, transceiver 120 may include multiple transceivers that enable WTRU 102 to communicate via multiple RATs (eg, NR and IEEE 802.11).

The processor 118 of the WTRU 102 may be coupled to a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may User input data from speaker/microphone 124, keypad 126, and/or display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) is received. The processor 118 can also output user profiles to the speaker/microphone 124, the keypad 126, and/or the display/trackpad 128. In addition, processor 118 can access information from any suitable type of memory, such as non-removable memory 130 and/or removable memory 132, and store the data in these memories. The non-removable memory 106 can include random access memory (RAM), read only memory (ROM), hard disk, or any other type of memory storage device. The removable memory 132 can include a Subscriber Identity Module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from the memory that is not physically located in the WTRU 102 and store the data in the memory. As an example, the memory may be located on a server or a home computer (not shown). )on.

The processor 118 can receive power from the power source 134 and can be configured to transmit and/or control power for other components in the WTRU 102. Power source 134 may be any suitable device that powers WTRU 102. For example, the power source 134 can include one or more dry battery packs (eg, nickel cadmium (Ni-Cd), nickel zinc (Ni-Zn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), solar cells, and Fuel cells and more.

The processor 118 may also be coupled to a GPS chipset 136 that may be configured to provide location information (eg, longitude and latitude) related to the current location of the WTRU 102. The WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) plus or in place of GPS chipset 136 information via null intermediaries 116, and/or upon receipt from two or more nearby base stations. Signal timing to determine its position. It should be understood that the WTRU 102 may obtain location information via any suitable positioning method while remaining consistent with the embodiments.

Processor 118 may also be further coupled to other peripheral devices 138, where the peripheral devices may include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, peripheral device 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photo and video), a universal serial bus (USB) port, a vibrating device, a television transceiver, a hands-free headset, a Bluetooth® mode. Group, FM radio unit, digital music player, media player, video game console module, internet browser, virtual reality and/or augmented reality (VR/AR) device, and activity tracker and many more. Peripheral device 138 can include one or more sensors. The sensor can be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, a position sensor, a proximity sensor, a temperature sensor, a time sensor, a geography Position sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors and/or humidity sensors, and the like.

The WTRU 102 may include a full-duplex radio for which some or all of the signals (e.g., associated with special subframes for UL (e.g., for transmission) and downlink (e.g., for reception) are associated with The reception or transmission of the connection may be parallel and/or simultaneous. A full-duplex radio may include signal processing through a hardware (eg, a choke) or via a processor (eg, a separate processor (not shown) or via processor 118) to reduce and/or substantially eliminate self-interference. Interface management unit. In an embodiment, the WTRU 102 may include half-duplex transmitting or receiving some or all of the signals (e.g., associated with a special subframe for UL (e.g., for transmission) or downlink (e.g., for reception). radio.

1C is a system diagram showing RAN 104 and CN 106, in accordance with an embodiment. As described above, the RAN 104 can communicate with the WTRUs 102a, 102b, 102c over the null plane 116 using E-UTRA radio technology. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include eNodeBs 160a, 160b, 160c, however it should be understood that the RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. Each of the eNodeBs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the null plane 116. In an embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNodeB 160a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a.

Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user queues in UL and/or DL Cheng and so on. As shown in FIG. 1C, the eNodeBs 160a, 160b, 160c can communicate with each other through the X2 interface.

The CN 106 shown in FIG. 1C may include an active management gateway (MME) 162, a service gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is described as being part of CN 106, it should be understood that any of these elements may be owned and/or operated by entities other than the CN operator.

The MME 162 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 142 may be responsible for verifying the users of the WTRUs 102a, 102b, 102c, bearer initiation/deactivation procedures, and selecting a particular service gateway or the like in the initial attach procedures of the WTRUs 102a, 102b, 102c. The MME 162 may provide control plane functionality for switching between the RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM or WCDMA.

SGW 164 may be coupled to each eNodeB 160a, 160b, 160c in RAN 104 via an S1 interface. SGW 164 can typically route and forward user data packets to/from WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane in the inter-eNB handover, triggering paging when the DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c, etc. Wait.

The SGW 164 can be coupled to the PGW 146, which can provide packet switching network (e.g., Internet) access to the WTRUs 102a, 102b, 102c to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices.

The CN 106 can facilitate communication with other networks. For example, CN 106 may provide WTRUs 102a, 102b, 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communication devices. For example, CN 106 may include or communicate with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server), and the IP gateway may act as an interface between CN 106 and PSTN 108. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.

Although the WTRU is described as a wireless terminal in Figures 1A through 1D, it should be appreciated that in certain representative embodiments, such terminals and communication networks may use (e.g., temporary or permanent) wired communications. interface.

In the representative embodiment, the other network 112 can be a WLAN.

A WLAN in an Infrastructure Basic Service Set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or have another type of wired/wireless network that interfaces with a distributed system (DS) or carries traffic and/or carries BSS. Traffic originating from the outside of the BSS to the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS can be sent to the AP for delivery to the corresponding destination. Traffic between STAs within the BSS may be sent by the AP, for example where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The amount of traffic between STAs within the BSS can be considered and/or referred to as point-to-point traffic. The point-to-point traffic can be sent between the source and destination STAs (eg, directly between them) with direct link setup (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs that are internal to the IBSS or that use the IBSS (eg, all STAs) may communicate directly with each other. The BSS communication mode can also be referred to as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure operating mode or a similar mode of operation, the AP can transmit beacons on fixed channels (eg, primary channels). The main channel can be a fixed width (eg, a 20 MHz bandwidth) or a dynamically set width via messaging. The primary channel can be the operational channel of the BSS and can be used by the STA to establish a connection with the AP. In a representative exemplary embodiment, carrier sense multiple access with collision avoidance (CSMA/CA) can be implemented (e.g., in an 802.11 system). For CSMA/CA, STAs including APs (eg, each STA) can sense the primary channel. If the special channel is sensed/detected and/or determined to be busy by the special STA, the special STA may back off. In a given BSS, there is one STA (for example, only one station) for transmission between any finger timings.

High throughput (HT) STAs can communicate using a 40 MHz wide channel (eg, by combining a 20 MHz main channel with a 20 MHz adjacent or non-adjacent channel to form a 40 MHz wide channel).

Ultra High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz and/or 160MHz. 40MHz and/or 80MHz channels can be formed by combining successive 20MHz channels. A 160 MHz channel can be formed by combining 8 consecutive 20 MHz channels or by combining two discrete 80 MHz channels (this combination can be referred to as an 80+80 configuration). For an 80+80 configuration, after channel encoding, the data can be passed through a segmentation parser that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing or time domain processing may be performed on each stream, respectively. The stream can be mapped on two 80 MHz channels and the data can be transmitted by the STA performing the transmission. At the receiver performing the received STA, the above operations for the 80+80 configuration may be reversed and the combined material may be sent to the Media Access Control (MAC).

802.11af and 802.11ah support the next 1 GHz (GHz) mode of operation. The channel operation bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. In accordance with a representative embodiment, 802.11ah can support meter type control/machine type communication (e.g., MTC devices in a macro coverage area). The MTC device may have certain capabilities, such as including limited capabilities to support (e.g., only support) certain and/or limited bandwidth. The MTC device can include a battery and the battery life of the battery is above a threshold (eg, to maintain a very long battery life).

A WLAN system that can support multiple channels and channel bandwidths (eg, 802.11n, 802.11ac, 802.11af, and 802.11ah) includes channels that can be designated as primary channels. The bandwidth of the primary channel may be equal to the maximum shared operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by the STA, where the STA is derived from all STAs operating in the BSS supporting the least bandwidth mode of operation. In the example of 802.11ah, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth modes of operation, support (eg, only support) 1 MHz mode STAs For a device such as an MTC type, the width of the main channel can be 1 MHz. Carrier sensing and/or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy (because the STA (eg, 1 MHz mode of operation STA) transmits to the AP), then the entire available frequency band can be considered busy even though most of the frequency bands remain idle and available for use.

In the United States, the available frequency band available for 802.11ah is 902 MHz to 928 MHz. In Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5 MHz to 927.5 MHz. According to the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.

FIG. 1D is a system diagram showing RAN 104 and CN 106, in accordance with an embodiment. As described above, the RAN 104 can communicate with the WTRUs 102a, 102b, 102c over the null plane 116 using NR radio technology. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include gNBs 180a, 180b, 180c, but it should be understood that the RAN 104 may include any number of gNBs while remaining consistent with the embodiments. Each gNB 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c via the null plane 116. In an embodiment, gNBs 180a, 180b, 180c may implement MIMO technology. Moreover, for example, gNBs 180a, 180b, 180c may use beamforming processes to transmit and/or receive signals to and/or from gNBs 180a, 180b, 180c. Thus, for example, gNB 180a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, WTRU 102a. In an embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, gNB 180a may transmit multiple CCs (not shown) to WTRU 102a. A subset of these CCs can be on the unlicensed spectrum, while the remaining CCs can be on the licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement Cooperative Multipoint (CoMP) technology. For example, the WTRU 102a may receive cooperative communications from the gNBs 180a and gNBs 180b (and/or gNBs 180c).

The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using communications associated with the scalable parameter configuration. For example, the OFDM symbol spacing and/or the OFDM subcarrier spacing (SCS) may be different for different communications, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may use subframes or transmission time intervals (TTIs) having different or scalable lengths (e.g., containing different numbers of OFDM symbols and/or continuing different absolute time lengths) to communicate with the gNB 180a, 180b, 180c communicate.

The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c in a discrete configuration and/or a non-discrete configuration. In a separate configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c). In a separate configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a separate configuration, the WTRUs 102a, 102b, 102c may use signals in the unlicensed band to communicate with the gNBs 180a, 180b, 180c. In a non-discrete configuration, the WTRUs 102a, 102b, 102c may communicate/connect with the gNBs 180a, 180b, 180c while communicating/connecting with another RAN (e.g., eNodeBs 160a, 160b, 160c). For example, the WTRUs 102a, 102b, 102c may implement one or more of the gNBs 180a, 180b, 180c and one or more of the eNodeBs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principles. Communicate. In a non-discrete configuration, eNodeBs 160a, 160b, 160c may act as mobility anchors for WTRUs 102a, 102b, 102c, and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput to be WTRU 102a , 102b, 102c provide services.

Each gNB 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and/or DL, network truncation Support, dual connectivity, interworking between NR and E-UTRA, user plane data routed to user plane functions (UPF) 184a, 184b, and route to access and mobility management functions (AMF) 182a , 182b control plane information and so on. As shown in FIG. 1D, the gNBs 180a, 180b, 180c can communicate with each other through the Xn interface.

The CN 106 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possibly a data network (DN) 185a, 185b. While each of the foregoing elements is described as being part of CN 106, it should be understood that any of these elements may be owned and/or operated by other entities than the CN operator.

The AMFs 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, AMFs 182a, 182b may be responsible for authenticating users of WTRUs 102a, 102b, 102c, supporting network truncation (e.g., handling different protocol data unit PDU sessions with different needs), selecting special SMFs 183a, 183b, managing registration areas. , terminate non-access layer (NAS) messaging, as well as mobility management and more. The AMFs 182a, 1823b may use network cuts to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. For example, different network cuts can be established for different use cases, such as services that rely on ultra-reliable low-latency communication (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access. And/or services for MTC access, etc. The AMFs 182a, 182b may provide other RANs (not shown) for use in the RAN 104 with other radio technologies (e.g., LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi). Control plane function for switching between.

The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 106 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 106 via an N4 interface. The SMFs 183a, 183b can select and control the UPFs 184a, 184b, and can configure traffic routing through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing down-link data notifications and the like. The PDU session type can be IP based, non IP based, Ethernet based, and the like.

The UPFs 184a, 184b may be coupled to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, such that the WTRUs 102a, 102b, 102c may be provided to a packet switched network (e.g., the Internet 110). Access to facilitate communication between the WTRUs 102a, 102b, 102c and the IP-enabled device. The UPFs 184, 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, and providing mobility anchoring, etc. .

The CN 106 can facilitate communication with other networks. For example, CN 106 may include, or may be in communication with, an IP gateway (eg, an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and CN 108. 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 operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may connect to the local DN 185a via UPFs 184a, 184b via an N3 interface to UPFs 184a, 184b and an N6 interface between UPFs 184a, 184b and DNs 185a, 185b, 185b.

In view of Figures 1A through 1D and the corresponding descriptions of Figures 1A through 1D, one or more or all of the functions described herein for one or more of the following may be performed by one or more analog devices (not Displayed to perform: WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMF 183a- b. DN 185 ab and/or any other device described herein. These analog devices may be one or more devices configured to simulate one or more or all of the functions described herein. For example, these analog devices can be used to test other devices and/or analog network and/or WTRU functions.

The simulation device can be designed to implement one or more tests on other devices in a laboratory environment and/or an operator network environment. For example, one or more analog devices may perform one or more or all of the functions while being implemented and/or deployed in whole or in part as part of a wired and/or wireless communication network to test other devices within the communication network. The one or more analog devices may perform one or more or all of the functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The analog device can be directly coupled to another device to perform the test, and/or can perform the test using over-the-air wireless communication.

One or more analog devices may perform one or more functions including all functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the simulation device can be used in a test lab and/or in a test scenario of a wired and/or wireless communication network that is not deployed (eg, tested) to perform testing of one or more components. The one or more analog devices can be test devices. The analog device can transmit and/or receive data using direct RF coupling and/or wireless communication via an RF circuit (which, by way of example, may include one or more antennas).

For sub-6 GHz transmissions, multiple antenna configurations (such as Multiple Input Multiple Output (MIMO), Single Input Multiple Output (SIMO), or Multiple Input Single Output (MISO), etc., can increase the wireless data rate. Different MIMO configurations can provide diversity gain, multiplex gain, beamforming or array gain, and the like. When multiple WTRUs are communicating with a single central node, MU-MIMO may increase system throughput by transmitting multiple data streams to different WTRUs at the same time and on the same or overlapping set of resources in time and frequency. In single-user MIMO (SU-MIMO), the same central node can stream multiple streams of data to the same WTRU instead of transmitting to multiple WTRUs as in multi-user MIMO (MU-MIMO). Multi-antenna transmissions on millimeter wave frequencies may differ from sub-antenna configurations of 6 GHz. The reason for this may be because the propagation characteristics at the millimeter wave frequency are different or the BTS or WTRU has a different number of RF chains from the antenna elements and the like.

For multi-antenna, MIMO or other configurations, beam reporting, beam fault detection or new candidate beam identification are desirable when using multiple RSs for beam management (BM). While the dynamic availability and uniform use of multiple RSs (RSs) for BM can provide resource flexibility and efficient use, it is desirable to be able to efficiently discover and determine beam quality from measurements based on different RSs, This avoids beam-level ping-pong efficiency, TRP or gNB-level ping-pong effects, and the like.

A unified downlink (DL) BM can perform beam measurements and reporting using different RS configurations. Beam measurements and reports can be based on RS, Channel State Information-RS (CSI-RS), Synchronization Signal (SS) blocks, or Demodulated RS (DMRS), and the like. In any of the examples given herein, the SS block can be transmitted as an SS/PBCH block together with a Physical Broadcast Channel (PBCH). In some configurations, SSB, SS blocks, SS-blocks, or SS/PBCH blocks are used interchangeably. In the example given here, the report processing can use a joint beam report or an independent beam report. Further, the unified beam indication can include a mapping between an actual transmission configuration indicator (TCI) state and an N-bit TCI status field. The unified beam indication may include a quasi-co-location (QCL) indication across multiple component carriers (CCs). The unified beam indication can also be used to optimize processing using a TCI state, a spatial QCL reference update in a TCI state, or a uplink (UL) beam indication, and the like.

Figure 2 is an example 200 of a transmit/receive point (TRP) and WTRU antenna model. The massive antenna model can be configured as Mg antenna panels in each vertical dimension and Ng antenna panels in each horizontal dimension. Each antenna panel can be configured to have N rows and M columns of polarized or non-polarized antenna elements. Timing and phase cannot be calibrated across panels. Multiple panels can be configured in the same eNB. According to the operating frequency bands given in Table 1, the base antenna configuration may be different. Table 1

The precoding process at the millimeter wave frequency can be digital, analog, digital and analog or mixed digital and analog, and the like. Digital precoding processing can be combined with equalization processing and can be used for SU, MU, and multi-cell precoding processing. The digital precoding process is similar to the digital precoding process used in sub 6 GHz (eg, in IEEE 802.11n, 802.11x, 3GPP LTE, 4G or 5G, etc.). However, in millimeter wave frequencies, the limited number of RF chains present compared to antenna elements, as well as the sparse nature of the channels, may require different digital beamforming configurations.

Due to the limited number of RF chains, the analog beamforming process can be configured to have an analog phase shifter on each antenna element. In IEEE 802.11ax or 802.11ad or the like, in a sector-level scanning procedure for identifying an optimum sector, in a beam refinement procedure for refining a sector to an antenna beam or for use in a beam refinement procedure for refining a sector to an antenna beam The analog beamforming process can be configured in a beam tracking procedure that temporally adjusts the sub-beams to account for any changes in the channel procedure. In hybrid beamforming, the precoder can be divided between an analog domain and a digital domain. Each domain can use precoding processing and can combine matrices with different structural constraints, such as constant modulus constraints for combining matrices in the analog domain. Although limited by the number of RF chains, hybrid beamforming processing can achieve high digital precoding processing performance due to the sparse nature of the channel, multi-user multiplex processing or multi-stream multiplexing processing.

As the frequency increases, the channel may have higher path loss and more abrupt changes. In the high frequency band, a large-scale antenna array is used for high beamforming gain, thereby solving high propagation loss. Using directional beam based communication may require accurate beam pairing. The beam direction is likely to be associated with the channel in terms of the angle of arrival and the angle of departure in the azimuth and elevation. The beam direction can be dynamically adjusted as the channel changes.

As an example, the beam management program can include DL and UL beam management procedures. The downlink beam management program can be referred to as P-1, P-2, P-3, and the like. In some configurations, P1 and P-1, P2 and P-2, and P3 and P-3 are used interchangeably. The uplink beam management program can be referred to as U-1, U-2, U-3, and the like. The first downlink sensor management procedure (e.g., P-1) can be used for WTRU measurements on different TRP TX beams (e.g., to support selection of TRP TX beams or WTRU RX beams). P-1 may include a TX beam scan between TRP internal or TRP originating from a different set of beams (eg, for beamforming processing at TRP). P-1 may also include WTRU RX beam scanning operations originating from a different set of beams (e.g., for beamforming processing at the WTRU). In some configurations, the TRP TX beam and the WTRU RX beam may be jointly or sequentially determined.

In an example, a second downlink beam management procedure (e.g., P-2) can be used for WTRU measurements of different TRP TX beams. P-2 may be a scenario for changing the P-1 between one or more TRP internals or between TRPs (eg, from a smaller set of beams than P-1 for beam refinement). Moreover, as an example, when the WTRU uses beamforming processing, a third downlink beam management procedure (e.g., P-3) can be used for WTRU measurements on the same TRP TX beam to change the WTRU RX beam.

In the example given here, a first uplink beam management procedure (e.g., U-1) can be used to enable TRP measurements on different WTRU TX beams to support one or more WTRU TX beams or one or Selection of multiple TRP RX beams. A second uplink beam management procedure (e.g., U-2) can be used for TRP measurements on different TRP RX beams to change or select one or more RX beams between or within the TRP. A third uplink beam management procedure (e.g., U-3) can be used to enable TRP measurements on the same TRP RX beam in order to change the WTRU TX beam.

In the example given here, a DL L1 or L2 BM procedure for selecting a TRP TX or WTRU RX beam may be configured within one or more TRPs. Programs P-1, P-2 or P-3 for beam selection, TX beam refinement, RX beam change or TRP TX and WTRU RX beam scanning may be configured or used. The WTRU-triggered beam failback operation, WTRU-specific beam group based reporting processing, and CSI-RS configuration for TX or RX beam scanning for the BM can also be used.

Figure 3 is an example 300 of an SS burst and multiple SS blocks. The SS block may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). In 300, SS bursts can be configured for a period of x milliseconds, as well as multiple SS blocks 1, 2, ... N in an SS burst.

The mechanism of the network controlled BM for UL transmission can be configured. For example, in 300, SS bursts can be used when multiple beams are used for initial access. One or more SS blocks in the SS burst may be associated with one or more beams, and the number of SS blocks in the SS burst may be determined by the gNB based on the number of transmit beams. In an example, if N beams are configured on the gNB, then N SS blocks can be used or transmitted in the SS burst. The SS block can be configured with relatively less resources than the WTRU-specific CSI-RS, using less messaging burden, and having low interference. For OFDMA-based networks, WTRU communications within cells may be mutually orthogonal, and inter-cell interference (especially near cell boundaries) may be the primary source of interference. In the example given here, the transmission power of the CSI-RS or SS block can be changed or adapted for inter-cell interference coordination, interference mitigation or flexible cell coverage, and the like.

Figure 4 is an example 400 of a measurement model for a unified BM. A DL unified BM may use multiple available RSs, such as WTRU-specific CSI-RS, SS blocks, or DMRS (when PDCCH or PDSCH associated with one RS or multiple RSs is configured), and the like. These reference signals can be used by the WTRU for beam measurement and reporting. For high frequency NR systems configured with SS blocks and DMRS beamforming transmissions, the reference signals can be used to assist CSI-RS based BM procedures for beam discovery, beam tracking, beam refinement or beam recovery, etc. (eg P-1, P-2, P-3). DMRS can provide early detection and accurate prediction of beam faults.

In 400, gNB beams 1 through K can be input as signal A into layer 1 filter component 402 and output as A ¹ . The RRC parameters and signal A ¹ may be input to the beam combining/selecting component 404. The K beam or signal A ¹ and RRC parameters can also be input to the L3 beam filtering component 406 and output at the signal E. This signal E can be input to the beam selection component 408 for reporting along with the RRC parameters to generate a signal F of X beams. The output signal B and RRC parameters may be processed by a layer 3 filtering component 410 for cell quality to generate a signal C. The signal C and C ¹ may be processed at the reporting criteria evaluation component 412 to generate the signal D.

Figure 5 is an example 500 of using multiple RSs for a unified BM. During the SS burst period 502, the TRP or gNB may transmit SS blocks 1-3 and CSI-RS 1-4 of the RS for reception by beam 506. The WTRU-specific CSI-RS period (504) may be a period of time during which the TRP or gNB may transmit CSI-RS 1-4 or PDCCH. The RS may include CSI-RS, SS block or DMRS, whereby they are available at different time instances when transmitted with the PDCCH or PDSCH.

The WTRU may perform measurements on the SS block to perform fast beam discovery processing and establish a coarse beam pairing link (BPL) for the BM procedure P-1. Further, in a configuration in which an SS block can be configured to transmit with a wider beam than a CSI-RS, a process of covering a scan area using a beam smaller than a CSI-RS is achievable. This configuration may also reduce the beam scanning delay, load or resource usage of the CSI-RS, and may reduce excessive inter-cell interference for the WTRU-specific CSI-RS (because the SS block may be always on without WTRU-specific configuration) signal of).

Based on measurements at different SS blocks (eg, RS Received Power (RSRP) or RS Receive Quality (RSRQ), etc.), the WTRU may select N(N>=1) comparisons based on certain predefined or configured rules. Good SS block. For example, the preference may be a block with the best N RSRPs reported to the TRP or gNB.

A WTRU in RRC connected mode may aperiodically transmit measurements on a physical uplink shared channel (PUSCH) or a short physical uplink control channel (PUCCH), such as layer 1 - RSRP (L1-RSRP), beam resource indicator, CSI Resource Index (CRI) or Synchronization Signal Block (SSB) index and so on. In some configurations, the CRI may be a CSI-RS resource indicator, a CSI-RS resource index, a CSI resource index, or a CSI identifier or indicator (ID), and the like. In some configurations, the SSBRI may be an SSB resource indicator, an SSB index, an SS/PBCH resource indicator, an SS/PBCH resource index, an SS block identifier or an indicator or index (ID), or an SSB ID, and the like. The measurement results can also be piggybacked on the data, multiplexed with the data, or periodically fed back on PUCCHs with different formats. Different PUCCH formats may include a regular format, an extended format, a long PUCCH, or a short PUCCH, etc., based on the size or number of measurements. At a certain time duration, if the WTRU is fast acting, the measurement may be passed in a semi-permanent report if at least one serving beam quality falls below a certain threshold, or if at least one of the measured beams has a high quality threshold For at least one service beam, etc., the measurement results can be passed in an event-triggered report. In any of the examples given here, the event trigger can be based on a timer, an RS specific timer or a threshold, and the like.

A WTRU in RRC idle or inactive mode may pass measurement results through a Physical Random Access Channel (PRACH) preamble, PRACH message 3 or higher layer messages, and the like. The WTRU may perform random access using a particular RACH resource, a particular RACH preamble transmitted in a particular subband, and a symbol associated with the selected one or more SS blocks. The WTRU may identify the TRP or gNB TX beam associated with the SS block by the SS block time index. In addition, one or more SS blocks and a subset of RACH resources or a preamble index may be sent to or known by the WTRU in System Information (SI). The one or more SS blocks and the RACH resource subset or the preamble index subset may also be transmitted to the WTRU through a dedicated signal in the previous connected mode. In addition, idle or inactive WTRUs may select a subset of RACH resources for the selected RACH preamble subset in step 1 of the RACH procedure. The TRP or gNB may implicitly derive the beam ID selected at the WTRU from the RACH resource or preamble and may use it as a DL TX beam in step 2 of the RACH procedure.

The WTRU for connected mode can configure dominant BM and reporting. For a connected mode WTRU, report feedback containing beam quality information for the selected SS block can be sent directly back to the TRP or gNB.

Once the TRP or gNB receives the RACH preamble from the WTRU in idle or inactive mode, or receives a measurement report from the WTRU in connected mode, then the better SS block measurement will be known. The TRP or gNB may form M (M>=1) fine or narrow beam CSI-RSs such that the aggregate coverage of M fine or narrow beams and one or more SSs selected by the TRP or gNB from the reported SS blocks The blocks match. With feedback from the WTRU based on the measured SS blocks, the newly formed fine or narrow beams used to carry the CSI-RS may include a subset of possible DL beams of the TRP or gNB. This can reduce beam scanning latency, power, power consumption, and interference by avoiding the use of a large number of CSI-RS beams to cover a particular coverage area.

Based on measurements of the newly formed fine or narrow CSI-RS beams, the WTRU may further refine the serving BPL between the WTRU and the TRP or gNB for use in the BM procedure P-2 or P-3. Beam refinement can be performed on a non-periodic CSI-RS. The service BPL between the WTRU and the gNB or TRP may be periodically monitored or reported in the event of service BPL quality degradation due to channel fluctuations or WTRU mobility, rotation or speed, and the like.

The service BPL monitoring or tracking process can use periodic or aperiodic RS. For WTRU-specific periodic CSI-RS and SS blocks, if the period is long, they may not be able to track or acquire frequent or sudden channel changes. An example of such a scenario due to the WTRU may not be able to detect or acquire beam quality information in time is given herein. Aperiodic signals (such as DMRS) can also be used for BM. Multi-beam transmission for control channels can improve the reliability of control signals. Based on measurements of the DMRS associated with the multi-beam PDCCH or PDSCH, one or more new candidate beams for the BM can be measured and identified using DMRS resources transmitted with the control channel or data channel.

In order to maintain the performance of the serving BPL, the WTRU may maintain a candidate BPL list, whereby if the serving BPL quality is degraded, the WTRU may quickly find another BPL. Candidate BPL list updates can use frequent RS measurements. Since CSI-RS and SS blocks may not be available, DMRS associated with control channels or data control may be used. Since the DMRS is transmitted on a beam that can be used for subsequent data or control information, and the measurement results for the DMRS can represent accurate beam quality information, it is desirable to use the DMRS to update the candidate BPL list.

Figure 6 is an example 600 of a signal flow for unifying BM. The TRP or gNB may send Scan SS blocks 1-3 to the WTRU (602). The WTRU may perform measurements on the discovered SS blocks (604), and for the connected mode, the WTRU may report the results on the PUCCH (606). For a WTRU in idle or inactive mode, a 4-step or 2-step RACH procedure can be performed, an RRC connection is established, and a coarse BPL is established (608). The TRP or gNB may form M fine or narrow CSI-RS beams (610) for the coverage area. The newly formed CSI-RS1-4 beam can be transmitted (612) to the WTRU. The TRP or gNB and the WTRU may perform beam refinement through beam management P-2 or P-3. The TRP or gNB may indicate to the WTRU the DMRS information of the control channel or data channel on other candidate beams (616). The TRP or gNB may transmit the PDCCH or PDSCH over multiple beams (618). The WTRU may use the configured UI information to perform measurements on the DMRS, obtain corresponding beam quality information, and update the candidate BPL list (620).

In 600, if the blocking of the serving BPL is detected and cannot be recovered (622) from the candidate BPL list (eg, due to a sudden channel change), UE measurements can be initiated on the discovered SS blocks and the signal flow flow repeated. (624). Also, when a beam failure is detected, the SS block signal can be used to quickly find the rough BPL. If beam reciprocity is applicable, the SS block can be used to perform beam discovery processing for the UL BM.

The dynamic availability or uniform usage of multiple signals for the BM may include configurations for finding or determining beam quality from measurements from different RSs. For example, RSRP can be used as a measure of multiple RSs in order to perform BM. Beam measurements for different signals can have different characteristics. For example, if a wide beam is used to transmit SS blocks and a narrow beam is used to transmit CSI-RS, it is possible to generate different beam RSRP, SS block RSRP or CSI-RS RSRP values due to different beamforming gains. . In addition, the WTRU may use different spatial filtering processes when receiving different RSs (eg, wide WTRU RX beams for SS blocks or narrow WTRU RX beams for CSI-RS, etc.).

Frequent candidate BPL updates can be configured in the manifest to keep the list current. Different numbers of samples and quality of candidate BPLs on similar or different signals may be used due to different frequencies of different signals, different periodicities and configurations of SS blocks and CSI-RS, or random use of PDCCH and PDSCH, and the like. Take an average, update, or perform a similar operation. This can be configured to avoid fluctuations in the quality ranking in the candidate BPL list.

Figure 7 is an example 700 of a WTRU acting in overlapping coverage of two narrow beams. In 700, in a single NR TRP or NR gNB configuration, the WTRU may be within coverage of multiple beams, SS blocks 3-5, and CSI-RS 6-11/PDCCH 6-11. When the WTRU is located at a location A near the middle of the narrow beam 11, a serving beam quality (eg, an L1-RSRP above a certain threshold) may be sufficient, and the WTRU may be configured to skip adjacent beams 6-10. measuring.

Figure 8 is an example 800 of a beam level ping-pong effect. The WTRU may experience undesired beam-level ping-pong effects due to the use of multiple types of RSs. In Figure 7, this effect may occur when the WTRU shuttles between narrow beams 10 and 11. When transmitting DMRS using PDCCH or PDSCH, the serving DL TX beam of the WTRU may be the narrow beam 11 in FIG. 7 based on beam measurement at time t0. From time t1 to time t2, the WTRU may move from location A to B to enter overlapping coverage of narrow beams 10 and 11, and the quality of service beam 11 may fall below a certain threshold. The WTRU may be triggered by an event (eg, if service beam quality <Th1) to initiate a candidate DL TX beam update procedure and begin measuring nearby RSs (eg, SS blocks), thereby searching for potential beams if service beam quality continues to degrade .

After the SS block based measurement, the WTRU may send the result to the NR TRP or gNb, which triggers and transmits the aperiodic CSI-RS on several fine or narrow beams. For example, if the WTRU is in coverage that is not transmitting on beam 11, the CSI-RS may be transmitted on narrow beam 10 since the reported SS block based measurements did not trigger CSI-RS transmission. Since the quality of the current serving beam 11 (e.g., L1-RSRP) may be derived from the previous DMRS signal without the current update, the beam 10 will have a higher L1-RSRP measurement from the newly formed CSI-RS signal. . Furthermore, since beam 10 becomes a new DL TX service beam, a new BPL can be established between the WTRU and the TRP. Beam switching from beam 11 to beam 10 is likely to occur due to quality changes based on different RS, DMRS or CSI-RS, and the like.

If the WTRU is outside the middle of beam 10 and the measured quality of beam 10 is insufficient or above a threshold, the WTRU may discover or track adjacent beams by measuring SS blocks or the like. The TRP or gNB can configure a set of CSI-RS beams with beams 11 based on new or recently reported SS block measurements. The WTRU may determine that the measured L1-RSRP value of beam 11 has a higher value and switch back to using beam 11 as a new DL TX beam.

Undesired switching between beam 10 and beam 11 may indicate beam level ping-pong switching. Beam-level ping-pong switching occurs because of quality comparisons between different or identical beams based on measurements from different signals, where the absolute quality value may be if it is measured or determined by transmitting a different RS different. Beam-level ping-pong effects can be mitigated by pre-defining, specifying, or configuring a set of measurement settings. The measurement configuration settings may include at least one RS, one or more trigger conditions or rules for measurement and reporting, respectively (eg, unified L1 (L1-Unified) or RS-RSRP below a threshold), unified formula, or beam report format and many more. You can also configure related parameters, thresholds or offset values, and more. The maximum number of measurement settings for a cell can be dynamic or pre-configured. The measurement settings may be WTRU-specific, based on WTRU group or cell-specific, etc., thereby reducing burden or network traffic.

A WTRU group may be set or configured as a plurality of WTRUs having similar attributes associated with beam level ping-pong effects. For example, multiple WTRUs that are within the same cell but have similar or different QoS requirements may form a WTRU group that may be used for WTRU group based configuration. For a group of WTRUs that require higher energy efficiency, the measurement period may be relatively long since the beam quality around the WTRU group may be stable. For groups of WTRUs with randomization or higher mobility/rotation, the measured higher frequencies or densities can be configured for enhanced or fine beam tracking.

A WTRU may be configured with one or more measurement configuration sets, and each set may be triggered by a pre-defined, specified, or configured measurement event. For example, a WTRU may have multiple applications that operate simultaneously with diverse QoS requirements (eg, latency, throughput, or reliability, etc.). The WTRU may switch between different states (eg, a power saving state, a high performance state, or a high speed state, etc.), each having a different QoS requirement. Thus, the WTRU may be configured for multiple configuration sets of different QoS requirements associated with different states.

By configuring one or more specific measurement settings, the WTRU may perform beam measurements and reporting based on one RS or multiple RSs (with comparable beam quality and flexible availability of different RSs). The measurement configuration can be implemented by higher layer communication, RRC communication, lower layer communication, media access control-control element (MAC-CE) or DCI, and the like.

An example of a beam measurement configuration that can reduce the beam level ping-pong effect is given in Tables 2 and 3. As an example, when the quality of the serving beam satisfies certain conditions, beam measurements within the TRP or within the gNB may be skipped, thereby conserving energy or avoiding undesired beam switching that may result in beam level ping-pong effects. Furthermore, when more samples for the RS type are desired, short-term channel fluctuations may result in changes in the quality of the measured one or more beams, and GracePeriodForMeasurement may be used. In addition, the beam-level ping-pong effect can be mitigated by setting a threshold such that the signal-to-noise ratio (SNR) or energy of the target beam or link is X dB higher than the service beam or link. A higher X will reduce the ping-pong effect (the cost of higher latency or delay for beam switching). Table 2 table 3

As shown in Table 2, two sets of measurements can be configured here, where each set of measurements can include a set ID (identifier or indicator), a trigger event or a measure set body, and the like. The measurement set body in Table 3 can specify how the configured WTRU performs beam measurements or how to report measurement information. The type of signal that the WTRU may measure may be indicated by a binary bit. For example, 1 (or 0) may indicate ON or be used, and 0 (or 1) may indicate OFF or not used. In Table 3, 1100 may indicate that an RS, CSI-RS, or SS block is used, which may be indicated by bit 1. At least one RS can be indicated with an ON state, thereby ensuring that the BM is correctly executed. When an RS is enabled or indicated as having ON (eg, only SS blocks or only CSI-RS), the WTRU may be configured to perform L1-RSRP beam measurements and reporting based on this RS.

The binary bit can be used to indicate the amount of measurement measured by the WTRU. For example, 1 (or 0) can indicate ON or be used, and 0 (or 1) can indicate OFF or not used. In Table 3, the bit map 10 may indicate that an RSRP value is used, which may be indicated by bit 1.

Layer 1 filtering can be configured to use a measurement averaging operation. The averaging operation may be WTRU-specific and may be based on performance requirements, such as energy or delay for different situations (eg, internal to TRP, between TRP, or internal to frequency, etc.). Large fluctuations between different measurement samples can be reduced by using time domain averaging operations, and some configurable coefficients can be sampling frequencies (eg, one sample per ms or the number of samples before the averaging operation, etc.).

Due to delays and power consumption, the WTRU may be configured to measure a limited number of beams for different situations (eg, within TRP, between TRP or within frequency, etc.), and report measurements on a limited number of beams. For example, beams with the N highest quality can be reported, thereby minimizing the burden of messaging. The duration of the configurable time for measurements that will be valid, used, and expired. Higher durations will be more stable or reliable, but will not result in fast channel or beam quality variations.

When multiple types of RSs are configured, the same beam may have different representative values due to different beam characteristics originating from different RSs. For example, time resources, frequency resources, the number of symbols used, or different sub-bands, etc., can be used in different ways for the RS. In the case of different characteristics, if a single beam quality value is required before reporting, a beam quality information combination spanning different measured RSs can be configured.

Referring again to Table 3, the unified beam reporting format can use a weighted action averaging operation as a uniform formula and can be configured for weighting coefficients for different RSs. When configuring a unified report, the parameters β1, β2, β3, and β4 may be different configurable weighting coefficients for different RSs. When configuring an independent report, the parameter μ1 can be a configurable weighting factor for a different RS. If beam measurements from different RSs are available and a uniform value is to be produced, then a configurable unified formula can be used to combine multiple measurements into a single value. If a uniform value is not generated, independent reports or measurements on beam quality from different RSs can be generated and reported while the associated report trigger is met.

The unified formula can be adjusted for the WTRU and configured for U for different beam measurement reports. Referring to the unified formula in the unified beam reporting format in Table 3, when an RS is configured to the WTRU for beam measurement reporting (eg, only SS block or CSI-RS only) and the Boolean value is true, a weighting coefficient β1 may It is configured as a positive value and a non-zero value, while other weighting coefficients β2, β3 or β4, etc. can be configured to be zero. If the Boolean value is false, then a similar procedure can be performed.

When multiple RSs are configured to the WTRU for beam measurement and reporting, the combined beam measurement report and the independent beam measurement report can be used simultaneously. For joint beam measurement reports, a pseudo-bullet value and different weighting coefficients β1, β2 or β3 with non-zero values, etc., can be used to generate uniformity from beam measurements on different RSs (eg, SS blocks or CSI-RS). value. For independent beam measurement reports, the Boolean values in this example can be configured to be false, whereby measurements from different RSs are reported in an independent rather than a joint manner.

The TRP or gNB is configured such that the RS transmitted over the potential beam is measured at least once in a configurable time window (eg, the SS burst period 802 with the SS burst set 804). Referring again to Fig. 8, at time t4, even if the quality of beam 11 and beam 10 are comparable, the WTRU's current serving DL TX beam will change from beam 11 to 10 without the measurement opportunity of beam 11. This switching may occur when the WTRU is in the middle of the overlapping coverage areas of beams 10 and 11.

Figure 9 is an example 900 of an RS for reducing beam level ping-pong effects. In example 900, if supplemental transmission (902) of CSI-RS on beams 11-14 is available for measurement, the WTRU may determine that the quality of beam 11 and beam 10 is comparable, thereby avoiding switching from beam 11 to Undesired beam switching of beam 10. The supplemental transmission of the CSI-RS may be initiated by the network, TRP or gNB. Supplemental transmissions may also be initiated or requested by the WTRU either explicitly or implicitly.

The TRP or gNB may add the WTRU's current serving DL TX beam to the newly formed CSI-RS beam to cause the WTRU to perform new measurements on the serving beam or adjacent beams. The TRP or gNB may also be the cause of other beams that are spatially co-located with the service beam, such as supplemental transmissions on beams 11-14 in Figure 9.

In a recessive initiation or request, the WTRU may include the last measurement of the serving beam in the measurement based on the last reported SS block. In a dominant initiation or request, the WTRU may send a transmission request for the RS on a particular beam, service beam or QCL beam or the like. The request can be a discrete message, a PUCCH message, a MAC-CE message, or a number of bit information piggybacked on other messages. For example, a field following the SS block based measurement report can be used. An explicit initiation or request can be sent immediately after the measurement report, followed by a measurement report, or a delay until the RS on the expected beam does not arrive.

Different RSs may have different characteristics, such as beamwidth, periodicity, number of available measurement samples, or special measurement duration for full beam scanning. Different measurements or quality parameters can be used to characterize the beam due to different beamforming gains. When a single value (eg L1-RSRP) is configured to represent beam quality, if the measurement samples from the CSI-RS are more than from the SS block, the single value of the SS block based measurement may be lower than the CSI-RS based A single value measured.

The measured quantity or quality of two or more signals may change over time due to changes in the wireless channel, or may change over time from measurements at different time instances. In one configuration, by performing individual filtering or combining processes (e.g., averaging over time), the measured beam quality information from different RSs may be combined and combined before the WTRU reports or feeds back to the TRP or gNB. This separate filtering or merging process can use a pre-configured mapping table (eg, Table 4). Table 4

Beam quality information measured from different RSs can be reported directly to the TRP or gNB for merging or merging measurements. Based on the above combining or merging, the TRP or gNB can generate or adapt the DL TX beam. Table 5 is an example of a merge or merge operation performed with respect to TRP or gNB. table 5

The power offsets in Table 5 can be applied to beam fault detection or beam measurement and reporting. The values V1, V2, V3, α1, α2, and α3 may be WTRU-specific or configurable. For example, for beam fault detection, the power offset may be a transmission power offset between a DL RS, a CSI-RS, an SS block, and the like, and a DMRS of the PDCCH.

In the example given here, L1-RSRP or Signal-to-Noise Interference Ratio (SINR) can be used for beam fault detection. Such detection may be based on assumed control channel performance or assumed PDCCH block error rate (BLER) and the like. If the beam fault is determined based on measurements of DL RS, CSI-RS or SS block, etc., thereby converting the DL RS based measurements into hypothetical control channel performance, the WTRU may calculate the DL RS used for the DMRS and the PDCCH. The transmission power offset between. When the quality measurement metric L1-RSRP or the assumed PDCCH BLER is used, the transmission power offset can be used at this time.

A beam failure can be determined if some or all of one or more of the service beams fail. If the quality measurement metric for beam failure detection (eg, L1-RSRP or hypothetical PDCCH BLER, etc.) exceeds a threshold specified in advance or configured through higher layer communication, it can be recorded as a beam failure instance. A beam recovery request can be sent if the number of continuously detected beam failure instances exceeds the configured maximum number.

If a beam failure is detected, one or more candidate beams and beam failure recovery request transmissions can be identified and reported. To identify higher quality candidate beams, one or more candidate beams may be identified based on quality measurement metrics of candidate beams above a threshold. The quality measurement metric of the candidate beam may be L1-RSRP, SINR or hypothetical PDCCH BLER, and the like.

Similar or different threshold values may be introduced for SS blocks, SSBs, and CSI-RSs when considering similar or different transmission power offsets between DL RSs, CSI-RSs, SS blocks, or DMRSs of PDCCHs, and the like. For example, the network may configure similar or different thresholds for candidate beam identification corresponding to CSI-RS or SS blocks. The network may configure the quality measurement metric of the selected candidate beam to be a configurable offset above the beam failure threshold and/or to win a configurable offset from one or more service beams. In the example presented here, for candidate beam identification and trigger beam failure recovery requests, the WTRU may need to know the DL RS (eg, CSI-RS or SS block) used and pre-designated to be higher layered, RRC message or MAC- The transmission power offset between the DMRS of the fixed value PDCCH configured by the CE or the like. For example, if a transmission power offset is configured, a threshold value of another DL RS (CSI-RS) can be derived from a threshold of one DL RS (SS block). This can be performed by a scaling operation or the like.

A unified BM for multiple TRPs can be configured to avoid TRP or gNB ping-pong effects. In multiple TRP configurations, the beam-level ping-pong effect may become a TRP-level or cell-level ping-pong effect. TRP-level or cell-level beam switching can result in more burden, delay, power or data interruption time, and so on. This may be due to data forwarding during cell switching, path switching or WTRU context retrieval, and the like.

Figure 10 is an example 1000 of the TRP ping-pong effect resulting from the use of multiple types of RSs for BM. In 1000, beam 11 and beam 10 in Figure 7 may be transmitted from different TRPs 1-2 or gNBs 1-2 as different (1002) or similar (1004) types of beams. To avoid TRP or gNB level ping-pong problems stemming from multiple TRP deployments, the serving gNB can configure a set of parameters or thresholds for the WTRU to use a differential beam measurement configuration. The differential measurement configuration can show the bias towards service TRP or gNB due to the high cost of beam switching. For example, to report beam quality information for beams from neighboring TRPs or gNBs, the value of the measured amount of beam may have to be higher in the configuration than the beam from the serving TRP during the extended time period. Above the critical value.

Each SS block can have configurable characteristics, such as transmissions in a particular time, frequency, subband or symbol, and the like. Each SS block may also have configurable features, such as periodicity, beam scanning pattern, full or partial scanning within each SS block burst set, beam scanning order, association with RACH resources, and random storage with specific entities. Take the association of the channel (PRACH) preamble. The CSI-RS may have configurable features such as periodic, dominant or implicit trigger signals, CSI-RS resource configuration, CSI-RS resource element (RE) pattern, number of CSI-RS antennas, CSI-RS resources The set combination, the number of CSI-RS resources, or the time domain weight associated with each CSI-RS resource, and the like.

The SS block or CSI-RS may become dynamically available, whereby the CSI-RS or SS block will not be available at the same time in the inter-timing instance where the WTRU performs beam measurements. In addition, CSI-RS or SS blocks can be used and configured by TRP or gNB for unified beam measurement, unified beam reporting (UBR), beam fault detection or new candidate beam identification, and the like. The type of periodic NR-PUCCH feedback or time or frequency resources for aperiodic reporting, etc., can also be configured by TRP or gNB.

The dedicated PRACH resources can be configured to SS blocks or CSI-RS resources. When multiple SS blocks are configured, one or more SS blocks may be associated with the same uplink resource or PRACH resource or the like. For example, one or more dedicated generic PRACH resources may be reserved and configured for the WTRU. Multiple SS blocks may be associated with the same or different uplink resources (eg, PRACH resources). In order to perform robust transmission, when the beam is not available due to blocking or WTRU rotation, etc., multiple beams may be used to transmit the control channel. If the network, gNB, or TRP, etc. receive uplink transmissions from the WTRU through uplink resources associated with multiple SS blocks, the network may pass all of the associated SS blocks simultaneously in accordance with WTRU capabilities or network capabilities. The transmission is performed on or transmitted by the TX beam scan. The network may request further beam measurements and reporting of SS blocks from the WTRU so that the network may select all of the associated SS blocks or a subset thereof for use in subsequent or subsequent transmissions.

For BM, the CSI-RS and SS blocks may be complementary, as the SS blocks may be periodically available and may be used to reduce the burden of configuring the WTRU-specific CSI-RS. Depending on whether beam measurements for a subset of SS blocks are sufficient for the WTRU to perform beam discovery, refinement or tracking processing, etc., the WTRU may be configured to have all SS block resources or beams or SS block resources or beam subsets.

The SS block and the CSI-RS can be transmitted through the same TX beam. In the case of transmitting SS blocks and CSI-RSs through different TX beams, each signal can be used as a baseline RS for each beam. When an RS, SS block or CSI-RS or the like is configured to the WTRU for beam measurement and reporting, the configured RS will be preset as a baseline reference. If multiple RSs are configured to the WTRU, but independent beam measurement reports are configured by the network, then each RS will be a baseline signal, respectively, and the WTRU can perform beam measurements and reporting independently for each configured RS.

Since the CSI-RS is WTRU-specific and can be flexibly configured for each WTRU in accordance with channel and mobility conditions or bandwidth, etc., the CSI-RS can be used as the baseline RS for the unified BM. In the example given herein, CSI resources can be transmitted on multiple CSI-RSs. The CSI-RS can be transmitted in a periodic, aperiodic or semi-permanent manner through flexible trigger conditions.

If both the SS block and the CSI-RS are used for the BM, the WTRU may be configured to compare the measured amount between the CSI-RS and the SS block resource for the respective beam. If the CSI-RS and the SS block have different characteristics, the measured RSRP may be different even for the same beam measured at the same time instance. In response, the WTRU may use an SS block RSRP adjusted to a baseline RS RSRP or a CSI-RS with a certain offset value when the WTRU compares, selects, or reports the RSRP to the TRP or gNB to perform the BM.

If the transmission power of the downlink RS is fixed, the relative transmission power offset between the CSI-RS and the SS block may be configured by the TRP or gNB to the WTRU through dedicated communication (eg, SI transmission or RRC reconfiguration). This may be performed during the WTRU's entry into the connected mode or during the transition from another cell or TRP that configures the WTRU in a different manner. If the transmission power of the downlink RS is changed for inter-cell interference coordination or flexible cell coverage, the WTRU may require power values of different SS blocks or power offsets between different SS blocks and different CSI-RS beams. . The WTRU may also require power values for different SS blocks, or power offsets between different sets of SS blocks (if the transmission powers of all SS block beams within the same set of SS blocks are the same) and different CSI-RS beams. In the configuration, the TRP or the gNB does not transmit different CSI-RSs within the CSI-RS resources with different transmission powers, and instead, different CSI-RS resources are transmitted with different transmission powers.

In some configurations, the SS block can be cell-specific. When the transmission power of the SS block is changed, if the transmission power of each SS block beam is different, the power value or reference power value of each other SS block plus the power offset may be configured. If the power information contains a small payload, or if the transmission power within a single SS burst set is the same, then the power value can be passed in the SI so that all of the WTRUs in the cell receive the information. If the power information contains a large payload, the power value and offset can be configured by a dedicated SI for the WTRU group or a common search space PDCCH. For example, power information can be embedded in a common PDCCH transmitted in the same time slot as the SS block. The CSI-RS may also be WTRU-specific, and if CSI-RS resources are configured in higher layer messaging, Layer 3 messaging or RRC configuration messages, etc., power information is sent to the WTRU.

The SS block can be configured to be a baseline RS of the unified BM. This configuration can reduce the configuration burden for idle and connected mode WTRUs, scheduling CSI-RS resources or interference coordination, and the like. Using the SS block as the baseline RS can also reduce interference from CSI-RS transmissions and latency from scheduling WTRU-specific CSI-RS.

In the example given herein, when the SS block is configured as a baseline RS, the measured quantities of the other RSs can be converted into equivalent values for comparing the beam qualities. For example, if the transmission power of different CSI-RS resources is fixed, the WTRU may be configured with power information when configuring CSI-RS resources. If the transmission power of different CSI-RS resources is dynamically changed, information similar to that when the CSI-RS is selected as the baseline RS by dedicated MAC-CE, higher layer communication, or RRC communication, etc., may be configured for the WTRU. The power information format can be flexible, and if the power information or payload does not contain a large burden on the WTRU, the absolute value of the transmission power can be transmitted. In other configurations, offset values of transmission power or even differential values of transmission power having different resolution levels may be transmitted.

In the examples given here, the UBR can be periodic, semi-persistent or aperiodic. The UBR for beam measurement information (BMI) or beam correlation information (BRI) may include reference signal received power (RSRP), reference signal received quality (RSRQ), channel state information (CSI), beam index, beam group index, Channel Quality Indicator (CQI), Rank Indicator (RI), CSI Resource Indicator (CRI) or SS block resource indicator associated with beam information, and the like. One or more BRIs reported by the WTRU may be pre-designated or configured by RRC messages, or may be dynamically signaled by L1, L2, MAC-CE or NR-(e)PDCCH/NR-DCI And so on. Beam measurement information or beam related information can be configured by the TRP or gNB to be periodic or aperiodic.

A unified BM measurement and reporting configuration can use a mapping table that includes RS type, periodicity, beamwidth or on-demand or active configuration, and so on. As presented herein, unified BM measurements and reports can be periodic, aperiodic, semi-persistent, or event-triggered. Event triggering can be based on RS-specific timers or thresholds.

Figure 11 is an example 1100 of a configuration for measurement and reporting settings for a unified BM with joint and independent beam reporting of CSI-RS and SS blocks. The BM may include a reference resource configuration, a measurement configuration or a report configuration, and the like, and may use a format similar to resource setting and report settings for CSI-RS and SS block resources. When the WTRU is configured for a unified BM with N > 1 report settings and M > 1 resource settings, the measurement settings (1102) may link N report settings to M RS settings and the like. Configuration parameters N, M, and L can be implicitly or explicitly indicated or signaled in higher layer communications, Layer 3 communications, RRC communications, and the like. The configuration parameters that can be signaled in each report setting may include the reported RS ID, SS block ID, CRI, reported BRI, measurement quality, L1-RSRP on the SS, CSI-RS, report type, Joint reporting parameters, independent reporting parameters, time domain behavior, aperiodic settings, periodic settings, or semi-persistent settings, and more.

In 1100, report setting 1 may be periodic and may report the best 3 L1-RSRP values, while reporting setting 2 may be aperiodic and may report all measured L1-RSRPs. Resource setting 1 (period) may include a joint CSI-RS and SS resource set, where set 1 has four CSI-RSs and four SS block resources, and the repeatability is set to OFF. Resource setting 2 (non-periodic) may include a CSI-RS resource set, where set 1 has eight resources, and repeatability is set to ON. Further, the set 2 can have four resources, and the repeatability is set to OFF. Resource setting 3 (periodic) may include independent CSI-RS and SS block resource sets, where set 1 has 12 CSI-RS resources, and repeatability is set to OFF. In another configuration, set 1 may have 24 SS block resources and the repeatability is set to OFF.

In some configurations, S ≥ 1 CSI-RS or one or more SS block resource sets may be signaled. The set of resources may correspond to different sets of pools from all configured CSI-RS or SS block resources. If Ks ≥ 1 and the CSI-RS or SS block resources correspond to each set, then the mapping to the RE, the number of 、, the time domain behavior, the aperiodic report, the periodic report, the semi-persistent report, the RS frequency can be configured. Frequency span, RS power, RS power offset, or mapping to OFDM symbols in the configured time/time slot, and so on.

In some configurations, each of the L links in the CSI or SS block beam measurement settings may include a joint or independent report setting indication on the SS block or CSI-RS, a resource setting indication, to be measured, L1- RSRP measurements, L1-RSRP metrics on SS blocks, or L1-RSRP measurements on CSI-RS, and so on. Federated or independent reporting settings can be linked to one or more resource settings or the same resource settings.

In example 1100, a periodic report setting can be linked to two resource settings including a union and independent CSI-RS and SS block resource sets, respectively. The set of resources can be configured to have a repeating information element (IE), where the element is set to OFF to perform a TRP or gNB TX beam scan. A similar configuration can be used for WTRU RX beam scanning where the repeatability is set to ON. In addition, the aperiodic report settings can be linked to resource settings 3, where the repeatability of the two sets is set to ON and OFF, respectively. In example 1100, the WTRU may be configured to perform report setting 1 with resource setting 1 or resource setting 3, thereby using a joint L1-RSRP report of QCL-based SS blocks and CSI-RS, or using SS Independent L1-RSRP reports for blocks and CSI-RS are used.

Figure 12 is an example 1200 of another configuration for unified measurement and reporting of BMs with joint and independent beam reporting of CSI-RS and SS blocks. In the example 1200, both report setting 1 and report setting 2 can be linked to the same periodic resource setting 1. The resource setting 1 may include a resource set 1 having four CSI-RS resources and a resource set 2 having 8 SS block resources. Any set or all of the two sets can be selected by DCI or MAC-CE, etc., and can be configured by higher layer communication or RRC communication or the like. In the example 1200, since the resource setting 1 includes a periodic RS, an aperiodic report or a periodic report can be used.

Since independent reporting (eg, independent L1-RSRP reporting using QCL-based SS blocks and CSI-RS) can have a large burden, aperiodic reporting processing can be used. Due to the low burden of L1-RSRP measurements from the combined QCL-based SS block and CSI-RS compared to the independent report, periodic joint reports can be configured (eg using QCL-based SS blocks and CSI-RS) Joint L1-RSRP report). The TRP or gNB may command WTRUs within the same cell to perform similar types of reporting (eg, independent L1-RSRP reporting for periodic reporting). The WTRU may also operate a separate L1-RSRP report to perform periodic reporting.

Referring again to FIG. 4, the unified BM L3 beam filtering process can be used or configured for L3-RSRP or L3-RSRP for SS blocks of WTRU L3 mobility. Due to RRC configuration or reconfiguration, the L3 filtering process is more flexible than the L1 filtering process. In a configuration of a battery-limited WTRU with a static location, the L3 filtering process can be performed over a long time scale for stable and long-term beam quality. In another configuration, the mobility event is likely to be more frequent, and for a WTRU that is modestly limited or unrestricted, accurate beam quality measurements would be highly desirable. In order to obtain short-term beam quality fluctuations stemming from blocking, the L3 filtering process may be RRC configured to perform a process of taking a measurement average on a shorter time scale. This configuration may allow the network and the WTRU to quickly switch beams if the serving beam encounters beam blocking. The L3 filtering process can also be used with different configurations derived from L3-RSRP to address short-term beam quality fluctuations. However, since the L3-RSRP report can be carried on the PUCCH, the PUSCH, or the MAC-CE, etc., it is likely to cause a larger UL resource burden.

Figure 13 is an example 1300 of a layer 3RS received power (L3-RSRP) beam filtering process for a measurement model of a BM. In 1300, by configuring the L3 filtering parameters, the L3-RSRP beam filtering process shown in the example 400 can be used, whereby both L3-RSRP (1302) and/or L1-RSRP (1304) will be reported.

Figure 14 is an example 1400 of a measurement model using Layer 1 (L1) beam filtering. The L1 filtering process used to calculate the L1-RSRP can use an average or weighted action average of existing or available L1 beam measurements. For different RSs, the L1 filtering process may be pre-defined, configured in a similar manner to the L3 filtering process, or configured in a different manner than the L3 filtering process, and the like. The L1 filtering process can be flexible or adaptive and can be indicated by L1 or L2 control (eg, DCI messaging or MAC message delivery, etc.). In 1400, gNB 1-K beam may be input to the layer 1 as a signal filtering component 1402 A, and may be output as a signal A ^1. The RRC parameters and signal A ¹ may be input to a beam combining/selecting component 1404. The K beam or signal A ¹ and RRC parameters may also be input to the L3 beam filtering component 1406 and output as a signal E. Signal E may be input to report beam selection component 1410 along with the RRC parameters to produce an output F of the X beam. The output B and RRC parameters may be processed by layer 3 cell quality filtering component 1414 to produce signal C. In reporting guidelines RRC evaluation component 1416 can be used to process the signals C and parameter C ^1, to generate a signal D.

In the example 1400, the signal A ¹ and DCI parameters can also be input to the L1 beam filtering component 1408 and can be output as the signal G. Signal G may be input to the report beam selection component 1412 along with the DCI parameters to produce an output H of the Y beams. Beam measurement reports may be performed jointly or independently when multiple WTRUs are configured for the WTRU or when multiple RSs are available for use. Since the measurement results are equivalent to each other based on the same RS, when the independent beam measurement report is configured, the beam report information may include measurement results from only one RS and directly reported. The beam report information may include measurements from multiple RSs by combining beam measurement reports (eg, using a joint L1-RSRP of QCL-based SS blocks and CSI-RS). In this configuration, since the measurement results are not comparable when measuring different RSs, in order to generate separate representative values for each beam, UBR can be used to combine the measurement results of the beams and reduce the burden.

UBR 1 can use a uniform value in which measurements from different RSs measuring a particular beam are consolidated into a uniform value based on the configured uniform formula. Table 3 shows an example body of a measurement configuration set, and Table 6 shows an example of a uniform value. The WTRU may be configured to measure a set of beams, such as beams 0-10. Measurements from different RSs can be consolidated or combined into a single representative or uniform value for each beam. In UBR 1, RS information may not be available, or UBR 1 will not include RS type information in the report. Table 6

In UBR 2, an RS report can be used and the WTRU can be configured to select a certain RS as a baseline RS. If measurements are made on different RSs other than the configured baseline RS, the measurements can be converted to equivalent values based on the baseline RS and the configured or measured offset values. Table 7 shows an example of the conversion value. Table 7

In UBR 3, as shown in Table 8, a 1-bit RS type indicator can be used for two RSs, such as CSI-RS and SS blocks. A 1-bit RS type indicator may be passed by the WTRU in a bit map on PUCCH, PUSCH, or any other uplink channel. Also, the UBR format may include a 2-bit RS type indicator for more than two RSs. Table 9 shows an example of four RSs represented by an indicator of a 2-bit RS type, including CSI-RS, SS block, PDCCH-DMRS, and PDSCH-DMRS, which may be by the WTRU on PUCCH, PUSCH or Passed in the bit map on any other uplink channel. Table 8 Table 9

In UBR 3, the complete representation of the measurement results may include fields for RS type (eg, 1 or 2 bits), as well as variable length measurements for different RS and correlation values. The lengths of the measurements for different RSs may be similar or different depending on the reporting burden, accuracy, L1-RSRP resolution, L1-RSRP step size or maximum L1-RSRP range, and the like. An example of a beam report is shown in Table 10. As an example, when the measured quantity is 001101, the first two bits 00 may indicate the SS block beam, and the four bits 1101 may be used for the range of the SS block L1-RSRP value. In another example, when the measured quantity is 011000101, the first two bits 01 may indicate a CSI-RS beam, and the seven bits 1000101 may be used for a wide range of CSI-RS L1-RSRP values. Table 10

In the example given herein, UBR 1 or UBR 2 may be configured for joint beam reporting. For example, UBR 1 can perform joint reporting without RS information, while UBR 2 uses baseline RS information to perform joint reporting (eg, when converting measurements from multiple RSs into baseline RS based measurements). UBR 3 can be used for independent beam reporting where measurements from different RSs can be calculated separately and independently.

In UBR 4, the mixed UBR format can be used to indicate information such as beam ID, RS type, SS block usage, CSI-RS usage, measurement, L1-RSRP, L1-RSRQ, report type, independent L1-RSRP report or joint L1-RSRP report and so on. The Report Type field can be used in UBR 4 to enable federated and independent reporting for mixed UBR formats. An example of beam reporting using UBR 4 is shown in Table 11. Beam 2 and Beam 3 can use independent beam reporting, while a bit indicates the RS measured for independent beam reporting. The first bit in the measured quantity may indicate the RS type, for example, 1 and 0 may indicate CSI-RS and SS blocks for Beam 2 and Beam 3, respectively. The remaining 5 bits of the measured quantity 01101 can be used for the measured quantities, such as the L1-RSRP values for the CSI-RS and SS blocks, respectively. Beam 5 can use a joint beam report where all 6 bits 101101 of the measured quantity are used to represent the L1-RSRP value of UBR 1 or UBR 2. Table 11

Furthermore, beam 2 and beam 5 can be configured to have the same measurement magnitude (eg 101101) with different report types (eg independent beam report or joint beam report). The same values for beam 2 and beam 5 due to different report types The measured amount of 101101 can represent different measured quantities, such as L1-RSRP values. For beam 2, the first bit can be used to indicate which RS is used (eg CSI-RS) due to the use of independent reporting. And the remaining 5 bits 01101 may represent L1-RSRP values. Beam 5 may use joint beam reporting processing, where all 6 bits 101101 of the measured quantity may be used to represent the L1-RSRP value.

Periodic beam measurements can be configured to have normal triggering in order to maintain the quality status of the beam group. The burden for periodic measurements can be reduced or optimized by limiting the measurement and reporting of beams around one or more service beams or one or more BPLs. By limiting or constraining measurements, short-term fluctuations due to WTRU rotation and beam blocking can be obtained while managing the burden. The group of beams in each periodic measurement and report may be adjusted by the WTRU, although it is initiated (e.g., configured or signaled) or controlled (e.g., configured or signaled) by the WTRU or the network. For example, based on periodic measurements at particular moments, the WTRU may determine the beam around the best beam reported in the next measurement in an independent manner or the network without the measurement of one or more surrounding service beams.

For aperiodic beam measurements, the WTRU or network may configure a one-shot beam measurement for a sudden degraded SNR in a decoded control transmission, a decoded data transmission, or a detected beam failure, etc. trigger. A large report can be configured for non-periodicity because it is a single.

Flexible differential beam reporting can be used for the beam measurements given here. Since different levels of measurement complexity and burden tolerance may be different, RSRP resolution and RSRP reference can also be configured in different ways. In addition, for different RSs, the dynamic range of transmission power, frequency selective fading, or measurement may also be different due to different beamforming gains. Differential beam reporting for a unified BM may use a format to represent differential beam reports with differential reference RSRP or resolution for different RSs.

A differential RSRP for each beam-based report or a non-group based multi-beam report can be configured. Table 12 shows multiple offset and multi-resolution RSRP for different beams. All of the reported beams may be based on a similar reference RSRP, and any beam with a measured RSRP below the reference may not be reported because the reference RSRP may be the largest RSRP in the multi-beam configuration.

Different offset values can be used for beams measured on different RSs. In Table 12, beam 1 may be an SS block with an offset value of 0 dBm, and beam 5 is a CSI-RS beam with an offset value of 30 dBm. The WTRU may adjust RSRP for multiple RS resources, SS blocks or CSI-RSs, etc. based on the power offset of the corresponding RS. In addition, beams near and containing the service beam(s) can be reported with higher resolution (eg, 1 for beam 3). Different resolutions can be used for beams measured on different RSs. For example, for frequencies above 6 GHz, the CSI-RS beam and the PDSCH beam may have more than 64 beams. In this configuration, the SS block beam can have a wider beamwidth and a relatively coarser RSRP value and can be reported with a lower RSRP resolution. Table 12

Table 13 includes a plurality of differential RSRP reporting rules, each having different measurement reporting features that can be mapped to a particular BM RS. In one configuration, to determine the absolute RSRP value of the beam using Tables 12 and 13, the offset type and the relative RSRP value can be used. The reference RSRP values for the beam group can be similar. The offset type may indicate an RS based on the measured beam.

For non-group based differential beam reporting for multiple beams, the bit widths of the reference RSRP and differential RSRP may be pre-specified or configured to be similar or different values. For example, the reference L1-RSRP can be reported with a first bit width, such as X1 bit = 7 bits, and the differential L1-RSRP can be reported with a second bit width, such as X2 bit = 4 bits. For differential L1-RSRP on different RSs, the same set of bit widths for reference L1-RSRP and differential L1-RSRP can be used. Alternatively, different sets of bit widths for reference L1-RSRP and differential L1-RSRP can be used for differential L1-RSRP on different RSs. Table 13

If different groups are configured for different rules, differential RSRP can also be used for group-based beam reporting. In this configuration, beams that are reported by measuring the same RS may be designated as the same group or RS-specific beam group, and the like. Beams from the same TRP, gNB, or the same panel may be designated as the same group, RS specific beam group, and the like. RSRP reports with the same level of resolution or beams received/measured simultaneously may be designated as the same group or RS-specific beam group, and so on.

For L1-RSRP reports for group-based beam reporting, the bit width for reference RSRP or differential RSRP can be pre-specified or configured to similar or different values. For example, the reference L1-RSRP can be reported with similar bit widths for different RS specific beam groups (eg, SS block based beam groups and CSI-RS based beam groups), while differential L1-RSRP can be used. Reported for similar or different bit widths for different beam groups. If different differential quantization step sizes are used for different beam groups, the bit width may depend on the number of beams of different beam groups. For example, a reference L1-RSRP for an SS block and a CSI-RS may use a similar bit width (eg, 7 bits), while for a differential L1-RSRP on an SS block, a smaller bit may be used. Furthermore, reference L1-RSRP for beam groups based on SS blocks and CSI-RS may use different bit widths (eg 7-bit or 5-bit) for SS-based and CSI-RS-based beams Groups can use similar or different bit widths.

When constructing a beam group through RS or constructing a group without a single type of RS and configuring independent beam reporting, the following reporting formats can be configured: Baseline Reference RSRP is used for RS1 rule R1, reporting beam number n1. Pair 1: (beam G1_1, relative RSRP value 1) ... Pair n: (beam G1_n, relative RSRP value n1) Note: Beams with RSRP values below the minimum RSRP may not be reported; RSRP values are higher than the maximum RSRP The beam will be adjusted to the maximum RSRP; these pairs are reported in order; the number of reported beams is given at the outset. Rule R2 for RS2, reporting the number of beams n2. Pair 1: (beam G2_1, relative RSRP value 1) ... Pair n: (beam G2_n, relative RSRP value n2) Rule R3 for RS3, report beam number n3. Pair 1: (beam G3_1, relative RSRP value 1) ... Pair n: (beam G3_n, relative RSRP value n2)

If the beam group is not constructed by the RS being used and the joint beam report is configured, then the reporting format using the two-level group reporting structure can be configured: Baseline Reference RSRP Group 1 Rule R1 for RS1, Report Beam The number is n1. Pair 1: (Beam 1, relative RSRP value 1) ... Rule R2 for RS2, report beam number n2. ... Group 2 is used for rule R1 of RS1, reporting the number of beams n1. Pair 1: (Beam 1, relative RSRP value 1) ... Rule R2 for RS2, report beam number n2. ... Group 3 is used for rule R1 of RS1, reporting the number of beams n1. Pair 1: (Beam 1, relative RSRP value 1) ... Rule R2 for RS2, report beam number n2. ... In the second level, the beams are ordered within each given group of RS-based groups.

The differential beam ID reported on a per beam basis can also be configured. In addition to beam quality information (such as RSRP), the beam ID can also cause a traffic burden. In order to identify a beam (eg, a CSI-RS or SS block from an unknown TRP or gNB), a large number of bits may be required. In a configuration where the SS burst set has 64 SS blocks, an additional 6 bits may be needed to identify the SS block time index. For a CSI-RS based beam at a higher frequency than 6 GHz, it is possible to require more than 6 bits, which results in a burden of more than 16 bits. To reduce the signaling burden of the beam ID, the mapping table may include a list of shortened beam IDs when the WTRU is configured to have multiple SS blocks and CSI-RS resources for beam measurement and reporting. The shortened ID can identify a subset of available SS blocks and CSI-RS beams compared to the full beam ID.

Figure 15 is an example 1500 of the reported WTRU being geographically close to the WTRU between cell 1 and cell 2. When the WTRU is triggered to perform beam measurements and reporting, since the finally reported beam is likely to be geographically close to and centered on the WTRU, other beams that are further away from the WTRU and have a low RSRP will not be reported. In 1500, cell 1 may include a beam (m-2, m-1, m, m+1), and cell 2 may include a beam (n-2, n-1, n, n+1). By using the beam ID of a selected beam (eg, a beam with the lowest index value) as a reference value, beam reporting can be performed using other beams of the differential beam ID. Table 14 provides an example of a report based on differential beam ID. For differential IDs, the shortened beam ID may include 2 bits of each beam ID reported. Table 14

For efficiency, the WTRU may be configured to measure and report a subset of all available CSI-RS or SS block resources or beams. The WTRU may report all or a subset of the measurements. For example, when the WTRU is configured to measure M beams, it can report N beams, where N <= M.

The network configuration mapping table 15 at the WTRU may include a plurality of full-short IDs for indicating an ID (eg, a combination of cell ID, beam ID, or beam type for measured CSI-RS or SS block resource/beam) Mapping. The network can configure a WTRU-specific mapping table, which is also known to the network. For a WTRU reporting a measurement, a shortened ID (eg, a shortened cell ID, a shortened beam ID, or a combination of beam types) may be used to indicate the beam identity, and the network will use a locally stored WTRU-specific mapping table. Determine the full ID. As shown in Table 15, the length of the full beam ID may be 17 bits (having a 10-bit cell ID, a 1-bit beam type, and a 6-bit beam ID). The length of the short beam ID may be 4 bits (with 1 bit cell ID, 1 bit beam type, and 2 bit beam ID). Table 15

If there is no overlap by jointly indexing the CSI-RS, SS block beam or resource ID, the network may configure joint coding of the cell ID, beam type or beam ID, etc., for the WTRU mapping table. As shown in Table 16, by jointly indexing CSI-RS or SS block beam/resource ID, the bits required for the short beam ID can be reduced. Since the CSI-RS and SS block beam/resource ID are jointly indexed, the beam type in Table 16 will not be necessary, thereby further reducing the number of bits (3 bits) for the short beam ID. In Tables 15 and 16, the TRP or gNB may have a local copy of the WTRU-specific mapping table. In order to reduce the burden, all or a subset of the WTRUs within the cell may not have a mapping table in the network. As described in Table 17, the mapping table can use the reference ID for the short cell ID or beam ID. Table 16 Table 17

If the mapping table configured by the WTRU is not stored in the network, then the WTRU update of the mapping table and reporting the subset of beam measurements in accordance with the prior beam reporting configuration will also reduce the burden. For example, the WTRU may report a beam with an L1-RSRP above a certain threshold. As shown in Table 18, for this configuration, one bit may be required for the short beam ID. Table 18

Even if the WTRU's beam reporting settings change, the traffic burden between the network and the WTRU will also decrease as the network skips the mapping table update. When both the SS block and the CSI-RS are configured for beam measurement reporting, the WTRU may perform beam reporting independently based on each beam or on a per group basis. When both SS blocks and CSI-RSs are configured for beam measurement and reporting, differential beam reporting for unified BM can also be used for independent beam reporting.

Independent beam reports for SS blocks or CSI-RS can be configured or specified with different parameters. For an L1-RSRP measurement report for an SS block, the maximum number of TX beams measured for a given report instance may depend on the frequency band and may be expressed as K _SSB . For example, if it is less than 3 GHz, then K _SSB = 4, if it is less than 6 GHz, then K _SSB = 8, if it is greater than 6 GHz and less than 52.6 GHz, then K _SSB = 64. The maximum number of TX beams reported by the WTRU at each reporting instance may depend on the frequency band and may also be configured with N _SSB by the TRP or gNB. In a configuration, if less than 3 GHz, then N _SSB = 1, if less than 6 GHz, then N _SSB = [1, 2], if greater than 6 GHz and less than 52.6 GHz, then N _SSB = [1, 2, 4, 8] .

The values for reporting on PUCCH and PUSCH may be different. For example, a TRP or gNB may configure a larger value for PUSCH based reporting and a smaller value for PUCCH based reporting. Referring again to Figure 4, the values for the P-1, P-2, and P-3 programs can be different. For example, the P-2 program can be configured with a larger value, and the P-1 program can be configured with a smaller value. Report values for aperiodic reports, semi-persistent reports, periodic reports, and the like can also be different. For example, you can configure a larger value for aperiodic reporting and configure a smaller value for semi-persistent or periodic reporting.

The report values used for related report content can be different. For example, for a small amount of measurement to be reported (eg, using a differential L1-RSRP report), then a large value can be configured, and for more measurements to be reported (eg using absolute or regular L1-RSRP reports) , then you can configure a small value. In the example given in this paper, TRP or gNB can select a subset of N (<=N _SSB ) beams, and the subset can pass higher layer communication, RRC communication, MAC-CE, L1 communication or DCI, etc. Indicated to the WTRU.

The maximum number of TX beams measured by the WTRU for a given reporting instance may depend on the frequency band and may be indicated as K _CSIRS for the L1-RSRP measurement report of the CSI-RS. For example, if it is less than 6 GHz, then K _CSIRS = 8, and if it is greater than 6 GHz, then K _CSIRS = 64 or K _CSIRS = 128. In another example, the single maximum number of TX beams measured by the WTRU for a given reporting instance may be independent of the frequency band, such as K _CSIRS = 128.

The maximum number of TX beams reported by the WTRU at each reporting instance may depend on the frequency band and may be configured by the TRP or gNB for the L1-RSRP measurement report of the CSI-RS. The indication for this configuration may be N _CSIRS , as an example, if less than 6 GHz, then N _CSIRS = [1, 2], if greater than 6 GHz, then N _CSIRS = [1, 2, 4, 8]. In another example, the single maximum number of TX beams reported by the WTRU at each reporting instance may be independent of the frequency band, eg, K _CSIRS = [1, 2, 4, 8].

Different configurations may be used for N _CSIRS , where the TRP or gNB may configure a larger N _CSIRS value for PUSCH based reporting and may configure a smaller value for PUCCH reporting. Larger values can be configured for the P-2 program and smaller values can be configured for the P-1 program. Large values can be configured for aperiodic reports, and smaller values can be configured for semi-persistent or periodic reports. In addition, the N _CSIRS can be different for the associated report content. For example, for a small amount of measurement to be reported (eg, using a differential L1-RSRP report), then a large value can be configured for more measurements to be reported (eg using absolute or regular L1-RSRP reports) , can be configured with small values. Similar to the other examples given in this paper, TRP or gNB can select a subset of N (<=NC _SIRS ) beams, and the subset can pass higher layer communication, RRC communication, MAC-CE, L1 communication, DCI or A similarity indication for reporting is to the WTRU.

For the L1-RSRP level, the maximum L1-RSRP range and step size of the L1-RSRP on the SS block and the CSI-RS may be similar or different and may be measured and reported depending on the SS block and the CSI-RS. The number of beams or the desired traffic burden and so on. For example, if there is a larger beamwidth on the SS block, the L1-RSRP level may be less than or equal to the L1-RSRP on the CSI-RS. Furthermore, the step size of the L1-RSRP on the CSI-RS may be greater than the step size of the L1-RSRP on the SS block in order to reduce the burden when the number of beams measured on the CSI-RS is greater than the number of beams measured on the SS block.

The maximum TX reported by the WTRU in each reporting instance on the SS block or CSI-RS in accordance with PUCCH based reporting, PUSCH based reporting, P-1 procedure, P-2 procedure, P-3 procedure or periodic reporting, etc. The number of beams can be similar or different. The WTRU specific configuration may be indicated in the WTRU Capability Information Element for the maximum TX beam report or any other parameter presented herein.

For the beam resource indicator, CRI report, SS block index report, L1-RSRP report, periodic report or aperiodic report for the BM, etc., the WTRU may use different UL channels, short PUCCH, short PUSCH, Long PUCCH or long PUSCH and so on. For example, for periodic beam reporting, the WTRU may be configured for long PUCCH and short PUCCH reporting. For semi-persistent beam reporting, the WTRU may be configured for short PUCCH, long PUCCH, and PUSCH. For aperiodic beam reporting, the WTRU may be configured for short PUCCH and PUSCH.

The beam report prioritization map shown in Table 19 can be configured to optimize beam reporting to achieve low burden and power consumption. Based on the beam report prioritization mapping, the WTRU may be configured to perform multi-level beam reporting for different WTRU conditions (eg, configured UL channel, WTRU speed or WTRU service type, etc.). Table 19

When transmitting beam reports and CSI reports on a short PUCCH, due to the capacity limitations of a short PUCCH, the WTRU may be configured to report only beam reporting content with a higher priority than a predetermined or configured value. A large size beam report can be configured by signaling a low priority value of the same L1 message that triggers the aperiodic beam measurement report. If a non-periodic beam report is transmitted on the PUSCH, then the configuration will apply to the aperiodic beam report as it is a single event and the PUSCH has a greater payload capacity than the short PUCCH. In some configurations, for low latency aperiodic reporting, the WTRU may report content with high priority on short PUCCHs with low payload capacity. For UL transmissions, the WTRU may be configured to perform SRS transmissions with beam reporting and CSI reporting.

Optimization rules can be configured to reduce transmission burdens and possible conflicts. For example, when the total payload size of the CSI report and the beam report is above the capacity of the short PUCCH, when the number of available OFDM symbols inside the slot is insufficient to transmit the SRS and the PUCCH, there may be a collision at this time. The WTRU may use scalable multi-level beam reporting to avoid these and other collisions.

Aperiodic transmissions, beam reports, CSI reports, or SRS, etc., can be configured for higher transmission prioritization than periodic transmissions. A PUCCH, a short PUCCH, or a long PUCCH may have a higher transmission priority order than PUSCH and SRS transmission. In the event of a collision, the channel may be partially dropped in the time domain. For example, an SRS transmission may partially overlap with a PUCCH, a short PUCCH, or a long PUCCH, and only SRS symbols overlapping with a PUCCH, a short PUCCH, or a long PUCCH are not transmitted. The next scheduled periodic or semi-persistent transmission can be skipped when the aperiodic transmission is delivered. In some configurations, aperiodic beam reporting can be triggered on each emergency request, and periodic reporting can be used during the slow channel change period.

Figure 16 is an example 1600 of unified beam measurement and reporting. Unified beam measurements and reports on multiple reference signals based on power offset indications (eg, joint or independent L1-RSRP reports on CSI-RS and SSB) are shown in 1600. At 1600, the WTRU may receive a unified beam configuration (1602) for beam measurements and reporting on SS blocks and CSI-RS. Beam measurements can be performed based on the configured RS (1604). If the trigger for beam reporting is satisfied (1606), a determination can be made based on whether a single RS is configured (1612). Otherwise, it may be determined that a request for measurement assistance is sent to the TRP or gNB (1608), and the measurement assistance information request is to be received (1610) to perform additional measurements. Additional measurements can be performed if a request for measuring assistance information is not sent. The WTRU may request measurement assistance from the TRP or gNB to perform supplemental RS transmissions by means of time division multiplexing (TDM) or frequency division (FDM).

If a single RS is configured, beam measurement and reporting of a single RS can be performed (1614). If more than one RS or multiple RSs are configured, then a power offset can be configured/indicated (eg, via the network) and joint or independent measurements and reports can be performed based on the indicated power offsets (1618) . Otherwise joint or independent measurements and reports can be performed without the indicated power offset (1624).

For joint measurements and reports with power offsets, joint measurements and reports can be performed using a unified baseline RS report (UBRR) (1620). The WTRU may perform UBRR by using the SS block and the joint L1-RSRP on the CSI-RS based on the baseline RS and the indicated power offset relative to the baseline RS in order to achieve accurate measurements and reporting. In UBRR, the WTRU-measured L1-RSRP value can be converted to a range of values for the configured baseline RS.

Flexible independent beam reporting (FIBR) can also be performed for independent measurements and reporting with power offset (1622). In FIBR, the WTRU may perform separate measurements on SS blocks or CSI-RS, but may report measurements derived from an RS, SS block or CSI-RS or two reference signals based on the indicated power offset.

For joint measurements and reports without power offsets, the Joint Report Unified Measurement Report (UMR) (1626) can be used. The WTRU may perform coarse measurements (e.g., have a simple average over multiple RSs) and may use UMR to report joint L1-RSRPs on multiple RSs. For UMR, the WTRU may perform separate measurements on the SS block or CSI-RS, but will report the result of the joint or merge. An example of a merge result may be a linear average of L1-RSRP values for the same beam from an SS block or CSI-RS.

For independent measurements and reporting, Independent Beam Reporting (IBR) (1628) can also be used without power offset. In the IBR, the WTRU may perform separate measurements on different RSs, SSBs, or CSI-RSs, and the like. For this configuration, the two measurements on the SSB or CSI-RS can be reported separately or independently.

After performing and determining the beam measurement and reporting procedures, the WTRU may report joint or independent L1-RSRP reports on the SS block and/or CSI-RS via a unified beam reporting format. The unified beam reporting format may include beam ID (eg, differential or absolute beam ID), RS type (eg, SSB or CSI-RS), measurement (eg, L1-RSRP value or differential L1-RSRP value), or report type (eg, federation) Or independent L1-RSRP report) and so on.

In the examples presented herein, the WTRU may receive a unified BM configuration for beam measurement and reporting from the network. These configurations may include minimum SI from broadcast and RRC configurations, and the like. The configuration may include at least one RS, a trigger condition for beam reporting, an L1-RSRP threshold, a report setting, a power offset or a report type, and the like. The configuration may be based on a mapping table for mapping RS type, periodicity, beamwidth, on-demand reporting, active reporting, periodic reporting, aperiodic reporting, semi-persistent reporting or event triggering, and the like. Examples of configurations are given in Table 3, and report settings and possible measurement resource/report settings are given in Figures 11 and 12.

In the examples presented herein, the WTRU may be configured by the network for periodic beam measurement and reporting. The network may also request the WTRU to perform aperiodic or semi-persistent beam measurements and reporting. In the case of a triggered WTRU, the WTRU may use actively triggered beam measurements and reports. For example, the WTRU may use signal requests for beam training, measurements, or beam reporting. The WTRU may also be configured to terminate the current beam training procedure. Event triggering can be configured and defined by using RS-specific timers and thresholds. The measurement configuration settings presented herein (eg, in Tables 2 and 3) can be used. For some configurations, if the trigger is not met (eg, L1-RSRP is not above the threshold), the WTRU may request measurement assistance explicitly or implicitly to the network TRP or gNB to perform supplements using TDM or FDM. RS transmission. Figure 9 shows an example 900 for supplemental RS transmission.

During beam measurement, the total bandwidth of the measured RS can be considered and a minimum measurement bandwidth can be configured. For example, when the measured reference resource occupies a minimum bandwidth, the measurement can reflect accurate beam quality information. One or more combinations of measuring RS resources or different RS resources of the QCL, etc. may be used due to the minimum bandwidth. In an example, the configured WTRU-specific CSI-RS resources may exceed the minimum bandwidth. In order to satisfy the minimum bandwidth using FDM, both the SS block resource and the CSI-RS resource can be transmitted by the same symbol. In order to satisfy the minimum bandwidth using TDM, SS block resources and CSI-RS resources can be transmitted by different symbols. The minimum bandwidth used for BM and CSI capture can be different or similar. A measurement on a single RS can trigger a beam measurement report when the CSI-RS or SS block resource meets the minimum bandwidth requirement.

In the examples presented herein, different or similar CSI-RS configurations may be used for the BM and CSI acquisition processes. If a CSI-RS configuration is used for the BM, then there may or may not be an additional configuration to distinguish between beam measurements or CSI acquisitions being performed (or possible time instances).

If the CSI-RS or SSB resources meet the minimum bandwidth requirement, then measurements on a single RS are sufficient to trigger a beam measurement report. In some configurations, the WTRU may send a measurement assistance request related to the minimum bandwidth and the number of CSI-RS resources or sets. This can be performed during the P-1 and P-3 procedures due to RX beam scanning. For different numbers of scanned WTRU RX beams, the number of CSI-RS resources within the CSI-RS resource set may be different in the P-3 procedure. For example, a CSI-RS resource can be transmitted on a beam. The number of CSI-RS resource sets may also be different during the P-1 procedure. For example, the WTRU may use the same RX beam within the network TX beam scan period, but will use a different RX beam when the network switches to the next TX beam scan period.

As given in the examples herein, if the trigger is satisfied after measuring a single RS, SS block, or CSI-RS, the WTRU may perform a beam measurement report for the L1-RSRP of a single RS. If the trigger is satisfied after measurements are made on multiple RSs, SS blocks or CSI-RSs, etc., the WTRU may perform joint on CSI-RS and SS blocks based on power offset indications from the network, TRP or gNB, and the like. Or a separate L1-RSRP report.

Referring again to FIG. 16, once the reporting procedure is determined, the WTRU may report a joint or independent L1-RSRP of SS blocks and/or CSI-RSs via a unified beam reporting format. For example, the unified beam reporting format may include one or any combination of the following: a beam ID having a differential value or an absolute value (ie, a differential beam ID or an absolute beam ID/conventional beam ID/beam ID), RS type of SSB type or CSI-RS type, measurement quantity of L1-RSRP value, differential L1-RSRP value, RSRP value or RSRQ value, or report type of joint or independent L1-RSRP report, and the like.

In one configuration, the unified beam indication for beam measurement, beam-based transmission, or beam switching may be via RRC message, MAC-CE or NR-(e)PDCCH, NR-DCI, DCI field or random access response (RAR) The license is advertised to the WTRU explicitly. The unified beam indication from the TRP or gNB may include beams for WTRU data reception, unified beam measurements for beam tracking, transmission or handover, number of beams measured and reported by the WTRU, and associated RS, or The type of beam measurement reported by the WTRU, and so on. The unified beam indication may also be a bit map with one or more fields to indicate an RS type indicator, a number of beams, and associated beam measurements, RSRP or CSI, and the like.

In some configurations, the unified beam indication may be implicitly signaled since the TRP or gNB may not be aware of the WTRU's measurement capabilities. For example, the number of beams or beam groups that the signal WTRU is to measure and report is explicitly signaled instead for the associated beam measurement (eg, SS-RSRP, CSI-RSRP, or DMRS-RSRP, etc.) Different thresholds can also be signaled to the WTRU for reporting to the TRP or gNB.

The N-bit indicator field in the DCI can be used for spatial QCL reference for DL RS or CSI-RS SS block, etc., in order to demodulate the downlink channel, PDCCH or PDSCH, and the like. The indicator may be an indicator state associated with an index of a DL RS, CRI or SS block or the like. For CSI-RS, the resource can be periodic, semi-persistent or aperiodic, and so on. During WTRU measurements, the DL RS index may be associated with the indicator state by explicit signaling or implicitly. As an example of implicit messaging, the network may configure a subset of the DL RS for measurement by the WTRU, and the WTRU may establish an association between the DL RS index and the indicator state based measurement. The N-bit indicator can be a function of the TCI and can be transmitted in a DCI field size. The TCI field size can be pre-specified to a fixed value, or configured by higher layer messaging, RRC messaging, or MAC-CE.

The WTRU may be configured by RRC to have up to M lists of TCI states for QCL indication. In some configurations, M can be equal to or greater than 2 ^N , where N is the size of the N-bit TCI status field in the DCI. Since the total number of indexes, CRI or SS block indexes, etc. of the DL RS may be higher than 2N, the value of M may be greater than 2N, and the mapping between the actual TCI state and the state described by the N-bit DCI field may be Use hierarchical group-based or three-phase mapping.

In hierarchical group-based mapping, the corpus of DL RSs can be divided into groups according to pre-defined or configured rules. The rules may include spatial QCL references or RS types, such as SS blocks, periodic CSI-RS, aperiodic CSI-RS or semi-persistent CSI-RS, and the like. A WTRU may be configured to measure and report a subset of DL RS index groups. In this configuration, the total number of configured DL RS indices can be mapped one-to-one to the number of states of the N-bit TCI field index. For example, the WTRU may be configured to measure 7 DL RSs indexed with a 3-bit (23=8>7) indicator field in the DCI. If the complete set of DL RS indices is 10, it can be divided into two groups based on the RS type, where the first group can include 4 DL RS indexes for SS blocks, and the second group can include for CSI- 6 DL RS indexes of the RS.

In addition, the WTRU may be configured to measure a first group of 4 DL RSs, which may be indicated by 2 bits in the 3-bit TCI field for 4 DL RS indices. The remaining 1 bit can be reserved to indicate a group or group rule. The second group of 6 DL RS indices can be indicated by a 3-bit TCI field. Another grouping rule may be a QCL DL RS, such as RSs of 7 DL space QCLs, grouped together and indexed by a 3-bit (2 ³ = 8 > 7) indicator field in the DCI. . If the TCI states (where each state can be associated with a DL RS set) have associated QCL configurations, they can be mapped to the same N-bit TCI status field in the DCI. The associated QCL configuration may be one or more DL RSs carried in a set of RSs in a TCI state, including QCLs having one or more DL RSs carried in an RS set of another TCI state.

The three-phase mapping may include the RRC configuration of the first phase, the MAC-CE initiation or deactivation of the second phase, and the DCI field indication of the third phase. Additionally, the WTRU may be configured with a DL RS pool through RRC. The network can use MAC-CE to dynamically initiate or deactivate a subset of the DL RSs in the DL RS pool. The size of the dynamically initiated DL RS can be indexed by the N-bit TCI field in the DCI.

The TCI state can be used as a QCL reference for receiving and demodulating the PDSCH. For PDSCH, the QCL reference can be dynamically indicated by the TCI field carried in the DCI. TCI will be present when the TCI state is configured. For example, the WTRU may include a fixed RX beam or an omnidirectional beam without performing DL RX beam scanning. The TCI state may also be a QCL reference for monitoring or receiving the PDCCH.

The WTRU may be configured to have multiple resource control resource sets (CORESET) and may also be indicated by one or more TCI states if all or a subset of the configured CORESETs are associated with one or more TCI states The QCL reference is used for the PDCCH. Different from the TCI state of the PDSCH used for the L1 DCI indication, for the PDCCH, the TCI state for CORESET can be carried by the higher layer communication, RRC communication, MAC-CE or RRC communication and MAC-CE, and the like. To configure or advertise. The PDCCH CORESET configuration can also be configured in a semi-static manner.

In the NR configuration, for DL, the QCL settings can be applied across the carrier and bandwidth portion (BWP). For high frequency (HF) carrier aggregation, if two transceivers are co-located and the two frequencies are numerically close, then the two HF carriers will have similar power distributions in the spatial domain. In this configuration, the BM information in the first HF CC can be used at least partially in the second HF CC, which reduces the burden on the second CC.

When the NR is configured for a wider bandwidth for higher capacity, the network, TRP or gNB dynamically configures the active bandwidth from one BWP to another BWP with or without overlapping. In the dynamic bandwidth adjustment procedure, SS block resources and CSI-RS resources may or may not exist. When the SS block and the CSI-RS resources are all available within the new BWP, the WTRU may need a spatial QCL parameter indication across the BWP. If the spatial QCL configuration is applicable between the SS block and the CSI-RS resources, the QCL SS block and the CSI-RS resources can be transmitted on the same beam, which indicates that the joint sum of the QCL SS block and the CSI-RS is used. The independent L1-RSRP report is being used by the WTRU. An example of a joint L1-RSRP report is described above. If the spatial QCL configuration is not applicable between the SS block and the CSI-RS resources, the WTRU may use a separate L1-RSRP report.

Figure 17 is an example 1700 of beam measurement and reporting outside of an active BWP. In 1700, if configured, the BWPs 1-3 can be configured to be used for robust transmissions where some BMPs have been fully used, blocked, or reserved. In some configurations, the configured BWP 2 can be active. BWPs 1-3 may also allow for flexible capacity requirements when the WTRU requests different capacities for different applications or service types. For robustness or capacity considerations, etc., the WTRU may also dynamically switch one or more active BWPs via DCI based or timer based handover. Prior to handover, the WTRU may determine QoS for different candidate BWPs for use in appropriate selection. The WTRU may be configured or indicated by higher layer messaging, RRC messaging, MAC-CE or DCI, etc. to explicitly or implicitly measure BWPs outside of the active BWP.

The bandwidth resource of the CSI-RS may be smaller than the BWP, and the BWP may or may not contain the SS block. The size of the BWP may range from the bandwidth of the SS block to the maximum bandwidth capability available to the WTRU for the CC. Thus, the WTRU may perform beam measurements and reporting on multiple BWPs (which include both one or more active BWPs and inactive BWPs) by considering one or more types of RSs. These RSs may include periodic CSI-RS, aperiodic CSI-RS, semi-persistent CSI-RS or SS block, and the like.

In Table 20, the WTRU may be configured to have a spatial QCL relationship between different CCs (e.g., CC1 and CC2) and may indicate that for CC1, TCI State 0 is maintained to be used for another QCL CC2. The gNB may signal in the DCI that the WTRU will use CRI #0 in CC1 for TCI State 0. The WTRU may use this configuration for subsequent BM and data and control transmissions in CC2. In the RS set associated with TCI State 0, the two DL RSs in CRI #0 and SSB #1 may be in the same QCL. Based on TCI state 0, the two indices may point to the same beam and BM, which may indicate that the WTRU will utilize a joint L1-RSRP report using a QCLized SS block and a CSI-RS. Table 20

The WTRU may acquire spatial QCL relationships between different CCs from the SI in the initial access. The QCL relationship may be associated with WTRU capabilities or CCs associated with the WTRU, and the like. The QCL information may be obtained after receiving a WTRU capability report from the network. A WTRU in RRC connected mode may be configured to perform measurements and reporting on multiple CCs. Due to the dynamically changing propagation environment (including mobility, blocking, multipath or reflection, etc.) observed by the WTRU, the gNB may use WTRU feedback to dynamically update or indicate spatial QCL information between different CCs. Updates can be performed with higher layer signals, RRC messaging, RRC messages, MAC-CE or DCI, and the like. The measurement report or spatial QCL information may be signaled from the WTRU to the gNB through higher layer signals, RRC messaging, RRC messages, MAC-CE or UCI, and the like. Likewise, the WTRU may be configured by RRC to have spatial QCL parameters across multiple BWPs across the domain such that the WTRU may perform joint or independent L1-RSRP reporting using QCL SS blocks and CSI-RS.

The QCL relationship between different CCs can also be signaled to the WTRU when a new CC is initiated. For example, a cross-carrier QCL configuration for DL can be signaled by the primary CC or primary serving cell. Similarly, the QCL configuration or relationship between BWPs can also be signaled when the BWP is launched. For example, a QCL configuration that spans multiple BWPs can be advertised by an intermediate BWP located at the carrier frequency. The communication can be high-level communication, RRC communication, MAC-CE, or RRC communication and MAC-CE for high reliability. The messaging can also use lower layer messaging (eg, DCI) for lower burdens with lower reliability.

As shown in Table 20, the TCI state may include one or more DL RS indices and may use a single beam or multiple beam transmission configuration. For example, TCI state 0 may refer to a DL RS index, where CRI #0 and SSB #1 may be the same beam, and TCI state 1 may refer to two DL RS indices CRI #2 and SSB #3. If a DL RS ID is included within the RS set of the TCI status finger, a single beam transmission, a single TRP or a single panel or the like can be utilized. If multiple DL RS IDs (eg, two DL RS IDs) are included within the RS set, simultaneous multi-beam transmission, multiple TRP or multi-panel, etc. can be used. The RS set of one or more per TCI state may also be configured to use more than one DMRS group for the PDSCH.

The multi-beam indication can also be configured to be a multi-bit map in DCI or MAC-CE. For example, the length of the multi-bit map may indicate the number of multiple beams, and each bit may indicate a beam or a DL RS ID. In addition, multi-dimensional multi-bit mapping for multi-TRP or multi-panel deployments is also configurable, with each dimension being used for a TRP, a gNB, a panel or a beam group, and the like.

In addition, the T-bit status may be carried in the N-bit field for PDSCH or PDCCH beam indication carried in the DCI. The TCI status or N-bit indicator field may contain additional parameters depending on capacity or burden. The TCI may include a PDSCH or PUSCH rate matching parameter. Furthermore, in NR, PDSCH or PUSCH RE mapping can be configured to have a large set of potential RE mapping parameters by RRC. MAC-CE messaging can be used to reduce or initiate a subset of RE mapping parameters configured through RRC. Finally, the PDSCH RE mapping and Pseudo-Resonance Indication (PQI) bits carried in the DCI can be used to dynamically indicate the actual RE mapping set for the scheduled PDSCH or PUSCH. The RE mapping parameters may include a PDSCH start symbol, a PUSCH start symbol, a PDSCH end symbol, a PUSCH end symbol, a number of PDSCH symbols, or a number of PUSCH symbols, and the like.

The parameters can be directly related to the QCL indication in the TCI state. The timing with respect to the time indicated by the QCL with respect to the QCL may vary. For example, a time delay value, a number of time slots or a number of symbols, etc., are configured for the timing gap to correctly decode the PDCCH, or to change or apply the PDSCH beam in accordance with the PDCCH indication. The PDSCH start symbol may provide a DCI decoding time and a beam switching time gap for applying or changing the PDSCH beam. For example, if the value of the PDSCH start symbol is K, then K time symbols can be used to determine the beam for the corresponding PDSCH reception.

Figure 18 is a diagram 1800 showing an example of a relationship between a starting symbol index or symbol offset for scheduling a new radio entity downlink shared channel (NR-PDSCH) and a DCI decoding delay or potential beam switching time. The value of K may indicate a start symbol index or a symbol offset between the DCI and the start symbol of the corresponding NR-PDSCH allocation (1802). The DCI decoding time or beam switching time may be configured based on K (1804). The value of K may be pre-specified, configured, or indicated by higher layer messaging, RRC signaling or MAC-CE, etc., and may also be based on WTRU hardware capabilities, DCI decoding delay, RF tuning delay, or beam switching. Time and so on. The value of K may implicitly represent the threshold of the time delay, which takes into account the TCI decoding time, the decoding time for the DCI with TCI, the RF tuning time or beam switching time, and the like. As an example, a WTRU may apply different RX beams to perform DCI reception and PDSCH reception, and it may take time to acquire and apply an appropriate RX beam to receive a corresponding PDSCH indicated by the DCI.

The threshold may vary depending on WTRU hardware capabilities, DCI decoding delay, beam handoff delay, carrier frequency, WTRU specific configuration, WTRU CORESET, WTRU search space, WTRU operating parameter configuration, symbol length, WTRU service type or URLLC operation, and the like. The value of K can be greater or less than the critical value. When the value of K is greater than the threshold, then the WTRU will have the appropriate time to acquire and apply the indicated DCI beam. When the value of K is less than the threshold, then within a limited time, the WTRU will rely on one or more pre-configured beams, or a predefined configuration or rule may be used to determine the appropriate RX beam to receive the corresponding PDSCH. The pre-configured one or more beams and predefined rules may be explicitly configured to the WTRU by using higher layer messaging, RRC messaging, broadcast SI or unicast SI, and the like. In some configurations, the value of K may represent the scheduling offset of the PDSCH allocation and may be included in the same scheduling allocation DCI that carries the TCI state. In this configuration, the value of K is carried in the TCI status field in the DCI or outside the TCI status field.

Figure 19 is an example 1900 for processing the start time slot index or time slot offset of the scheduled NR-PDSCH for scheduling of different time slots or time slots. In 1900, if the time slot schedule of the DCI and the corresponding NR-PDSCH allocation are configured, the value of K may indicate a start slot index or a time slot offset (1902). Based on this K, DCI decoding time or beam switching time (1904) may be available.

Once there is a TCI state configured for the WTRU, one or more TCI states may be updated by explicit or implicit messaging and based on the WTRU's actions, WTRU rotation, WTRU's active BWP handover, or WTRU's active CC handover, and the like. Space QCL reference or pre-configuration. In some configurations, the QCL relationship or spatial QCL reference may reflect beam or spatial RX parameters that will be used for beam management or control or data reception.

The explicit update can be based on beam measurement reports from the WTRU, and the network, TRP or gNB can determine if a explicit update is needed. The update may be based on all RS indexes or subsets in the measurement report associated with one or more different TCI states. If explicit updates are required, the network may signal one or more TCIs and one or more associated DL RS indices to the WTRU for QCL reference updates in one or more TCI states.

The spatial QCL reference or configuration update in the TCI state initiated by the WTRU may also be configured. The WTRU may initiate an update instead of a network initiated update. As an example, when the WTRU determines that the serving beam quality is degraded (eg, low L1-RSRP or low SNR), the WTRU may send a particular update request to the network, or may send the updated beam measurement report result directly. Upon receiving a request or updated measurement report, the network will be triggered to determine and update the QCL reference or configuration in one or more TCI states at the WTRU.

Timing delays when the WTRU is able to apply an updated spatial QCL reference or configuration in the TCI state may be utilized by certain configurations. Once the QLC update is performed at the WTRU, the network may instruct the WTRU to apply the updated QCL reference or the start time of the configuration for demodulating the channel, PDCCH or PDSCH, and the like. If the QCL update is performed via explicit messaging, the WTRU will take the time to process the messaging content and update the TCI status and perform beam switching as needed. If the QCL update is performed by implicit messaging, the WTRU may inform the network that the update has completed successfully and may provide update details. The update details may include an updated spatial QCL reference or configuration. The network may need to coordinate the scheduled PDCCH or PDSCH with the WTRU based on explicit or implicit messaging.

If the scheduling offset of the PDCCH or PDSCH is greater than the time delay required by the WTRU to complete the QCL reference or configuration update and beam handover, the WTRU may acquire and apply one or more suitable RX beams. If the schedule offset is less than the time delay, the WTRU may switch to the appropriate RX beam in accordance with a pre-configured or pre-defined rule or the like before applying the updated QCL reference or configuration. When updating the relevant TCI state, the PDSCH and PDCCH, the time delay may be similar or different. If the PDCCH and PDSCH share the same TCI state, then a similar time delay can be used for both channels.

The same timing in the spatial QCL reference or pre-configuration for updating the TCI state may include a delay when the WTRU applies the updated spatial QCL reference or configuration in the TCI state. The time delay may be indicated, configured or pre-specified by higher layer communication, RRC communication or MAC-CE, etc. based on the WTRU hardware capability of processing the communication content, resources for updating the TCI status, and subsequent beam switching, and the like. . If the WTRU receives a PDCCH or PDSCH based on the updated TCI status after this time delay, the WTRU may apply a new spatial QCL reference or pre-configuration. However, if the WTRU receives the PDCCH or PDSCH based on the updated TCI status prior to the time delay, pre-configured or pre-specified rules and the like may be utilized.

Figure 20 is an example 2000 of timing delays when an updated spatial QCL reference is applied in the TCI state. In 2000, TCI 001 for NR-PDSCH (2002) will be received by WTRU RX Beam 3. After updating the QCI reference for TCI 001 (2004), there is a time delay for the WTRU to apply the updated QCL reference (2010) in TCI state 001. During this delay, the WTRU may be configured to continue to apply the old QCL reference or apply a pre-configured QCL reference for PDCCH, PDSCH or NR-PDSCH (2006) reception. For example, if no updated QCL reference or pre-configuration is applied, the pre-configuration for the WTRU may use a particular pre-configured beam to receive the PDCCH or PDSCH. In another example, the pre-configuration may use a beam obtained from an idle mode, an omnidirectional beam as a fallback mode, a primary serving beam or an anchor beam, and the like. If the time delay is sufficient, the WTRU may use the updated QCL reference for the RX beam 5 to receive the NR-PDSCH (2008).

The QCL indication can be utilized to indicate spatial QCL relationships between different DL RSs. The SS block may spatially implement QCL with one or more of the internal CSI-RS resources for periodic, aperiodic or semi-permanent reporting, and the like. Since P-1 can be used to provide coarse beam related information, the spatial QCL can be used for the BMP-1 procedure, where the CSI-RS resources are configured to spatially interact with the SS block to implement QCL. In another embodiment, the CSI-RS resources may spatially perform QCL with another CSI-RS resource for the P-2 and P-3 procedures. Beam refinement processing may be performed in this configuration, and a QCL relationship may be used to refer to previously transmitted CSI-RS resources or beams.

Spatial QCL relationships can be configured using higher layer messaging, RRC messaging or RRC messaging and MAC-CE. The spatial QCL relationship can also be indicated by DCI, such as for aperiodic CSI-RS reporting. Since the purpose of the QCL indication for PDCCH or PDSCH reception and the DL RS may be different, the DCI field or format may also be different. The PDCCH or PDSCH reception and DL RS may also be jointly indicated, and the joint DCI field or format may be jointly encoded.

The DL beam indication configuration presented herein can be applied to UL beam indication. Separate TCI tables containing multiple TCI states for UL beam indication can be configured and maintained. The higher layer or RRC communication may configure the QCL association between the TCI state and the RS set for the UL at the beginning. Each TCI state may be a candidate for a reference RS that performs QCL spatially with a target RS, a DM-RS of a PUCCH, or a DM-RS of a PUSCH, etc. for UL transmission. Dynamic messaging, higher layer messaging, RRC messaging, MAC-CE or DCI, etc., may update the relationship between TCI status, RS ID, SRI, CRI or SS block index, etc. for dynamic beam indication of UL transmissions.

When beam correspondence between UL and DL is applicable, for efficiency, the RS set may include only the DL RS ID or both the SRS ID and the DL RS ID. If there is no beam correspondence, the RS set may contain a PRACH preamble or an SRS ID and the like. In another embodiment, a joint TCI table can be configured for the DL beam indication and the UL beam indication. In this case, if the RS set of the TCI state refers to only the DL RS ID, it may indicate that the beam correspondence between the UL and the DL is applicable, and the same DL ID may be used for the DL and UL QCL. reference. Thus, the WTRU may use the SRS beam having the same direction as the DL RX beam paired with the indicated DL RS ID as the UL TX beam.

Although features and elements of a particular combination are described above, one of ordinary skill in the art will recognize that each feature can be used alone or in any combination with other features and elements. Moreover, the methods described herein can be implemented in a computer program, software or firmware incorporated into a computer readable medium for use by a computer or processor. Examples of computer readable media include electrical signals (transmitted via wired or wireless connections) and computer readable storage media. Examples of computer readable storage media include, but are not limited to, read only memory (ROM), random access memory (RAM), scratchpad, cache memory, semiconductor memory devices, magnetic media (eg internal hard drives) And detachable magnetic disks), magneto-optical media, and optical media (such as CD-ROM discs and digital versatile discs (DVD)). A processor associated with the software can be used to implement a radio frequency transceiver for use at a WTRU, UE, terminal, base station, RNC, or any computer host.

BPL‧‧‧beam paired link

CSI-RS‧‧‧Channel Status Information Reference Signal

DCI‧‧‧Chain Control Information

DL‧‧‧High speed chain

DMRS‧‧‧Demodulation RS

FDM‧‧‧divided multiplex

FIBR‧‧‧Flexible independent beam report

ID‧‧‧identifier or indicator

L1‧‧‧ layer 1

L1-RSRP‧‧‧First layer reference signal received power

N2, N3, N4, N6, N11, S1, X2, Xn‧‧ interface

NR‧‧‧New radio

NR-PDSCH, 2002, 2008‧‧‧New radio entity downlink shared channel

PBCH‧‧‧ entity broadcast channel

PSS‧‧‧ primary sync signal

PUCCH‧‧‧ Short physical chain control channel

QCL‧‧‧ Quasi-co-location

RS‧‧‧ reference signal

SS‧‧‧Synchronization signal

SSS‧‧‧Secondary sync signal

TCI‧‧‧Transmission Configuration Indicator

TDM‧‧‧Time-division

TRP‧‧‧ transmission receiving point

UBRR‧‧‧ Unified Baseline RS Report

UE‧‧‧User equipment

100‧‧‧Communication system

102, 102a, 102b, 102c, 102d, 602 ‧ ‧ WTRU

104‧‧‧Radio Access Network (RAN)

106‧‧‧ Core Network (CN)

108‧‧‧Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧Intermediate mediation

118‧‧‧Processor

120‧‧‧ transceiver

122‧‧‧Transmission/receiving components

124‧‧‧Speaker/Microphone

126‧‧‧Keypad

128‧‧‧Display/Touchpad

130‧‧‧ Non-removable memory

132‧‧‧Removable memory

134‧‧‧Power supply

136‧‧‧Global Positioning System (GPS) chipset

138‧‧‧ Peripherals

160a, 160b, 160c‧‧‧e Node B

162‧‧‧Action Management Gateway (MME)

164‧‧‧Service Gateway (SGW)

166‧‧‧ Packet Data Network (PDN) Gateway (or PGW)

180a, 180b, 180c‧‧‧Next generation node b (gNB)

184a, 184b‧‧‧ User Plane Function (UPF)

182a, 182b‧‧‧Access and mobility management functions (AMF)

183a, 183b‧‧‧ Session Management Function (SMF)

185a, 185b‧‧‧ Data Network (DN)

402‧‧‧Layer 1 filter component

404, 1404‧‧‧ Beam Consolidation/Selection Components

406‧‧‧L3 beam filter assembly

408‧‧‧beam selection component

410‧‧‧ Layer 3 Filter Components

412, 1416‧‧ Reporting criteria assessment component

502, 802‧‧‧SS bursting time

504‧‧‧WTRU-specific CSI-RS period

506‧‧‧beam

1102‧‧‧Measurement settings

1402‧‧‧ Layer 1 Filter Assembly

1406‧‧‧L3 beam filter assembly

1408‧‧‧L1 beam filter assembly

1410, 1412‧‧‧Report beam selection component

1414‧‧‧ Layer 3 cell quality filter component

1626‧‧‧ Unified Measurement Report (UMR)

1628‧‧‧Independent Beam Reporting (IBR)

A more detailed description may be derived from the following detailed description of the embodiments illustrated in the accompanying drawings, in which System diagram of an example communication system of one or more embodiments; FIG. 1B is a diagram showing an exemplary wireless transmit/receive unit (WTRU) that may be used within the communication system illustrated in FIG. 1A, in accordance with an embodiment. System Schematic; FIG. 1C is a system diagram showing an example radio access network (RAN) and an example core network (CN) that can be used within the communication system shown in FIG. 1A, in accordance with an embodiment. 1D is a system diagram showing another example RAN and another example CN that may be used inside the communication system shown in FIG. 1A according to an embodiment; FIG. 2 is a transmission/reception point ( Examples of TRP and WTRU antenna models; Figure 3 is an example of synchronization signal (SS) bursting and multiple SS blocks; Figure 4 is an example of a measurement model for unified beam management (BM); Is to have multiple reference signals ( RS) an example for unifying BM; Figure 6 is an example signal flow for unifying BM; Figure 7 is an example of a WTRU acting in overlapping coverage of two narrow beams; Figure 8 is for signal flow An example of a beam-level ping-pong effect; Figure 9 is an example of an RS for reducing the beam-stage ping-pong effect; Figure 10 is an example of a TRP ping-pong effect caused by using multiple types of RSs for BM; An example of measurement and report setting configuration for unified BM with joint and independent beam reporting for channel state information-RS (CSI-RS) and SS blocks; Figure 12 is a diagram with joints for CSI-RS and SS blocks An example of another configuration for measurement and reporting of uniform BM reporting with independent beams; Figure 13 is an example of a measurement model in which Layer 3 RS received power (L3-RSRP) beam filtering can be used for BM Figure 14 is an example of a measurement model with Layer 1 (L1) beam filtering; Figure 15 is an example of a reported beam geographically close to the WTRU and WTRU-centric; Figure 16 is for a unified beam Examples of measurements and reports Figure 17 is an example of beam measurement and reporting outside the active bandwidth portion (BWP); Figure 18 is the use of downlink control information (DCI) decoding delay or beam switching time to schedule new radio entity downlink shared channels Example starting symbol index or symbol offset of (NR-PDSCH); Figure 19 is the starting time slot index or time slot offset for scheduling NR-PDSCH for different time slot or time slot scheduling An example of FIG. 20; and FIG. 20 is an example of a latent time delay when an updated spatial quasi-co-location (QCL) reference is applied in a Transmission Configuration Indicator (TCI) state.

Claims (20)

A wireless/transmission receiving unit (WTRU), comprising: a transceiver configured to receive configuration information from a transmission receive point (TRP), the configuration information including a beam measurement report for a plurality of reference signals (RS) Setting a transmission power offset between the RSs; a transceiver configured to measure a first reference signal (RS) of a beam and a first layer reference signal received power (L1-RSRP) of a second RS; And a processor configured to send a joint report or an independent report, wherein the joint report or the independent report is one of the measured L1-RSRP of the first RS or the second RS being higher than a threshold And generated based on the transmission power offset. The WTRU as claimed in claim 1, wherein the WTRU requests measurement assistance from the TRP to perform supplementary RS transmission in a time division multiplexing (TDM) or a frequency division multiplexing (FDM) manner. The WTRU of claim 1, further comprising: the WTRU performing a joint report measurement of the first RS and the second RS based on the baseline RS and the power offset of the baseline RS. The WTRU as claimed in claim 1, wherein the first RS is a synchronization signal (SS)/physical broadcast channel (SS/PBCH) block, and the second RS is within a bandwidth portion (BWP) Channel status information reference signal (CSI-RS) on co-located (QCL) resources. The WTRU as claimed in claim 1, wherein the WTRU sends a unified report of the first RS and the second RS, and the unified report includes one or more of the following: a beam identification (beam ID) ), a report type, an RS type, or an L1-RSRP value. The WTRU as recited in claim 5, wherein the report type indicates a joint report or an independent report. The WTRU as claimed in claim 1, wherein an updated Transmission Configuration Indicator (TCI) table is received based on the joint report or the independent report, the joint report or the independent report includes a plurality of An updated quasi-co-location (QCL) reference for a component carrier or multiple bandwidth portions (BWP). The WTRU as claimed in claim 1, wherein the transmission power offset is between a synchronization signal (SS)/physical broadcast channel (SS/PBCH) block and a channel for assisting beam measurement reporting or beam failure recovery. Between status information reference signals (CSI-RS). The WTRU as claimed in claim 8 wherein the transmission power offset between the SS/PBCH block and the CSI-RS is used to derive a quasi-co-location (QCL) SSB and for the A unified L1-RSRP value of the CSI-RS reported by the beam measurement. The WTRU as claimed in claim 8 wherein the transmission power offset between the SS/PBCH block and the CSI-RS is used to derive different L1-RSRP thresholds for beam failure recovery. Candidate beam selection. A method performed by a wireless/transmission receiving unit (WTRU), the method comprising: receiving, by the WTRU, configuration information from a transmission receiving point (TRP), the configuration information including beam measurements on a plurality of reference signals (RS) a report setting and a transmission power offset between the RSs; the WTRU measures a first reference signal (RS) of a beam and a layer 1 reference signal received power (L1-RSRP) of a second RS; The WTRU sends a joint report or an independent report, where the joint report or the independent report is based on the condition that the measured L1-RSRP of the first RS or the second RS is higher than a threshold and based on the transmission power Offset generated. The method of claim 11, wherein the WTRU requests measurement assistance from the TRP to perform supplementary RS transmission in a time division multiplexing (TDM) or a frequency division multiplexing (FDM) manner. The method of claim 11, further comprising: performing, by the WTRU, a measurement of a joint report for the first RS and the second RS based on the baseline offset of the baseline RS and the baseline RS. The method of claim 11, wherein the first RS is a synchronization signal (SS)/physical broadcast channel (SS/PBCH) block, and the second RS is in a bandwidth portion (BWP) A channel status information reference signal (CSI-RS) on a quasi-co-location (QCL) resource. The method of claim 11, the method further comprising: the WTRU transmitting a unified report of the first RS and the second RS, and the unified report includes one or more of the following: a beam Identification (beam ID), a report type, an RS type, or an L1-RSRP value. The method of claim 15, wherein the report type indicates a joint report or an independent report. The method of claim 11, wherein an updated Transmission Configuration Indicator (TCI) table is received based on the joint report or the independent report, the joint report or the independent report is included An updated quasi-co-location (QCL) reference for multiple component carriers or multiple bandwidth portions (BWP). The method of claim 11, wherein the transmission power offset is between a synchronization signal (SS)/physical broadcast channel (SS/PBCH) block and a channel for assisting beam measurement reporting or beam failure recovery. Between status information reference signals (CSI-RS). The method of claim 18, wherein the transmission power offset between the SS/PBCH block and the CSI-RS is used to derive a quasi-co-location (QCL) SSB and for a beam The measurement reports a uniform L1-RSRP value of the CSI-RS. The method of claim 18, wherein the transmission power offset between the SS/PBCH block and the CSI-RS is used to derive a different L1 of candidate beam selection for beam failure recovery. -RSRP threshold.