Method, architecture, apparatus and system for beam failure recovery

Abstract

A process, method, architecture, apparatus, system, apparatus, and computer program product for measurement of beam failure recovery. A wireless transmit / receive unit (WTRU) determines a beam failure of at least one beam, in which the beam failure is determined based on a measured value of a first type of beam and an estimated value of a second type of beam, respectively, and after determining the number of beam failures, determines a determined candidate beam among a plurality of candidate beams based on a parameter, wherein the parameter is based on a measurement parameter of the candidate beam of the first type, and wherein the parameter is predicted for the candidate beam of the second type.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 456,982, filed April 4, 2023, which is incorporated by reference herein in its entirety. BACKGROUND

[0003] The present disclosure relates generally to the fields of communications, software, and coding, including, for example, methods, architectures, apparatuses, systems involving beam failure detection (BFD) and beam failure recovery (BFR). SUMMARY

[0004] In a first aspect, the present principles relate to a method at a wireless transmit / receive unit, WTRU, the method comprising: determining a beam failure of at least one beam, wherein the beam failure is determined based on a measured value of a first type of beam and an estimated value of a second type of beam, respectively, and after determining a number of beam failures, determining a determined candidate beam among a plurality of candidate beams based on a parameter, wherein the parameter is based on a measured parameter of the first type of candidate beam, and wherein the parameter is predicted for the second type of candidate beam.

[0005] In a second aspect, the present principles relate to a wireless transmit / receive unit, WTRU, the WTRU comprising at least one processor configured to: determine a beam failure of at least one beam, wherein the beam failure is determined based on a measured value of a first type of beam and an estimated value of a second type of beam, respectively, and after determining a number of beam failures, determine a determined candidate beam among a plurality of candidate beams based on a parameter, wherein the parameter is based on a measured parameter of the first type of candidate beam, and wherein the parameter is predicted for the second type of candidate beam. BRIEF DESCRIPTION OF DRAWINGS

[0006] A more detailed understanding can be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

[0007] FIG. 1A is a system diagram illustrating an example communications system;

[0008] FIG. 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system FIG. 1A illustrated in FIG. 1;

[0009] FIG. 1Cis a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system FIG. 1A is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system

[0010] FIG. 1D is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system FIG. 1A is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system

[0011] FIG. 2 is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system

[0012] FIG. 3 is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system

[0013] FIG. 4 is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system

[0014] FIG. 5 is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system

[0015] FIG. 6 is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system DETAILED DESCRIPTION

[0016] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples can be practiced without some or all of these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the following description. Also, embodiments and examples not specifically described herein can be implemented or can be practiced in combination with the embodiments and other examples described, disclosed or otherwise provided (collectively, “provided”) herein. Although various embodiments are described and / or claimed herein, it should be understood that any

[0017] Example communication system

[0018] The methods, apparatus and systems provided herein are well suited to communications involving both wired and wireless networks. With respect to FIGS. 1A-1DAn overview of various types of wireless devices and infrastructures is provided, wherein various elements of the network can utilize, perform, be arranged and / or adapted and / or configured for use with the methods, apparatus and systems provided herein.

[0019] FIG. 1A This is a system diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail (ZT) Unique Word (UW) Discrete Fourier Transform (DFT) Extended OFDM (ZT UW DTS-OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0020] like FIG. 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102A, 102b, 102c, 102d, radio access networks (RANs) 104 / 113, core networks (CNs) 106 / 115, public switched telephone networks (PSTNs) 108, the Internet 110, and other networks 112. 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, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRU102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or be) user equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, cellular phone, personal digital assistant (PDA), smartphone, laptop computer, netbook, personal computer, wireless sensor, hotspot or Mi-Fi device, Internet of Things (IoT) device, watch or other wearable device, head-mounted display (HMD), vehicle, drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRU102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0021] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly connect to at least one of WTRUs 102a, 102b, 102c, and 102d, for example, to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or Network 112. As an example, base stations 114a and 114b can be any of a base transceiver station (BTS), Node-B (NB), eNode-B (eNB), home Node-B (HNB), home eNode-B (HeNB), gNode-B (gNB), NRNode-B (NR NB), site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[0022] Base station 114a may be part of RAN 104 / 113, and may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of radio services to a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In embodiments, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

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

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

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

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

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

[0028] In one embodiment, the base station 114a and the wireless transmission and receiving units 102a, 102b, and 102c may implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA 2000, CDMA 2000 1X, CDMA 2000 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 GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0029] FIG. 1ABase station 114B can be, for example, a wireless router, a home Node-B, a home eNode-B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area such as a business premises, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA 2000, GSM, LTE-A Pro, NR, etc.) to establish any of small cells, pico cells, or femtocells. FIG. 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN 106 / 115.

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

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

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

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

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

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

[0036] Although the transmitting / receiving element 122 is in FIG. 1C While described as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. For example, WTRU 102 may use MIMO technology. Therefore, in one embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0037] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0038] The processor 118 of WTRU 102 can be connected to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) or organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad 128. Additionally, the processor 118 can access information from any type of suitable memory and store data in said memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a Subscriber Identity Module (SIM) card, Memory Stick, Secure Digital (SD) memory card, etc. In other embodiments, the processor 118 can access information from memory and store data in memory that is not physically located on WTRU 102, for example, on a server or home computer (not shown).

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

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

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

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

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

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

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

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

[0047] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, activating / deactivating bearers, selecting a specific serving gateway during initial contact with WTRUs 102a, 102b, and 102c, and so on. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies (such as GSM and / or WCDMA).

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

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

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

[0051] Although WTRU is FIG. 1D While described as a wireless terminal, it is conceivable in some representative embodiments that such a terminal may use (e.g., temporarily or permanently) a wired communication interface of a communication network.

[0052] In a representative embodiment, another network 112 may be a WLAN.

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

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

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

[0056] Very 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 adjacent 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels or by combining two non-consecutive 80MHz channels; this is known as an 80+80 configuration. In the 80+80 configuration, after channel coding, the data can pass through a segmented parser that divides the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. The streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC) layer, entities, etc.

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

[0058] WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah) include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STAs operating in the BSS, supporting minimum bandwidth operating modes. In the 802.11ah example, for STAs supporting (e.g., only supporting) 1MHz mode (e.g., MTC type devices), the primary channel can be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports 1MHz operating mode) is transmitting to the AP, the entire available band can be considered busy even if most of the band remains idle and available.

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

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

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

[0062] WTRU 102a, 102b, and 102c can communicate with gNB 180a, 180b, and 180c using transmissions associated with a scalable digital architecture. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRU 102a, 102b, and 102c can communicate with gNB 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various lengths or scalable lengths (e.g., including a varying number of OFDM symbols and / or a continuously varying absolute time).

[0063] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without needing to access other RANs (e.g., eNode-B160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, and also with another RAN such as eNode-B160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement the DC principle to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, and one or more eNode-B160a, 160b, and 160c. In a non-standalone configuration, eNode-B160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

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

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

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

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

[0068] UPF 184a and 184b can be connected via the N3 interface to one or more of gNB180a, 180b, and 180c in RAN 113. This provides WTRU102a, 102b, and 102c with access to packet-switched networks such as Internet 110, for example, to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and so on.

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

[0070] Given FIGS. 1A-1D and FIG. 2 The corresponding descriptions herein refer to one or more or all of the functions described in any of the following: WTRU102a-d, base station 114a-b, eNode-B160a-c, MME 162, SGW 164, PGW 166, gNB180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other element / device described herein, which may be performed by one or more emulated elements / devices (not shown). An emulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0072] One or more emulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in test scenarios within test laboratories and / or non-deployed (e.g., testing) wired and / or wireless communication networks to perform testing of one or more components. One or more emulation devices may be test equipment. Emulation devices may transmit and / or receive data using direct RF connections and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0073] introduce

[0074] 3GPP Rel-15 introduced Radio Access Technology (RAT) in Frequency Range 2 (FR2), specifically 24.2552.6 GHz, in New Radio (NR). Since propagation loss increases with carrier frequency, a key challenge for FR2 is its high propagation loss. Efficient use of highly directional beamforming in transmission and reception can mitigate this high propagation loss.

[0075] Beamforming gain can be achieved by adding one signal to another or subtracting one signal from another. Since higher beamforming gain can be achieved as more signals are added or subtracted, a large number of antenna elements are typically required for highly directional beamforming transmissions. Controlling signal addition or subtraction can be accomplished by controlling the phase of the antenna elements.

[0076] Based on phase control type, beamforming methods can be classified into three types (i.e., analog beamforming, digital beamforming, and hybrid beamforming). Digital beamforming controls the phase of the signal by applying a digital precoder, while analog beamforming controls the phase of the signal by a phase shifter. Generally, digital beamforming offers good flexibility (e.g., applying different phases to different frequency resource blocks), but requires a more complex implementation. In contrast, analog beamforming offers a relatively simple implementation, but has some limitations (e.g., using the same analog beam for the entire frequency resource). Therefore, hybrid beamforming, which combines analog and digital beamforming (examples of which are shown in...), is a more advanced approach. Joint BFR based on explicit configuration of estimated and measured beams (As shown in the figure) it can achieve large beamforming gain with flexibility and reasonable implementation complexity.

[0077] Because the beamwidth of a beam decreases as beamforming gain increases, a beam can only cover a limited area. Therefore, base stations (BSs) and / or UEs need to utilize multiple beams to cover the entire cell. For example, broadcast signals such as synchronization signal blocks (SSBs) can be transmitted in all directions (e.g., via beam scanning) to cover the entire cell. For unicast transmissions between the BS and UE, beam management provides a process for optimizing the beam direction to the UE. Beam management includes selecting and maintaining beam directions for unicast transmissions (including control and data channels) between the BS and UE.

[0078] Beam management can be categorized into beam determination, beam measurement and reporting, beam switching, beam indication, and beam recovery. In beam determination, the BS and UE determine the beam direction to ensure good radio link quality for unicast control and data channel transmission. Once the link is established, the UE measures the link quality of multiple transmit (TX) and receive (RX) beam pairs and reports the results to the BS. As is known, UE mobility, orientation, and channel congestion can affect the radio link quality of TX and RX beam pairs. When the quality of the current beam pair degrades, the BS and UE can switch to another beam pair with better radio link quality. To do this, the BS and UE can monitor the quality of the current beam pair and one or more other beam pairs and perform a switchover when necessary. The beam indication procedure is used when the BS assigns a TX beam to the UE via downlink (DL) control signaling. Beam recovery requires a recovery procedure when the link between the BS and UE can no longer be maintained.

[0079] In RAN#94e, a research project on AI / ML for the NR air interface was approved to identify the benefits of AI / ML for the air interface. The research project investigated AI / ML models, terminology, and descriptions for multiple use cases to identify common and specific features of the framework: enhanced CSI feedback (e.g., reduced overhead, improved accuracy, prediction), beam management (e.g., beam prediction in the time and / or spatial domains for reduced overhead and latency, improved beam selection accuracy), and enhanced positioning accuracy for various scenarios, including those with heavy NLOS conditions.

[0080] For beam management, RAN 1#109-e agrees on two cases: BM-Case 1: spatial domain DL beam prediction for beam set A based on measurement results of beam set B; and BM-Case 2: temporal DL beam prediction for beam set A based on historical measurement results of beam set B.

[0081] Based on the evaluation results, spatial domain beam prediction (BM-Case 1) generally exhibits good beam prediction probability. However, since the beam measurement signal is cell-specific rather than UE-specific, RS overhead reduction should be achieved not only for beam measurement but also for other purposes, including beam fault recovery.

[0082] It is unclear how the UE supports beam fault recovery (BFR) based on predicted RSRP values ​​from partial measurements, or how the UE supports reliable beam fault recovery when it supports partial measurements.

