Efficient measurement of power at higher frequencies

Abstract

Power efficient measurements may be implemented for radio frequency operation. The WTRU may determine measurement occasions, DRX cycle / configuration transitions, DRX pause / resume, DRX timer operation, and / or BFR based on scheduling activity, beam configuration, BFI detection, BFD, beam loss, etc. The WTRU may be configured with multiple DRX cycles and measurement occasions (e.g., with different periodicities). The WTRU may perform (e.g., RS) measurement(s) at determined / configured timing (e.g., DRX on period) in a first DRX cycle based on condition(s). The WTRU may switch to a second DRX cycle and perform RS measurement(s) at determined / configured timing based on condition(s) (e.g., the count number of BFIs detected in the first DRX cycle). The WTRU may switch from the second (e.g., short) DRX cycle to the first (e.g., long) DRX cycle or to non-DRX operation (e.g., DRX suspended or DRX inactivity timer reset) based on condition(s) (e.g., the number of BFIs in the first and / or second DRX cycle(s)).

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 62 / 975,416, filed on February 12, 2020, the disclosure of which is incorporated herein by reference in its entirety.

Background Art

[0002] Mobile communication using wireless communication has been continuously evolving. The fifth generation may be referred to as 5G. Previous (conventional) generations of mobile communication may be, for example, the fourth generation (4G) long - term evolution (LTE).

Summary of the Invention

[0003] Efficient measurement of power can be implemented for high-frequency operation. A wireless transmit / receive unit (WTRU) may determine a measurement occasion according to scheduling activity and beam configuration. The WTRU may determine a measurement occasion for beam failure detection (BFD), radio link monitoring (RLM), and / or mobility according to discontinuous reception (DRX) and / or BFD configuration. The WTRU may determine that a first set of reference signal (RS) measurement opportunities is applicable based on a first condition (e.g., when / if the DRX / BFD / channel state information (CSI) condition is satisfied), and a second set of RS measurement opportunities is applicable based on a second condition (e.g., when / if the DRX / BFD / CSI condition is not satisfied). The WTRU may be configured using multiple sets of CSI-RS measurement opportunities (e.g., using different periodicities). The WTRU may, for example, assume that a given set is applicable when the DRX / BFD / CSI condition is satisfied. The WTRU may determine DRX operation or non-DRX operation, for example, based on whether a BFI counter is less than a threshold or greater than or equal to the threshold. The WTRU may reset an inactivity timer, for example, based on one or more BFD states (e.g., beam failure instance (BFI) counter > threshold and no BFD resources before inactivity timer expiration). The WTRU may pause, disable, or (re)start a BFD timer, for example, when inactive time occurs. The WTRU may change a beam state, (de)activate related CSI-RS, and / or pause / resume related BFD according to, for example, DRX state / configuration or related signaling.The WTRU may transition to different DRX cycles / configurations, suspend / resume DRX functionality, and / or (re)start / stop one or more DRX timers in response to, for example, beam obstruction, loss of beam(s), or detection of a related measurement. The WTRU may trigger a BFR / beam re-establishment procedure (e.g., a new BFR / beam re-establishment procedure), for example, if the WTRU does not have a satisfactory beam during a DRX beam observation period.

[0004] In an embodiment, a method for efficient measurement of power for high frequency operation may be implemented. The method may be implemented (e.g., wholly or partially) by a device(s) (e.g., a WTRU, a network node such as a gNodeB (gNB), and / or the like), and / or a system(s) configured to implement the method, which may include one or more processors configured to execute the method (e.g., wholly or partially) as computer-executable instructions that may be stored on a computer-readable medium or a computer program product. The computer-readable medium or computer program product may include instructions that cause one or more processors to execute the method by executing the instructions.

[0005] A WTRU may perform recovery associated with beam failure detection (BFD) and DRX. In an embodiment, the WTRU performs a first CSI-RS measurement during an on-period associated with a first DRX cycle, determines a first number of beam failure events based on the first CSI-RS measurement, switches to a second DRX cycle based on the determined first number of beam failure events, performs a second CSI-RS measurement during an on-period associated with the second DRX cycle, determines a second number of beam failure events based on the second CSI-RS measurement, and switches to non-DRX operation if the second number of beam failure events is greater than a first threshold. For example, see FIG. 3 herein. The non-DRX operation may include at least one of an interruption of DRX or a reset of an inactivity timer. A beam failure event may be associated with a channel condition state determination. The timing associated with at least one of the first CSI-RS measurement or the second CSI-RS measurement may be indicated to the WTRU by a network device. The first DRX cycle may be a long DRX cycle and the second DRX cycle may be a short DRX cycle.

[0006] The WTRU may be (e.g., further) configured to switch from the second DRX cycle to the first DRX cycle if, for example, the second number of beam failure events is less than a second threshold.

[0007] The WTRU may be (e.g., further) configured to receive configuration information indicating the first DRX cycle and the second DRX cycle.

[0008] The WTRU may be (e.g., further) configured to determine the timing associated with at least one of the first CSI-RS measurement or the second CSI-RS measurement.

[0009] At least one of the first number of beam obstruction cases or the second number of beam obstruction cases can be determined via the use of a beam obstruction case counter.

Brief Description of the Drawings

[0010]

Figure 1A

Figure 1B

Figure 1C

Figure 1D

Figure 2

Figure 3

Modes for Carrying Out the Invention

[0011] Efficient measurement of power can be implemented for high-frequency operation. A wireless transmit / receive unit (WTRU) may determine measurement occasions according to scheduling activities and beam configurations. The WTRU may determine measurement occasions for beam failure detection (BFD), radio link monitoring (RLM), and / or mobility according to discontinuous reception (DRX) and / or BFD configurations. The WTRU may determine that a first set of reference signal (RS) measurement opportunities is adaptable based on a first condition (e.g., when / if DRX / BFD / channel state information (CSI) conditions are met), and that a second set of RS measurement opportunities is applicable based on a second condition (e.g., when / if DRX / BFD / CSI conditions are not met). The WTRU may be configured using multiple sets of CSI-RS measurement opportunities (e.g., using different periodicities). The WTRU may, for example, assume that a given set is applicable when the DRX / BFD / CSI conditions are met. The WTRU may determine DRX operation or non-DRX operation based on, for example, whether a BFI counter is less than a threshold or greater than or equal to the threshold. The WTRU may reset an inactivity timer based on, for example, one or more BFD states (e.g., beam failure instance (BFI) counter > threshold and no BFD resources before inactivity timer expiration). The WTRU may pause, disable, or (re)start a BFD timer, for example, when in an inactive time. The WTRU may change a beam state, (de)activate related CSI-RS, and / or pause / resume related BFD according to, for example, DRX state / configuration or related signaling. The WTRU may transition to different DRX cycles / configurations, pause / resume DRX functionality, and / or (re)start / stop one or more DRX timers according to, for example, detection of beam failure, loss of beam(s), or related measurement values. The WTRU may trigger a BFR / beam re-establishment procedure (e.g., a new BFR / beam re-establishment procedure), for example, if the WTRU does not have a satisfactory beam during a DRX beam observation period.

[0012] FIG. 1A is a diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 can be a plurality of access systems that provide content such as voice, data, video, messaging, broadcast, etc. to a plurality of wireless users. The communication system 100 can enable a plurality of wireless users to access such content through sharing of 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 unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC).

[0013] As shown in Figure 1A, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, but it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to interchangeably as a "station" and / or "STA", can be configured to transmit and / or receive wireless signals and can be user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscriber-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., a robot and / or other wireless device operating in an industrial and / or automated processing chain context), a home appliance device, a device operating in a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

[0014] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as CN106 / 115, Internet 110, and / or other network 112. By way of example, base stations 114a, 114b may be a base transceiver station (BTS), Node B, eNodeB, home Node B, home eNodeB, gNB, NR NodeB, site controller, access point (AP), wireless router, and the like. Although base stations 114a, 114b are each shown as a single element, it will be understood that base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0015] Base station 114a can be part of RAN 104 / 113 and can also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. Base station 114a and / or base station 114b can be configured to transmit and / or receive radio signals at one or more carrier frequencies, which can be referred to as a cell (not shown). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectra. A cell can provide wireless service coverage to a specific geographic area that can be relatively fixed or can change over time. A cell can further be divided into cell sectors. For example, the cell associated with base station 114a can be divided into three sectors. Thus, in one embodiment, base station 114a can include three transceivers, i.e., one for each sector of the cell. In one embodiment, base station 114a can use multiple-input multiple-output (MIMO) technology and can utilize multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

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

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

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

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

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

[0021] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), GSM Evolution (Enhanced Data rates for GSM Evolution (EDGE)), GSM EDGE (GERAN), etc.

[0022] The base station 114b in Fig. 1A may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connection in a local area such as an office, a home, a vehicle, a campus, an industrial facility, an aerial corridor (for use by, e.g., a drone), a road, or other locations. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a pico cell or a femto cell. As shown in Fig. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115 in some cases.

[0023] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, 102d. The data can have various quality of service (QoS) requirements such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that employ the same or a different radio access technology (RAT) as RAN 104 / 113. For example, in addition to being connected to a RAN 104 / 113 that can utilize New Radio (NR) radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0024] CN106 / 115 may also serve as a gateway for WTRU102a, 102b, 102c, 102d to access the PSTN108, the Internet 110, and / or other networks 112. The PSTN 108 may include a public switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the transmission control protocol (TCP), the user datagram protocol (UDP), and / or the Internet protocol (IP) of the TCP / IP Internet protocol suite. The network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs that may employ the same RAT or a different RAT as the RAN 104 / 113.

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

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

[0027] The processor 118 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B shows the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0029] The transmit / receive element 122 is shown in FIG. 1B as a single element, but the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may utilize MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interface 116.

[0030] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs such as, for example, NR and IEEE 802.11.

[0031] The processor 118 of the WTRU 102 may be coupled to the speaker / microphone 124, keypad 126, and / or display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 can include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 can include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 can access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

[0033] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or instead of information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via the air interface 116 and / or may determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may obtain location information by any suitable positioning method while remaining consistent with one embodiment.

