Power efficient measurement at higher frequency

Abstract

To implement power efficient measurements for high frequency operations.SOLUTION: A 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 opportunities. The WTRU may perform measurement(s) with determined / configured timing in a first DRX cycle based on condition(s). The WTRU may switch to a second DRX cycle and perform RS measurement(s) with determined / configured timing based on condition(s). The WTRU may switch from the second DRX cycle to the first DRX cycle or to non-DRX operation based on condition(s).SELECTED DRAWING: Figure 3

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 February 12, 2020, the disclosure of which is incorporated herein by reference in its entirety. [Background technology]

[0002] Mobile communications using radio communications continues to evolve. The fifth generation may be referred to as 5G. Previous (traditional) generations of mobile communications may be, for example, fourth generation (4G) long term evolution (LTE). Summary of the Invention

[0003] Power-efficient measurements may be implemented for radio frequency operation. A wireless transmit / receive unit (WTRU) may determine measurement occasions depending on scheduling activity and beam configuration. The WTRU may determine measurement occasions for beam failure detection (BFD), radio link monitoring (RLM), and / or mobility depending on discontinuous reception (DRX) and / or BFD configuration. The WTRU may determine that a first set of reference signal (RS) measurement occasions is applicable based on a first condition (e.g., if / when a DRX / BFD / channel state information (CSI) condition is met) and that a second set of RS measurement occasions is applicable based on a second condition (e.g., if / when a DRX / BFD / CSI condition is not met). The WTRU may be configured with multiple sets of CSI-RS measurement occasions (e.g., with different periodicities). The WTRU may assume that a given set is applicable, for example, if the DRX / BFD / CSI conditions are met. The WTRU may decide on DRX or non-DRX operation, for example, based on whether a BFI counter is below a threshold or above a threshold. The WTRU may reset the inactivity timer, for example, based on one or more BFD conditions (e.g., beam failure instance (BFI) counter > threshold and no BFD resources before the inactivity timer expires). The WTRU may, for example, pause, disable, or (re)start the BFD timer upon inactivity time. The WTRU may, for example, change the beam state, (de)activate the associated CSI-RS, and / or suspend / resume the associated BFD, depending on the DRX state / configuration or associated signaling.The WTRU may transition to a different DRX cycle / configuration, pause / resume DRX functionality, and / or (re)start / stop one or more DRX timers, for example, in response to detection of a beam failure, loss of beam(s), or related measurements. 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., in whole or in part) by, for example, device(s) (e.g., a WTRU, a network node such as a gNodeB (gNB), and / or the like) and / or system(s) configured to implement the method, which have one or more processors configured to perform the method (e.g., in whole or in part) as computer-executable instructions that may be stored, for example, on a computer-readable medium or a computer program product. The computer-readable medium or computer program product may include instructions that, when executed, cause one or more processors to perform the method.

[0005] The WTRU may perform beam failure detection (BFD) and recovery associated with DRX. In an embodiment, the WTRU may be configured to perform one or more of: performing a first CSI-RS measurement during an on-period associated with a first DRX cycle; determining a first number of beam failure cases based on the first CSI-RS measurement; switching to a second DRX cycle based on the determined first number of beam failure cases; performing a second CSI-RS measurement during an on-period associated with the second DRX cycle; determining a second number of beam failure cases based on the second CSI-RS measurement; and switching to non-DRX operation on condition that the second number of beam failure cases is greater than a first threshold. See, for example, FIG. 3 herein. The non-DRX operation may include at least one of suspending DRX or resetting an inactivity timer. The beam failure cases 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 by the network device to the WTRU. 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 (eg, further) be configured to switch from the second DRX cycle to the first DRX cycle, eg, on condition that a second number of beam failure instances is less than a second threshold.

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

[0008] The WTRU may (eg, further) be configured to determine 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 may be determined through use of a beam obstruction case counter. [Brief explanation of the drawings]

[0010] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that may be used within the communication system shown in FIG. 1A, according to one embodiment. [Figure 1C] 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system shown in FIG. 1A, according to one embodiment. [Figure 1D] 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system shown in FIG. 1A, according to one embodiment. [Figure 2] 1 shows an example of detecting a beam fault case by a measurement opportunity during an ON period in a DRX cycle. [Figure 3] 10 shows an example of detecting beam failure cases at measurement occasions with different periodicities during the DRX on periods in multiple DRX cycles with different durations. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] 1A illustrates an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. Communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcasts, etc., to multiple wireless users. Communication system 100 may enable multiple wireless users to access such content through the 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), etc.

[0013] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RANs 104 / 113, CNs 106 / 115, public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of WTRUs 102a, 102b, 102c, 102d may 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 as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

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

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

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

[0017] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114 a and the WTRUs 102 a, 102 b, 102 c in the RAN 104 / 113 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communications protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0018] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may 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 may implement a radio technology such as New Radio (NR) radio access, which may establish the air interface 116 using NR.

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

[0021] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (i.e., Wireless Fidelity, WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000EV-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), or the like.

[0022] 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 connectivity in a local area such as a location such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio 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 radio 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 establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-APro, NR, etc.). 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 through the CN 106 / 115.

[0023] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may 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. The CN 106 / 115 may 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 the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0024] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a public switched telephone network providing 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, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0025] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links.) For example, the WTRU 102c shown in FIG. 1A 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 IEEE 802 wireless technology.

