[go: up one dir, main page]

WO2025174743A1 - Conception pour indication de faisceau initiée par un ue basée sur un rapport de csi - Google Patents

Conception pour indication de faisceau initiée par un ue basée sur un rapport de csi

Info

Publication number
WO2025174743A1
WO2025174743A1 PCT/US2025/015379 US2025015379W WO2025174743A1 WO 2025174743 A1 WO2025174743 A1 WO 2025174743A1 US 2025015379 W US2025015379 W US 2025015379W WO 2025174743 A1 WO2025174743 A1 WO 2025174743A1
Authority
WO
WIPO (PCT)
Prior art keywords
csi
uibr
report
circuitry
base station
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
PCT/US2025/015379
Other languages
English (en)
Inventor
Haitong Sun
Wei Zeng
Ankit Bhamri
Hong He
Dawei Zhang
Oghenekome Oteri
Xiang Chen
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.)
Apple Inc
Original Assignee
Apple 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
Application filed by Apple Inc filed Critical Apple Inc
Publication of WO2025174743A1 publication Critical patent/WO2025174743A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • H04B7/063—Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06964—Re-selection of one or more beams after beam failure

Definitions

  • Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods to facilitate UE-initiated/event-driven beam management for reducing overhead and latency in wireless communication systems.
  • LTE Long Term Evolution
  • 5G NR Fifth Generation New Radio
  • 5G-NR also simply referred to as NR
  • NR provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and/or lower battery consumption.
  • NR may allow for more flexible scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of NR to take advantage of higher throughputs possible at higher frequencies.
  • Wireless communication systems provide mobility through the use of battery-powered user equipment (UEs) that communicate with network components, such as base stations that may be referred to as gNBs or gNodeBs.
  • UEs battery-powered user equipment
  • network components such as base stations that may be referred to as gNBs or gNodeBs.
  • Embodiments relate to wireless communications, and more particularly to methods of providing a user equipment (UE)-initiated beam report (UIBR) to a base station (BS) in a wireless communication system, comprising: decoding, at a UE, configuration information from the BS, the configuration information indicating a plurality of channel state information (CSI) report occasions; determining, at the UE, to include or exclude the UIBR at each of the plurality of CSI report occasions; and encoding, at the UE, the UIBR for transmission to the BS at one of the plurality of CSI report occasions if the UE determined to include the UIBR at that CSI report occasion.
  • CSI channel state information
  • Embodiments relate to wireless communications, and more particularly to methods of wireless communication performed by a user equipment (UE), comprising: decoding, at the UE, configuration information transmitted by a base station (BS); determining, at the UE, a set of channel state information (CSI) processing units (CPU) that are occupied based on the configuration information; and counting the CPU for a UE initiated beam report (UIBR) regardless if the UE transmits the UIBR or not to the BS.
  • CSI channel state information
  • UIBR UE initiated beam report
  • UAVs unmanned aerial vehicles
  • UACs unmanned aerial controllers
  • IOT internet of things
  • FIG. 1 A illustrates an example wireless communication system according to some embodiments.
  • FIG. 1 B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.
  • UE user equipment
  • FIG. 3 illustrates an example block diagram of a server according to some embodiments.
  • FIG. 4 illustrates an example block diagram of a UE according to some embodiments.
  • FIG. 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.
  • FIG. 6 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.
  • FIG. 7 illustrates an example block diagram of an interface of baseband circuitry according to some embodiments.
  • FIG. 12 illustrates an example of a diagram showing CSI reporting occasions in relation to UE-initiated/even-driven reports in accordance with some embodiments.
  • FIG. 13 illustrates an example of a channel state report in accordance with some embodiments.
  • FIG. 14 illustrates an example of a diagram showing CSI reporting between a base station and a user equipment in accordance with some embodiments in accordance with some embodiments.
  • FIG. 17 is an illustration of an example of ASN.1 (Abstract Syntax Notation One) code according to some embodiments.
  • FIGS. 18-20 each illustrates an example method of UE-initiated/even- driven reporting according to some embodiments.
  • Memory Medium or Memory Any of various types of non-transitory memory devices or storage devices.
  • the term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc.
  • the memory medium may include other types of non-transitory memory as well or combinations thereof.
  • Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • a physical transmission medium such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs).
  • the programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores).
  • a programmable hardware element may also be referred to as "reconfigurable logic”.
  • Computer System any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices.
  • PC personal computer system
  • mainframe computer system workstation
  • network appliance Internet appliance
  • PDA personal digital assistant
  • television system grid computing system, or other device or combinations of devices.
  • computer system can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.
  • Channel - a medium used to convey information from a sender (transmitter) to a receiver.
  • channel widths may be variable (e.g., depending on device capability, band conditions, etc.).
  • LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz.
  • 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1 ) and up to 400 MHz in FR2.
  • WLAN channels may be 22 MHz wide while Bluetooth channels may be 1 MHz wide.
  • Other protocols and standards may include different definitions of channels.
  • some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and/or different channels for different uses such as data, control information, etc.
  • band - has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.
  • spectrum e.g., radio frequency spectrum
  • a user filling out an electronic form by selecting each field and providing input specifying information is filling out the form manually, even though the computer system will update the form in response to the user actions.
  • the form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields.
  • the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed).
  • the present specification provides various examples of operations being automatically performed in response to actions the user has taken.
  • Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1 % of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as set by the particular application.
  • Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner.
  • concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.
  • Information Element - a group of information that may be included within a Signaling Message or Data Flow which is sent across an interface.
  • rN when used in conjunction with an Information Element (IE) refers to a UE that is capable of supporting 3GPP Release N.
  • IE Information Element
  • r18 denotes a UE capable of supporting 3GPP release 18.
  • a UE that is capable of supporting a release greater than N may also be capable of supporting 3GPP Release N.
  • a UE that is not capable of supporting 3GPP Release N may not be capable of supporting the lEs that include rN.
  • Various components may be described as “configured to” perform a task or tasks.
  • “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected).
  • “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on.
  • the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.
  • the example embodiments are described with regard to communication between a Next Generation Node B (gNB) and a user equipment (UE).
  • gNB Next Generation Node B
  • UE user equipment
  • reference to a gNB or a UE is merely provided for illustrative purposes.
  • the example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to support for reducing energy usage by network components in wireless communication systems. Therefore, the gNB or UE as described herein is used to represent any appropriate type of electronic component.
  • the example embodiments are also described with regard to a fifth generation (5G) New Radio (NR) network that may configure a UE to support for reducing energy usage by network components in wireless communication systems.
  • 5G fifth generation
  • NR New Radio
  • reference to a 5G NR network is merely provided for illustrative purposes.
  • the example embodiments may be utilized with any appropriate type of network.
  • FIGS 1 A and 1 B Communication Systems
  • FIG. 1 A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of FIG. 1 A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.
  • the UE 106 may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate.
  • the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol.
  • the UE 106 might include a shared radio for communicating using either of LTE or 5G NR (or LTE or IxRTTor LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.
  • FIG. 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 204 which may execute program instructions for the base station 102. The processor(s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor(s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.
  • MMU memory management unit
  • the base station 102 may include at least one network port 270.
  • the network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figures 1 and 2.
  • the network port 270 may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider.
  • the core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices 106.
  • the network port 270 may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider).
  • base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”.
  • base station 102 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs).
  • TRPs transition and reception points
  • a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
  • the base station 102 may include at least one antenna 234, and possibly multiple antennas.
  • the at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 230.
  • the antenna 234 communicates with the radio 230 via communication chain 232.
  • Communication chain 232 may be a receive chain, a transmit chain or both.
  • the radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.
  • the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).
  • multiple wireless communication technologies e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.
  • the processor 204 of the base station 102 in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.
  • processor(s) 204 may be comprised of one or more processing elements.
  • processor(s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 204.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 204.
  • radio 230 may be comprised of one or more processing elements.
  • one or more processing elements may be included in radio 230.
  • radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 230.
  • the base station or gNB 102, and/or processors 204 thereof can be capable of and configured to determine, for a user equipment, a paging configuration that reduces energy usage by network components, e.g., base station or gNB 102, in wireless communication systems.
  • FIG. 3 Block Diagram of a Server
  • FIG. 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of FIG. 3 is merely one example of a possible server. As shown, the server 104 may include processor(s) 344 which may execute program instructions for the server 104. The processor(s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor(s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.
  • MMU memory management unit
  • the server 104 may be configured to provide a plurality of devices, such as base station 102, and UE devices 106 access to network functions, e.g., as further described herein.
  • the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network.
  • the server 104 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRG) network.
  • EPC legacy evolved packet core
  • NSG NR core
  • the server 104 may include hardware and software components for implementing or supporting implementation of features described herein.
  • the processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium).
  • the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof.
  • the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and/or 374 may be configured to implement or support implementation of part or all of the features described herein.
  • processor(s) 344 may be comprised of one or more processing elements.
  • processor(s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 344.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 344.
  • FIG. 4 Block Diagram of a User Equipment (UE)
  • the communication device 106 may include various types of memory (e.g., including NAND flash 410), an input/output interface such as connector l/F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 460, which may be integrated with or external to the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., BluetoothTM and WLAN circuitry).
  • communication device 106 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.
  • cellular communication circuitry 430 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR).
  • cellular communication circuitry 430 may include a single transmit chain that may be switched between radios dedicated to specific RATs.
  • the communication device 106 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 445.
  • SIM Subscriber Identity Module
  • UICC Universal Integrated Circuit Card
  • SIM entity is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards 445, one or more eUlCCs, one or more eSIMs, either removable or embedded, etc.
  • the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and/or otherwise implement SIM functionality.
  • the DSDS functionality may allow either of the two SIMs in the UE 106 to be on standby waiting for a voice call and/or data connection. In DSDS, when a call/data is established on one SIM, the other SIM is no longer active.
  • DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUlCC) that executes multiple SIM applications for different carriers and/or RATs.
  • modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 535.
  • RF front end 535 may include circuitry for transmitting and receiving radio signals.
  • RF front end 535 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534.
  • receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.
  • DL downlink
  • modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540.
  • RF front end 540 may include circuitry for transmitting and receiving radio signals.
  • RF front end 540 may include receive circuitry 542 and transmit circuitry 544.
  • receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.
  • processors 512 may include one or more processing elements.
  • processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 512.
  • the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
  • the components of the illustrated device 600 may be included in a UE 106 or a RAN node 102A.
  • the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC).
  • the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C- RAN) implementations).
  • C- RAN Cloud-RAN
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
  • the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the device 600 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 600 goes into a very low power state and it performs paging where, again, it periodically wakes up to listen to the network and then powers down at least portions of the device again.
  • the device 600 may not receive data in this state. In order to receive data, it will transition back to an RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 604 alone or in combination, may be used for defining clusters of PFs, POs, and PEIs during paging cycles.
  • the baseband circuitry 604 can be used to encode a message for transmission between a UE and a gNB, or decode a message received between a UE and a gNB.
  • the baseband circuitry 604 can be used to encode, at the gNB, paging configurations that define clusters of PFs, POs, and PEIs. These examples are not intended to be limiting.
  • the baseband circuitry can be used as previously described.
  • FIG. 7 Block Diagram of an Interface of Baseband Circuitry
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. It is noted that the baseband circuitry of FIG. 7 is merely one example of a possible circuitry, and that features of this disclosure may be implemented in any of various systems, as desired.
  • the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
  • Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
  • the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604
  • an application circuitry interface 714 e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6
  • an RF circuitry interface 716 e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a wireless hardware connectivity interface 718 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
  • FIG. 8 Control Plane Protocol Stack
  • FIG. 8 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 800 is shown as a communications protocol stack between the UE 106a (or alternatively, the UE 106b), the RAN node 102A (or alternatively, the RAN node 102B), and the mobility management entity (MME) 621 .
  • MME mobility management entity
  • the PHY layer 801 may transmit or receive information used by the MAC layer 802 over one or more air interfaces.
  • the PHY layer 801 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 805.
  • AMC link adaptation or adaptive modulation and coding
  • the PHY layer 801 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
  • FEC forward error correction
  • MIMO Multiple Input Multiple Output
  • the MAC layer 802 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.
  • SDUs MAC service data units
  • TB transport blocks
  • HARQ hybrid automatic repeat request
  • the RLC layer 803 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • the RLC layer 803 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • PDUs protocol data units
  • ARQ automatic repeat request
  • the RLC layer 803 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • the PDCP layer 804 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform insequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timerbased discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • SNs PDCP Sequence Numbers
  • the main services and functions of the RRC layer 805 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • system information e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)
  • AS access stratum
  • paging paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN
  • Said MIBs and SIBs may comprise one or more information elements (lEs), which may each comprise individual data fields or data structures.
  • the UE 601 and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804, and the RRC layer 805.
  • a Uu interface e.g., an LTE-Uu interface
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) 814 may ensure reliable delivery of signaling messages between the RAN node 102A and the MME 621 based, in part, on the IP protocol, supported by the IP layer 813.
  • the L2 layer 812 and the L1 layer 81 1 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • FIG. 9 User Plane Protocol Stack
  • FIG. 9 is an illustration of an example of a user plane protocol stack in accordance with some embodiments.
  • a user plane 900 is shown as a communications protocol stack between the UE 106A (or alternatively, the UE 106B or 106N), the RAN node 102A (or alternatively, the RAN node 102B), the S-GW 622, and the P-GW 623.
  • the user plane 900 may utilize at least some of the same protocol layers as the control plane 800.
  • the UE 601 and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804.
  • a Uu interface e.g., an LTE-Uu interface
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 904 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 903 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 102A and the S-GW 622 may utilize an S1 -U interface to exchange user plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the UDP/IP layer 903, and the GTP-U layer 904.
  • the S-GW 622 and the P-GW 623 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the L1 layer 811 , the L2 layer 812, the UDP/IP layer 903, and the GTP- U layer 904.
  • NAS protocols support the mobility of the UE 106 and the session management procedures to establish and maintain IP 813 connectivity between the UE 106 and the P-GW 623.
  • FIG. 10 Legacy Beam Management and Reporting (TCI and CSI)
  • Beam management is one of the key enabling technologies employed in 5G new radio (NR) systems.
  • NR beam management includes the following important components, beam indication, beam measurement and report, and beam failure recovery.
  • NR may use indicators transmitted by a base station to a UE, including a transmission configuration indicator (TCI).
  • TCI is an indicator used to convey specific transmission configuration parameters from the base station to the UE.
  • TCI may include parameters such as Quasi-collocation reference resource, power control related information.
  • TCI allows the UE to properly decode the transmitted signal by configuring its receiver parameters accordingly.
  • TCI is often included in control signaling messages exchanged between the base station and user equipment. TCI is crucial for efficient resource allocation, dynamic scheduling, and ensuring compatibility between different devices and network configurations.
  • uTCI unified TCI
  • a single set of TCI states are used to indicate the beams for multiple channel/signals for both DL and UL in one of two modes.
  • the first mode is “Joint TCI” meaning that one joint TCI can be applied to both UL and DL channel/signal.
  • the second mode is “Separate TCI” meaning that DL TCI is used for DL beam indication and UL TCI is used for UL beam indication.
  • the table 1600 in FIG. 16 depicts uTCI configurations under Schemes 1 , 1 or 2, or 2.
  • uTCI supports two schemes of TCI state indication.
  • common TCI indication for multiple channels/signals (1 ) the common TCI is always applied to dedicated PDCCH/PDSCH/PUCCH/PUSCH, (2) the common TCI can be optionally applied to aperiodic CSI-RS for BM/CSI, SRS for CB/NCB/AS/BM, (3) whether the common TCI is applied to the channels/signals is configured by RRC.
  • dedicated TCI indication for one channel/RS (1 ) this scheme is applied to the signals that the common TCI indication (Scheme 1 ) is not applied to, and (2) reuse 3GPP Release 16 signaling to provide the TCI indication for such channel/signal. Table 1600 in FIG. 16 shows these relationships.
  • channel state information plays a crucial role.
  • a base station can configure a UE to report CSI, including when to report CSI, how to report CSI, and what CSI parameters for the UE to measure and report back to the base station.
  • CSI provides feedback to the base station about the characteristics of a beam between the UE and the base station.
  • a base station may provide a channel state information reference signal (CSI-RS).
  • CSI-RS channel state information reference signal
  • Various configuration options enable the CSI-RS to be sent on multiple ports with various scheduling options such as periodic, semi persistent, and aperiodic.
  • the base station first configures the UE with a CSI-ReportConfig message.
  • the UE uses the channel state information reference signal (CSI-RS) to measure the CSI parameters, such as CQI, the PMI, and the Rl (alternatively, the UE may use other reference signals, such as demodulation reference signals (DMRS) in the synchronization signal (SS) physical broadcast channel (PBCH) block (SSB) as the reference signal for certain measurements).
  • DMRS demodulation reference signals
  • SS synchronization signal
  • PBCH physical broadcast channel
  • SSB physical broadcast channel block
  • the base station Upon receiving the CSI parameters, the base station can use the measurements in the CSI-Report to schedule downlink data transmissions (such as modulation scheme, code rate, number of transmission layers, and MIMO precoding) accordingly.
  • Another mechanism under Legacy 3GPP is CSI resource counting.
  • a base station may transmit reference signals to UEs in order for UEs to perform beam measurements.
  • the UE may be configured to receive and report on a periodic CSI-RS.
  • the UE may have a limited number of resources for processing the CSI. These processing resources of the UE may be referred to as CSI processing units (CPUs).
  • Conventional scheduling techniques may allow the UE to “count” CPU occupancy to prevent the base station from over configuring the UE with CSI.
  • the number of occupied CPUs may be an accumulated number (or aggregated number) of occupied CPUs for configured CSI operations.
  • the UE may perform a number of CSI operations based on the determined number of CPUs.
  • the base station may configure the UE to perform the number of CSI operations and may refrain from configuring additional CSI operations if an additional CSI operation will require more CPUs than are available at the UE. That is, the number of CSI operations configured for a UE by a base station may use up to a total number of CPUs in the CPU pool at the UE.
  • Another drawback to the current CSI reporting framework is that a UE may not be able to timely report changes in beam quality if there are insufficient CSI reporting occasions configured by the base station. This can cause increased beam failures and latency issues in the communication of data between the UE and the BS.
  • FIGS. 1 1 - 17 Novel Beam Reporting Configurations and Procedure
  • the present disclosure provides a user equipment initiated/event-driven beam report (UIBR) encoded and transmitted from a UE to a base station.
  • the UIBR can indicate beam parameters of a reference signal as measured by the UE.
  • the UIBR can indicate one or more parameters of a reference signal, such as Reference Signal Received Power (RSRP) or Signal-to-lnterference-plus-Noise Ratio (SINR).
  • RSRP Reference Signal Received Power
  • SINR Signal-to-lnterference-plus-Noise Ratio
  • the UIBR may report parameters for multiple beams.
  • a diagram 1100 shows that a base station (gNB) may encode and transmit channel state configuration information (CSCI) to a UE.
  • CSCI channel state configuration information
  • the CSCI of the present disclosure may be the same as or different from CSI configurations specified by under Legacy specifications, e.g., 3GPP Release 18 (CSI- ReportConfig).
  • CSI- ReportConfig 3GPP Release 18
  • the CSCI of the present disclosure may differ from Legacy CSI configurations to accommodate the features described herein.
  • the CSCI may indicate a schedule of channel state (CS) report occasions to the UE.
  • the CS report occasions configured by the base station may be one of periodic, semi persistent, or aperiodic.
  • the CS report occasions may be configured with the same as channel state information (CSI) report occasions configured under Legacy specifications, e.g., 3GPP Release 18 (reportConfigType - periodic, semipersistent, aperiodic).
  • CSI channel state information
  • CS report occasions according to the present disclosure may be configured identically to, or differently from, Legacy CSI report occasions.
  • the CSCI of the present disclosure may further indicate to the UE the parameters to measure. These parameters may be the same as or different than the parameters configured by Legacy CSI configurations (reportQuantity). These parameters may include one or more of RSRP, or SINR.
  • the CSCI may further explicitly indicate a channel measurement resource (CMR) that identifies the resource (e.g. reference signal (RS)) from which the UE is to measure the parameters. That is, the CMR refers to the specific physical resources allocated for measuring the channel state information.
  • the CSCI may indicate, as CMR, one or more of: a list of uTCI state, a list of synchronization signal (SS) physical broadcast channel (PBCH) blocks (SSBs), or a channel state information reference signal (CSI-RS).
  • CMR channel measurement resource
  • RS reference signal
  • the list of uTCI state is chosen from a list provided by the base station (e.g., the dl-OrJointTCI-StateList-r17 IE per the PDSCH-Config IE).
  • the list can be chosen from (1 ) only DL uTCI (e.g., the dl-OrJointTCI- StateList-r17 IE per the PDSCH-Config IE), (2) DL uTCI or UL uTCI (i.e., the ul- TCI-StateList-r17 IE per BWP-UplinkDedicated IE), but not a mixture of DL uTCI and UL unified TCI, or (3) a mixture of DL uTCI and UL uTCI.
  • the list of uTCI states can be selected from (1 ) only medium access control (MAC) control element (MAC-CE) activated uTCI states, or (2) all radio resource control (RRC) configured uTCI states.
  • MAC medium access control
  • RRC radio resource control
  • SSBs can be configured with a different Physical Cell Identity (PCI) from the serving cell.
  • PCI Physical Cell Identity
  • the CSCI may not explicitly indicate a CMR to the UE.
  • the CMR is implicitly configured by the UE as one or more of the following (1 ) all the MAC-CE activated uTCI states, or (2) all the RRC configured uTCI states.
  • the list of uTCI state can be chosen from a list provided by the base station (e.g., the dl-OrJointTCI-Statel_ist-r17 IE per the PDSCH-Config IE).
  • the list can be chosen from (1 ) only DL uTCI (e.g., the dl-OrJointTCI-StateList-r17 IE per the PDSCH-Config IE), (2) DL uTCI or UL uTCI (i.e., the ul-TCI-Statel_ist-r17 IE per the BWP-UplinkDedicated IE), but not a mixture of DL uTCI and UL unified TCI, or (3) a mixture of DL uTCI and UL uTCI.
  • DL uTCI e.g., the dl-OrJointTCI-StateList-r17 IE per the PDSCH-Config IE
  • DL uTCI or UL uTCI i.e., the ul-TCI-Statel_ist-r17 IE per the BWP-UplinkDedicated IE
  • uTCI state when uTCI state is used as a CMR, and two quasi- co-located (QCL) sources (QCL-Info) are configured by TCI-State as shown in the ASN.1 code 1700 shown in FIG. 17, then two options are available. Under option 1 , only the QCL source (QCL-Info) with qcl-Type of “typeD” is used for beam measurement. Under option 2, both QCL sources are used for beam measurement.
  • the CSCI may further explicitly indicate the events/conditions monitored by a UE and the events or conditions that can trigger encoding and transmission of a UIBR by the UE.
  • a UE monitored event/condition may determine if a different uTCI state has a greater measured quality than an active TCI state. In an embodiment, the measured quality may need to be greater than a quality threshold. In an embodiment, a UE monitored event/condition may determine if the quality of the active TCI state is below a quality threshold. For both of the foregoing embodiments, each of the UE monitored event/condition may be measured on multiple occasions, i.e., the event/condition may need to be met for multiple consecutive times to trigger the UIBR.
  • any quality threshold values may be configured by the CSCI or another IE or pre-configured (hardcoded) at the UE.
  • quality measurements may consider one or both of the following: Reference Signal Received Power (RSRP) or Signal-to-lnterference-plus-Noise Ratio (SINR).
  • RSRP Reference Signal Received Power
  • SINR Signal-to-lnterference-plus-Noise Ratio
  • the CSCI may further explicitly indicate to the UE that group-based beam reporting is allowed.
  • a pair of beams i.e., uTCI state
  • the UE reported pair of beams can be used to receive simultaneously, and transmit simultaneously.
  • the UE can report two pairs of beams, one pair of beams can be used to receive simultaneously only, and the other pair of beams can be used to transmit simultaneously only.
  • the UE reported pair of beams can be used to receive simultaneously only.
  • the UE reported pair of beams can be used to transmit simultaneously only.
  • one pair of beams may be used, with one beam used to transmit signals from the UE and one beam used to receive signals at the UE.
  • N 4 beams or pairs of beams can be reported.
  • the CSCI may further explicitly indicate to the UE that a capability index (Capabilityindex) IE can be reported together in the UIBR with each reported beam. In an embodiment, the CSCI may further explicitly indicate to the UE that a capability index (Capabilityindex) IE cannot be reported together in the UIBR with each reported beam. In an embodiment, the capability index (Capabilityindex) IE indicates the maximum number of SRS ports.
  • the CSCI may further explicitly indicate to the UE that beam quality can be reported together with each reported beam. In an embodiment, the CSCI may further explicitly indicate to the UE that beam quality cannot be reported together with each reported beam. In an embodiment, beam quality can be used to configure the UE to measure one or both of the following: RSRP or SINR.
  • the UE may be pre-configured (hard coded) with any of the CSCI identified above to eliminate the need for the base station to configure the UE in some or all instances. It will be appreciated that pre-configuring the UE with CSCI saves overhead resources and improves latency.
  • the UE may independently monitor and detect events and conditions related to beam quality that may need to be reported to the base station.
  • the UE may encode and transmit a UE-initiated/event-driven beam report (UIBR) to the base station at one of an upcoming CS report occasions.
  • UIBR can be carried by the Physical Uplink Control Channel (PUCCH), and is can be communicated using Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • the UIBR can also be carried by the Physical Uplink Shared Channel (PUSCH), and can be activated/deactivated by a Medium Access Control - Control Element (MAC-CE).
  • the UIBR can be carried by the Physical Uplink Shared Channel (PUSCH), and can be triggered by Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • FIG. 12 depicting plurality of CS report occasions that allow the UE to communicate the UIBR to the base station.
  • the base station may configure the plurality of CS report occasions with the CSCI encoded and transmitted to the UE.
  • the CS report occasions are one of periodic, semi-persistent, or aperiodic.
  • the CS report occasions are one of PUSCH or PUCCH occasions.
  • the UE may choose to provide the UIBR or not at each CSI report occasions based on the determination of a UE event/condition. For example, when the UE detects an event or condition that may impact beam management, the UE can encode and transmit the UIBR to the base station in the next available CS report occasion.
  • the CSCI may indicate the event/condition monitored by a UE that can trigger encoding and transmission of a UIBR.
  • a UE monitored event/condition may determine if a different uTCI state has a greater measured quality than an active TCI state.
  • the measured quality may need to be greater than a quality threshold.
  • a UE monitored event/condition may determine if the quality of the active TCI state is below a quality threshold.
  • each of the UE monitored event/condition may be measured on multiple occasions, i.e., the event/condition may need to be met for multiple consecutive times to trigger the UIBR.
  • any quality threshold values may be configured by the CSCI or pre-configured (hardcoded) at the UE.
  • quality measurements may consider one or both of the following: Reference Signal Received Power (RSRP) or Signal-to-lnterference-plus-Noise Ratio (SINR).
  • RSRP Reference Signal Received Power
  • SINR Signal-to-lnterference-plus-Noise Ratio
  • the event/condition monitored by a UE by be implicitly indicated or pre-configured at the UE.
  • the CSR may comprise a Part 1 and a Part 2.
  • Part 1 indicates if Part 2 contains the UIBR.
  • Part 1 may contain the minimum number of bits to indicate if the UIBR is included or excluded in Part 2.
  • a “0” in Part 1 indicates that the UIBR is excluded from Part 2, while a “1 ” indicates that the UIBR is carried in Part 2.
  • other indicators may be used to indicate the inclusion or exclusion of the UIBR.
  • a diagram 1400 shows that once configured by the base station by CSCI, the UE may independently monitor and detect events and conditions related to a CMR. In response to detecting an event/condition, the UE may encode and transmit a UE- initiated/event-driven beam report (UIBR) as part of a CSR (e.g., in Part 2) to the base station at one of an upcoming CS report occasions, as illustrated in the exemplary block diagram 1500 of FIG. 15. If an event/condition is not detected, the base station still encodes and transmits the CSR, but without the UIBR.
  • UIBR UE- initiated/event-driven beam report
  • UEs may have a limited number of resources for processing CSI. These processing resources of the UE may be referred to as CSI processing units (CPUs).
  • CPUs CSI processing units
  • the number of occupied CPUs may be an accumulated number (or aggregated number) of occupied CPUs for configured CSI operations.
  • CPUs may be estimated based on certain parameters, include algorithm complexity, number of antennas (CSI-RS resource/port), modulation scheme, UE processing capabilities, and resource allocation (CPU cycles and memory).
  • the present disclosure may utilize Legacy processes and methods for determining CPU as is known in the art.
  • the UE may be configured to perform a limited number of CSI operations based on the determined number of CPUs.
  • the base station may configure the UE to perform the number of CSI operations and may refrain from configuring additional CSI operations if an additional CSI operation will require more CPUs than available. That is, the number of CSI operations required by a base station may use up to a total number of CPUs in the CPU pool at the UE.
  • a UE may not report UIBR at every scheduled CS reporting occasions as described above. Nevertheless, the CPU is counted by the UE for the UIBR even though it is not provided to the base station. In another embodiment, the CPU is only counted if the UIBR is provided to the base station by the UE.
  • CSI-RS resource/port counting various options are available under the present disclosure, including: (1 ) CSI-RS resource/port is counted regardless whether UE reports the beam or not, or (2) CSI-RS resource/port is counted only when UE reports the beam.
  • the CSI-RS resource/port is counted starting from the end of when the MAC-CE activation command is applied, and ending at the end of when the MAC-CE deactivation command is applied.
  • the CSI-RS resource/port is counted starting when the periodic CSI-RS is configured by RRC, and ending when the periodic CSI-RS configuration is released by RRC.
  • Example 1 is directed to a method of providing a user equipment (UE)- initiated beam report (UIBR) to a base station (BS) in a wireless communication system, the method comprising: decoding, at a UE, configuration information from the BS, the configuration information indicating a plurality of channel state information (CSI) report occasions; determining, at the UE, to include or exclude the UIBR at each of the plurality of CSI report occasions; and encoding, at the UE, the UIBR for transmission to the BS at one of the plurality of CSI report occasions if the UE determined to include the UIBR at that CSI report occasion.
  • CSI channel state information
  • Example 31 includes an apparatus configured to cause a user equipment (UE) to perform any of the methods of Examples 1 -19 and 26-31.
  • Example 33 includes a baseband processor configured to perform one or more of the methods Examples 1 to 31.
  • Example 34 includes an apparatus configured to cause a base station (BS) to perform any of the methods of Examples 20-25.
  • Example 35 includes a computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the operations or methods described herein.
  • a non-transitory computer-readable memory medium may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.