[0034] The processor 118 may further be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality / Augmented Reality (VR / AR) device, an activity tracker, etc. The peripheral devices 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0035] WTRU102 may include a full-duplex radio in which some or all of the transmission and reception of signals (e.g., for both UL (e.g., for transmission) and downlink (e.g., for reception), associated with a particular subframe) can be parallel and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., choke) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, WRTU102 may include a half-duplex radio for the transmission and reception of any of some or all of the signals (e.g., associated with a particular subframe for either UL (e.g., for transmission) or downlink (e.g., for reception)).

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

[0037] RAN104 may include eNode-Bs 160a, 160b, 160c, but it will be understood that RAN104 may include any number of eNode-Bs while remaining consistent with one embodiment. Each of eNode-Bs 160a, 160b, 160c may include one or more transceivers for communicating with WTRU102a, 102b, 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, eNode-B160a can transmit a radio signal to WTRU102a and / or receive a radio signal from WTRU102a, for example, using multiple antennas.

[0038] Each of eNode-Bs 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, etc. in the UL and / or DL. As shown in Figure 1C, eNode-Bs 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0039] CN 106 shown in Figure 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the foregoing elements is shown 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.

[0040] MME 162 can be connected to each of eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can function as a control node. For example, MME 162 can authenticate WTRUs 102a, 102b, 102c, bearer active / inactive users, and can play a role in selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, 102c. MME 162 can provide control plane functions for switching between RAN 104 and other RANs (not shown) that employ other radio technologies such as GSM and / or WCDMA.

[0041] SGW 164 can be connected to each of eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. SGW 164 can generally route and transfer user data packets to / from WTRUs 102a, 102b, and 102c. SGW 164 can perform other functions such as the function of anchoring the user plane during handover between eNode Bs, the function of triggering paging when DL data is available to WTRUs 102a, 102b, and 102c, and the function of managing and storing the contexts of WTRUs 102a, 102b, and 102c.

[0042] SGW 164 can be connected to PGW 166, and PGW 166 can provide WTRUs 102a, 102b, and 102c with access to a packet switched network such as the Internet 110 in order to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0043] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to a circuit switched network such as PSTN 108 in order to facilitate communication between WTRUs 102a, 102b, and 102c and conventional landline communication devices. For example, CN 106 can include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that functions as an interface between CN 106 and PSTN 108. Further, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112 that can include other wired and / or wireless networks owned and / or operated by other service providers.

[0044] The WTRU is described as a wireless terminal in FIGS. 1A - 1D, but in certain representative embodiments, it is contemplated that such a terminal can use a wired communication interface (e.g., temporarily or permanently) with a communication network.

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

[0046] A WLAN in infrastructure basic service set (BSS) mode can have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP can have access or an interface to another type of wired / wireless network that carries traffic entering and / or exiting the distribution system (DS) or the BSS. Traffic from outside the BSS to an STA can reach and be delivered to the STA through the AP. Traffic originating from an STA to a destination outside the BSS can be sent to the AP and then sent to their respective destinations. Traffic between STAs within the BSS can be transmitted, for example, via the AP. The source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be regarded as and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be transmitted in a direct link setup (DLS) directly between the source STA and the destination STA (e.g., directly between them). In certain representative embodiments, the DLS can use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (e.g., all of the STAs) can communicate directly with each other. The IBSS mode of communication can be referred to herein as the "ad hoc" communication mode in some cases.

[0047] When using an 802.11ac infrastructure operation mode or a similar operation mode, the AP may transmit beacons on a fixed channel such as a primary channel. The primary channel can be of a fixed width (e.g., a 20 MHz bandwidth) or a width 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, for example, in an 802.11 system, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) with collision avoidance can be implemented. In the case of CSMA / CA, STAs including the AP (e.g., all STAs) can sense the primary channel. If the primary channel is sensed / detected as busy by a particular STA and / or determined to be so, the particular STA can back off. Only one STA (e.g., only one station) can transmit at any given time in a given BSS.

[0048] A High Throughput (HT) STA can form a 40 MHz wide channel for communication, for example, via a combination of an adjacent or non - adjacent 20 MHz channel with the primary 20 MHz channel.

[0049] A Very High Throughput (VHT) STA may support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. A 40 MHz and / or 80 MHz channel may be formed by combining consecutive 20 MHz channels. A 160 MHz channel may be formed by combining eight consecutive 20 MHz channels or by combining two non - consecutive 80 MHz channels, which may be referred to as an 80 + 80 configuration. In the case of an 80 + 80 configuration, after channel encoding, the data may pass through a segment parser that may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time - domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80 + 80 configuration may be reversed, and the combined data may be transmitted to the Medium Access Control (MAC).

[0050] The sub-1 GHz operating mode is supported by 802.11af and 802.11ah. The channel operating bandwidth and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using the non-TVWS spectrum. According to an exemplary embodiment, 802.11ah may support meter type control / machine type communication, such as MTC devices within a macro coverage area. The MTC device may have limited capabilities, including support (e.g., only support therefor) for a particular and / or limited bandwidth. The MTC device may include a battery having a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0051] A WLAN system that supports multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah includes channels that can be designated as primary channels. The primary channel may 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 restricted by the STA among all STAs operating in a BSS that supports the minimum bandwidth operation mode. In the example of 802.11ah, the primary channel is 1 MHz wide for an STA (e.g., an MTC type device) that supports the 1 MHz mode (e.g., supports only that) even when the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operation modes. Carrier sensing and / or Network Allocation Vector (NAV) setting may depend on the state of the primary channel. For example, if the primary channel is busy due to an STA transmitting to the AP (supporting only the 1 MHz operation mode), the entire available frequency band may be considered busy even if most of the frequency band remains idle and available.

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

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

[0054] RAN 113 may include gNBs 180a, 180b, and 180c, although it will be understood that RAN 113 may include any number of gNBs while remaining consistent with one embodiment. Each of gNBs 180a, 180b, and 180c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 108b may be able to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c using beamforming. Thus, gNB 180a, for example, may be able to transmit a wireless signal to WTRU 102a and / or receive a wireless signal from WTRU 102a using multiple antennas. In one embodiment, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a may be able to transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, and the remaining component carriers may be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may be able to receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0055] WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using transmissions associated with an extensible numerology. For example, the OFDM symbol interval and / or the OFDM subcarrier interval can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including various numbers of OFDM symbols and / or having absolute times of various lengths).

[0056] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in a stand-alone configuration and / or a non-stand-alone configuration. In a stand-alone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c, etc.). In a stand-alone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as a mobility anchor point. In a stand-alone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in an unlicensed band. In a non-stand-alone configuration, WTRUs 102a, 102b, and 102c can communicate with and connect to gNBs 180a, 180b, and 180c while also communicating with and connecting to another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement a DC principle for communicating with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c substantially simultaneously. In a non-stand-alone configuration, eNode-Bs 160a, 160b, and 160c can function as a mobility anchor 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.

[0057] 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, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPFs) 184a, 184b, routing of control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, gNBs 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0058] CN 115 shown in FIG. 1D can include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and optionally data networks (DNs) 185a, 185b. Although each of the foregoing elements is shown as part of CN 115, it will be understood that any of these elements can be owned and / or operated by entities other than the CN operator.

[0059] AMF 182a and 182b can be connected to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can function as control nodes. For example, AMF 182a and 182b can play roles such as authentication of users of WTRUs 102a, 102b, and 102c, support for network slicing (e.g., handling different PDU sessions with different requirements), selection of specific SMFs 183a and 183b, management of the registration area, termination of NAS signaling, and mobility management. Network slicing can be used by AMF 182a and 182b to customize the CN support for WTRUs 102a, 102b, and 102c based on the type of service being utilized by WTRUs 102a, 102b, and 102c. For example, different network slices can be established for different use cases such as services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. AMF 162 can provide control plane functions for switching between RAN 113 and other RANs (not shown) that employ other radio technologies such as non-3GPP access technologies like LTE, LTE-A, LTE-A Pro, and / or WiFi.

[0060] SMF183a and 183b can be connected to AMF182a and 182b in CN115 via the N11 interface. SMF183a and 183b can also be connected to UPF184a and 184b in CN115 via the N4 interface. SMF183a and 183b can select and control UPF184a and 184b and configure the routing of traffic passing through UPF184a and 184b. SMF183a and 183b can perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. The PDU session type can be IP-based, non-IP-based, Ethernet-based, etc.

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

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

[0063] Looking at FIGS. 1A - 1D and the corresponding descriptions of FIGS. 1A - 1D, one or more of the functions described herein related to one or more of WTRU102a - d, base stations 114a - b, eNode - B160a - c, MME162, SGW164, PGW166, gNB180a - c, AMF182a - b, UPF184a - b, SMF183a - b, DN185a - b, and / or any other device described herein may be implemented by one or more emulation 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, emulation devices may be used to test other devices and / or simulate network and / or WTRU functionality.

[0064] An emulation device can be designed to implement one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, one or more emulation devices can be 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, and can execute one or more or all functions while being deployed. One or more emulation devices can execute one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. An emulation device can be directly coupled to another device for testing purposes and / or can execute tests using terrestrial wireless communication.

[0065] One or more emulation devices can execute one or more functions including all while not being implemented / deployed as part of a wired and / or wireless communication network. For example, an emulation device can be utilized in a test scenario in a test laboratory and / or in a wired and / or wireless communication network that is not deployed (e.g., for testing) to implement tests of one or more components. One or more emulation devices can be test equipment. Direct RF coupling and / or wireless communication via an RF circuit (which can include one or more antennas) can be used by an emulation device to transmit and / or receive data.

[0066] For example, a wireless technology that uses New Radio (NR) as an example in this specification can support higher frequencies and beamforming (e.g., frequencies from 52.6 GHz to 71 GHz). NR can be used for high data rate eMBB, mobile data offloading, short-range high data rate D2D communication, and industrial IoT. The power consumption of the WTRU can be improved. For example, the wireless of the WTRU can be turned off to save energy without degrading the beam management, mobility, and connectivity management of the WTRU.

[0067] Beam failure detection (BFD) and beam failure recovery (BFR) may be provided. The WTRU may be configured to maintain one or more beam pairs (e.g., in a beamformed NR system). The WTRU may monitor one or more periodic channel state information reference signals (CSI-RS) on the serving downlink (DL) beam, for example, to evaluate beam quality and calculate corresponding quality metrics. The physical layer (PHY) entity of the WTRU may report a beam failure instance (BFI) to the MAC sublayer, for example, if the beam quality for a given RS period for one or more (e.g., some and / or all) of the beams in the maintenance set falls below a configured threshold.