[0026] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 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, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0027] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. 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. While FIG. 1B depicts 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., the base station 114a) over 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 IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light 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] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may use 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 over 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 mentioned 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 and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Furthermore, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown).

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

[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) over the air interface 116 and / or determine its location based on the timing of signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0034] The processor 118 may further be coupled to other peripherals 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 peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripheral device 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, a direction 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] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the UL (e.g., for transmission) and downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference through hardware (e.g., chokes) or processor-based signal processing (e.g., via a separate processor (not shown) or processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for transmission and reception of either some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or downlink (e.g., for reception)).

[0036] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

[0037] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, although it will be understood that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

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

[0039] 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 the 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] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, and selecting a particular serving gateway during initial attach of the WTRUs 102a, 102b, 102c. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0041] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions such as anchoring the user plane during inter-eNode B handovers, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

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

[0043] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional landline communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. Furthermore, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

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

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

[0046] A WLAN in infrastructure Basic Service Set (BSS) mode may have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic to a STA originating from outside the BSS may arrive through the AP and be delivered to the STA. Traffic originating from a STA to a destination outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs within a BSS may be transmitted, for example, through the AP, where the source STA may send traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between (e.g., directly between) a source STA and a destination STA via a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (e.g., all of the STAs) may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad hoc" communication mode.

[0047] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit beacons on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be the operating channel of the BSS and may be used by STAs 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 may be implemented. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0048] High Throughput (HT) STAs may, for example, use 40 MHz wide channels for communication via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0049] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. A 40 MHz and / or 80 MHz channel may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 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 Medium Access Control (MAC).

[0050] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah may support meter-type control / machine-type communications, such as MTC devices within macro coverage areas. MTC devices may have limited capabilities, including, for example, support for (e.g., only for) specific and / or limited bandwidths. MTC devices may include batteries with above-threshold battery life (e.g., to maintain very long battery life).

[0051] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be configured and / or limited by the STA among all STAs operating in the BSS that support the minimum bandwidth operating mode. In an 802.11ah example, the primary channel can be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) configuration can depend on the conditions of the primary channel. For example, if the primary channel is busy due to a STA (that only supports 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered busy, even though most of the frequency band may remain idle and be available for use.

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

[0053] FIG. 1D is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As mentioned above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also communicate with the CN 115.

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

[0055] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[0056] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. The non-standalone configured WTRUs 102a, 102b, 102c may communicate with and connect to gNBs 180a, 180b, 180c while also communicating with and connecting to another RAN, such as eNode-Bs 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0057] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the 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 , the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

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

[0059] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0060] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions, such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0061] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks such as the Internet 110 to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

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

[0063] 1A-1D and their corresponding descriptions, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0064] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation devices may be directly coupled to another device for testing purposes and / or may perform testing using terrestrial wireless communication.

[0065] One or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, e.g., one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0066] For example, a radio technology using New Radio (NR) as an example herein may support higher frequencies and beamforming (e.g., frequencies between 52.6 GHz and 71 GHz). NR may be used for high-data-rate eMBB, mobile data offload, short-range high-data-rate D2D communications, and industrial IoT. WTRU power consumption may be improved. For example, the WTRU's radio may be turned off to conserve energy without compromising the WTRU's beam management, mobility, and connectivity management.

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

[0068] The 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 in which the maintained beam is measured periodically. A beam failure recovery (BFR) request may be reported to the network, for example, upon detecting a beam failure. BFR may be configured for beam maintenance for a primary cell (Pcell) and / or a secondary cell (Scell). BFD measurements may be performed, for example, at the maximum of {DRX period, CSI-RS period} (e.g., in conventional systems) 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 (e.g., to notify the serving gNB that a beam failure has been detected) if, for example, the BFI counter exceeds a threshold or maximum number of BFIs.

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

[0071] The WTRU may report a BFR request for a detected beam failure for the SpCell, for example, by initiating a random access procedure for beam re-establishment. 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 re-establish a beam pair, for example, if the WTRU can determine an 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 re-establishment random access (RA) procedure may be 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 detected beam failure for the Scell, for example, by sending a MAC CE indicating the cell for which the beam failure was detected.

[0072] DRX may refer to any form of power saving applied by a WTRU characterized by reduced receive and / or transmit activity. DRX may be applicable to any WTRU state (e.g., connected, inactive, idle, etc.). Connected mode DRX may, for example, specify (e.g., minimum) physical downlink control channel (PDCCH) decoding requirements while the WTRU is configured in connected mode DRX. The WTRU may (e.g., further) be 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)(s). DRX may be based on (e.g., fixed periodic) "on" periods occurring in a DRX cycle (e.g., once per DRX cycle). The on periods may be specified.

[0073] The 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), an L1 channel measurement (e.g., a reference signal received power (RSRP) such as L1-RSRP, or a 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 measurement measured by the 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] The channel conditions may include any conditions related to radio / channel conditions. 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 status, and / or channel availability in the unlicensed spectrum (e.g., whether the channel is occupied or whether the channel is considered to be experiencing consistent listen-before-talk (LBT) failures based on a listen-before-talk procedure determination).

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

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

