EP4612807A2 - Indication de capacité de latence pour répéteur commandé par réseau - Google Patents

Indication de capacité de latence pour répéteur commandé par réseau

Info

Publication number
EP4612807A2
EP4612807A2 EP23798643.5A EP23798643A EP4612807A2 EP 4612807 A2 EP4612807 A2 EP 4612807A2 EP 23798643 A EP23798643 A EP 23798643A EP 4612807 A2 EP4612807 A2 EP 4612807A2
Authority
EP
European Patent Office
Prior art keywords
ncr
repeater
mode
latency
aspects
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23798643.5A
Other languages
German (de)
English (en)
Inventor
Navid Abedini
Junyi Li
Luca Blessent
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/481,947 external-priority patent/US20240154687A1/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to EP25226623.4A priority Critical patent/EP4701094A3/fr
Publication of EP4612807A2 publication Critical patent/EP4612807A2/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15557—Selecting relay station operation mode, e.g. between amplify and forward mode, decode and forward mode or FDD - and TDD mode
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for providing a latency capability indication for a network- controlled repeater.
  • BACKGROUND [0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like).
  • a wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs.
  • UE user equipment
  • UE user equipment
  • a UE may communicate with a network node via downlink communications and uplink communications.
  • Downlink (or “DL”) refers to a communication link from the network node to the UE
  • uplink (or “UL”) refers to a communication link from the UE to the network node.
  • Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and/or a wireless personal area network (WPAN) link, among other examples).
  • SL sidelink
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • New Radio which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
  • NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • MIMO multiple-input multiple-output
  • Some aspects described herein relate to a method of wireless communication performed by a network-controlled repeater (NCR).
  • the method may include transmitting an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding.
  • the method may include communicating based at least in part on the latency capability.
  • Some aspects described herein relate to a method of wireless communication performed by an NCR.
  • the method may include transmitting an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the method may include switching from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • Some aspects described herein relate to a method of wireless communication performed by a network entity.
  • the method may include receiving an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding.
  • the method may include communicating based at least in part on the latency capability.
  • Some aspects described herein relate to a method of wireless communication performed by an NCR.
  • the method may include receiving an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the method may include communicating based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode.
  • 0097-4273PCT 2 Some aspects described herein relate to an NCR for wireless communication.
  • the NCR may include memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors.
  • the instructions may be executable by the one or more processors to cause the NCR to transmit an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding.
  • the instructions may be executable by the one or more processors to cause the NCR to communicate based at least in part on the latency capability.
  • Some aspects described herein relate to an NCR for wireless communication.
  • the NCR may include memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors.
  • the instructions may be executable by the one or more processors to cause the NCR to transmit an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the instructions may be executable by the one or more processors to cause the NCR to switch from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • Some aspects described herein relate to a network entity for wireless communication.
  • the network entity may include memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors.
  • the instructions may be executable by the one or more processors to cause the network entity to receive an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding.
  • the instructions may be executable by the one or more processors to cause the network entity to communicate based at least in part on the latency capability.
  • Some aspects described herein relate to an NCR for wireless communication.
  • the NCR may include memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors.
  • the instructions may be executable by the one or more processors to cause the NCR to receive an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the instructions may be executable by the one or more processors to cause the NCR to communicate based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores one or more instructions for wireless communication by an NCR.
  • the one or more instructions when executed by one or more processors of the NCR, may cause the NCR to transmit an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding.
  • the one or more instructions when executed by one 0097-4273PCT 3 or more processors of the NCR, may cause the NCR to communicate based at least in part on the latency capability.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores one or more instructions for wireless communication by a non-transitory computer- readable medium storing one or more instructions for wireless communication.
  • the one or more instructions when executed by one or more processors of the NCR, may cause the NCR to transmit an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the one or more instructions when executed by one or more processors of the NCR, may cause the NCR to switch from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores one or more instructions for wireless communication by a network entity.
  • the one or more instructions when executed by one or more processors of the network entity, may cause the network entity to receive an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding.
  • the one or more instructions when executed by one or more processors of the network entity, may cause the network entity to communicate based at least in part on the latency capability.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores one or more instructions for wireless communication by an NCR.
  • the one or more instructions when executed by one or more processors of the NCR, may cause the NCR to receive an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the one or more instructions when executed by one or more processors of the NCR, may cause the NCR to communicate based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode.
  • the apparatus may include means for transmitting an indication of a latency capability of the apparatus for switching between repeater modes for mobile termination and for forwarding.
  • the apparatus may include means for communicating based at least in part on the latency capability.
  • Some aspects described herein relate to an apparatus for wireless communication.
  • the apparatus may include means for transmitting an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the apparatus may include means for switching from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • the apparatus may include means for receiving an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding.
  • the apparatus may include means for communicating based at least in part on the latency capability.
  • Some aspects described herein relate to an apparatus for wireless communication.
  • the apparatus may include means for receiving an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the apparatus may include means for communicating based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, mobile station, base station, NCR, network entity, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
  • the foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims.
  • aspects may be implemented via integrated chip embodiments or other non-module- component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices).
  • non-module- component based devices e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices.
  • aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components.
  • Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects.
  • transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including 0097-4273PCT 5 antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers).
  • RF radio frequency
  • aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.
  • Fig.1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.
  • Fig.2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
  • Fig.3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.
  • Fig.4 is a diagram of an example of a network-controlled repeater (NCR), in accordance with the present disclosure.
  • Fig.5 is a diagram illustrating an example associated with using a latency for switching repeater modes, in accordance with the present disclosure.
  • Fig.6 is a diagram of an example of an NCR using sleep modes, in accordance with the present disclosure.
  • Fig.7 is a diagram illustrating an example process performed, for example, by an NCR, in accordance with the present disclosure.
  • Fig.8 is a diagram illustrating an example process performed, for example, by an NCR, in accordance with the present disclosure.
  • Fig.9 is a diagram illustrating an example process performed, for example, by a network entity, in accordance with the present disclosure.
  • Fig.10 is a diagram illustrating an example process performed, for example, by an NCR, in accordance with the present disclosure.
  • Fig.11 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.
  • 0097-4273PCT 6 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.
  • DETAILED DESCRIPTION [0038] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings.
  • Fig.1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure.
  • the wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples.
  • 5G e.g., NR
  • 4G Long Term Evolution
  • the wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and/or other entities.
  • a network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network 0097-4273PCT 7 nodes.
  • a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit).
  • RAN radio access network
  • a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
  • CUs central units
  • DUs distributed units
  • RUs radio units
  • a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU.
  • a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU.
  • a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU.
  • a network node 110 may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs.
  • a network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof.
  • the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.
  • a network node 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a network node 110 and/or a network node subsystem serving this coverage area, depending on the context in which the term is used.
  • a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)).
  • CSG closed subscriber group
  • a network node 110 for a macro cell may be referred to as a macro network node.
  • a network node 110 for a pico cell may be referred to as a pico network node.
  • a network node 110 for a femto cell may be referred to as a femto network 0097-4273PCT 8 node or an in-home network node.
  • the network node 110a may be a macro network node for a macro cell 102a
  • the network node 110b may be a pico network node for a pico cell 102b
  • the network node 110c may be a femto network node for a femto cell 102c.
  • a network node may support one or multiple (e.g., three) cells.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node).
  • the terms “base station,” “network node,” or “network entity” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof.
  • IAB integrated access and backhaul
  • base station or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, or a combination thereof.
  • the terms “base station,” “network node,” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110.
  • the terms “base station,” “network node,” or “network entity” may refer to a plurality of devices configured to perform the one or more functions.
  • each of a quantity of different devices may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station,” “network node,” or “network entity” may refer to any one or more of those different devices.
  • the terms “base station,” “network node,” or “network entity” may refer to one or more virtual base stations or one or more virtual base station functions.
  • two or more base station functions may be instantiated on a single device.
  • the terms “base station,” “network node,” or “network entity” may refer to one of the base station functions and not another.
  • the wireless network 100 may include one or more relay stations.
  • a relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110).
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the network node 110d may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d.
  • a network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.
  • the wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network 0097-4273PCT 9 nodes, relay network nodes, or the like.
  • a network controller may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110.
  • the network controller may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link.
  • the network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • a network-controlled repeater (NCR) 130 may be a network entity that is coupled to or communicates with one or more network entities (e.g., network node 110) and one or more UEs (e.g., UE 120).
  • the NCR 130 may have a mobile termination (MT) function for communications.
  • the network entity may control the operation of the NCR 130 via a control link.
  • the NCR 130 may also have a forwarding (Fwd) function for forwarding communications between network entities (via a backhaul link) and UEs (via an access link).
  • Fwd forwarding
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit.
  • a UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular component or sensor,
  • Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, another device (e.g., a remote device), or some other entity.
  • Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices.
  • Some UEs 120 may be considered a Customer Premises Equipment.
  • a UE 120 may be included inside a housing that 0097-4273PCT 10 houses components of the UE 120, such as processor components and/or memory components.
  • the processor components and the memory components may be coupled together.
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies.
  • a RAT may be referred to as a radio technology, an air interface, or the like.
  • a frequency may be referred to as a carrier, a frequency channel, or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 e.g., shown as UE 120a and UE 120e
  • may communicate directly using one or more sidelink channels e.g., without using a network node 110 as an intermediary to communicate with one another).
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to- vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network.
  • V2X vehicle-to-everything
  • a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the network node 110.
  • Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands.
  • devices of the wireless network 100 may communicate using one or more operating bands.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz – 24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are 0097-4273PCT 11 currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • an NCR may include a communication manager 160.
  • the communication manager 160 may transmit an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding.
  • the communication manager 160 may communicate based at least in part on the latency capability.
  • the communication manager 160 may transmit an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the communication manager 160 may switch from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • the communication manager 160 may receive an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the communication manager 160 may communicate based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode. Additionally, or alternatively, the communication manager 160 may perform one or more other operations described herein.
  • a network entity e.g., network node 110
  • the communication manager 150 may receive an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding.
  • the communication manager 150 may communicate based at least in part on the latency capability. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
  • Fig.1 is provided as an example. Other examples may differ from what is described with regard to Fig.1. 0097-4273PCT 12
  • an individual processor may perform all of the functions described as being performed by the one or more processors.
  • one or more processors may collectively perform a set of functions.
  • a first set of (one or more) processors of the one or more processors may perform a first function described as being performed by the one or more processors
  • a second set of (one or more) processors of the one or more processors may perform a second function described as being performed by the one or more processors.
  • the first set of processors and the second set of processors may be the same set of processors or may be different sets of processors.
  • Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig. 2.
  • Reference to “memory” or “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig.2.
  • Fig.2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
  • the network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ⁇ 1).
  • the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ⁇ 1).
  • the network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 254.
  • a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.
  • a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120.
  • MCSs modulation and coding schemes
  • the network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120.
  • the transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols.
  • the transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)).
  • SRPI semi-static resource partitioning information
  • control information e.g., CQI requests, grants, and/or upper layer signaling
  • CRS cell-specific reference signal
  • DMRS demodulation reference signal
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform 0097-4273PCT 13 spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t.
  • each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
  • Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal.
  • the modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.
  • a set of antennas 252 may receive the downlink signals from the network node 110 and/or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r.
  • R received signals e.g., R received signals
  • each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
  • Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
  • controller/processor may refer to one or more controllers, one or more processors, or a combination thereof.
  • a channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSSRQ reference signal received quality
  • CQI parameter a CQI parameter
  • one or more components of the UE 120 may be included in a housing 284.
  • the NCR 130 may include a communication unit 294, a controller/processor 290, and a memory 292.
  • the NCR 130 may communicate with the network node 110 and other network entities via the communication unit 294.
  • the NCR 130 may also include components used for wireless communication with UEs and network entities. These components may include a wireless communication unit 296 and an antenna 298.
  • the wireless communication unit 296 may include the components described for the network node 110, such as modems and transmit/receive processors. 0097-4273PCT 14 [0066]
  • One or more antennas e.g., antennas 234a through 234t and/or antennas 252a through 252r
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig.2.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280.
  • the transmit processor 264 may generate reference symbols for one or more reference signals.
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110.
  • the modem 254 of the UE 120 may include a modulator and a demodulator.
  • the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266.
  • the transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs.4-12).
  • a processor e.g., the controller/processor 280
  • the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs.4-12).
  • the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
  • the modem 232 e.g., a demodulator component, shown as DEMOD, of the modem 232
  • MIMO detector 236 e.g., a
  • the receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240.
  • the network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244.
  • the network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications.
  • the modem 232 of the network node 110 may include a modulator and a demodulator.
  • the network node 110 includes a transceiver.
  • the transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230.
  • the transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs.4-12).
  • the controller/processor of a network entity may perform one or more techniques associated with indicating a latency capability and/or a sleep capability for NCR repeater modes, as described in more detail elsewhere herein.
  • the controller/processor 290 of the NCR 130, the controller/processor 240 of the network node 110, and/or any other component(s) of Fig.2 may perform or direct operations of, for example, process 700 of Fig.7, process 800 of Fig.8, process 900 of Fig.9, process 1000 of Fig.10, and/or other processes as described herein.
  • the memory 242 and the memory 292 may store data and program codes for the network node 110 and the UE 120, respectively.
  • the memory 242 and/or the memory 292 may include a non-transitory computer- readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication.
  • the one or more instructions when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the NCR 130, may cause the one or more processors, the network node 110, and/or the NCR 130 to perform or direct operations of, for example, process 700 of Fig.7, process 800 of Fig.8, process 900 of Fig.9, process 1000 of Fig.10, and/or other processes as described herein.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.
  • an NCR (e.g., NCR 130) includes means for transmitting an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding; and/or means for communicating based at least in part on the latency capability.
  • the means for the NCR to perform operations described herein may include, for example, one or more of communication manager 160, communication unit 294, controller/processor 290, memory 292, wireless communication unit 296, antenna 298, transmit processor 220, TX MIMO processor 230, modem 232, MIMO detector 236, and/or receive processor 238.
  • an NCR (e.g., NCR 130) includes means for transmitting an indication of a sleep mode capability for using sleep modes that are associated with repeater modes; and/or means for switching from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • an NCR (e.g., NCR 130) includes means for receiving an indication of a sleep mode capability for using sleep modes that are associated with repeater modes; and/or means for communicating based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode.
  • a network entity e.g., network node 110 includes means for receiving an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding; and/or means for communicating based at least in 0097-4273PCT 16 part on the latency capability.
  • the means for the network entity to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
  • communication manager 150 transmit processor 220
  • TX MIMO processor 230 receive processor 238, controller/processor 240
  • memory 242 or scheduler 246.
  • MIMO detector 236, receive processor 238, controller/processor 240 controller/processor 240
  • memory 242 or scheduler 246.
  • the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components.
  • the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.
  • Fig.2 is provided as an example.
  • a network node may be implemented in an aggregated or disaggregated architecture.
  • a network entity may be implemented in an aggregated or disaggregated architecture.
  • a base station such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP, or a cell, among other examples
  • a base station may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.
  • Network entity or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit).
  • a disaggregated base station e.g., a disaggregated network node
  • a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.
  • VCU virtual central unit
  • VDU virtual distributed unit
  • VRU virtual radio unit
  • disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network 0097-4273PCT 17 configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed.
  • O-RAN open radio access network
  • vRAN also known as a cloud radio access network (C-RAN)
  • a disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
  • Fig.3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure.
  • the disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both).
  • a CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces.
  • Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links.
  • Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.
  • Each of the units including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • each of the units can be configured to communicate with one or more of the other units via the transmission medium.
  • each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • the CU 310 may host one or more higher layer control functions.
  • control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310.
  • the CU 310 may be configured to handle user plane functionality (for example, Central Unit – User Plane (CU-UP) 0097-4273PCT 18 functionality), control plane functionality (for example, Central Unit – Control Plane (CU-CP) functionality), or a combination thereof.
  • the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • a CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration.
  • the CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.
  • Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340.
  • the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP.
  • RLC radio link control
  • PHY high physical
  • the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples.
  • the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples.
  • FFT fast Fourier transform
  • iFFT inverse FFT
  • PRACH physical random access channel
  • Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
  • Each RU 340 may implement lower-layer functionality.
  • an RU 340 controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP), such as a lower layer functional split.
  • a functional split for example, a functional split defined by the 3GPP
  • each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120.
  • OTA over the air
  • real-time and non-real- time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330.
  • the SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface).
  • the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface 0097-4273PCT 19 (such as an O2 interface).
  • a cloud computing platform such as an open cloud (O-Cloud) platform 390
  • network element life cycle management such as to instantiate virtualized network elements
  • a cloud computing platform interface 0097-4273PCT 19 such as an O2 interface
  • Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325.
  • the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface.
  • O-eNB open eNB
  • the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface.
  • the SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.
  • the Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325.
  • the Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325.
  • the Near-RT RIC 325 may be configured to include a logical function that enables near-real- time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.
  • the near-RT RIC 325 may be a logical function that enables near-real-time control and optimization of O-RAN elements and resources via fine-grained data collection and actions over an E2 interface.
  • the Near-RT RIC 325 may be collocated with the RAN or network entity to provide the real-time processing, such as online ML training or near real time ML inference.
  • the non- RT RIC 315 may be a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in near-RT RIC 325, as well as ML inference with less latency specification.
  • the non-RT RIC 315 may be located further from the RAN or network node, such as on a cloud-based server or on an edge server.
  • the Non-RT RIC 315 may receive parameters or external enrichment information from external servers.
  • Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions.
  • the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance.
  • the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies).
  • Fig.3 is provided as an example. Other examples may differ from what is described with regard to Fig.3.
  • Fig.4 is a diagram of an example 400 of an NCR (e.g., NCR 130), in accordance with the present disclosure.
  • the NCR 430 may communicate with a network entity 410 (e.g., network node 110) and one or more UEs, such as UE 420, in a wireless communication network (e.g., wireless network 100 shown in Fig.1).
  • An NCR-MT component 432 of the NCR 430 may receive instructions on a control link for forwarding.
  • An NCR-Fwd component 434 of the NCR 430 may forward communications for the network entity 410 to the UE 420 and from the UE 420 to the network entity 410.
  • the NCR 430 may use a backhaul link to the network entity 410 and an access link to the UE 420.
  • one, none, or both of the NCR-MT component 432 and the NCR-Fwd component 434 may be active.
  • the NCR 430 When NCR-MT is ON, the NCR 430 may be in an uplink (UL) transmission (TX) mode, a downlink (DL) reception (RX) mode, or a full-duplex mode.
  • TX uplink
  • RX downlink
  • NCR-Fwd When NCR-Fwd is ON, the NCR 430 may be in DL forwarding, UL forwarding, or bidirectional (DL & UL) forwarding.
  • NCR-MT When NCR-MT is OFF, the NCR 430 may not transmit or receive communications.
  • NCR-MT may be in different sleep modes (such as micro, light, and deep) associated with different power consumption values and transition times (different sleep modes may be associated with which components of MT are OFF).
  • NCR-Fwd When NCR-Fwd is OFF, the NCR 430 does not forward any communications.
  • the NCR-Fwd may be in different sleep modes associated with different power consumption levels and transition times.
  • the NCR 430 may operate in consideration of a minimum latency for switching between repeater modes.
  • the minimum latency may be preconfigured via RRC signaling, specified in stored configuration information, and/or indicated to a network entity.
  • the NCR 430 may transmit an indication of a latency capability (e.g., a minimum latency to be able to switch repeater modes) to a network entity (e.g., network entity 410) via uplink control information (UCI), a medium access control control element (MAC CE), an RRC message, or operations, administration, and maintenance (OAM) signaling.
  • UCI uplink control information
  • MAC CE medium access control control element
  • OFAM operations, administration, and maintenance
  • the indication may be included in a capability report or associated with guard symbols used for IAB systems.
  • the latency capability of the NCR 430 may be updated or adjusted.
  • the latency indicated in a latency capability may be based at least in part on the state of NCR-MT/NCR-Fwd when the components are ON (e.g., TX, RX, TX and RX, UL forwarding, DL forwarding, bidirectional forwarding).
  • the latency may be based at least in part on the NCR-MT’s CC(s) and/or passbands over which NCR-Fwd is operating.
  • the latency may be based at least in part on the NCR-MT’s and/or NCR-Fwd’s beamforming 0097-4273PCT 21 configuration.
  • the latency may be based at least in part on the power configuration of NCR- MT and/or NCR-Fwd, where the power configuration can be related to NCR-MT’s TX and/or RX power (or phase spectral density (PSD)), NCR-Fwd’s RX power, NCR-Fwd’s TX power or amplification gain, and/or the relative power offset between NCR-MT’s and NCR-Fwd’s powers.
  • the latency may be based at least in part on (and be indicated or be associated with) different time resources.
  • the latency may be based at least in part on underlying slot or resource configurations, such DL, UL, flexible, full-duplex, HARD, SOFT, or unavailable.
  • the latency of switching between two repeater modes may not be symmetric.
  • the NCR 430 may not support simultaneous UL TX by NCR-MT and NCR-Fwd, or NCR-MT transmitting UL and NCR-Fwd forwarding UL.
  • the two signals may be time division multiplexed (TDMed).
  • Two associated modes for TDM may include a first sub-mode (Mode i) for MT transmitting UL and NCR-Fwd OFF and a second sub-mode (Mode j) for MT OFF and NCR-Fwd forwarding UL.
  • switching between the two modes may require a minimum latency that may be due to expected changes in the TX power setting, expected changes in the analog filter setting, or an internal delay of NCR-Fwd.
  • the NCR-Fwd may start forwarding UL before the UL TX reference, to accommodate an internal delay.
  • Fig.4 is provided as an example. Other examples may differ from what is described with regard to Fig.4.
  • Fig.5 is a diagram illustrating an example 500 associated with using a latency for switching repeater modes, in accordance with the present disclosure.
  • the NCR 430 may transmit an indication of a latency capability. This may include an indication of a minimum latency for switching repeater modes.
  • the minimum latency may be direction-specific for NCR-MT or for NCR-Fwd.
  • the minimum latency may be based at least in part on direction-specific transmit powers for NCR- MT or for NCR-Fwd.
  • the minimum latency may be specific to a time resource, such as a slot in a slot configuration. There may be a first minimum latency for switching from a first repeater mode to a second repeater mode and a second (different) minimum latency for switching from the second repeater mode to a third repeater mode or back to the first repeater mode.
  • the NCR 430 may receive an instruction message that is associated with the latency capability. For example, the NCR 430 may be instructed to switch repeater modes according to a timeline that is no shorter than the minimum latency indicated by the latency capability. [0101] As shown by reference number 515, the NCR 430 may switch repeater modes based at least in part on the latency capability. For example, the NCR 430 may switch from a first repeater mode to a second repeater mode based at least in part on the minimum latency. [0102] The NCR 430 may communicate with the network entity 410 and the UE 420 based at least in part on the latency capability.
  • the NCR 430 may forward communications based at least in part on the repeater mode. For example, the NCR 430 may forward communications if the repeater mode includes a repeater mode in which NCR-Fwd is ON.
  • NCR-MT may receive and decoding the side control information (e.g., sent via downlink control information (DCI)
  • DCI downlink control information
  • the NCR 430 may start forwarding (e.g., ramp up NCR-Fwd) communications a little earlier based at least in part on the latency capability and an internal delay of the NCR 430.
  • the NCR 430 may start forwarding while receiving and decoding control information for the NCR-MT.
  • the NCR 430 may use time domain duplexing information to determine the potential direction over which NCR-Fwd is expected to be fully active and forwarding.
  • the NCR 430 may start forwarding based at least in part on a control message.
  • the NCR 430 may start forwarding based at least in part on a received power (e.g., RSRP) on resources over which a side control is being monitored satisfying a power threshold (e.g., meets minimum RSRP).
  • a received power e.g., RSRP
  • the NCR 430 may start forwarding further based at least in part on DL DMRS detection.
  • the indication by the NCR 430 may indicate a capability for starting forwarding early based at least in part on a received power threshold and/or DMRS detection.
  • the NCR 430 may also receive an indication regarding whether the NCR 430 is allowed to start forwarding early.
  • the NCR 430 may receive configuration information that indicates one or more of resources (e.g., time, frequency, spatial), restrictions, or conditions (e.g., thresholds) for starting forwarding early.
  • the NCR 430 may indicate a preferred time offset (e.g., minimum k0 or kx) between a physical downlink control channel (PDCCH) communication and a physical downlink shared channel (PDSCH) communication and/or a preferred time offset (e.g., minimum k2 or kx) between an uplink grant (in a PDCCH) and a physical uplink shared channel (PUSCH) communication that are supported by the NCR 430.
  • a preferred time offset e.g., minimum k0 or kx
  • PUSCH physical uplink shared channel
  • the preferred time offsets may be associated with a latency between side control information (e.g., transmitted via DCI in a 0097-4273PCT 23 PDCCH communication) and NCR-Fwd operation (starting forwarding scheduled by the side control information).
  • the instruction message from the network entity 410 may be based at least in part on one or more of the preferred offsets.
  • the NCR 430 may receive a minimum offset indication that indicates a minimum offset between a PDCCH communication and starting forwarding. That is, the network entity 410 may notify or guarantee the NCR 430 that there will be at least some minimum offset between the PDCCH communication and the time of the NCR-Fwd operation.
  • the actual offset may be indicated in the PDCCH communication, and the actual offset may be equal to or greater in length than the indicated minimum offset.
  • the indication may indicate a sleep mode capability for using sleep modes (e.g., deep, mini, micro) that are associated with repeater modes.
  • the sleeps modes may be considered sub-modes for each repeater mode.
  • the NCR 430 communication may include switching from a first repeater mode to a second repeater mode based at least in part on a first sleep mode associated with the first repeater mode and/or a second sleep mode associated with the second repeater mode.
  • Fig.5 is provided as an example. Other examples may differ from what is described with regard to Fig.5.
  • Fig.6 is a diagram of an example 600 of an NCR using sleep modes, in accordance with the present disclosure.
  • the NCR 430 may support different sleep modes for NCR-MT and/or NCR-Fwd.
  • the sleep modes may be used in combination with a minimum latency or other latency capability aspects.
  • the supported sleep modes and associated information may be preconfigured via RRC signaling, specified in stored configuration information, and/or indicated by a network entity.
  • the associated information may include a level (e.g., relative level) of power consumption and/or minimum sleep-to-wake transition time across different sleep and active modes.
  • the NCR 430 may indicate a sleep mode capability for using sleep modes in association with repeater modes.
  • the sleep modes may be configured separately for each component, or jointly for NCR-MT and NCR-Fwd such that a sleep mode is common for both NCR-MT and NCR-MT.
  • the NCR 430 may indicate transition and/or switching times between different active and sleep states of NCR-MT and NCR-Fwd (e.g., NCR-MT micro sleep to NCR-Fwd light sleep).
  • the NCR 430 may also indicate a total (e.g., relative) power consumption for pairs of NCR-MT and NCR-Fwd states. Information about the power consumption and transition times can assist the network entity 410 with scheduling communications and resource allocation.
  • the NCR 430 may transmit state 0097-4273PCT 24 information that indicates a current repeater mode of the NCR and a sleep mode associated with the current repeater mode.
  • the NCR 430 may receive an instruction to use one or more sleep modes with specific repeater modes, such as sub-modes of the specific repeater modes.
  • the network entity 410 may transmit an indication of a latency capability and/or a sleep mode capability to the NCR 430, as shown by reference number 615.
  • the indications and instructions between the network entity 410 and the NCR 430 may be dynamic, semi-static, or semi-persistent. Semi-static and periodic patterns may be provided.
  • the NCR 430 may switch repeater modes based at least in part on the sleep mode capability and/or a latency capability. For example, the NCR 430 may switch from a first repeater mode to a second repeater mode based at least in part on a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode. The NCR 430 may switch repeater modes further based at least in part on a minimum latency.
  • the NCR 430 may forward communications based at least in part on the sleep modes used in association with repeater modes. In this way, the NCR 430 may conserve energy by sleeping and transitioning without losing communications, which results in conserving power, processing resources, and signaling resources.
  • the indication from the NCR 430 may indicate one or more of a capability of a total power consumption of the first repeater mode or a total power consumption of the second repeater mode.
  • the NCR 430 may switch repeater modes further based at least in part on the one or more of the total power consumption of the first repeater mode or the total power consumption of the second repeater mode.
  • the network entity 410 may transmit a wake-up signal to wake up the NCR-Fwd if wake-up signals are supported.
  • the NCR 430 may transmit an indication to the network entity 410 to the NCR-MT. This wake-up signal may be different from an ON indication and may serve the purpose of activating NCR-Fwd and possibly bringing the NCR 430 out of a deep sleep to be ready to start forwarding immediately, if needed.
  • the NCR 430 may accommodate two delay components.
  • a first delay component may include DL processing for NCR-MT (e.g., the time that NCR-MT may require to receive, process, or extract information from the side control indication).
  • the delay may be about 1 or 2 slots if indicated via DCI or about 3 to 5 milliseconds (ms) if indicated via a MAC CE.
  • a second delay component may be a time required for the NCR-Fwd to power ON and start a forwarding operation.
  • the NCR 430 may speed up forwarding operations such that the latency for waking up and/or switching repeater modes will be less than a sum of the first delay component and the second delay component.
  • Fig.6 is provided as an example.
  • Fig.7 is a diagram illustrating an example process 700 performed, for example, by an NCR, in accordance with the present disclosure.
  • Example process 700 is an example where the NCR (e.g., NCR 130, NCR 430) performs operations associated with indicating a latency capability for switching NCR repeater modes.
  • process 700 may include transmitting an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding (block 710).
  • process 700 may include communicating based at least in part on the latency capability (block 720).
  • the NCR e.g., using communication manager 1108, reception component 1102, and/or transmission component 1104 depicted in Fig.11
  • Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 700 includes receiving an instruction message that is associated with the latency capability and switching from a first repeater mode to a second repeater mode based at least in part on the instruction message.
  • the indication indicates a minimum latency for switching between a first repeater mode and a second repeater mode.
  • the indication is included in a capability report.
  • the indication is associated with preferred guard symbols.
  • the indication indicates a latency that is based at least in part on one or more of a direction of MT or a forwarding direction.
  • the indication indicates a latency that is based at least in part on one or more of MT component carriers or forwarding passbands.
  • the indication indicates a latency that is based at least in part on one or more of a direction-specific transmit power for MT or a direction-specific transmit power for forwarding.
  • the indication indicates a latency that is specific to a time resource.
  • the indication indicates a latency that is based at least in part on a slot or time resource configuration.
  • the indication indicates a first latency for switching between a first repeater mode and a second repeater mode and a second latency for switching between the second repeater mode and a third repeater mode, and the first latency is different than the second latency.
  • process 700 includes starting forwarding based at least in part on the latency capability and an internal delay of the NCR.
  • the indication indicates a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the communicating includes switching from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • process 700 includes starting forwarding while receiving and decoding control information for mobile termination.
  • the starting forwarding includes starting forwarding based at least in part on one or more of a received power threshold or DMRS detection.
  • the indication indicates a capability for starting forwarding based at least in part on a received power threshold or DMRS detection.
  • process 700 includes receiving configuration information that indicates one or more of resources, restrictions, or conditions for starting forwarding. 0097-4273PCT 27
  • the indication indicates a preferred time offset between receiving a control message in a PDCCH communication and starting forwarding.
  • process 700 includes receiving a minimum offset indication that indicates a minimum offset between receiving a control message in a PDCCH communication and starting forwarding.
  • Fig.7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig.7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.
  • Fig.8 is a diagram illustrating an example process 800 performed, for example, by an NCR, in accordance with the present disclosure.
  • Example process 800 is an example where the NCR (e.g., NCR 130, NCR 430) performs operations associated with indicating a sleep mode capability for NCR repeater modes.
  • process 800 may include transmitting an indication of a sleep mode capability for using sleep modes that are associated with repeater modes (block 810).
  • the NCR e.g., using communication manager 1108 and/or transmission component 1104 depicted in Fig.11
  • process 800 may include switching from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode (block 820).
  • the NCR e.g., using communication manager 1108 and/or switching component 1110 depicted in Fig.11
  • Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the indication indicates one or more of a capability of a total power consumption of the first repeater mode or a total power consumption of the second repeater mode.
  • the switching includes switching further based at least in part on the one or more of the total power 0097-4273PCT 28 consumption of the first repeater mode or the total power consumption of the second repeater mode.
  • process 800 includes receiving a sleep mode indication that indicates a sleep mode to use for a repeater mode.
  • process 800 includes transmitting state information that indicates a current repeater mode of the NCR and a sleep mode associated with the current repeater mode.
  • process 800 includes receiving a wake-up signal for waking up from a sleep mode used in associated with a repeater mode.
  • the wake-up signal is based at least in part on one or more of a processing delay, an application delay, or a power up delay.
  • Fig.8 shows example blocks of process 800
  • process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig.8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.
  • Fig.9 is a diagram illustrating an example process 900 performed, for example, by a network entity, in accordance with the present disclosure.
  • Example process 900 is an example where the network entity (e.g., network node 110, network entity 410) performs operations associated with using a latency capability and/or a sleep mode capability for controlling an NCR.
  • process 900 may include receiving an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding (block 910).
  • the network entity e.g., using communication manager 1208 and/or reception component 1202 depicted in Fig.12
  • process 900 may include communicating based at least in part on the latency capability (block 920).
  • the network entity e.g., using communication manager 1208, reception component 1202, and/or transmission component 1204 depicted in Fig.12
  • 0097-4273PCT 29 Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 900 includes transmitting an instruction message that is associated with the latency capability.
  • the indication indicates a minimum latency for switching between a first repeater mode and a second repeater mode.
  • the indication indicates a latency that is based at least in part on one or more of a direction-specific transmit power for MT or a direction-specific transmit power for forwarding.
  • the indication indicates a latency that is specific to a time resource.
  • the indication indicates a latency that is based at least in part on a slot or time resource configuration.
  • the indication indicates a first latency for switching between a first repeater mode and a second repeater mode and a second latency for switching between the second repeater mode and a third repeater mode, and the first latency is different than the second latency.
  • the indication indicates a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the indication indicates a capability for starting forwarding based at least in part on a received power threshold or DMRS detection.
  • process 900 includes transmitting configuration information that indicates one or more of resources, restrictions, conditions for starting forwarding, or a minimum offset indication that indicates a minimum offset between receiving a control message in a PDCCH communication and starting forwarding.
  • the indication indicates a preferred time offset between receiving a control message in a PDCCH communication and starting forwarding.
  • Fig.9 shows example blocks of process 900
  • process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks 0097-4273PCT 30 than those depicted in Fig.9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.
  • Fig.10 is a diagram illustrating an example process 1000 performed, for example, by an NCR, in accordance with the present disclosure.
  • Example process 1000 is an example where the NCR (e.g., NCR 130, NCR 430) performs operations associated with receiving an indication of a sleep mode capability.
  • the NCR e.g., NCR 130, NCR 430
  • process 1000 may include receiving an indication of a sleep mode capability for using sleep modes that are associated with repeater modes (block 1010).
  • the NCR e.g., using communication manager 1108 and/or reception component 1102 depicted in Fig.11
  • process 1000 may include communicating based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode (block 1020).
  • the NCR may communicate based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode, as described above.
  • Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the indication indicates one or more of a capability of a total power consumption of the first repeater mode or a total power consumption of the second repeater mode.
  • process 1000 includes transmitting a sleep mode indication that indicates a sleep mode to use for a repeater mode.
  • process 1000 includes receiving state information that indicates a current repeater mode of the NCR and a sleep mode associated with the current repeater mode.
  • process 1000 includes transmitting a wake-up signal for waking up from a sleep mode used in association with a repeater mode.
  • the wake-up signal is based at least in part on one or more of a processing delay, an application delay, or a power up delay.
  • a processing delay e.g., a processing delay, a power up delay.
  • a power up delay e.g., a power up delay.
  • Fig.10 shows example blocks of process 1000, in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig.10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
  • Fig.11 is a diagram of an example apparatus 1100 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1100 may be an NCR (e.g., NCR 130, NCR 430), or an NCR may include the apparatus 1100.
  • the apparatus 1100 includes a reception component 1102 and a transmission component 1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
  • the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the reception component 1102 and the transmission component 1104.
  • the apparatus 1100 may include the communication manager 1108.
  • the communication manager 1108 may control and/or otherwise manage one or more operations of the reception component 1102 and/or the transmission component 1104.
  • the communication manager 1108 may include one or more antennas, a modem, a controller/processor, a memory, or a combination thereof, of the NCR described in connection with Fig.2.
  • the communication manager 1108 may be, or be similar to, the communication manager 160 depicted in Figs.1 and 2.
  • the communication manager 1108 may be configured to perform one or more of the functions described as being performed by the communication manager 160.
  • the communication manager 1108 may include the reception component 1102 and/or the transmission component 1104.
  • the communication manager 1108 may include a switching component 1110, among other examples.
  • the apparatus 1100 may be configured to perform one or more operations described herein in connection with Figs.1-6.
  • the apparatus 1100 may be configured to perform one or more processes described herein, such as process 700 of Fig.7, process 800 of Fig.8, process 1000 of Fig.10, or a combination thereof.
  • the apparatus 1100 and/or one or more components shown in Fig.11 may include one or more components of the NCR described in connection with Fig.2. Additionally, or alternatively, one or more components shown in Fig.11 may be implemented within one or more components described in connection with Fig.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory.
  • a component may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1106.
  • the reception component 1102 may provide received communications to one or more other components of the apparatus 1100.
  • the reception component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1100.
  • the reception component 1102 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the NCR described in connection with Fig.2.
  • the transmission component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1106.
  • one or more other components of the apparatus 1100 may generate communications and may provide the generated communications to the transmission component 1104 for transmission to the apparatus 1106.
  • the transmission component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1106.
  • the transmission component 1104 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the NCR described in connection with Fig.2.
  • the transmission component 1104 may be co-located with the reception component 1102 in a transceiver.
  • the transmission component 1104 may transmit an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding.
  • the transmission component 1104 and the reception component 1102 may communicate based at least in part on the latency capability.
  • the reception component 1102 may receive an instruction message that is associated with the latency capability.
  • the switching component 1110 may switch from a first repeater mode to a second repeater mode based at least in part on the instruction message.
  • the transmission component 1104 may start forwarding based at least in part on the latency capability and an internal delay of the NCR.
  • the transmission component 1104 may start forwarding while receiving and decoding control information for mobile termination.
  • the reception component 1102 may receive configuration information that indicates one or more of resources, restrictions, or conditions for starting forwarding. 0097-4273PCT 33
  • the transmission component 1104 may transmit an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the switching component 1110 may switch from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • the reception component 1102 may receive a sleep mode indication that indicates a sleep mode to use for a repeater mode.
  • the transmission component 1104 may transmit state information that indicates a current repeater mode of the NCR and a sleep mode associated with the current repeater mode.
  • the reception component 1102 may receive a wake-up signal for waking up from a sleep mode used in association with a repeater mode.
  • the reception component 1102 may receive an indication of a sleep mode capability for using sleep modes that are associated with repeater modes.
  • the transmission component 1104 and the reception component 1102 may communicate based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode.
  • the transmission component 1104 may transmit a sleep mode indication that indicates a sleep mode to use for a repeater mode.
  • the reception component 1102 may receive state information that indicates a current repeater mode of the NCR and a sleep mode associated with the current repeater mode.
  • the transmission component 1104 may transmit a wake-up signal for waking up from a sleep mode used in association with a repeater mode.
  • the number and arrangement of components shown in Fig.11 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig.11. Furthermore, two or more components shown in Fig.11 may be implemented within a single component, or a single component shown in Fig.11 may be implemented as multiple, distributed components.
  • Fig.12 is a diagram of an example apparatus 1200 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1200 may be a network entity (e.g., network node 110, network entity 410), or a network entity may include the apparatus 1200.
  • the apparatus 1200 includes a reception component 1202 and a transmission component 1204, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
  • the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the reception component 1202 and the transmission component 1204.
  • the apparatus 1200 may include the communication manager 1208.
  • the communication manager 1208 may control and/or otherwise manage one or more operations of the reception component 1202 and/or the transmission component 1204.
  • the communication manager 1208 may include one or more antennas, a modem, a controller/processor, a memory, or a combination thereof, of the network entity described in connection with Fig.2.
  • the communication manager 1208 may be, or be similar to, the communication manager 150 depicted in Figs.1 and 2.
  • the communication manager 1208 may be configured to perform one or more of the functions described as being performed by the communication manager 150.
  • the communication manager 1208 may include the reception component 1202 and/or the transmission component 1204.
  • the communication manager 1208 may include an instruction component 1210, among other examples.
  • the apparatus 1200 may be configured to perform one or more operations described herein in connection with Figs.1-7. Additionally, or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as process 900 of Fig.9.
  • the apparatus 1200 and/or one or more components shown in Fig.12 may include one or more components of the network entity described in connection with Fig.2.
  • one or more components shown in Fig. 12 may be implemented within one or more components described in connection with Fig.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component. [0189]
  • the reception component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1206. The reception component 1202 may provide received communications to one or more other components of the apparatus 1200.
  • the reception component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1200.
  • the reception component 1202 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the network entity described in connection with Fig.2.
  • the transmission component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1206.
  • one or more other components of the apparatus 1200 may generate 0097-4273PCT 35 communications and may provide the generated communications to the transmission component 1204 for transmission to the apparatus 1206.
  • the transmission component 1204 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1206.
  • the transmission component 1204 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the network entity described in connection with Fig.2.
  • the transmission component 1204 may be co-located with the reception component 1202 in a transceiver.
  • the reception component 1202 may receive an indication of a latency capability of an NCR for switching between repeater modes for mobile termination and for forwarding.
  • the instruction component 1210 may instruct the NCR to use a latency for switching repeater modes and/or to use a sleep mode for a repeater mode based at least in part on NCR capabilities, UE capabilities, traffic conditions, and/or channel conditions.
  • the transmission component 1204 and the reception component 1202 may communicate based at least in part on the latency capability.
  • the transmission component 1204 may transmit an instruction message that is associated with the latency capability.
  • the transmission component 1204 may transmit configuration information that indicates one or more of resources, restrictions, or conditions for starting forwarding.
  • the number and arrangement of components shown in Fig.12 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig.12. Furthermore, two or more components shown in Fig.12 may be implemented within a single component, or a single component shown in Fig.12 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig.12 may perform one or more functions described as being performed by another set of components shown in Fig. 12.
  • Aspect 1 A method of wireless communication performed by a network-controlled repeater (NCR), comprising: transmitting an indication of a latency capability of the NCR for switching between repeater modes for mobile termination and for forwarding; and communicating based at least in part on the latency capability.
  • Aspect 2 The method of Aspect 1, further comprising: receiving an instruction message that is associated with the latency capability; and switching from a first repeater mode to a second repeater mode based at least in part on the instruction message.
  • Aspect 3 The method of any of Aspects 1-2, wherein the indication indicates a minimum latency for switching between a first repeater mode and a second repeater mode.
  • Aspect 4 The method of any of Aspects 1-3, wherein the indication is included in a capability report.
  • Aspect 5 The method of any of Aspects 1-4, wherein the indication is associated with preferred guard symbols.
  • Aspect 6 The method of any of Aspects 1-5, wherein the indication indicates a latency that is based at least in part on one or more of a direction of mobile termination or a forwarding direction.
  • Aspect 7 The method of any of Aspects 1-6, wherein the indication indicates a latency that is based at least in part on one or more of mobile termination component carriers or forwarding passbands.
  • Aspect 8 The method of any of Aspects 1-7, wherein the indication indicates a latency that is based at least in part on one or more of a direction-specific transmit power for mobile termination or a direction-specific transmit power for forwarding.
  • Aspect 9 The method of any of Aspects 1-8, wherein the indication indicates a latency that is specific to a time resource.
  • Aspect 10 The method of any of Aspects 1-9, wherein the indication indicates a latency that is based at least in part on a slot or time resource configuration.
  • Aspect 11 The method of any of Aspects 1-10, wherein the indication indicates a first latency for switching between a first repeater mode and a second repeater mode and a second latency for switching between the second repeater mode and a third repeater mode, and wherein the first latency is different than the second latency.
  • Aspect 12 The method of any of Aspects 1-11, further comprising starting forwarding based at least in part on the latency capability and an internal delay of the NCR.
  • Aspect 13 The method of any of Aspects 1-12, wherein the indication indicates a sleep mode capability for using sleep modes that are associated with repeater modes.
  • Aspect 14 The method of Aspect 13, wherein the communicating includes switching from a first repeater mode to a second repeater mode based at least in part on one or more of a first sleep mode associated with the first repeater mode or a second sleep mode associated with the second repeater mode.
  • Aspect 15 The method of any of Aspects 1-14, further comprising starting forwarding while receiving and decoding control information for mobile termination.
  • Aspect 16 The method of Aspect 15, wherein the starting forwarding includes starting forwarding based at least in part on one or more of a received power threshold or demodulation reference signal (DMRS) detection. 0097-4273PCT 37 [0211] Aspect 17: The method of Aspect 16, wherein the indication indicates a capability for starting forwarding based at least in part on a received power threshold or DMRS detection. [0212] Aspect 18: The method of any of Aspects 1-17, further comprising receiving configuration information that indicates one or more of resources, restrictions, or conditions for starting forwarding.
  • DMRS demodulation reference signal
  • Aspect 19 The method of any of Aspects 1-18, wherein the indication indicates a preferred time offset between receiving a control message in a physical downlink control channel communication and starting forwarding.
  • Aspect 20 The method of any of Aspects 1-19, further comprising receiving a minimum offset indication that indicates a minimum offset between receiving a control message in a physical downlink control channel communication and starting forwarding.
  • NCR network-controlled repeater
  • Aspect 22 The method of Aspect 21, wherein the indication indicates one or more of a capability of a total power consumption of the first repeater mode or a total power consumption of the second repeater mode.
  • Aspect 23 The method of Aspect 22, wherein the switching includes switching further based at least in part on the one or more of the total power consumption of the first repeater mode or the total power consumption of the second repeater mode.
  • Aspect 24 The method of any of Aspects 21-23, further comprising receiving a sleep mode indication that indicates a sleep mode to use for a repeater mode.
  • Aspect 25 The method of any of Aspects 21-24, further comprising transmitting state information that indicates a current repeater mode of the NCR and a sleep mode associated with the current repeater mode.
  • Aspect 26 The method of any of Aspects 21-25, further comprising receiving a wake- up signal for waking up from a sleep mode used in association with a repeater mode.
  • Aspect 27 The method of Aspect 26, wherein the wake-up signal is based at least in part on one or more of a processing delay, an application delay, or a power up delay.
  • Aspect 28 A method of wireless communication performed by a network entity, comprising: receiving an indication of a latency capability of a network-controlled repeater (NCR) for switching between repeater modes for mobile termination and for forwarding; and communicating based at least in part on the latency capability.
  • NCR network-controlled repeater
  • Aspect 29 The method of Aspect 28, further comprising transmitting an instruction message that is associated with the latency capability.
  • Aspect 30 The method of any of Aspects 28-29, wherein the indication indicates a minimum latency for switching between a first repeater mode and a second repeater mode.
  • Aspect 31 The method of any of Aspects 28-30, wherein the indication indicates a latency that is based at least in part on one or more of a direction-specific transmit power for mobile termination or a direction-specific transmit power for forwarding.
  • Aspect 32 The method of any of Aspects 28-31, wherein the indication indicates a latency that is specific to a time resource.
  • Aspect 33 The method of any of Aspects 28-32, wherein the indication indicates a latency that is based at least in part on a slot or time resource configuration.
  • Aspect 34 The method of any of Aspects 28-33, wherein the indication indicates a first latency for switching between a first repeater mode and a second repeater mode and a second latency for switching between the second repeater mode and a third repeater mode, and wherein the first latency is different than the second latency.
  • Aspect 35 The method of any of Aspects 28-34, wherein the indication indicates a sleep mode capability for using sleep modes that are associated with repeater modes.
  • Aspect 36 The method of any of Aspects 28-35, wherein the indication indicates a capability for starting forwarding based at least in part on a received power threshold or DMRS detection.
  • Aspect 37 The method of any of Aspects 28-36, further comprising transmitting configuration information that indicates one or more of resources, restrictions, conditions for starting forwarding, or a minimum offset indication that indicates a minimum offset between receiving a control message in a physical downlink control channel communication and starting forwarding.
  • Aspect 38 The method of any of Aspects 28-37, wherein the indication indicates a preferred time offset between receiving a control message in a physical downlink control channel communication and starting forwarding.
  • Aspect 39 A method of wireless communication performed by a network-controlled repeater (NCR), comprising: receiving an indication of a sleep mode capability for using sleep modes that are associated with repeater modes; and communicating based at least in part on one or more of a first sleep mode associated with a first repeater mode or a second sleep mode associated with a second repeater mode.
  • NCR network-controlled repeater
  • Aspect 41 The method of any of Aspects 39-40, further comprising transmitting a sleep mode indication that indicates a sleep mode to use for a repeater mode.
  • Aspect 42 The method of any of Aspects 39-41, further comprising receiving state information that indicates a current repeater mode of the NCR and a sleep mode associated with the current repeater mode.
  • Aspect 43 The method of Aspect 42, further comprising transmitting a wake-up signal for waking up from a sleep mode used in association with a repeater mode.
  • Aspect 44 The method of Aspect 43, wherein the wake-up signal is based at least in part on one or more of a processing delay, an application delay, or a power up delay.
  • Aspect 45 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-44.
  • Aspect 46 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-44.
  • Aspect 47 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-44.
  • Aspect 48 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-44.
  • Aspect 49 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-44.
  • the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software.
  • “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • a “processor” is implemented in hardware and/or a combination of hardware and software.
  • systems 0097-4273PCT 40 and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software.
  • the actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects.
  • the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).
  • the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”). 0097-4273PCT 41

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Radio Relay Systems (AREA)