[0068] Lost beam pair(s) may be established faster than the radio link monitoring (RLM) / radio link failure (RLF) procedure. The WTRU may maintain a beam failure detection (BFD) procedure where the maintained beams are periodically measured. A beam failure recovery (BFR) request may be reported to the network, for example, when a beam failure is detected. BFR may be configured for beam maintenance for the primary cell (Pcell) and / or secondary cell (Scell). BFD measurements may be made, for example, at the maximum of the {DRX period, CSI-RS period} (e.g., in a legacy system) if BFD and discontinuous reception (DRX) are configured.

[0069] The MAC entity may maintain a beam failure instance (BFI) counter (BFI_counter) for beam failure detection (BFD). The MAC entity may count the number of BFI indications received from the PHY entity. A BFR request may be triggered, for example, if the BFI counter exceeds the BFI threshold or maximum number (e.g., to notify the serving gNB where a beam failure has been detected).

[0070] The MAC entity may reset the BFI counter, for example, only after the beam failure detection timer (BFD_timer) expires (e.g., only after expiration), which may help provide hysteresis in the detection function. The WTRU may reset the BFD timer, for example, each time a BFI is indicated. In an embodiment, the MAC entity may reset the BFI counter, for example, only after observing no BFI indication from the physical layer (PHY) over a plurality (e.g., three) of consecutive CSI-RS periods (e.g., based on the BFD timer configuration).

[0071] The WTRU may report a BFR request for a beam failure detected for the SpCell, for example, by initiating a random access procedure for beam reestablishment. The WTRU may select an appropriate physical random access channel (PRACH) preamble and / or PRACH resource depending on the best and / or better measured downlink beam (CSI-RS or DL synchronization signal block (SSB)). The WTRU may reestablish a beam pair, for example, if the WTRU can determine the association between the DL beam and the UL preamble and / or PRACH occasion. The downlink (DL) beam selected by the WTRU may be tested, for example, by receiving a random access response (RAR) on the DL beam. The reestablishment random access (RA) procedure may be performed faster, for example, if the gNB configures a set of contention-free PRACH preambles / resources, which may be prioritized for selection by the WTRU (e.g., at the time of initiating the RA procedure). The WTRU may report a BFR request for a beam failure detected for the Scell, for example, by transmitting a MAC CE indicating the cell in which the beam failure was detected.

[0072] DRX may refer to any form of power saving applied by a WTRU, characterized by a reduction in receive and / or transmit activities. DRX may be applicable to any WTRU state (e.g., connected, inactive, idle, etc.). Connected mode DRX may specify, for example, (minimum) physical downlink control channel (PDCCH) decoding requirements while the WTRU is configured in connected mode DRX. The WTRU may be further configured to monitor the PDCCH during an on-period, for example, if the WTRU receives a wake-up signal (WUS) before the on-period. DRX may define an active time for decoding (e.g., some) downlink control information (DCI) (plural available). DRX may be based on an "on" period that occurs (e.g., periodically at a fixed rate) once per DRX cycle (e.g., per DRX cycle). The on-period may be specified.

[0073] Channel state information (CSI) may include, for example, at least one of a channel quality index (CQI), a rank indicator (RI), a precoding matrix index (PMI), L1 channel measurements (e.g., reference signal received power (RSRP) such as L1-RSRP, or signal to interference and noise ratio (SINR)), a CSI-RS resource indicator (CRI), a synchronization signal (SS) / physical broadcast channel (PBCH) block resource indicator (SSBRI), a layer indicator (LI), and / or any other measured quantity measured by a WTRU from a configured CSI-RS or SS / PBCH block.

[0074] Uplink control information (UCI) may include, for example, CSI, hybrid automatic repeat request (HARQ) feedback for one or more HARQ processes, a scheduling request (SR), a link recovery request (LRR), cell group uplink control information (CG-UCI), and / or other control information bits that may be transmitted on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

[0075] Channel conditions can include any conditions related to the radio / channel state. The WTRU may determine the channel conditions from, for example, WTRU measurements (e.g., L1 / SINR / RSRP, CQI / modulation and coding scheme (MCS), channel occupancy (CO), received signal strength indicator (RSSI), power headroom, exposure headroom), L3 / mobility-based measurements (e.g., RSRP, reference signal received quality (RSRQ)), RLM state, and / or channel availability in the unlicensed spectrum (e.g., whether the channel is occupied or is considered to be experiencing consistent LBT failures based on the determination of the listen-before-talk (LBT) procedure).

[0076] Wireless transmissions (e.g., in an NR system) can support operation in higher frequency bands. Transmissions in higher frequency bands may experience higher propagation losses, for example, due to the channel characteristics of those bands. Beam-based transmissions can be beneficial at higher frequencies (e.g., to direct power on one or more beams).

[0077] Omnidirectional transmissions can be used in higher frequency ranges, for example, to target short-range transmissions, lower data rates or control information, and / or WTRUs without an established narrow beam. For example, broadcast transmissions (e.g., for sidelink) can be used for short-range communication.

[0078] Omnidirectional link management may have different measurement requirements than directional beams, for example, for beam management, radio link monitoring, CSI reporting, and / or mobility management purposes. It may be useful for the measurement requirements to be adapted, for example, to reduce the impact on the battery usage of the WTRU (e.g., in combination with beam management and higher frequencies).

[0079] The beam management process may not function properly, for example, when the WTRU wakes up after a long DRX period (e.g., especially when the DRX period is relatively long compared to the CSI-RS periodicity), (e.g., when there are no requirements for beam maintenance measurements during the DRX sleep period). CSI-RS-based radio link monitoring overlapping with the DRX on period may result in increased power consumption (e.g., when the DRX period is shortened so that the radio link is reliably maintained) or an increased probability of link loss (e.g., when the DRX period is too large for the WTRU to maintain the beam without waking up), thereby presenting a trade-off between power consumption and the level of radio link maintenance.

[0080] Beam management may be provided. Beams (e.g., at higher frequencies) may be characterized, for example, based on beam identification and / or management processes.

[0081] A beam may be associated with a beam identification (beam ID) or a beam index. The beam index may be unique to the downlink (DL) and / or uplink (UL). For example, a downlink beam may identify the downlink beam and the associated uplink beam. The association between the uplink beam and the downlink beam may be determined, for example, configured and / or implicitly, based on the results of the beam management process and the associated UL and DL frequencies.

[0082] The WTRU may maintain a beam management process to determine, for example, among other operations, which beam IDs to maintain, activate, deactivate, and / or consider as candidates for activation. The beam management process may track a list of maintained beams and a list of candidate beams. The beam management process may (e.g., further) perform operations related to BFD and BFR. The beam management process may (e.g., also) be used to change the beam state. (For example, each) beam may have at least one of, for example, (i) an active state and / or a maintained state, (ii) an inactive state, (iii) a candidate state, (iv) an initial state, and / or (v) an adjusted state.

[0083] The WTRU may, for example, measure the associated CSI-RS or SSB (e.g., part of the BFD) for beams in the active state and / or maintained state. The WTRU may monitor the associated PDCCH resources or search space. The WTRU may activate a beam, for example, by a quasi-static configuration (e.g., a default active beam) (e.g., after receiving activation signaling), or after measuring the channel state quantity of the associated measurement resources below a configured threshold.

[0084] The WTRU may, for example, not measure the associated CSI-RS or SSB (e.g., part of the BFD) for beams in the inactive state. The WTRU may deactivate a beam, for example, after receiving deactivation signaling, after declaring a beam failure, and / or after measuring the channel state quantity of the associated measurement resources below a configured threshold.

[0085] The candidate state beam may be, for example, also an inactive beam. The beam ID can be configured, for example, by upper layer signaling or determined by the WTRU (e.g., based on the channel condition measurement of the related CSI-RS / SSB) and can be a candidate. The WTRU may measure the related CSI-RS or SSB, for example, as part of the BFR for the candidate beam (e.g., for beam reselection).

[0086] The initial state beam can be transmitted / received with default parameters (e.g., beam width, etc.).

[0087] The adjusted state beam can be transmitted / received with modified parameters.

[0088] Beam configurations and characteristics can be provided. Beamforming and / or patterns can be provided.

[0089] The beam can be characterized, for example, by at least one of (i) beam parameters, (ii) beam width or directivity coefficient, (iii) beam type, (iv) beam reference signal, and / or (v) beam transmission configuration indicator (TCI) state(s).

[0090] A beam can be characterized by beam parameters. The beam parameters can include one or more of an applied (e.g., spatial) filter, a codebook(s), a precoding table(s) and / or weights, RF phase shifts, and channel state information (CSI). The beam parameters can exist for a downlink beam, an uplink beam, or a bi-directional beam. The channel can be reciprocal (e.g., time division duplex (TDD)) or non-reciprocal (e.g., frequency division duplex (FDD)). A WTRU can be composed of multiple beams. For example, each of the multiple beams can be associated with a different set of parameters (s), where each can have an assigned value or range of values. For example, a WTRU can be composed of multiple beams, and each beam can be associated with a specific (e.g., different) spatial filter.

[0091] A beam can be characterized by a beam width and / or a beam steering coefficient. For example, a WTRU can be configured to associate a beam with a “width”. The beam width can correspond to a set of beam parameters (s). For example, the beam width can correspond to one or more weighting patterns. The beam width can correspond to a specific spatial filter.

[0092] A beam can be characterized by a beam type. For example, a beam can be omnidirectional or directional and can be considered a special case of beam width characteristics.

[0093] A beam can be characterized by a beam reference signal. For example, a beam can be associated with a synchronization signal block (SSB) and / or a channel state information reference signal (CSI-RS) for purposes such as, for example, measurement of the quality of a DL beam, beam obstruction detection, and / or beam identification.

[0094] The beam can be characterized by a beam transmission configuration indicator (TCI) state(s). The beam can be associated with one or more TCI states. The network may use the TCI, for example, to indicate the (in)active state of a given beam for PDCCH and / or physical downlink shared channel (PDSCH) transmission. The beam can also be associated with an uplink TCI state (for example).