[0083] The first embodiment provides joint BFR based on the explicit configuration of the estimated beam and the measured beam. The UE uses beam fault detection of different qualities based on the beam type of the RS (e.g., the hypothetical physical downlink control channel block error rate (PDCCH BLER) used for estimating the beam and the received signal received power (RSRP) used for the transmit beam, prioritizes the transmit beam for new beam selection (e.g., adds an RSRP value), and indicates the determined reference signal (RS) type used for new beam selection.

[0084] The UE receives information indicating one or more Beam Failure Detection (BFD) RSs, one or more new Candidate Beam (NCB) RSs, a first threshold, a second threshold, a third threshold, an incremental value (e.g., to be used for prioritizing measurements from the transmitted beam), a first Physical Random Access Channel (PRACH) resource, a second PRACH resource, a first Control Resource Set / Synchronization Signal (CORESET / SS), and a second CORESET / SS configuration. Each RS can be a first RS type (e.g., a transmitted beam) or a second RS type (e.g., an estimated beam).

[0085] If one or more configured BFD RSs fail, the UE determines a beam fault instance. How an RS fault is defined can depend on the RS type. For a first RS type, the UE determines a BFD RS beam fault if the measured parameters of the RS's first type (e.g., the assumed PDCCH BLER) are below a first threshold. For a second RS type, the UE determines a BFD RS beam fault if the predicted parameters of the RS's second type (e.g., RSRP) are below a second threshold.

[0086] If the number of beam fault instances within the first time window exceeds a third threshold, the UE initiates beam fault recovery and determines the optimal RS from one or more NCB RSs based on a third-type measurement parameter (e.g., RSRP) of one or more NCB RSs. For NCB RSs of the first RS type, the UE determines the third-type measurement parameter plus the incremental value of the NCB RS. For NCB RSs of the second RS type, the UE determines the third-type prediction parameter based on the predicted value of the NCB RS.

[0087] The UE transmits PRACH based on the determined RS type. If the determined RS is the first RS type, the UE transmits PRACH in the first PRACH resource. If the determined RS is the second RS type, the UE transmits PRACH in the second PRACH resource.

[0088] The UE monitors the PDCCH based on a determined RS type. If the determined RS is a first RS type, the UE monitors the PDCCH in the first CORESET / SS. If the determined RS is a second RS type, the UE monitors the PDCCH in the second CORESET / SS.

[0089] The second embodiment provides a joint BFR based on the implicit configuration of the estimated beam and the measured beam.

[0090] The UE dynamically determines the type of quality parameters used for beam fault detection in beam estimation (e.g., if PDCCH / PDSCH is measured, the demodulation reference signal (DM-RS) and assumed PDCCH BLER are used; otherwise, beam prediction and predicted RSRP are used). The UE determines the optimal new beam and applies different PRACH transmissions (e.g., contention-free transmit beam and contention-based estimated beam) for the new beam indication.

[0091] The UE receives information indicating the configuration of one or more Transport Configuration Index (TCI) states, one or more NCBRS, a first threshold, a second threshold, a third threshold, a first time window, contention-free PRACH resources, and one or more CORESETs associated with contention-based PRACH resources. Each RS can be a first RS type (e.g., transmit beam) or a second RS type (e.g., estimated beam).

[0092] The UE determines one or more BFD RS and BFD RS types based on the RS configured in one or more TCI states.

[0093] If all of one or more BFD RSs fail, the UE determines a beam fault instance. RS faults can be defined differently depending on the RS type. For a first RS type, the UE determines a beam fault if the RS's measurement quality (e.g., assumed PDCCH BLER) is below a first threshold. For a second RS type, if one or more PDCCH / PDSCHs are transmitted within a first time window (e.g., in / by one or more CORESETs associated with the RS), the UE determines a beam fault if the DMRS measurement quality (e.g., assumed PDCCH BLER) of the one or more PDCCH / PDSCHs is below a second threshold; if no PDCCH / PDSCHs are transmitted within the first time window, the UE determines a beam fault if the RS's prediction quality (e.g., assumed PDCCH BLER) is below the second threshold.

[0094] If the number of beam fault instances within the first time window is greater than the third threshold, the UE begins beam fault recovery and determines the best RS from one or more NCB RSs based on the measurement quality / prediction quality (e.g., RSRP) of one or more NCB RSs.

[0095] The UE transmits PRACH in the PRACH resource associated with the determined best RS. If the UE determines that the best RS is of the first RS type, the UE transmits PRACH in a contention-free PRACH resource. If the UE determines that the best RS is of the second RS type, the UE transmits PRACH in a contention-based PRACH resource.

[0096] The UE monitors the PDCCH via one or more CORESETs.

[0097] The third embodiment provides dynamic BFR mode activation / deactivation. The UE determines the BFR operating mode (e.g., BFR based on only the transmitted beam or a joint BFR based on both the transmitted beam and the estimated beam) based on the quality of the prediction (e.g., RSRP difference or beam prediction accuracy).

[0098] The UE receives information indicating the configuration of one or more Beam Failure Detection (BFD) RSs, one or more New Candidate Beam (NCB) RSs, a first threshold, a second threshold, a third threshold, a fourth threshold, a fifth threshold, a sixth threshold, PRACH resources, a first PRACH sequence, a second PRACH sequence, a first CORESET, and a second CORESET. Each RS can be of a first RS type (e.g., transmit beam) or a second RS type (e.g., estimate beam).

[0099] The UE determines the prediction quality based on one or more BFD RS and one or more NCB RS, including, for example, the difference between the predicted RSRP value and the actual measured RSRP value (e.g., based on DMRS from PDCCH / PDSCH) and the beam prediction accuracy (e.g., the predicted best beam versus the actual best beam).

[0100] The UE determines the BFR mode based on the predicted quality and a first threshold. For example, if the predicted quality is less than the first threshold, the UE determines a first BFR mode (e.g., using only the first RS type for BFD and NCB (e.g., disabling one or more RSs with a second type)), and if the predicted quality is greater than the first threshold, the UE determines a second BFR mode (e.g., using both the first and second RS types for BFD and NCB (e.g., activating all RSs configured for BFD and NCB)).

[0101] The UE determines the set of beam fault detection / recovery parameters based on the predicted quality. For example, the UE determines to use one of a second and a third threshold for BFD RS fault detection of type second RS based on the predicted quality. The UE determines to use one of a fourth and a fifth threshold for beam fault detection based on the predicted quality.

[0102] If all of one or more active BFD RSs fail, the UE determines a beam fault instance. For the first RS type, if the measurement quality of the RS is below a sixth threshold, the UE determines the RS to be beam faulted. For the second RS type, if the measurement quality of the RS is below one of the second and third thresholds determined by the UE, the UE determines the RS to be beam faulted.

[0103] The UE detects beam faults based on the number of beam fault instances and a threshold determined by the UE. If the number of beam fault instances within a time window determined by the UE is greater than either a fourth threshold or a fifth threshold, the UE initiates beam fault recovery and determines the optimal RS from the active NCB RS based on the measurement quality of the active NCB RS.

[0104] The UE transmits PRACH in the PRACH resource based on the determined BFR mode. If the UE determines a first BFR mode, the UE transmits PRACH using a first PRACH sequence. If the UE determines a second BFR mode, the UE transmits PRACH using a second PRACH sequence.

[0105] The UE monitors the PDCCH based on a determined BFR mode. If the UE determines a first BFR mode, the UE monitors the PDCCH in the first CORESET. If the UE determines a second BFR mode, the UE monitors the PDCCH in the second CORESET.

[0106] Here, “one,” “a,” and similar phrases will be interpreted as “one or more” and “at least one.” Similarly, any term ending with the suffix “(s)” will be interpreted as “one or more” and “at least one.” The term “may” will be interpreted as “may, for example.”

[0107] The symbol " / " (e.g., a forward slash) can be used here to mean "and / or", where "A / B" for example can imply "A and / or B".

[0108] Artificial intelligence (AI) can be broadly defined as the behavior exhibited by machines. Such behavior can, for example, mimic cognitive functions such as perception, reasoning, adaptation, and action.

[0109] Machine learning (ML) can refer to a type of algorithm that solves problems based on learning from experience (“data”) rather than explicitly programming (“configuring a set of rules”). Machine learning can be considered a subset of AI. Different machine learning paradigms can be envisioned based on the nature of the data or feedback available to the learning algorithm. Supervised learning can involve learning a function that maps inputs to outputs based on labeled training examples, where each training example can be a pair consisting of an input and a corresponding output. Unsupervised learning can include detecting patterns in data without pre-existing labels. Reinforcement learning can involve performing a sequence of actions in an environment to maximize cumulative rewards. Machine learning algorithms can be applied using combinations or interpolation of machine learning techniques. For example, semi-supervised learning methods can use a combination of a small amount of labeled data and a large amount of unlabeled data during training. In this respect, semi-supervised learning falls between unsupervised learning (no labeled training data) and supervised learning (only labeled training data).

[0110] Deep learning (DL) refers to machine learning algorithms that employ artificial neural networks (specifically, DNNs) loosely inspired by biological systems. Deep neural networks (DNNs) are a special class of machine learning models inspired by the human brain, where the input is linearly transformed and passed multiple times through a non-linear activation function. DNNs typically consist of multiple layers, each composed of a linear transformation and a given non-linear activation function. DNNs can be trained using training data via a backpropagation algorithm. Recently, DNNs have demonstrated state-of-the-art performance in various fields, such as speech, vision, natural language processing, etc., and have been used in a variety of supervised, unsupervised, and semi-supervised machine learning settings. The term AIML-based methods / processes can refer to the implementation of explicitly configured behaviors and / or compliance with requirements through data-based learning of sequences of steps without actual actions. Such methods enable the learning of complex behaviors that might be difficult to specify and / or implement using conventional methods.

[0111] Definition of a beam. A UE can transmit or receive physical channels or reference signals based on at least one spatial domain filter. The term "beam" can be used to refer to a spatial domain filter. A UE can use the same spatial domain filter used to receive RS (e.g., CSI-RS) or SS blocks to transmit physical channels or signals. The UE transmission can be referred to as the "target," and the received RS or SS block can be referred to as the "reference" or "source." In this context, it can be said that the UE transmits a target physical channel or signal based on its spatial relationship with the reference RS or SS block.

[0112] The UE can transmit the first physical channel or signal using the same spatial domain filter as the spatial domain filter used to transmit the second physical channel or signal. The first and second transmissions can be referred to as the "target" and the "reference" (or "source"), respectively. In this case, it can be said that the UE transmits the first (target) physical channel or signal based on the spatial relationship with the reference of the second (reference) physical channel or signal.

[0113] Spatial relationships can be implicit, configured by Radio Resource Control (RRC), or signaled by MAC CE or Downlink Control Information (DCI). For example, a UE can implicitly transmit the Physical Uplink Shared Channel (PUSCH) and the DM-RS of the PUSCH based on the same spatial domain filter as the SRS (Sound Reference Signal) indicated by the SRS Resource Index (SRI) in the DCI or configured by RRC. In another example, spatial relationships can be configured by RRC for the SRS Resource Indicator (SRI) or signaled by MAC CE for the PUCCH. This spatial relationship can also be referred to as "beam indication."

[0114] The UE can receive a first (target) downlink channel or signal based on the same spatial domain filter or spatial reception parameters as the second (reference) downlink channel or signal. For example, such an association can exist between physical channels such as PDCCH or PDSCH and their corresponding DM-RS. This association can exist at least when the first and second signals are reference signals, and when the UE is configured with a quasi-co-location (QCL) assumption type D between corresponding antenna ports. This association can be configured as a TCI (Transmission Configuration Indicator) state. Information indicating the association between the CSI-RS or SS block and the DM-RS can be provided to the UE via an index to the set of TCI states configured by the RRC and / or signaled by the MAC CE. This indication can also be referred to as a "beam indication."

[0115] TRP, MTRP, M-TRP: Here, TRP (e.g., transmit and receive points) can be used interchangeably with one or more of TP (transmit point), RP (receive point), RRH (remote radio head), DA (distributed antenna), BS (base station), (BS's) sector, and cell (e.g., the geographic cell area served by the BS), but still conforms to the principles of the present invention. Furthermore, multiple TRPs can be used interchangeably with one or more of MTRP, M-TRP, and multiple TRPs, but still conform to the principles of the present invention.

[0116] CSI Components: The UE may report a subset of Channel State Information (CSI) components, wherein the CSI components may correspond to at least the CSI-RS Resource Indicator (CRI), the SSB Resource Indicator (SSBRI), an indication of the panel used for reception at the UE (such as a panel identifier or group identifier), measurements (such as L1-RSRP, L1-SINR (e.g., CRI-RSRP, CRI-SINR, SSB Index RSRP, SSB Index SINR) obtained from the SSB or CSI-RS), and other channel state information (such as at least the Rank Indicator (RI), Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Layer Index (LI), and / or the like).

[0117] The principles of this invention can be applied using multiple channel and / or interference measurements, which will now be described.

[0118] SSB: The UE can receive the Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block. The SS / PBCH block (SSB) can include the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Physical Broadcast Channel (PBCH). The UE can monitor, receive, or attempt to decode the SSB during initial access, initial synchronization, Radio Link Monitoring (RLM), cell search, and cell handover.

[0119] CSI-RS: The UE can measure and report Channel State Information (CSI), wherein the CSI for each connection mode may include or be configured with one or more of the following: CSI reporting configuration (including the number of CSI reports (e.g., Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI)), CSI reporting type (e.g., aperiodic, semi-persistent, periodic), CSI reporting codebook configuration (e.g., Type I, Type II, Type II port selection) and CSI reporting frequency), CSI-RS resource set (including one or more of NZP-CSI-RS resources for channel measurement, NZP-CSI-RS resources for interference measurement, and CSI-IM resources for interference measurement), and NZP CSI-RS resources (including NZP-RS resource ID, periodicity and offset, QCL information and TCI status, and resource mapping (e.g., number of ports, density, and CDM type)).

[0120] The UE can indicate, determine, or be configured with one or more reference signals. The UE can monitor, receive, and measure one or more parameters based on the corresponding reference signals. The following parameters are non-limiting examples of parameters that can be included in the reference signal measurement. One or more of these parameters may be included. Other parameters may be included.

[0121] SS-RSRP. SS reference signal received power (SS-RSRP) can be measured based on a synchronization signal (e.g., the demodulated reference signal (DMRS) in the PBCH or SSS). It can be defined as a linear average of the power contributions of the resource elements (REs) carrying the corresponding synchronization signal. Power scaling of the reference signal may be required when measuring RSRP. In the case of SS-RSRP used for L1-RSRP, the measurement can be performed based on a CSI reference signal other than the synchronization signal.

[0122] CSI-RSRP. CSI-RSRP can be measured based on a linear average of the power contribution of the resource element (RE) carrying the corresponding CSI-RS. CSI-RSRP measurement can be configured within the measurement resources used for configuring CSI-RS timing.

[0123] SS-SINR. The signal-to-noise ratio and interference ratio (SS-SINR) can be measured based on a synchronization signal (e.g., DMRS in PBCH or SSS). It can be defined as the linear average of the power contribution of the resource element (RE) carrying the corresponding synchronization signal divided by the linear average of the noise and interference power contributions. When SS-SINR is used for L1-SINR, noise and interference power measurements can be performed based on resources configured by the higher layer.

[0124] CSI-SINR. CSI-SINR can be measured based on the linear average of the power contribution of resource elements (REs) carrying the corresponding CSI-RS, divided by the linear average of the noise and interference power contributions. When CSI-SINR is used for L1-SINR, noise and interference power measurements can be performed based on resources configured at higher levels. Otherwise, noise and interference power can be measured based on resources carrying the corresponding CSI-RS.

[0125] RSSI. Received Signal Strength Indicator (RSSI) can be measured based on the average of the total power contribution in the configured OFDM symbols and bandwidth. Power contributions can be received from different resources, such as co-channel serving and non-serving cells, adjacent channel interference, and thermal noise.

[0126] CLI-RSSI. The Cross-Layer Interference Received Signal Strength Indicator (CLI-RSSI) can be measured as the average of the total power contribution across configured OFDM symbols based on configured time and frequency resources. Power contributions can be received from different resources (e.g., cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, and thermal noise).

[0127] SRS-RSRP. The probe reference signal RSRP (SRS-RSRP) can be measured based on the linear average of the power contribution of the resource element (RE) carrying the corresponding SRS.

[0128] SS-RSRQ. The secondary synchronization signal reference signal reception quality (SS-RSRQ) can be measured based on measurements of the received reference signal power (SS-RSRP) and received signal strength (RSSI). In one example, SS-RSRQ can be calculated as the ratio of N × SS-RSRP / NR carrier RSSI, where N can be determined based on the number of resource blocks in the corresponding NR carrier RSSI measurement bandwidth. Thus, the measurements used in the numerator and denominator can be on the same set of resource blocks.

[0129] CSI-RSRQ. CSI Reference Signal Received Quality (CSI-RSRQ) can be measured based on measurements of the received reference signal power (CSI-RSRP) and received signal strength (RSSI). In one example, CSI-RSRQ can be calculated as the ratio of N × CSI-RSRP / CSIRSSI, where N can be determined based on the number of resource blocks in the corresponding CSI-RSSI measurement bandwidth. Thus, the measurements used in the numerator and denominator can be on the same set of resource blocks.

[0130] Beam / CSI Report Configuration. A CSI report configuration (e.g., CSI report setup) can be associated with a single BWP (e.g., indicated by BWP-Id), wherein one or more of the following parameters are configured: CSI-RS resources and / or sets of CSI-RS resources for channel and interference measurements; CSI-RS report configuration type, including periodic, semi-persistent, and aperiodic; CSI-RS transmission period for periodic and semi-persistent CSI reports; CSI-RS transmission slot offset for periodic, semi-persistent, and aperiodic CSI reports; a list of CSI-RS transmission slot offsets for semi-persistent and aperiodic CSI reports; time constraints for channel and interference measurements; report band configuration (wideband / subband CQI, PMI, etc.); thresholds and calculation modes for report quantities (CQI, RSRP, SINR, LI, RI, etc.); codebook configuration; group-based beam reporting; CQI table; subband size; non-PMI port indication; and port index.

[0131] CSI-RS resource configuration. A CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) may include one or more CSI-RS resources (e.g., NZP-CSI-RS resource and CSI-ResourceConfig), wherein the UE may configure one or more of the following in the CSI-RS resources: CSI-RS period and slot offset for periodic and semi-persistent CSI-RS resources; CSI-RS resource mapping to define the number, density, CDM type, OFDM symbol and subcarrier occupancy of CSI-RS ports; the bandwidth portion to which the configured CSI-RS is allocated; and references to TCI-State, including QCL source RS and corresponding QCL type.