Landscapes

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

Abstract

Un procédé de fourniture d'un rapport de faisceau initié par un équipement utilisateur (UE) (UIBR) à une station de base (BS) dans un système de communication sans fil consiste à décoder, au niveau d'un UE, des informations de configuration provenant de la BS, les informations de configuration indiquant une pluralité d'occasions de rapport d'informations d'état de canal (CSI) ; déterminer, au niveau de l'UE, d'inclure ou d'exclure l'UIBR à chacune de la pluralité d'occasions de rapport de CSI ; et coder, au niveau de l'UE, de l'UIBR pour une transmission à la BS à l'une de la pluralité d'occasions de rapport de CSI si l'UE a déterminé d'inclure l'UIBR à cette occasion de rapport de CSI.
PCT/US2025/015379 2024-02-16 2025-02-11 Conception pour indication de faisceau initiée par un ue basée sur un rapport de csi Pending WO2025174743A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463554923P 2024-02-16 2024-02-16
US63/554,923 2024-02-16

Publications (1)

Publication Number Publication Date
WO2025174743A1 true WO2025174743A1 (fr) 2025-08-21

Family

ID=94968636

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/015379 Pending WO2025174743A1 (fr) 2024-02-16 2025-02-11 Conception pour indication de faisceau initiée par un ue basée sur un rapport de csi