[0078] Omni-directional link management may have different measurement requirements than directional beams, e.g., for beam management, radio link monitoring, CSI reporting, and / or mobility management purposes. It may be useful that the measurement requirements can be adapted to, for example, mitigate 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, if / when the WTRU wakes up after a long DRX period (e.g., especially if the DRX period is relatively longer than the CSI-RS periodicity) (e.g., if there is no requirement for beam maintenance measurements during the DRX sleep period). Radio link monitoring based on CSI-RS that overlaps with the DRX on period may result in increased power consumption (e.g., if / when the DRX period is shortened to ensure that the radio link is maintained) or a higher probability of link loss (e.g., if / when the DRX period is too large for the WTRU to maintain the beam without waking up), which may present a trade-off between power consumption and level of radio link maintenance.

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

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

[0082] The WTRU may maintain a beam management process, e.g., to determine which beam IDs to consider as candidates for maintaining, activating, deactivating, and / or activating, among other operations. 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 beam states. (E.g., each) beam may have, for example, at least one of: (i) an active and / or 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 and / or maintained state. The WTRU may monitor the associated PDCCH resources or search space. The WTRU may, for example, activate a beam by semi-static configuration (e.g., default active beam) (e.g., after receiving activation signaling) or after measuring a channel state quantity for the associated measurement resource 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 a deactivated beam. The WTRU may deactivate a beam, for example, after receiving deactivation signaling, after declaring a beam failure, and / or after measuring a channel state quantity for the associated measurement resource below a configured threshold.

[0085] A beam in candidate state may (e.g., also) be an inactive beam. A beam ID may be a candidate if, for example, it is configured by higher layer signaling or determined by the WTRU (e.g., based on channel condition measurements of the associated CSI-RS / SSB). The WTRU may, for example, measure the associated CSI-RS or SSB as part of a BFR (e.g., for beam reselection) for the candidate beam.

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

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

[0088] Beam configurations and characteristics may be provided. Beam shaping and / or patterns may be provided.

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

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

[0091] A beam may be characterized by a beamwidth and / or a beam-directing factor. For example, a WTRU may be configured to associate a beam with a "width." A beamwidth may correspond to a set of beam parameter(s). For example, a beamwidth may correspond to one or more weighting patterns. A beamwidth may correspond to a particular spatial filter.

[0092] A beam may be characterized by a beam type, for example, a beam may be omnidirectional or directional, which may be considered a special case of a beamwidth characteristic.

[0093] A beam may be characterized by a beam reference signal, e.g., a synchronization signal block (SSB) and / or a channel state information reference signal (CSI-RS), e.g., for purposes of DL beam quality measurement, beam failure detection, and / or beam identification.

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

[0095] There may be beam-related requirements for higher frequencies. For example, a WTRU implementation may meet one or more (e.g., as described above) beam characteristic requirements, which may be test aspects of the WTRU implementation. In an example, the tests may include expected patterns of radiation, spectral leakage of the radiation pattern, etc. Different WTRU implementations may be adapted, for example, to particular (e.g., determined, selected, configured) sensitivity levels, spectral emission patterns, etc. The WTRU adaptation may support different beams that meet particular requirements.

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

[0097] The WTRU may be configured for beam-related requirements for higher frequencies. The WTRU may be configured with multiple beams. For example, the WTRU may be configured with beam ID=0 (e.g., for an omni-directional beam) and beam ID !=0 (e.g., for a directional beam). The WTRU may (e.g., further) be configured with one or more directional beams. For example, the WTRU may be configured with beam ID=1 (e.g., associated with a first beam width x=1), beam ID=2 (e.g., associated with a second beam width x=2), etc. (e.g., up to a 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, for example, such that a (e.g., one) reference signal configuration may be assigned multiple beamwidths. A beam reference signal configuration may be associated with multiple beamwidth indices, where (e.g., each) index may correspond to (e.g., at most) one beamwidth. The beam (e.g., in such a scenario) may be defined, for example, based on the reference signal configuration of the beam, and the control thereof may be associated with a change in the beam width index, which may correspond, for example, to the beam ID.

[0099] The 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 a PDCCH). The control signaling may include an index to a beam configuration for (i) receiving data (e.g., for a DL beam on a data channel such as a PDSCH), (ii) transmitting data (e.g., for a bidirectional beam on an uplink channel such as a PUSCH), and / or transmitting control information using the indicated beam configuration (e.g., for a bidirectional beam on an uplink control channel such as a PUCCH).

[0100] The WTRU may receive control signaling indicating (de)activation of a beam configuration, beam index, and / or associated beam width(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 MAC CE or DCI) or semi-static (e.g., received via RRC (re)configuration).

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

[0102] The reference signal (RS) configuration may depend on a beam index. For example, a WTRU may be configured with one or more indices (e.g., representing a beam and / or beam width) that may be associated with a reference signal configuration (e.g., each of which may be associated with a reference signal configuration). 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, for example, control the allocation of resources for reference signals for beam management and / or the determination of beam parameters (e.g., applicable beam width for uplink transmission of a bidirectional beam) by controlling the beam index (e.g., using the index in DCI on a control channel). The WTRU may (and may be expected to) perform RS-related measurements within the resources.