[0132] RS resource set configuration. A UE may be configured with one or more RS resource sets, which may include one or more of the following: RS resource set ID; one or more RS resources for the RS resource set; repetition (i.e., on or off); non-periodic trigger offset (e.g., one of 0-6 time slots); and TRS information (e.g., true or false).

[0133] RS resource configuration. A UE may be configured with one or more RS resources, which may include one or more of the following: RS resource ID; resource mapping (e.g., RE in PRB); power control offset (e.g., a value of -8, ..., 15); power control offset with SS (e.g., -3dB, 0dB, 3dB, 6dB); ID scrambling; periodicity and offset; and QCL information (e.g., based on TCI state).

[0134] Attributes of authorization or assignment. Here, the attributes of authorization or assignment may include at least one of the following: frequency allocation; aspects of time allocation, such as duration; priority; modulation and coding scheme; transport block size; number of spatial layers; number of transport blocks; TCI status, CRI, or SRI; number of repetitions; whether the repetition scheme is type A or type B; whether the authorization is a configured authorization type 1, type 2, or dynamic authorization; whether the assignment is a dynamic assignment or a semi-persistent scheduling (configured) assignment; the configured authorization index or semi-persistent assignment index; the periodicity of the configured authorization or assignment; Channel Access Priority Class (CAPC); and any parameters in the DCI, provided by the MAC, or by the RRC for scheduling authorization or assignment.

[0135] Here, the indication of DCI may include at least one of: an explicit indication of the DCI field and an explicit indication of RNTI for masking or scrambling the CRC of the DCI; and an implicit indication of attributes such as DCI format, DCI size, core set or search space, aggregation level, first resource element of the received DCI (e.g., index of the first control channel element), wherein the mapping between attributes and values ​​can be signaled by RRC or MAC.

[0136] Receiving or monitoring a DCI that has or uses a Radio Network Identifier (RNTI) may mean that the DCI's CRC is masked or scrambled using the RNTI.

[0137] In this document, “signal” may be used interchangeably with one or more of the following: sounding reference signal (SRS); channel state information-reference signal (CSI-RS); demodulation reference signal (DM-RS); phase tracking reference signal (PT-RS); and synchronization signal block (SSB).

[0138] In this document, "channel" may be used interchangeably with one or more of the following: Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), and Physical Random Access Channel (PRACH).

[0139] Here, signals, channels, and messages (e.g., in DL or UL signals, channels, and messages) can be used interchangeably, but still conform to the present invention.

[0140] Here, "RS" can be used interchangeably with one or more of "RS resource", "RS resource set", "RS port" and "RS port group".

[0141] Here, “RS” can be used interchangeably with one or more of “SSB”, “CSI-RS”, “SRS”, “DM-RS”, “TRS”, “PRS”, and “PTRS”.

[0142] Here, the terms “time instance”, “time slot”, “symbol” and “subframe” are used interchangeably.

[0143] Here, the terms “SSB”, “SS / PBCH block”, “PSS”, “SSS”, “PBCH” and “MIB” can be used interchangeably.

[0144] The principles of this invention for beam resource prediction can be applied to beam resources belonging to a single or multiple cells and a single or multiple TRPs.

[0145] Here, "CSI Report" can be used interchangeably with "CSI Measurement", "Beam Report", and "Beam Measurement".

[0146] Here, “RS resource set” can be used interchangeably with “beam group”.

[0147] One or more thresholds (i.e., set values) in this invention may be based on one or more predetermined values, semi-statistical configuration values ​​(e.g., RRC), and dynamic indication values ​​(e.g., MAC CE and / or DCI).

[0148] Here, "transmit beam" can be used interchangeably with "transmit beam", "measurement beam", "transmit RS", "measurement RS", "measurement RS", "set A", "type ARS" and "type I RS".

[0149] Here, “estimated beam” can be used interchangeably with “estimated beam”, “predicted beam”, “predicted RS”, “predicted RS”, “estimated RS”, “estimated RS”, “set B”, “type B RS” and “type II RS”.

[0150] Here, "beam ID" can be used interchangeably with "beam pair ID".

[0151] RS configuration for beam fault monitoring and new candidate beams. In at least one embodiment, the UE may support different configurations for transmitting and estimating beams. For example, these configurations may be based on one or more of the following, each of which will be described below: support for measurement type configuration, support for different RS resource sets, support for different QCL configurations, support for beam IDs for estimating beams and RS resource indexes for transmitting beams, and support for auxiliary information for estimating beams using one or more reference RSs.

[0152] Measurement-based configuration is supported. For example, each resource can be configured with a type of RS (e.g., transmit beam or estimate beam). The UE can determine whether the RS is a transmit beam or an estimate beam based on the RS type.

[0153] Different RS resource sets are supported. For example, a UE can be configured with two RS resource sets: one for transmitting beams (e.g., set B) and another for estimating beams (e.g., set A). Each RS resource set can be configured with a measurement type (e.g., transmitting beam or estimating beam). Each RS resource can be configured with an associated RS resource set ID. The UE can determine whether an RS is a transmitting beam or an estimating beam based on the associated RS resource set. For example, if the associated RS resource set is configured as a transmitting beam, the UE can identify the RS as a transmitting beam. If the associated RS resource set is configured as an estimating beam, the UE can identify the RS as an estimating beam.

[0154] Different QCL configurations are supported. In an embodiment, the first RS configuration for transmitting the beam may be based on the beam ID (e.g., CSI-RS resource ID) and QCL information (QCL type-D) used for transmitting the beam, and a beam-only ID (without QCL) used for estimating the beam. The UE can determine whether the RS is a transmitting beam or an estimated beam based on the configured QCL configuration. For example, if the configured QCL information is a QCL type-D RS and a resource ID, the UE can determine the transmitting beam. If the configured QCL information includes a resource ID but does not include QCL information (e.g., QCL type-D RS), the UE can determine the estimated beam. Support is provided for the beam ID (e.g., CSI-RS resource ID) and QCL information (QCL type-D) used for transmitting the beam, as well as the beam ID used to identify the beam characteristics used for estimating the beam and one or more adjacent RS resources. The UE can determine whether the RS is a transmitting beam or an estimated beam based on the configured QCL configuration. For example, if the configured QCL information is a QCL type-D RS and a resource ID, the UE can determine the transmitting beam. If the configured QCL information includes a resource ID and two or more QCL information (e.g., two or more QCL types - D RS), the UE can determine the estimated beam.

[0155] Support is provided for beam IDs used for beam estimation and RS resource indexes used for transmitting beams. In an embodiment, the UE can be configured with a first type of beam ID (e.g., RS resource ID) for transmitting beams and a second type of beam ID (e.g., logical beam ID) for beam estimation. The UE can determine whether the RS is a transmitting beam or an estimated beam based on the configured beam ID type. For example, if the RS is configured with a first type of beam ID (e.g., RS resource ID), the UE can identify the RS as a transmitting beam. If the RS is configured with a second type of beam ID (e.g., logical beam ID), the UE can identify the RS as an estimated beam.

[0156] Support is provided for auxiliary information used to estimate beams using one or more reference RSs. In embodiments, the UE can be configured with one or more reference RSs and auxiliary information for beam estimation. For example, the UE can be configured with a single reference RS having one or more differential angles (e.g., delta angles). The UE can determine the angle of the RS based on the differential angles and the reference RS. For example, horizontal angle = delta_h angle + horizontal angle of the reference RS, vertical angle = delta_y angle + vertical angle of the reference RS. For example, the UE can be configured with two or more reference RSs having one or more differential angles (e.g., delta angles). The UE can determine the angle of the RS based on the differential angles and the reference RSs. For example, horizontal angle = delta1_h angle + horizontal angle of the first reference RS = delta2_h angle + horizontal angle of the second reference RS, vertical angle = delta1_y angle + vertical angle of the first reference RS = delta2_y angle + vertical angle of the second reference RS. The UE can determine whether the RS is a transmit beam or an estimated beam based on the configured auxiliary information and / or the reference RS. For example, if the RS is configured with auxiliary information and / or one or more reference RSs, the UE can identify the RS as the estimated beam. If the RS is configured without auxiliary information and / or reference RSs, the UE can identify the RS as the transmit beam.

[0157] In an embodiment, the UE may determine the beam ID based on explicit configuration, based on the provided beam direction, and by determining one or more of the beam pair IDs (e.g., logical beam ID).

[0158] Explicit configuration. In an embodiment, the UE may receive configuration for each RS resource or each beam ID.