Country Status (1)

Country Link
WO (1) WO2025174743A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230344490A1 (en) * 2020-09-15 2023-10-26 Lg Electronics Inc. Method and device for beam reporting in wireless communication system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230344490A1 (en) * 2020-09-15 2023-10-26 Lg Electronics Inc. Method and device for beam reporting in wireless communication system

Similar Documents

Publication Publication Date Title
US11917626B2 (en) Uplink transmission for multi-panel operation
US12250046B2 (en) Channel state information concatenation and antenna port measurement
US12101153B2 (en) Group based beam reporting and channel state information reference signal configuration in new radio systems
US11006429B2 (en) Antenna panel switching and beam indication
CN110365458B (zh) 准共位（qcl）指示的系统和方法
US10897776B2 (en) Downlink control information design with shorter TTI
US10812169B2 (en) User equipment measurements for new radio
US20240206004A1 (en) Multiple cdrx configurations and dynamic configuration switching for xr traffic
WO2025174743A1 (fr) Conception pour indication de faisceau initiée par un ue basée sur un rapport de csi
WO2025112009A1 (fr) Appareil et procédé de configuration pf/po en grappe et de transmission pei pour l'économie d'énergie du réseau
WO2025171562A1 (fr) Procédés pour la transmission de signaux de diffusion et la gestion de cellules dans des communications sans fil
WO2025171561A1 (fr) Rapport de faisceau déclenché par un ue (uibr) à l'aide de ressources (ul) d'autorisation configurée pour plage de fréquence deux (fr2)
WO2025030430A1 (fr) Signalisation et capacité d'agrégation de porteuses sans ssb inter-bandes
WO2025171558A1 (fr) Rapport de faisceau déclenché par un équipement utilisateur (ue) basé sur un canal de commande (uibr) par un ue pour une plage de fréquences deux (fr2)
WO2025208463A1 (fr) Rrm basé sur une lp-wur en mode edrx de veille et inactif
WO2025171549A1 (fr) Procédés d'adaptation de ressources pour signal de synchronisation et signaux prach dans une communication sans fil
WO2025208420A1 (fr) Prédiction de mesure de modèle basée sur l'intelligence artificielle côté réseau
WO2025111920A1 (fr) Configuration pour signal de réveil d'ue déclenchant une transmission et une surveillance de sib1
WO2025091266A1 (fr) Conception cssf pour opération scell sans ssb
WO2025231656A1 (fr) Conception commune pour deux types de complexité de dispositifs de l'ido ambiant
WO2025091222A1 (fr) Adaptation de niveau d'agrégation dans une surveillance de liaison radio
US20240032002A1 (en) Dynamic resource allocation
WO2025199805A1 (fr) Mesure lte inter-rat sans intervalle de mesure
WO2025155933A1 (fr) Signalisation d'uto-uci pour configurations multiples d'octroi configuré
WO2025117482A1 (fr) Transmission de csi reconstruite d'un réseau à un équipement utilisateur (ue)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25711270

Country of ref document: EP

Kind code of ref document: A1