[0095] There may be beam-related requirements for higher frequencies. For example, a WTRU implementation may meet the requirements of one or more (e.g., the aforementioned) beam characteristics, which may be a test mode of the WTRU implementation. In an embodiment, the test may include the expected pattern of radiation, spectral leakage of the radiation pattern, etc. Different WTRU implementations may be adapted to specific (e.g., determined, selected, configured) sensitivity levels, spectral emission patterns, etc. WTRU compliance may support different beams that meet specific requirements.

[0096] The WTRU may have the ability to meet beam-related requirements for higher frequencies. For example, a WTRU implementation may support one or more requirements to enable different beams with different interference characteristics and / or beam widths. The WTRU may report beam availability to the network, for example, as part of WTRU capability exchange.

[0097] The WTRU may be configured for beam-related requirements for higher frequencies. The WTRU may be composed of multiple beams. For example, the WTRU may be composed of beam ID = 0 (e.g., in the case of an omnidirectional beam) and beam ID!= 0 (e.g., in the case of a directional beam). The WTRU may be further composed of one or more directional beams. For example, the WTRU may be composed of beam ID = 1 (e.g., associated with the first beam width x = 1), beam ID = 2 (e.g., associated with the second beam width x = 2), etc. (e.g., up to the maximum number of beams). In an embodiment, the maximum number of directional beams may be a WTRU capability.

[0098] The WTRU may be configured for beamwidth control. The WTRU may be configured with a reference signal (e.g., SSB, CSI-RS) configuration for a given beam. The WTRU may be configured such that, for example, (e.g., one) reference signal configuration may be assigned multiple beamwidths. The beam reference signal configuration may be associated with a plurality of beamwidth indices where, for example, (e.g., each) index may correspond to (e.g., at most) one beamwidth. A beam, for example, in such a scenario, may be defined based on the reference signal configuration of the beam, and for example, its control may be associated with a change in the beamwidth index. The beamwidth index may correspond to, for example, a beam ID.

[0099] Beam control may be provided (e.g., in downlink control information (DCI)). The WTRU may receive control signaling (e.g., on a first beam carrying a control channel such as PDCCH). The control signaling may include an index to a beam configuration for (i) reception of data (e.g., for a DL beam on a data channel such as PDSCH), (ii) transmission of data (e.g., for a two-way beam on an uplink channel such as PUSCH), and / or (iii) transmission of control information using the indicated beam configuration (e.g., for a two-way beam on an uplink control channel such as PUCCH).

[0100] The WTRU may receive control signaling indicating (de)activation of a beam configuration, beam index, and / or associated beamwidth(s). The (de)activation indication may be applicable to a particular direction (e.g., downlink), a particular channel (e.g., PDSCH, PDCCH, PUSCH, PUCCH, PRACH), and / or a subset of transmission types (e.g., paging, UCI type, data type). The control signaling may be dynamic (e.g., received on a MAC CE or DCI) or semi-static (e.g., received by an RRC (re)configuration).

[0101] The beam reference signal may be specific to the WTRU. The WTRU may be composed of reference signals specific to the WTRU (e.g., SSB, CSI-RS) for one or more beams of the WTRU configuration, in addition to, for example, broadcast signals and / or any common beam configuration (e.g., SSB) determined from the configuration. The WTRU may receive the configuration, for example, using L3 / RRC signaling.

[0102] The reference signal (RS) configuration may depend on the beam index. For example, the WTRU may be composed of one or more indices (e.g., each representing) that may be associated with the reference signal configuration (e.g., representing the beam and / or beam width). The WTRU may use the associated configuration to determine the applicable resource allocation (e.g., in time and / or frequency) for a given index. The gNB may control the allocation of resources of the reference signal for beam management and / or the determination of beam parameters (e.g., the applicable beam width for uplink transmission of a bi-directional beam), for example, by controlling the beam index (e.g., using the index in DCI on the control channel). The WTRU may perform RS-related measurements within the resource (as may be expected).

[0103] The beam index may depend on the RS configuration (e.g., blind detection and / or measurement). For example, the WTRU may perform measurements using multiple reference signal configurations. The WTRU may perform measurements in time / frequency resources associated with different reference signal configurations. The WTRU may determine the index from the association with the reference signal configuration, for example, if the WTRU determines that the measured value on the corresponding resource exceeds a threshold. The WTRU may select the applicable index for subsequent transmission and determine the applicable beam parameters according to the index, e.g., the beam width. The gNB may control the determination of beam allocation and / or beam parameters (e.g., the applicable beam width for uplink transmission of a bi-directional beam), for example, by controlling the transmission of the reference signal specific to the WTRU for beam management.

[0104] Measurements can be responsive to discontinuous reception (DRX). The network (NW) can configure the WTRU, for example, such that measurement opportunities for beam management (e.g., BFD) are aligned (e.g., as closely as possible) with the WTRU's power saving mechanism (if configured).

[0105] Network configuration can provide alignment between DRX and BFD. For example, the WTRU may receive a DRX configuration that temporally (e.g., mostly) aligns or matches measurement opportunities for beam management (e.g., BFD) with the DRX active time resulting from the WTRU. This alignment of opportunities can match the DRX on-period portion of the DRX active time.