Abstract

Selon divers aspects, la présente divulgation concerne le domaine des communications sans fil. Selon certains aspects, un répéteur commandé par réseau (NCR) peut transmettre une indication d'une capacité de latence du NCR pour commuter entre des modes de répéteur pour une terminaison mobile et pour un transfert. Le NCR peut communiquer sur la base, au moins en partie, de la capacité de latence. De nombreux autres aspects sont décrits.
EP23798643.5A 2022-11-04 2023-10-06 Indication de capacité de latence pour répéteur commandé par réseau Pending EP4612807A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP25226623.4A EP4701094A3 (fr) 2022-11-04 2023-10-06 Indication de capacité de latence pour répéteur commandé par réseau

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202263382409P 2022-11-04 2022-11-04
US18/481,947 US20240154687A1 (en) 2022-11-04 2023-10-05 Latency capability indication for network-controlled repeater
PCT/US2023/076229 WO2024097503A2 (fr) 2022-11-04 2023-10-06 Indication de capacité de latence pour répéteur commandé par réseau

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP25226623.4A Division EP4701094A3 (fr) 2022-11-04 2023-10-06 Indication de capacité de latence pour répéteur commandé par réseau

Publications (1)

Publication Number Publication Date
EP4612807A2 true EP4612807A2 (fr) 2025-09-10