[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 on 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 a measurement value on the corresponding resource exceeds a threshold. The WTRU may select an index applicable to a subsequent transmission and determine applicable beam parameters according to the index, e.g., beam width. The gNB may control beam assignment and / or beam parameter determination (e.g., applicable beam width for uplink transmission of a bidirectional beam), for example, by controlling transmission of a WTRU-specific reference signal for beam management.

[0104] The measurements may be in response to discontinuous reception (DRX). The network (NW) may configure the WTRU, for example, so that measurement occasions for beam management (e.g., BFD) are aligned (e.g., as aligned as possible) with the WTRU's power saving mechanism (e.g., if configured).

[0105] Network configuration may provide alignment between DRX and BFD. For example, a WTRU may receive a DRX configuration that causes measurement occasions for beam management (e.g., BFD) to coincide or align in time (e.g., mostly) with the WTRU's resulting DRX active time. This opportunity alignment may coincide with the DRX on period portion of the DRX active time.

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

[0107] The network configuration may provide WTRU-configurable RS for beam management and DRX coordination. The WTRU may be configured with WTRU-specific reference signals for beam management (e.g., SSB, CSI-RS). The WTRU may receive a configuration, for example, where the periodicities of the RS and DRX cycles are similar and / or integer multiples of each other.

[0108] The network configuration may provide WTRU-configurable RS for beam management and DRX control. The WTRU may determine measurement occasions for beam management, for example, depending on 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 occasions. The WTRU may be configured to determine the measurement occasion and / or timing of the measurement occasion (e.g., for beam management) according to at least one of, for example, (i) DRX on period, (ii) DRX inactivity timer, (iii) DRX cycle period (e.g., short, long), (iv) DRX configuration, (v) DRX active time, (vi) wake up signal (WUS) occasion, (vii) wake up signal (WUS), (viii) channel conditions (e.g., RSRP, SINR, RSSI, power headroom, CO, and / or CQI), (ix) rate or level of channel variation (e.g., in terms of fast fading), (x) state of beams in the maintained set of beams, (xi) downlink reception, (xii) uplink reception, (xiii) change in bandwidth part (BWP), and / or (xiv) change in search space set (e.g., from reception of DCI format 2_0).

[0109] The WTRU may be configured to determine the measurement occasions and / or timing of the measurement occasions, for example, based on the 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 time (e.g., and / or frequency) of the RS measurement occasions 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 WTRU-specific pattern and / or an indication to apply a mask function, for example, to a system-specific set of RS occasions. The WTRU may determine (e.g., similarly) that the second set of RS measurements are applicable outside of the on period if (e.g., only if) (i) the WTRU is within a DRX active time and / or (ii) the WTRU is configured to apply a mask function.

[0110] FIG. 2 shows an example of beam management detection of a beam failure case with measurement occasions during on-periods associated with a DRX cycle. As shown by the example of FIG. 2, the DRX cycle may be a long DRX cycle. The WTRU may be configured to detect a beam failure (e.g., BFD) based on detection of a threshold number of BFIs. In FIG. 2, BFIs are indicated by an X, and the absence of BFIs is indicated by a check mark. BFIs 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 failure (e.g., BFD) based, for example, on a threshold of more than six (6) BFIs or BFIs equal to seven (7) BFIs (e.g., as shown by the example of FIG. 2). The measurement occasions for detecting a BFI, or lack thereof, may occur during on-periods in the long DRX cycle. Counts of BFIs detected (e.g., by a BFI counter) during the on-periods of the long DRX cycle are shown as 0, 1, 2, and 3 in FIG. 2. BFIs that occur outside of the on-period may not be detected or counted by the BFI counter. As shown to detect beam faults, counting seven (7) BFIs during an on-period may take a long time.

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

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

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

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

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

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

[0117] The WTRU may be configured to determine the measurement occasion and / or the timing of the measurement occasion based on, for example, one or more channel conditions (e.g., RSRP, SINR, RSSI, power headroom, CO, and / or CQI). The WTRU may determine that a first set of RS measurement occasions may be applicable, or (e.g., more generally) may (de)activate a given RS measurement pattern, for example, if (i) the measured channel condition(s) (e.g., RSRP, SINR, RSSI, PH, CO, and / or CQI) or (ii) the 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 configured range for the applicable set.

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

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

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

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

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

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

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

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

[0126] The WTRU may perform measurements at measurement occasions (eg, determined as described herein) for, eg, beam failure detection (BFD) purposes.

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

[0128] In an RS measurement occasion implementation, the WTRU may be configured with multiple CSI measurement resources (e.g., with different periodicities). The WTRU may assume that the existing CSI measurement resources correspond to the currently applicable set, thereby assuming that a given set is applicable, e.g., if a condition is met.

[0129] A set of RS measurement occasions may be defined by, for example, (i) an index or identification of the set, (ii) a time-domain offset (e.g., a starting offset from a slot boundary), (iii) a periodicity (e.g., in slots, symbols, or absolute time), and (iv) a frequency-domain granularity (e.g., every physical resource block (PRB), every other PRB, etc.) at which CSI measurements may be (e.g., are) taken. (x) associated WUS(s) or WUS occasion applicability; (xi) inactivity timer(s) (e.g., in slot, symbol, or absolute time); (xii) whether a set of RS opportunities applies or can be applied for BFD; and / or (xiii) whether the set can be used as a default configuration.

[0130] In an embodiment, a set of RS measurement occasions may be applied as a mask to a set of resources used for CSI measurements, and the WTRU may, for example, assume / determine that a resource exists if (e.g., only if) it overlaps in time with a time pattern corresponding to the set of RS measurement occasions.

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

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

[0133] The CSI reporting configuration may (e.g., alternatively) comprise / include at least one set of RS measurement occasions (e.g., including a default set). The (e.g., each) set of RS measurement occasions may include one set of resources for channel measurements and multiple sets of resources for interference measurements (e.g., CSI-IM and / or NZPCSI-RS). The WTRU may utilize resources (e.g., for each CSI reporting configuration) corresponding to an index that identifies the set of RS measurement occasions, 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, for example, change the state of a subset of beam states, (de)activate associated CSI-RS or SSBs, and / or suspend / resume associated BFD measurements and procedures depending on the DRX state and / or active DRX configuration. The WTRU may, for example, (de)activate specific beams and associated CSI-RS depending on the DRX state and / or based on whether a specific DRX timer is running. The WTRU may, for example, (de)activate one or more (e.g., specific) beams and / or associated CSI-RS during DRX inactivity time. The WTRU may activate or deactivate one or more (e.g., particular) beams and / or associated CSI-RS, for example, (i) while the DRX inactivity timer is running, (ii) while the WTRU is in 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) during the period from the WUS occasion (e.g., including the WUS occasion) to the on period (e.g., or the end of the on period), and / or (ix) after meeting any of the triggers (e.g., as described herein). In an embodiment, the WTRU may measure the CSI-RS associated with the BFD, for example, even when the WTRU is inactive or during a DRX off period.

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

