WO2021163404A1 - Power efficient measurements at higher frequencies - Google Patents
Power efficient measurements at higher frequencies Download PDFInfo
- Publication number
- WO2021163404A1 WO2021163404A1 PCT/US2021/017756 US2021017756W WO2021163404A1 WO 2021163404 A1 WO2021163404 A1 WO 2021163404A1 US 2021017756 W US2021017756 W US 2021017756W WO 2021163404 A1 WO2021163404 A1 WO 2021163404A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- wtru
- drx
- measurement
- csi
- drx cycle
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/309—Measuring or estimating channel quality parameters
- H04B17/318—Received signal strength
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- methods may be implemented for power efficient measurements for high frequency operations.
- Methods may be implemented (e.g., in whole or in part), for example, by device(s) (e.g., a WTRU, a network node such as a gNodeB (gNB), and/or the like) and/or system(s) that are configured to implement the methods, e.g., having one or more processors configured to execute the methods (e.g., in whole or in part) as computer executable instructions that may be stored on a computer readable medium or a computer program product.
- the computer readable medium or the computer program product may comprise instructions that cause one or more processors to perform the methods by executing the instructions.
- a beam failure instance may be associated with a channel condition state determination.
- a timing associated with at least one of the first CSI-RS measurement or the second CSI-RS measurement may be indicated to the WTRU by a network device.
- the first DRX cycle may be a long DRX cycle and the second DRX cycle may be a short DRX cycle.
- the WTRU may be (e.g., further) configured to switch from the second DRX cycle to the first DRX cycle, for example, on a condition that the second number of beam failure instances is less than a second threshold.
- the WTRU may be (e.g., further) configured to receive configuration information that indicates the first DRX cycle and the second DRX cycle.
- the WTRU may be (e.g., further) configured to determine a timing associated with at least one of the first CSI-RS measurement or the second CSI-RS measurement.
- FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
- FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment; and
- RAN radio access network
- CN core network
- FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
- FIG. 3 illustrates an example of detecting beam failure instances at measurement opportunities with different periodicities during DRX on durations in multiple DRX cycles with different durations.
- a WTRU may be configured with multiple sets of CSI-RS measurement opportunities (e.g., with different periodicities).
- a WTRU may assume a given set is applicable, for example, if a DRX/BFD/CSI condition is met.
- a WTRU may determine DRX operation or non-DRX operation, for example, based on whether a BFI counter is or is not less than a threshold.
- a WTRU may reset an inactivity timer, for example, based on one or more BFD statuses (e.g., beam failure instance (BFI) counter > threshold and no BFD resource before inactivity timer expiry).
- BFI beam failure instance
- a WTRU may pause, disable, or (re)-start the BFD timer, for example, upon going into inactive time.
- a WTRU may trigger a BFR/beam reestablishment procedure (e.g., a new BFR/beam reestablishment procedure), for example, if the WTRU does not have a satisfactory beam during a DRX-beam observation period.
- a BFR/beam reestablishment procedure e.g., a new BFR/beam reestablishment procedure
- the communications systems 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), and the like.
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal FDMA
- SC-FDMA single-carrier FDMA
- ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
- UW-OFDM unique word OFDM
- FBMC filter bank multicarrier
- the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
- WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
- the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
- UE user equipment
- PDA personal digital assistant
- HMD head-mounted display
- a vehicle a drone
- the communications systems 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 communication networks, such as the CN 106/115, the Internet 110, and/or the other networks 112.
- the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
- the cell associated with the base station 114a may be divided into three sectors.
- the base station 114a may include three transceivers, i.e., one for each sector of the cell.
- the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
- MIMO multiple-input multiple output
- beamforming may be used to transmit and/or receive signals in desired spatial directions.
- the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an 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).
- RAT radio access technology
- 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, and the like.
- the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c 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 communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
- HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
- 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-A Pro).
- E-UTRA Evolved UMTS Terrestrial Radio Access
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- LTE-A Pro LTE-Advanced Pro
- the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
- NR New Radio
- the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
- the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
- DC dual connectivity
- the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
- the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
- IEEE 802.11 i.e., Wireless Fidelity (WiFi)
- IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
- CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
- IS-95 Interim Standard 95
- IS-856 Interim Standard 856
- GSM Global System for
- the base station 114b in FIG. 1 A may be a wireless router, Flome Node B, Flome eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
- 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).
- WLAN wireless local area network
- 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).
- the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE- A Pro, NR etc.) to establish a picocell or femtocell.
- a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE- A Pro, NR etc.
- the base station 114b may have a direct connection to the Internet 110.
- the base station 114b may not be required to access the Internet 110 via the CN 106/115.
- 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 the other networks 112.
- the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
- POTS plain old telephone service
- 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), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
- the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
- the networks 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.
- the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
- 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 appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
- the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
- the WTRU 102 may have multi-mode capabilities.
- the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.
- the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or 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.
- the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
- the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
- dry cell batteries e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.
- solar cells e.g., solar cells, fuel cells, and the like.
- the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
- location information e.g., longitude and latitude
- the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
- a base station e.g., base stations 114a, 114b
- the WTRU 102 may acquire location information by way of any suitable location- determination method while remaining consistent with an embodiment.
- 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.
- the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), 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, and the like.
- FM frequency modulated
- FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
- the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
- the RAN 104 may also be in communication with the CN 106.
- the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
- the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
- the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
- the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
- the CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
- MME mobility management entity
- SGW serving gateway
- PGW packet data network gateway
- the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
- the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
- the SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
- the CN 106 may facilitate communications with other networks.
- 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 land-line communications devices.
- the CN 106 may include, or may 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.
- IMS IP multimedia subsystem
- the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
- a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
- the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
- Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
- Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
- Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
- the AP may transmit a beacon on a fixed channel, such as a primary channel.
- the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
- the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
- Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
- the STAs e.g., every STA, including the AP, may sense the primary channel.
- High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
- Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
- the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11h, and 802.11ac.
- 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
- 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
- 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
- MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
- the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
- the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 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) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
- STAs e.g., MTC type devices
- NAV Network Allocation Vector
- the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
- FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
- the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
- the RAN 113 may also be in communication with the CN 115.
- the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
- the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
- the gNBs 180a, 180b, 180c may implement MIMO technology.
- gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
- the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
- the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
- the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
- the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
- WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
- CoMP Coordinated Multi-Point
- the WTRUs 102a, 102b, 102c may communicate with 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 gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
- TTIs subframe or transmission time intervals
- 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.
- WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
- WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
- WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
- WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
- 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.
- the CN 115 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
- SMF Session Management Function
- 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 serve as a control node.
- the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and 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.
- the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
- the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
- the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
- the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
- a PDU session type may be IP-based, non-IP based, Ethernet- based, and the like.
- the UPF 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 UPF 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, and the like.
- the CN 115 may facilitate communications with other networks.
- the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108.
- IMS IP multimedia subsystem
- the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
- the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
- DN local Data Network
- one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, 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.
- the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
- the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
- the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
- the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
- RF circuitry e.g., which may include one or more antennas
- 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 multiple beam pairs.
- a WTRU may monitor one or more periodic channel state information reference signals (CSI-RS) on a serving downlink (DL) beam, for example, to assess beam quality and compute a corresponding quality metric.
- CSI-RS channel state information reference signals
- a WTRU's physical layer (PHY) entity may report a beam failure instance (BFI) to the MAC sub-layer, for example, if the beam quality in a given RS period for (e.g. some and/or all) beams in the maintenance set is below a configured threshold.
- Lost beam pair(s) may be re-established faster than a radio link monitoring (RLM)/radio link failure (RLF) procedure.
- a WTRU may maintain a beam failure detection (BFD) procedure in which maintained beams are periodically measured.
- BFD beam failure detection
- 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 on the primary cell (Pcell) and/or secondary cell (Scell).
- BFD measurements may be taken, for example, at the max of ⁇ DRX period, CSI-RS period ⁇ , (e.g. in legacy systems), for example, if BFD and discontinuous reception (DRX) are configured.
- the MAC entity may maintain a beam failure instance (BFI) counter (BFI_counter) for beam failure detection (BFD).
- BFI beam failure instance
- 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), for example, if a BFI counter exceeds a threshold or maximum number of BFIs.
- the MAC entity may reset the BFI counter, for example, (e.g. only) after a beam failure detection timer (BFD imer) has expired, which may help provide hysteresis in the detection function.
- a WTRU may reset the BFD timer, for example, each time a BFI is indicated.
- the MAC entity may (e.g. only) reset the BFI counter, for example, after observing no BFI indications from a physical layer (PHY) for multiple (e.g. three) consecutive CSI-RS periods (e.g. based on the BFD timer configuration).
- PHY physical layer
- a WTRU may report a BFR request for a beam failure detected 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 (PRACFI) preamble and/or PRACH resource dependent on the best and/or better measured downlink beam (CSI-RS or DL synchronization signal block (SSB)).
- PRACFI physical random access channel
- the WTRU may reestablish a beam pair, for example, if the WTRU can determine an association between DL beams and UL preambles and/or PRACFI occasions.
- the downlink (DL) beam selected by the WTRU may be tested, for example, by receiving the random access response (RAR) on the DL beam.
- RAR random access response
- DRX may refer to any form of power saving applied by the WTRU characterized by reduced reception and/or transmission activity.
- DRX may be applicable to any WTRU state (e.g., connected, inactive, idle state, etc.).
- Connected mode DRX may specify a (e.g., minimum) physical downlink control channel (PDCCFI) decoding requirement, e.g., while the WTRU is configured with connected mode DRX.
- the WTRU may be (e.g. further) configured to monitor the PDCCFI during the on duration, for example, if the WTRU receives a wake-ups signal (WUS) prior to the on duration.
- WUS wake-ups signal
- Channel state information may include, for example, at least one of the following: channel quality index (CQI), rank indicator (Rl), precoding matrix index (PM I), an L1 channel measurement (e.g., reference signal received power (RSRP) such as L1-RSRP, or signal to interference and noise ratio (SINR)), CSI-RS resource indicator (CRI), synchronization signal (SS)/physical broadcast channel (PBCH) block resource indicator (SSBRI), layer indicator (LI), and/or any other measurement quantity measured by the WTRU from the configured CSI-RS or SS/PBCH block.
- CQI channel quality index
- Rl rank indicator
- PM I precoding matrix index
- L1 channel measurement e.g., reference signal received power (RSRP) such as L1-RSRP, or signal to interference and noise ratio (SINR)
- CSI-RS resource indicator CRI
- SS synchronization signal
- PBCH physical broadcast channel
- SSBRI synchronization signal block resource indicator
- LI layer indicator
- a WTRU may determine channel conditions from, for example, a WTRU measurement (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)), an RLM state, and/or channel availability in unlicensed spectrum (e.g., whether the channel is occupied based on determination of an listen-before-talk (LBT) procedure or whether the channel is deemed to have experienced a consistent LBT failure).
- a WTRU measurement e.g., L1/SINR/RSRP, CQI/modulation and coding scheme (MCS), channel occupancy (CO), received signal strength indicator (RSSI), power headroom, exposure headroom
- L3/mobility-based measurements e.g., RSRP, reference signal received quality (RSRQ)
- RLM state e.g.,
- Wireless transmissions may support operation in higher frequency bands. Transmissions on high frequency bands may experience a higher path loss, e.g., due to channel characteristics of those bands. Beam-based transmission may be beneficial in higher frequencies (e.g., to direct the power on one or more beams).
- Omni-directional transmissions may be used in higher frequency ranges, for example, to target short range transmissions, lower data rates or control information, and/or for WTRUs without established narrow beams.
- broadcast transmissions e.g., for sidelink
- Omni-directional link management may have different measurement requirements than directional beams, for example, for beam management, radio link monitoring, CSI reporting, and/or mobility management purposes. Measurement requirements may be adapted, for example, to mitigate the impact on battery usage of a WTRU may be useful (e.g. combined with beam management and higher frequencies).
- Beam management processes may not function properly (e.g., in the absence of requirements for beam maintenance measurement during DRX sleep periods), for example, if/when a WTRU wakes up after a long DRX period (e.g., especially if a DRX period is relatively longer than CSI-RS periodicity).
- Radio link monitoring based on CSI-RS overlapping with DRX on durations may result in increased power consumption (e.g., if/when the DRX period is reduced to ensure the radio link is maintained) or higher probability of link loss (e.g., if/when the DRX period is too large for the WTRU to maintain beams without waking up), which may present a tradeoff between power consumption and the level of radio link maintenance.
- Beam management may be provided. Beams (e.g. at higher frequencies) may be characterized, for example, based on beam identities and/or management processes.
- a beam may be associated with a beam identity (beam ID) or a beam index.
- a beam index may be unique to downlink (DL) and/or uplink (UL).
- DL downlink
- UL uplink
- a downlink beam may identify a downlink beam and an associated uplink beam.
- the association between uplink and downlink beams may be configured and/or implicitly determined, for example, based on the outcome of a beam management process and the associated UL and DL frequencies.
- a WTRU may maintain a beam management process, for example, to determine which beam IDs to maintain, activate, deactivate, and/or consider as a candidate for activation, among other actions.
- a beam management process may keep track of a list of maintained beams and a list of candidate beams.
- a beam management process may (e.g., further) carry actions related to BFD and BFR.
- a beam management process may (e.g., also) be used to change beam states.
- a (e.g., each) beam may have, for example, at least one of the following states: (i) active and/or maintained; (ii) de-active; (iii) candidate; (iv) initial state; and/or (v) adjusted state.
- a WTRU may measure associated CSI-RS or SSBs (e.g., part of BFD), for example, for a beam in an active and/or a maintained state.
- the WTRU may monitor associated PDCCFI resources or search spaces.
- the WTRU may activate a beam (e.g., after reception of activation signaling), for example, by semi-static configuration (e.g., a default active beam), or after measuring a channel state quantity for an associated measurement resource below a configured threshold.
- a WTRU may not measure associated CSI-RS or SSBs (e.g., part of BFD), for example, for a beam in a de-active state.
- the WTRU may de-activate a beam, for example, after reception of de activation signaling, after declaring a beam failure, and/or after measuring a channel state quantity for an associated measurement resource below a configured threshold.
- a beam in an initial state may be transmitted/received with default parameters (e.g., beamwidth, etc.).
- a beam in an adjusted state may be transmitted/received with modified parameters.
- a beam may be characterized, for example, by at least one of the following: (i) beam parameters; (ii) beam width or directivity index; (iii) beam type; (iv) beam reference signal; and/or (v) beam transmission configuration indicator (TCI) state(s).
- a beam may be characterized by beam parameters.
- Beam parameters may include one or more of the following: applied (e.g., spatial) filter, codebook(s), precoding table(s) and/or weight(s), RF phase shift(s), channel state information (CSI).
- Beam parameters may exist for a downlink beam, an uplink beam, or a bidirectional beam.
- a channel may be reciprocal (e.g., time division duplex (TDD)) or not reciprocal (e.g., frequency division duplex (FDD)), etc.
- a WTRU may be configured with a plurality of beams, for example, where each of multiple beams may be associated with a different set of parameter(s) (e.g., each with an assigned value or value range).
- a WTRU may be configured with a plurality of beams, where each beam may be associated with a specific (e.g., different) spatial filter.
- a beam may be characterized by beam width and/or a beam directivity index.
- a WTRU may be configured to associate a beam with a "width.”
- a beam width may correspond to a set of beam parameter(s).
- a beam width may correspond to one or more weighting patterns.
- a beam width may correspond to a specific spatial filter.
- a beam may be characterized by a beam type.
- a beam may be omnidirectional or directional, which may be considered a special case of beam width characterization.
- a WTRU implementation may meet requirements for one or more (e.g. foregoing) beam characteristics, which may be a testing aspect of the WTRU implementation.
- testing may include an expected pattern of radiation, spectral leakage of the radiation pattern, etc.
- Different WTRU implementations may conform, for example, to specific (e.g.., determined, selected, configured) sensitivity levels, spectral emission patterns, etc. WTRU conformity may support different beams meeting specific requirements.
- a WTRU may have capabilities for beam-related requirements for higher frequencies.
- a WTRU implementation may support one or more requirements to make available different beams with different interference characteristics and/or beam widths.
- a WTRU may report beam availability to the network, for example, as part of a WTRU capability exchange.
- a WTRU may be configured for beam-related requirements for higher frequencies.
- a WTRU may be configured with a plurality of beams.
- a WTRU may be (e.g., further) configured with one or more directional beams.
- a WTRU may be configured for beam width control.
- a WTRU may be configured with a reference signal (e.g., SSB, CSI-RS) configuration for a given beam.
- a WTRU may be configured, for example, such that a (e.g., one) reference signal configuration may be assigned a plurality of beam widths.
- a beam reference signal configuration may be associated with a plurality of beam width indices, e.g., where a (e.g., each) index may correspond to (e.g., at most) one beam width.
- a beam (e.g. in such a scenario) may be defined, for example, based on the beam's reference signal configuration, e.g., where control thereof may be associated with changes in the beam width index.
- a beam width index may correspond to, for example, a beam ID.
- Beam control may be provided (e.g. in downlink control information (DCI)).
- a WTRU may receive control signaling (e.g., on a first beam carrying the control channels, such as PDCCFI).
- Control signaling may include an index to a beam configuration for: (i) the reception of data (e.g., for a DL beam on a data channel such as PDSCH), (ii) the transmission of data (e.g., for a bi-directional beam on an uplink channel, such as PUSCH), (iii) and/or the transmission of control information (e.g., for a bi-directional beam on an uplink control channel, such as PUCCFI) using the indicated beam configuration.
- DCI downlink control information
- a WTRU may receive control signaling that indicates (de)-activation of a beam configuration, beam index, and/or associated beamwidth(s).
- a (de)-activation indication may be applicable to a specific direction (e.g., downlink), a specific channel (e.g., PDSCH, PDCCFI, PUSCH, PUCCFI, PRACH), and/or for a subset of transmission types (e.g., paging, UCI type, data type).
- Control signaling may be dynamic (e.g., received on a MAC CE or DCI) or semi-static (e.g., received by RRC (re)-configuration).
- Beam reference signals may be WTRU-specific.
- a WTRU may be configured with WTRU-specific reference signals (e.g., SSB, CSI-RS) for one or more beams of the WTRU's configuration, for example, in addition to any common beam configurations (e.g., SSBs) determined from broadcast signals and/or configurations.
- WTRU may receive a configuration, for example, using L3/RRC signaling.
- a reference signal (RS) configuration may be a function of a beam index.
- a WTRU may be configured with one or more indices (e.g. representing a beam and/or a beam width) that may (e.g. each) be associated with a reference signal configuration.
- a WTRU may determine the applicable resource allocation (e.g., in time and/or frequency) for a given index using the associated configuration.
- Measurements may be a function of Discontinuous Reception (DRX).
- a network may configure a WTRU, for example, so that measurement opportunities for beam management (e.g., for BFD) are aligned (e.g., as aligned as possible) with the WTRU's power savings mechanisms (e.g., if configured).
- a network configuration may provide alignment between DRX and BFD.
- a WTRU may receive a DRX configuration that causes measurement opportunities for beam management (e.g., for BFD) to (e.g. largely) coincide or align in time with the WTRU's resulting DRX active time. Alignment of the opportunities may coincide with the DRX on-duration part of the DRX active time.
- a network configuration may provide a WTRU-configurable masking function between DRX and BFD.
- a WTRU may be configured, for example, to perform beam-related measurements when in DRX active time (e.g., a masking function between DRX active time and measurement opportunities).
- a WTRU may determine to apply masking (e.g. only) based on the DRX on-duration period (e.g., the WTRU may not perform beam-related measurement outside the WTRU's DRX on-duration period).
- a masking function may be, for example, an L3/RRC configurable aspect of the WTRU.
- a network configuration may provide a WTRU-configurable RS for beam management and DRX alignment.
- a WTRU may be configured with WTRU-specific reference signals for beam management (e.g., SSB, CSI-RS).
- a WTRU may receive a configuration, for example, where the periodicities of the RS and DRX cycles are similar and/or an integer multiple of each other.
- a network configuration may provide a WTRU-configurable RS for beam management and DRX control.
- a WTRU may determine measurement opportunities for beam management, for example, as a function of DRX PDCCH monitoring occasions.
- the network may control DRX.
- PDCCH blind decoding occasions may be synchronized between the WTRU and the NW.
- a WTRU may be configured with one or more measurement configurations to measure channel conditions (e.g., based on CSI-RS and/or SSBs), such as a set of RS measurement opportunities.
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities (e.g., for beam management), for example, according to at least one of the following: (i) DRX on-duration; (ii) DRX inactivity timer; (iii) DRX cycle duration (e.g., short, long); (iv) DRX configuration; (v) DRX active time; (vi) wake up signal (WUS) occasions; (vii) wake up signal (WUS); (viii) channel conditions (e.g., RSRP, SINR, RSSI, power headroom, CO and/or CQI); (ix) speed or level of channel variation (e.g., in terms of fast fading); (x) status of beams in the maintained set of beams; (xi) downlink reception
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on a DRX inactivity timer.
- the WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, if the DRX inactivity timer is running, and a second set of RS measurement opportunities may be applicable, for example, otherwise.
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on a DRX Configuration: The WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, if/when the associated DRX configuration is used, and a second set of RS measurement opportunities may be applicable, for example, if/when otherwise.
- the WTRU may be configured with a plurality of DRX configurations.
- the WTRU may be configured with an association between a set of RS measurement opportunities and a DRX configuration (e.g., by RRC signaling).
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on WUS occasions.
- the WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, in periods where the WUS may be received (e.g., WUS occasions), and a second set of RS measurement opportunities may be applicable, for example, if/when otherwise.
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on one or more channel conditions (e.g., RSRP, SINR, RSSI, power headroom, CO and/or CQI).
- the WTRU may determine that a first set of RS measurement opportunities may be applicable, or may (e.g., more generally) (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 set to be applicable.
- the measured channel condition(s) e.g., RSRP, SINR, RSSI, PH, CO and/or CQI
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on status of beams in the maintained set of beams.
- the WTRU may determine loss of a maintained beam IDs, for example, due to blocking effects, corner effects, or based on associated measurements below a threshold.
- the WTRU may (de)-activate a set of RS measurement opportunities associated with the lost beams.
- the WTRU may (de)-activate a set of RS measurement opportunities associated with the candidate beams for beam realignment.
- the WTRU may monitor the set of RS measurement opportunities associated with (i) the active beams in the set of maintained beams and/or (ii) the configured set of candidate beams.
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on downlink reception.
- the WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, (i) after reception of downlink data or control signaling (e.g., on a subset of DL channels or resources), and/or (ii) upon receiving a dynamic indication (e.g., DCI or MAC control element (CE)) to apply the measurement pattern.
- a second set of RS measurement opportunities may be applicable, for example, otherwise.
- a first set of RS measurement opportunities may be applicable for a specific period (e.g., based on a configured inactivity timer).
- the first set of RS measurement opportunities may depend on a priority level associated with the downlink reception or its associated HARQ-ACK, such as a priority indication signaled from DCI or configured by higher layer.
- a priority level may correspond, for example, to one of a set of possible sets of RS measurement opportunities configured by higher layers.
- a priority indication may be obtained, for example, from an explicit field of the DCI, from RNTI, from the search space, or from the control resource set (CORESET) where the DCI is decoded.
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on uplink transmission.
- the WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, after transmission of uplink data or UCI (e.g., on a certain uplink resource or channels associated with the measurement pattern).
- a second set of RS measurement opportunities may be applicable, for example, otherwise.
- a first set of RS measurement opportunities may be applicable for a specific period (e.g., based on a configured inactivity timer).
- the first set of RS measurement opportunities may depend on a priority level associated with the uplink transmission, such as a priority indication signaled from DCI (e.g., for dynamically scheduled PUSCH) or configured by higher layer (e.g., for a scheduling request or a configured grant).
- a priority level associated with the uplink transmission such as a priority indication signaled from DCI (e.g., for dynamically scheduled PUSCH) or configured by higher layer (e.g., for a scheduling request or a configured grant).
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on a change (e.g., a switch) of bandwidth part (BWP).
- the WTRU may determine that a default set of RS measurement opportunities may be applicable, for example, upon a change of bandwidth part (e.g., by DCI or by timer expiry).
- a WTRU may be configured to determine measurement opportunities and/or timing of the measurement opportunities, for example, based on a change (e.g., a switch) of search space sets (e.g., from reception of DCI format 2_0).
- the WTRU may determine that a first set of RS measurement opportunities may be applicable, for example, for a first group index of a search space set, and that a second set of RS measurement opportunities may be applicable, for example, for a second group index of a search space set, and so on.
- a second set of RS measurement opportunities may have a longer period between each measurement (e.g., for more relaxed BFD activity) compared to the first set of RS measurement opportunities, or vice versa.
- a WTRU may perform behavior related to DRX, for example, (e.g. only) if the WUS is not configured.
- a WTRU may perform behavior related to WUS, for example, (e.g. only) if DRX is not configured.
- a WTRU may perform measurements in the measurement opportunities (e.g., determined as described herein), for example, for the purpose of beam failure detection (BFD).
- BFD beam failure detection
- a WTRU may (e.g. similarly) apply any logic described herein to measurements related to radio link monitoring (RLM), to measurements related to mobility, and/or to measurements related to CSI reporting.
- RLM radio link monitoring
- a WTRU may be configured with multiple CSI measurement resources (e.g., with different periodicities).
- a WTRU may assume that CSI measurement resources that are present correspond to the currently applicable set, whereby a given set is applicable, for example, if a condition is met.
- a set of RS measurement opportunities may be configured, for example, with at least one of the following: (i) an index or identity of the set, (ii) a time domain offset (e.g., a start offset from the slot boundary), (iii) a periodicity (e.g., in slots, symbols, or absolute time), (iv) a frequency domain granularity for which CSI measurements may be (e.g.
- CSI measurements are) measured (e.g., every physical resource block (PRB), every other PRB, etc.), (v) an associated frequency domain allocation for CSI measurements (e.g., BWP, carrier, subband), (vi) an associated uplink reporting resource or channel (e.g., a PUCCH or PUSCH reporting resource), (vii) associated CSI-RS(s)/CSI-RS resource set(s), (viii) associated DRX configurations or cycles, (ix) a list of associated beam identifiers (IDs) or beam types, (x) applicability to associated WUS(s) or WUS occasions, (xi) inactivity timer(s) (e.g., in slots, symbols, or absolute time), (xii) whether the set of RS opportunities is or may be applied for BFD, and/or (xiii) whether the set may be used as the default configuration.
- IDs associated beam identifiers
- inactivity timer(s) e.g., in slots, symbols, or
- a set of RS measurement opportunities may (e.g., alternatively) correspond to a specific group of resources that may be used for CSI measurement, e.g., and that may be identified by an index.
- An index may be added to the configuration of a (e.g., each) CSI resource configuration, or to the configuration of a (e.g., each) CSI-RS, CSI interference measurement (CSI-IM) or SSB resource.
- a WTRU may determine or assume that a (e.g., each) resource is present, for example, (e.g. only) if the set of RS measurement opportunities corresponding to the index is applicable, e.g., according to at least one of the examples.
- An index may (e.g., alternatively) be added, for example, as part of the configuration of a (e.g., each) CSI report configuration.
- a WTRU may measure and report according to a CSI report configuration, for example, if the set of RS measurement opportunities corresponding to the index is applicable (e.g., according to at least one of the examples), which may support (e.g., allow) adaptation of the measurement resources and the reporting resources.
- an RRC may configure groups of CSI report configurations within a CSI measurement configuration, where a (e.g., each) group may correspond to a set of RS measurement opportunities.
- a WTRU may (e.g., at any point of time) apply the set of CSI report configurations of the group corresponding to the set of RS measurement opportunities that may be obtained, e.g., according to at least one of the examples.
- a CSI report configuration may (e.g., alternatively) comprise/include at least one set of RS measurement opportunities ⁇ . g., including a default set).
- a (e.g., each) set of RS measurement opportunities may comprise a set resources for channel measurement and sets of resources for interference measurement (e.g., CSI-IM and/or NZP CSI-RS).
- a WTRU may (e.g., for each CSI report configuration) utilize the resources corresponding to the index identifying the set of RS measurement opportunities, e.g., according to at least one of the examples.
- a link may be configured between BFD and DRX.
- DRX may impact beam management.
- a WTRU may change the status of a subset of beam states, (de)-activate associated CSI-RS or SSBs, and/or pause/resume associated BFD measurements and procedures, for example, as a function of the DRX state and/or the active DRX configuration.
- a WTRU may (de)-activate certain beams and associated CSI-RS, for example, as a function of DRX states and/or based on whether certain DRX timers are running.
- a WTRU may (de)-activate one or more (e.g., certain) beams and/or associated CSI-RS, for example, during DRX inactive times.
- a WTRU may change a subset of beam states, (de)-activate associated CSI-RS or SSBs, and/or pause/resume associated BFD measurements and procedures, for example, after receiving (or after a lack of receiving) network signaling associated with DRX or power savings.
- a WTRU may (de)- activate certain beams, associated CSI-RS, and/or pause or resume associated BFD measurements and procedures, for example, after receiving a DRX short cycle command, a DRX long cycle command, a WUS, and/or a PDCCFI signal.
- a WTRU may (de)-activate certain beams, associated CSI-RS, and/or pause or resume associated BFD measurements and procedures, for example, after not receiving a life signal or a WUS associated with the beam.
- a (de)activation may be, for example, for a number of consecutive configured periods (e.g., DRX periods or a separate configured period).
- a WTRU may turn off or pause DRX, transition into a different DRX cycle (e.g., short DRX), and/or (re)-start the DRX inactivity timer, for example, based on (e.g., upon) detecting a beam failure, measuring a loss of beam(s), and/or measuring a channel condition quantity below a threshold for the set of maintained beams.
- a WTRU may (re)-start the DRX retransmission timers or the DRX FIARQ RTT timers, for example, after measuring a loss of beam(s) or measuring a channel condition quantity below a threshold for the set of maintained beams.
- a WTRU may transition into a different DRX cycle and/or DRX configuration, pause/resume DRX functionality, and/or start certain DRX timers, for example, after receiving (or after a lack of receiving) network signaling associated with an active beam in the maintained set of beams.
- a WTRU may transition into a different DRX cycle and/or DRX configuration, pause/resume DRX functionality, and/or start certain DRX timers, for example, after measuring CSI-RS of a certain set of RS measurement opportunities (e.g., lower or higher than a threshold), receiving an aperiodic CSI-RS request, and/or receiving dynamic signaling associated with the set of RS measurement opportunities.
- Beam reestablishment (e.g. after DRX sleep) may impact BFR.
- a WTRU may measure configured active CSI-RS, for example, during a DRX-beam observation period.
- a DRX-beam observation period may be, for example, the on duration, a configured period prior to the on duration, a configured period prior to the WUS occasion, and/or during the time between the WUS occasion and the on duration.
- a WTRU may measure configured active CSI-RS during the DRX-beam observation period, conditioned on, for example, receiving a WUS signaling wake up prior to the on duration and/or expiration of the inactivity timer.
- a WTRU may measure CSI-RS and/or SSBs associated with the maintained beam set.
- a WTRU may (e.g., additionally) measure CSI-RS and/or SSBs associated with the candidate beam set, for example, conditioned on the lack of a satisfactory beam (e.g., that meets a configured channel condition measurement threshold) in the maintained beam set.
- a WTRU may (i) trigger a BFR (e.g., a new BFR) or beam reestablishment procedure, for example, if the WTRU does not have any satisfactory beam (e.g., that meets a configured channel condition measurement threshold) in the maintained beam set during the DRX-beam observation period and may (ii) (e.g., further) transition into active time or switch DRX cycles.
- a WTRU may (e.g., further) condition triggering a BFR, for example, based on having at least one beam with a satisfactory measurement in the candidate beam set.
- a WTRU may (e.g., during the BFR procedure), for example, perform at least one of the following actions: (i) follow a legacy BFR procedure (e.g., as described herein), (ii) transition into active time, (iii) report preferred beam ID(s) on a different serving cell (e.g., using a BFR MAC CE or a PUCCH), and/or (iv) transmit an SRS associated with the preferred beam(s).
- a WTRU may monitor one or more (e.g., certain) PDCCFI resources (e.g., a subset of configured CORESET(s) or search space(s)) associated with the indicated preferred beam(s).
- An association may be configured, for example, by RRC signaling.
- a WTRU may consider a beam reestablishment or BFR procedure successful, for example, based on (e.g., upon) receiving a response on the downlink.
- a response may be conditioned for receipt on the PDCCFI resources associated with the indicated preferred beams.
- DRX may impact a BFD procedure.
- a WTRU may pause or (re)-start a BFD timer, for example, based on (e.g., upon) going into inactive time (e.g., after the expiry of the DRX inactivity timer or during the DRX sleep opportunity), which may support, for example, maintaining the BFI count before going into sleep, e.g., without resetting the BFI counter.
- a WTRU may restart the BFD timer at a (e.g., each) CSI-RS occasion (e.g., occasions monitored in connected mode) or a subset of CSI-RS occasions, for example, if the WTRU is in DRX inactive time, e.g., even if the WTRU does not make any CSI measurements during the DRX sleep duration.
- a WTRU may be configured with a separate value for the BFD timer, which the WTRU may apply, for example, if the WTRU is configured with DRX and if DRX is active.
- a WTRU may be configured with a separate timer (e.g., a timer in lieu of the BFD timer), which the WTRU may apply for BFD, for example, if the WTRU is configured with DRX, if DRX is active, and/or if DRX is used to rest the BFI counter when C-DRX is used.
- a WTRU may restart the BFD timer with a value that equals the DRX cycle duration (e.g., period between on durations), for example, upon going into inactive time (e.g., after the expiry of the DRX inactivity timer or during the DRX sleep opportunity).
- a WTRU may (e.g., alternatively), apply (e.g., only) the BFD timer to the BFD procedure, for example, if the WTRU is in active time and/or if C-DRX is not used or not configured.
- a WTRU may be configured with a DRX BFI counting timer (e.g., a new DRX BFI counting timer), which the WTRU may apply for BFD, for example, if the WTRU is configured with DRX and/or if the WTRU is inactive.
- a WTRU may (re)-start the BFD timer or resume the BFD timer if it was paused, for example, after the expiry of the DRX counting timer.
- a WTRU may limit counting BFIs to BFIs measured during active time.
- a WTRU may scale counting a beam failure instance, for example, by a (e.g., certain) ratio related to the DRX period and/or the relative CSI-RS period.
- a WTRU may apply scaling during DRX on durations and/or after the expiry of the inactivity timer.
- a WTRU may increment the BFI counter, for example, by (active DRX period/CSI-RS period), (active DRX period/max(shortest configured DRX period, CSI-RS period)), and/or (active DRX period/an RRC configured period).
- a long DRX cycle is 20 ms
- a short cycle is 10 ms
- a CSI period is 2 ms.
- a WTRU may round counting to an integer, for example, if/when incrementing counting by a scaled value.
- BFD may impact DRX operation.
- a WTRU may perform beam failure detection in a (e.g., each) beam failure detection instance, for example, with (i) one or more periodic CSI-RS resources configured as beam failure detection resources (BFDR) or (e.g., if BFDR is not configured) (ii) the periodic CSI-RS resources and/or SS/PBCH blocks associated with CORESETs (e.g., that the WTRU uses for monitoring PDCCFI).
- BFDR beam failure detection resources
- SS/PBCH blocks associated with CORESETs e.g., that the WTRU uses for monitoring PDCCFI.
- a WTRU may perform beam failure detection, for example, if the WTRU is in active time with a C-DRX configuration.
- beam failure detection resources (BFDR) and (ii) periodic CSI-RS resources and/or SS/PBCH blocks associated with CORESETs may be used interchangeably.
- a WTRU may switch between DRX states (e.g., long DRX and short DRX cycles), for example, based on detected beam failure instance(s) (BFIs).
- BFIs detected beam failure instance(s)
- the time to detect a connection problem e.g., beam failure
- a WTRU may switch from a long DRX cycle to a short DRX cycle to confirm or detect a beam failure.
- a WTRU may perform beam failure detection (BFD) and recovery associated with DRX.
- BFD beam failure detection
- the WTRU may switch to the short DRX cycle or may suspend DRX for CSI-RS measurements for BFD, for example, based on a 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” durations associated with a short DRX cycle.
- the WTRU may update the first BFI counter value to a second BFI counter value, for example, based on the measurements.
- the WTRU may switch to or may resume using the long DRX cycle for CSI-RS measurements associated with BFD, for example, on a condition that the second BFI counter value is less than a second threshold.
- a BFI may be determined/detected and a BFI counter may be incremented, for example, based on a channel condition state determined from measurement of a CSI-RS.
- a WTRU may be configured to detect or trigger beam failure based on a threshold of greater than six BFIs or equal to or greater than seven (7) BFIs. Measurement opportunities to detect BFIs, or lack thereof, may occur during on durations in a long DRX cycle and during on durations in a short DRX cycle.
- the number of BFIs detected e.g., tracked, for example via the BFI counter
- durations of long DRX and short DRX cycles is shown as 0, 1 , 2, 3, 4, 5, 6, and 7 in FIG. 3.
- a WTRU configured as shown in FIG. 3 may detect beam failure and enter BFR faster than a WTRU configured to remain in a long DRX cycle (e.g., as shown by example in FIG. 2).
- a WTRU may perform a channel state information-reference signal (CSI-RS) measurement(s) during one or more on-durations associated with a first (e.g., long) DRX cycle.
- the WTRU may determine/track a number of beam failure instances based on the CSI-RS measurement(s).
- the BFI counter may remain at zero (0) if no BFI is detected (e.g., as indicated by a checkmark at "0” in FIG. 3) during an on duration of a long DRX cycle.
- the WTRU may increment the BFI counter to one (1), for example, based on a detection of a first BFI (e.g., as indicated by an X at ⁇ ” in FIG. 3) during an on duration of the long DRX cycle.
- the WTRU may increment the BFI counter to two (2), for example, based on detection of a second BFI during the on duration of the long DRX cycle (e.g., as indicated by an X at "2” in FIG. 3).
- the WTRU may switch to a second (e.g., short) DRX cycle, for example, based on the determined number of beam failure instances (e.g., in comparison to a switch threshold).
- the WTRU may be configured to switch between DRX cycles (e.g., long and short DRX cycles), for example, based on a switch threshold number of BFIs (e.g., as counted by the BFI counter).
- a WTRU may be configured to switch from a long DRX cycle to a short DRX cycle if/when the BFI counter value is greater than one (1) BFI.
- the WTRU may (e.g., as shown in FIG. 3) switch from a long DRX cycle to a short DRX cycle if/when the BFI counter value is two (2)
- the WTRU may perform a CSI-RS measurement during an on-duration associated with the second (e.g., short) DRX cycle.
- the rate of measurement and/or measurement opportunities to detect BFIs may increase by switching to short DRX cycles, e.g., which may permit a WTRU to detect a beam failure faster (e.g., in a shorter period of time) than if the WTRU remained in a long DRX cycle (e.g., as shown by example in FIG. 2).
- the WTRU may update the number of beam failure instances based on additional CSI-RS measurement(s). For example (e.g., as shown in FIG.
- 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) (e.g., equal to six or fewer) BFIs after a configured number of cycles of the second (e.g., short) cycle.
- the BFI counter is less than seven (7) (e.g., equal to six or fewer) BFIs after a configured number of cycles of the second (e.g., short) cycle.
- the WTRU may determine and/or receive (e.g., from a network device) configuration information, which may include, for example, one or more of the following: the first (e.g., long) DRX cycle, the second (e.g., short) DRX cycle, a timing associated with CSI-RS measurement in the first DRX cycle, a timing associated with CSI-RS measurement in the second DRX cycle, the first DRX cycle switch threshold, the first (e.g., BFD) threshold, the second (e.g., non-DRX) threshold, the second DRX cycle switch threshold, and/or the like.
- the first (e.g., long) DRX cycle the second (e.g., short) DRX cycle
- a timing associated with CSI-RS measurement in the first DRX cycle a timing associated with CSI-RS measurement in the second DRX cycle
- the first DRX cycle switch threshold the first (e.g., BFD) threshold
- the second set of PDCCH search spaces may be an empty set (e.g., if the BFI counter is less than the maximum); (ii) The second set of PDCCH search spaces may include beam recovery search space (e.g., if the BFI counter reached the maximum count); and/or (iii) The second set of PDCCH search space may include beam recovery search space (e.g., if the new candidate beam has been indicated and the WTRU has not received a confirmation from the gNB).
- a WTRU may operate in DRX operation (e.g., monitor PDCCH in Active time and skip monitoring PDCCH in inactive time), for example, if BFI counter ⁇ threshold.
- the threshold may be a predefined number (e.g., 0) or may be configured.
- One or more following WTRU behaviors may be used, for example, based on whether a BFI counter is or is not less than threshold.
- a WTRU may monitor (a) a PDCCH search space in inactive time (e.g., for recovery) or (b) all configured PDCCH search spaces in inactive time and the PDCCH search space (e.g., for recovery), for example, after the WTRU sends a new candidate beam index via PRACH or a recovery request signal (e.g., a BFR MAC CE); (ii) a WTRU may measure beam failure detection resources in inactive time; (iii) inactivity time may be reset (e.g., based on beam failure detection status); (iv) a WTRU may report to gNB that the BFI counter is larger than or equal to the threshold, for example, by transmitting a signal (e.g., UCI on PUCCH, UCI on PUSCH, or an SR) for the report; and/or (v) a WTRU may monitor (e.g.,
- a measurement threshold may be a function of beam management.
- a WTRU may be configured with measurement configurations that may be specific to a beam characteristic (e.g., beam type, beam width, beam ID, or the likes). For example, a WTRU may perform (e.g., specific) link and/or connectivity management procedures as a function of a (e.g., specific) beam configuration.
- a WTRU may be configured with a default beam and may use the associated configuration, for example, if no other beam is selected (e.g., for scheduled transmission(s)).
- a WTRU may use a default, for example, if/when the time alignment timer (TAT) is not running, if/when the WTRU is in DRX Inactive time, and/or under a period of limited (e.g., if any) scheduling activity for unicast transmissions.
- a measurement configuration may include, for example, configurations related to beam management, configurations for radio link monitoring (RLM), configurations for mobility management and/or measurement reporting, configurations for measurements related to CSI reporting, and/or configurations for sensing in unlicensed spectrum (e.g., energy detection level, sensing duration).
- DRX configurations may be beam-specific.
- a WTRU may be configured with beam- specific, beam index specific, beam ID specific, and/or beam type specific DRX configurations.
- a WTRU may determine the applicable DRX configuration, for example, as a function of the beam used for reception of the PDCCH control channel for a given cell.
- a WTRU may determine the applicable DRX configuration, for example, when a beam is first established.
- a wireless transmit/receive unit may determine measurement occasions as a function of scheduling activity and beam configuration.
- a WTRU may determine measurement occasions for beam failure detection (BFD), radio link monitoring (RLM), and/or mobility as a function of discontinuous reception (DRX) and/or BFD configuration.
- BFD beam failure detection
- RLM radio link monitoring
- DRX discontinuous reception
- a WTRU may determine that a first set of reference signal (RS) measurement opportunities are applicable based on a first condition (e.g., if/when a DRX/BFD/channel state information (CSI) condition is met) and a second set of RS measurement opportunities are applicable based on a second condition (e.g., if/when the DRX/BFD/CSI condition is not met).
- RS reference signal
- a WTRU may be configured with multiple sets of CSI-RS measurement opportunities (e.g., with different periodicities).
- a WTRU may assume a given set is applicable, for example, if a DRX/BFD/CSI condition is met.
- a WTRU may determine DRX operation or non-DRX operation, for example, based on whether a BFI counter is or is not less than a threshold.
- a WTRU may reset an inactivity timer, for example, based on one or more BFD statuses (e.g., beam failure instance (BFI) counter > threshold and no BFD resource before inactivity timer expiry).
- BFI beam failure instance
- a WTRU may pause, disable, or (re)-start the BFD timer, for example, upon going into inactive time.
- a WTRU may change beam states, (de)-activate associated CSI-RS, and/or pause/resume associated BFD, for example, as a function of the DRX state/configuration or related signaling.
- a 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, as a function of detecting a beam failure, loss of beam(s), or related measurements.
- a WTRU may trigger a BFR/beam reestablishment procedure (e.g., a new BFR/beam reestablishment procedure), for example, if the WTRU does not have a satisfactory beam during a DRX-beam observation period.
- a BFR/beam reestablishment procedure e.g., a new BFR/beam reestablishment procedure
- the processes described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor.
- Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media.
- Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, 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.
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/795,332 US20230088597A1 (en) | 2020-02-12 | 2021-02-12 | Power efficient measurements at higher frequencies |
CN202180018125.5A CN115211162A (en) | 2020-02-12 | 2021-02-12 | Power efficient measurement at higher frequencies |
EP21709860.7A EP4104490A1 (en) | 2020-02-12 | 2021-02-12 | Power efficient measurements at higher frequencies |
CN202310082981.8A CN116112968A (en) | 2020-02-12 | 2021-02-12 | Power efficient measurement at higher frequencies |
BR112022015873A BR112022015873A2 (en) | 2020-02-12 | 2021-02-12 | WIRELESS TRANSMISSION/RECEPTION UNIT AND METHOD |
JP2022546486A JP2023512676A (en) | 2020-02-12 | 2021-02-12 | Efficient measurement of power at higher frequencies |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202062975416P | 2020-02-12 | 2020-02-12 | |
US62/975,416 | 2020-02-12 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021163404A1 true WO2021163404A1 (en) | 2021-08-19 |
Family
ID=74856958
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2021/017756 WO2021163404A1 (en) | 2020-02-12 | 2021-02-12 | Power efficient measurements at higher frequencies |
Country Status (6)
Country | Link |
---|---|
US (1) | US20230088597A1 (en) |
EP (1) | EP4104490A1 (en) |
JP (1) | JP2023512676A (en) |
CN (2) | CN115211162A (en) |
BR (1) | BR112022015873A2 (en) |
WO (1) | WO2021163404A1 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210297213A1 (en) * | 2020-03-19 | 2021-09-23 | Acer Incorporated | Device and Method for Handling Reference Signals in an Unlicensed Band |
WO2023102695A1 (en) * | 2021-12-06 | 2023-06-15 | Oppo广东移动通信有限公司 | Measurement relaxation method and apparatus, and terminal device and storage medium |
WO2023132771A1 (en) * | 2022-01-07 | 2023-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Adapting transitions between ue activity states |
WO2023156654A1 (en) | 2022-02-18 | 2023-08-24 | Continental Automotive Technologies GmbH | Inter-drx assistance method for operating a user equipment (ue) |
WO2023191993A1 (en) * | 2022-03-31 | 2023-10-05 | Qualcomm Incorporated | Enhanced ue behavior for bfd/bfr in drx mode |
WO2023229769A1 (en) * | 2022-05-26 | 2023-11-30 | Qualcomm Incorporated | Beam quality enhancement techniques in discontinuous reception (drx) mode |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230088966A1 (en) * | 2021-09-22 | 2023-03-23 | Apple Inc. | Power Efficient Beam Recovery Procedures |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2621242A1 (en) * | 2012-01-26 | 2013-07-31 | Panasonic Corporation | Improved discontinuous reception operation with additional wake up opportunities |
US20190261287A1 (en) * | 2016-11-02 | 2019-08-22 | Idac Holdings, Inc. | Devices, systems and methods for power efficient beam management in wireless systems |
US20190394082A1 (en) * | 2018-06-21 | 2019-12-26 | Ali Cagatay Cirik | PUCCH Based Beam Failure Recovery Procedure |
-
2021
- 2021-02-12 JP JP2022546486A patent/JP2023512676A/en active Pending
- 2021-02-12 CN CN202180018125.5A patent/CN115211162A/en active Pending
- 2021-02-12 BR BR112022015873A patent/BR112022015873A2/en unknown
- 2021-02-12 US US17/795,332 patent/US20230088597A1/en active Pending
- 2021-02-12 EP EP21709860.7A patent/EP4104490A1/en active Pending
- 2021-02-12 WO PCT/US2021/017756 patent/WO2021163404A1/en unknown
- 2021-02-12 CN CN202310082981.8A patent/CN116112968A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2621242A1 (en) * | 2012-01-26 | 2013-07-31 | Panasonic Corporation | Improved discontinuous reception operation with additional wake up opportunities |
US20190261287A1 (en) * | 2016-11-02 | 2019-08-22 | Idac Holdings, Inc. | Devices, systems and methods for power efficient beam management in wireless systems |
US20190394082A1 (en) * | 2018-06-21 | 2019-12-26 | Ali Cagatay Cirik | PUCCH Based Beam Failure Recovery Procedure |
Non-Patent Citations (3)
Title |
---|
ASUSTEK: "BFR procedure during DRX mode", vol. RAN WG2, no. Chengdu, China; 20181008 - 20181012, 28 September 2018 (2018-09-28), XP051524596, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F103bis/Docs/R2%2D1815238%2Ezip> [retrieved on 20180928] * |
HUAWEI ET AL: "Beam failure detection in DRX", vol. RAN WG2, no. Chengdu, China; 20181008 - 20181012, 28 September 2018 (2018-09-28), XP051523356, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F103bis/Docs/R2%2D1813886%2Ezip> [retrieved on 20180928] * |
HUAWEI ET AL: "CR on TS38.133 for beam failure detection requirements", vol. RAN WG4, no. Melbourne, Australia; 20180416 - 20180420, 15 April 2018 (2018-04-15), XP051431622, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN4/Docs/> [retrieved on 20180415] * |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210297213A1 (en) * | 2020-03-19 | 2021-09-23 | Acer Incorporated | Device and Method for Handling Reference Signals in an Unlicensed Band |
US11843555B2 (en) * | 2020-03-19 | 2023-12-12 | Acer Incorporated | Device and method for handling reference signals in an unlicensed band |
WO2023102695A1 (en) * | 2021-12-06 | 2023-06-15 | Oppo广东移动通信有限公司 | Measurement relaxation method and apparatus, and terminal device and storage medium |
WO2023132771A1 (en) * | 2022-01-07 | 2023-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Adapting transitions between ue activity states |
WO2023156654A1 (en) | 2022-02-18 | 2023-08-24 | Continental Automotive Technologies GmbH | Inter-drx assistance method for operating a user equipment (ue) |
WO2023191993A1 (en) * | 2022-03-31 | 2023-10-05 | Qualcomm Incorporated | Enhanced ue behavior for bfd/bfr in drx mode |
WO2023229769A1 (en) * | 2022-05-26 | 2023-11-30 | Qualcomm Incorporated | Beam quality enhancement techniques in discontinuous reception (drx) mode |
Also Published As
Publication number | Publication date |
---|---|
CN116112968A (en) | 2023-05-12 |
BR112022015873A2 (en) | 2022-10-25 |
EP4104490A1 (en) | 2022-12-21 |
US20230088597A1 (en) | 2023-03-23 |
CN115211162A (en) | 2022-10-18 |
JP2023512676A (en) | 2023-03-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230379910A1 (en) | System and method for bandwidth part operation | |
US20230216565A1 (en) | Beam indication based on tci state group | |
US20230088597A1 (en) | Power efficient measurements at higher frequencies | |
US20230144010A1 (en) | Methods, apparatuses and systems directed to beam management in connection with multiple cells and/or multiple transmission/reception points | |
US20220287094A1 (en) | Methods for reception of csi-rs and csi feedback in nr-u | |
US20230072340A1 (en) | Channel access in unlicensed spectrum | |
EP4278735A1 (en) | Methods and systems for efficient uplink (ul) synchronization maintenance with a deactivated secondary cell group (scg) | |
US20230300645A1 (en) | Methods and apparatus for beam failure recovery | |
EP4154663A1 (en) | Method and apparatus for power savings on a dormant secondary cell group (scg) | |
US20230354327A1 (en) | Methods and apparatus for dynamic spectrum sharing | |
US20220303795A1 (en) | Power saving signal operations | |
US20240031931A1 (en) | Wtru power saving in active time | |
WO2023081258A1 (en) | Methods, architectures, apparatuses and systems for network energy savings | |
WO2021207490A1 (en) | Receiving node channel assessment | |
WO2024030658A1 (en) | Methods for pdu duplication in multicarrier sidelink | |
WO2023196574A1 (en) | Method and apparatus for beam failure recovery in mimo systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21709860 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022546486 Country of ref document: JP Kind code of ref document: A |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112022015873 Country of ref document: BR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021709860 Country of ref document: EP Effective date: 20220912 |
|
ENP | Entry into the national phase |
Ref document number: 112022015873 Country of ref document: BR Kind code of ref document: A2 Effective date: 20220810 |