Family

ID=88600603

Family Applications (2)

Application Number Title Priority Date Filing Date
EP25226623.4A Pending EP4701094A3 (fr) 2022-11-04 2023-10-06 Indication de capacité de latence pour répéteur commandé par réseau
EP23798643.5A Pending EP4612807A2 (fr) 2022-11-04 2023-10-06 Indication de capacité de latence pour répéteur commandé par réseau

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP25226623.4A Pending EP4701094A3 (fr) 2022-11-04 2023-10-06 Indication de capacité de latence pour répéteur commandé par réseau

Country Status (3)

Country Link
EP (2) EP4701094A3 (fr)
CN (1) CN120130032A (fr)
WO (1) WO2024097503A2 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5204811B2 (ja) * 2010-07-30 2013-06-05 株式会社バッファロー 無線通信を行う通信装置、無線通信システム、および、無線通信を行う方法
US11671168B2 (en) * 2019-09-05 2023-06-06 Qualcomm Incorporated Relay with a configurable mode of operation
US11831389B2 (en) * 2020-08-04 2023-11-28 Qualcomm Incorporated Techniques for reporting repeater communication capability

Also Published As

Publication number Publication date
WO2024097503A3 (fr) 2024-07-18
WO2024097503A2 (fr) 2024-05-10
CN120130032A (zh) 2025-06-10
EP4701094A2 (fr) 2026-02-25
EP4701094A3 (fr) 2026-04-15