[0136] Beam management may affect DRX. The WTRU may transition to a different DRX cycle and / or DRX configuration, suspend / resume DRX functionality, and / or (re)start or stop certain DRX timers, for example, in response to detection of beam failure, detection of loss of beam(s), and / or related measurements. The WTRU may turn off or suspend DRX, transition to a different DRX cycle (e.g., short DRX), and / or (re)start a DRX inactivity timer, for example, based on detection of beam failure (e.g., upon detection), measurement of loss of beam(s), and / or measurement of a channel condition amount below a threshold for the set of maintained beams. The WTRU may (re)start a DRX retransmission timer or a DRX HARQ RTT timer, for example, after measuring loss of beam(s) or after measuring a channel condition amount below a threshold for the set of maintained beams.

[0137] The WTRU may transition to a different DRX cycle and / or DRX configuration, pause / resume DRX functionality, and / or start a specific DRX timer, for example, after receiving (or lack of receiving) network signaling associated with an active beam in the maintained set of beams. The WTRU may transition to a different DRX cycle and / or DRX configuration, pause / resume DRX functionality, and / or start a specific DRX timer, for example, after measuring CSI-RS on a specific set of RS measurement occasions (e.g., below or above a threshold), after receiving an aperiodic CSI-RS request, and / or after receiving dynamic signaling associated with a set of RS measurement occasions.

[0138] Beam re-establishment (e.g., after DRX sleep) may affect BFR. The WTRU may, for example, measure the configured active CSI-RS during the DRX beam observation period. The DRX beam observation period may, for example, be the 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 the configured active CSI-RS during the DRX beam observation period, for example, conditioned on receiving a WUS signaling wake-up before the on period and / or expiration of the inactivity timer. The WTRU may measure the CSI-RS and / or SSB associated with the set of maintained beams. The WTRU may (e.g., additionally) measure the CSI-RS and / or SSB associated with the set of candidate beams, for example, conditioned on the lack of a satisfactory beam (e.g., meeting a configured channel condition measurement threshold) in the set of maintained beams.

[0139] The WTRU may (i) trigger a BFR (e.g., a new BFR) or beam re-establishment procedure, for example, if the WTRU does not have a satisfactory beam (e.g., meeting a configured channel condition measurement threshold) in the set of maintained beams during the DRX beam observation period, or (ii) transition (e.g., further) to active time or switch to a DRX cycle. The WTRU may (e.g., further) coordinate triggering a BFR based, for example, on having at least one beam with satisfactory measurements in the set of candidate beams. The WTRU (e.g., during the BFR procedure) may perform, for example, at least one of the following actions: (i) follow a conventional BFR procedure (e.g., as described herein), (ii) transition to active time, (iii) report preferred beam ID(s) on a different serving cell (e.g., using a BFR MAC CE or PUCCH), and / or (iv) transmit an SRS associated with the preferred beam(s). The WTRU may monitor one or more (e.g., specific) PDCCH resources (e.g., a subset of 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 the beam re-establishment or BFR procedure successful, for example, based on (e.g., upon) receiving a response on the downlink. The response may be tailored to receive the PDCCH resources associated with the indicated preferred beam(s).

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

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

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

[0143] The WTRU may switch between DRX states (e.g., between a long DRX and a short DRX cycle) based on, for example, detected beam failure instance(s). For example, the time to detect a connectivity 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 in one or more messages) indicating a short DRX cycle, a long DRX cycle, and / or CSI-RS measurements (e.g., to determine the BFI). The WTRU may determine a first number of beam failure instance(s) (BFI), e.g., based on one or more CSI-RS measurements during one or more "on" periods or active times of the long DRX cycle, using a BFI counter value as an example herein. The BFI counter may count BFIs detected during CSI-RS measurements, for example, 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 suspend 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(s), for example, during one or more "on" periods associated with the short DRX cycle. The WTRU may update the first BFI counter value to a second BFI counter value, for example, based on the measurements. The WTRU may switch to a long DRX cycle or resume using a long DRX cycle for CSI-RS measurements associated with BFD, for example, based on the condition that the second BFI counter value is less than a second threshold. The WTRU may initiate beam failure recovery and / or suspend DRX or reset an inactivity timer associated with DRX, for example, on condition that the second BFI counter exceeds a third threshold (which may, for example, indicate detection of a beam failure).