[0159] The beam ID is determined based on the provided beam direction (e.g., beam ID 0 = lowest angle). In embodiments, the UE may be configured with one or more of the following beam information for the transmitted beam and / or estimated beam: the number of transmitted beams (the UE may receive a configuration for each in the horizontal / vertical domain; the UE may indicate a configuration for each in the horizontal / vertical domain (e.g., via UE capability)), the number of estimated beams (the UE may receive information indicating a configuration for each in the horizontal / vertical domain; the UE may indicate a configuration for each in the horizontal / vertical domain (e.g., via UE capability)); the coverage of the transmitted beam (e.g., angular coverage such as 120 degrees); the coverage of the estimated beam (e.g., angular coverage such as 60 degrees); the position / center / direction of the transmitted beam (e.g., 0 degrees); the estimated beam... The position / center / direction of the beam (e.g., 0 degrees); the granularity of the transmitted beam, e.g., 3 degrees (the UE can receive a configuration for each of the horizontal / vertical domains; the UE can indicate a configuration for each of the horizontal / vertical domains (e.g., via UE capabilities)); the estimated beam granularity, e.g., 12 degrees (the UE can receive a configuration for each of the horizontal / vertical domains; the UE can indicate a configuration for each of the horizontal / vertical domains (e.g., via UE capabilities); UE panel related information (number of UE panels, position / center / direction of UE panels); the number of gNBTRPs and / or panels (number of gNBTRPs and / or panels, position / center / direction of gNBTRPs and / or panels).

[0160] Based on configuration and / or predefined rules, the UE can determine the necessary information to transmit / estimate the beam.

[0161] In an embodiment, the UE can determine the number of transmit beams and / or estimated beams based on configured beam information. For example, the UE can divide the coverage of an indicated transmit beam / estimated beam (e.g., 120 degrees) into granular angles (e.g., 10 degrees) to determine the number of transmit beams and / or estimated beams (e.g., 12). The UE can measure and / or transmit the transmit beams / estimated beams based on the determined number of transmit beams and / or estimated beams.

[0162] In an embodiment, the UE can determine the direction / location / granularity of the transmitted beam and / or estimated beam based on configured beam information. For example, the UE can divide the indicated coverage (e.g., 120 degrees) into multiple transmitted beams / estimated beams (e.g., 12 beams) to determine the location of the estimated beams (e.g., 5, 15, 25, ..., 115 degrees).

[0163] Determine the beam pair ID. In an embodiment, the UE can determine the beam pair ID based on the beam ID. For example, the following equations can be used: Beam pair ID = TX beam ID * RX number of beams + RX beam ID. Beam pair ID = RX beam ID * TX number of beams + TX beam ID.

[0164] FIG. 3

[0165] refer to Separate BFR based on estimated and measured beams In an embodiment of the principle of the present invention, the UE performs beam fault detection with different quality based on the beam type of the RS (e.g., the hypothetical PDCCH BLER for estimating the beam and the RSRP for transmitting the beam), prioritizes the transmitting beam for new beam selection (e.g., adds an RSRP value), and indicates the determined RS type for new beam selection.

[0166] In step S302, the UE receives configuration information, which includes one or more of the following: Beam Failure Detection (BFD) RS, one or more New Candidate Beams (NCB) RS, a first threshold, a second threshold, a third threshold, an increment value, a first PRACH resource, a second PRACH resource, a first CORESET / SS, and a second CORESET / SS. The RS can be of the first RS type (e.g., transmit beam) or the second RS type (e.g., estimate beam).

[0167] In step S304, if each configured BFD RS fails, the UE can determine a beam fault instance. For a first RS type, if the measured parameter (e.g., RSRP) of the first type of BFD RS is below a first threshold, the beam fault of that RS is determined. For a second RS type, if the predicted parameter (e.g., assumed PDCCH BLER) of the second type of RS is below a second threshold, the beam fault of that BFD RS is determined.

[0168] If the number of beam fault instances within the first time window exceeds a third threshold, in step S306, the UE may initiate beam fault recovery and determine the RS (e.g., optimal) from one or more NCB RSs based on a third type of measurement parameter (e.g., RSRP) of one or more NCB RSs. For NCB RSs of the first RS type, the UE determines the incremental value of the third type of measurement parameter + NCB RS. For NCB RSs of the second RS type, the UE determines the third type of prediction parameter based on the predicted value of the NCB RS.

[0169] In step S308, the UE transmits PRACH based on the determined RS type. If the determined RS is a first RS type, the UE transmits PRACH in the first PRACH resource. If the determined RS is a second RS type, the UE transmits PRACH in the second PRACH resource.

[0170] In step S310, the UE monitors the PDCCH based on the determined RS type. If the determined RS is a first RS type, the UE monitors the PDCCH in the first CORESET / SS. If the determined RS is a second RS type, the UE monitors the PDCCH in the second CORESET / SS.

[0171] The UE can support beam fault recovery by jointly utilizing the transmitted RS and the estimated RS.

[0172] The UE can receive information corresponding to one or more configurations that can be used for beam fault recovery.

[0173] The UE can be configured with, for example, a beam fault detection (BFD) RS (e.g., One or more of the following: Each BFD RS can be a transmitting RS or an estimated RS. The configuration of BFD-RS can be based on the explicit configuration of the gNB. The configuration of BFD-RS can also be based on the implicit configuration. For example, if the UE does not receive an explicit configuration of BFD-RS, the UE can determine one or more BFD-RS based on one or more RSs with QCL type-D in the configuration TCI state used for PDCCH reception (e.g., in the configured CORESET / SearchSpaces).

[0174] The UE can be configured with one or more counters and one or more maximum numbers of the one or more counters. The counters can be, for example, a BFD counter and a threshold for the BFD counter, a beam reporting counter and a threshold for the beam reporting counter, and a preamble power ramp-up counter and a threshold for the preamble power ramp-up counter.

[0175] When a set of counters (e.g., one or more of BFD counters, beam reporting counters, and preamble power ramp counters) and thresholds is configured, the set of counters and thresholds can be used for both beam estimation and transmit beam estimation. If multiple sets of counters (e.g., one or more of BFD counters, beam reporting counters, and preamble power ramp counters) and thresholds are configured, a first set of counters and thresholds can be used for transmit beam estimation, while a second set of counters and thresholds can be used for beam estimation. The number of configured counters and the number of configured thresholds in each set can be the same.

[0176] The UE can be configured with one or more timers, such as the BFI timer, BFD timer, and BFR timer.

[0177] When a set of timers (e.g., one or more of BFI, BFD, and BFR timers) is configured, the set of timers can be used for both transmitting and estimating the beam. If multiple sets of timers are configured, a first set of timers can be used for transmitting the beam, and a second set of timers can be used for estimating the beam.

[0178] The UE can be configured with a new candidate beam (NCB) RS (e.g., One or more sets of BFD-RS. The configuration of BFD-RS can be based on the explicit configuration of the gNB. Each of the one or more BFD RSs can be a transmit RS or an estimate RS. Each RS in the NCB-RS can be associated with one or more uplink resources (e.g., PRACH (resources and / or sequences), PUCCH, PUSCH, and / or SRS).

[0179] The UE can be configured with one or more uplink resources (S) for new candidate beam indication, where S is one or more uplink resources indicating a new candidate beam. Each uplink resource can be associated with each NCB-RS. Each uplink resource can be associated with an NCB-RS type. For example, a first uplink resource can be associated with a transmit beam, and a second uplink resource can be associated with an estimated beam.

[0180] The UE can be configured with a CORESET and / or a search space (C) for receiving one or more acknowledgment random access responses from the BFR, wherein C i It is a set of search spaces used to receive the random access response of the BFR. Each CORESET / search space can be associated with an NCB-RS type. For example, the first CORESET / search space can be associated with the transmit beam, and the second CORESET / search space can be associated with the estimated beam.

[0181] If the number of faulty BFD RSs exceeds a threshold (e.g., all configured BFD RSs are faulty), the UE can identify a beam fault instance. BFD RS faults can be defined, for example, based on the application of the same set of measurement parameters and thresholds (e.g., if the measurement parameters of an RS (e.g., assumed PDCCH BLER or RSRP) are below a threshold, the UE can identify a beam fault). BFD RS faults can also be defined based on the application of different sets of measurement parameters and thresholds (e.g., the UE can apply different sets of parameters and thresholds based on the RS type; for example, for a first RS type, if the measurement parameters of the first type of RS (e.g., assumed PDCCH BLER) are below a first threshold, the UE can identify a beam fault for the BFD RS; for a second RS type, if the prediction parameters of the second type of RS (e.g., RSRP) are below a second threshold, the UE can identify a beam fault for the BFD RS).

[0182] If the number of detected beam fault instances within a time window exceeds a corresponding threshold, the UE can determine a beam fault recovery process. For example, the UE can initiate a process for new beam selection. The UE can determine one or more RSs from one or more NCB RSs based on one or more measured parameters.

[0183] The UE can determine one or more RSs based on the same set of measurement parameters and thresholds. For example, the UE can measure parameters of the same type (e.g., RSRP) of one or more NCB RSs. If the measured parameters of one or more NCB RSs are above a threshold, the UE can determine one or more RSs (e.g., having the highest quality based on the measurement parameters). The UE can apply an offset to the measured parameters based on the RS type. For example, the UE can determine the measured parameter as the final value of a first RS type (e.g., transmit beam). The UE can determine the measured parameter – increment value as the final value of a second RS type (e.g., estimated beam). The UE can also apply an offset to the measured parameters based on the RS type. For example, the UE can determine the measured parameter + increment value as the final value of a first RS type (e.g., transmit beam). The UE can determine the measured parameter as the final value of a second RS type (e.g., estimated beam).

[0184] The UE can apply different sets of parameters and thresholds based on the RS type. For example, the UE can measure different types of measurement parameters (e.g., measured RSRP or predicted RSRP) based on the RS type in one or more NCB RSs. When the measured parameter of an RS is higher than the corresponding threshold, the UE can determine one or more RSs based on the determined measurement parameters (e.g., having the highest quality based on the measurement parameters).

[0185] For example, for a first RS type, the UE can determine one or more RSs from one or more NCB RSs based on a first set of measurement parameters (e.g., measured RSRP) and thresholds. For a second RS type, the UE can determine one or more RSs from one or more NCB RSs based on a second set of measurement parameters (e.g., measured RSRP) and thresholds.

[0186] The UE may transmit one or more uplink channels and / or signals for beam failure event indication and / or new candidate beam indication. The uplink channels and / or signals may be one or more of MAC-CE, RRC, PRACH (e.g., RACH msg 1, msg 3, msg A), PUSCH, PUCCH, PUSCH DM-RS, SR, SRS, and similar SR signals, wherein similar SR signals may be uplink channels that can be periodically reserved.

[0187] A UE can transmit one or more uplink channels based on the same set of uplink resource configurations. For example, regardless of the RS type of one or more defined NCB RSs, a UE can transmit one or more uplink channels based on the same set of uplink resource configurations (e.g., using the same uplink sequence and / or within the same uplink resources).

[0188] A UE can transmit one or more uplink channels based on different sets of uplink resource configurations. For example, based on the RS type of one or more determined NCB RSs, the UE can determine different uplink resource configurations for transmitting one or more uplink channels. For example, for a first RS type, the UE can transmit one or more uplink channels based on a first set of uplink resource configurations (e.g., using a first uplink sequence and / or in the first uplink resources). For a second RS type, the UE can transmit one or more uplink channels based on a second set of uplink resource configurations (e.g., using a second uplink sequence and / or in the second uplink resources).

[0189] The UE may receive one or more downlink channels and / or signals for confirming beam failure event indications and / or new candidate beam indications (e.g., from the gNB). Downlink channels and / or signals may be one or more of PDCCH, PDSCH, MACCE, RRC, PDCCH DM-RS, PDSCH DM-RS, CSI-RS, SSB, TRS (e.g., CSI-RS for tracking), and PT-RS. Downlink resources may be based on one or more of the following.

[0190] A UE can receive one or more downlink channels based on the same set of uplink resource configurations. For example, regardless of the RS type of one or more indicated NCB RSs, a UE can receive one or more downlink channels based on the same set of downlink resource configurations (e.g., utilizing the same CORESET / SearchSpace / time and frequency resources).

[0191] A UE can receive one or more downlink channels based on different sets of downlink resource configurations. For example, based on the RS type of one or more indicated NCB RSs, the UE can determine different downlink resource configurations for receiving one or more downlink channels. For example, for a first RS type, the UE can receive one or more downlink channels based on a first set of downlink resource configurations (e.g., utilizing a first set of CORESET / SearchSpace / time and frequency resources). For a second RS type, the UE can receive one or more downlink channels based on a second set of downlink resource configurations (e.g., utilizing a second set of CORESET / SearchSpace / time and frequency resources).

[0192] As can be seen, the Wireless Transmit / Receive Unit (WTRU) can determine at least one beam fault, wherein the beam fault is determined based on measurements of a first type of beam and estimates of a second type of beam. After determining the number of beam faults: a specific candidate beam is determined from a plurality of candidate beams based on parameters, wherein the parameters are based on measured parameters for the first type of candidate beam and predicted parameters for the second type of candidate beam; a message is sent, wherein if the determined candidate beam is of the first type, the message is sent on a first resource, and if the determined candidate beam is of the second type, the message is sent on a second resource; and a response is monitored using a set of resources or signals based on the type of the determined candidate beam.

[0193] FIG. 4

[0194] refer to Joint BFR based on implicit configuration of estimated and measured beams In embodiments of the present invention, the UE monitors and / or selects based on a separate set of RSs used for transmitting and estimating the beam. If the UE detects a beam fault, it indicates one or more sets of faults to the gNB (e.g., the gNB currently serving it).

[0195] In step S402, the UE receives first configuration information indicating one or more RSs for a first BFD RS set and one or more RSs for a first NCB RS set having a first RS type, and second configuration information indicating one or more RSs for a second BFD RS set and one or more RSs for a second NCB RS set having a second RS type.

[0196] In step S404, the UE receives third configuration information indicating a first threshold, a second threshold, a third threshold, a fourth threshold, PUCCH resources for scheduling requests, and CORESET.

[0197] In step S406, the UE identifies one or more beam fault instances. If all RSs in the first BFD RS set are faulty (e.g., based on an assumed PDCCH BLER), the UE can identify a beam fault instance for that set, wherein the RS fault instance is identified if the measurement quality of the RS is below a first threshold. If all RSs in the second BFD RS set are faulty (e.g., based on an assumed PDCCH BLER), the UE can also identify a beam fault instance for that set, wherein the RS fault instance is identified if the prediction quality of the RS is below a second threshold.

[0198] In step S408, if the number of beam fault instances determined for the first BFD RS set is greater than a third threshold and / or the number of beam fault instances determined for the second BFD RS set is greater than a fourth threshold, then the UE determines a beam fault.

[0199] In step S410, the UE determines the beam (e.g., the optimal beam) for the faulty BFD RS set based on the measurement quality / prediction quality of the NCB RS set associated with the faulty BFD RS set.

[0200] In step S412, the UE sends a scheduling request via the PUCCH resource for MAC CE.

[0201] In step S414, the UE receives the PDCCH scheduling uplink resources for MAC CE via CORESET.

[0202] In step S416, the UE sends a MAC CE indicating the type of beam fault (i.e., a beam fault detected on the first set of BFD RSs, a beam fault detected on the second set of BFD RSs, or a beam fault detected on both sets).

[0203] The UE can be configured with one or more sets of beam fault detection (BFD) RS (e.g., ).

[0204] For example, two RS sets can be configured for the operating mode, and the first BFD-RS set (e.g., ) can be associated with the transmitted beam, while the second BFD-RS set (e.g., This can be associated with beam estimation.

[0205] BFD-RS configuration can be based on implicit configuration. For example, if the UE does not receive explicit configuration for one or more sets of BFD-RS, the UE can determine one or more sets of BFD-RS based on one or more RSs with QCL type-D in the configuration TCI state for PDCCH reception. For example, the UE can determine one or more sets of BFD-RS based on explicit / implicit CORESET / search space group configuration / indication. CORESET / search space group configuration / indication can be based on one or more explicit or implicit configurations / indications.

[0206] For explicit configuration / indication of CORESET / search space group IDs, a UE can be configured with one or more CORESETs having a CORESET group ID. Based on the group ID, the UE can determine the CORESET group for one or more CORESETs. For example, if a UE is configured with a first CORESET (e.g., for transmitting beams) having a first CORESET group ID and a second CORESET (e.g., for estimating beams) having a second CORESET group ID, the UE can determine the first CORESET as the first CORESET group and the second CORESET as the second CORESET group. The UE can receive the group ID from the TCI state configuration instead of the group ID from the CORESET configuration.

[0207] Implicit configurations / indicators include, for example, RS, CORESET / search space type, or ID configurations that can be used for each CORESET / search space (e.g., CORESET / search space ID and / or TCI status ID).

[0208] For each CORESET / search space, the UE can configure one or more CORESETs and one or more QCL reference RSs (e.g., for QCL type-D) for each CORESET / search space. The UE can determine the BFD-RS set based on the configured QCL reference RSs. For example, if the configured QCL reference RS is of type one (e.g., transmit beam), the UE can determine the reference RS as an RS in the first BFD RS set. If the configured QCL reference RS is of type two (e.g., transmit beam), the UE can determine the reference RS as an RS in the second BFD RS set.

[0209] For CORESET / search space types, a UE can be configured with one or more CORESETs of a CORESET type. Based on the CORESET type, the UE can determine a CORESET group. For example, if the UE is configured with a first CORESET of a first CORESET type (e.g., Joint TCI Status Indication), the UE can determine the first CORESET as the first CORESET group. If the UE is configured with a second CORESET of a second CORESET type (e.g., PDSCH / PUSCH Scheduling), the UE can determine the second CORESET as the second CORESET group.

[0210] For ID configurations (e.g., CORESET / Search Space ID and / or TCI Status ID), the UE can determine the CORESET group based on the ID. For example, if the associated ID of the first CORESET is less than (or equal to) a threshold, the UE can determine the first CORESET as the first CORESET group. If the associated ID of the first CORESET is greater than the threshold, the UE can determine the first CORESET as the second CORESET group.

[0211] The UE can be configured with a new candidate beam (NCB) RS (e.g., one or more sets, where This can be a set of new candidate beams (RSs) associated with either the transmitted beam or the estimated beam. For example, a first set of NCB-RSs can be associated with the transmitted beam, and a second set of NCB-RSs can be associated with the estimated beam. For example, all NCB-RSs in the NCB-RS sets can be associated with an uplink resource. For example, each NCB-RS in this set can be associated with one or more uplink resources (e.g., PRACH, PUCCH, PUSCH, and / or SRS).

[0212] The UE can be configured with one or more uplink resources (S) for new candidate beam indication. i The set S, where S i This is a set of uplink resources used to indicate a new candidate beam for either the transmitted beam or the estimated beam. For example, S0 can be associated with the transmitted beam, and S1 can be associated with the estimated beam.

[0213] The UE can be configured with one or more search spaces (C) for receiving one or more acknowledgment random access responses (BFRs). i ) set, where C i It is the set of search spaces used to receive random access responses to either the transmitted beam or the estimated beam for the BFR. For example, C0 can be associated with the transmitted beam, and C1 can be associated with the estimated beam.

[0214] The UE can determine one or more new candidate beams (q new,i And each new candidate beam can be associated with a different cell, where q new,i This refers to the new candidate beam (or beam index) determined for either the transmitted beam or the estimated beam. For example, a first new candidate beam (q) can be selected from the set of new candidate beams RS associated with the transmitted beam. new,1 Furthermore, a second new candidate beam (q) can be selected from the new candidate beam RS set associated with the estimated beam. new,2 ).

[0215] The UE can be configured with a transmitted beam set and a predicted beam set. The transmitted beam can be associated with a set B or its configuration. For example, the UE can be configured to predict the RSRP of a first beam (i.e., the predicted beam) based on the measured RSRP of a second beam (e.g., the transmitted beam). The terms "predicted beam" and "skipped beam" are used interchangeably. The terms "transmitted beam," "set B beam," and "measured beam" are used interchangeably. The term "beam" can refer to "SSB beam," "CSI-RS beam," or both.

[0216] The UE can receive first configuration information for one or more RSs in a first BFD RS set and one or more RSs in a first NCB RS set having a first RS type, and second configuration information for one or more RSs in a second BFD RS set and one or more RSs in a second NCB RS set having a second RS type. For example, the first configuration information may be associated with a transmitted beam (i.e., a measurement beam / set B beam), and the second configuration information may be associated with a skipped beam (i.e., a predicted beam). For example, the first RS type may be associated with a transmitted beam (i.e., a measurement beam / set B beam), and the second RS type may be associated with a skipped beam (i.e., a predicted beam).

[0217] For beam fault detection / recovery, the UE can be configured with a first threshold, a second threshold, a third threshold, and a fourth threshold. For example, the first threshold can be associated with beam fault instance determination in a first BFD RS set, the second threshold can be associated with beam fault instance determination in a second BFD RS set, the third threshold can be associated with beam fault detection in the first BFD RS set, and the fourth threshold can be associated with beam fault detection in the second BFD RS set.

[0218] The UE may be configured with RACH resources for transmitting scheduling requests associated with beam fault recovery. The UE may be configured with a first RACH resource and a second RACH resource for transmitting scheduling requests associated with beam fault recovery. The UE may be configured with PUCCH resources for transmitting scheduling requests associated with beam fault recovery. The UE may be configured with a first PUCCH resource and a second PUCCH resource for transmitting scheduling requests associated with beam fault recovery. The UE may be configured with CORESET for receiving UL authorization for transmissions of beam fault recovery requests and / or receiving acknowledgments of beam fault recovery. The UE may be configured with a first CORESET and a second CORESET for receiving UL authorization for transmissions of beam fault recovery requests and / or receiving acknowledgments of beam fault recovery.

[0219] The UE can be configured to perform a first beam fault detection procedure associated with a first BFD RS set. For example, the first BFD RS set may be associated with a transmitted beam (i.e., the measurement beam / set B beam). The UE can be configured to evaluate the link quality of the RSs associated with the first BFD set against a first threshold. If all RSs in the first BFD RS set are faulty, the UE can determine a beam fault instance for that set. For example, if the measurement quality of an RS is below the first threshold, an RS fault is determined. The threshold and measurement quality may be based on an assumed PDCCH BLER or RSRP.

[0220] The UE can be configured to perform a second beam fault detection procedure associated with a second BFD RS set. For example, the second BFD RS set may be associated with predicted beams (i.e., skipped beams). The UE can be configured to evaluate the link quality of RSs associated with the second BFD set against a second threshold. If all RSs in the second BFD RS set are faulty, the UE can determine a beam fault instance for that set. For example, if a pre-configured number of RSs in the second BFD RS set are faulty, the UE can determine a beam fault instance for the second BFD RS set. For example, if the predicted quality of an RS is below the second threshold, an RS fault can be determined. The UE can derive the predicted quality of RSs based on the measured quality of one or more RSs from the first BFD RS set. This threshold can be based on a hypothetical PDCCH BLER. This determination can be based on a hypothetical PDCCH BLER threshold that differs from the hypothetical PDCCH BLER threshold associated with the first BFD RS set. A threshold based on RSRP can be applied instead of the BLER threshold.

[0221] The UE can be configured to detect / claim a beam fault if the number of beam fault instances in the first BFD RS set exceeds a third threshold. The UE can be configured to detect / claim a beam fault if the number of beam fault instances in the second BFD RS set exceeds a fourth threshold. The UE can also be configured to detect / claim a beam fault if the number of beam fault instances in both the first and second BFD RS sets exceeds the third and fourth thresholds.

[0222] The UE can be configured with rules to determine the beam for beam recovery (e.g., the optimal beam) based on the state of beam faults in a first BFD RS set and a second BFD RS set. For example, the UE can be configured to determine a beam from the first NCB RS set if a beam fault is detected for both the first and second BFD RS sets. Alternatively, the UE can be configured to determine a beam from the second NCB RS set if a beam fault is detected for the first BFD RS set but not the second BFD RS set. Finally, the UE can be configured to determine a beam from the first NCB set if a beam fault is detected for the second BFD RS set but not the first BFD RS set.

[0223] The UE can be configured to determine the beam for beam recovery based on the state of beam quality associated with a first NCB RS set associated with a first RS type and a second NCB RS set associated with a second RS type, wherein the first RS type can be associated with the transmitted beam (i.e., the measurement beam / set B beam) and the second RS type can be associated with the skipped beam (i.e., the predicted beam).

[0224] The UE can be configured to select the beam for a faulty BFD RS set based on the measurement / prediction quality of the NCB RS set associated with the faulty BFD RS set. The UE can also be configured to select the beam for a faulty BFD RS set based on the measurement / prediction quality of an NCB RS set not associated with the faulty BFD RS set.

[0225] For example, in the event of a beam failure in the first BFD RS set, the UE can be configured to select a beam for recovery from the first NCB RS set. Alternatively, in the event of a beam failure in the first BFD RS set, the UE can be configured to select the recovery beam considering both the first and second NCB RS sets. This selection may be based on the measurement quality of the beam from the first NCB RS set and the predicted quality of the beam from the second NCB RS set. For example, in the event of a beam failure in the second BFD RS set, the UE can be configured to select the recovery beam based on the predicted quality of the beam from the second NCB RS set. For example, in the event of a beam failure in the second BFD RS set, the UE can be configured to select the recovery beam considering both the first and second NCB RS sets, which may be based on the measurement quality of the beam from the first NCB RS set and the predicted quality of the beam from the second NCB RS set.

[0226] If a beam fault is identified for the second BFD RS set but not the first BFD RS set, and if UL authorization is unavailable, the UE may send a scheduling request via the PUCCH resources configured for the second BFD RS set and / or the second NCB RS set. The UE may be configured to receive PDCCH on a CORESET pre-configured for the second BFD RS set and / or the second NCB RS set.

[0227] The UE may transmit one or more UL channels and signals (e.g., PRACH, PUCCH, PUSCH, MAC CE, and SRS) indicating a beam fault, one or more sets of RSs on which a beam fault is detected (e.g., a first, second, or both), and one or more newly selected beams from the detected RS sets. In one example, the UE may explicitly indicate the detected RS sets (e.g., via MAC CE). For example, 0 may indicate beam fault detection from a first RS set (e.g., transmitted RS), 1 may indicate beam fault detection from a second RS set (e.g., estimated RS), and 2 may indicate beam fault detection from both sets (e.g., transmitted and estimated RS). In another example, the UE may implicitly indicate the detected RS sets (e.g., via PUCCH and / or PRACH). For example, if a beam fault is detected from a first set (e.g., transmitted RS), the UE may transmit one or more UL channels and signals in a first UL resource and / or a first UL sequence. The UE may transmit one or more UL channels and signals in the second UL resource and / or the second UL sequence (e.g., estimated RS) of the second set. If a beam fault is detected from both sets, the UE may transmit one or more UL channels in both the first UL resource and / or sequence and the second UL resource and / or sequence.

[0228] If a beam fault recovery request is associated with a first BFD RS set, if a beam fault recovery request is associated with a second BFD RS set, or if a beam fault recovery request is associated with both BFD RS sets, the UE can monitor the PDCCH in the first CORESET / search space.

[0229] FIG. 5

[0230] The UE can monitor the beam fault detection RS set in an active BWP. The UE can further estimate beam and / or radio link quality and report desynchronization and / or synchronization states. In one example, the UE can measure the radio link quality (L1-RSRP) of one or more SSBs and / or one or more CSI-RSs in the corresponding beam fault detection RS set. The UE can then compare the measurement results with corresponding thresholds to determine, indicate, or detect whether a beam fault instance (BFI) has occurred.

[0231] The UE can indicate, determine, or be configured with one or more Beam Failure Detection (BFD) counters. This allows the UE to detect beam failures by counting BFI indications. The UE can indicate, determine, or configure one or more of the following: BFI_Counter (used to count the number of BFIs, initially set to 0 and incrementing with each BFI detection), BFI_Max_Count (the maximum value of BFI_Counter; which can trigger beam failure detection), and BFD_Timer (a timer started with the first BFI detection). If the timer expires before BFI_Counter reaches BFI_Max_Count, the beam failure detection process stops. These parameters are non-limiting examples of parameters that can be used in beam failure detection.

[0232] In one example, if a BFI has already occurred, the UE starts, restarts, or exits the BFD timer and increments BFI_Counter by 1. If BFI_Counter reaches BFI_Max_Count, the UE can trigger a BFD event and initiate a Beam Failure Recovery (BFR) procedure.

[0233] The UE can determine, indicate, or trigger beam fault recovery based on beam fault detection events. The UE can indicate, determine, or configure one or more of the following: BFR_Timer (a timer to begin the beam fault recovery process), RSRP_Threshold (a threshold for RSRP during beam fault recovery), CandidateBeamRSList (a list of candidate beam reference signal indices to be monitored, measured, and selected during beam fault recovery), power ramp (including parameters such as power ramp step size and received preamble target power), and random access data (PRACH parameters, such as preamble index, SSB per RACH timing, random access response window, PRACH configuration index, random access timing, and SSB associated mask index). These parameters are non-limiting examples of parameters that can be included in beam fault detection.

[0234] The UE can use, receive, and / or configure one or more sets of reference signals per BWP for monitoring, measuring, and selecting as resources for beam fault recovery. For example, the term q1 can be used for a beam fault recovery set. In another example, the terms q1,0 or q1,1 can be used as a beam fault recovery set. A beam fault recovery set (e.g., set q1,q1,0 or q1,1) can include one or more reference signals, where the reference signals can be CSI-RS resource configuration indices, SS / PBCH block (SSB) indices, etc. In one example, the reference signals included in the beam fault recovery RS set can be based on CandidateBeamRSList, which is configured as part of the BFR procedure.

[0235] The UE can initiate beam fault recovery based on a random access procedure. In one example, the UE can configure random access parameters, start a BFR_Timer, and apply power ramp parameters. The UE can monitor and measure one or more reference signals from the CandidateBeamRSList. The UE can determine whether at least one SSB has an SS-RSRP higher than the corresponding RSRP_Threshold among the SSBs in the CandidateBeamRSList, or whether at least one of the CSI-RS has a CSI-RSRP higher than the corresponding RSRP_Threshold among the CSI-RS in the CandidateBeamRSList. The UE can then select the corresponding reference signal as a new candidate beam (NCB) and / or random access resource for the BFR procedure. For example, the term q_new can be used to present the newly selected beam and / or random access resource. The UE can perform PRACH transmission in the corresponding random access resource and based on the configuration of the periodic CSI-RS resource or on the spatial relationship of the SS / PBCH block associated with and / or with index q_new through the QCL.

[0236] PRACH preamble transmission can be based on contention-free PRACH transmission, which is subject to the UE being provided with and / or configured with a preamble (e.g., an index) for PRACH transmission. For example, the UE can use configured preambles and / or resources for PRACH transmission (e.g., via one or more of RRC, MAC CE, and DCI). Based on PRACH transmission, the UE can receive a PDSCH (e.g., Msg1) for a random access response. PRACH preamble transmission can also be based on contention-based PRACH transmission, where the UE selects (e.g., randomly) a PRACH preamble (e.g., an index) from a set of available preambles (e.g., indices) for PRACH transmission. For example, the UE can randomly select a preamble and / or PRACH resources from a configured preamble / PRACH resource pool and transmit the PRACH in the selected preamble / PRACH resource (e.g., Msg1). Based on the transmitted PRACH, the UE can receive a PDCCH (e.g., a scheduled PDSCH for a random access response) and a PDSCH (e.g., a random access response) (e.g., within a random access response window). The random access response may contain one or more of the following: an RA preamble identifier, timing alignment information, initial uplink grant, and a temporary C-RNTI. A single PDSCH can carry an RA response to multiple UEs. If the UE receives a random access response containing a random access preamble identifier that is identical to the identifier contained in the transmitted RA preamble, the UE can transmit uplink scheduling information (e.g., Msg3). If the UE does not receive a response within the random access response window or fails to verify the response, the UE can determine that a previous attempt failed. In this case, if the number of random access attempts (e.g., transmitting a PRACH) is less than a threshold (e.g., 10), the UE can transmit another PRACH. If the number of random access attempts is greater than (or equal to) the threshold, random access may fail. If the UE receives a PDCCH (e.g., Msg4) with a C-RNTI or UE contention resolution identifier IE before the contention resolution timer expires (e.g., 4ms), the UE can determine that the random access procedure was successful and apply the received C-RNTI to future operations. If the contention resolution timer expires before the PDCCH is received, the UE can perform the random access procedure again. If the number of random access procedure attempts is equal to (or greater than) a threshold (e.g., 10), the UE can assume that the random access procedure failed.

[0237] The UE can determine, identify, or configure one or more CORESETs corresponding to random access procedures for recovery from corresponding beam faults. In one example, the UE can monitor the PDCCH in the search space set to detect a DCI format with a corresponding CRC scrambled using a radio network identifier (e.g., C-RNTI or MCS-C-RNTI). The UE can determine antenna port quasi-co-address parameters that are identical to the antenna port quasi-co-address parameters associated with the index q_new for monitoring the PDCCH in the search space set and receiving the corresponding PDSCH.

[0238] If the BFR_Timer has expired and the beam fault recovery process has not been successfully completed, the UE can trigger link fault detection and then proceed with the link fault recovery (LFR) process.

[0239] refer to Dynamic BFR mode activation / deactivation In this embodiment, the UE dynamically determines the type of quality parameters for beam fault detection used to estimate the beam (e.g., DMRS and assumed PDCCH BLER are used if PDCCH / PDSCH is measured; otherwise, beam prediction and predicted RSRP are used). The UE determines the optimal new beam and applies different PRACH transmissions (e.g., contention-free transmit beam and contention-based estimated beam) for the new beam indication.

[0240] In step S502, the UE receives configuration information indicating one or more CORESETs associated with one or more TCI states, one or more NCBRSs, a first threshold, a second threshold, a third threshold, a first time window, contention-free PRACH resources, and contention-based PRACH resources. Each RS can be a first RS type (e.g., transmit beam) or a second RS type (e.g., estimate beam).

[0241] In step S504, the UE determines one or more BFDRS and BFD RS types based on the RS configured in one or more TCI states.

[0242] In step S506, if all of one or more BFD RSs fail, the UE determines a beam fault instance. For a first RS type, if the measurement quality of the RS (e.g., assumed PDCCH BLER) is below a first threshold, the UE determines the RS has a beam fault. For a second RS type, if one or more PDCCH / PDSCHs are transmitted within a first time window (e.g., in / by one or more CORESETs associated with the RS), then if the measurement quality of the DMRS of one or more PDCCH / PDSCHs (e.g., assumed PDCCH BLER) is below a second threshold, the UE determines the RS has a beam fault. For a second RS type, if no PDCCH / PDSCHs are transmitted within the first time window, then if the prediction quality of the RS (e.g., assumed PDCCH BLER) is below a second threshold, the UE determines the RS has a beam fault.

[0243] If the number of beam fault instances within the first time window is greater than the third threshold, then in step S508, the UE begins beam fault recovery and determines the RS (e.g., the best RS) from one or more NCB RSs based on the measurement quality / predicted quality (e.g., RSRP) of one or more NCB RSs.

[0244] In step S510, the UE transmits PRACH in the PRACH resource associated with the determined best RS. If the UE determines that the RS is a first RS type, the UE transmits PRACH in a contention-free PRACH resource. If the UE determines that the RS is a second RS type, the UE transmits PRACH in a contention-based PRACH resource.

[0245] In step S512, the UE monitors the PDCCH via one or more CORESETs.

[0246] The UE can receive configuration information and be configured accordingly for beam fault recovery.

[0247] The UE can be configured with beam fault detection (BFD) RS (e.g., One or more of the following: Each BFD RS can be a transmitting RS or an estimated RS. The configuration of BFD-RS can be based on the explicit configuration of the gNB. The configuration of BFD-RS can also be based on the implicit configuration. For example, if the UE does not receive an explicit configuration of BFD-RS, the UE can determine one or more BFD-RS based on one or more RSs with QCL type-D in the configuration TCI state used for PDCCH reception (e.g., in the configured CORESET / SearchSpaces).

[0248] The UE can be configured with one or more counters and one or more maximum numbers of these counters, such as a BFD counter and its threshold, a beam reporting counter and its threshold, and a preamble power ramp-up counter and its threshold.

[0249] The UE can be configured with one or more timers, such as the BFI timer, BFD timer, and BFR timer.

[0250] The UE can be configured with one or more sets of new candidate beams (NCBs) RS (e.g., The configuration of BFD-RS can be based on the explicit configuration of the gNB. Each BFD RS can be a transmit RS or an estimate RS. Each NCB-RS can be associated with one or more uplink resources (e.g., PRACH (resources and / or sequences), PUCCH, PUSCH, and / or SRS).

[0251] The UE can be configured with one or more uplink resources (S) for new candidate beam indication, wherein S is one or more uplink resources for indicating new candidate beams. Each uplink resource can be associated with each NCB-RS.

[0252] The UE can be configured with a CORESET and / or a search space (C) for receiving one or more acknowledgment random access responses from the BFR, wherein C i It is the set of search spaces used to receive random access responses from BFRs.

[0253] The UE can receive configuration information for one or more CORESETs associated with one or more TCI states used for beam fault detection. In one example, the UE can be configured and / or provided with one or more beam fault detection RS sets for the BWP. The beam fault detection RS set for the BWP can be based on the reference signal resource configuration used by the UE to monitor the PDCCH in the corresponding CORESET, as indicated by the TCI state.

[0254] The UE can be configured with BFD reference signals of type 1, type 2, etc. In one example, the type 1 BFD reference signal may indicate that the reference signal is based on the beam being transmitted; the type 2 BFD reference signal may indicate that the reference signal is based on the estimated beam. The UE can determine one or more BFDRS and BFDRS types based on RS configured in one or more TCI states.

[0255] The UE can receive and / or be configured to use one or more New Candidate Beam (NCB) reference signals (e.g., for use during beam failure recovery). The UE can be configured with NCB reference signals of type 1, type 2, etc. In the example, the type 1 NCB reference signal may indicate that the reference signal is based on the beam being transmitted; the type 2 NCB reference signal may indicate that the reference signal is based on an estimated beam.

[0256] The UE can receive or be configured with a first threshold, a second threshold, a third threshold, a first time window, contention-free PRACH resources, and contention-based PRACH resources.

[0257] In the event that all of one or more BFD reference signals have failed, the UE can identify and / or indicate a beam fault instance (BFI). The UE can determine the different types of BFD RS faults.

[0258] Type 1. In the case of Type 1 BFD RS, if one or more measurement parameters of the corresponding BFD RS (e.g., assuming PDCCH BLER) are below a first threshold, the UE determines that the RS is faulty.

[0259] Type 2. In the case of Type 2 BFD RS, the UE can receive one or more PDCCHs and / or PDSCHs transmitted within a first time window (e.g., received in and / or by one or more CORESETs associated with the RS). Thus, the UE can measure one or more parameters (e.g., hypothetical PDCCH BLER) based on the received PDCCHs and / or PDSCHs (e.g., based on DMRS). If one or more measured parameters of one or more PDCCHs and / or PDSCHs are below a second threshold, the UE can determine a BFD RS failure.

[0260] Type 3. In the case of Type 2 BFD RS, the UE can monitor to receive one or more PDCCHs and / or PDSCHs (e.g., received in and / or by one or more CORESETs associated with the RS). If the UE does not receive any PDCCHs and / or PDSCHs within a first time window, the UE can determine, calculate, and / or predict one or more parameters (e.g., a hypothetical PDCCH BLER). If one or more predicted parameters are below a second threshold, the UE can determine that the BFD RS is faulty.

[0261] The UE can activate a counter to count the number of beam fault instances within a first time window. If the number of beam fault instances within the first time window exceeds a third threshold, the UE can initiate a beam fault recovery process. The UE can monitor, detect, and / or measure one or more parameters (e.g., RSRP) for a determined and / or configured first type of NCB reference signal. Alternatively, the UE can calculate, estimate, and / or predict one or more parameters (e.g., RSRP) for a determined and / or configured second type of NCB reference signal. The UE can determine an optimal reference signal based on one or more measured and / or predicted parameters (e.g., RSRP) from one or more NCB reference signals.

[0262] The UE can determine to initiate an initial access procedure (e.g., transmit a PRACH preamble) in the PRACH time and / or frequency resources associated with one or more determined reference signals (e.g., optimal reference signals). The UE can perform PRACH transmission in the corresponding random access resources and according to the spatial relationship (e.g., QCL-ed) with respect to the determined optimal reference signals. If the determined one or more reference signals are of a first RS type, the UE can determine to use a first type of PRACH preamble and / or PRACH resources (e.g., a contention-free PRACH procedure). If the determined one or more reference signals are of a second RS type, the UE can determine to use a second type of PRACH preamble and / or PRACH resources (e.g., a contention-based PRACH procedure).

[0263] After the PRACH preamble is transmitted, the UE can monitor and attempt to detect RAR messages (e.g., DCI with CRC scrambling using RA-RNTI) within a random access response (RAR) window or a limited time period. In one example, if the UE determines to use a 4-step random access (RA) procedure, the UE can send a configured, selected, and / or determined PRACH preamble to the cell. After sending the PRACH preamble, the UE can monitor DL ​​messages (e.g., PDCCH) that can provide UL authorization (e.g., indicating a RAR message). Thus, the UE can send a UL message or indication (e.g., in a PUSCH) based on the UL authorization. In another example, if the UE determines to use a 2-step RA, the UE can send a message, such as MsgA, to the cell, which may include a configured, selected, and / or determined PRACH preamble and a PUSCH carrying the message. After sending MsgA, the UE can monitor DL ​​messages (e.g., PDCCH) (e.g., indicating MsgB), which may include (e.g., at least) RAR and may include contention resolution information.

[0264] As can be seen, the Wireless Transmit / Receive Unit (WTRU) can identify at least one beam fault, wherein after determining the number of beam faults, the beam fault is determined based on at least one of the measurements of a first type of beam and the measurements and estimates of a second type of beam: a specific candidate beam is determined among a plurality of candidate beams based on parameters, wherein the parameters are based on measurement parameters for the first type of candidate beam and the parameters are predicted for the second type of candidate beam; a message is transmitted using resources associated with the specific candidate beam; and a set of resources or signals based on the type of the specific candidate beam are used to monitor the response.

[0265] FIG. 6

[0266] refer to FIGS. 1A-1D In this embodiment, the UE determines the operating mode of the BFR based on prediction quality (e.g., RSRP difference or beam prediction accuracy) (e.g., BFR based on transmit beam only or based on joint BFR, which is based on both transmit beam and estimated beam).

[0267] In step S602, the UE receives configuration information indicating one or more Beam Failure Detection (BFD) RSs, one or more New Candidate Beam (NCB) RSs, a first threshold, a second threshold, a third threshold, a fourth threshold, a fifth threshold, a sixth threshold, PRACH resources, a first PRACH sequence, a second PRACH sequence, a first CORESET, and a second CORESET. Each RS can be a first RS type (e.g., transmit beam) or a second RS type (e.g., estimate beam).

[0268] In step S604, the UE determines the prediction quality based on one or more BFD RS and one or more NCB RS. The prediction quality can be determined as the difference between the predicted RSRP value and the measured RSRP value (e.g., based on DMRS from the PDCCH / PDSCH), or as beam prediction accuracy (e.g., the predicted optimal beam versus the actual optimal beam).

[0269] In step S606, the UE determines the BFR mode based on the predicted quality and a first threshold. In a first example, if the predicted quality is lower than the first threshold, the UE determines a first BFR mode (e.g., using only the first RS type for BFD and NCB (e.g., disabling one or more RSs with a second type)). In a second example, if the predicted quality is greater than the first threshold, the UE determines a second BFR mode (e.g., using both the first and second RS types for BFD and NCB (e.g., activating all RSs configured for BFD and NCB)).

[0270] In step S608, the UE determines a set of beam fault detection / recovery parameters based on the predicted quality. In the first example, the UE determines to use one of a second threshold and a third threshold for BFD RS fault detection of the second RS type based on the predicted quality. In the second example, the UE determines to use one of a fourth threshold and a fifth threshold for beam fault detection based on the predicted quality.

[0271] In step S610, if all of one or more active BFD RSs fail, the UE determines a beam fault instance. For the first RS type, if the measurement quality of the RS is below a sixth threshold, the UE can determine that the RS is beam faulted. For the second RS type, if the measurement quality of the RS is below either a second threshold or a third threshold (determined by the UE), the UE can determine that the RS is beam faulted.

[0272] In step S612, the UE detects beam faults based on the number of beam fault instances and a threshold determined by the UE. For example, if the number of beam fault instances within a time window is greater than either a fourth threshold or a fifth threshold (determined by the UE), the UE initiates beam fault recovery and determines the RS from the active NCB RS based on the measurement quality of the active NCB RS.

[0273] In step S614, the UE transmits PRACH in the PRACH resource based on the determined BFR mode. If the UE determines a first BFR mode, the UE transmits PRACH using a first PRACH sequence. If the UE determines a second BFR mode, the UE transmits PRACH using a second PRACH sequence.

[0274] In step S616, the UE monitors the PDCCH based on the determined BFR mode. If the UE determines a first BFR mode, the UE monitors the PDCCH in the first CORESET. If the UE determines a second BFR mode, the UE monitors the PDCCH in the second CORESET.

[0275] A UE equipped with AI / ML capabilities for beam management (e.g., beam selection, beam failure detection (BFD), monitoring new candidate beams (NCBs) RS, etc.) can support different operating modes for beam failure recovery (BFR). The BFR procedure for a UE can be associated with multiple steps, including BFD, monitoring the NCB, indicating the BFR and the selected NCB beam, receiving acknowledgment of the selected NCB from the gNB, and so on. For example, in a first operating mode, the UE can perform BFR based solely on the transmitted beam (the beam transmitted by the gNB). In a second operating mode, the UE can perform BFR based on both the transmitted beam and the estimated beam (the beam predicted by the AI / ML model).

[0276] The UE can be indicated or configured with an operating mode for BFR by the gNB via RRC signaling and / or MAC-CE indication and / or DCI indication. Alternatively, the UE can use one or more of the following methods to select the BFR operating mode and select the BFR-related procedures and parameters.

[0277] The UE can receive configuration information from the gNB (e.g., via RRC signaling and / or MAC-CE indication and / or DCI indication) regarding one or more BFD RS, one or more New Candidate Beam (NCB) RS, a first threshold, a second threshold, a third threshold, a fourth threshold, a sixth threshold, a seventh threshold, an eighth threshold, PRACH resources, a first PRACH sequence, a second PRACH sequence, a first CORESET, and a second CORESET. The BFD RS and NCB RS configured by the gNB can be of the first RS type (e.g., transmit beam or transmit RS) or the second RS type (e.g., estimate beam or estimate RS).

[0278] The UE can be configured in different ways for beam failure recovery:

[0279] The UE can be configured with beam fault detection (BFD) RS (e.g., One or more of the following: Each BFD RS can be a transmitting RS or an estimated RS. The configuration of BFD-RS can be based on the explicit configuration of the gNB. The configuration of BFD-RS can also be based on the implicit configuration. For example, if the UE does not receive an explicit configuration of BFD-RS, the UE can determine one or more BFD-RS based on one or more RSs with QCL type-D in the configuration TCI state used for PDCCH reception (e.g., in the configured CORESET / SearchSpaces).

[0280] The UE can be configured with one or more counters and one or more maximum numbers of one or more counters, such as BFD counter and BFD counter threshold, beam report counter and beam report counter threshold, and preamble power ramp counter and preamble power ramp counter threshold.

[0281] When a set of counters (e.g., one or more of BFD counters, beam reporting counters, and preamble power ramp counters) and thresholds is configured, this set of counters and thresholds can be used to estimate both the beam and the transmitted beam. If a set of counters (e.g., one or more of BFD counters, beam reporting counters, and preamble power ramp counters) and thresholds is configured, a first set of counters and thresholds can be used for the transmitted beam, while a second set of counters and thresholds can be used for beam estimation. The number of configured counters and the number of configured thresholds in each set can be the same.

[0282] The UE can be configured with one or more timers, such as the BFI timer, BFD timer, and BFR timer.

[0283] When a set of timers (e.g., one or more of BFI timers, BFD timers, and BFR timers) is configured, this set of timers can be used for both transmitting and estimating the beam. If a set of timers is configured, a first set of timers can be used for transmitting the beam, and a second set of timers can be used for estimating the beam.

[0284] The UE can be configured with a new candidate beam (NCB) RS (e.g., A set of one or more uplink resources. The configuration of BFD-RS can be based on the explicit configuration of the gNB. Each BFD RS can be a transmit RS or an estimate RS. Each NCB-RS can be associated with one or more uplink resources (e.g., PRACH (resources and / or sequences), PUCCH, PUSCH, and / or SRS).

[0285] The UE can be configured with one or more uplink resources (S) for new candidate beam indication, where S is one or more uplink resources for indicating new candidate beams. Each uplink resource can be associated with each NCB-RS. Each uplink resource can be associated with an NCB-RS type. For example, a first uplink resource can be associated with a transmit beam, and a second uplink resource can be associated with an estimated beam.

[0286] The UE can be configured with a CORESET and / or a search space (C) for receiving one or more acknowledgment random access responses from the BFR, wherein C i It is a set of search spaces used to receive the random access response of the BFR. Each CORESET / search space can be associated with an NCB-RS type. For example, the first CORESET / search space can be associated with the transmit beam, and the second CORESET / search space can be associated with the estimated beam.

[0287] The UE can determine the quality of the AI / ML-based beam estimation (prediction quality) by using one or more BFD RSs and / or one or more NCB RSs. To do this, the UE can determine the prediction quality. For example, the UE can determine the difference between the predicted RSRP value and the measured RSRP value of one or more RSs. For instance, the UE can estimate the RSRP of the predicted RS or beam by measuring the RSRP of an associated DMRS (e.g., a DMRS from a PDCCH or PDSCH that has the same beam as the predicted RS (e.g., QCL type-D)). In a second example, the UE can determine the quality of beam prediction by comparing the success (or failure) of the AI / ML model to rank the beams based on beam quality (e.g., the best k predicted beams versus the best k measured beams).

[0288] The UE can determine the operating mode of the BFR based on the prediction quality of the AI / ML model and a first threshold. For example, if the beam prediction quality is below the first threshold, the UE can determine a first operating mode for the BFR (e.g., using only one or more RSs with a first RS type (e.g., for BFD RS and / or as NCB RS)). To this end, if the beam prediction quality is below the first threshold, the UE can deactivate or invalidate one or more RSs with a second RS type (e.g., BFD RS and / or NCB RS). If the beam prediction quality is greater than or equal to the first threshold, the UE can determine a second operating mode for the BFR (e.g., using both the first and second RS types for BFD and / or as NCB). To this end, if the beam prediction quality is greater than the first threshold, the UE can activate or verify all RSs configured for BFD and / or as NCB.

[0289] The UE can determine one or more parameters associated with the BFR based on the quality of beam prediction.

[0290] The first parameter is a threshold for the beam quality of the BFD RS (e.g., assuming BLER) to determine a Beam Failure Instance (BFI). For example, the UE can determine a threshold for the beam quality of the BFD RS to determine the BFI based on the quality of the beam prediction. In an example configuration, if the beam prediction quality is lower than a threshold pre-configured via the gNB (e.g., pre-configured via RRC signaling and / or MAC-CE indication and / or DCI indication), the UE can determine to use a second threshold as a threshold for the quality used for BFI determination (e.g., assuming PDCCH BLER). If the beam prediction quality is greater than or equal to the threshold pre-configured by the gNB, the UE can determine to use a third threshold as a threshold for the quality used for BFI determination (e.g., assuming BLER).

[0291] The second parameter is a threshold associated with beam failure determination. For example, the UE can determine the number of detected BFIs (e.g., beamFailureInstanceMaxCount) required to declare a beam failure within a configured time window (e.g., beamFailureDetectionTimer) based on the quality of beam prediction. In the example configuration, if the quality of beam prediction is lower than a threshold pre-configured by the gNB (e.g., via RRC configuration and / or MAC-CE indication and / or DCI indication), the UE can select a fourth threshold as beamFailureInstanceMaxCount. If the quality of beam prediction is greater than or equal to the threshold pre-configured by the gNB, the UE can select a fifth threshold as beamFailureInstanceMaxCount.

[0292] The third parameter is the threshold quality of the NCB (e.g., threshold RSRP) to classify it as a potential new beam (e.g., rsrp-ThresholdSSB). For example, if the beam prediction quality is below a threshold pre-configured by the gNB (e.g., via RRC signaling and / or MAC-CE indication, and / or DCI indication), the UE can determine to use a sixth threshold as the rsrp-ThresholdSSB. If the beam prediction quality is greater than or equal to the threshold pre-configured by the gNB, the UE can determine to use a seventh threshold as the rsrp-ThresholdSSB. The UE can determine the rsrp-Threshold SSB for an NCB based on the beam prediction quality, either only for the second RS type NCB or for all NCBs, to classify it as a potential new beam.

[0293] The fourth parameter is the maximum value associated with one or more timers related to BFR. For example, if the beam prediction quality is below a threshold pre-configured by the gNB (e.g., via RRC configuration, and / or MAC-CE indication, and / or DCI indication), the UE can select a first maximum value for the timer. If the beam prediction quality is greater than or equal to the threshold pre-configured by the gNB, the UE can select a second maximum value for the timer. The gNB can configure the first and second maximum values ​​for the timers via RRC signaling and / or MAC-CE indication and / or DCI indication. The timer may include a BeamFailureRecoveryTimer, which is associated with the CFRA used for BFR. When the BeamFailureRecoveryTimer expires, the UE does not use the CFRA for BFR. The timer may also include a BeamFailureDetectionTimer, which is associated with a beam failure instance counter. When the BeamFailureDetectionTimer expires, the beam failure instance counter is reset.

[0294] The fifth parameter is the step size associated with the preamble transmission power ramp-up process (e.g., powerRampingStep), and the maximum power associated with the preamble transmission indicating the selected new beam (e.g., preamble transmission in the CFRA for BFR) (e.g., preambleTransMax). For example, if the beam prediction quality is below a threshold pre-configured by the gNB (e.g., via RRC configuration and / or MAC-CE indication and / or DCI indication), the UE can use the first step size for powerRampingStep. If the beam prediction quality is greater than or equal to the threshold pre-configured by the gNB, the UE can select a second step size for powerRampingStep. The first and second step sizes for powerRampingStep can be configured by the gNB via RRC configuration and / or MAC-CE indication and / or DCI indication.

[0295] The UE can identify beam fault instances when one or more active BFD RSs fail. To determine a BFD RS failure, the UE can compare the quality of each beam (e.g., RSRP, assumed BLER) with different defined thresholds based on the RS type. For example, if the measured quality of the RS (e.g., RSRP, assumed BLER) is below an eighth threshold, the UE can determine a beam fault for a first RS type BFD RS. If the estimated quality of the RS is below a second or third threshold, the UE can determine a beam fault for a second RS type BFD RS. The UE can determine a second or third threshold to be used to determine the beam fault for the second RS type BFD RS based on the quality of the beam prediction.

[0296] The UE can determine a beam fault based on the number of BFIs it detects and a threshold determined by the UE. If the number of BFIs within a time window is greater than or equal to one of a fourth and a fifth threshold determined by the UE, the UE can initiate a BFR procedure and determine a new beam (e.g., the NCB with the highest RSRP) from the active NCBRS based on the measured or predicted beam quality (e.g., RSRP) in the active NCBRS. The UE can select either a fourth or a sixth threshold for determining a beam fault based on the quality of the predicted beam.

[0297] The UE can transmit one or more UL channels and signals (e.g., PRACH, MACCE, PUCCH, PUSCH, and SRS) based on a determined BFR mode (e.g., PRACH in the PRACH resource during the CFRA procedure for beam fault indication and new beam indication). For example, if the UE determines a first BFR mode, the UE can utilize a first UL sequence and / or UL PRACH resources to transmit one or more UL channels and signals. If the UE determines a second BFR mode, the UE can utilize a second UL sequence and / or second UL resources to transmit one or more UL channels and signals.

[0298] The UE can monitor the PDCCH associated with a determined BFR (e.g., PDCCH confirming beam fault indication and / or confirming a new beam selected and indicated by the UE) based on the determined BFR mode. For example, if the UE determines a first BFR mode, the UE can monitor the PDCCH in a first CORESET / search space. If the UE determines a second BFR mode, the UE can monitor the PDCCH in a second CORESET / search space.

[0299] As can be seen, the Wireless Transmit / Receive Unit (WTRU) can determine the predicted quality associated with at least one reference signal, determine a beam fault recovery mode based on the predicted quality, determine a set of beam fault recovery parameters based on the predicted quality, determine at least one beam fault, and after determining the number of beam faults, determine a reference signal for determining a candidate beam among at least one reference signal used for candidate beams based on measurements of the reference signal, wherein the parameters are measurement parameters based on a first type of reference signal and the parameters are predicted for a second type of reference signal, transmit a message based on the beam fault recovery mode, and monitor the response using a set of resources or signals based on the determined type of reference signal.

[0300] in conclusion

[0301] While features and elements have been provided for the foregoing in specific combinations, those skilled in the art will understand that each feature or element may be used alone or in any combination with other features and elements. This disclosure should not be limited to the specific embodiments described in this application, which are intended to illustrate various aspects. Many modifications and variations can be made without departing from the spirit and scope of the invention, as will be apparent to those skilled in the art. Unless expressly provided so, elements, actions, or instructions used in the description of this application should not be construed as critical or essential to the invention. Functionally equivalent methods and apparatus within the scope of this disclosure, in addition to those listed herein, will be apparent to those skilled in the art based on the foregoing description. These modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only by the terminology of the appended claims and the full scope of the equivalents granted by those claims. It should be understood that this disclosure is not limited to specific methods or systems.

[0302] For simplicity, the foregoing embodiments are discussed in terms of the terminology and structure of infrared-capable devices (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as sound waves.

[0303] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "image" can mean any one of a snapshot, a single image, and / or multiple images displayed on a time basis. As another example, when referenced herein, the term "user equipment" and its abbreviation "UE," the term "remote," and / or the term "head-mounted display" or its abbreviation "HMD" can mean or include: (i) a wireless transmitting and / or receiving unit (WTRU); (ii) any of several embodiments of a WTRU; (iii) a device with wireless and / or wired capabilities (e.g., tetherable), particularly configured with some or all of the structure and functions of a WTRU; (iv) a device with wireless and / or wired capabilities, configured with fewer than all the structure and functions of a WTRU; or (iv) the like. References herein ​ Details of an example WTRU are provided, which may represent any WTRU described herein. As another example, the various embodiments disclosed above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than head-mounted displays can be utilized, and some or all of the embodiments disclosed herein and in the various disclosures can be modified accordingly without excessive experimentation. Examples of such other devices may include drones or other devices configured to stream information for providing an adapted, realistic experience.

[0304] Furthermore, the methods provided herein can be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROMs and digital multifunction discs (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0305] Variations of the methods, apparatus, and systems provided above are possible without departing from the scope of the invention. Given the wide variety of applicable embodiments, it should be understood that the illustrated embodiments are merely examples and should not be considered as limiting the scope of the appended claims. For example, embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery) supplied with any suitable voltage.

[0306] Furthermore, in the embodiments provided above, note the processing platform, computing system, controller, and other devices including the processor. These devices may include at least one central processing unit (“CPU”) and memory. According to the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions can be executed by various CPUs and memories. Such actions and operations or instructions may be referred to as “execution,” “computer execution,” or “CPU execution.”

[0307] Those skilled in the art will understand that the actions and symbols representing operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause transformations or reductions of electrical signals and the maintenance of data bits at memory locations in a memory system, thereby reconfiguring or otherwise altering the operation of the CPU and other signal processing. The memory location maintaining the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided methods.

[0308] Data bits can also be maintained on computer-readable media, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage systems. Computer-readable media can include cooperative or interconnected computer-readable media that reside exclusively on the processing system or are distributed among multiple interconnected processing systems that may be located locally or remotely on the processing system. It should be understood that the embodiments are not limited to the aforementioned memories, and other platforms and memories may support the provided methods.

[0309] In the illustrative embodiments, any operations, processes, etc., described herein may be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions may be executed by a processor of a mobile unit, network element, and / or any other computing device.

[0310] There is little difference between the hardware and software implementations of various aspects of the system. The use of hardware or software is often (but not always, as the choice between hardware and software may become important in some cases) a design choice representing a trade-off between cost and efficiency. Various vehicles can exist through which the processes and / or systems and / or other technologies (e.g., hardware, software, and / or firmware) described herein can be implemented, and the preferred vehicle can vary depending on the context of the deployment of the processes and / or systems and / or other technologies. For example, if the implementer determines that speed and accuracy are paramount, the implementer may choose a primarily hardware and / or firmware-based tool. If flexibility is paramount, the implementer may choose a primarily software-based implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0311] The foregoing detailed description has illustrated various embodiments of the apparatus and / or processes using block diagrams, flowcharts, and / or examples. Where such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by a wide variety of hardware, software, firmware, or virtually any combination thereof. In embodiments, several portions of the subject matter described herein can be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be implemented, in whole or in part, equivalently in an integrated circuit as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware, or virtually any combination thereof, and those skilled in the art will design circuits and / or write code for software and / or firmware entirely within their skill set based on this disclosure. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as various forms of program products, and that the illustrative embodiments of the subject matter described herein are applicable regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media, such as floppy disks, hard disks, CDs, DVDs, digital magnetic tapes, computer memory, etc., and transmission media, such as digital and / or analog communication media (e.g., optical fibers, waveguides, wired communication links, wireless communication links, etc.).

[0312] Those skilled in the art will recognize that it is common practice in the art to describe devices and / or processes in the manner set forth herein, and subsequently to integrate such described devices and / or processes into data processing systems using engineering practice. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system through a reasonable number of experiments. Those skilled in the art will recognize that a typical data processing system may generally include one or more of the following: a system unit housing, a video display device, memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, a computing entity such as an operating system, drivers, a graphical user interface and applications, one or more interactive devices such as a touchpad or touchscreen, and / or a control system including feedback loops and control motors (e.g., feedback for sensing position and / or speed, control motors for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0313] The topics described herein sometimes illustrate different components included within or connected to different other components. It should be understood that the architectures described in this way are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components that achieve the same functionality is effectively “associated” to enable the desired functionality. Therefore, any two components combined in this document to achieve a particular function can be considered “associated” with each other to enable the desired functionality, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operably connected” or “operably linked” to each other to achieve the desired functionality, and any two components that can be so associated can also be considered “operably linked” to each other to achieve the desired functionality. Specific examples of operably linked components include, but are not limited to, physically pairable and / or physically interactive components and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.

[0314] Regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can convert plural to singular and / or singular to plural as needed by the context and / or application. For clarity, various singular / plural substitutions may be explicitly described herein.

[0315] Those skilled in the art will understand that, in general, the terms used herein and especially in the appended claims (e.g., the body of the appended claims) are intended to be “open-ended” terms (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will also understand that if the intent is to have a specific number of introduced claims, such intent will be explicitly stated in the claims, and without such a statement, such intent does not exist. For example, the term “single” or similar language may be used to indicate only one item. To aid understanding, the appended claims and / or the description herein may include the use of the introductory phrases “at least one” and “one or more” to introduce the claims. However, the use of such phrases should not be construed as implying that a claim introduced by the indefinite article "a" limits any particular claim to include only one such embodiment, even when the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" (e.g., "a" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles to introduce a claim. Furthermore, even if a specific number of introduced claim statements are explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the number stated (e.g., in the absence of other modifiers, simply stating "two statements" means at least two statements, or two or more statements). Moreover, in instances where conventions such as "at least one of A, B, and C" are used, such construction is generally intended to be understood by those skilled in the art in the sense of the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, systems having only A, only B, only C, A and B, A and C, B and C, and / or systems having A, B, and C, etc.). In instances where conventions such as "at least one of A, B, or C" are used, such a construction is generally intended to be understood by those skilled in the art in the sense of the convention (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, systems having only A, only B, only C, A and B, A and C, B and C, and / or systems having A, B, and C, etc.). Those skilled in the art will also understand that any transitional conjunctions and / or phrases that actually present two or more alternative terms, whether in the specification, claims, or drawings, should be understood to imply the possibility of including one, any one, or both of these terms (e.g., the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B").Furthermore, as used herein, the term "any" followed by a list of multiple items and / or multiple item categories is intended to include "any," "any combination," "any number," and / or "a combination of any number" of items and / or item categories, individually or in combination with other items and / or other item categories. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Furthermore, as used herein, the term "quantity" is intended to include any quantity, including zero. And the term "many" as used herein is intended to be synonymous with "multiple."

[0316] Furthermore, where features or aspects of this disclosure are described in accordance with the Markush Group, those skilled in the art will recognize that this disclosure is also described in accordance with any individual member or subgroup of the Markush Group.

[0317] As those skilled in the art will understand, for any and all purposes, such as providing a written description, all scopes disclosed herein also encompass any and all possible subscopes and combinations thereof. Any listed scope can be readily considered sufficiently descriptive and such that the same scope can be decomposed into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily decomposed into a lower third, a middle third, and an upper third, etc. Those skilled in the art will also understand that all language such as “at most,” “at least,” “greater than,” “less than,” etc., includes the listed numbers and refers to a scope that can subsequently be decomposed into subscopes as described above. Finally, as those skilled in the art will understand, a scope includes each individual member. Thus, for example, a group having 1 to 3 units means a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units means a group having 1, 2, 3, 4, or 5 units, and so on.

[0318] Furthermore, unless otherwise stated, the claims should not be construed as being limited to the order or elements provided. Additionally, the use of the term "for means of..." in any claim is intended to invoke 35 U.S.SC §112. 6. The means plus function claim format, and any claim without the term "means for..." is not intended to be so.

Claims

1. A method at a wireless transmit / receive unit (WTRU), the method comprising: Determine a beam fault for at least one beam, wherein the beam fault is determined based on measurements of a first type of beam and estimates of a second type of beam, respectively; and After determining the number of beam faults: A specific candidate beam is determined from a plurality of candidate beams based on parameters, wherein the parameters are based on measurement parameters for a first type of candidate beam, and wherein the parameters are predicted for a second type of candidate beam.

2. The method of claim 1, further comprising, after determining the number of beam faults: Send a message, in which, The message is sent on a first resource if the determined candidate beam is of the first type, and on a second resource if the determined candidate beam is of the second type. as well as Use a set of resources or signals based on a defined type of candidate beam to monitor the response.

3. The method of claim 1, wherein the first type of beam is measurable by the WTRU, the method further comprising measuring the at least one beam to obtain the measurement value.

4. The method of claim 3, wherein, When the measured value is determined to be lower than a first given value, a beam fault of the first type of beam is determined.

5. The method according to claim 3, wherein, Measuring the at least one beam includes measuring a reference signal.

6. The method according to claim 5, wherein, The reference signal is a beam fault detection reference signal.

7. The method according to claim 1, wherein, The characteristics of the second type of beam are estimated by the WTRU, and the method further includes estimating at least one characteristic of the at least one beam to obtain the estimated value.

8. The method according to claim 7, wherein, When the estimated value is determined to be lower than the second given value, a beam fault of the second type of beam is determined.

9. The method of claim 7, wherein the second type of beam is not measured by the WTRU.

10. The method according to claim 1, wherein, The number of beam faults is equal to the number of measurement reference signals for the first type of beam, and wherein the number of beam faults is equal to the number of estimated reference signals for the second type of beam.

11. The method according to claim 1, wherein, The candidate beams are determined under the condition that a certain number of beam failures occur within a given time period.

12. The method according to claim 1, wherein, The number of beam faults is the sum of the number of beam faults for the first type of beam and the number of beam faults for the second type of beam.

13. The method according to claim 1, wherein, The number of beam faults is reached when at least one of the following conditions is met: the number of beam faults for the first type of beam reaches a first value and the number of beam faults for the second type of beam reaches a second value.

14. A wireless transmit / receive unit (WTRU), the WTRU comprising at least one processor, the at least one processor being configured to: Identify a beam fault in at least one beam, wherein, Beam faults are determined based on measurements of the first type of beam and estimates of the second type of beam, respectively. as well as After determining the number of beam faults: A specific candidate beam is determined from a plurality of candidate beams based on parameters, wherein the parameters are based on measurement parameters for a first type of candidate beam, and wherein the parameters are predicted for a second type of candidate beam.

15. The WTRU of claim 14, wherein the at least one processor is further configured to: after determining the number of beam faults: Send a message, in which, The message is sent on a first resource if the determined candidate beam is of the first type, and on a second resource if the determined candidate beam is of the second type. as well as Use a set of resources or signals based on a defined type of candidate beam to monitor the response.

16. The WTRU of claim 14, wherein, The first type of beam can be measured by the WTRU, and wherein the at least one processor is further configured to measure the at least one beam to obtain the measurement value.

17. The WTRU of claim 16, wherein, The at least one processor is configured to determine a beam fault of the first type of beam when it is determined that the measured value is lower than a first given value.

18. The WTRU according to claim 16, wherein, Measuring the at least one beam includes measuring a reference signal.

19. The WTRU according to claim 18, wherein, The reference signal is a beam fault detection reference signal.

20. The WTRU of claim 14, wherein, The characteristics of the second type of beam are estimated by the WTRU, wherein the at least one processor is further configured to estimate at least one characteristic of the at least one beam to obtain the estimated value.

21. The WTRU according to claim 20, wherein, The at least one processor is configured to determine a beam fault of the second type of beam when it is determined that the estimated value is lower than a second given value.

22. The WTRU of claim 20, wherein, The second type of beam is not measured by the WTRU.

23. The WTRU according to claim 14, wherein, The number of beam faults is equal to the number of measurement reference signals for the first type of beam, and the number of beam faults is equal to the number of estimated reference signals for the second type of beam.

24. The WTRU of claim 14, wherein the candidate beams are determined under the condition that a determined number of beam failures occur within a given time period.

25. The WTRU according to claim 14, wherein, The number of beam faults is the sum of the number of beam faults for the first type of beam and the number of beam faults for the second type of beam.

26. The WTRU of claim 14, wherein the number of beam faults is reached when at least one of the number of beam faults for the first type of beam reaches a first value and the number of beam faults for the second type of beam reaches a second value.

Images