Similar Documents

Publication Publication Date Title
US12052691B2 (en) Default beam for multi-downlink control information based multi-transmit receive point with unified transmission configuration indicator
US20240056862A1 (en) Conditional measurement gaps for delay critical traffic
WO2023184371A1 (fr) Groupe d'avance temporelle commun pour multiples opérations de point d'émission-réception
US20240154687A1 (en) Latency capability indication for network-controlled repeater
US20240114547A1 (en) Uplink subband for initial access
US20240107346A1 (en) Network energy savings mode associated with cross-link interference
US20240073718A1 (en) Cross-link interference measurement activity during network entity inactivity period
US20240064751A1 (en) Cross sub-band scheduling in a full-duplex network
WO2024011445A1 (fr) Signalisation d'avance temporelle pour de multiples points de réception d'émission
WO2024044431A1 (fr) Activité de mesure d'interférence de liaison croisée pendant une période d'inactivité d'entité de réseau
WO2023122438A1 (fr) Commutation de cellule primaire en fonction d'informations de commande de liaison descendante
EP4701094A2 (fr) Indication de capacité de latence pour répéteur commandé par réseau
US12490155B2 (en) Primary cell switching in accordance with downlink control information
US12588048B2 (en) Collision handling for multiple transmit receive points
US12452862B2 (en) Physical downlink control channel skipping based on an anchor and an indication
US12439410B2 (en) Transmitting an indication of a waveform used by a network node
US12550120B2 (en) Location of tracking reference signal availability information
US20240276485A1 (en) Duplex mode switching based at least in part on an indication of a skipped uplink occasion
US20240056972A1 (en) Network transmit inactivity time
US20240334429A1 (en) Transmission of packet via multiple configured grant configurations
WO2024197779A1 (fr) Indication de multiples occasions d'octroi configuré inutilisées
US20240267930A1 (en) Performing downlink channel monitoring on cells based on discontinuous reception states
WO2024207282A1 (fr) Commutation de bande
US20240098650A1 (en) Transmitting secondary cell transmissions using transmit power control adjustment values associated with a primary cell
WO2024035458A1 (fr) Temps d'inactivité de transmission de réseau

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250213

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)