[0144] 3 shows an example of detecting beam failure cases at measurement occasions with different periodicities associated with DRX on periods in multiple DRX cycles with different durations. As shown by the example of FIG. 3, the variable DRX cycles may include a first (e.g., long) DRX cycle and a second (e.g., short) DRX cycle. The WTRU may be configured to detect beam failure (e.g., BFD) based on a threshold number of BFIs. As shown in FIG. 3, a BFI is indicated by an X, and the absence of a BFI is indicated by a check mark. The number of detected BFIs may be tracked or counted, for example, using a BFI counter (e.g., as shown in FIG. 3). BFIs may be determined / detected, and the BFI counter may be incremented based on channel condition status determined, for example, from CSI-RS measurements. As shown by the example of FIG. 3, the WTRU may be configured to detect or trigger beam failure based on a threshold of more than six BFIs or seven (7) or more BFIs. Measurement occasions for detecting BFIs, or the absence thereof, may occur during on periods in the long DRX cycle and during on periods in the short DRX cycle. The number of BFIs detected (e.g., tracked via a BFI counter) during the on periods of the long and short DRX cycles are shown as 0, 1, 2, 3, 4, 5, 6, and 7 in FIG. 3. A BFI occurring outside the on period during the first long DRX cycle may not be detected or counted by the BFI counter. A WTRU configured as shown in FIG. 3 may detect a beam failure and enter a BFR faster than a WTRU configured to stay in a long DRX cycle (eg, as shown by the example of FIG. 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 at zero (0) if no BFI is detected during the on period of the long DRX cycle (e.g., as indicated by a check mark "0" in FIG. 3). The WTRU may increment the BFI counter to one (1), for example, based on the detection of a first BFI during the on period of the long DRX cycle (e.g., as indicated by an X at "1" in FIG. 3). The WTRU may increment the BFI counter to two (2), for example, based on the detection of a second BFI during the on period of the long DRX cycle (e.g., as indicated by an X at "2" in FIG. 3).

[0146] The WTRU may switch to a second (e.g., short) DRX cycle, for example, based on a determined number of beam failure cases (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), for example, based on a switching threshold number of BFIs (e.g., counted by a BFI counter). As shown by the example of FIG. 3, the WTRU may be configured to switch from the long DRX cycle to the short DRX cycle if / when the BFI counter value is greater than one (1) BFI. For example, the WTRU may switch from the long DRX cycle to the short DRX cycle if / when the BFI counter value is two (2) (e.g., as shown in FIG. 3).

[0147] The WTRU may perform CSI-RS measurements during an on period associated with a second (e.g., short) DRX cycle. The measurement rate and / or measurement occasions for detecting BFIs may increase by switching to a short DRX cycle; for example, this may allow 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 cases based on additional CSI-RS measurement(s). For example, (e.g., as shown in FIG. 3), a BFI counter may be incremented to three (3) based on the detection of a third BFI (e.g., as shown by the X at the "3" in FIG. 3) during the on period of the first short DRX cycle. Measurement(s) of the 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 cases based on the CSI-RS measurement(s). For example, (e.g., as shown in FIG. 3), the BFI counter may update the BFI count to 4, 5, 6, and 7 (e.g., at "4," "5," "6," and "7," respectively) in association with the on-period of a short DRX cycle.

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

[0149] The WTRU may switch (e.g., switch back) from the second (e.g., short) DRX cycle to the first (e.g., long) DRX cycle, e.g., if / when (e.g., conditional on) the number of beam failure instances associated with the second DRX cycle is less than a second threshold, 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 the second (e.g., short) DRX cycle to the first (e.g., long) DRX cycle if / when the BFI counter is less than seven (7) BFIs (e.g., 6 or less) after a configured number of cycles of the second (e.g., short) cycle.

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

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

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

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

[0154] A first set of PDCCH search spaces may be monitored during active time, and a second set of PDCCH search spaces may be monitored during 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., when the BFI counter is less than a maximum), (ii) the second set of PDCCH search spaces may include beam recovery search space (e.g., when the BFI counter has reached a maximum count), and / or (iii) the second set of PDCCH search space may include beam recovery search space (e.g., when a new candidate beam is indicated and the WTRU has not received a confirmation from the gNB).

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