[0106] Network configuration can provide a WTRU-configurable mask function between DRX and BFD. The WTRU can be configured to perform beam-related measurements, for example, when it is in the DRX active time (e.g., a mask function between the DRX active time and the measurement opportunity). The WTRU can determine to apply a mask (e.g., only this one) based on the DRX on-period (e.g., the WTRU may not need to perform beam-related measurements outside of the WTRU's DRX on-period). The mask function can be, for example, a WTRU L3 / RRC configurable aspect.

[0107] Network configuration can provide a WTRU-configurable RS for beam management and DRX alignment. The WTRU can be configured with reference signals specific to the WTRU for beam management (e.g., SSB, CSI-RS). The WTRU can receive a configuration where, for example, the periodicity of the RS and the DRX cycle are similar to each other and / or are integer multiples of each other.

[0108] The network configuration may provide WTRU-configurable RSs for beam management and DRX control. The WTRU may determine measurement opportunities for beam management, for example, in response to DRX PDCCH monitoring occasions. The network may control DRX. PDCCH blind decoding occasions may be synchronized between the WTRU and the NW. The WTRU may be configured with one or more measurement configurations for measuring channel conditions (e.g., based on CSI-RS and / or SSB), such as a set of RS measurement opportunities. The WTRU may, for example, determine measurement opportunities and / or the timing of measurement opportunities (e.g., for beam management) according to at least one of: (i) the DRX on period, (ii) the DRX inactivity timer, (iii) the DRX cycle period (e.g., short, long), (iv) the DRX configuration, (v) the DRX active time, (vi) the wake up signal (WUS) occasion, (vii) the wake up signal (WUS), (viii) the channel conditions (e.g., RSRP, SINR, RSSI, power headroom, CO, and / or CQI), (ix) the speed or level of channel variations (e.g., from the perspective of fast fading), (x) the state of the beam in a maintained set of beams, (xi) downlink reception, (xii) uplink reception, (xiii) changes in the bandwidth part (BWP), and / or (xiv) changes in the search space set (e.g., from the reception of DCI format 2_0).

[0109] A WTRU may be configured to determine a measurement occasion and / or the timing of a measurement occasion, for example, based on a DRX on-period. The WTRU may determine that a first set of RS measurement occasions may be applicable during the on-period. The WTRU may determine a pattern in the time (e.g., and / or frequency) of an RS measurement occasion relative to the start of the on-period (e.g., the first symbol). The pattern may be a configurable aspect of the WTRU. The pattern may be a pattern specific to the WTRU and / or may be an indication for applying a masking function, for example, to a system-specific set of RS occasions. The WTRU may determine, for example, that a second set of RS measurements is applicable outside of the on-period (e.g., similarly) if (i) the WTRU is within a DRX active time and / or (ii) the WTRU is configured to apply a masking function (e.g., if and only if in that case).

[0110] FIG. 2 shows an example of beam management detection for a beam obstruction case having a measurement occasion during an on-period associated with a DRX cycle. As shown by the example of FIG. 2, the DRX cycle may be a long DRX cycle. A WTRU may be configured to detect a beam obstruction (e.g., BFD) based on detection of a threshold number of BFIs. In FIG. 2, a BFI is indicated by an X and the absence of a BFI is indicated by a checkmark. A BFI may be tracked or counted, for example, using a BFI counter (e.g., as shown in FIG. 2). The WTRU may be configured to detect or trigger a beam obstruction (e.g., BFD) based on, for example, more than six (6) BFIs or a threshold of seven (7) BFIs (e.g., as shown by the example of FIG. 2). Measurement occasions for detecting a BFI, or the absence thereof, may occur during an on-period in a long DRX cycle. Counts of BFIs (e.g., by a BFI counter) detected during an on-period of a long DRX cycle are shown as 0, 1, 2, and 3 in FIG. 2. BFIs occurring outside of the on-period may not be detected or counted by a BFI counter. As shown for detecting a beam obstruction, it may take a long time to count seven (7) BFIs during an on-period.

[0111] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity, for example, based on a DRX inactivity timer. The WTRU may determine that, for example, when the DRX inactivity timer is running, a first set of RS measurement opportunities may be applicable, or for example, otherwise, a second set of RS measurement opportunities may be applicable.

[0112] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity, for example, based on a DRX cycle period (e.g., short, long). The WTRU may determine that, for example, when a short DRX cycle is used, a first set of RS measurement opportunities may be applicable, or otherwise (e.g., when a long cycle is used), a second set of RS measurement opportunities may be applicable.

[0113] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity, for example, based on a DRX configuration. The WTRU may determine that, for example, when the associated DRX configuration is used, a first set of RS measurement opportunities may be applicable, or for example, when not, a second set of RS measurement opportunities may be applicable. The WTRU may be configured with multiple DRX configurations. The WTRU may be configured with an association between a set of RS measurement opportunities and a DRX configuration (e.g., by RRC signaling).

[0114] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity, for example, based on a DRX active time. The WTRU may determine that, for example, when the WTRU is within the DRX active time, a first set of RS measurement opportunities may be applicable, or for example, when not, a second set of RS measurement opportunities may be applicable.

[0115] The WTRU may be configured to determine a measurement opportunity and / or the timing of the measurement opportunity, for example, based on a WUS occasion. The WTRU may determine that, for example, a first set of RS measurement opportunities may be applicable during a period in which a WUS may be received (e.g., a WUS occasion), and, for example, a second set of RS measurement opportunities may be applicable if not.

[0116] The WTRU may be configured to determine a measurement opportunity and / or the timing of the measurement opportunity, for example, based on a WUS. The WTRU may determine that, for example, a first set of RS measurement opportunities may be applicable starting from when a WUS for the WTRU is received. The first set of RS measurement opportunities may be applicable for a specific (e.g., configurable) period. The period may correspond to a timer. The WTRU may start (or restart) the timer, for example, based on the reception (e.g., at the time of reception) of the WUS. The WTRU may determine that, for example, a second set of RS measurement opportunities may be applicable if not (e.g., if the timer is not running and / or the period has elapsed). The period may be determined, for example, (implicitly) (alternatively) from the DRX and WUS configuration. The WTRU may determine the period as the time from a WUS occasion or after a WUS occasion until the start of a DRX on period. The period may be a (pre-)defined or (pre-)configured period, for example, before a WUS occasion or the start of a DRX on period. The first set of RS measurement opportunities may depend on an index indicated as part of the WUS. The index may refer to, for example, one of a set of (e.g., possible) sets of RS measurement opportunities configured by a higher layer.

[0117] The WTRU may be configured to determine measurement opportunities and / or the timing of measurement opportunities, for example, based on one or more channel conditions (e.g., RSRP, SINR, RSSI, power headroom, CO, and / or CQI). The WTRU may determine, for example, that a first set of RS measurement opportunities may be applicable, or (more generally, for example) may determine to (de)activate a given RS measurement pattern if (i) measured channel condition(s) (e.g., RSRP, SINR, RSSI, PH, CO, and / or CQI), or (ii) a change in the measured channel condition(s) since the last measurement, is (a) less than a configured threshold, (b) greater than a configured threshold, or (c) within a range configured for an applicable set.

[0118] The WTRU may be configured to determine measurement opportunities and / or the timing of measurement opportunities, for example, based on the speed or level of channel variation (e.g., from the perspective of fast fading). The WTRU may switch to a particular set of RS measurement opportunities, for example, if the measured WTRU speed is higher or lower than a configured threshold, or (more generally, for example) may (de)activate a given RS measurement pattern. Otherwise, a second set of RS measurement opportunities may be applicable.

[0119] The WTRU may be configured to determine measurement opportunities and / or the timing of measurement opportunities, for example, based on the state of the beam in a maintained set of beams. The WTRU may determine a loss of the maintained beam ID, for example, due to a blocking effect, a corner effect, or based on a relevant measured value below a threshold. The WTRU may (de)activate a set of RS measurement opportunities associated with the lost beam. The WTRU may (de)activate a set of RS measurement opportunities associated with a candidate beam for beam realignment. The WTRU may monitor a set of RS measurement opportunities associated with (i) the active beam(s) in the maintained set of beams and / or (ii) the configured set of candidate beams.

[0120] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity, for example, based on downlink reception. The WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, (i) after receiving downlink data or control signaling (e.g., on a subset of DL channels or resources), and / or (ii) upon receiving a dynamic indication (e.g., DCI or MAC control element (CE)) for applying a measurement pattern. For example, otherwise, a second set of RS measurement opportunities may be applicable. The first set of RS measurement opportunities may be applicable for a specific period (e.g., based on a configured inactivity timer). The first set of RS measurement opportunities may depend on a priority or its associated HARQ-ACK associated with downlink reception, such as a priority indication signaled from DCI or configured by a higher layer. The priority may correspond to, for example, one of a set of possible sets of RS measurement opportunities configured by a higher layer. The priority indication may be obtained, for example, from an explicit field of DCI, from an RNTI, from a search space, or from a control resource set (CORESET) in which the DCI is decoded.

[0121] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity, for example, based on uplink transmission. The WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, after transmitting uplink data or UCI (e.g., on a channel associated with a specific uplink resource or measurement pattern). For example, otherwise, a second set of RS measurement opportunities may be applicable. The first set of RS measurement opportunities may be applicable for a specific period (e.g., based on a configured inactivity timer). The first set of RS measurement opportunities may depend on a priority associated with uplink transmission, such as a priority indication signaled from DCI (e.g., for a dynamically scheduled PUSCH) or configured by a higher layer (e.g., for a scheduling request or configured grant).

[0122] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity based on, for example, a change (e.g., a switch) in a bandwidth part (BWP). The WTRU may determine, for example, that a default set of RS measurement opportunities may be applicable when there is a change in the bandwidth part (e.g., due to DCI or timer expiration).

[0123] The WTRU may be configured to determine a measurement opportunity and / or the timing of a measurement opportunity based on, for example, a change (e.g., a switch) in a search space set (e.g., from reception of DCI format 2_0). The WTRU may determine, for example, that a first set of RS measurement opportunities may be applicable for a first group index of the search space set, and that a second set of RS measurement opportunities may be applicable for a second group index of the search space set, etc. In some examples, the second set of RS measurement opportunities may have a longer period between each measurement (e.g., for more relaxed BFD activity) compared to the first set of RS measurement opportunities, or vice versa.

[0124] The WTRU may perform behavior related to DRX, for example, if WUS is not configured (e.g., if and only if). The WTRU may perform behavior related to WUS, for example, if DRX is not configured (e.g., if and only if).

[0125] The SSB / CSI-RS periodicity can be aligned with the DRX period, including, for example, switching between long DRX and short DRX. The measurement opportunities for SSB / CSI-RS (or their periodicity) can vary, for example, according to the DRX state. In an example, more scheduling activity for a given WTRU on the PDCCH can result in a shorter BFD evaluation period (e.g., more beam management and monitoring), while less scheduling can result in a longer BFD period. The longer BFD period can be bounded, for example, by (e.g., configurable) values. The WTRU can adapt (e.g., dynamically) the measurement opportunities (e.g., in time and / or frequency) for BFD, SSB / CSI-RS measurements in synchronization with DRX, for example, under the control of the gNB.

[0126] The WTRU can perform measurements at measurement opportunities (e.g., determined as described herein) for the purpose of, for example, beam failure detection (BFD).

[0127] The WTRU may apply any of the logics described herein to measurements related to radio link monitoring (RLM), mobility related measurements, and / or CSI reporting (e.g., similarly).

[0128] In an example of RS measurement opportunities, the WTRU can be composed of multiple CSI measurement resources (e.g., having different periodicities). The WTRU may assume that the existing CSI measurement resources correspond to currently applicable sets, such that, for example, a given set is applicable if certain conditions are met.

[0129] A set of RS measurement opportunities can be configured by at least one of, for example, (i) an index or identification of the set, (ii) a time domain offset (e.g., a start offset from a slot boundary), (iii) periodicity (e.g., in slots, symbols, or absolute time), (iv) a frequency domain granularity (e.g., all physical resource blocks (PRBs), every other PRB, etc.) in which CSI measurements can be (e.g., are) performed, (v) a related frequency domain allocation (e.g., BWP, carrier, sub-band) for CSI measurements, (vi) a related uplink reporting resource or channel (e.g., PUCCH or PUSCH reporting resource), (vii) a related CSI-RS(s) / CSI-RS resource set(s), (viii) a related DRX configuration or cycle, (ix) a related beam identification (ID) or list of beam types, (x) applicability to a related WUS(s) or WUS occasion, (xi) an inactivity timer(s) (e.g., in slots, symbols, or absolute time), (xii) whether the set of RS opportunities is applied or can be applied for BFD, and / or (xiii) whether the set can be used as a default configuration.

[0130] In an example, a set of RS measurement opportunities can be applied as a mask to a set of resources used for CSI measurements. The WTRU may assume / determine that a resource exists if, for example, and only if, it temporally overlaps with a time pattern corresponding to the set of RS measurement opportunities.

[0131] A set of RS measurement opportunities may correspond to (e.g., alternatively) a particular group of resources that can be used for CSI measurement and that can be identified, e.g., by an index. The index may be added to the configuration of (e.g., each) CSI resource configuration or to the configuration of (e.g., each) CSI-RS, CSI interference measurement (CSI-IM), or SSB resource. The WTRU may determine or assume the presence of (e.g., each) resource if, e.g., a set of RS measurement opportunities corresponding to the index is applicable, e.g., according to at least one of the embodiments (e.g., if and only if in that case).

[0132] The index may be added as (e.g., alternatively) part of the configuration of (e.g., each) CSI reporting configuration. The WTRU may measure and report according to the CSI reporting configuration if, e.g., a set of RS measurement opportunities corresponding to the index is applicable (e.g., according to at least one of the embodiments), thereby enabling (e.g., making possible) the matching of measurement resources and reporting resources. In (e.g., alternative) embodiments, the RRC may configure a group of CSI reporting configurations within the CSI measurement configuration, where (e.g., each) group may correspond to a set of RS measurement opportunities. The WTRU may apply (e.g., at any time) a set of CSI reporting configurations of the group corresponding to the set of RS measurement opportunities that can be obtained, e.g., according to at least one of the embodiments.

[0133] A CSI reporting configuration may comprise (e.g., alternatively) at least one set of RS measurement opportunities (including, e.g., a default set). Each set of RS measurement opportunities may include a set of resources for channel measurement and multiple sets of resources for interference measurement (e.g., CSI-IM and / or NZP CSI-RS). The WTRU may utilize (e.g., for each CSI reporting configuration) resources corresponding to an index that identifies the set of RS measurement opportunities, e.g., according to at least one of the embodiments.

[0134] A link may be configured between BFD and DRX. DRX may affect beam management. The WTRU may change the state of a subset of beam states, activate / deactivate the associated CSI-RS or SSB, and / or pause / resume the associated BFD measurements and procedures, e.g., according to the DRX state and / or the active DRX configuration. The WTRU may activate / deactivate a particular beam and the associated CSI-RS, e.g., according to the DRX state and / or based on whether a particular DRX timer is running. The WTRU may activate / deactivate one or more (e.g., particular) beams and / or the associated CSI-RS, e.g., during the DRX inactive time. The WTRU may activate / deactivate one or more (e.g., particular) beams and / or the associated CSI-RS after satisfying any of the following triggers: (i) while the DRX inactivity timer is running, (ii) while the WTRU is within the active time, (iii) while the on period is running, (iv) at the start of a certain period before the on period, (v) while the DRX short cycle timer is running, (vi) while the DRX retransmission timer is running, (vii) at the start of a certain period before the WUS occasion, (viii) the period from the WUS occasion (e.g., including the WUS time) to the on period (e.g., or the end of the on period), and / or (ix) (e.g., as described herein). In an embodiment, the WTRU may measure the CSI-RS associated with BFD even if the WTRU is inactive or during the DRX off period.

[0135] After receiving (or in the absence of receiving) network signaling associated with, for example, DRX or power saving, the WTRU may change a subset of beam states, (de)activate associated CSI-RS or SSB, and / or pause / resume associated BFD measurements and procedures. In an embodiment, the WTRU may (de)activate a particular beam, associated CSI-RS, and / or pause or resume associated BFD measurements and procedures after receiving, for example, a short cycle command of DRX, a long cycle command of DRX, a WUS, and / or a PDCCH signal. In (for example, additional and / or alternative) examples, the WTRU may (de)activate a particular beam, associated CSI-RS, and / or pause or resume associated BFD measurements and procedures after not receiving, for example, a lifetime signal or a WUS associated with a beam. The (de)activation may be for, for example, several consecutive configured periods (for example, a DRX period or a separate configured period).

[0136] Beam management may affect DRX. The WTRU may transition to different DRX cycles and / or DRX configurations, pause / resume DRX functionality, and / or (re)start or stop a particular DRX timer in response to, for example, detection of a beam failure, detection of loss of a beam(s), and / or associated measurements. The WTRU may turn off or pause DRX, transition to a different DRX cycle (for example, short DRX), and / or (re)start a DRX inactivity timer based on, for example, detection of a beam failure (for example, at the time of detection), measurement of loss of a beam(s), and / or measurement of a channel condition quantity below a threshold of a maintained set of beams. The WTRU may (re)start a DRX retransmission timer or a DRX HARQ RTT timer after, for example, measuring loss of a beam(s) or measuring a channel condition quantity below a threshold of a maintained set of beams.

[0137] The WTRU may transition to different DRX cycles and / or DRX configurations, suspend / resume DRX functionality, and / or start certain DRX timers, for example, after receiving (or in the absence of receiving) network signaling associated with an active beam in a maintained set of beams. The WTRU may transition to different DRX cycles and / or DRX configurations, suspend / resume DRX functionality, and / or start certain DRX timers, for example, after measuring CSI-RS of a particular set of RS measurement opportunities (e.g., lower or higher than a threshold), after receiving an aperiodic CSI-RS request, and / or after receiving dynamic signaling associated with a set of RS measurement opportunities.

[0138] Beam re-establishment (e.g., after DRX sleep) may affect the BFR. The WTRU may measure configured active CSI-RS during a DRX beam observation period. The DRX beam observation period may be, for example, an on-period, a configured period before the on-period, a configured period before a WUS occasion, and / or the time between a WUS occasion and the on-period. The WTRU may measure configured active CSI-RS during a DRX beam observation period, provided that the WTRU receives WUS signaling wakeup before the on-period and / or before expiration of the inactivity timer. The WTRU may measure CSI-RS and / or SSB associated with a maintained set of beams. The WTRU may measure (e.g., additionally) CSI-RS and / or SSB associated with a set of candidate beams, for example, conditioned on the absence of a satisfactory beam in a maintained set of beams (e.g., meeting a configured channel condition measurement threshold).

[0139] The WTRU may trigger a BFR (e.g., a new BFR) or a beam re-establishment procedure if, for example, the WTRU does not have a satisfactory beam in a set of maintained beams during a DRX beam observation period (e.g., that meets a configured channel condition measurement threshold), and may (e.g., further) transition to active time or switch to a DRX cycle. The WTRU may (e.g., further) adjust triggering a BFR based on having at least one beam with a satisfactory measurement in a set of candidate beams. The WTRU may (e.g., during a BFR procedure) perform at least one of the operations of, for example, (i) following a conventional BFR procedure (e.g., as described herein), (ii) transitioning to active time, (iii) reporting a preferred beam ID(s) on a different serving cell (e.g., using a BFR MAC CE or PUCCH), and / or (iv) transmitting an SRS associated with a preferred beam(s). The WTRU may monitor one or more (e.g., specific) PDCCH resources (e.g., a subset of a configured CORESET(s) or search space(s)) associated with the indicated preferred beam(s). The association may be configured, for example, by RRC signaling. The WTRU may consider a beam re-establishment or BFR procedure to be successful based on, for example, receiving a response on the downlink (e.g., upon reception). The response may be adjusted to receive a PDCCH resource associated with the indicated preferred beam.

[0140] DRX can affect the BFD procedure. The WTRU may, for example, (e.g., after the expiration of the DRX inactivity timer or during a DRX sleep opportunity) based on becoming inactive (e.g., at that time), pause or (re)start the BFD timer, whereby, for example, it can be supported to maintain the BFI count, e.g., without resetting the BFI counter, e.g., before entering the sleep state. The WTRU may, for example, restart the BFD timer in (e.g., each) CSI-RS occasion (e.g., an occasion monitored in the connected mode) or a subset of CSI-RS occasions, e.g., if the WTRU is within the DRX inactivity time, e.g., if the WTRU does not perform CSI measurements during the DRX sleep period. The WTRU may be configured with a separate value of the BFD timer applicable to the WTRU, e.g., if the WTRU is configured with DRX and DRX is active. The WTRU may be configured with a separate timer (e.g., a timer instead of the BFD timer), whereby the WTRU can be applied to BFD, e.g., if the WTRU is configured with DRX, DRX is active, and / or DRX is used to freeze the BFI counter when C-DRX is used. The WTRU may, for example, restart the BFD timer with a value equal to the DRX cycle period (e.g., the period during the on period) when becoming inactive (e.g., after the expiration of the DRX inactivity timer or during a DRX sleep opportunity). The WTRU may, for example, apply the BFD timer (e.g., only this) to the BFD procedure (e.g., alternatively), if the WTRU is in the active time and / or C-DRX is not used or not configured. The WTRU may be configured with a DRX BFI count timer (e.g., a new DRX BFI count timer), whereby the WTRU can be applied to BFD, e.g., if the WTRU is configured with DRX and / or the WTRU is inactive. The WTRU may, for example, restart or resume the BFD timer if the BFD timer was paused after the expiration of the DRX count timer.

[0141] The WTRU may limit the count of BFIs to the BFIs measured during the active time. The WTRU may scale the count of beam failure events, for example, by a (e.g., specific) ratio related to the DRX period and / or the relative CSI-RS period. The WTRU may apply the scaling during the DRX on period and / or after the expiration of the inactivity timer. In an example, (e.g., if the CSI period is smaller than the active DRX period), the WTRU may increment the BFI counter, for example, by (active DRX period / CSI-RS period), (active DRX period / max (shortest configured DRX period, CSI-RS period)), and / or (active DRX period / period configured by RRC). As a possible illustration, consider a case where the long DRX cycle is 20 ms, the short cycle is 10 ms, and the CSI period is 2 ms. When the WTRU is in the long DRX and the WTRU detects a single BFI, the WTRU may increment the BFI counter by 20 / 2 = 10. When the WTRU is in the long DRX and detects a BFI, the WTRU may increment the BFI counter by 20 / 10 = 2. If the "period configured by RRC" is used and, for example, it is 5 ms, when the WTRU is in the long DRX and detects a BFI, the WTRU may increment the BFI counter by 20 / 5 = 4. The WTRU may round the count to an integer when incrementing the count, for example, when / if incrementing the count by a scaled value.

[0142] BFD may affect DRX operation. The WTRU may perform beam failure detection in each beam failure detection instance, for example, using (i) one or more periodic CSI-RS resources configured as beam failure detection resources (BFDRs), or (in the case where no BFDR is configured, for example) one or more periodic CSI-RS resources and / or SS / PBCH blocks associated with a CORESET (e.g., used by the WTRU to monitor the PDCCH). The WTRU may perform beam failure detection, for example, when the WTRU is within the active time having a C-DRX configuration. Hereinafter, (i) beam failure detection resources (BFDRs) and (ii) periodic CSI-RS resources and / or SS / PBCH blocks associated with a CORESET may be used interchangeably.

[0143] The WTRU may switch between DRX states (e.g., long DRX and short DRX cycles) based on, for example, detected beam failure incidents (BFIs) (plural possible). For example, the time to detect a connection problem (e.g., beam failure) may be reduced by switching between DRX states. For example, the WTRU may switch from a long DRX cycle to a short DRX cycle to confirm or detect a beam failure. The WTRU may perform beam failure detection (BFD) and recovery associated with DRX. For example, the WTRU may receive one or more configurations (e.g., configuration information within one or more messages) indicating short DRX cycles, long DRX cycles, and / or CSI-RS measurements (e.g., for determining a BFI). The WTRU may determine, as an example herein, a first number of beam failure incidents (BFIs) using a BFI counter value based on one or more CSI-RS measurements during one or more "on" periods of a long DRX cycle or during one or more active times. The BFI counter may count, for example, BFIs detected during CSI-RS measurements to determine a first BFI counter value. The WTRU may determine whether the BFI counter value exceeds a first threshold. The WTRU may switch to a short DRX cycle or interrupt DRX for CSI-RS measurements for BFD, for example, based on the condition that the first BFI counter value is greater than the first threshold. The WTRU may measure CSI-RS (plural possible) during one or more "on" periods associated with a short DRX cycle. The WTRU may update the first BFI counter value to a second BFI counter value, for example, based on the measurement. The WTRU may switch to a long DRX cycle for CSI-RS measurements associated with BFD or resume use of a long DRX cycle, for example, if the condition that the second BFI counter value is less than a second threshold. The WTRU may initiate beam failure recovery and / or interrupt DRX or reset an inactivity timer associated with DRX, for example, if the second BFI counter exceeds a third threshold (which may indicate detection of a beam failure).

[0144] Figure 3 shows an example of detecting beam failure cases in measurement opportunities with different periodicities associated with DRX on-periods having different durations. As shown by the example of Figure 3, the variable DRX cycle may include a first (e.g., long) DRX cycle and a second (e.g., short) DRX cycle. The WTRU may be configured to detect a beam failure (e.g., BFD) based on a threshold number of BFIs. As shown in Figure 3, the BFI is indicated by an X, and the absence of a BFI is indicated by a checkmark. The number of detected BFIs may be tracked or counted (e.g., as shown in Figure 3) using, for example, a BFI counter. The BFI may be determined / detected, and the BFI counter may be incremented based on, for example, the channel condition state determined from CSI-RS measurements. As shown by the example of Figure 3, the WTRU may be configured to detect or trigger a beam failure based on more than six BFIs, or a threshold of seven (7) or more BFIs. The measurement opportunities for detecting a BFI, or its absence, may occur during the on-period in a long DRX cycle and during the on-period in a short DRX cycle. The number of BFIs detected (e.g., tracked via the BFI counter) during the on-periods of the long DRX cycle and the short DRX cycle are shown as 0, 1, 2, 3, 4, 5, 6, and 7 in Figure 3. BFIs occurring outside the on-period during the first long DRX cycle may not be detected or counted by the BFI counter. The WTRU configured as shown in Figure 3 may detect a beam failure and enter BFR faster than a WTRU configured to remain in the long DRX cycle (e.g., as shown by the example of Figure 2).

[0145] As shown in FIG. 3, the WTRU may perform channel state information reference signal (CSI-RS) measurement(s) during one or more on-periods associated with a first (e.g., long) DRX cycle. The WTRU may determine / track the number of beam failure instances based on the CSI-RS measurement(s). In the example of FIG. 3, the BFI counter may remain zero (0) if no BFI is detected during the on-period of the long DRX cycle (e.g., as indicated by the "0" check mark in FIG. 3). The WTRU may increment the BFI counter by one (1) based on the detection of a first BFI (e.g., as indicated by the "1" X in FIG. 3) during the on-period of the long DRX cycle. The WTRU may increment the BFI counter by two (2) based on the detection of a second BFI (e.g., as indicated by the "2" X in FIG. 3) during the on-period of the long DRX cycle.

[0146] The WTRU may switch to a second (e.g., short) DRX cycle based on the determined number of beam failure instances (e.g., compared to a switching threshold). The WTRU may be configured to switch between DRX cycles (e.g., between a long DRX cycle and a short DRX cycle) based on, for example, the number of BFI switching thresholds (counted by the BFI counter). As shown by the example of FIG. 3, the WTRU may be configured to switch from a long DRX cycle to a short DRX cycle when the BFI counter value is greater than one (1) BFI. For example, the WTRU may (e.g., as shown in FIG. 3) switch from a long DRX cycle to a short DRX cycle when the BFI counter value is two (2).

[0147] The WTRU may perform CSI-RS measurements during an on-period associated with a second (e.g., short) DRX cycle. The rate and / or the measurement opportunities for detecting BFI may be increased by switching to a short DRX cycle. For example, this may enable the WTRU to detect beam failures faster (e.g., in a shorter period) than if the WTRU remained in a long DRX cycle (e.g., as shown by the example of FIG. 2). The WTRU may update the number of beam failure events based on additional CSI-RS measurement(s). For example, (e.g., as shown in FIG. 3), the BFI counter may be incremented to 3(3) based on the detection of a third BFI during the on-period of a first short DRX cycle (e.g., as indicated by the X of "3" in FIG. 3). The measurement(s) of CSI-RS(s) may continue during the on-period of the short cycle DRX. The WTRU may continue to update the number of beam failure events based on the CSI-RS measurement(s). For example, (e.g., as shown in FIG. 3), the BFI counter may update the count of BFI to 4, 5, 6, and 7 (e.g., at "4", "5", "6", and "7" respectively) in relation to the on-period of the short DRX cycle.

[0148] The WTRU may switch to non-DRX operation based on a determined number of beam failure events, e.g., (e.g., as shown in FIG. 3), compared to a BFD threshold. For example, the WTRU may switch to non-DRX operation if the number of beam failure events is equal to or greater than the BFD threshold (e.g., in the example of FIG. 3, more than 6 (6) BFIs, or 7 (7) BFIs). Non-DRX operation may include, for example, (e.g., as shown in FIG. 3), interrupting DRX, resetting or starting a DRX inactivity timer, and / or entering an active time mode.

[0149] The WTRU may switch (e.g., switch back) from a second (e.g., short) DRX cycle to a first (e.g., long) DRX cycle if, for example, the number of beam failure instances associated with the second DRX cycle is less than a second threshold (e.g., conditional thereon), which may be based on the number of BFIs detected during a particular (e.g., specified, determined, or configured) number of cycles of the second DRX cycle. For example, the WTRU may switch (e.g., switch back) from a second (e.g., short) DRX cycle to a first (e.g., long) DRX cycle if, after a configured number of cycles of the second (e.g., short) cycle, the BFI counter is less than seven (7) BFIs (e.g., six or less).

[0150] The WTRU may determine and / or receive (e.g., from a network device) configuration information that may include, for example, one or more of a first (e.g., long) DRX cycle, a second (e.g., short) DRX cycle, a timing associated with CSI-RS measurements in the first DRX cycle, a timing associated with CSI-RS measurements in the second DRX cycle, a first DRX cycle switch threshold, a first (e.g., BFD) threshold, a second (e.g., non-DRX) threshold, a second DRX cycle switch threshold, and / or the like.

[0151] The DRX inactivity timer can be reset based on, for example, a beam failure detection state (as shown, for example, by the example of FIG. 3). In an embodiment, the WTRU can reset the DRX inactivity timer when, for example, (i) the number of beam failure instances (BFIs) is greater than a threshold (where the threshold can be configured or determined independently of the maximum number of BFIs for declaring a beam failure (e.g., the first BFI threshold for inactivity time reset can be smaller than the second BFI threshold for BF declaration)), (ii) the beam quality of the beam failure detection resource is less than a threshold different from Qout, LR (e.g., used to determine a beam failure), (iii) the remaining BFDR within the active time (e.g., before the inactivity timer expires) is not sufficient to declare a beam failure, and / or (iv) there is no BFDR resource before the inactivity timer expires and the current BFI counter is greater than the first threshold and smaller than the second threshold (e.g., the WTRU can reset the timer if it can detect a beam failure when counting the number of BFIs in future BFDRs during an extra inactivity timer period). The DRX inactivity timer can be reset when one or more of the above conditions are met.

[0152] The inactivity timer can be suspended, for example, based on a beam failure detection state (e.g., when one or more of the aforementioned conditions are met) (e.g., alternatively).

[0153] The WTRU may monitor a PDCCH search space if it (i) interrupts DRX, (ii) ignores the DRX-off period (or inactive time), and / or (iii) considers itself within the active time. For example, if the WTRU declares a beam failure during the active time, it may monitor the PDCCH search space. The WTRU may skip monitoring one or more PDCCH search spaces that may be monitored by the WTRU during the active time (e.g., in this scenario). The WTRU may (i) monitor a PDCCH search space (e.g., configured as a beam recovery search space) after a new candidate beam indication (e.g., using a PRACH or BFR MAC CE), and / or (ii) monitor any search space associated with the beam recovery procedure (e.g., a common search space for RAR reception) after transmitting a contention-based random access (CBRA) preamble part of a RA initiated by BFR.

[0154] The first set of PDCCH search spaces may be monitored during the active time and the second set of PDCCH search spaces may be monitored during the inactive time. One or more of the following may apply: (i) the second set of PDCCH search spaces may be an empty set (e.g., if the BFI counter is less than the maximum), (ii) the second set of PDCCH search spaces may include a beam recovery search space (e.g., if the BFI counter reaches the maximum count), and / or (iii) the second set of PDCCH search spaces may include a beam recovery search space (e.g., if a new candidate beam is indicated and the WTRU has not received confirmation from the gNB).

[0155] The beam recovery search space may be a PDCCH search space using a recoverySearchSpaceId configured via higher layer signaling, for example.

[0156] The WTRU may (i) interrupt DRX, (ii) ignore DRX operation, or (iii) consider itself within the active time and operate as non-DRX operation, for example, when the BFI counter is higher than a threshold. The WTRU may resume DRX operation, for example, when the BFI counter is reset (e.g., when the measurement value of the beam failure detection resource is higher than the threshold Qin,LR). (i) The threshold may be a constant (e.g., 1) or a configured number that may be the same as or different from the maximum number of BFIs in the BF declaration, and / or (ii) the WTRU may operate as non-DRX operation, for example, until the WTRU receives confirmation of a new candidate beam indicated to the gNB (e.g., when the BFI counter is above the threshold). One or more of the above may apply. The confirmation of the new candidate beam may be the activation of the TCI state via the upper layer configuration or an explicit indication in the DCI using the C-RNTI or MCS-C-RNTI (e.g., on the recovery search space).

[0157] The WTRU may operate in DRX operation, for example, when the BFI counter < threshold (e.g., monitor the PDCCH within the active time and skip monitoring the PDCCH within the inactive time). The WTRU may operate in non-DRX operation, for example, when the BFI counter ≥ threshold (e.g., always monitor the PDCCH). The threshold may be a predefined number (e.g., 0) or may be configured.

[0158] For example, based on whether the BFI counter is less than or greater than a threshold, one or more of the following WTRU behaviors may be used.

[0159] In an embodiment, (e.g., when the BFI counter < threshold), for example, (i) the WTRU may monitor one or more PDCCH search spaces configured during the active time, and the WTRU may sleep during the inactive time (e.g., skip monitoring the PDCCH), (ii) the WTRU may measure one or more beam failure detection resources during the active time and skip measuring the configured beam failure detection resources during the inactive time, and / or (iii) the inactivity timer may not be reset by the beam failure detection procedure.

[0160] In an embodiment, (e.g., when the BFI counter ≥ threshold), for example, (i) the WTRU may monitor (a) the PDCCH search space during the inactive time (e.g., for recovery), or (b) for example, all configured PDCCH search spaces during the inactive time after the WTRU has transmitted a new candidate beam index or a recovery request signal (e.g., BFR MAC CE) via the PRACH, and the PDCCH search space (e.g., for recovery), (ii) the WTRU may measure the beam failure detection resources during the inactive time, (iii) the inactivity timer may be reset (e.g., based on the beam failure detection state), (iv) the WTRU may report to the gNB that the BFI counter is above the threshold by transmitting a signal (e.g., UCI on PUCCH, UCI on PUSCH, or SR) for reporting, for example, and / or (v) the WTRU may monitor the PDCCH search space and the CORESET (e.g., similar to BFD when DRX is not configured, generally).

[0161] The measurement threshold can be responsive to beam management. The WTRU can be configured with a measurement configuration that is specific to beam characteristics (e.g., beam type, beam width, beam ID, etc.). For example, the WTRU can perform (e.g., specific) link and / or connectivity management procedures in accordance with (e.g., a specific) beam configuration. The WTRU can be configured with a default beam and can use the associated configuration, for example, when no other beam has been selected (e.g., for (a) scheduled transmission(s)). The WTRU can use the default when, for example, a time alignment timer (TAT) is not running, when the WTRU is within DRX inactive time, and / or under the period of scheduling activity for (e.g., if any) limited unicast transmissions. The measurement configuration can include, for example, configurations related to beam management, configurations for radio link monitoring (RLM), configurations for mobility management and / or measurement reporting, configurations for measurements related to CSI reporting, and / or configurations for sensing unlicensed spectrum (e.g., energy detection level, sensing period).

[0162] The DRX configuration can be specific to a beam. For example, the WTRU can be configured with a DRX configuration that is specific to a beam, specific to a beam index, specific to a beam ID, and / or specific to a beam type. The WTRU can determine the applicable DRX configuration, for example, in accordance with the beam used for reception of the PDCCH control channel for a given cell. The WTRU can also determine the applicable DRX configuration, for example, when the beam is first established.

[0163] Efficient measurement of power is described for high-frequency operation. A wireless transmit / receive unit (WTRU) may determine measurement occasions according to scheduling activities and beam configuration. The WTRU may determine measurement occasions for beam failure detection (BFD), radio link monitoring (RLM), and / or mobility according to discontinuous reception (DRX) and / or BFD configuration. The WTRU may determine that a first set of reference signal (RS) measurement opportunities is applicable based on a first condition (e.g., when / if the DRX / BFD / channel state information (CSI) condition is satisfied), and a second set of RS measurement opportunities is applicable based on a second condition (e.g., when / if the DRX / BFD / CSI condition is not satisfied). The WTRU may be configured using multiple sets of CSI-RS measurement opportunities (e.g., using different periodicities). The WTRU may, for example, assume that a given set is applicable when the DRX / BFD / CSI condition is satisfied. The WTRU may determine DRX operation or non-DRX operation based on, for example, whether a BFI counter is less than a threshold or greater than or equal to the threshold. The WTRU may reset an inactivity timer based on, for example, one or more BFD states (e.g., beam failure instance (BFI) counter > threshold and no BFD resources before inactivity timer expiration). The WTRU may pause, disable, or (re)start a BFD timer when, for example, an inactive time is reached. The WTRU may change a beam state, (de)activate related CSI-RS, and / or pause / resume related BFD according to, for example, DRX state / configuration or related signaling. The WTRU may transition to different DRX cycles / configurations, pause / resume DRX functionality, and / or (re)start / stop one or more DRX timers according to, for example, detection of beam failure, loss of beam(s), or related measurement values. The WTRU may trigger a BFR / beam re-establishment procedure (e.g., a new BFR / beam re-establishment procedure) when, for example, the WTRU does not have a satisfactory beam during a DRX beam observation period.

[0164] Although the above features and elements are described in specific combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or may be used in various combinations with or without other features and elements.

[0165] The implementations described herein may consider 3GPP-specific protocols, but it is understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, the solutions described herein consider LTE, LTE-A, New Radio (NR), or 5G-specific protocols, but it is understood that the solutions described herein are not limited to this scenario and are further applicable to other wireless systems.

[0166] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, magnetic media such as read only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, internal hard disks, and removable disks, magneto-optical media, and optical media such as compact disc (CD)-ROM disks and / or digital versatile disk (DVD), etc. A wireless frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer may be implemented using a processor associated with the software.

Claims

Claim 1 A wireless transmit / receive unit (WTRU) comprising: a processor, receiving a radio resource control (RRC) message, the RRC message including measurement configuration information for beam failure detection, the measurement configuration information for beam failure detection indicating one or more reference signals to be used for performing beam failure detection, the RRC message including information indicating at least a first threshold and a second threshold to be used for determining whether to use a relaxed second beam failure detection measurement period; performing one or more first measurements for evaluating beam failure detection according to a first beam failure detection measurement period; determining that an L1 channel quality measurement value is greater than the first threshold; determining that a change in reference signal received power (RSRP) is less than the second threshold, the change in RSRP corresponding to an L3 / mobility-based measurement value; determining to evaluate beam failure detection according to the second beam failure detection measurement period based on the L1 channel quality measurement value being greater than the first threshold and based on the change in RSRP being less than the second threshold, the second beam failure detection measurement period being greater than the first beam failure detection measurement period; performing one or more second measurements for evaluating beam failure detection according to the second beam failure detection measurement period based on the L1 channel quality measurement value being greater than the first threshold and based on the change in RSRP being less than the second threshold; a WTRU comprising a processor configured to perform the above. Claim 2. The measurement configuration information includes information indicating at least a third threshold to be used for determining whether to use a relaxed second radio link monitoring measurement period. The processor performing one or more third measurements according to a first radio link monitoring measurement period; determining, based on the first threshold and the second threshold, that one or more channel conditions for using the second beam failure detection measurement period are satisfied; determining, based on the third threshold, that one or more conditions for using the second radio link monitoring measurement period are satisfied. Based on the first threshold, the second threshold, and the third threshold being satisfied, performing one or more fourth measurements according to a second wireless link monitoring measurement period, wherein the second wireless link monitoring measurement period is greater than a first wireless link monitoring measurement period, and The WTRU according to claim 1, further configured to perform the above. **Claim 3**: The WTRU according to claim 1, wherein the one or more first measurements are performed at least on a synchronization signal block (SSB). **Claim 4**: The WTRU according to claim 1, wherein the one or more first measurements are performed at least on a channel state information reference signal (CSI-RS). **Claim 5**: The processor is configured to Determine that the performed beam failure detection measurement is outside a configured beam quality threshold; Increment a beam failure event counter based on determining that the performed beam failure detection measurement is outside the configured beam quality threshold; Determine that the beam failure event counter has reached a maximum number of beam failure events; Based on determining that the beam failure event counter has reached the maximum number of beam failure events, start a random access procedure, wherein the WTRU is configured to use a contention-free random access preamble configured for beam failure detection in the random access procedure, and The WTRU according to claim 1, further configured to perform the above. **Claim 6**: The RRC message indicates the periodicity, time domain offset, and frequency domain information for the one or more reference signals used to perform beam failure detection measurements, and the RRC message indicates each reference signal associated with each of a plurality of candidate beams. The WTRU according to claim 1. **Claim 7**: The WTRU according to claim 1, wherein the processor is further configured to perform the one or more second measurements according to the second beam failure detection measurement period based on determining that a change in the synchronization signal block (SSB) RSRP measurement is less than a configured threshold. **Claim 8**: The WTRU according to claim 1, wherein the second beam failure detection measurement period is based on a discontinuous reception (DRX) period. **Claim 9** A method implemented by a wireless transmit / receive unit (WTRU), comprising Receiving a Radio Resource Control (RRC) message, wherein the RRC message includes measurement configuration information for beam failure detection, the measurement configuration information for beam failure detection indicates one or more reference signals used to perform beam failure detection, and the RRC message includes information indicating at least a first threshold and a second threshold used to determine whether to use a relaxed second beam failure detection measurement period, Performing one or more first measurements for evaluating beam failure detection according to a first beam failure detection measurement period, Determining that the L1 channel quality measurement value is greater than the first threshold, Determining that a change in reference signal received power (RSRP) is less than the second threshold, wherein the change in RSRP corresponds to an L3 / mobility-based measurement value, Determining to evaluate beam failure detection according to the second beam failure detection measurement period based on the L1 channel quality measurement value being greater than the first threshold and the change in RSRP being less than the second threshold, wherein the second beam failure detection measurement period is greater than the first beam failure detection measurement period, Performing one or more second measurements for evaluating beam failure detection according to the second beam failure detection measurement period based on the L1 channel quality measurement value being greater than the first threshold and the change in RSRP being less than the second threshold, A method comprising. [

10. ] The measurement configuration information includes information indicating at least a third threshold used to determine whether to use a relaxed second radio link monitoring measurement period, The method includes Performing one or more third measurements according to a first radio link monitoring measurement period, Determining that one or more channel conditions for using the second beam failure detection measurement period are satisfied based on the first threshold and the second threshold, Determining that one or more conditions for using a second radio link monitoring measurement period are satisfied based on the third threshold, Based on the satisfaction of the first threshold, the second threshold, and the third threshold, performing one or more fourth measurements according to a second radio link monitoring measurement period, wherein the second radio link monitoring measurement period is greater than the first radio link monitoring measurement period, and The method according to claim 9, further comprising.

11. The method according to claim 9, wherein the one or more first measurements are performed at least with a synchronization signal block (SSB).

12. The method according to claim 9, wherein the one or more first measurements are performed at least with a channel state information reference signal (CSI-RS).

13. The method comprises Determining that the performed beam obstacle detection measurement is outside the configured beam quality threshold; Incrementing a beam obstacle case counter based on determining that the performed beam obstacle detection measurement is outside the configured beam quality threshold; Determining that the beam obstacle case counter has reached the maximum number of beam obstacle cases; Based on determining that the beam obstacle case counter has reached the maximum number of beam obstacle cases, starting a random access procedure, wherein the WTRU uses a contention-free random access preamble configured for beam obstacle detection in the random access procedure, and The method according to claim 9, further comprising.

14. The method according to claim 9, wherein the second beam obstacle detection measurement period is based on a discontinuous reception (DRX) period.

15. Performing the one or more second measurements according to the second beam obstacle detection measurement period is based on determining that a change in a synchronization signal block (SSB) RSRP measurement is less than a configured threshold. The method according to claim 9.

Images