[0156] The WTRU may (i) suspend DRX, (ii) ignore DRX operation, or (iii) consider itself within the active time and operate as non-DRX operation, e.g., if the BFI counter is higher than a threshold. The WTRU may resume DRX operation, e.g., if the BFI counter is reset (e.g., if the measured beam failure detection resource is higher than a threshold Qin,LR). One or more of the following may apply: (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 BFI number for BF declaration; and / or (ii) the WTRU may operate as non-DRX operation (e.g., if the BFI counter is equal to or greater than a threshold), e.g., until the WTRU receives confirmation of a new candidate beam indicated to the gNB. The confirmation of a new candidate beam may be activation of a TCI state via higher layer configuration or an explicit indication in the DCI using the C-RNTI or MCS-C-RNTI (e.g., over the recovery search space).

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

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

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

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

[0161] The measurement threshold may depend on the beam management. The WTRU may be configured with measurement configurations that may be specific to beam characteristics (e.g., beam type, beam width, beam ID, etc.). For example, the WTRU may perform (e.g., specific) link and / or connectivity management procedures depending on the (e.g., specific) beam configuration. The WTRU may be configured with a default beam and, e.g., use the associated configuration when no other beam is selected (e.g., for scheduled transmission(s)). The WTRU may use the default, e.g., when / if the time alignment timer (TAT) is not running, when / if the WTRU is within a DRX inactive time, and / or under a period of scheduling activity for limited unicast transmissions (e.g., if any). The measurement configurations may include, e.g., 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 may be beam-specific. For example, the WTRU may be configured with a beam-specific, beam index-specific, beam ID-specific, and / or beam type-specific DRX configuration. The WTRU may determine the applicable DRX configuration, for example, depending on the beam used to receive the PDCCH control channel for a given cell. The WTRU may determine the applicable DRX configuration, for example, when the beam is initially established.

[0163] Power-efficient measurements are described for radio frequency operation. A wireless transmit / receive unit (WTRU) may determine measurement occasions depending on scheduling activity and beam configuration. The WTRU may determine measurement occasions for beam failure detection (BFD), radio link monitoring (RLM), and / or mobility depending on discontinuous reception (DRX) and / or BFD configuration. The WTRU may determine that a first set of reference signal (RS) measurement occasions is applicable based on a first condition (e.g., if / when a DRX / BFD / channel state information (CSI) condition is met) and that a second set of RS measurement occasions is applicable based on a second condition (e.g., if / when a DRX / BFD / CSI condition is not met). The WTRU may be configured with multiple sets of CSI-RS measurement occasions (e.g., with different periodicities). The WTRU may assume that a given set is applicable, for example, if a DRX / BFD / CSI condition is met. The WTRU may decide on DRX or non-DRX operation, for example, based on whether a BFI counter is below a threshold or above a threshold. The WTRU may reset the inactivity timer, for example, based on one or more BFD conditions (e.g., beam failure instance (BFI) counter > threshold and no BFD resources before the inactivity timer expires). The WTRU may pause, disable, or (re)start a BFD timer, for example, upon an inactivity time. The WTRU may change the beam state, (de)activate the associated CSI-RS, and / or suspend / resume the associated BFD, for example, depending on the DRX state / configuration or related signaling. The WTRU may transition to a different DRX cycle / configuration, suspend / resume DRX functionality, and / or (re)start / stop one or more DRX timers, for example, depending on the detection of a beam failure, loss of beam(s), or related measurements. The WTRU may trigger a BFR / beam re-establishment procedure (eg, a new BFR / beam re-establishment procedure), for example, if the WTRU does not have a satisfactory beam during a DRX beam observation period.

[0164] Although the above-described features and elements are described in particular 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 the other features and elements.

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

[0166] The processes described above may be implemented in a computer program, software, and / or firmware embodied 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 over wired and / or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer. [Explanation of symbols]

[0167] 100 Communication Systems 102a WTRU 102b WTRU 102c WTRU 102d WTRU 110 Internet 112 Network 114a base station 114b base station 116 Air Interface 118 processors 120 Transceiver 122 receiving elements 124 microphones 126 keypad 128 Touchpad 130 Non-removable Memory 132 Removable Memory 134 Power supply 136 GPS chipset 138 Peripherals

Claims

1. 1. A wireless transmit / receive unit (WTRU), comprising: receiving measurement configuration information, the measurement configuration information indicating one or more criteria for determining a measurement period associated with one or more reference signal (RS) measurements; performing one or more RS measurements; determining a measurement period for one or more subsequent RS measurements based on the one or more RS measurements and the one or more criteria indicated in the measurement configuration information; receiving configuration information indicating a power saving pattern; receiving downlink control information (DCI), the DCI including an instruction to activate the received power saving pattern; determining one or more RS transmissions that overlap with at least one active period of the power saving pattern activated by the DCI; performing at least one RS measurement for the one or more RS transmissions that overlap with at least one active period of the power saving pattern activated by the DCI; transmitting a channel state information (CSI) report based on the at least one RS measurement for the one or more RS transmissions during the at least one active period of the power saving pattern activated by the DCI.

12. A WTRU comprising: a processor configured to:

2. 10. The WTRU of claim 1, further configured to transmit a physical random access channel (PRACH) preamble based on the one or more subsequent measurements performed according to the determined measurement period.

3. 2. The WTRU of claim 1, wherein the one or more criteria include either the one or more RS measurements exceeding a first set threshold or a change in the one or more RS measurements from a previous RS measurement being less than a second set threshold.

4. 2. The WTRU of claim 1, wherein the determined measurement period associated with the one or more subsequent measurements is longer when one or more criteria are met based on the one or more RS measurements than when the one or more criteria are not met.

5. 5. The WTRU of claim 4, wherein the determined measurement period for the one or more subsequent measurements is associated with one or more of beam failure detection (BFD), beam failure recovery (BFR), or radio link monitoring (RLM).

6. 6. The WTRU of claim 5, wherein the at least one of the one or more RS measurements indicates that the WTRU is in a low mobility state or indicates that a serving cell radio link quality is greater than an associated criterion of the one or more criteria.

7. The WTRU of claim 1 , wherein the at least one of the one or more RS measurements is a reference signal received power (RSRP) measurement.

8. 1. A method for use in a wireless transmit / receive unit (WTRU), comprising: receiving measurement configuration information from a network, the measurement configuration information indicating one or more criteria for determining a measurement period associated with one or more Reference Signal (RS) measurements; performing one or more RS measurements; determining a measurement period for one or more subsequent RS measurements based on the one or more RS measurements and the one or more criteria indicated in the measurement configuration information; receiving configuration information indicative of a power saving pattern; receiving downlink control information (DCI), the DCI including an instruction to activate the received power saving pattern; determining one or more RS transmissions that overlap with at least one active period of the power saving pattern activated by the DCI; performing at least one RS measurement for the one or more RS transmissions that overlap with at least one active period of the power saving pattern activated by the DCI; transmitting a channel state information report based on the at least one RS measurement for the one or more RS transmissions during the at least one active period of the power saving pattern activated by the DCI; A method comprising:

9. 10. The method of claim 8, further comprising: transmitting a Physical Random Access Channel (PRACH) preamble based on the one or more subsequent measurements performed according to the determined measurement period.

10. 9. The method of claim 8, wherein the one or more criteria include either the one or more RS measurements exceeding a first set threshold or a change in the one or more RS measurements from a previous RS measurement being less than a second set threshold.

11. 9. The method of claim 8, wherein the determined measurement period associated with the one or more subsequent measurements is longer when one or more criteria are met based on the one or more RS measurements than when the one or more criteria are not met.

12. 12. The method of claim 11 , wherein the determined measurement period for the one or more subsequent measurements is associated with one or more of beam failure detection (BFD), beam failure recovery (BFR), or radio link monitoring (RLM).

13. 13. The method of claim 12, wherein the at least one of the one or more RS measurements indicates that the WTRU is in a low mobility state or that a serving cell radio link quality is greater than an associated criterion of the one or more criteria.

14. The method of claim 8 , wherein the at least one of the one or more RS measurements is a reference signal received power (RSRP) measurement.

15. 2. The WTRU of claim 1, wherein the processor is further configured to determine not to perform the at least one RS measurement for one or more RS transmissions that do not overlap with at least one active period of the power saving pattern activated by the DCI.

16. 2. The WTRU of claim 1, wherein the processor is further configured to: determine not to transmit a CSI report based on the at least one RS measurement for one or more RS transmissions scheduled outside at least one active period of the power saving pattern activated by the DCI.

17. The WTRU of claim 1 , wherein the received DCI is included in a physical downlink control channel (PDCCH).

18. The WTRU of claim 17 , wherein the power saving pattern is a mask function and is included in the PDCCH.

19. 9. The method of claim 8, further comprising: determining not to perform the at least one RS measurement for one or more RS transmissions that do not overlap with at least one active period of the power saving pattern activated by the DCI.

20. 9. The method of claim 8, further comprising: determining not to transmit a CSI report based on the at least one RS measurement for one or more RS transmissions scheduled outside at least one active period of the power saving pattern activated by the DCI.

21. The method of claim 8 , wherein the received DCI is included in a physical downlink control channel (PDCCH).

22. The method of claim 21 , wherein the power saving pattern is a mask function and is included in the PDCCH.

23. The WTRU of claim 1 , wherein the processor is further configured to receive a second DCI, the second DCI including an instruction to deactivate the received power saving pattern.

24. 10. The method of claim 8, further comprising: receiving a second DCI, the second DCI comprising an instruction to deactivate the received power saving pattern.

25. 1. A wireless transmit / receive unit (WTRU), comprising: receiving configuration information indicating a power saving pattern; receiving downlink control information (DCI), the DCI including an instruction to activate the received power saving pattern; determining one or more RS transmissions that overlap with at least one active period of the power saving pattern activated by the DCI; performing at least one RS measurement for the one or more RS transmissions that overlap with at least one active period of the power saving pattern activated by the DCI; transmitting a channel state information (CSI) report based on the at least one RS measurement for the one or more RS transmissions during the at least one active period of the power saving pattern activated by the DCI.

12. A WTRU comprising: a processor configured to:

26. 26. The WTRU of claim 25, wherein the at least one of the one or more RS measurements is a reference signal received power (RSRP) measurement.

27. 26. The WTRU of claim 25, wherein the processor is further configured to determine not to perform the at least one RS measurement for one or more RS transmissions that do not overlap with at least one active period of the power saving pattern activated by the DCI.

28. 26. The WTRU of claim 25, wherein the processor is further configured to determine not to transmit a CSI report based on the at least one RS measurement for one or more RS transmissions scheduled outside at least one active period of the power saving pattern activated by the DCI.

29. 26. The WTRU of claim 25, wherein the received DCI is included in a physical downlink control channel (PDCCH).

30. 26. The WTRU of claim 25, wherein the processor is further configured to receive a second DCI comprising an instruction to deactivate the received power saving pattern.

Images